Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Quality Measures (FHIR)
-
current
-
Clinical Quality Information
-
CQFM Library [deprecated]
-
Agree with recommendation and will update accordingly:
1. Updating profiles page (as part of work voted in 44642 https://jira.hl7.org/browse/FHIR-44642) to include use cases for ELM use.
2. Update second paragraph https://build.fhir.org/ig/HL7/cqf-measures/measure-conformance.html#including-elm to include sentence in red below:
Both CQL and ELM representations may be included in the Library resource depending on the requirements of the appropriate profile. It can follow the approach of supporting human readability (in this case, the high-level CQL syntax) and a canonical representation for machine processing (in this case, CQL’s Expression Logical Model (ELM)). This approach facilitates human review of measure logic via CQL and implementation of that logic in tools via ELM. For implementations unable to compile CQL, ELM representations should be included.
3. In addition, update the third conformance statement to state:
Conformance Requirement 3.2 (Referencing ELM Documents):
- To support implementations that cannot compile CQL, an ELM translation SHOULD be provided, in either XML or JSON format.
Agree with recommendation and will update accordingly: 1. Updating profiles page (as part of work voted in 44642 https://jira.hl7.org/browse/FHIR-44642 ) to include use cases for ELM use. 2. Update second paragraph https://build.fhir.org/ig/HL7/cqf-measures/measure-conformance.html#including-elm to include sentence in red below: Both CQL and ELM representations may be included in the Library resource depending on the requirements of the appropriate profile. It can follow the approach of supporting human readability (in this case, the high-level CQL syntax) and a canonical representation for machine processing (in this case, CQL’s Expression Logical Model (ELM)). This approach facilitates human review of measure logic via CQL and implementation of that logic in tools via ELM. For implementations unable to compile CQL, ELM representations should be included. 3. In addition, update the third conformance statement to state: Conformance Requirement 3.2 (Referencing ELM Documents): To support implementations that cannot compile CQL , an ELM translation SHOULD be provided, in either XML or JSON format. -
Juliet Rubini/Jen Seeman: 21-0-1
-
Clarification
-
Non-substantive
Description
Given that the QM IG requires ELM to be included in a Library, this forces all parties that author CQL to have a CQL-to-ELM converter. The assumption that all authors will use one and the same authoring tooling suite doesn't hold - in the spirit of FHIR we try and move complexity to the server, not the client. A server could implement this conversion as part of the existing $convert operation, e.g. from application/cql+json to application/elm+json.
The requirement to have an ELM expression in a Library seems problematic to me, a server could simply add it if it's missing - so why this specific requirement? An authoring client tool should never have to have awareness of the existence of ELM IMHO. Nor should a client that evaluates a Library.