Profile: ITK-Message-Bundle-1
Elements required for capability
| Element | Use | CareConnect | UK Core |
|---|---|---|---|
| meta | |||
| identifier | |||
| type | |||
| entry (ITK-Message-Header-2) | |||
| entry (CareConnect-ITK-Header-Organization-1) | |||
| entry (ITK-Document-Bundle-1) |
meta
Usage
Optional
Guidance
This guide relies on MESH as the sending mechanism, and harnesses the MESH .CTL <version> element to indicate the version of the document that is being sent.
However, it is recommended that the meta.versionId element be populated with the version of the document that is being sent. This will be the same version as that populated in the MESH .CTL file.
Example
<meta> <versionId value="1" /> </meta>
identifier
Usage
Mandatory
Guidance
The identifier MUST be present and unique for each message.
Example
<identifier> <system value="https://tools.ietf.org/html/rfc4122" /> <value value="73c52d0f-8584-43fe-b492-3a4d3017ac22" /> </identifier>
type
Usage
Mandatory
Guidance
The type MUST have a fixed value of message, from the BundleType valueset.
Example
<type value="message" />
entry
entry elements, which are outlined below.
entry (ITK-MessageHeader-2)
Usage
Mandatory
Guidance
The entry MUST contain a MessageHeader resource profiled to the ITK-MessageHeader-2 structure definition.
More information about how to populate this resource can be found in this guide using the link below.
entry (CareConnect-ITK-Header-Organization-1)
Usage
Mandatory
Guidance
The entry MUST contain a Organzation resource profiled to the CareConnect-ITK-Header-Organization-1 structure definition.
More information about how to populate this resource can be found in this guide using the link below.
entry (ITK-Document-Bundle-1)
Usage
Mandatory
Guidance
The entry MUST contain a Bundle resource profiled to the ITK-Document-Bundle-1 structure definition.
More information about how to populate this resource can be found in this guide using the link below.