Print Page as PDF
HL7 MESSAGE TEXT FILE (#772) ICR (4069)

HL7 MESSAGE TEXT FILE (#772)    ICR (4069)

Name Value
NUMBER 4069
IA # 4069
FILE NUMBER 772
GLOBAL ROOT HL(772,
DATE CREATED 2003/04/01
CUSTODIAL PACKAGE HEALTH LEVEL SEVEN
CUSTODIAL ISC San Francisco
USAGE Controlled Subscription
TYPE File
DBIC APPROVAL STATUS APPROVED
NAME HL7 MESSAGE TEXT FILE (#772)
GENERAL DESCRIPTION
This integration agreement will be used for all
references to all structures in the HL7 Message Text File (#772) file.  Each
reference by package is included in the SUBSCRIBING DETAILS for each
subscribing package.

As new requests to this file are received and accepted by the VistA HL7
development staff, this integration agreement will be updated.
GLOBAL REFERENCE
GLOBAL REFERENCE FIELD NUMBER GLOBAL DESCRIPTION
HL(772,
FIELD NUMBER ACCESS FIELD NAME LOCATION
.01 Direct Global Read & w/Fileman DATE/TIME ENTERED 0;1
4 Direct Global Read & w/Fileman TRANSMISSION TYPE 0;4
5 Direct Global Read & w/Fileman RELATED MAILMAN MESSAGE 0;5
10 Direct Global Read & w/Fileman RELATED EVENT PROTOCOL 0;10
20 Direct Global Read & w/Fileman STATUS P;1
21 Direct Global Read & w/Fileman DATE/TIME PROCESSED P;2
200 Direct Global Read & w/Fileman MESSAGE TEXT IN;D1;0
HL(772,"B",
Direct global read access to "B" x-ref.
STATUS Active
DURATION Till Otherwise Agreed
ID HL(772,
SUBSCRIBING PACKAGE
SUBSCRIBING PACKAGE SUBSCRIBING DETAILS
IFCAP
Access to DATE/TIME ENTERED field .01 and MESSGE TEXT
field 200.
INCOME VERIFICATION MATCH
Access to RELATED MAILMAN MESSAGE field 5.
RADIOLOGY/NUCLEAR MEDICINE
Access to ^HL(772,"B",
EVENT CAPTURE
Access to MESSAGE TEXT field 200.
CLINICAL INFO RESOURCE NETWORK
Access to DATA/TIME ENTERED field .01
TRANSMISSION TYPE field 4
RELATED EVENT PROTOCOL field 10
^HL(772,"B", x-ref
STATUS field 20
DATE/TIME PROCESSED field 21
LAB SERVICE
Access to STATUS field 20.
DSS EXTRACTS
E CLAIMS MGMT ENGINE
CONSULT/REQUEST TRACKING
GMRC has an HL7 interface with a Referral &
Authorization System (RAS) database in the Austin FSC. Certain types of
consults are sent to RAS in support of Veterans being approved for community
(non-VA) care. Occasionally, there may be an issue in parsing the data sent
from GMRC to RAS. When this occurs, a mail message is generated from the data
in the ACK message. The mail message contains the Message ID of the offending
HL7 message. GMRC would like to extend the information in the mail message by
adding the consult record number. To do that, GMRC will take the Message ID
from the ACK, look up the associated HL7 Message Text, and then parse the
Message Text (772;200) in order to retrieve the consult record number.
CREATOR SCHLEHUBER,CAMERON
DBA Comments
JSHARVEY 20070124/ NPI SPONSORING E CLAIMS' NEED TO BE ADDED

5/26/17-MM:  Added Consult/Request Tracking as a subscriber for GMRC*3.0*88.
The Subscribing Package section describes Consults use of ICRs #4069 and 4966.

Rob reviewed Consults request for subscription to ICR #4069 and 4966 and had
two concerns.  Tony said Consults is using FileMan APIs to read the data which
covered Rob's first concern about potential issues with Global read access if
changes were made to the file structure.

His second concern is documented below:

A second, general concern I have regards idiosyncrasies of the VistA HL7
package may cause problems for a subscribing package. For example:

- One might expect that the STATUS field in the HL7 Message Text file
for a TCP-type interface would be P - PENDING until the message is
transmitted. This is NOT the case
- I seem to remember an issue for either Lab or ESR in trying to reuse
the MESSAGE ID field.  I don't remember the particulars, but I'd be
on-guard for a new Integration Agreement triggering a required
change by VistA HL7

Specifics for 4966 :

- Is there really a need for direct global read, rather than FM?
- Although, in principle, I'd push for only FM access, I really
don't see a problem.

Specifics for 4069:
- Am I correct that 'Access to' does NOT mean WRITE/Delete access?
- See above regarding STATUS
- The 'C' xref for file #773 (Message ID) may have more than 1 entry
(duplicate messages). Not a problem, just a caveat.
DATE ACTIVATED 2007/01/24
MAIL MESSAGE 36003714
DATE/TIME EDITED
DATE/TIME EDITED ACTION AT THE REQUEST OF WITH CONCURRENCE OF
2007/01/24 12:23 SUBSCRIBER ADDED WHITE,DARLENE GROHOWSKI,THOMAS
2017/05/26 13:47 SUBSCRIBER ADDED THOMPSON,TONY WHELAN,ROB
2017/05/26 13:50 SUBSCRIBER ADDED THOMPSON,TONY ADES,ROBERT
Generated from SEP 10, 2019@ IA Listing Descriptions