|CUSTODIAL PACKAGE||HEALTH LEVEL SEVEN|
|DBIC APPROVAL STATUS||APPROVED|
|NAME||Read access to HLO Messages file for capacity planning|
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.
|DURATION||Till Otherwise Agreed|
|SUBSCRIBING PACKAGE||VISTA SYSTEM MONITOR|
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).