Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^HL(771

Package: Health Level Seven

Global: ^HL(771


Information

FileMan FileNo FileMan Filename Package
771 HL7 APPLICATION PARAMETER Health Level Seven

Description

Directly Accessed By Routines, Total: 58

Package Total Routines
Health Level Seven 31 *HL7 MESSAGE    *HL7 SEGMENT    HLCHK    HLCS2    HLCSHDR4    HLCSRPT    HLCSRPT1    HLCSRPT2
HLCSRPT3    HLCSRPT5    HLEMU    HLERCHK    HLFNC1    HLFNC2    HLPA108A    HLPAT54
HLPAT96A    HLPOST16    HLSUB    HLTF1    HLTP    HLTP1    HLTP3    HLTPCK1A
^HL(772    HLTPCK2A    HLTPCK2B    HLTRANS    HLUTIL2    ^HL(770    ^HL(771    
Surgery 7 SR122PST    SRHLMFN    SRHLOORU    SRHLPOST    SRHLVOOR    SRHLVZIU    SRHLZIU    
Radiology Nuclear Medicine 5 RA25PRE1    RAAIPST1    RAHLRU    RAIPST13    RAIPST4    
IHS Support HL7 Interfaces 3 BHLBPS    BHLRXPS1    BHLRXPS2    
Registration 3 DGQEPST1    DGV53PTE    VAFHUTL    
Scheduling 3 SCMSP1    SD290P    SD53P177    
IHS RPMS CHR System 2 BCHPOS1    BCHPOS2    
Automated Lab Instruments 1 LA7POST    
Controlled Substances 1 PSDHLK    
Kernel 1 XPDIA1    
Lab Service 1 LR175P    

Accessed By FileMan Db Calls, Total: 31

Package Total Routines
Radiology Nuclear Medicine 7 RA84POS    RAHLEX    RAHLRPC    RAHLRPTT    RAHLRS1    RAIPST4    RAMAGHL    
Registration 7 DG53190T    DG53484P    DGQEPST1    DGRUDYN    DGV53PTE    VAFHPOST    VAFHUTL    
Scheduling 6 SCMSPU1    SD53142    SD53239P    SD53441A    SD53P210    SD53P212    
Automated Lab Instruments 4 LA67    LA68    LA7POST    LA7VSTP    
Controlled Substances 2 PSDHL7    PSDHLK    
Health Level Seven 2 HLPOST16    HLUOPT    
IHS RPMS CHR System 1 BCHPOS1    
IHS Support HL7 Interfaces 1 BHLRXPS1    
Surgery 1 SRHLPOST    

Pointed To By FileMan Files, Total: 13

Package Total FileMan Files
Health Level Seven 6 HL7 NON-DHCP APPLICATION PARAMETER(#770)[812]    HL7 FIELD(#771.1)[#771.113(.01)]    HL7 MESSAGE TEXT(#772)[23]    HL7 MONITOR EVENTS PROFILE(#776.5)[#776.53(.01)]    HL7 MESSAGE ADMINISTRATION(#773)[1314]    SUBSCRIPTION CONTROL(#774)[#774.01(1)]    
Radiology Nuclear Medicine 4 RAD/NUC MED DIVISION(#79)[#79.02(.01)]    HL7 MESSAGE EXCEPTIONS(#79.3)[.02]    RAD/NUC MED HL7 APPLICATION EXCEPTION(#79.7)[.01]    RAD/NUC MED REPORTS(#74)[9.3]    
Registration 2 ADT/HL7 TRANSMISSION(#39.4)[.06]    ADT/HL7 EVENT REASON(#391.72)[.02]    
Kernel 1 PROTOCOL(#101)[770.1770.2]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Health Level Seven 3 HL7 MESSAGE TYPE(#771.2)[#771.06(.01)]    HL7 SEGMENT TYPE(#771.3)[#771.05(.01)]    COUNTRY CODE(#779.004)[7]    
MailMan 1 MAIL GROUP(#3.8)[4]    

Fields, Total: 9

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)>120!($L(X)<3)!'(X'?1P.E) X I $D(X),$D(^HL(771,"B",X)) K X D EN^DDIOL("Sorry, Application names must be unique.")
  • LAST EDITED:  MAR 02, 2004
  • HELP-PROMPT:  The 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.
  • DESCRIPTION:  
    The 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  771^B
    1)= S ^HL(771,"B",$E(X,1,30),DA)=""
    2)= K ^HL(771,"B",$E(X,1,30),DA)
    Regular 'B' cross reference.
  • CROSS-REFERENCE:  771^AC^MUMPS
    1)= S:$P(^HL(771,DA,0),"^",2)]"" ^HL(771,"AF",X,$P(^(0),"^",2),DA)=""
    2)= K:$P(^HL(771,DA,0),"^",2)]"" ^HL(771,"AF",X,$P(^(0),"^",2),DA)
    This cross reference is used in conjunction with the 'AF' cross reference on the Active/Inactive field (#2) to determine whether a specific Application is active.
2 ACTIVE/INACTIVE 0;2 SET
  • 'a' FOR ACTIVE;
  • 'i' FOR INACTIVE;

  • LAST EDITED:  SEP 25, 1991
  • HELP-PROMPT:  This field indicates whether the DHCP application is currently active. A DHCP application should be inactivated when application updates are taking place.
  • DESCRIPTION:  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.
  • CROSS-REFERENCE:  771^AF^MUMPS
    1)= S ^HL(771,"AF",$P(^HL(771,DA,0),"^"),X,DA)=""
    2)= K ^HL(771,"AF",$P(^HL(771,DA,0),"^"),X,DA)
    This cross reference is used in conjunction with the 'AC' cross reference on the Name field (#.01) to determine whether a specific DHCP Application is active.
3 FACILITY NAME 0;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>80!($L(X)<1) X
  • LAST EDITED:  MAR 02, 2004
  • HELP-PROMPT:  Answer must be 1-80 characters in length
  • DESCRIPTION:  This 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.
4 MAIL GROUP 0;4 POINTER TO MAIL GROUP FILE (#3.8) MAIL GROUP(#3.8)

  • LAST EDITED:  JUL 08, 1994
  • HELP-PROMPT:  The mail group related to this application to which notifications will be sent should problems arise with delivering messages.
  • DESCRIPTION:  
    Vista 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 SEGMENT SEG;0 POINTER Multiple #771.05 771.05

  • LAST EDITED:  JUL 07, 1999
  • DESCRIPTION:  
    This is applicable to HL7 v1.5 interfaces only. Enter the HL7 segments used by the Vista application.
6 *HL7 MESSAGE MSG;0 POINTER Multiple #771.06 771.06

  • LAST EDITED:  JUL 07, 1999
  • DESCRIPTION:  
    This is applicable only to HL7 v1.5 interfaces. Enter the HL7 messages used by the DHCP application.
7 COUNTRY CODE 0;7 POINTER TO COUNTRY CODE FILE (#779.004) COUNTRY CODE(#779.004)

  • LAST EDITED:  SEP 28, 1994
  • HELP-PROMPT:  The country code applicable to this application.
  • DESCRIPTION:  
    Enter the country code associated with this application.
100 HL7 FIELD SEPARATOR FS;E1,2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>1!($L(X)<1)!'(X?1P) X S HLEC=$G(^HL(771,DA,"EC")) I HLEC]"",HLEC[X K X
  • LAST EDITED:  APR 18, 2000
  • HELP-PROMPT:  The HL7 field separator used by the DHCP application. If this field is not filled in, the uparrow (^) character is defaulted to as the field separator. Answer must be 1 character in length.
  • DESCRIPTION:  The 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
101 HL7 ENCODING CHARACTERS EC;E1,4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<1)!'(X?1.4P) X S HLFS=$G(^HL(771,DA,"FS")) S:HLFS="" HLFS="^" I X[HLFS K X
  • LAST EDITED:  APR 18, 2000
  • HELP-PROMPT:  The HL7 encoding characters used by the DHCP application. If this field is not filled in, the characters ~|\& are used as the default encoding characters. Answer must be 1-4 characters in length.
  • DESCRIPTION:  If 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER

Found Entries, Total: 60

NAME: AAC    NAME: DG HOME TELEHEALTH    NAME: DGMST HL7 EVENT    NAME: DGQE DATACARD    NAME: DGQE VIC EVENTS    NAME: DGRO-QRY    NAME: DGRO-QRYRESP    NAME: DGRU RAI CLIENT    
NAME: DGRU RAI EVENTS    NAME: GMRA VDEF IE SIDE    NAME: GMRV VDEF IE SIDE    NAME: HDRADAS    NAME: HDRADRA    NAME: HDRALGY    NAME: HDRVTLS    NAME: HTAPPL    
NAME: IHS    NAME: LA7HDR    NAME: LA7LAB    NAME: LA7POC1    NAME: LA7POC2    NAME: LA7POC3    NAME: LA7POC4    NAME: LA7POC5    
NAME: NPI FSC    NAME: NPI VISTA    NAME: OR RDI RECEIVER    NAME: OR RDI SENDER    NAME: PCMM    NAME: PCMM-515    NAME: PSO DISPENSE    NAME: PSO VISTA    
NAME: PSS DISPENSE    NAME: PSS VISTA    NAME: PSU NAT SITE    NAME: PSU-SITE    NAME: PXRM7-REM-COM    NAME: QUEST    NAME: RA-SCIMAGE-TCP    NAME: SD ENC PERF MON    
NAME: SD-AAC-PAIT    NAME: SD-SITE-PAIT    NAME: TIUHL7 EX RECEIVING APP    NAME: TIUHL7 EX SENDING APP    NAME: VAFC PIMS    NAME: VAFC TRIGGER    NAME: VAFCHL7TEMPLATE    NAME: VAFH PIMS    
NAME: VAFHL7 TEMPLATE    NAME: VETS DATA    NAME: VETS MD5    NAME: VETS UPDATE    NAME: XUMF 04 MFK    NAME: XUMF 04 MFN    NAME: XUMF 04 MFQ    NAME: XUMF 04 MFR    
NAME: XUMF DATA    NAME: XUMF MD5    NAME: XUMF UPDATE    NAME: XUPS APP    

ICR, Total: 9

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #1937
  • EVENT CAPTURE
  • MAIL GROUP (4).
    Access: Direct Global Read & w/Fileman

    ICR #2342
  • SURGERY
  • ACTIVE/INACTIVE (2).
    Access: Direct Global Read & w/Fileman

    ICR #2900
  • SCHEDULING
  • FACILITY NAME (3).
    Access: Write w/Fileman

    ICR #3036
  • Clinical Information Resource Network
  • NAME (.01).
    Access: Read w/Fileman

    ICR #4861
  • REGISTRATION
  • INTEGRATED BILLING
  • NAME (.01).
    Access: Direct Global Read & w/Fileman

    FACILITY NAME (3).
    Access: Write w/Fileman

    ICR #4918
  • SURGERY
  • NAME (.01).
    Access: Read w/Fileman

    FACILITY NAME (3).
    Access: Write w/Fileman

    ICR #5632
  • RADIOLOGY/NUCLEAR MEDICINE
  • NAME (.01).
    Access: Read w/Fileman

    ICR #6598
  • ADVANCED PROSTHETICS ACQUISITION TOOL
  • NAME (.01).
    Access: Read w/Fileman

    ACTIVE/INACTIVE (2).
    Access: Read w/Fileman

    ICR #10136

    External References

    Name Field # of Occurrence
    EN^DDIOL .01+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^HL(771 - [#771] .01+1, .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), 2(XREF 1S), 2(XREF 1K), 100+1, 101+1

    Naked Globals

    Name Field # of Occurrence
    ^(0 .01(XREF 2S), .01(XREF 2K)

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> DA .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), 2(XREF 1S), 2(XREF 1K), 100+1, 101+1
    >> DIC IDW+1
    >> HLEC 100+1*
    >> HLFS 101+1*
    X .01+1!, .01(XREF 1S), .01(XREF 1K), .01(XREF 2S), .01(XREF 2K), 2(XREF 1S), 2(XREF 1K), 3+1!, 100+1!, 101+1!
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All