Last week I retrieved the full list of the active IA (Integration Agreement) Description Nov 2010 from the VA download site - url - https://downloads.va.gov, to begin the process of using the IAs to validate the dependencies between Vista modules. Even though we received an ICRs listing from Julie Harvey of VA back in October, that list contained only 616 so-called “public” ICRs; whereas the full list retrieved from VA download site contained 4197 of “public”, “private”, and “controlled” ICRs. The IA, a.k.a. DBIA or ICR, as defined by VA is “A formal understanding between two or more application packages which describes how data is shared or how packages interact. This Agreement maintains information between package Developers, allowing the use of internal entry points or other package-specific features.” An example of a DBIA record listed in the VA document is shown here
1 NAME: DBIA1
CUSTODIAL PACKAGE: KERNEL San Francisco
SUBSCRIBING PACKAGE: ORDER ENTRY/RESULTS REPORTING Salt Lake City
USAGE: Private ENTERED: JUL 27,1989
STATUS: Active EXPIRES:
DURATION: Till Otherwise Agr VERSION:
DESCRIPTION: TYPE: Other
COMPONENT: Protocol Menu
VARIABLES: XQOR Type: Used
Set, when an option with type protocol
menu is encountered, to the internal
number of the option before execution is
turned over to OE/RR.
Based on the information contained in the Custodial Package and Subscribing Package fields, which specifies the module dependencies, I updated the dependency diagram for 15 of the 168 VistA modules defined in the OSEHRA System Architecture – Product Definition and Roadmap Enterprise Architecture (EA) model. The following shows one of the dependency diagrams, in particular, the CPRS or Order Entry/Result Reporting package.
Comparing against the OSEHRA VISTA Visual Cross Reference at : http://code.osehra.org/dox/:
Module dependencies found in Cross Reference but not in DBIA (7 modules) –
Drug Grouper, Emergency Department Integration Software, Master Patient Index VistA, Health Data and Informatics, CPT HCPCS Codes, Medicine, and Web Services.
Module dependencies found in DBIA but not in the Cross Reference (5 modules) –
NDBI, CORBA Services, Imaging, CMOP, HINQ
A cursory look at the description associated with the dependencies found in DBIA but not in the Cross Reference indicates dependencies that were associated with globals and communication processes. This is one area where the current XINDEX based Cross Reference does not take into account when determining the package dependencies.
Note: There were 784 DBIAs associated with Order Entry/Result Reporting package, of which 230 of the DBIAs had OE/RR as custodial package and 554 as subscribing packages.
I’m in the process of creating a database to host the DBIA data to ease the updating process for the System Architecture model and to incorporate the DBIA documentation into the OSEHRA VistA Cross Reference online documentation. My plan is to create the database in SQL with XML and Excel export for portability.
Let me know if you have questions or suggestions.