| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 4638 | DBIA4638-A | Routine | HEALTH DATA & INFORMATICS | 2005/04/05 | APPROVED | Active | Supported | The NTRTMSG^HDISVAP API is used to direct the user on how to enter a new term using the New Term Rapid Turnaround Process (NTRT) being provided by Enterprise Terminology Services (ETS). |
HDISVAP | |||
| 4639 | DBIA4638-B | Routine | HEALTH DATA & INFORMATICS | 2005/04/06 | APPROVED | Active | Supported | The EN^HDISVCMR API is used to invoke the VUID Seeding Process for a specified HDIS Domain. Packages may invoke this API without registering another IA only if the domain and files being referenced are in the calling package's numberspace. |
HDISVCMR | |||
| 4640 | DBIA4638-C | Routine | HEALTH DATA & INFORMATICS | 2005/04/06 | APPROVED | Active | Supported | API(s) for retrieval and screening of the file/field implementation status. |
HDISVF01 | |||
| 4641 | DBIA4638-D | File | HEALTH DATA & INFORMATICS | 2005/04/06 | APPROVED | Active | Controlled Subscription | The Data Standardization (DS) Domain Action Team (DAT), which includes the application developer, identifies which reference files should be standardized for the Domain. Each entry in the file is then assigned a VHA Unique Identifier (VUID) by the Enterprise Reference Terminology (ERT) Group. DS then assists in the seeding of the VUIDs at the Facilities. There are two approaches to the VUID Seeding. The first is Facility by Facility and the second is Global Distribution. Additional information about the approaches can be found in the VUID Implementation Application Patch Requirements Document for the Domain being Standardized. Each Domain is given a document which identifies the changes needed in Current VistA for the DS effort. One of the requirements is to release a VistA patch via the National Patch Module (NPM) which contains the changes identified in the Patch Requirements Document. For the Facility by Facility Approach the HDIS Domain file is used during the VUID Seeding Process. It contains a list of the files being standardized for the Domain. The VUID Seeding Process itself is invoked in the application post-initialization routine by calling EN^HDISVCMR (IA #4639). As part of this process DS will look through the entries for each of the files being standardized for the Domain and extract the .01 field to be bundled into an XML message. The subscriber agrees to give DS permission to directly access the Global in the routine FILE^HDISVCFX for the .01 field of the file being standardized. GLOBAL REFERENCE: ^Global(file#,D0,0)=.01 field read only |
HDISVCFX | |||
| 4651 | DBIA4638-E | Routine | HEALTH DATA & INFORMATICS | 2005/04/11 | APPROVED | Active | Supported | The $$GETIEN^HDISVF09 API is used to get the HDIS Domain file IEN by the Domain. The MFSUP^HDISVF09 API is used in the Master File Server Parameters to update the status of the file to Complete and send out the HDR Activation bulletin. |
HDISVF09 | |||
| 4801 | DBIA4801 | Routine | HEALTH DATA & INFORMATICS | 2005/10/05 | APPROVED | Active | Private | Within the Lab Data file (#63), is the Microbiology multiple (field #5, subfile #63.05), and within that is the Organism multiple (field #12, subfile #63.3) for microbiology organisms. This in turn contains site specific fields (created by the option LRWU7 - Add a new internal name for an antibiotic) for antibiotics associated with the organism. There are values associated with the antibiotic that meet the criteria for being described as a set of codes: Value Description ---------------- ------------------------------------------------------- ALWAYS DISPLAY Always display the result. NEVER DISPLAY Never display the result unless the user has the LRLAB key that indicates user is laboratory personnel. RESTRICT DISPLAY Result is only displayed if the interpretation of all antibiotics that are always displayed is resistant. Although the set of codes has been assigned VHA Unique Identifier (VUID), new antibiotics can be entered into VistA by a facility. The new antibiotics are dynamically assigned field numbers and would not automatically find translation to a VUID. Since this is a rare exception and one not felt to jeopardize the integrity of the VUID model, DS proposes to handle the translation of these site specific fields and provide APIs for the Lab application to use when converting to/from a VUID. This will allow for more expediency if changes are needed and ensure that new entries are assigned VUIDs that are interpretable by the HDR. This DBIA contains the APIs. |
HDISVAP | |||
| 4856 | DBIA4856 | Routine | HEALTH DATA & INFORMATICS | 2006/09/08 | APPROVED | Active | Supported | API will be used by HSITES as part of their software to insure that mirrored test accounts are setup properly. |
HDISVCUT | |||
| 4860 | HDI | Routine | HEALTH DATA & INFORMATICS | 2006/05/23 | APPROVED | Active | Supported | API for storage of the file/field implementation status. Packages may invoke this API without registering another IA only if the domain and files being referenced are in the calling package's numberspace. |
HDISVF01 | |||
| 5026 | TRANSMIT LAB SNOMED CT EXCEPTIONS | Routine | HEALTH DATA & INFORMATICS | 2007/08/07 | APPROVED | Active | Private |
This Integration Agreement permits the Lab package to utilize a Health Data and Informatics (HDI) application programmer interface (API) to report SNOMED CT (SCT) exceptions to the Enterprise Reference Terminology (ERT) team for resolution. There are three exceptions/events that result in the Lab package using the API. They are: 1) Error encountered while loading ERT mapped SCT code into the target database 2) Loading new/additional terms received from another system via HL7 messaging 3) New terms are entered locally |
HDISVAP1 | 2012/09/12 | ||
| 5162 | HDIS STATUS UPDATE EVENTS | Other | HEALTH DATA & INFORMATICS | 2008/03/25 | Pending | Supported | This event point is used to post before/after status values whenever the implementation status of a file is changed. The values posted are what would be output by $$GETSTAT^HDISVFO1() before and after the change is made. The following nodes will be posted: ^TMP("HDIS",$J,"STATUS",FileNumber,"BEFORE") = StatusCode ^ StatusPointer ^ StatusDate ^TMP("HDIS",$J,"STATUS",FileNumber,"AFTER") = StatusCode ^ StatusPointer ^ StatusDate |
|||||
| 5203 | Get HDIS Status Text | Routine | HEALTH DATA & INFORMATICS | 2008/05/22 | Pending | Supported | The $$GETCTXT^HDISVF06 API is used to get the Status Text for the Status by Status Type and Status Code. The $$GETTEXT^HDISVF06 API is used to get the Status Text for the Status by IEN. |
HDISVF06 | ||||
| 5209 | HDISVLM MAPPING TOOL | Other | HEALTH DATA & INFORMATICS | 2008/06/05 | Pending | Supported | This event point is used to post before/after record mapping values whenever the STS Generic Mapping Tool changes the mapping of a record during the release process when implementing a new standardized domain. The following nodes will be posted: ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"BEFORE",<record ien>,"REPLACED BY")=<value of field 99.97> ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"BEFORE",<record ien>,"INHERITS FROM")=$$RPLCMNT^XTIDTRM(<file#>,<record ien>) ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"AFTER",<record ien>,"REPLACED BY")=<value of field 99.97> ^TMP("HDISVLM MAPPING TOOL",$J,<file#>,"AFTER",<record ien>,"INHERITS FROM")=$$RPLCMNT^XTIDTRM(<file#>,<record ien>) |
|||||
| 6894 | HDI COLLECT SDOS | Routine | HEALTH DATA & INFORMATICS | 2018/03/27 | APPROVED | Active | Controlled Subscription | API for collecting Standards Development Organization (SDO) codes from Laboratory based on items in the ORDERABLE ITEMS File (#101.43) |
HDISDOC | 2018/10/30 |