Files > HL7 APPLICATION PARAMETER

name
HL7 APPLICATION PARAMETER
number
771
location
^HL(771,
description
This file contains a list of Vista applications that are capable of sending and receiving HL7 transmissions.
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1FREE TEXTBThe name of the application that will send/receive HL7 messages (e.g., RADIOLOGY). Vista application names must be namespaced and unique. Answer must be 3-120 characters in length.
2active/inactive0;2SET OF CODESa:ACTIVE
i:INACTIVE
This field indicates whether the DHCP application is currently active. A DHCP application should be inactivated when application updates are taking place. The HL7 package will not accept messages from an inactive SENDING APPLICATION. An error will be returned from the call to GENERATE^HLMA. Also, it will not hand off inbound messages to an inactive RECEIVING APPLICATION. An error status will be logged.
3facility name0;3FREE TEXTThis information will be placed in the FACILITY ID field of the HL7 message header if present. This information will override the default facility id information whenever the FACILITY ID REQUIRED field of the subscriber protocol is set to YES.
4mail group0;4POINTER3.8Vista applications may use this field to generate Mailman notifications when messaging problems are detected. To retrieve this mailgroup, see documentation for the API, GETAPP^HLCS2.
5*hl7 segmentSEG;0MULTIPLE771.05This is applicable to HL7 v1.5 interfaces only. Enter the HL7 segments used by the Vista application.
6*hl7 messageMSG;0MULTIPLE771.06This is applicable only to HL7 v1.5 interfaces. Enter the HL7 messages used by the DHCP application.
7country code0;7POINTER779.004Enter the country code associated with this application.
100hl7 field separatorFS;E1,2FREE TEXTThe field separator separates two adjacent fields within a segment. It also separates the segment ID from the first data field in the segment. The field separator can be defined differently for each HL7 message. The fourth character in the MSH segment serves as the field separator for all segments in the HL7 message. If this field is left blank, the default will be the '^' character. However, most messaging applications use the '|' as a field separator. Note that the character used as a field separator CANNOT be reused as one of the HL7 ENCODING CHARACTERS. If you choose the default '^' as a field separator then choose the default encoding characters as well (~|\&). If you choose the vertical bar as a field separator, then simply replace the vertical bar in the encoding characters with the '^', i.e., ~^\&. Due to Fileman limitations, the '^' cannot be the first character in the encoding character string.
101hl7 encoding charactersEC;E1,4FREE TEXTIf this field is left blank, the default encoding characters will be set to, "~|\&". Note that if you choose this default, the FIELD SEPARATOR must be set to "^". If you choose the vertical bar ("|") as a field separator, enter "~^\&" as your encoding characters. This will avoid a potential conflict with VA Fileman. Up to four encoding characters may be defined. Each encoding character must be unique and none of the encoding characters may be the same as the field separator character. Each encoding character serves a specific purpose. The first encoding character is the component separator. Some data fields may be divided into multiple components. The component separator is used to separate adjacent components within a data field. The second encoding character is the repetition separator. Some data fields may be repeated multiple times in a segment. The repetition separator character is used to separate multiple occurrences of a field. The third encoding character is the escape character. Data fields defined as text or formatted text may include escape sequences. The escape character is used to separate escape sequences from the actual text. The fourth encoding character is the sub-component separator. Some data fields may be divided into components, and each component may be further divided into sub-components. The sub-component separator is used to separate adjacent sub-components within a component of a field. Note that the character used as a field separator CANNOT be reused as one of the HL7 ENCODING CHARACTERS. If you choose the default '^' as a field separator then choose the default encoding characters as well (~|\&). If you choose the vertical bar as a field separator, then simply replace the vertical bar in the encoding characters with the '^', i.e., ~^\&. Due to Fileman limitations, the '^' cannot be the first character in the encoding character string.

Referenced by 9 types

  1. ADT/HL7 TRANSMISSION (39.4) -- sending application
  2. RAD/NUC MED REPORTS (74) -- report verified by cots app
  3. HL7 Message Exceptions File (79.3) -- sending application
  4. RAD/NUC MED HL7 APPLICATION EXCEPTION (79.7) -- hl7 application name
  5. PROTOCOL (101) -- sending application, receiving application
  6. ADT/HL7 EVENT REASON (391.72) -- hl7 application parameter
  7. HL7 NON-DHCP APPLICATION PARAMETER (770) -- dhcp application, related file 771 entry
  8. HL7 MESSAGE TEXT (772) -- server application, client application
  9. HL7 MESSAGE ADMINISTRATION (773) -- sending application, receiving application