Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All
Print Page as PDF
Global: ^HL(770

Package: Health Level Seven

Global: ^HL(770


Information

FileMan FileNo FileMan Filename Package
770 HL7 NON-DHCP APPLICATION PARAMETER Health Level Seven

Description

Accessed By FileMan Db Calls, Total: 8

Package Total Routines
Health Level Seven 3 HLPOST16    HLTASK    HLUOPT    
Registration 2 DG53140P    DGYLPOST    
Automated Medical Information Exchange 1 DVBAPST3    
Income Verification Match 1 IVM20P1    
Surgery 1 SRHLPOST    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Automated Lab Instruments 1 LA7 MESSAGE PARAMETER(#62.48)[7]    

Pointer To FileMan Files, Total: 3

Package Total FileMan Files
Health Level Seven 2 HL7 APPLICATION PARAMETER(#771)[8, 12]    HL7 VERSION(#771.5)[7]    
MailMan 1 MAIL GROUP(#3.8)[10]    

Fields, Total: 16

Field # Name Loc Type Details
.01 NAME 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>15!($L(X)<3)!'(X'?1P.E) X I $D(X),$S($D(^HL(770,"B",X)):1,$D(^HL(771,"B",X)):1,1:0) K X D EN^DDIOL("Sorry, Non-DHCP Application names must be unique.")
  • LAST EDITED:  JAN 10, 1995
  • HELP-PROMPT:  The name of the application from/to which HL7 messages may be transmitted by the DHCP system. Answer must be 3-15 characters in length and must be unique.
  • DESCRIPTION:  The 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  770^B
    1)= S ^HL(770,"B",$E(X,1,30),DA)=""
    2)= K ^HL(770,"B",$E(X,1,30),DA)
    Regular 'B' cross reference.
  • CROSS-REFERENCE:  770^AC^MUMPS
    1)= S:$P(^HL(770,DA,0),"^",3)]"" ^HL(770,"AF",X,$P(^(0),"^",3),DA)=""
    2)= K:$P(^HL(770,DA,0),"^",3)]"" ^HL(770,"AF",X,$P(^(0),"^",3),DA)
    This cross reference is used in conjunction with the 'AF' cross reference on the Facility Name field (#3) of the HL7 Non-DHCP Application Parameter file to validate the non-DHCP application name and non-DHCP facility name
    that are contained in the message header of each HL7 message that is received.
    This is a multi-key cross reference which contains the name of the non-DHCP application in the first piece and the name of the non-DHCP facility in the second piece.
  • CROSS-REFERENCE:  770^AD^MUMPS
    1)= S:$P(^HL(770,DA,0),"^",2)]"" ^HL(770,"AE",X,$P(^(0),"^",2),DA)=""
    2)= K:$P(^HL(770,DA,0),"^",2)]"" ^HL(770,"AE",X,$P(^(0),"^",2),DA)
    This cross reference is used in conjunction with the 'AE' cross reference on the DHCP Station Number field (#2) of the HL7 Non-DHCP Application Parameter file to validate the receiving DHCP facility for an HL7 message.
    This information is contained in the message header that is received with every HL7 message.
    This is a multi-key cross reference that contains the name of the non-DHCP application in the first piece and the DHCP station number in the second piece.
2 DHCP STATION NUMBER 0;2 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S DIC="^DIC(4,",DIC(0)="QEM" D ^DIC S X=$S(Y<0:0,'$D(^DIC(4,+Y,99)):0,$P(^(99),"^")']"":0,1:$P(^(99),"^")) K:X=0 X K DIC
  • LAST EDITED:  OCT 02, 1991
  • HELP-PROMPT:  The station number of the DHCP site that will receive/send HL7 messages to the non-DHCP application.
  • DESCRIPTION:  
    The station number of the DHCP site that will receive/send HL7 messages to the non-DHCP application.
  • EXECUTABLE HELP:  S Z1=D,X="?",DIC="^DIC(4,",DIC(0)="QEM" D ^DIC S DIC=DIE,D=Z1 K Z1,DIC
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  770^AE^MUMPS
    1)= S ^HL(770,"AE",$P(^HL(770,DA,0),"^"),X,DA)=""
    2)= K ^HL(770,"AE",$P(^HL(770,DA,0),"^"),X,DA)
    This is the corresponding cross reference to the 'AD' cross reference on the .01 field. See the description on the 'AD' cross reference for further information.
