This page is part of the Using CQL with FHIR Implementation Guide (v1.0.0-snapshot: STU1 Draft) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
Changes
This page details changes made in each version of the Using CQL with FHIR Implementation Guide.
STU1 Reconciliation Changes (version 1.0.0-ballot)
The following changes were made as reconciliation of issues raised in the 1.0.0-ballot
The following trackers were applied for this version:
Status: Summary:(Jira Issue)
- Applied: Missing period (FHIR-44091) (Applied here)
- Applied: Convert text link to hyperlink (FHIR-43777) (Applied here)
- Applied: Define or Replace “Initial Case” (FHIR-43785) (Applied here)
- Applied: CQL Library Evaluate: return parameter doesn’t always return all expressions (FHIR-43886) (Applied here)
- Applied: Repetitive IG (FHIR-44059) (Applied here)
- Applied: Clarify double-braces / context in FHIR Query Pattern extension (FHIR-43915) Applied (here)
- Applied: Typos: package, csn (FHIR-43881) Applied (here)
- Applied: Consider adding an acronyms page (FHIR-44063) Applied (here), (here), (here), and (here)
- Applied: Typo: A library profiles (FHIR-43733) Applied (here)
- Applied: Incorrect reference to CRMI IG (FHIR-43732) Applied (here)
- Applied: Incomplete Sentence (FHIR-44082) Applied (here)
- Applied: Page listing does not match menu (FHIR-43731) Applied (here) and in menu.xml
- Applied: Should Health Level 7 be upper class (FHIR-44066) Applied (here)
- Applied: “When” should be lower case (FHIR-44069) Applied (here)
- Applied: Misspelling of “Explain” in Status: Summary (FHIR-44065) Applied (here)
- Applied: Conformance requirement 2.10 - provide example (FHIR-43698) Applied (here)
- Applied: Relax prohibition against string-based membership testing (FHIR-43780) Applied (here)
- Applied: Value set is written 5 different ways (FHIR-44089) Changes applied in the whole section (here)
- Applied: Conflicting information about underscores (FHIR-44075) Applied (here)
- Applied: A Conformance Requirement that SHOULD be followed is confusing (FHIR-43885) Applied (here)
- Applied: Consider including the terminology operators link (FHIR-44090) (Applied here)
- Applied: Consider updating examples to align with Conformance Requirement 2.14 (FHIR-44113) Applied (here), (here), and (here)
- Applied: Attributes versus Elements (FHIR-44541) (Applied here)
- Applied: Too many spaces before colon (FHIR-44077) (Applied here)
- Applied: Missing period (FHIR-44079) (Applied here)
- Applied: Confusing Terminology (FHIR-44086) Applied (here)
- Applied: add link to cqf-notDoneValueSet (FHIR-44512) (Applied here)
- Applied: Large number of technical corrections (FHIR-44548 )Applied (here), (here), (here), (here), and (here)
- Applied: Missing periods (FHIR-44087) (Applied here)
- Applied: Mismatch between CQL Capability Statement profile and example (FHIR-43734) Applied (here)
- Applied: CQL Module: Consider using invariant to require parameters have defaultValue or cqlType (FHIR-43741) (Applied here)
- Applied: CQL CQL Operation: Clarify return (FHIR-43762) (Applied here)
- Applied: CQL Module: Clarify inputParameters extension vs Library.parameter element (FHIR-43740) (Applied here)
- Applied: Clarify use of data absent reason codes in CQL Evaluation Result (FHIR-43737) Applied (here)
- Applied: FHIR version of code structure does not include the term “using” (FHIR-44099) Applied (here)
- Applied: Consider tightening ELM Library profile requirements w/ invariants (FHIR-43742) Applied (here)
- Applied: Clarify purpose of “Representation in Narrative” section (FHIR-43783) Applied (here)
- Applied: Conflict in Mime Type version guidance and Library profiles (FHIR-43877) Applied (here), (here), (here), (here), (here), and (here)
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.
- Use a dataAbsentReason extension to indicate missing results(FHIR-43076)
- Add guidance on missing information(FHIR-43075)
- Consider requiring the use of a SignatureLevel higher than none(FHIR-42921)
- Libraries are not required for CQL(FHIR-42574)
- Explaining conformance requirement 4.12(FHIR-42573)
- Representation in a Library needs clarification(FHIR-42571)
- Code URI expectation inconsistent(FHIR-42570)
- What is “knowledge artifact CQL”?(FHIR-42569)
- Why so much discussion about VSAC in an international spec?(FHIR-42568)
- Use a value set avoiding OIDs(FHIR-42567)
- Update location of code system URIs(FHIR-42566)
- How is the association between a namespace and URI established?(FHIR-42565)
- Put versioning stuff together(FHIR-42562)
- Explain identifier rules(FHIR-42561)
- Better explain library declarations(FHIR-42560)
- Clarify language around CQL artifacts(FHIR-42559)
- No content in this ModelInfo section of Using CQL(FHIR-41869)
- Provide more context in examples(FHIR-41868)
- Fixed a typo in 2.14 (FHIR-43789)
- Made some typo fixes on using CQL page (FHIR-43418)
- Finished sentence on 2.1.2 (FHIR-43436)
- Added -version to the CQL naming convention conformance requirement 2.18 (FHIR-43582)
- Clarify FHIR Type Mapping for List and Tuple types (FHIR-43793)
- Created new ModelInfoSettings profile as per the ticket (FHIR-43901)
- Updated example in Concepts to include a code from another system (FHIR-43703)
- Added additional details to 2.18.2 to note profiles are StructureDefinitions with derivation set to constraint (FHIR-43882)
- Removed quotes from parameters in the example in 2.8 (FHIR-43479)
- Added a dependency slice to relatedArtifact in the CQLModule profile (FHIR-43747)