Content Management Infrastructure Implementation Guide, published by Clinical Decision Support WG. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/HL7/Content-Management-Infrastructure-IG/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
CQF Measures Shareable Measure Repository Capability Statement |
Capability statement for a repository service supporting minimum required capabilities to share FHIR-based measure specifications. See the Publishable and Authoring Measure Repository capability statements for more comprehensive support for publishing and authoring workflows. |
CQF Measures Publishable Measure Repository Capability Statement |
Capability statement for a repository service supporting additional publishing capabilities for FHIR-based measure specifications above the basic ShareableMeasureRepository. |
CQF Measures Authoring Measure Repository Capability Statement |
Capability statement for a repository service supporting additional authoring and content workflow capabilities for FHIR-based measure specifications above the basic ShareableMeasureRepository. |
Measure Terminology Service Capability Statement |
Capability statement for a terminology service supporting measure authoring and evaulation use cases. A server can support more functionality than defined here, but this defines the minimum expectations. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide
CQF Measures Extension of Value Set Expansion |
The definition of a value set is used to create a simple collection of codes suitable for use for data entry or validation. If the operation is not called at the instance level, one of the in parameters url, context or valueSet must be provided. An expanded value set will be returned, or an OperationOutcome with an error message. |
Library Data Requirements |
Determines the effective data requirements for the library, including known components and dependencies, and optionally informed by a version manifest. |
Library Packaging |
Packages the contents referenced by an asset-collection library such as a quality program release or version manifest. |
These define constraints on FHIR resources for systems conforming to this implementation guide
CMI Publishable CodeSystem |
Defines the expectations for publishable code systems used with quality measure specifications |
CMI Publishable Measure |
The CMI Publishable Measure profile defines the minimum expectations to enable appropriate content management, discovery, and utilization of published electronic Clinical Quality Measures (eCQMs) |
CMI Software System Device |
The Software System device profile is used to capture software details about the various systems used in authoring, testing, packaging, or evaluation of a knowledge artifact |
CMI Executable Measure |
The CMI Executable Measure Profile describes minimum expectations for an executable electronic Clinical Quality Measure (eCQM), including a reference to an executable library, and restricted to the use of identifier-based expressions only for all criteria. |
CMI Executable ValueSet |
Defines an executable value set as one that SHALL have an expansion included, as well as a usage warning indicating the expansion is a point-in-time snapshot and must be maintained over time for production usage. The value set expansion specifies the timestamp when the expansion was produced, SHOULD contain the parameters used for the expansion, and SHALL contain the codes that are obtained by evaluating the value set definition. If this is ONLY an executable value set, a computable definition of the value set must be obtained to compute the updated expansion. |
CMI Model Info Library |
The CMI Model Information Library profile defines the must support elements for a computable Model Definition library used to support declaration and distribution of CQL ModelInfo such as the FHIR Model Info Library |
CMI Computable ValueSet |
Defines a computable value set as one that SHALL have an expression-based definition (i.e. a value set defined intensionally using expressions of the code systems involved) and MAY have an expansion included. The expression-based definition SHALL be represented in only one of three ways; using the compose element, using the expression extension, or using the rules-text extension to provide a step-by-step process for expanding the value set definition |
CMI Computable Measure |
The CMI Computable Measure Profile describes minimum expectations for a computable electronic Clinical Quality Measure (eCQM), including the use of a computable library, and the use of expressions or identifiers for all criteria. |
CMI Measure |
The CMI Measure Profile describes minimum expectations for defining an electronic Clinical Quality Measure (eCQM) |
CMI Version Manifest |
Defines and supports the definition of a version manifest used to declare specific versions of dependencies used in knowledge artifacts |
CMI Library |
The CMI Library profile defines the minimum expectations for a library used to distribute eCQM logic |
CMI Publishable ValueSet |
Defines the expectations for publishable value sets used in quality measurement specifications |
CMI Publishable Library |
The CMI Publishable Library profile defines the must support elements in a library used to support eCQM logic |
CMI Executable Library |
The CMI Execuable Library profile defines the must support elements for an executable library used to support eCQM logic |
CMI Computable Library |
The CMI Computable Library profile defines the must support elements for a computable library used to support eCQM logic |
CMI Module Definition Library |
The CMI Module Definition Library profile defines the must support elements for a library that communicates the effective data requirements and dependencies of an artifact (or set of artifacts). This is most commonly used as the result of a $data-requirements operation, but could also be persisted statically as a way to persist the calculation of effective data requirements for a specific artifact and input parameters |
CMI Capability Statement |
The CMI Capability Statement Profile enables capability statements to express supported CQL versions. |
These define constraints on FHIR data types for systems conforming to this implementation guide
CMI FHIR Query Pattern |
A FHIR Query URL pattern that corresponds to the data specified by the data requirement. If multiple FHIR Query URLs are present, they each contribute to the data specified by the data requirement (i.e. the union of the results of the FHIR Queries represents the complete data for the data requirement). This is not a resolveable URL, in that it will contain 1) No base canonical (i.e. it’s a relative query), and 2) Parameters using tokens that are delimited using double-braces and the context parameters are dependent solely on the subjectType, according to the following: Patient: context.patientId, Practitioner: context.practitionerId, Organization: context.organizationId, Location: context.locationId, Device: context.deviceId. |
CMI Publication Date |
Specifies the publication date of the referenced artifacts. |
CMI Is Selective |
Allows a given data requirement to be identified as “selective”, meaning that it can be used as an additive criteria to filter a population. A selective data requirement is guaranteed to define a subset (not necessarily proper) of the initial population of a measure. If multiple data requirements are marked selective, they all apply (i.e. AND semantics). |
CMI Supported CQL Version |
The version of CQL supported. |
CMI Direct Reference Code |
Defines a code directly referenced by artifact logic, as opposed to a value set. Direct reference codes may be the target of data requirements. |
CMI Definition Term |
Specifies a term and its associated definition. |
CMI Usage Warning |
An extra warning about the correct use of the value set. |
CMI Expansion Parameters |
Specifies the expansion parameters that should be used to expand the ValueSet, or any ValueSets in the Library (or referenced by components of the Library). |
CMI Is Primary Citation |
Specifies whether the related artifact is defining a primary citation for the measure (i.e. one that should appear in the narrative for the measure specification. |
CMI Default Value |
Provides a default value for a parameter definition. |
CMI CQL Options |
Specifies a parameters (contained) resource that identifies the options for the CQL-to-ELM translator associated with the CQL content. |
CMI Logic Definition |
Defines a logic definition used by the artifact. |
CMI Value Filter |
Allows additional value-based filters to be specified as part of a data requirement. |
CMI Publication Status |
Specifies the publication status of the referenced artifacts. |
CMI Input Parameters |
Specifies the input parameters to the operation (such as a test case or data requirements operation). |
CMI Software System |
Specifies the software systems used in the packaging and testing of measure and library resources. Specifically to know which version of what software was used. |
CMI Effective Data Requirements |
A module definition library that contains the effective data requirements for an artifact (i.e. the calculated data requirements for the expressions directly referenced by the artifact structure). |
These define sets of codes used by systems conforming to this implementation guide
CQL Version |
The version of CQL cupported |
Value Filter Comparator |
The type of comparator operator to use |
These define new code systems used by systems conforming to this implementation guide
CQL Version Codes |
The version of CQL supported |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like
Device - Software System Example |
Example of a Software System Device used to illustrate a tooling, testing, or authoring system |
SNOMED CT International Edition |
This is an example code system, based on the SNOMED CT Code System to illustrate a publishable code system resource. SNOMED CT is a core clinical healthcare terminology that contains concepts with unique meanings and formal logic based definitions organized into hierarchies. |
Measure Calculation Service Capability Statement Example |
Basic conformance statement for a Measure Calculation Service. A server can support more fucntionality than defined here, but this is the minimum amount |