| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | message id(+) | 0;1 | FREE TEXT | B | ||
| .02 | message body(+) | 0;2 | POINTER | 777 | ||
| .03 | application acknowledgment to | 0;3 | FREE TEXT | This is the Message Control ID of the original message to which this message is an application acknowledgment. | ||
| .04 | direction(+) | 0;4 | SET OF CODES | I:INCOMING O:OUTGOING | ||
| .05 | link(+) | 0;5 | FREE TEXT | |||
| .06 | queue | 0;6 | FREE TEXT | |||
| .07 | application acknowledgment by | 0;7 | FREE TEXT | |||
| .08 | remote port | 0;8 | NUMERIC | This is the remote port # that may be found in the message header. For outgoing messages, it is in the Receiving Facility field, for incoming messages it is in tthe Sending Facility. For application acknowledgments, the port provided in the original message is used to return the acknowledgment. | ||
| .09 | scheduled purge date/time | 0;9 | DATE-TIME | |||
| .1 | application ack rspns tag | 0;10 | FREE TEXT | The sending application routine to execute when the application ack is received. This is part one of a two-part field which is the entry point. The second part names the routine. | ||
| .11 | application ack rspns rtn | 0;11 | FREE TEXT | Answer must be 1-8 characters in length. The sending application routine to execute when the application ack is received. This is part two of a two-part field which is the routine name. The first part names the entry point. For an returned application ack, this field documents the routine that was executed to process the application ack. | ||
| .12 | accept ack rspns tag | 0;12 | FREE TEXT | The sending application's routine to execute when the transmission of the message fails, i.e., the message cannot be sent or no acceptack is received. This is part one of a two-part field, naming the entry point of the routine to be called. The second part names the routine. | ||
| .13 | accept ack respns rtn | 0;13 | FREE TEXT | The sending application routine to execute whe the commit ack is received. This is part two of a two-part field, consisting of the routine name. The first part names the entry point with the M routine. | ||
| .14 | transmission failure rspns tag | 0;14 | FREE TEXT | The sending application's routine to execute when the transmission of the message fails, i.e., the message can not be sent or no commit ack is received. This is part one of a two-part field which is the entry point. The second part names the routine. | ||
| .15 | transmission failure rspns rtn | 0;15 | FREE TEXT | The sending application's routine to execute when the transmission of the message fails, i.e., the message can not be sent or no commit ack is received. This is part two of a two-part field which is the routine's name. The first part names the entry point. | ||
| .16 | transmission date/time | 0;16 | DATE-TIME | This is the date and time that the message was either received or sent. | ||
| .17 | accept ack'd | 0;17 | BOOLEAN | 1:YES | ||
| .18 | application ack'd | 0;18 | BOOLEAN | 1:YES | For incoming messages, this flag indicates that an application ack was returned. For outgoing messages, this field indicates that the application ack was sent. | |
| .19 | application handoff | 0;19 | BOOLEAN | 1:YES | This flag indicates that this message was handed to the application. That may be for initial processing, or it may be in response to one of the other conditions that an application may register its need to respond, such as a failure of the remote system to accept the message. | |
| .2 | completion status | 0;20 | SET OF CODES | SU:SUCCESSFUL TF:(obsolete) transmission failure SE:(obsolete) system error AE:(obsolete) application error ER:ERROR | This field indicates the final status of the message. Any code but SU (SUCCESSFUL) indicates that an error occurred. No value indicates that the message has not completed. | |
| .21 | error text | 0;21 | FREE TEXT | The HL7 package may use this field to document errors that prevent transmission. Errors determined by the remote system are contained in the MSA segment of the response message. | ||
| .22 | app-specified retention | 0;22 | NUMERIC | This field indicates the minimum retention time in days specified by the application for the message before it is purged. When the purge is actually scheduled the site parameter will override the retention time specified in this field if the site parameter specifies a longer retention time. | ||
| 1 | hdr segment,components 1-6(+) | 1;E1,250 | FREE TEXT | |||
| 2 | hdr segment,components 7-end(+) | 2;E1,250 | FREE TEXT | |||
| 3 | msh segments for batch | 3;0 | MULTIPLE | 778.03 | ||
| 4.01 | date/time of accept ack | 4;1 | DATE-TIME | This field will be used to record the accept ack. | ||
| 4.02 | accept ack message id | 4;2 | FREE TEXT | |||
| 4.03 | accept ack msa segment | 4;3 | FREE TEXT | |||
| 5 | tranmission attempts | TRIES;1 | NUMERIC | For outgoing messages, this field is a counter of how many times HLO attempted to send this message. | ||
| 5.01 | sequence queue | 5;1 | FREE TEXT | Applications may have difficulty insuring that messages are received by the remote application in the same order that the sending application generates the messages. If an application determines that maintaining the order of its messages is necessary, one method it may use it to specify that 1) Application acknowledgemnts are needed and 2) that the messages should be placed on a sequence queue. Messages that are placed on a particular sequence queue are not moved to the outgoing queue for transmission until the application acknolwedgment for the preceding message is received. This guarantees the order of delivery. | ||
| 5.02 | moved to out queue | 5;2 | BOOLEAN | 1:YES | ||
| 5.03 | sequencing exception raised | 5;3 | BOOLEAN | 1:YES |
Not Referenced