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(772

Package: Health Level Seven

Global: ^HL(772


Information

FileMan FileNo FileMan Filename Package
772 HL7 MESSAGE TEXT Health Level Seven

Description

Directly Accessed By Routines, Total: 101

Package Total Routines
Health Level Seven 62 HLCIRN    HLCS    HLCSAS1    HLCSHDR    HLCSHDR1    HLCSHDR3    HLCSHDR4    HLCSHDR6
HLCSOUT    HLCSRPT    HLCSRPT1    HLCSRPT2    HLCSRPT3    HLCSRPT4    HLCSRPT5    HLCSTCP1
HLCSTCP2    HLCSTCP4    HLCSUTL    HLDIE    HLDIE772    HLEVSRV0    HLEVUTI0    HLEVUTI3
HLFNC1    HLLP    HLMA    HLMA1    HLMA2    HLMSG    HLOAPI7    HLP109
HLPAT19    HLPOST16    HLPRE16    HLQPURGE    HLTF    HLTF0    HLTF1    HLTF2
HLTP0    HLTP1    HLTP3    HLTP4    HLTPCK1A    HLTPCK2B    HLUCM    HLUCM001
HLUCM002    HLUCM003    HLUCM009    HLUCM050    HLUCM090    HLUOPT1    HLUOPT2    HLUOPT3
HLUOPT6    HLUOPTF1    HLUTIL2    HLUTIL3    HLUTIL4    ^HL(772    
Income Verification Match 6 IVM16PM    IVM2078P    IVMPREC1    IVMPRECZ    IVMPTRN4    IVMUCHK    
Scheduling 5 SD53142    SD53239P    SD53293    SD5370PT    SDPMHLA    
Registration 4 DG NPTF TOTALS    DGPFHLUT    DGRUUTL1    VAFHUTL9    
Clinical Information Resource Network 3 RGMTHL2    RGMTHLDB    RGMTHLPD    
Automated Medical Information Exchange 2 DVBCHLQ    DVBCHLR    
Clinical Procedures 2 MDCPHL7B    MDHL7U3    
Radiology Nuclear Medicine 2 RAHLBKVQ    RAHLBKVR    
Surgery 2 SRHLVORU    SRHLVQRY    
Automated Lab Instruments 1 LA7HL7    
Barcode Medication Administration 1 ALPBELOG    
Clinical Reminders 1 PXRM7API    
Controlled Substances 1 PSDFT    
E Claims Management Engine 1 BPSJACK    
VistA System Monitor 1 KMPVVHLM    

Accessed By FileMan Db Calls, Total: 14

Package Total Routines
Health Level Seven 5 HLCSTCP1    HLPOST16    HLTF    HLTF0    HLUOPT    
Scheduling 4 SD53142    SD53239P    SD53293    SD5370PT    
Clinical Reminders 1 PXRM7API    
Income Verification Match 1 IVMPREC1    
Lab Service 1 LREPIAK    
Mental Health 1 YTQHL7    
Registration 1 DGRUHL1    

Pointed To By FileMan Files, Total: 5

Package Total FileMan Files
Health Level Seven 2 HL7 MESSAGE TEXT(#772)[78]    HL7 MESSAGE ADMINISTRATION(#773)[.01]    
Auto Replenishment Ward Stock 1 PADE OUTBOUND MESSAGES(#58.72)[17]    
Clinical Procedures 1 CP_HL7_LOG(#704.002)[.05]    
Integrated Billing 1 PFSS ACCOUNT(#375)[#375.099(.04)]    

Pointer To FileMan Files, Total: 6

Package Total FileMan Files
Health Level Seven 5 HL7 APPLICATION PARAMETER(#771)[23]    HL7 MESSAGE STATUS(#771.6)[20]    HL7 ERROR MESSAGE(#771.7)[23]    HL7 MESSAGE TEXT(#772)[78]    HL LOGICAL LINK(#870)[11]    
Kernel 1 PROTOCOL(#101)[10]    

Fields, Total: 26

Field # Name Loc Type Details
.01 DATE/TIME ENTERED 0;1 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  APR 16, 1998
  • DESCRIPTION:  
    The Date/Time the message was created.
  • CROSS-REFERENCE:  772^B
    1)= S ^HL(772,"B",$E(X,1,30),DA)=""
    2)= K ^HL(772,"B",$E(X,1,30),DA)
    Regular 'B' cross reference.
2 SERVER APPLICATION 0;2 POINTER TO HL7 APPLICATION PARAMETER FILE (#771)
************************REQUIRED FIELD************************
HL7 APPLICATION PARAMETER(#771)

  • LAST EDITED:  JUL 07, 1994
  • HELP-PROMPT:  The server application related to this transmission.
  • DESCRIPTION:  
    The DHCP application related to this transmission.
2.02 FAST PURGE DT/TM 2;2 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:X<1 X
  • LAST EDITED:  SEP 24, 2003
  • HELP-PROMPT:  Enter the date and time at which the record may be purged.
  • FIELD INDEX:  AJ (#345) MUMPS ACTION
    Short Descr:  Removes the record from the AI x-ref if the Fast Purge Date/Time is edited
    Set Logic:  Q
    Kill Logic:  K:$G(X1(1)) ^HLMA("AI",X1(1),772,+$G(DA))
    X(1):  FAST PURGE DT/TM  (772,2.02)  (Subscr 1)  (forwards)
3 CLIENT APPLICATION 0;3 POINTER TO HL7 APPLICATION PARAMETER FILE (#771)
************************REQUIRED FIELD************************
HL7 APPLICATION PARAMETER(#771)

  • LAST EDITED:  OCT 03, 1995
  • HELP-PROMPT:  The client application related to this transmission.
  • DESCRIPTION:  
    The client application related to this transmission.
  • CROSS-REFERENCE:  772^AE^MUMPS
    1)= N HLX0,HLXP S HLXP=$G(^HL(772,DA,"P")),HLX0=$G(^(0)) S:'$P(HLXP,"^",2)&($P(HLX0,"^",4)="O") ^HL(772,"AC","O",X,DA)=""
    2)= N HLX0 S HLX0=$G(^HL(772,DA,0)) K:$P(HLX0,"^",4)="O" ^HL(772,"AC","O",X,DA)
    3)= Required to determine outgoing transmissions that need to be transmitted.
    This cross reference is used in conjunction with the 'AC' cross reference on the Transmission Type field (#4) and the 'AD' cross reference on the Date/Time Processed field (#21) to determine outgoing transmissions for a
    specific application that need to be transmitted.
  • CROSS-REFERENCE:  772^AG^MUMPS
    1)= S:$P(^HL(772,DA,0),"^",6)]"" ^HL(772,"AH",X,$P(^(0),"^",6),DA)=""
    2)= K:$P(^HL(772,DA,0),"^",6)]"" ^HL(772,"AH",X,$P(^(0),"^",6),DA)
    3)= Required to link initial messages with acknowledgment messages.
    This cross reference is used in conjunction with the 'AH' cross reference on the Message ID field (#6) to look up and link initial HL7 messages with reply/acknowledgement messages.
4 TRANSMISSION TYPE 0;4 SET
************************REQUIRED FIELD************************
  • 'I' FOR INCOMING;
  • 'O' FOR OUTGOING;

  • LAST EDITED:  NOV 30, 1994
  • HELP-PROMPT:  The type of transmission (incoming or outgoing).
  • DESCRIPTION:  
    The type of transmission (incoming or outgoing).
  • CROSS-REFERENCE:  772^AC^MUMPS
    1)= N HLX0,HLXP S HLXP=$G(^HL(772,DA,"P")),HLX0=$G(^(0)) S:'$P(HLXP,"^",2)&($P(HLX0,"^",3))&(X="O") ^HL(772,"AC","O",$P(HLX0,"^",3),DA)=""
    2)= Q:X'="O"  N HLX0 S HLX0=$G(^HL(772,DA,0)) K:$P(HLX0,"^",3) ^HL(772,"AC","O",$P(HLX0,"^",3),DA)
    3)= Required to determine outgoing transmissions that need to be transmitted.
    This cross reference is used in conjunction with the 'AE' cross reference on the Client Application field (#3) and the 'AD' cross reference on the Date/Time Processed field (#21) to determine outgoing transmissions for a
    specific application that need to be transmitted.
5 RELATED MAILMAN MESSAGE 0;5 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<1)!'(X?1N.N) X
  • LAST EDITED:  MAY 12, 1993
  • HELP-PROMPT:  The MailMan message number related to this transmission.
  • DESCRIPTION:  
    The MailMan message number related to this transmission.
6 MESSAGE ID 0;6 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<1) X
  • LAST EDITED:  AUG 01, 2007
  • HELP-PROMPT:  Answer must be 1-60 characters in length
  • DESCRIPTION:  
    The unique ID for this HL7 message.
  • CROSS-REFERENCE:  772^AH^MUMPS
    1)= S:$P(^HL(772,DA,0),"^",3) ^HL(772,"AH",$P(^(0),"^",3),X,DA)=""
    2)= K:$P(^HL(772,DA,0),"^",3) ^HL(772,"AH",$P(^(0),"^",3),X,DA)
    This cross reference is used in conjunction with the 'AG' cross reference on the Non-DHCP Application field (#3) to look up and link initial HL7 messages with reply/acknowledgement messages.
  • FIELD INDEX:  C (#781) REGULAR IR LOOKUP & SORTING
    Short Descr:  This is a regular index of new-style cross-reference on the Message ID field
    Description:  This cross reference allows a user to look up an HL7 message by its unique message ID.
    Set Logic:  S ^HL(772,"C",$E(X,1,60),DA)=""
    Kill Logic:  K ^HL(772,"C",$E(X,1,60),DA)
    Whole Kill:  K ^HL(772,"C")
    X(1):  MESSAGE ID  (772,6)  (Subscr 1)  (Len 60)  (forwards)
7 ACKNOWLEDGMENT TO 0;7 POINTER TO HL7 MESSAGE TEXT FILE (#772) HL7 MESSAGE TEXT(#772)

  • LAST EDITED:  DEC 09, 1994
  • HELP-PROMPT:  The incoming message that this message is replying to. This field is only applicable to outgoing messages.
  • DESCRIPTION:  
    The incoming message that this message is replying to.  This field is only applicable to outgoing messages.
8 PARENT MESSAGE 0;8 POINTER TO HL7 MESSAGE TEXT FILE (#772) HL7 MESSAGE TEXT(#772)

  • LAST EDITED:  JAN 25, 1995
  • HELP-PROMPT:  The original message to which this message is related, if applicable.
  • CROSS-REFERENCE:  772^AI
    1)= S ^HL(772,"AI",$E(X,1,30),DA)=""
    2)= K ^HL(772,"AI",$E(X,1,30),DA)
    3)= This cross reference is needed by the purge utility to determine when a parent entry can be deleted.
    This cross reference is needed by the purge utility to determine when a parent entry can be deleted.  When the only entry in the cross reference is the parent (all children have been deleted), then the parent entry can be
    deleted.
9 PRIORITY 0;9 SET
************************REQUIRED FIELD************************
  • 'I' FOR IMMEDIATE;
  • 'D' FOR DEFERRED;

  • LAST EDITED:  JAN 18, 1995
  • HELP-PROMPT:  The mode in which this message will be delivered.
  • DESCRIPTION:  
    The delivery priority assigned to this message.  Either 'I' for Immediate or 'D' for Deferred.
10 RELATED EVENT PROTOCOL 0;10 POINTER TO PROTOCOL FILE (#101) PROTOCOL(#101)

  • LAST EDITED:  SEP 09, 1994
  • HELP-PROMPT:  The entry in the Protocol file related to this Message Text entry.
11 LOGICAL LINK 0;11 POINTER TO HL LOGICAL LINK FILE (#870) HL LOGICAL LINK(#870)

  • LAST EDITED:  FEB 20, 1997
  • HELP-PROMPT:  The link that will be used to exchange messages with an external application.
  • DESCRIPTION:  This is a pointer to the Logical Link file (#870). This link is used to transmit messages to an external (client) application. This field is not filled in when messages are exchanged between DHCP applications on the same
    system.
  • CROSS-REFERENCE:  772^AXMITOUT1^MUMPS
    1)= N HLXRFST,HLXRFLL S HLXRFST=+$G(^HL(772,DA,"P")),HLXRFLL=+$P($G(^HL(772,DA,0)),"^",11) Q:(('HLXRFST)!('HLXRFLL))  S HLXRFST=$P($G(^HL(771.6,HLXRFST,0)),"^",2) Q:(HLXRFST'="PT")  S ^HL(772,"A-XMIT-OUT",HLXRFLL,DA)=""
    2)= K:$D(^HL(772,"A-XMIT-OUT",X,DA)) ^HL(772,"A-XMIT-OUT",X,DA)
    This cross reference is used by the outgoing filer to find all messages with a status of 'PENDING TRANSMISSION' (CODE=PT).  The Logical Link that the message is queued for is stored in the cross reference to synchronize
    delivery of messages to their Logical Links.
    Resulting node: ^HL(772,"A-XMIT-OUT",HLXRFLL,DA)="" Where: HLXRFLL = Pointer to the Logical Link
    DA = Pointer to the message
    Notes: This cross reference is only set if the status code is 'PT'
    : This cross reference is also set by the AXMITOUT2 cross reference
    on the STATUS field (#20)
12 SECURITY 0;12 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1) X
  • LAST EDITED:  SEP 28, 1994
  • HELP-PROMPT:  The value to use in the Security field of the Message Header segment. Answer must be 1-40 characters in length.
13 CONTINUATION POINTER 1;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>180!($L(X)<1) X
  • LAST EDITED:  SEP 28, 1994
  • HELP-PROMPT:  The value to use in the Continuation Pointer field of the Message Header segment. Answer must be 1-180 characters in length.
14 MESSAGE TYPE 0;14 SET
************************REQUIRED FIELD************************
  • 'M' FOR SINGLE MESSAGE;
  • 'B' FOR BATCH OF MESSAGES;
  • 'F' FOR FILE OF BATCHES;

  • LAST EDITED:  JAN 18, 1995
  • HELP-PROMPT:  The type of message. Single, batch or file.
  • DESCRIPTION:  There are three types of messages as follows:
    M for Single message (contains only one MSH segment) B for Batch of messages (contains multiple MSH segments) F for File of batches (contains multiple BHS segments)
    This field is automatically filled in by the Messaging System and is used to determine the appropriate header segment to build for a message.
15 DON'T PURGE 2;1 SET
  • '1' FOR DON'T PURGE;
  • '0' FOR TO PURGE;

  • LAST EDITED:  JUL 28, 1997
  • HELP-PROMPT:  When this field is set to 1, the message wil never be purged by the HL7 "Purge Message Text File Entries" option.
  • DESCRIPTION:  When this field is set to 1, the message wil never be purged by the HL7 "Purge Message Text File Entries" option. However, when this field is set to 0 or is empty, the message is allowed to be purged by the HL7 "Purge
    Message Text Entries" option.
16 NAMESPACE 0;13 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<1)!'(X?1U1.3NU) X
  • LAST EDITED:  FEB 15, 2002
  • HELP-PROMPT:  Answer must be 1-4 characters in length, and start with 1 uppercase letter, followed by up to 3 uppercase letters and numerics.
  • DESCRIPTION:  This field must not be filled in manually. It will be filled in automatically by the HL7 processes that create entries in the HL7 Message Text file (#772). In most instances, applications will call GENERATE^HLMA,
    GENACK^HLMA, or DIRECT^HLMA.  When they do, they will pass by reference into the last OPTIONS (in the documentation) parameter the value of the namespace.  The value of the namespace will be in the form of
    OPTIONS("NAMESPACE")=NAMESPACE.
    Please note that the calls to the three APIs mentioned above use the variable HLP to hold the passed in by reference array.  So, in the HLMA code (and other code invoked by HLMA), the actual variable used is
    HLP("NAMESPACE").
    This field is populated by UPDATE^HLTF0.
20 STATUS P;1 POINTER TO HL7 MESSAGE STATUS FILE (#771.6)
************************REQUIRED FIELD************************
HL7 MESSAGE STATUS(#771.6)

  • LAST EDITED:  FEB 20, 1997
  • HELP-PROMPT:  The current status of the message.
  • DESCRIPTION:  
    The status currently assigned to this transmission.
  • CROSS-REFERENCE:  772^AF
    1)= S ^HL(772,"AF",$E(X,1,30),DA)=""
    2)= K ^HL(772,"AF",$E(X,1,30),DA)
    This cross reference is used to produce the Pending and Failed Transmission reports.
  • CROSS-REFERENCE:  772^AXMITOUT2^MUMPS
    1)= N HLXRFST,HLXRFLL S HLXRFST=+$G(^HL(772,DA,"P")),HLXRFLL=+$P($G(^HL(772,DA,0)),"^",11) Q:(('HLXRFST)!('HLXRFLL))  S HLXRFST=$P($G(^HL(771.6,HLXRFST,0)),"^",2) Q:(HLXRFST'="PT")  S ^HL(772,"A-XMIT-OUT",HLXRFLL,DA)=""
    2)= N HLXRFLL S HLXRFLL=+$P($G(^HL(772,DA,0)),"^",11) Q:'HLXRFLL  K:$D(^HL(772,"A-XMIT-OUT",HLXRFLL,DA)) ^HL(772,"A-XMIT-OUT",HLXRFLL,DA)
    This cross reference is used by the outgoing filer to find all messages with a status of 'PENDING TRANSMISSION' (CODE=PT).  The Logical Link that the message is queued for is stored in the cross reference to synchronize
    delivery of messages to their Logical Links.
    Resulting node: ^HL(772,"A-XMIT-OUT",HLXRFLL,DA)="" Where: HLXRFLL = Pointer to the Logical Link
    DA = Pointer to the message
    Notes: This cross reference is only set if the status code is 'PT'
    : This cross reference is also set by the AXMITOUT1 cross reference
    on the LOGICAL LINK field (#11)
21 DATE/TIME PROCESSED P;2 DATE

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  OCT 02, 1995
  • HELP-PROMPT:  The date and time this transmission was actually processed (sent or received).
  • DESCRIPTION:  
    The date and time this transmission was actually processed (sent or received).
  • CROSS-REFERENCE:  772^AD^MUMPS
    1)= N HLX0 S HLX0=$G(^HL(772,DA,0)) K:$P(HLX0,"^",3)&($P(HLX0,"^",4)="O") ^HL(772,"AC","O",$P(HLX0,"^",3),DA)
    2)= N HLX0,HLXP S HLXP=$G(^HL(772,DA,"P")),HLX0=$G(^(0)) S:'$P(HLXP,"^",2)&($P(HLX0,"^",3))&($P(HLX0,"^",4)="O") ^HL(772,"AC","O",$P(HLX0,"^",3),DA)=""
    3)= Required to determine outgoing transmissions that need to be transmitted.
    This cross reference is used in conjunction with the 'AE' cross reference on the Client Application field (#3) and the 'AC' cross reference on the Transmission Type field (#4) to determine outgoing transmissions for a
    specific application that need to be transmitted.
22 ERROR MESSAGE P;3 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>200!($L(X)<3) X
  • LAST EDITED:  NOV 18, 1991
  • HELP-PROMPT:  If there was an error in sending or receiving this transmission, this field will contain the 3-200 character error message.
  • DESCRIPTION:  
    If there was an error in sending or receiving this transmission, this field will contain the 3-200 character error message.
23 ERROR TYPE P;4 POINTER TO HL7 ERROR MESSAGE FILE (#771.7) HL7 ERROR MESSAGE(#771.7)

  • LAST EDITED:  FEB 20, 1997
  • HELP-PROMPT:  A description of the type of error that occured.
26 ACK TIMEOUT P;7 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>600)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAY 05, 2000
  • HELP-PROMPT:  Type a Number between 0 and 600, 0 Decimal Digits
  • DESCRIPTION:  
    The number of seconds the Lower Layer Protocol waits for an acknowledgement from the receiving application. This field will override the ACK TIMEOUT of the Logical Link for this message.
100 NO. OF CHARACTERS IN MESSAGE S;1 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>1000000)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  JAN 25, 1993
  • HELP-PROMPT:  Type a Number between 1 and 1000000, 0 Decimal Digits
  • DESCRIPTION:  
    A count of the total number of characters in the mail message associated with this HL7 transmission entry.
