MSH
From Updox API
The following describes the MSH segment requirements for messages inbound to Updox. Requirements for messages outbound from Updox are dependent on the receiving implementation/system, and are negotiated during the implementation phase.
| Sequence | Length | Data Type | Req/Optional/Not Used | Element Name |
|---|---|---|---|---|
| 1 | 1 | ST | R | Field Separator |
| 2 | 4 | ST | R | Encoding Characters |
| 3 | 180 | HD | O | Sending Application |
| 4 | 180 | HD | O | Sending Facility |
| 5 | 180 | HD | O | Receiving Application |
| 6 | 180 | HD | O | Receiving Facility |
| 7 | 26 | TS | O | Date/Time of Message |
| 8 | 40 | ST | NU | Security |
| 9 | 7 | CM_MSG | R | Message Type |
| 10 | 20 | ST | R | Message Control Id |
| 11 | 3 | PT | R | Processing Id |
| 12 | 8 | ID | R | Version Id |
| 13 | 15 | NM | NU | Sequence Number |
| 14 | 180 | ST | NU | Continuation Pointer |
| 15 | 2 | ID | NU | Accept Acknowledgement Type |
| 16 | 2 | ID | NU | Application Acknowledgement Type |
| 17 | 2 | ID | NU | Country Code |
| 18 | 6 | ID | NU | Character Set |
| 19 | 3 | CE | NU | Principal Language of Message |
