Ancillary Systems

Sends transfusion notifications to external Blood Bank systems so that blood banks can update their records when a given blood unit is transfused. To use this interface, an organization must document the unit number and product code for blood transfusions using the Blood Product Administration Module.

You can configure each copy of this interface one of the following ways:

• This interface can send result messages in the LRI format. LRI format results follow the HL7 version 2.5.1 Implementation Guide: S&I Framework Lab Results Interface, Release 1. It can send both order status and result messages from Beaker to external systems, when Beaker is the reference lab for another LIS or clinical system.
• This interface can send result messages in the ELR format. ELR format results follow the HL7 version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 1. This format is often used to notify public health agencies of tests which must be reported for disease tracking, and meet Meaningful Use (MU) or Promoting Interoperability (PI) measures in the U.S.
• This interface can send messages for pathology reports that contain electronic cancer checklists. These messages conform to the North American Association of Central Cancer Registries (NAACCR) Standards for Cancer Registries Volume V rules for constructing HL7 messages for CAP electronic cancer checklist synoptic reporting.

Use the LRI format unless you have a specific need to use the ELR or NAACCR formatted results. Note: Performing labs which are active participants in the Orders and Results Anywhere network use an interface that adheres to the same guidelines but has context aware connectivity to its consistituent ordering organizations without the need for a VPN or TCP/IP connection. These specifications are located in "Orders and Results Anywhere".

Sends orders placed by a clinical user in EpicCare to external ancillary systems - including messages for new orders, order cancellations, and number assignment responses to externally-initiated orders. Use cases include: Send physician placed orders to external laboratory, radiology or cardiology systems, when not using Epic equivalent product. Send orders from Beaker, Epic's LIS, to an external LIS if test needs to be performed at another lab. Send orders to blood bank system from Beaker. To send orders to both an external lab system (not to Beaker) and an external radiology system (not Radiant, Epic's RIS), two copies of the interface are needed, one for each purpose.

This interface is included with the Blood Product Administration Module and facilitates matching (positive patient identification with blood) of blood products received from an external blood bank system.

Receives test results from instruments into Beaker, Epic's LIS. This is also the interface to use to receive point of care testing results, such as from docked glucometer systems, into Beaker.

Sends information about new or canceled laboratory orders from Beaker, Epic's LIS, to an instrument. This is also the interface to use for Point of Care testing with Beaker, for example, docked glucometer systems. It can trigger messages when a new specimen is received, a test is reordered, an add-on test is ordered for a specimen that has already been received, or a test is canceled.

Receives orders from external ordering systems. The interface can create, update, or cancel orders. Common use cases are routing lab orders to Beaker (Epic's LIS), radiology orders to Radiant (Epic's RIS), or cardiology orders to Cupid (Epic's CVIS). Some integrations may additionally require either an Incoming Patient Administration interface to create or update patient records or an incoming query to look up patient information before sending the order message.

The Epic EHR receives test results from a laboratory, cardiology, or similar information system for use in Epic. These results include general lab, microbiology, pathology, and blood bank results, results with a narrative/impression, and hyperlinks to results that are stored elsewhere. These results can include LIS data, RIS data, pacemaker data, ECG records, and hemodynamic data. The interface can accept incoming order messages that request order numbers, replace procedures, or cancel existing orders. This HL7v2 interface is specific to a clinical order and uses TCP/IP to exchange messages. Test your implementation with our HL7 V2 Validator

Discrete genomic results file to Epic via the Incoming Ancillary Results interface. To include discrete genomic data as a part of the test's result, specifically formatted OBX segments must be included on the result (ORU^R01) message. These OBX segments follow the representation for discrete genomic data published in the HL7 Version 2.5.1 Implementation Guide: Lab Results Interface (LRI), Release 1 and the supported data elements are outlined in the specification document.

The integration between Beaker, Epic's lab software, and an image-management system for the digital pathology workflow utilizes the Outgoing Lab Instrument Orders and the Incoming Lab Instrument Results interfaces. Beaker sends patient, case, and slide information and receives image availability notifications to enable whole slide imaging workflows.