Canonical Resource Management Infrastructure Implementation Guide
1.0.0-snapshot - Snapshot
Canonical Resource Management Infrastructure Implementation Guide
1.0.0-snapshot - Snapshot
This page is part of the Canonical Resource Management Infrastructure 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
| Active as of 2023-03-12 |
{
"resourceType" : "OperationDefinition",
"id" : "crmi-package",
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>URL: [base]/ActivityDefinition/$package</p><p>URL: [base]/ActivityDefinition/[id]/$package</p><p>URL: [base]/CapabilityStatement/$package</p><p>URL: [base]/CapabilityStatement/[id]/$package</p><p>URL: [base]/ChargeItemDefinition/$package</p><p>URL: [base]/ChargeItemDefinition/[id]/$package</p><p>URL: [base]/CodeSystem/$package</p><p>URL: [base]/CodeSystem/[id]/$package</p><p>URL: [base]/CompartmentDefinition/$package</p><p>URL: [base]/CompartmentDefinition/[id]/$package</p><p>URL: [base]/ConceptMap/$package</p><p>URL: [base]/ConceptMap/[id]/$package</p><p>URL: [base]/EffectEvidenceSynthesis/$package</p><p>URL: [base]/EffectEvidenceSynthesis/[id]/$package</p><p>URL: [base]/EventDefinition/$package</p><p>URL: [base]/EventDefinition/[id]/$package</p><p>URL: [base]/Evidence/$package</p><p>URL: [base]/Evidence/[id]/$package</p><p>URL: [base]/EvidenceVariable/$package</p><p>URL: [base]/EvidenceVariable/[id]/$package</p><p>URL: [base]/ExampleScenario/$package</p><p>URL: [base]/ExampleScenario/[id]/$package</p><p>URL: [base]/GraphDefinition/$package</p><p>URL: [base]/GraphDefinition/[id]/$package</p><p>URL: [base]/ImplementationGuide/$package</p><p>URL: [base]/ImplementationGuide/[id]/$package</p><p>URL: [base]/Library/$package</p><p>URL: [base]/Library/[id]/$package</p><p>URL: [base]/Measure/$package</p><p>URL: [base]/Measure/[id]/$package</p><p>URL: [base]/Medication/$package</p><p>URL: [base]/Medication/[id]/$package</p><p>URL: [base]/MedicationKnowledge/$package</p><p>URL: [base]/MedicationKnowledge/[id]/$package</p><p>URL: [base]/MessageDefinition/$package</p><p>URL: [base]/MessageDefinition/[id]/$package</p><p>URL: [base]/NamingSystem/$package</p><p>URL: [base]/NamingSystem/[id]/$package</p><p>URL: [base]/OperationDefinition/$package</p><p>URL: [base]/OperationDefinition/[id]/$package</p><p>URL: [base]/PlanDefinition/$package</p><p>URL: [base]/PlanDefinition/[id]/$package</p><p>URL: [base]/Questionnaire/$package</p><p>URL: [base]/Questionnaire/[id]/$package</p><p>URL: [base]/ResearchDefinition/$package</p><p>URL: [base]/ResearchDefinition/[id]/$package</p><p>URL: [base]/ResearchElementDefinition/$package</p><p>URL: [base]/ResearchElementDefinition/[id]/$package</p><p>URL: [base]/RiskEvidenceSynthesis/$package</p><p>URL: [base]/RiskEvidenceSynthesis/[id]/$package</p><p>URL: [base]/SearchParameter/$package</p><p>URL: [base]/SearchParameter/[id]/$package</p><p>URL: [base]/StructureDefinition/$package</p><p>URL: [base]/StructureDefinition/[id]/$package</p><p>URL: [base]/StructureMap/$package</p><p>URL: [base]/StructureMap/[id]/$package</p><p>URL: [base]/Substance/$package</p><p>URL: [base]/Substance/[id]/$package</p><p>URL: [base]/TerminologyCapabilities/$package</p><p>URL: [base]/TerminologyCapabilities/[id]/$package</p><p>URL: [base]/TestScript/$package</p><p>URL: [base]/TestScript/[id]/$package</p><p>URL: [base]/ValueSet/$package</p><p>URL: [base]/ValueSet/[id]/$package</p><p>Parameters</p><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 or artifact 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=\"http://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\ncomputable elements in packaged content; <code>executable</code> to include executable\nelements in packaged content; <code>publishable</code> to include publishable elements in\npackaged content.</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\nof the target environment. For example, an environment may be capable of processing\nspecific types of value set definitions, but not others (e.g. LOINC panel definitions,\nbut not SNOMED hierarchies).</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\nthe resource does not already specify a version. The format is the same as a canonical URL:\n[url]|[version] - e.g. http://loinc.org|2.56 Note that this is a generalization of the <code>system-version</code>\nparameter 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\nthe resource specifies a different version, an error is returned instead of the package. The\nformat is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56 Note that\nthis is a generalization of the <code>check-system-version</code> parameter to the $expand operation to\napply 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\nspecified version in the artifact (and any artifacts it depends on). The\nformat is the same as a canonical URL: [system]|[version] - e.g.\nhttp://loinc.org|2.56. Note that this has obvious safety issues, in that it may\nresult in a value set expansion giving a different list of codes that is both\nwrong and unsafe, and implementers should only use this capability reluctantly.\nIt primarily exists to deal with situations where specifications have fallen\ninto decay as time passes. If the version of a canonical is overridden, the version used SHALL\nexplicitly be represented in the expansion parameters. Note that this is a generalization of the\n<code>force-system-version</code> parameter to the $expand operation to apply to any canonical resource,\nincluding 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> (<a href=\"StructureDefinition-crmi-manifestlibrary.html\" title=\"http://hl7.org/fhir/uv/crmi/StructureDefinition/crmi-manifestlibrary\">CRMI Manifest Library</a>)</td><td/><td><div><p>Specifies a reference to an asset-collection library that defines version\nbindings for code systems and other canonical resources referenced by the value\nset(s) being expanded and other canonical resources referenced by the artifact.\nWhen specified, code systems and other canonical resources identified as\n<code>depends-on</code> related artifacts in the manifest library have the same meaning as\nspecifying that code system or other canonical version in the <code>system-version</code>\nparameter 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\nnumber of records (not number of pages). If offset > 0 the resulting bundle will be of type <code>collection</code>.</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 should be provided in a partial page view.\nIf count = 0, the client is asking how large the package is. If count > 0 but less than the total number of resources, the result will be a bundle of type <code>collection</code>.</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#code\">code</a></td><td/><td><div><p>Specifies what contents should only be included in the resulting package. The\ncodes indicate which types of resources should be included, but note that the\nset of possible resources is determined as all known (i.e. present on the\nserver) dependencies and related artifacts.</p>\n<p>Possible values are either a code to mean a category of resource types:</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<p>Or a valid FHIR resource Type (e.g. <code>PlanDefinition</code>, <code>MedicationKnowledge</code>, etc)</p>\n</div></td></tr><tr><td>IN</td><td>includeUri</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>Specifies what contents should be included in the resulting package by canonical\nURL, can take the form <code>{url}</code> or <code>{url}|{version}</code>.</p>\n</div></td></tr><tr><td>IN</td><td>exclude</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#code\">code</a></td><td/><td><div><p>Specifies what contents should be excluded in the resulting package. The codes\nindicate which types of resources should be excluded, but note that the set of\npossible resources is determined as all known (i.e. present on the server)\ndependencies and related artifacts.</p>\n<p>Possible values are either a code to mean a category of resource types:</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<p>Or a valid FHIR resource Type (e.g. <code>PlanDefinition</code>, <code>MedicationKnowledge</code>, etc)</p>\n</div></td></tr><tr><td>IN</td><td>excludeUri</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4/datatypes.html#uri\">uri</a></td><td/><td><div><p>Specifies what contents should be excluded in the resulting package by canonical\nURL, can take the form <code>{url}</code> or <code>{url}|{version}</code>.</p>\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 should only include resources that are defined in the implementation guide\nor specification that defines the artifact being packaged. False (default) to indicate that the resulting package should\ninclude resources regardless of what implementation guide or specification they are defined in.</p>\n</div></td></tr><tr><td>IN</td><td>artifactEndpointConfiguration</td><td/><td>0..*</td><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.\n<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 <code>artifactRoute</code> <em>starts with</em> canonical or artifact reference</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> <code>artifactRoute</code> <em>starts with</em> canonical or artifact reference: 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>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\nmembership testing) referenced by the Resource. If no terminology endpoint is\nsupplied, the evaluation will attempt to use the server on which the operation\nis being performed as the terminology server.</p>\n</div></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. If the resulting bundle is paged using <code>count</code> or <code>offset</code>, it will be of type <code>collection</code>. In the special case where <code>count = 0</code> it will be of type <code>searchset</code>.</p>\n<p>Servers generating packages SHALL include all the\ndependency resources referenced by the artifact that are known to the server and\nspecified by the include parameters.</p>\n<p>For example, a measure repository SHALL include\nall the required library resources, but would not necessarily have the\nValueSet resources referenced by the measure.</p>\n</div></td></tr></table><div><p>The package operation supports producing a complete package of a particular artifact\nsupporting the capabilities expected to be available in a particular target environment.\nFor example, a Questionnaire may be packaged together with the value sets referenced by\nelements of the questionnaire, and those value sets may be definitions (Computable) or\nexpansions (Expanded), depending on the parameters to the operation.</p>\n</div></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "cds"
}
],
"url" : "http://hl7.org/fhir/uv/crmi/OperationDefinition/crmi-package",
"version" : "1.0.0-snapshot",
"name" : "CRMIPackage",
"title" : "CRMI Package",
"status" : "active",
"kind" : "operation",
"experimental" : false,
"date" : "2023-03-12",
"publisher" : "HL7 International / Clinical Decision Support",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/dss"
}
]
}
],
"description" : "Packages a specified canonical resource for use in a target environment, optionally \nincluding related content such as dependencies, components, and testing cases and data.\n\nSee [$package and $data-requirements](distribution.html#package-and-data-requirements)",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"code" : "package",
"comment" : "The package operation supports producing a complete package of a particular artifact \nsupporting the capabilities expected to be available in a particular target environment. \nFor example, a Questionnaire may be packaged together with the value sets referenced by \nelements of the questionnaire, and those value sets may be definitions (Computable) or \nexpansions (Expanded), depending on the parameters to the operation. ",
"resource" : [
"ActivityDefinition",
"CapabilityStatement",
"ChargeItemDefinition",
"CodeSystem",
"CompartmentDefinition",
"ConceptMap",
"EffectEvidenceSynthesis",
"EventDefinition",
"Evidence",
"EvidenceVariable",
"ExampleScenario",
"GraphDefinition",
"ImplementationGuide",
"Library",
"Measure",
"Medication",
"MedicationKnowledge",
"MessageDefinition",
"NamingSystem",
"OperationDefinition",
"PlanDefinition",
"Questionnaire",
"ResearchDefinition",
"ResearchElementDefinition",
"RiskEvidenceSynthesis",
"SearchParameter",
"StructureDefinition",
"StructureMap",
"Substance",
"TerminologyCapabilities",
"TestScript",
"ValueSet"
],
"system" : false,
"type" : true,
"instance" : true,
"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 or artifact 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\ncomputable elements in packaged content; `executable` to include executable\nelements in packaged content; `publishable` to include publishable elements in\npackaged content.",
"type" : "string"
},
{
"name" : "terminologyCapabilities",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "A TerminologyCapabilities resource describing the expected terminology capabilities \nof the target environment. For example, an environment may be capable of processing \nspecific types of value set definitions, but not others (e.g. LOINC panel definitions, \nbut not SNOMED hierarchies).",
"type" : "TerminologyCapabilities"
},
{
"name" : "artifactVersion",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies a version to use for a canonical or artifact resource if the artifact referencing \nthe resource does not already specify a version. The format is the same as a canonical URL:\n[url]|[version] - e.g. http://loinc.org|2.56 Note that this is a generalization of the `system-version`\nparameter 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 \nthe resource specifies a different version, an error is returned instead of the package. The\nformat is the same as a canonical URL: [url]|[version] - e.g. http://loinc.org|2.56 Note that\nthis is a generalization of the `check-system-version` parameter to the $expand operation to \napply 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\nspecified version in the artifact (and any artifacts it depends on). The\nformat is the same as a canonical URL: [system]|[version] - e.g.\nhttp://loinc.org|2.56. Note that this has obvious safety issues, in that it may\nresult in a value set expansion giving a different list of codes that is both\nwrong and unsafe, and implementers should only use this capability reluctantly.\nIt primarily exists to deal with situations where specifications have fallen\ninto decay as time passes. If the version of a canonical is overridden, the version used SHALL\nexplicitly be represented in the expansion parameters. Note that this is a generalization of the\n`force-system-version` parameter to the $expand operation to apply to any canonical resource,\nincluding code systems.",
"type" : "uri"
},
{
"name" : "manifest",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Specifies a reference to an asset-collection library that defines version\nbindings for code systems and other canonical resources referenced by the value\nset(s) being expanded and other canonical resources referenced by the artifact.\nWhen specified, code systems and other canonical resources identified as\n`depends-on` related artifacts in the manifest library have the same meaning as\nspecifying that code system or other canonical version in the `system-version`\nparameter of an expand or the `canonicalVersion` parameter.",
"type" : "canonical",
"targetProfile" : [
🔗 "http://hl7.org/fhir/uv/crmi/StructureDefinition/crmi-manifestlibrary"
]
},
{
"name" : "offset",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Paging support - where to start if a subset is desired (default = 0). Offset is\nnumber of records (not number of pages). If offset > 0 the resulting bundle will be of type `collection`.",
"type" : "integer"
},
{
"name" : "count",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "Paging support - how many resources should be provided in a partial page view.\nIf count = 0, the client is asking how large the package is. If count > 0 but less than the total number of resources, the result will be a bundle of type `collection`.",
"type" : "integer"
},
{
"name" : "include",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies what contents should only be included in the resulting package. The\ncodes indicate which types of resources should be included, but note that the\nset of possible resources is determined as all known (i.e. present on the\nserver) dependencies and related artifacts. \n\nPossible values are either a code to mean a category of resource types:\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)\n\nOr a valid FHIR resource Type (e.g. `PlanDefinition`, `MedicationKnowledge`, etc)",
"type" : "code"
},
{
"name" : "includeUri",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies what contents should be included in the resulting package by canonical\nURL, can take the form `{url}` or `{url}|{version}`.",
"type" : "uri"
},
{
"name" : "exclude",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies what contents should be excluded in the resulting package. The codes\nindicate which types of resources should be excluded, but note that the set of\npossible resources is determined as all known (i.e. present on the server)\ndependencies and related artifacts. \n\nPossible values are either a code to mean a category of resource types:\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)\n\nOr a valid FHIR resource Type (e.g. `PlanDefinition`, `MedicationKnowledge`, etc)",
"type" : "code"
},
{
"name" : "excludeUri",
"use" : "in",
"min" : 0,
"max" : "*",
"documentation" : "Specifies what contents should be excluded in the resulting package by canonical\nURL, can take the form `{url}` or `{url}|{version}`.",
"type" : "uri"
},
{
"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 \nor specification that defines the artifact being packaged. False (default) to indicate that the resulting package should \ninclude resources regardless of what implementation guide or specification they are defined in.",
"type" : "boolean"
},
{
"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.\n`{canonical.url}|{canonical.version}` or similar extensions for non-canonical artifacts).\n\n* Given a single `artifactEndpointConfiguration`\n * When `artifactRoute` is present\n * And `artifactRoute` *starts with* canonical or artifact reference\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* `artifactRoute` *starts with* canonical or artifact reference: 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" : "terminologyEndpoint",
"use" : "in",
"min" : 0,
"max" : "1",
"documentation" : "An endpoint to use to access terminology (i.e. valuesets, codesystems, naming systems, concept maps, and\nmembership testing) referenced by the Resource. If no terminology endpoint is\nsupplied, the evaluation will attempt to use the server on which the operation\nis being performed as the terminology server.",
"type" : "Endpoint"
},
{
"name" : "return",
"use" : "out",
"min" : 1,
"max" : "1",
"documentation" : "The result of the packaging. If the resulting bundle is paged using `count` or `offset`, it will be of type `collection`. In the special case where `count = 0` it will be of type `searchset`.\n\nServers generating packages SHALL include all the\ndependency resources referenced by the artifact that are known to the server and \nspecified by the include parameters. \n\nFor example, a measure repository SHALL include\nall the required library resources, but would not necessarily have the\nValueSet resources referenced by the measure.",
"type" : "Bundle"
}
]
}
IG © 2022+ HL7 International / Clinical Decision Support. Package hl7.fhir.uv.crmi#1.0.0-snapshot based on FHIR 4.0.1. Generated 2024-04-06
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change