Print Page as PDF
Read access to HLO Messages file for capacity planning ICR (6883)

Read access to HLO Messages file for capacity planning    ICR (6883)

Name Value
NUMBER 6883
IA # 6883
FILE NUMBER 778
GLOBAL ROOT HLB(
DATE CREATED 2018/02/26
CUSTODIAL PACKAGE HEALTH LEVEL SEVEN
USAGE Private
TYPE File
DBIC APPROVAL STATUS APPROVED
NAME Read access to HLO Messages file for capacity planning
GENERAL DESCRIPTION
The purpose of this IA is to allow subscribing packages
to read the HLO Messages (#778) file directly.  KMP routines will aggregate
message metrics for analysis and capacity planning.
GLOBAL REFERENCE
GLOBAL REFERENCE FIELD NUMBER GLOBAL DESCRIPTION
HLB(D0,0
FIELD NUMBER ACCESS FIELD NAME LOCATION
.03 Direct Global Read & w/Fileman APPLICATION ACKNOWLEDGMENT TO 0;3
.04 Direct Global Read & w/Fileman DIRECTION 0;4
.05 Direct Global Read & w/Fileman LINK 0;5
.06 Direct Global Read & w/Fileman QUEUE 0;6
HLB(D0,1
FIELD NUMBER ACCESS FIELD NAME LOCATION
1 Direct Global Read & w/Fileman HDR SEGMENT,COMPONENTS 1-6 1;E1,250
HLB('C'
Direct global read access to "C" x-ref.
HLB(D0,2
FIELD NUMBER ACCESS FIELD NAME LOCATION
2 Direct Global Read & w/Fileman HDR SEGMENT,COMPONENTS 7-END 2;E1,250
STATUS Active
DURATION Till Otherwise Agreed
ID HLB(
SUBSCRIBING PACKAGE VISTA SYSTEM MONITOR
CREATOR LUNDEN,JOHN M
DBA Comments
3/9/18-MM:  Activated ICR #6882 6883 for KMP*4.0*0 and
XU*8.0*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 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/09
DATE/TIME EDITED
DATE/TIME EDITED ACTION AT THE REQUEST OF WITH CONCURRENCE OF
2018/03/09 13:26 APPROVED LUNDEN,JOHN WHELAN,ROB
Generated from JAN 24, 2019@ IA Listing Descriptions