# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.001 | number | 11 | ||||
.01 | date/time entered(+) | 0;1 | POINTER | 772 | B | |
2 | message id | 0;2 | FREE TEXT | This is an unique identifier associated with a message. | ||
2.02 | fast purge dt/tm | 2;2 | DATE-TIME | |||
3 | transmission type(+) | 0;3 | SET OF CODES | I:INCOMING O:OUTGOING | The type of transmission (incoming or outgoing). | |
4 | priority | 0;4 | SET OF CODES | I:IMMEDIATE D:DEFERRED | The delivery priority assigned to this outgoing message. | |
5 | header type | 0;5 | SET OF CODES | M:SINGLE MESSAGE B:BATCH OF MESSAGES F:FILE OF BATCHES | There are three types of messages as follows: M for Single message (contains only one MSH segment) B for Batch of messages (contains multiple MSH segments) F for File of batches (contains multiple BHS segments) This field is automatically filled in by the Messaging System and is used to determine the appropriate header segment to build for a message. | |
6 | initial message | 0;6 | POINTER | 773 | AF | This is the first message of a transaction. All messages pointing to the initial message are part of the transaction. |
7 | logical link | 0;7 | POINTER | 870 | This is a pointer to the Logical Link file (#870). This link is used to transmit messages to an external receiving application. This field is not filled in when messages are exchanged between DHCP applications on the same system. | |
8 | subscriber protocol | 0;8 | POINTER | 101 | The Protocol related to this message. | |
9 | security | 0;9 | FREE TEXT | The value to use in the Security field of the Message Header segment. | ||
10 | don't purge | 2;1 | SET OF CODES | 1:DON'T PURGE 0:TO PURGE | When this field is set to 1, the message wil never be purged by the HL7 "Purge Message Text File Entries" option. However, when this field is set to 0 or is empty, the message is allowed to be purged by the HL7 "Purge Message Text Entries" option. | |
11 | continuation pointer | 1;1 | FREE TEXT | The value to use in the Continuation Pointer field of the Message Header segment. | ||
12 | acknowledgement to | 0;10 | POINTER | 773 | This field points to the message that the MSA segment in the current message is acknowledging. | |
13 | sending application | 0;11 | POINTER | 771 | The application that is sending the message. | |
14 | receiving application | 0;12 | POINTER | 771 | The application that is receiving this message. | |
15 | message type | 0;13 | POINTER | 771.2 | This is the Message type from the HL7 standard. | |
16 | event type | 0;14 | POINTER | 779.001 | This is the Event Type from the HL7 standard. | |
17 | logical link - in queue | 0;17 | POINTER | 870 | ||
20 | status(+) | P;1 | POINTER | 771.6 | AG | The status currently assigned to this message. |
21 | status update date/time | P;2 | DATE-TIME | The date and time the Status field was last updated for this message. | ||
22 | error message | P;3 | FREE TEXT | If there was an error in sending or receiving this message, this field will contain the error message. | ||
23 | error type | P;4 | POINTER | 771.7 | A description of the type of error that occured. | |
24 | transmission attempts | P;5 | NUMERIC | This field contains the number of transmission attempts for this outgoing message. | ||
25 | open attempts | P;6 | NUMERIC | This field contains the number of attempts to open a TCP connections for this outgoing message. | ||
26 | ack timeout | P;7 | NUMERIC | The number of seconds the Lower Layer Protocol waits for an acknowledgement from the receiving application. This field will override the ACK TIMEOUT of the Logical Link for this message. | ||
50 | message size | COMPUTED | This computed field returns the number of character in a message. It includes the message header and body. | |||
90.01 | hlp-subscriber protocol | 90;1 | FREE TEXT | This field holds the SUBSCRIBER PROTOCOL that was on the 1st piece of the HLP("SUBSCRIBER"[,#]) subscriber entry. (If the HLP("SUBSCRIBER") entry was used to reset the MSH segment fields, this field will be null.) Additional Comments on ^HLMA(ien,90) Node ----------------------------------------- When the MSH segment fields are successfully reset using either HLP("SUBSCRIBER") or HLP("SUBSCRIBER",#), the entire HLP("SUBSCRIBER") or HLP("SUBSCRIBER",#) array entry is stored on the ^HLMA(#,90) node. There are eight pieces in the HLP("SUBSCRIBER"[,#]) array, and there are eight fields on the ^HLMA(ien,90) node. The eight pieces of HLP("SUBSCRIBER"[,#]) and the eight ^HLMA(ien,90) fields exactly correspond to each other. Note: When ^HLMA(ien,90) is created, it is set equal to the entire value of the HLP("SUBSCRIBER"[,#]) array entry. The fields on the ^HLMA(ien,90) node are not set separately! (So, if the application developer creates an invalid HLP("SUBSCRIBER"[,#]) array, with invalid data stored in one or more of the eight pieces, the ^HLMA(ien,90) node will similarly hold invalid data.) | ||
90.02 | hlp-sending application | 90;2 | FREE TEXT | This field holds the SENDING APPLICATION that was on the 2nd piece of the HLP("SUBSCRIBER"[,#]) subscriber entry. (See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.) | ||
90.03 | hlp-sending facility | 90;3 | FREE TEXT | This field holds the SENDING FACILITY that was on the 3rd piece of the HLP("SUBSCRIBER"[,#]) subscriber entry. (See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.) | ||
90.04 | hlp-receiving application | 90;4 | FREE TEXT | This field holds the RECEIVING APPLICATION that was on the 4th piece of the HLP("SUBSCRIBER"[,#]) subscriber entry. (See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.) | ||
90.05 | hlp-receiving facility | 90;5 | FREE TEXT | This field holds the RECEIVING FACILITY that was on the 5th piece of the HLP("SUBSCRIBER"[,#]) subscriber entry. (See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.) | ||
90.06 | hlp-subroutine | 90;6 | FREE TEXT | See the description for the HLP-ROUTINE field (#90.07). | ||
90.07 | hlp-routine | 90;7 | FREE TEXT | Application developers may pass a reference to M code in the HLP("SUBSCRIBER"[,#]) subscriber entry. When this is done, the subroutine being referenced is stored in the HLP-SUBROUTINE field (#90.06), and the routine is stored in this field. | ||
90.08 | hlp-debug | 90;8 | FREE TEXT | The application developer can control what type of debugging data is stored when MSH segment fields are reset by the HLP("SUBSCRIBER"[,#]) entry. This field holds the data on the eighth piece of the HLP("SUBSCRIBER"[,#]) entry, which also specifies which debugging data should be stored. Types Debug Data: ----------------- There are three types of debug data: - Node ^HLMA(ien,90) data. (See global map of this file for fields.) - Node ^HLMA(ien,91) data. (See global map of this file for fields.) - ^XTMP("HLCSHDR3 ien") data. (See patch documentation for explanation.) Syntax: ------- The syntax for the eight piece of the HLP("SUBSCRIBER"[,#]) array entry, (which is also the value for this field), is: [1]-[1]-[1] The [brackets] above indicate optionality; any of the three dash-delimited pieces may be null. Examples: 1-1-1 -> ^HLMA(ien,90), ^HLMA(ien,91) and ^XTMP data captured. 1--1 -> ^HLMA(ien,90 and ^XTMP data captured. --1 -> Only ^XTMP data captured. | ||
91.01 | original snd app | 91;1 | FREE TEXT | The value of the SENDING APPLICATION is calculated from the event driver protocol. If this value is overwritten by a HLP("SUBSCRIBER"[,#]) entry, the value before overwrite is stored in this field. Note: Fields 91.03, 91.05, and 91.07 similarly hold the pre-overwrite values for their respective fields. | ||
91.02 | original snd app-source | 91;2 | SET OF CODES | A:ARRAY M:M CODE | MSH segment fields can be overwritten by free-text values on pieces 2 through 5 of the HLP("SUBSCRIBER"[,#]) node, or by M code referenced in this node. If the HLP-ORIGINAL SND APP field (#91.01) is overwritten by free-text data, this field will hold an "A" (for array.) If overwritten by M code this field will hold "M". | |
91.03 | original snd fac | 91;3 | FREE TEXT | The value of the SENDING FACILITY is calculated from the event driver protocol. If this value is overwritten by a HLP("SUBSCRIBER"[,#]) entry, the value before overwrite is stored in this field. | ||
91.04 | original snd fac-source | 91;4 | SET OF CODES | A:ARRAY M:M CODE | MSH segment fields can be overwritten by free-text values on pieces 2 through 5 of the HLP("SUBSCRIBER"[,#]) node, or by M code referenced in this node. If the HLP-ORIGINAL SND FAC field (#91.03) is overwritten by free-text data, this field will hold an "A" (for array.) If overwritten by M code this field will hold "M". | |
91.05 | original rec app | 91;5 | FREE TEXT | The value of the RECEIVING APPLICATION is calculated from the subscriber protocol. If this value is overwritten by a HLP("SUBSCRIBER"[,#]) entry, the value before overwrite is stored in this field. | ||
91.06 | original rec app-source | 91;6 | SET OF CODES | A:ARRAY M:M CODE | MSH segment fields can be overwritten by free-text values on pieces 2 through 5 of the HLP("SUBSCRIBER"[,#]) node, or by M code referenced in this node. If the HLP-ORIGINAL REC APP field (#91.05) is overwritten by free-text data, this field will hold an "A" (for array.) If overwritten by M code this field will hold "M". | |
91.07 | original rec fac | 91;7 | FREE TEXT | The value of the RECEIVING FACILITY is calculated from the subscriber protocol. If this value is overwritten by a HLP("SUBSCRIBER"[,#]) entry, the value before overwrite is stored in this field. | ||
91.08 | original rec fac-source | 91;8 | SET OF CODES | A:ARRAY M:M CODE | MSH segment fields can be overwritten by free-text values on pieces 2 through 5 of the HLP("SUBSCRIBER"[,#]) node, or by M code referenced in this node. If the HLP-ORIGINAL REC FAC field (#91.07) is overwritten by free-text data, this field will hold an "A" (for array.) If overwritten by M code this field will hold "M". | |
100 | last date/time updated | S;1 | DATE-TIME | AF | For outgoing message: 1. Date/time of its commit ACK received. 2. Date/time of its application ACK message received (overwriting #1). And for incoming message: 1. Date/time of the message received. 2. Date/time of the message has been processed by the application (overwriting #1). | |
102 | time start to send | S;2 | DATE-TIME | This is the date/time the transmission of this outgoing message began. | ||
103 | time sent | S;3 | DATE-TIME | This is the date/time the transmission of this outgoing message finished. | ||
104 | time of commit/app ack | S;4 | DATE-TIME | This is the date/time this message received the commit ACK, or application ACK of original mode or direct connect transmission (API: DIRECT^HLMA). | ||
105 | time of application ack | S;5 | DATE-TIME | This is the date/time this message received the application ACK. | ||
106 | time start processing | S;6 | DATE-TIME | This is the date/time the application began processing this message. | ||
107 | time processed | S;7 | DATE-TIME | This is the date/time the application finished processing this message. | ||
200 | msh | MSH;0 | WORD-PROCESSING |