Quality Measure Implementation Guide
2.0.0 - STU 2
Quality Measure Implementation Guide
2.0.0 - STU 2
Quality Measure Implementation Guide, published by HL7 International / Clinical Quality Information. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-cqm/ and changes regularly. See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 4 |
{
"resourceType" : "OperationDefinition",
"id" : "cqm-package",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: OperationDefinition cqm-package</b></p><a name=\"cqm-package\"> </a><a name=\"hccqm-package\"> </a><p>URL: [base]/MeasureReport/$package</p><h3>Parameters</h3><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>id</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#string\">string</a></td><td/><td><div><p>The logical id of an existing Resource to package on the server.</p>\n</div></td></tr><tr><td>IN</td><td>url</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>A canonical reference to a Resource to package on the server.</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#string\">string</a></td><td/><td><div><p>The version of the Resource</p>\n</div></td></tr><tr><td>IN</td><td>identifier</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#string\">string</a><br/>(<a href=\"https://hl7.org/fhir/R4/search.html#token\">token</a>)</td><td/><td><div><p>A business identifier of the Resource.</p>\n</div></td></tr><tr><td>IN</td><td>capability</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#string\">string</a></td><td/><td><div><p>A desired capability of the resulting package. <code>computable</code> to include computable elements in packaged content; <code>executable</code> to include executable elements in packaged content; <code>publishable</code> to include publishable elements in packaged content.</p>\n</div></td></tr><tr><td>IN</td><td>artifactVersion</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>Specifies a version to use for a canonical or artifact resource if the artifact referencing the resource does not already specify a version. The format is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56</p>\n<p>Note that this is a generalization of the <code>system-version</code> parameter to the $expand operation to apply to any canonical resource, including code systems.</p>\n</div></td></tr><tr><td>IN</td><td>checkArtifactVersion</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>Edge Case: Specifies a version to use for a canonical or artifact resource. If the artifact referencing the resource specifies a different version, an error is returned instead of the package. The format is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56</p>\n<p>Note that this is a generalization of the <code>check-system-version</code> parameter to the $expand operation to apply to any canonical resource, including code systems.</p>\n</div></td></tr><tr><td>IN</td><td>forceArtifactVersion</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>Edge Case: Specifies a version to use for a canonical or artifact resource. This parameter overrides any specified version in the artifact (and any artifacts it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56.</p>\n<p>Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers <strong>SHOULD</strong> only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the version of a canonical is overridden, the version used <strong>SHALL</strong> explicitly be represented in the expansion parameters.</p>\n<p>Note that this is a generalization of the <code>force-system-version</code> parameter to the $expand operation to apply to any canonical resource, including code systems.</p>\n</div></td></tr><tr><td>IN</td><td>manifest</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#canonical\">canonical</a></td><td/><td><div><p>Specifies an asset-collection library that defines version bindings for code systems and other canonical resources referenced by the value set(s) being expanded and other canonical resources referenced by the artifact. When specified, code systems and other canonical resources identified as <code>depends-on</code> related artifacts in the manifest library have the same meaning as specifying that code system or other canonical version in the <code>system-version</code> parameter of an expand or the <code>canonicalVersion</code> parameter.</p>\n</div></td></tr><tr><td>IN</td><td>offset</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#integer\">integer</a></td><td/><td><div><p>Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)</p>\n</div></td></tr><tr><td>IN</td><td>count</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#integer\">integer</a></td><td/><td><div><p>Paging support - how many resources <strong>SHOULD</strong> be provided in a partial page view. If count = 0, the client is asking how large the package is.</p>\n</div></td></tr><tr><td>IN</td><td>include</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#string\">string</a></td><td/><td><div><p>Specifies what contents <strong>SHOULD</strong> be included in the resulting package. The codes indicate which types of resources <strong>SHOULD</strong> be included, but note that the set of possible resources is determined as all known (i.e. present on the server) dependencies and related artifacts. Possible values are:</p>\n<ul>\n<li><code>all</code> (default) - all resource types</li>\n<li><code>artifact</code> - the specified artifact</li>\n<li><code>canonical</code> - canonical resources (i.e. resources with a defined url element or that can be canonical resources using the artifact-url extension)</li>\n<li><code>terminology</code> - terminology resources (i.e. CodeSystem, ValueSet, NamingSystem, ConceptMap)</li>\n<li><code>conformance</code> - conformance resources (i.e. StructureDefinition, StructureMap, SearchParameter, CompartmentDefinition)</li>\n<li><code>profiles</code> - profile definitions (i.e. StructureDefinition resources that define profiles)</li>\n<li><code>extensions</code> - extension definitions (i.e. StructureDefinition resources that define extensions)</li>\n<li><code>knowledge</code> - knowledge artifacts (i.e. ActivityDefinition, Library, PlanDefinition, Measure, Questionnaire)</li>\n<li><code>tests</code> - test cases and data (i.e. test cases as defined by the testing specification in this implementation guide)</li>\n<li><code>examples</code> - example resources (i.e. resources identified as examples in the implementation guide)</li>\n</ul>\n</div></td></tr><tr><td>IN</td><td>packageOnly</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#boolean\">boolean</a></td><td/><td><div><p>True to indicate that the resulting package <strong>SHOULD</strong> only include resources that are defined in the implementation guide or specification that defines the artifact being packaged. False (default) to indicate that the resulting package <strong>SHOULD</strong> include resources regardless of what implementation guide or specification they are defined in.</p>\n</div></td></tr><tr><td>IN</td><td>contentEndpoint</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/endpoint.html\">Endpoint</a></td><td/><td><div><p>An endpoint to use to access content (i.e. libraries, activities, measures, questionnaires, and plans) referenced by the artifact. If no content endpoint is supplied the evaluation will attempt to retrieve content from the server on which the operation is being performed.</p>\n</div></td></tr><tr><td>IN</td><td>terminologyEndpoint</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/endpoint.html\">Endpoint</a></td><td/><td><div><p>An endpoint to use to access terminology (i.e. valuesets, codesystems, naming systems, concept maps, and membership testing) referenced by the Resource. If no terminology endpoint is supplied, the evaluation will attempt to use the server on which the operation is being performed as the terminology server.</p>\n</div></td></tr><tr><td>IN</td><td>terminologyCapabilities</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/terminologycapabilities.html\">TerminologyCapabilities</a></td><td/><td><div><p>A TerminologyCapabilities resource describing the expected terminology capabilities of the target environment. For example, an environment may be capable of processing specific types of value set definitions, but not others (e.g. LOINC panel definitions, but not SNOMED hierarchies).</p>\n</div></td></tr><tr><td>IN</td><td>requestMethod</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#code\">code</a></td><td/><td><div><p>Indicates the request method (POST or PUT) that <strong>SHOULD</strong> be used for entries in the resulting package bundle. If not specified, the request method is at the discretion of the server.</p>\n</div></td></tr><tr><td>IN</td><td>bundleType</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#code\">code</a></td><td/><td><div><p>Determines the type of the output Bundle, <strong>MAY</strong> be either collection, or transaction. If not specified, the output bundle will be a transaction bundle, unless paging is used, or determined to be necessary by the server.</p>\n<p>If paging is used, the bundle type <strong>SHALL</strong> be searchset, and the resulting bundles <strong>SHALL</strong> conform to the paging guidance here: https://hl7.org/fhir/R4/http.html#paging</p>\n<p>It is an error to request a transaction or collection bundle and use paging. Servers are free to return a TOO-COSTLY error if a transaction or collection bundle is requested for a package that is deemed to be too large by the server.</p>\n</div></td></tr><tr><td>IN</td><td>artifactEndpointConfiguration</td><td/><td>0..*</td><td/><td/><td><div><p>Configuration information to resolve canonical artifacts</p>\n<ul>\n<li><code>artifactRoute</code>: An optional route used to determine whether this endpoint is expected to be able to resolve artifacts that match the route (i.e. start with the route, up to and including the entire url)</li>\n<li><code>endpointUri</code>: The URI of the endpoint, exclusive with the <code>endpoint</code> parameter</li>\n<li><code>endpoint</code>: An Endpoint resource describing the endpoint, exclusive with the <code>endpointUri</code> parameter</li>\n</ul>\n<p><strong>Processing semantics</strong>:</p>\n<p>Create a canonical-like reference (e.g. <code>{canonical.url}|{canonical.version}</code> or similar extensions for non-canonical artifacts).</p>\n<ul>\n<li>Given a single <code>artifactEndpointConfiguration</code>\n<ul>\n<li>When <code>artifactRoute</code> is present\n<ul>\n<li>And canonical or artifact reference <em>starts with</em> <code>artifactRoute</code></li>\n<li>Then attempt to resolve with <code>endpointUri</code> or <code>endpoint</code></li>\n</ul>\n</li>\n<li>When <code>artifactRoute</code> is not present\n<ul>\n<li>Then attempt to resolve with <code>endpointUri</code> or <code>endpoint</code></li>\n</ul>\n</li>\n</ul>\n</li>\n<li>Given multiple <code>artifactEndpointConfiguration</code>s\n<ul>\n<li>Then rank order each configuration (see below)</li>\n<li>And attempt to resolve with <code>endpointUri</code> or <code>endpoint</code> in order until resolved</li>\n</ul>\n</li>\n</ul>\n<p>Rank each <code>artifactEndpointConfiguration</code> such that:</p>\n<ul>\n<li>if <code>artifactRoute</code> is present <em>and</em> canonical or artifact reference <em>starts with</em> <code>artifactRoute</code>: rank based on number of matching characters</li>\n<li>if <code>artifactRoute</code> is <em>not</em> present: include but rank lower</li>\n</ul>\n<p>NOTE: For evenly ranked <code>artifactEndpointConfiguration</code>s, order as defined in the\nOperationDefinition.</p>\n</div></td></tr><tr><td>IN</td><td>artifactEndpointConfiguration.artifactRoute</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td/></tr><tr><td>IN</td><td>artifactEndpointConfiguration.endpointUri</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td/></tr><tr><td>IN</td><td>artifactEndpointConfiguration.endpoint</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4/endpoint.html\">Endpoint</a></td><td/><td/></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4/bundle.html\">Bundle</a></td><td/><td><div><p>The result of the packaging. Servers generating packages <strong>SHALL</strong> include all the dependency resources referenced by the artifact that are known to the server and specified by the include parameters.</p>\n<p>For example, a measure repository <strong>SHALL</strong> include all the required library resources, but would not necessarily have the ValueSet resources referenced by the measure.</p>\n</div></td></tr></table><div><p>This creates a measure report package that conforms to the test case profile.</p>\n</div></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "cqi"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 4,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/cqm/ImplementationGuide/hl7.fhir.uv.cqm"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/cqm/ImplementationGuide/hl7.fhir.uv.cqm"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/cqm/OperationDefinition/cqm-package",
"version" : "2.0.0",
"name" : "CQMPackage",
"title" : "CQM Package",
"status" : "active",
"kind" : "operation",
"date" : "2026-09-02T15:25:48+00:00",
"publisher" : "HL7 International / Clinical Quality Information",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/cqi"
}
]
}
],
"description" : "Packages a specified canonical resource with dependencies.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001"
}
]
}
],
"code" : "package",
"comment" : "This creates a measure report package that conforms to the test case profile.",
"resource" : [
"MeasureReport"
],
"system" : false,
"type" : true,
"instance" : false,
"parameter" : [
{
"name" : "id",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "The logical id of an existing Resource to package on the server.",
"type" : "string"
},
{
"name" : "url",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "A canonical reference to a Resource to package on the server.",
"type" : "uri"
},
{
"name" : "version",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "The version of the Resource",
"type" : "string"
},
{
"name" : "identifier",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "A business identifier of the Resource.",
"type" : "string",
"searchType" : "token"
},
{
"name" : "capability",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "A desired capability of the resulting package. `computable` to include computable elements in packaged content; `executable` to include executable elements in packaged content; `publishable` to include publishable elements in packaged content.",
"type" : "string"
},
{
"name" : "artifactVersion",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies a version to use for a canonical or artifact resource if the artifact referencing the resource does not already specify a version. The format is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56 \n\nNote that this is a generalization of the `system-version` parameter to the $expand operation to apply to any canonical resource, including code systems.",
"type" : "uri"
},
{
"name" : "checkArtifactVersion",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Edge Case: Specifies a version to use for a canonical or artifact resource. If the artifact referencing the resource specifies a different version, an error is returned instead of the package. The format is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56 \n\nNote that this is a generalization of the `check-system-version` parameter to the $expand operation to apply to any canonical resource, including code systems.",
"type" : "uri"
},
{
"name" : "forceArtifactVersion",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Edge Case: Specifies a version to use for a canonical or artifact resource. This parameter overrides any specified version in the artifact (and any artifacts it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56. \n\nNote that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers **SHOULD** only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the version of a canonical is overridden, the version used **SHALL** explicitly be represented in the expansion parameters. \n\nNote that this is a generalization of the `force-system-version` parameter to the $expand operation to apply to any canonical resource, including code systems.",
"type" : "uri"
},
{
"name" : "manifest",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Specifies an asset-collection library that defines version bindings for code systems and other canonical resources referenced by the value set(s) being expanded and other canonical resources referenced by the artifact. When specified, code systems and other canonical resources identified as `depends-on` related artifacts in the manifest library have the same meaning as specifying that code system or other canonical version in the `system-version` parameter of an expand or the `canonicalVersion` parameter.",
"type" : "canonical"
},
{
"name" : "offset",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)",
"type" : "integer"
},
{
"name" : "count",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Paging support - how many resources **SHOULD** be provided in a partial page view. If count = 0, the client is asking how large the package is.",
"type" : "integer"
},
{
"name" : "include",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies what contents **SHOULD** be included in the resulting package. The codes indicate which types of resources **SHOULD** be included, but note that the set of possible resources is determined as all known (i.e. present on the server) dependencies and related artifacts. Possible values are:\n* `all` (default) - all resource types\n* `artifact` - the specified artifact\n* `canonical` - canonical resources (i.e. resources with a defined url element or that can be canonical resources using the artifact-url extension)\n* `terminology` - terminology resources (i.e. CodeSystem, ValueSet, NamingSystem, ConceptMap)\n* `conformance` - conformance resources (i.e. StructureDefinition, StructureMap, SearchParameter, CompartmentDefinition)\n* `profiles` - profile definitions (i.e. StructureDefinition resources that define profiles)\n* `extensions` - extension definitions (i.e. StructureDefinition resources that define extensions)\n* `knowledge` - knowledge artifacts (i.e. ActivityDefinition, Library, PlanDefinition, Measure, Questionnaire)\n* `tests` - test cases and data (i.e. test cases as defined by the testing specification in this implementation guide)\n* `examples` - example resources (i.e. resources identified as examples in the implementation guide)",
"type" : "string"
},
{
"name" : "packageOnly",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "True to indicate that the resulting package **SHOULD** only include resources that are defined in the implementation guide or specification that defines the artifact being packaged. False (default) to indicate that the resulting package **SHOULD** include resources regardless of what implementation guide or specification they are defined in.",
"type" : "boolean"
},
{
"name" : "contentEndpoint",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "An endpoint to use to access content (i.e. libraries, activities, measures, questionnaires, and plans) referenced by the artifact. If no content endpoint is supplied the evaluation will attempt to retrieve content from the server on which the operation is being performed.",
"type" : "Endpoint"
},
{
"name" : "terminologyEndpoint",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "An endpoint to use to access terminology (i.e. valuesets, codesystems, naming systems, concept maps, and membership testing) referenced by the Resource. If no terminology endpoint is supplied, the evaluation will attempt to use the server on which the operation is being performed as the terminology server.",
"type" : "Endpoint"
},
{
"name" : "terminologyCapabilities",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "A TerminologyCapabilities resource describing the expected terminology capabilities of the target environment. For example, an environment may be capable of processing specific types of value set definitions, but not others (e.g. LOINC panel definitions, but not SNOMED hierarchies).",
"type" : "TerminologyCapabilities"
},
{
"name" : "requestMethod",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Indicates the request method (POST or PUT) that **SHOULD** be used for entries in the resulting package bundle. If not specified, the request method is at the discretion of the server.",
"type" : "code"
},
{
"name" : "bundleType",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Determines the type of the output Bundle, **MAY** be either collection, or transaction. If not specified, the output bundle will be a transaction bundle, unless paging is used, or determined to be necessary by the server.\n\nIf paging is used, the bundle type **SHALL** be searchset, and the resulting bundles **SHALL** conform to the paging guidance here: https://hl7.org/fhir/R4/http.html#paging\n\nIt is an error to request a transaction or collection bundle and use paging. Servers are free to return a TOO-COSTLY error if a transaction or collection bundle is requested for a package that is deemed to be too large by the server.",
"type" : "code"
},
{
"name" : "artifactEndpointConfiguration",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Configuration information to resolve canonical artifacts\n* `artifactRoute`: An optional route used to determine whether this endpoint is expected to be able to resolve artifacts that match the route (i.e. start with the route, up to and including the entire url)\n* `endpointUri`: The URI of the endpoint, exclusive with the `endpoint` parameter\n* `endpoint`: An Endpoint resource describing the endpoint, exclusive with the `endpointUri` parameter\n\n**Processing semantics**:\n\nCreate a canonical-like reference (e.g. `{canonical.url}|{canonical.version}` or similar extensions for non-canonical artifacts).\n\n* Given a single `artifactEndpointConfiguration`\n * When `artifactRoute` is present\n * And canonical or artifact reference *starts with* `artifactRoute`\n * Then attempt to resolve with `endpointUri` or `endpoint`\n * When `artifactRoute` is not present\n * Then attempt to resolve with `endpointUri` or `endpoint`\n* Given multiple `artifactEndpointConfiguration`s\n * Then rank order each configuration (see below)\n * And attempt to resolve with `endpointUri` or `endpoint` in order until resolved\n\nRank each `artifactEndpointConfiguration` such that:\n* if `artifactRoute` is present *and* canonical or artifact reference *starts with* `artifactRoute`: rank based on number of matching characters \n* if `artifactRoute` is *not* present: include but rank lower\n\nNOTE: For evenly ranked `artifactEndpointConfiguration`s, order as defined in the\nOperationDefinition.",
"part" : [
{
"name" : "artifactRoute",
"use" : "in",
"min" : 0,
"max" : "1",
"type" : "uri"
},
{
"name" : "endpointUri",
"use" : "in",
"min" : 0,
"max" : "1",
"type" : "uri"
},
{
"name" : "endpoint",
"use" : "in",
"min" : 0,
"max" : "1",
"type" : "Endpoint"
}
]
},
{
"name" : "return",
"use" : "out",
"min" : 1,
"max" : "1",
"documentation" : "The result of the packaging. Servers generating packages **SHALL** include all the dependency resources referenced by the artifact that are known to the server and specified by the include parameters. \n\nFor example, a measure repository **SHALL** include all the required library resources, but would not necessarily have the ValueSet resources referenced by the measure.",
"type" : "Bundle"
}
]
}
IG © 2019+ HL7 International / Clinical Quality Information.
Package hl7.fhir.uv.cqm#2.0.0 based on FHIR 4.0.1.
Generated
2026-09-02
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change