Print Page as PDF
Read access to HL7 Message Text file for capacity planning. ICR (6877)

Read access to HL7 Message Text file for capacity planning.    ICR (6877)

Name Value
NUMBER 6877
IA # 6877
FILE NUMBER 772
GLOBAL ROOT HL(772,
DATE CREATED 2018/02/22
CUSTODIAL PACKAGE HEALTH LEVEL SEVEN
USAGE Private
TYPE File
DBIC APPROVAL STATUS APPROVED
NAME Read access to HL7 Message Text file for capacity planning.
GENERAL DESCRIPTION
The purpose of this IA is to allow packages to read the
HL7 Message Text (#772) file directly.  KMP routines will aggregate message
metrics for analysis and capacity planning.
VIEWER
  • MARKS,MARY
  • FISHER,MARK
GLOBAL REFERENCE
GLOBAL REFERENCE FIELD NUMBER GLOBAL DESCRIPTION
HL(772,DO,0
FIELD NUMBER ACCESS FIELD NAME LOCATION
.01 Direct Global Read & w/Fileman DATE/TIME ENTERED 0;1
10 Direct Global Read & w/Fileman RELATED EVENT PROTOCOL 0;10
8 Direct Global Read & w/Fileman PARENT MESSAGE 0;8
16 Direct Global Read & w/Fileman NAMESPACE 0;13
HL(772,'B'
Direct global read access to "B" x-ref.
HL(772,D0,'S'
FIELD NUMBER ACCESS FIELD NAME LOCATION
100 Direct Global Read & w/Fileman NO. OF CHARACTERS IN MESSAGE S;1
101 Direct Global Read & w/Fileman NO. OF EVENTS IN MESSAGE S;2
102 Direct Global Read & w/Fileman TRANSMISSION TIME S;3
STATUS Active
DURATION Till Otherwise Agreed
ID HL(772,
SUBSCRIBING PACKAGE VISTA SYSTEM MONITOR
CREATOR LUNDEN,JOHN M
DBA Comments
3/8/18-MM:  ICR #6877 has been activated for KMP*4.0 and
XU*8*670.

Background:  KMP is updating the legacy HL7 metric collections. They are
simplifying and streamlining the collection routines.  In order to do this
they need to be able to READ only the necessary data. They then aggregate and
send to a central repository.  In order to minimize compute resources the code
will use the "B" xref to get data for the previous day,  get the data for a
global node and then piece out that data "locally".

Rob concurred with request and provided the following comments:

KMP's use of these records seems safe.  There are no usable, supported APIs to
provide the needed functionality.  I do have one concern: These are
high-volume files, and purging can occur at any time.   Records being purged
are by definition static and not being used - which could mean that READs on a
record during the split-second of purging could capture only part of a logical
record.  Because KMP's use of this is to gather metrics, I am not concerned
that there might occasionally be a file #773 record without it's logical #772
component (or vice versa).  Just make sure that your programming logic does
not depend on any logical consistency (e.g., generous use of $GET).
DATE ACTIVATED 2018/03/08
DATE/TIME EDITED
DATE/TIME EDITED ACTION AT THE REQUEST OF WITH CONCURRENCE OF
2018/03/08 12:05 APPROVED LUNDEN,JOHN WHELAN,ROB
Generated from JAN 24, 2019@ IA Listing Descriptions