101 NO. OF EVENTS IN MESSAGE S;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>100000)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  JAN 25, 1993
  • HELP-PROMPT:  Type a Number between 1 and 100000, 0 Decimal Digits
  • DESCRIPTION:  
    A count of the total number of events (HL7 messages) contained in the mail message associated with this HL7 transmission entry.
102 TRANSMISSION TIME S;3 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 03, 1993
  • HELP-PROMPT:  The time it took to transmit this message to the primary network addressee. A number between 0 and 999999, 0 Decimal Digits.
  • DESCRIPTION:  
    The time it took to transmit this message to the primary network addressee.
200 MESSAGE TEXT IN;0 WORD-PROCESSING #772.02

  • LAST EDITED:  JUL 15, 1994
  • DESCRIPTION:  The actual text of the incoming HL7 message(s).
  • TECHNICAL DESCR:  

Found Entries, Total: 176

DATE/TIME ENTERED: 2008-05-26 00:01:00    DATE/TIME ENTERED: 2014-10-01 09:52:58    DATE/TIME ENTERED: 2014-10-01 09:52:58    DATE/TIME ENTERED: 2014-10-01 10:33:15    DATE/TIME ENTERED: 2014-10-01 10:33:15    DATE/TIME ENTERED: 2014-10-10 14:01:09    DATE/TIME ENTERED: 2014-10-10 14:01:09    DATE/TIME ENTERED: 2014-10-10 14:02:09    
DATE/TIME ENTERED: 2014-10-10 14:02:09    DATE/TIME ENTERED: 2014-10-10 14:03:10    DATE/TIME ENTERED: 2014-10-10 14:03:10    DATE/TIME ENTERED: 2014-10-10 14:04:10    DATE/TIME ENTERED: 2014-10-10 14:04:11    DATE/TIME ENTERED: 2014-10-10 14:05:11    DATE/TIME ENTERED: 2014-10-10 14:05:11    DATE/TIME ENTERED: 2014-10-10 14:06:12    
DATE/TIME ENTERED: 2014-10-10 14:06:12    DATE/TIME ENTERED: 2014-10-10 14:07:12    DATE/TIME ENTERED: 2014-10-10 14:07:12    DATE/TIME ENTERED: 2014-10-10 14:08:13    DATE/TIME ENTERED: 2014-10-10 14:08:13    DATE/TIME ENTERED: 2014-10-10 14:09:13    DATE/TIME ENTERED: 2014-10-10 14:09:13    DATE/TIME ENTERED: 2014-10-10 14:10:14    
DATE/TIME ENTERED: 2014-10-10 14:10:14    DATE/TIME ENTERED: 2014-10-16 15:08:04    DATE/TIME ENTERED: 2014-10-16 15:08:04    DATE/TIME ENTERED: 2014-10-20 12:22:25    DATE/TIME ENTERED: 2014-10-20 12:22:25    DATE/TIME ENTERED: 2014-10-20 12:32:09    DATE/TIME ENTERED: 2014-10-20 12:32:09    DATE/TIME ENTERED: 2014-10-20 15:18:03    
DATE/TIME ENTERED: 2014-10-20 15:18:03    DATE/TIME ENTERED: 2014-10-22 12:33:23    DATE/TIME ENTERED: 2014-10-22 12:33:23    DATE/TIME ENTERED: 2014-10-28 11:16:16    DATE/TIME ENTERED: 2014-10-28 11:16:16    DATE/TIME ENTERED: 2014-10-28 13:41:20    DATE/TIME ENTERED: 2014-10-28 13:41:20    DATE/TIME ENTERED: 2014-12-16 13:31:24    
DATE/TIME ENTERED: 2014-12-16 13:31:24    DATE/TIME ENTERED: 2014-12-16 13:31:24    DATE/TIME ENTERED: 2014-12-16 13:31:24    DATE/TIME ENTERED: 2014-12-18 20:45:48    DATE/TIME ENTERED: 2014-12-18 20:54:45    DATE/TIME ENTERED: 2015-03-23 12:47:26    DATE/TIME ENTERED: 2015-03-23 12:47:26    DATE/TIME ENTERED: 2015-03-23 12:47:28    
DATE/TIME ENTERED: 2015-03-23 12:47:28    DATE/TIME ENTERED: 2015-03-23 14:12:56    DATE/TIME ENTERED: 2015-03-23 14:12:56    DATE/TIME ENTERED: 2015-03-23 14:12:56    DATE/TIME ENTERED: 2015-03-23 14:12:56    DATE/TIME ENTERED: 2015-04-14 15:04:44    DATE/TIME ENTERED: 2015-04-14 15:04:44    DATE/TIME ENTERED: 2015-04-14 15:04:45    
DATE/TIME ENTERED: 2015-04-14 15:04:45    DATE/TIME ENTERED: 2015-05-12 12:22:06    DATE/TIME ENTERED: 2015-05-12 12:22:06    DATE/TIME ENTERED: 2015-05-12 12:22:06    DATE/TIME ENTERED: 2015-05-12 12:22:06    DATE/TIME ENTERED: 2015-05-13 13:05:37    DATE/TIME ENTERED: 2015-05-13 13:05:37    DATE/TIME ENTERED: 2015-05-13 13:05:37    
DATE/TIME ENTERED: 2015-05-13 13:05:37    DATE/TIME ENTERED: 2015-05-13 14:39:12    DATE/TIME ENTERED: 2015-05-13 14:39:12    DATE/TIME ENTERED: 2015-05-13 14:39:12    DATE/TIME ENTERED: 2015-05-13 14:39:12    DATE/TIME ENTERED: 2015-05-21 17:37:14    DATE/TIME ENTERED: 2015-05-21 17:37:14    DATE/TIME ENTERED: 2015-05-21 17:37:15    
DATE/TIME ENTERED: 2015-05-21 17:37:15    DATE/TIME ENTERED: 2015-05-29 17:13:49    DATE/TIME ENTERED: 2015-05-29 17:13:49    DATE/TIME ENTERED: 2015-05-29 17:13:49    DATE/TIME ENTERED: 2015-05-29 17:13:49    DATE/TIME ENTERED: 2015-06-30 14:16:10    DATE/TIME ENTERED: 2015-06-30 14:24:32    DATE/TIME ENTERED: 2015-07-24 15:05:57    
DATE/TIME ENTERED: 2015-07-24 15:05:57    DATE/TIME ENTERED: 2015-07-24 15:05:57    DATE/TIME ENTERED: 2015-07-24 15:05:57    DATE/TIME ENTERED: 2015-07-24 15:05:57    DATE/TIME ENTERED: 2015-07-24 15:05:57    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    
DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2015-07-24 15:05:58    
DATE/TIME ENTERED: 2015-07-24 15:05:58    DATE/TIME ENTERED: 2016-01-01 19:48:54    DATE/TIME ENTERED: 2016-01-01 19:49:46    DATE/TIME ENTERED: 2016-04-16 05:36:38    DATE/TIME ENTERED: 2016-04-16 05:37:40    DATE/TIME ENTERED: 2016-06-10 23:19:23    DATE/TIME ENTERED: 2016-06-10 23:22:14    DATE/TIME ENTERED: 2016-06-27 05:53:44    
DATE/TIME ENTERED: 2016-06-27 05:53:44    DATE/TIME ENTERED: 2016-08-13 08:31:06    DATE/TIME ENTERED: 2016-08-13 08:52:15    DATE/TIME ENTERED: 2016-09-16 13:33:24    DATE/TIME ENTERED: 2016-09-26 07:40:19    DATE/TIME ENTERED: 2016-09-26 07:42:02    DATE/TIME ENTERED: 2016-10-27 03:35:02    DATE/TIME ENTERED: 2016-10-27 03:46:44    
DATE/TIME ENTERED: 2016-10-27 20:31:05    DATE/TIME ENTERED: 2016-10-27 20:41:24    DATE/TIME ENTERED: 2016-10-31 08:09:27    DATE/TIME ENTERED: 2016-10-31 08:20:53    DATE/TIME ENTERED: 2016-11-12 08:31:22    DATE/TIME ENTERED: 2016-11-12 08:56:25    DATE/TIME ENTERED: 2017-01-09 06:00:30    DATE/TIME ENTERED: 2017-01-09 06:01:05    
DATE/TIME ENTERED: 2017-02-17 01:44:51    DATE/TIME ENTERED: 2017-02-17 13:49:40    DATE/TIME ENTERED: 2017-02-26 12:54:07    DATE/TIME ENTERED: 2017-02-26 12:54:38    DATE/TIME ENTERED: 2017-04-18 21:42:37    DATE/TIME ENTERED: 2017-04-18 21:45:44    DATE/TIME ENTERED: 2017-06-19 20:51:30    DATE/TIME ENTERED: 2017-06-19 20:56:33    
DATE/TIME ENTERED: 2017-07-26 13:04:10    DATE/TIME ENTERED: 2017-07-26 13:04:55    DATE/TIME ENTERED: 2017-07-26 13:07:05    DATE/TIME ENTERED: 2017-08-12 08:03:10    DATE/TIME ENTERED: 2017-08-12 08:33:48    DATE/TIME ENTERED: 2017-09-19 01:22:02    DATE/TIME ENTERED: 2017-09-19 01:22:04    DATE/TIME ENTERED: 2017-11-20 00:48:05    
DATE/TIME ENTERED: 2017-11-20 00:49:02    DATE/TIME ENTERED: 2017-12-18 19:21:51    DATE/TIME ENTERED: 2017-12-19 15:19:31    DATE/TIME ENTERED: 2017-12-31 05:08:55    DATE/TIME ENTERED: 2017-12-31 05:10:38    DATE/TIME ENTERED: 2018-02-10 09:24:52    DATE/TIME ENTERED: 2018-02-10 09:52:29    DATE/TIME ENTERED: 2018-03-16 15:35:12    
DATE/TIME ENTERED: 2018-03-16 15:44:44    DATE/TIME ENTERED: 2018-04-02 23:11:20    DATE/TIME ENTERED: 2018-04-21 16:32:06    DATE/TIME ENTERED: 2018-04-21 16:36:35    DATE/TIME ENTERED: 2018-06-02 11:50:20    DATE/TIME ENTERED: 2018-06-02 11:50:50    DATE/TIME ENTERED: 2018-06-02 11:54:39    DATE/TIME ENTERED: 2018-06-18 19:58:33    
DATE/TIME ENTERED: 2018-07-06 15:24:02    DATE/TIME ENTERED: 2018-07-06 15:24:43    DATE/TIME ENTERED: 2018-07-06 15:27:08    DATE/TIME ENTERED: 2018-07-17 06:10:52    DATE/TIME ENTERED: 2018-07-17 06:11:38    DATE/TIME ENTERED: 2018-07-17 06:11:40    DATE/TIME ENTERED: 2018-09-07 22:48:46    DATE/TIME ENTERED: 2018-09-07 22:48:48    
DATE/TIME ENTERED: 2018-09-07 22:50:34    DATE/TIME ENTERED: 2018-10-13 22:58:03    DATE/TIME ENTERED: 2018-10-13 23:00:58    DATE/TIME ENTERED: 2018-10-13 23:01:50    DATE/TIME ENTERED: 2018-12-07 02:19:55    DATE/TIME ENTERED: 2018-12-07 02:20:33    DATE/TIME ENTERED: 2018-12-07 02:22:47    DATE/TIME ENTERED: 2019-02-02 15:45:21    
DATE/TIME ENTERED: 2019-02-02 15:45:22    DATE/TIME ENTERED: 2019-02-02 15:46:26    DATE/TIME ENTERED: 2019-04-13 09:04:39    DATE/TIME ENTERED: 2019-04-13 09:31:33    DATE/TIME ENTERED: 2019-04-13 09:33:03    DATE/TIME ENTERED: 2019-05-30 18:40:19    DATE/TIME ENTERED: 2019-05-30 18:42:32    DATE/TIME ENTERED: 2019-05-30 18:43:43    

