$package

Library Packaging

draftElectronic Case Reporting2.1.2operation13 inputs1 output

Packages the contents referenced by an asset-collection library such as a quality program release or version manifest.

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/fhir/us/ecr/OperationDefinition/operationdefinition-library-package
Code
$package
Kind
operation
Affects State
No
Publisher
HL7 International / Public Health

Invocation Context

Can be invoked at:
Type LevelInstance Level
Target Resources:

Implementation Notes

This operation is used to retrieve the contents associated with a particular library such as a quality program, including the use of the quality program as a binding parameters specification to identify code system and value set versions that should be used for expansion of value sets used by measures in the quality program.

Input Parameters (13)

NameTypeCard.Description
idstring0..1The logical id of the library to package. The server must know the library (e.g. it is defined explicitly in the server's libraries)
urluri0..1A canonical reference to a library. The server must know the library (e.g. it is defined explicitly in the server's libraries
versionstring0..1The version of the library to be used for packaging
identifierstring0..1A business identifier of the library to be packaged. The server must know the library and the identifier must resolve unambiguously to a single library on the server.
capabilitystring0..*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.
offsetinteger0..1Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)
countinteger0..1Paging support - how many resources should be provided in a partial page view. If count = 0, the client is asking how large the package is.
system-versioncanonical0..*Specifies a version to use for a system, if the library or value set does not already specify which one to use. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56
check-system-versioncanonical0..*Edge Case: Specifies a version to use for a system. If a library or value set specifies a different version, an error is returned instead of the package. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56
force-system-versioncanonical0..*Edge Case: Specifies a version to use for a system. This parameter overrides any specified version in the library and value sets (and any it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56. 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 should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the value is override, the version used SHALL explicitly be represented in the expansion parameters
manifestcanonical0..1Specifies an asset-collection library that defines version bindings for code systems referenced by the value set(s) being expanded. When specified, code systems identified as `depends-on` related artifacts in the library have the same meaning as specifying that code system version in the `system-version` parameter.
include-dependenciesboolean0..1Specifies whether to include known (i.e. present on the server) dependencies of the library in the resulting package, recursively (default = true)
include-componentsboolean0..1Specifies whether to include known (i.e. present on the server) components of the library in the resulting package, recursively (default = true)

Output Parameters (1)

NameTypeCard.Description
returnBundle1..1The result of the packaging. Servers generating packages SHALL include all the dependency resources referenced by the library that are known to the server (if include-dependencies is true), and all the component resources referenced by the library that are known to the server (if include-components is true). For example, a measure repository SHALL include all the required library resources, but would not necessarily have the ValueSet resources referenced by the measure.

Additional Information

Version
2.1.2
Date
2021-07-26T09:29:23+11:00