3 NON-DHCP FACILITY NAME 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>20!($L(X)<3) X
  • LAST EDITED:  SEP 12, 1994
  • HELP-PROMPT:  The name of the facility associated with the non-DHCP application. Answer must be 3-20 characters in length.
  • DESCRIPTION:  
    The name of the facility associated with the non-DHCP application.
  • CROSS-REFERENCE:  770^AF^MUMPS
    1)= S ^HL(770,"AF",$P(^HL(770,DA,0),"^"),X,DA)=""
    2)= K ^HL(770,"AF",$P(^HL(770,DA,0),"^"),X,DA)
    This is the corresponding cross reference to the 'AC' cross reference on the .01 field. See the description for the 'AC' cross reference for further information.
4 MAXIMUM BLOCK SIZE 0;4 NUMBER
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:+X'=X!(X>245)!(X<80)!(X?.E1"."1N.N) X
  • LAST EDITED:  SEP 30, 1991
  • HELP-PROMPT:  The maximum block size (line length) that the two applications can send/receive before a carriage return must be sent as a block separator. Type a Number between 80 and 245, 0 Decimal Digits.
  • DESCRIPTION:  
    The maximum block size should almost always be 245 characters.
5 NUMBER OF RETRIES 0;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  SEP 11, 1991
  • HELP-PROMPT:  The 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.
  • DESCRIPTION:  
    The 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.
