Profile: ITK-MessageHeader-2
Elements required for capability
| Element | Use | CareConnect | UK Core |
|---|---|---|---|
| extension(ITKMessageHandling) | |||
| event | |||
| receiver | |||
| sender | |||
| timestamp | |||
| source | |||
| response | |||
| focus |
extension(ITKMessageHandling)
Usage
Mandatory
Guidance
This item is found in the Extension-ITK-MessageHandling-2 extension within the ITK3 Message Header.
More information about how to populate this element can be found in this guide using the link below.
event
Usage
Mandatory
Guidance
The ITK-MessageHeader-2.event MUST contain a fixed value of ITK007C (ITK GP Connect Send Document) from the code system ITK-MessageEvent-2.
Example
<event> <system value="https://fhir.nhs.uk/STU3/CodeSystem/ITK-MessageEvent-2"/> <code value="ITK007C"/> <display value="ITK GP Connect Send Document"/> </event>
receiver
Usage
Do not use (if relying on MESH for message routing)
Guidance
This value MUST NOT be present. This is because we rely on MESH message routing to be used to route the message to the registered GP practice using a citizen's:
- NHS Number
- date of birth
- surname
sender
Usage
Mandatory
Guidance
A reference MUST be provided using the CareConnect-ITK-Header-Organization-1 resource.
More information about how to populate this resource can be found in this guide using the link below.
timestamp
Usage
Mandatory
Guidance
The timestamp element MUST contain the date and time of when the message was generated.
source
Usage
Mandatory
Guidance
The source element MUST contain the MESH mailbox ID of the sender.
Example
<source> <endpoint value="MESHGP0001" /> </source>
response
Usage
Do not use
Guidance
Not required to be populated as this use case assumes communication is linear between the sender and receiver.
focus
Usage
Mandatory
Guidance
A reference MUST be provided using the ITK-Document-Bundle-1 resource.
More information about how to populate this resource can be found in this guide using the link below.