Quality Measure Implementation Guide (STU5), published by HL7 International / Clinical Quality Information. This guide is not an authorized publication; it is the continuous build for version 5.0.0-ballot2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cqf-measures/ and changes regularly. See the Directory of published versions
To facilitate publishing and distribution of quality measures, this Implementation Guide provides guidance on how to package quality measures, either independently, or as part of a collection of related measures.
In general, artifacts such as libraries, measures, and test cases are packaged as a Bundle
of type transaction
. They may span multiple bundles in a given delivery, thus the bundle should be processed as a unit.
An artifact bundle contains the artifact as the first entry in the bundle, and optionally the dependencies and associated artifacts as subsequent entries as follows:
*Note that if an artifact package is large enough to require segmentation in multiple bundles, use of transaction
bundles may not be feasible.
When paging is used for the result of the package operation, the total element in the resulting bundle(s) is used to communicate the total number of entries in the package, not the number of entries in the bundle, similar to the way bundles are used to page search sets in the FHIR API. In addition, the initial artifact entry is only expected to be present in the first bundle (i.e. the partitioning of entries across the bundles does not change what entries are communicated overall).
To support usage of a logic library, the library package contains the following general components:
The following are conformance requirements when packaging a Library:
Conformance Requirement 6.1 (Library Packaging):
To support usage of a quality measure, the quality measure package contains the following general components:
The following are conformance requirements when packaging a Measure:
Conformance Requirement 6.2 (Measure Packaging):
Basic testing of measure logic should involve at least one positive and negative test of each of the population criteria. A test case is represented as a set of test resources, together with a MeasureReport that conforms to the CQFMTestCase profile to define the expected results. The test case bundle can then be used to package and distribute the test case.
Conformance Requirement 6.3 (Test Case Packaging):
Conformance Requirement 6.4 (Intellectual Property Considerations):
Conformance Requirement 6.5 (Quality Program):
This implementation guide includes a profile for describing a quality program as a collection of quality measures. This profile is a Library of type asset-collection
that uses the relatedArtifact
element to indicate which measures are part of the quality program. In addition, measures and libraries can use the useContext
element to specify a quality program.
useContext
element with the program
context type to specify a quality program