The MSH Message Header segment defines the intent, source, destination, and some specifics of the syntax of a message. Every message will have the MSH segment as the first message segment. For a more complete description of this segment, see the guide for HL7 version 2.5.1.
Throughout this section, "Acme" is used as a placeholder name for your organization.
The following table describes the guidelines that should be observed when interpreting these segment layouts:
| Sequence No. | Destination Data Length | Data Field Name | Comments | Special Processing for Destination | Field Sent to Target Application |
|---|---|---|---|---|---|
Unlimited | Segment ID | "MSH" | Copy | Yes | |
1 | Unlimited | Field Separator | Jamf: Required | Copy | Yes |
2 | Unlimited | Encoding Characters | Jamf: Required Acme IE Std: ^~\& | Copy | Yes |
3 | Unlimited | Sending Application | Jamf: Required Acme IE Std: "ACME_ADM" | Force "ACME_ADM" | Yes |
4 | Unlimited | Sending Facility | Acme IE Std: "ACME" | Force "ACME" | Yes |
5 | Unlimited | Receiving Application | Jamf: "JAMF" | Force "JAMF" | Yes |
6 | Unlimited | Receiving Facility | Force "ACME" | Yes | |
7 | Unlimited | Date/Time of Message | Jamf: Required Acme IE Std: YYYMMDDHHMM[SS] where [SS] is optional and only valued if received from source system. | Copy | Yes |
8 | Unlimited | Jamf: Ignores | Copy input MSH 9.2 | Yes | |
9 | Unlimited | Message Type | Jamf: Required | Yes | |
9.1 | Unlimited | Message Type Code | Copy | Yes | |
9.2 | Unlimited | Message Type Event Type Code | Calculate value based on trigger event table | Yes | |
10 | Unlimited | Message Control ID | Jamf: Required, but does not need to be unique. Acme IE Std: Source system's Message Control ID | Yes | |
11 | Unlimited | Processing ID | Jamf: Ignores Acme IE Std: "P" production, "T" testing. | Copy | Yes |
12 | Unlimited | Version ID | Jamf: Required Acme IE Std: 2.5.1 | Copy | Yes |
13.21 | Unlimited | Jamf: None needed | No |