MSH: Message Header
Definition
Segment | Field | Opt | RP/# | Component | Description | Example | 1 | |
---|---|---|---|---|---|---|---|---|
MSH | Message header | 2|||||||
MSH-3 | O | Sending application. Note that for inbound ORU R01 messages this field is used to determine whether the message contains radiology information. See the ORU R01 specification for more information. | 3||||||
MSH-3.1 | Sending application name | PAS | ||||||
4 | MSH-4 | O | Sending facility. If you configure org and/or team aliases with PKB, the value in this field will be mapped to a whitelisted organisation or team in PKB, and this message will be treated as coming from that organisation or team. | |||||
5 | MSH-4.1 | Sending facility name | MyFacility | 6|||||
MSH-5 | O | Receiving application. We do not use this field; you are welcome to send through whatever is convenient. There is only one PKB instance behind the HL7 endpoint, so no routing is required. | 7||||||
MSH-6 | O | Receiving facility. We do not use this field; you are welcome to send through whatever is convenient. There is only one PKB instance behind the HL7 endpoint, so no routing is required. | ||||||
8 | MSH-7 | R | Message timestamp. Sending an offset in MSH-7 is discouraged; please see our notes on time stamp handling for more information. | 9|||||
MSH-7.1 | Message timestamp | 20210521092210 | ||||||
10 | MSH-9 | R | Message type | |||||
11 | MSH-9.1 | Message type | QRY | |||||
12 | MSH-9.2 | Trigger event | A19 | 13|||||
MSH-10 | R | Message control ID. This must be unique for all messages sent to PKB by each sender. However, PKB does not currently detect or reject duplicate messages based on this value, so it is important that each sender enforces this themselves. | ||||||
14 | MSH-10.1 | Message control ID | 4003ace9-ab29-4a97-a76a-69d45052dbc6 | |||||
15 | MSH-11 | R | Processing ID | 16|||||
MSH-11.1 | Processing ID. This must be P for our production server. | P | 17||||||
MSH-12 | O | Version ID. We do not use this field. Our message definitions are not dependent on version number. | 18||||||
MSH-22 | O | Responsible Organisation | 19||||||
MSH-22.10 | Responsible Organisation Identifier | org.id.123 | 20
PKB customer sites:deploy |developer |information governance |procurement |manual
...