ICR, Total: 12

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #940
  • INCOME VERIFICATION MATCH
  • RELATED MAILMAN MESSAGE (.05).
    Access: Direct Global Read & w/Fileman

    The purpose of using the C cross-reference is to findthe internal entry number of a specific HL7 outgoing transmission, by usingthe Message Control ID. The Message Control ID of that transmission is storedin an IVM file.The purpose of accessing the associated Mailman messagenumber for an outgoing HL7 transmission is to determine, using a function callto VA MailMan, if that message is Awaiting Transmission.
    ICR #1339
  • RADIOLOGY/NUCLEAR MEDICINE
  • DATE/TIME ENTERED (.01).
    Access: Direct Global Read & w/Fileman

    ICR #1939
  • EVENT CAPTURE
  • MESSAGE TEXT (200).
    Access: Direct Global Read & w/Fileman

    ICR #2488
  • LAB SERVICE
  • STATUS (20).
    Access: Direct Global Read & w/Fileman

    ICR #2506
  • LAB SERVICE
  • MESSAGE TEXT (200).
    Access: Direct Global Read & w/Fileman

    ICR #3464
  • Clinical Information Resource Network
  • Master Patient Index VistA
  • MESSAGE TEXT (200).
    Access: Direct Global Read & w/Fileman

    DATE/TIME ENTERED (.01).
    Access: Direct Global Read & w/Fileman

    TRANSMISSION TYPE (4).
    Access: Direct Global Read & w/Fileman

    RELATED EVENT PROTOCOL (10).
    Access: Direct Global Read & w/Fileman

    STATUS (20).
    Access: Direct Global Read & w/Fileman

    DATE/TIME PROCESSED (21).
    Access: Direct Global Read & w/Fileman

    "B" CROSS REFERENCEFrom the message text multiple, examine the following segments.From the PID segment, get the ICN and the patient DFN.From the QAK segment, get the patient DFN.From the RDT segment, get the ICN.From the VTQ segment, get the SSN.From the MFE segment, for MAD or MUP, get the ICN.
    ICR #4069
  • IFCAP
  • INCOME VERIFICATION MATCH
  • RADIOLOGY/NUCLEAR MEDICINE
  • EVENT CAPTURE
  • Clinical Information Resource Network
  • LAB SERVICE
  • DSS EXTRACTS
  • E Claims Management Engine
  • CONSULT/REQUEST TRACKING
  • DATE/TIME ENTERED (.01).
    Access: Direct Global Read & w/Fileman

    TRANSMISSION TYPE (4).
    Access: Direct Global Read & w/Fileman

    RELATED MAILMAN MESSAGE (5).
    Access: Direct Global Read & w/Fileman

    RELATED EVENT PROTOCOL (10).
    Access: Direct Global Read & w/Fileman

    STATUS (20).
    Access: Direct Global Read & w/Fileman

    DATE/TIME PROCESSED (21).
    Access: Direct Global Read & w/Fileman

    MESSAGE TEXT (200).
    Access: Direct Global Read & w/Fileman

    Direct global read access to "B" x-ref.
    ICR #4564
  • CLINICAL REMINDERS
  • REGISTRATION
  • STATUS (20).
    Access: Read w/Fileman

    This is the "C" index on the 772 file that allows a userto look up a HL7 message by its unique message ID.This is the file node on which the STATUS field islocated.
    ICR #4739
  • INTEGRATED BILLING
  • DATE/TIME ENTERED (.01).
    Access: Pointed to

    ICR #4917 MESSAGE TEXT (200).
    Access: Read w/Fileman

    ICR #6877
  • VISTA SYSTEM MONITOR
  • DATE/TIME ENTERED (.01).
    Access: Direct Global Read & w/Fileman

    RELATED EVENT PROTOCOL (10).
    Access: Direct Global Read & w/Fileman

    PARENT MESSAGE (8).
    Access: Direct Global Read & w/Fileman

    NAMESPACE (16).
    Access: Direct Global Read & w/Fileman

    NO. OF CHARACTERS IN MESSAGE (100).
    Access: Direct Global Read & w/Fileman

    NO. OF EVENTS IN MESSAGE (101).
    Access: Direct Global Read & w/Fileman

    TRANSMISSION TIME (102).
    Access: Direct Global Read & w/Fileman

    Direct global read access to "B" x-ref.
    ICR #10138 INCOMING MESSAGE TEXT (200).
    Access: Read w/Fileman

    External References

    Name Field # of Occurrence
    ^%DT .01+1, 2.02+1, 21+1
    Y^DIQ ID2+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^DD(771 ID2+1
    ^HL(771 - [#771] ID2+1
    ^HL(771.6 - [#771.6] 11(XREF 1S), 20(XREF 2S)
    ^HL(772 - [#772] IXCSL+1*, IXCKL+1!, IXCKEIC+1!, .01(XREF 1S), .01(XREF 1K), 3(XREF 1S), 3(XREF 1K), 3(XREF 2S), 3(XREF 2K), 4(XREF 1S)
    4(XREF 1K), 6(XREF 2S), 6(XREF 2K), 8(XREF 1S), 8(XREF 1K), 11(XREF 1S), 11(XREF 1K), 20(XREF 1S), 20(XREF 1K), 20(XREF 2S)
    20(XREF 2K), 21(XREF 1S), 21(XREF 1K)
    ^HLMA("AI" IXAJKL+1!

    Naked Globals

    Name Field # of Occurrence
    ^(0 ID2+1, 3(XREF 1S), 3(XREF 2S), 3(XREF 2K), 4(XREF 1S), 6(XREF 2S), 6(XREF 2K), 21(XREF 1K)

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> %DT .01+1*, 2.02+1*, 21+1*
    %I ID2+1*!
    >> C ID2+1*
    >> DA IXAJKL+1, IXCSL+1, IXCKL+1, .01(XREF 1S), .01(XREF 1K), 3(XREF 1S), 3(XREF 1K), 3(XREF 2S), 3(XREF 2K), 4(XREF 1S)
    4(XREF 1K), 6(XREF 2S), 6(XREF 2K), 8(XREF 1S), 8(XREF 1K), 11(XREF 1S), 11(XREF 1K), 20(XREF 1S), 20(XREF 1K), 20(XREF 2S)
    20(XREF 2K), 21(XREF 1S), 21(XREF 1K)
    >> DIC ID2+1
    HLX0 3(XREF 1S), 3(XREF 1K), 4(XREF 1S), 4(XREF 1K), 21(XREF 1S), 21(XREF 1K)
    HLXP 3(XREF 1S), 4(XREF 1S), 21(XREF 1K)
    HLXRFLL 11(XREF 1S), 20(XREF 2S), 20(XREF 2K)
    HLXRFST 11(XREF 1S), 20(XREF 2S)
    U ID2+1
    X IXCSL+1, IXCKL+1, .01+1*!, .01(XREF 1S), .01(XREF 1K), 2.02+1*!, 3(XREF 1S), 3(XREF 1K), 3(XREF 2S), 3(XREF 2K)
    4(XREF 1S), 4(XREF 1K), 5+1!, 6+1!, 6(XREF 2S), 6(XREF 2K), 8(XREF 1S), 8(XREF 1K), 11(XREF 1K), 12+1!
    , 13+1!, 16+1!, 20(XREF 1S), 20(XREF 1K), 21+1*!, 22+1!, 26+1!, 100+1!, 101+1!, 102+1!
    >> X1(1 IXAJKL+1
    >> Y ID2+1*, .01+1, 2.02+1, 21+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