Difference between revisions of "MSH"
From Updox API
(Created page with "{| border="1" cellpadding="4" cellspacing="0" |- !Sequence !Length !Data Type !Req/Optional/Not Used !Element Name |- |1 |1 |ST |R |Field Separator |- |2 |4 |ST |R |Encoding ...") |
|||
| Line 1: | Line 1: | ||
| + | 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. | ||
| + | |||
{| border="1" cellpadding="4" cellspacing="0" | {| border="1" cellpadding="4" cellspacing="0" | ||
|- | |- | ||
| Line 52: | Line 54: | ||
|40 | |40 | ||
|ST | |ST | ||
| − | | | + | |NU |
|Security | |Security | ||
|- | |- | ||
| Line 82: | Line 84: | ||
|15 | |15 | ||
|NM | |NM | ||
| − | | | + | |NU |
|Sequence Number | |Sequence Number | ||
|- | |- | ||
| Line 88: | Line 90: | ||
|180 | |180 | ||
|ST | |ST | ||
| − | | | + | |NU |
|Continuation Pointer | |Continuation Pointer | ||
|- | |- | ||
| Line 94: | Line 96: | ||
|2 | |2 | ||
|ID | |ID | ||
| − | | | + | |NU |
|Accept Acknowledgement Type | |Accept Acknowledgement Type | ||
|- | |- | ||
| Line 100: | Line 102: | ||
|2 | |2 | ||
|ID | |ID | ||
| − | | | + | |NU |
|Application Acknowledgement Type | |Application Acknowledgement Type | ||
|- | |- | ||
| Line 106: | Line 108: | ||
|2 | |2 | ||
|ID | |ID | ||
| − | | | + | |NU |
|Country Code | |Country Code | ||
|- | |- | ||
| Line 112: | Line 114: | ||
|6 | |6 | ||
|ID | |ID | ||
| − | | | + | |NU |
|Character Set | |Character Set | ||
|- | |- | ||
| Line 118: | Line 120: | ||
|3 | |3 | ||
|CE | |CE | ||
| − | | | + | |NU |
|Principal Language of Message | |Principal Language of Message | ||
|} | |} | ||
Latest revision as of 04:52, 10 April 2018
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 |
