| 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 |
| 7231 | CERNER NAK ERROR LOG | Routine | ELECTRONIC HEALTH MODERNIZATION | 2021/02/26 | Under Revision | Supported | This integration agreement allows other packages to call the supported routine ADD2LOG^EHMUHLV. If any interface that is sending messages to/from Cerner receives a NAK, this API will need to be called in order to send an email back to Cerner users stating what error occurred. Six possible parameters need to be passed in to the API: ADD2LOG(TYPE,INTERFACE,MESSAGE,SEVERITY,CIDNUM,SOURCE) TYPE (Required) = Severity of the log entry 'E' FOR ERROR Record could not be processed 'W' FOR WARNING Record was processed but should be reviewed 'D' FOR DATA DEFAULTED A default value was substituted before processing the record INTERFACE (Required) = Interface that generated the log entry MESSAGE (Required) = Reason for log entry (may refer to a segment or field) SEVERITY (Required) = Severity of the error 'H' FOR HIGH failure requires immediate attention 'M' FOR MEDIUM failure is important, but not critical 'L' FOR LOW log entry can be researched over time 'I' FOR EH log entry is informational only CIDNUM (Required) = Cerner ID Number SOURCE (Optional) = Source of log entry. Should contain HL7 full message if needed |
EHMUHLV | 2021/03/03 | |||
| 7424 | HL7 MESSAGE REPOSITORY (EHRM HL7 Message #1609) | Routine | ELECTRONIC HEALTH MODERNIZATION | 2023/05/02 | APPROVED | Active | Controlled Subscription | Effective with patch EHM*1*10, a repository (EHRM HL7 Message file (#1609)) exists to store HL7 messages that can be used to research production issues. The repository is intended to store only Inter-Facility Consult (IFC) and Patient Record Flags (PRF) HL7 messages exchanged between non-converted VistA sites and Cerner Millennium. This ensures that the size of the repository is small relative to the total number of HL7 messages on any individual VistA. In addition to the repository, EHM*1*10 creates Application Programming Interfaces (API) callable by subscribing packages to populate the repository. The patch also supplies options to inquire into the repository and to purge records. Effective with patch GMRC*3*189, when an IFC is initiated by or received on a non-converted VistA site, the order message and all follow-up messages are added to the HL7 Message Repository. Effective with patch DG*5.3*1091, when a PRF is initiated by or received on a non-converted VistA site, the message is added to the HL7 Message Repository. Note: EHM*1*10, GMRC*3*189, DG*5.3*1091 and TIU*1*350 are combined in the IFC ORDER/ADDENDUM UPDATES 1.0 build released in IFC_ORDER_ADDENDUM_UPDATES.KID. Effective with EHM*1*16, the repository also stores Prosthetics (PSAS) HL7 messages exchanged between non-converted VistA sites and Cerner Millennium. |
EHMHL7 | 2025/04/23 |