Files > HL7 NON-DHCP APPLICATION PARAMETER

name
HL7 NON-DHCP APPLICATION PARAMETER
number
770
location
^HL(770,
description
This file contains parameters associated with non-DHCP applications from whom the DHCP system can accept HL7 transmissions. This is the main file that sites must edit before they can begin receiving HL7 transmissions from another system. This is done by using the Non-DHCP Application Parameters Enter/Edit option on the site manager's menu.
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1FREE TEXTBThe applications that the DHCP system will communicate with are referred to as non-DHCP applications simply as a way of distinguishing between the two applications. The application that the DHCP system will be communicating with could also be another DHCP application (e.g., Radiology sending/receiving HL7 messages to MAS). All application names (in files 770 and 771 combined) must be unique.
2dhcp station number(+)0;2FREE TEXTThe station number of the DHCP site that will receive/send HL7 messages to the non-DHCP application.
3non-dhcp facility name0;3FREE TEXTThe name of the facility associated with the non-DHCP application.
4maximum block size(+)0;4NUMERICThe maximum block size should almost always be 245 characters.
5number of retries0;5NUMERICThe number of times (1 to 99) to attempt sending an HL7 message (if initially unsuccessful) before requeuing the message for later transmission. A value of three is recommended.
6hl7 device0;6FREE TEXTNOTE: This field is only applicable if you are using the HL7 Hybrid Lower Layer Protocol. The HL7 Device and Mail Group fields are mutually exclusive. You may only enter a value in one of the fields. If you wish to enter a value in the HL7 Device field, you must first delete any value you have entered in the Mail Group field.
7hl7 version number(+)0;7POINTER771.5This is the version of the HL7 interface that the sending and receiving applications are using.
8dhcp application(+)0;8POINTER771AGThis is the DHCP application related to this non-DHCP application entry.
9lower level protocol timeout0;9NUMERICThe number of seconds (1 to 60) the lower level protocol should wait to receive data. This field is only applicable if you are using the HL7 Hybrid Lower Layer Protocol.
10mail group0;10POINTER3.8NOTE: This field is only applicable if you are using the MailMan lower level protocol. The Mail Group and HL7 Device fields are mutually exclusive. You may only enter a value in one of the fields. If you wish to enter a value in the Mail Group field, you must first delete any value you have entered in the HL7 Device field.
11transmission time0;11FREE TEXTThe time that transmissions to the non-DHCP application should occur expressed in 24 hour notation (i.e., 0001 to 2400).
12related file 771 entry(+)0;12POINTER771This field links entries in file 770 to corresponding entries in file 771.
13last transmission date/time0;13DATE-TIMEThe date and time of the last transmission to this non-DHCP application.
14hl7 processing id0;14SET OF CODESD:DEBUG
P:PRODUCTION
The HL7 processing ID may be either 'D' for 'DEBUG' or 'P' for 'PRODUCTION'. 'DEBUG' should be used while the interface is under test.
50start/stop transmission logLOG;1SET OF CODES1:START LOG
0:STOP LOG
This field is set automatically by the DHCP HL7 package when the option Start/Stop Log of HL7 Transmissions is executed. It indicates whether the log is turned on.
100purpose100;0WORD-PROCESSINGThis field is used to document the purpose of this non-DHCP application entry for local IRM staff. Basic information about the types of information exchanged, the frequency of the exchange, etc. should be entered.

Referenced by 1 types

  1. LA7 MESSAGE PARAMETER (62.48) -- hl7 non-dhcp application