Using CQL with FHIR
2.0.0-ballot - STU2Ballot International flag

Using CQL with FHIR, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cql-ig/ and changes regularly. See the Directory of published versions

Changes

This page details changes made in each version of the Using CQL with FHIR Implementation Guide.

STU2 Ballot (version 2.0.0-ballot)

  • FHIR-48919: Updated discussion of negation to address rejected proposals use case and added activity extent discussion. Applied (here)
  • FHIR-48819: Documented fluent function naming convention. Applied (here)
  • FHIR-48814: Updated examples that did not follow naming conventions. Applied (here)
  • FHIR-48641: Added FHIRHelpers and FHIRCommon libraries. Applied (here)
  • FHIR-48529: Noted difference in precision between CQL and FHIR date/time types. Applied (here)
  • FHIR-48332: Noted Long mapping to integer64 is only available in R5 and above. Applied (here)
  • FHIR-46423: Added guidance on library name length. Applied (here)
  • FHIR-46112: Clarified mapping for lists of lists. Applied (here)
  • FHIR-45580: Expanded guidance on use of terminologies. Applied (here)
  • FHIR-45579: Updated missing information example to improve flow. Applied (here)

STU1 Publication (version 1.0.0)

The following changes were made as a result of comments received in the 1.0.0-ballot

NOTE: This changelist is inclusive of changes published in the 1.0.0-snapshot version

Non-Compatible Changes

Compatible, Substanive Changes

  • FHIR-43885: A Conformance Requirement that SHOULD be followed is confusing Applied (here)
  • FHIR-43780: Relax prohibition against string-based membership testing Applied (here)
  • FHIR-43698: Conformance requirement 2.10 - provide example Applied (here)

Non-Substantive Changes

Initial STU 1 Ballot Changes (version 1.0.0-ballot)

This is the first ballot of this implementation guide in this form, but the content has been balloted and published in multiple prior implementation guides, including:

Change Summary This ballot made the following major changes:

The following changes were made as a result of ballot comments received in the September 2023 ballot of the Canonical Resource Management Infrastructure IG. One of those comments was the suggestion to break this CQL-specific content out into its own implementation guide; this IG is the result of that change.

  • FHIR-43076: Use a dataAbsentReason extension to indicate missing results
  • FHIR-43075: Add guidance on missing information
  • FHIR-42921: Consider requiring the use of a SignatureLevel higher than none
  • FHIR-42574: Libraries are not required for CQL
  • FHIR-42573: Explaing conformance requirement 4.12
  • FHIR-42571: Representation in a Library needs clarification
  • FHIR-42570: Code URI expectation inconsistent
  • FHIR-42569: What is "knowledge artifact CQL"?
  • FHIR-42568: Why so much discussion about VSAC in an international spec?
  • FHIR-42567: Use a value set avoiding OIDs
  • FHIR-42566: Update location of code system URIs
  • FHIR-42565: How is the association between a namespace and URI established?
  • FHIR-42562: Put versioning stuff together
  • FHIR-42561: Explain identifier rules
  • FHIR-42560: Better explain library declarations
  • FHIR-42559: Clarify language around CQL artifacts
  • FHIR-41869: No content in this ModelInfo section of Using CQL
  • FHIR-41868: Provide more context in examples