This file contains information related to the processing of all incoming and outgoing messages.
.01date/time entered(+)0;1DATE-TIMEBThe Date/Time the message was created.
2server application(+)0;2POINTER771The DHCP application related to this transmission.
2.02fast purge dt/tm2;2DATE-TIME
3client application(+)0;3POINTER771The client application related to this transmission.
4transmission type(+)0;4SET OF CODESI:INCOMING
The type of transmission (incoming or outgoing).
5related mailman message0;5FREE TEXTThe MailMan message number related to this transmission.
6message id0;6FREE TEXTThe unique ID for this HL7 message.
7acknowledgment to0;7POINTER772The incoming message that this message is replying to. This field is only applicable to outgoing messages.
8parent message0;8POINTER772AI
The delivery priority assigned to this message. Either 'I' for Immediate or 'D' for Deferred.
10related event protocol0;10POINTER101
11logical link0;11POINTER870This is a pointer to the Logical Link file (#870). This link is used to transmit messages to an external (client) application. This field is not filled in when messages are exchanged between DHCP applications on the same system.
12security0;12FREE TEXT
13continuation pointer1;1FREE TEXT
14message type(+)0;14SET OF CODESM:SINGLE MESSAGE
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.
15don't purge2;1SET OF CODES1:DON'T 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.
16namespace0;13FREE TEXTThis field must not be filled in manually. It will be filled in automatically by the HL7 processes that create entries in the HL7 Message Text file (#772). In most instances, applications will call GENERATE^HLMA, GENACK^HLMA, or DIRECT^HLMA. When they do, they will pass by reference into the last OPTIONS (in the documentation) parameter the value of the namespace. The value of the namespace will be in the form of OPTIONS("NAMESPACE")=NAMESPACE. Please note that the calls to the three APIs mentioned above use the variable HLP to hold the passed in by reference array. So, in the HLMA code (and other code invoked by HLMA), the actual variable used is HLP("NAMESPACE"). This field is populated by UPDATE^HLTF0.
20status(+)P;1POINTER771.6AFThe status currently assigned to this transmission.
21date/time processedP;2DATE-TIMEThe date and time this transmission was actually processed (sent or received).
22error messageP;3FREE TEXTIf there was an error in sending or receiving this transmission, this field will contain the 3-200 character error message.
23error typeP;4POINTER771.7
26ack timeoutP;7NUMERICThe 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.
100no. of characters in messageS;1NUMERICA count of the total number of characters in the mail message associated with this HL7 transmission entry.
101no. of events in messageS;2NUMERICA count of the total number of events (HL7 messages) contained in the mail message associated with this HL7 transmission entry.
102transmission timeS;3NUMERICThe time it took to transmit this message to the primary network addressee.
200message textIN;0WORD-PROCESSINGThe actual text of the incoming HL7 message(s).

Referenced by 4 types

  1. PADE OUTBOUND MESSAGES (58.72) -- 772 pointer
  2. CP_HL7_LOG (704.002) -- hl7_message_text
  3. HL7 MESSAGE TEXT (772) -- acknowledgment to, parent message
  4. HL7 MESSAGE ADMINISTRATION (773) -- date/time entered