Global: ^HLMA

1)= S ^HLMA("B",$E(X,1,30),DA)=""

2)= K ^HLMA("B",$E(X,1,30),DA)

This is an unique identifier associated with a message.

1)= S ^HLMA("C",$E(X,1,30),DA)=""

2)= K ^HLMA("C",$E(X,1,30),DA)

This cross reference allows a user to look up an HL7 message by its unique message ID.

1)= S:$P(^HLMA(DA,0),U,12) ^HLMA("AH",+$P(^(0),U,12),X,DA)=""

2)= K:$P(^HLMA(DA,0),U,12) ^HLMA("AH",+$P(^(0),U,12),X,DA)

3)= This x-reference is used in conjunction with the 'AG' x-ref on field 205

This x-reference is used to look up the original message when processing a response.

Short Descr:  Removes record from the "AI" x-ref if Fast Purge Date/Time is edited.

Set Logic:  Q

Kill Logic:  K:$G(X1(1)) ^HLMA("AI",X1(1),773,+$G(DA))

X(1):  FAST PURGE DT/TM  (773,2.02)  (Subscr 1)  (forwards)

The type of transmission (incoming or outgoing).

UNEDITABLE

The delivery priority assigned to this outgoing message.

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.

This is the first message of a transaction.  All messages pointing to the initial message are part of the transaction.

1)= S ^HLMA("AF",$E(X,1,30),DA)=""

2)= K ^HLMA("AF",$E(X,1,30),DA)

same system.

1)= Q  S %=$P(^HLMA(DA,0),U,3) S:%]"" ^HLMA("AC",%,X,DA)="" I %="O",'$D(HLTCPO) D LLCNT^HLCSTCP(X,3)

2)= Q  S %=$P(^HLMA(DA,0),U,3) K:%]"" ^HLMA("AC",%,X,DA)

3)= Required to determine outgoing transmissions and incoming deferred responses.

This cross-references is used to determine outgoing transmission for a Logical Link; ^HLMA("AC","O",LL,DA).  The background job for the LL will use this x-ref and delete it as each message is transmitted.  It is also used

to process incoming messages that have a deferred response; ^HLMA("AC","I",LL,DA).  The incoming filer will check this x-ref and delete it as it processes each message.

The Protocol related to this message.

The value to use in the Security field of the Message Header segment.

Message Text Entries" option.

The value to use in the Continuation Pointer field of the Message Header segment.

This field points to the message that the MSA segment in the current message is acknowledging.

The application that is sending the message.

The application that is receiving this message.

1)= S:$P($G(^HLMA(DA,0)),U,2)]"" ^HLMA("AH",X,$P(^(0),U,2),DA)=""

2)= K:$P($G(^HLMA(DA,0)),U,2)]"" ^HLMA("AH",X,$P(^(0),U,2),DA)

3)= This x-reference is used in conjunction with the 'AH' on field 2.

This x-reference is used to look up the original message when processing a response.

This is the Message type from the HL7 standard.

This is the Event Type from the HL7 standard.

The status currently assigned to this message.

1)= S ^HLMA("AG",$E(X,1,30),DA)=""

2)= K ^HLMA("AG",$E(X,1,30),DA)

Short Descr:  Used by the Fast Purge process.

Description:  This cross-reference is used by the fast purge option to purge records in both file 773 and file 772.  The format is:

"AI",,772,)=""

"AI",,773,)=""

Set Logic:  D PXREF^HLUOPTF1($G(DA),$G(X2(1)))

Kill Logic:  Q

X(1):  STATUS  (773,20)  (Subscr 1)  (forwards)

The date and time the Status field was last updated for this message.

If there was an error in sending or receiving this message, this field will contain the error message.

A description of the type of error that occured.

This field contains the number of transmission attempts for this outgoing message.

This field contains the number of attempts to open a TCP connections for this outgoing message.

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.

This computed field returns the number of character in a message.  It includes the message header and body.

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.)

(See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.)

(See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.)

(See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.)

(See the 'Additional Comments on ^HLMA(ien,90) Node' section in the description for field # 90.01.)

See the description for the HLP-ROUTINE field (#90.07).

stored in this field.

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.

Note:  Fields 91.03, 91.05, and 91.07 similarly hold the pre-overwrite

values for their respective fields.

free-text data, this field will hold an "A" (for array.)  If overwritten by M code this field will hold "M".

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.

free-text data, this field will hold an "A" (for array.)  If overwritten by M code this field will hold "M".

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.

free-text data, this field will hold an "A" (for array.)  If overwritten by M code this field will hold "M".

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.

free-text data, this field will hold an "A" (for array.)  If overwritten by M code this field will hold "M".

The date and time this message was processed (sent or received).  For outgoing messages, it is the time the message was actually transmitted.  For incoming messages, it is the time the application processed the message.

1)= S ^HLMA("AD",X,DA)="" N %,%1 S %=$G(^HLMA(DA,0)),%1=$P(%,U,3),%=$P(%,U,7) K:%1]""&% ^HLMA("AC",%1,%,DA)

2)= K ^HLMA("AD",X,DA)

3)= Required to determine if a message has been processed.

This cross-reference is used to remove messages from the 'AC' x-ref. after they have been processed.  It also set the 'AD' x-ref for the date processed.