6 HL7 DEVICE 0;6 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>30!($L(X)<1) X I $D(X) K:'$D(^%ZIS(1,"B",X)) X I $D(X),$P(^HL(770,DA,0),"^",10) K X D EN^DDIOL("You are not allowed to enter a value in both the Device and Mail Group fields.")
  • LAST EDITED:  JAN 04, 1995
  • HELP-PROMPT:  The name of the device (must exactly match a name in the DHCP Device file) that will be used to send/receive HL7 messages to this non-DHCP application. Answer must be 1-30 characters in length.
  • DESCRIPTION:  NOTE: 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  770^AL^MUMPS
    1)= S:$S('$D(^HL(770,DA,"LOG")):0,1:$P(^("LOG"),"^")) ^HL(770,"ALOG",X,DA)=""
    2)= K ^HL(770,"ALOG",X,DA)
    This cross reference is used in conjunction with the 'ALOG' cross reference on the Start/Stop Transmission Log field (#50) of the HL7 Non-DHCP Application Parameter file. When the value of field 50 is set to Start
    Transmission Log and the HL7 Device field (#6) in the HL7 Non-DHCP Application Parameter file is defined, the 'ALOG' cross reference is set. The 'ALOG' cross reference is used as a flag by the HL7 lower level protocol
    routine (HLLP) to determine when to start and stop logging information related to HL7 transmissions. The log can be turned on during initial testing of the HL7 link and anytime additional debugging is needed.
    The information captured by the log is stored in nodes descendant from the ^TMP("HL",ION) node, where ION is the name of the DHCP device that is specified as the HL7 Device in field 6 of the HL7 Non-DHCP Application
    Parameter file.
7 HL7 VERSION NUMBER 0;7 POINTER TO HL7 VERSION FILE (#771.5)
************************REQUIRED FIELD************************
HL7 VERSION(#771.5)

  • LAST EDITED:  SEP 30, 1991
  • HELP-PROMPT:  This is the version of the HL7 interface that the sending and receiving applications are using.
  • DESCRIPTION:  
    This is the version of the HL7 interface that the sending and receiving applications are using.
8 DHCP APPLICATION 0;8 POINTER TO HL7 APPLICATION PARAMETER FILE (#771)
************************REQUIRED FIELD************************
HL7 APPLICATION PARAMETER(#771)

  • LAST EDITED:  MAR 11, 1992
  • HELP-PROMPT:  This is the DHCP application related to this non-DHCP application entry.
  • DESCRIPTION:  
    This is the DHCP application related to this non-DHCP application entry.
  • CROSS-REFERENCE:  770^AG
    1)= S ^HL(770,"AG",$E(X,1,30),DA)=""
    2)= K ^HL(770,"AG",$E(X,1,30),DA)
    Regular cross-reference for relating DHCP applications to non-DHCP applications.
9 LOWER LEVEL PROTOCOL TIMEOUT 0;9 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>60)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  NOV 25, 1991
  • HELP-PROMPT:  The 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.
  • DESCRIPTION:  
    The 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.
10 MAIL GROUP 0;10 POINTER TO MAIL GROUP FILE (#3.8) MAIL GROUP(#3.8)

  • INPUT TRANSFORM:  I $P(^HL(770,DA,0),"^",6)]"" K X D EN^DDIOL("You are not allowed to enter a value in both the Device and Mail Group fields.")
  • LAST EDITED:  JAN 04, 1995
  • HELP-PROMPT:  Enter the name of the mail group from the MailMan Mail Group file to which HL7 messages for this non-DHCP application should be sent. Answer must be 3-30 characters in length.
  • DESCRIPTION:  NOTE: 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
11 TRANSMISSION TIME 0;11 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<4)!'(X?4N!(X>2400)) X
  • LAST EDITED:  NOV 25, 1991
  • HELP-PROMPT:  The time that transmissions to the non-DHCP application should occur expressed in 24 hour notation (i.e., 0001 to 2400). Answer must be 4 characters in length.
  • DESCRIPTION:  
    The time that transmissions to the non-DHCP application should occur expressed in 24 hour notation (i.e., 0001 to 2400).
12 RELATED FILE 771 ENTRY 0;12 POINTER TO HL7 APPLICATION PARAMETER FILE (#771)
************************REQUIRED FIELD************************
HL7 APPLICATION PARAMETER(#771)

  • LAST EDITED:  JAN 10, 1995
  • HELP-PROMPT:  A link to the application entry in file 771. All entries in file 770 must also be in file 771.
  • DESCRIPTION:  
    This field links entries in file 770 to corresponding entries in file 771.
13 LAST TRANSMISSION DATE/TIME 0;13 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  NOV 25, 1991
  • HELP-PROMPT:  The date and time of the last transmission to this non-DHCP application.
  • DESCRIPTION:  
    The date and time of the last transmission to this non-DHCP application.
14 HL7 PROCESSING ID 0;14 SET
  • 'D' FOR DEBUG;
  • 'P' FOR PRODUCTION;

  • LAST EDITED:  JAN 14, 1992
  • HELP-PROMPT:  The HL7 processing ID may be either 'D' for 'DEBUG' or 'P' for 'PRODUCTION'. 'DEBUG' should be used while the interface is under test.
  • DESCRIPTION:  
    The HL7 processing ID may be either 'D' for 'DEBUG' or 'P' for 'PRODUCTION'. 'DEBUG' should be used while the interface is under test.
50 START/STOP TRANSMISSION LOG LOG;1 SET
  • '1' FOR START LOG;
  • '0' FOR STOP LOG;

  • LAST EDITED:  SEP 26, 1991
  • HELP-PROMPT:  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.
  • DESCRIPTION:  
    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.
  • CROSS-REFERENCE:  770^ALOG^MUMPS
    1)= S:$P(^HL(770,DA,0),"^",6)]""&(X=1) ^HL(770,"ALOG",$P(^(0),"^",6),DA)=""
    2)= K:$P(^HL(770,DA,0),"^",6)]"" ^HL(770,"ALOG",$P(^(0),"^",6),DA)
    This cross reference is used in conjuntion with the 'AL' cross reference on the HL7 Device field (#6) of the HL7 Non-DHCP Application Parameter file to set/delete a flag for starting/stopping the logging of HL7
    transmission information. See the description of the 'AL' cross reference for further information.
100 PURPOSE 100;0 WORD-PROCESSING #770.01

  • DESCRIPTION:  
    This 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.
  • LAST EDITED:  MAR 25, 1993
  • HELP-PROMPT:  This field should document the purpose of this non-DHCP application parameter entry. It should describe what the application is, the type of data exchanged, reason for the exchange, etc.
  • DESCRIPTION:  
    This field should document the purpose of this non-DHCP application parameter entry. It should describe what the application is, the type of data exchanged, reason for the exchange, etc.

Found Entries, Total: 2

NAME: IVM CENTER    NAME: SR AAIS    
Info |  Desc |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All