Some labs that use Epic also use Lifepoint Informatics. Lifepoint can serve as an aggregator connecting your practice clients’ various EMR systems or by using the Lifepoint Provider Portal coupled with  your instance of Epic through a single interfaced connection. If you are currently working with Lifepoint or are interested in implementing a Lifepoint connection with Epic, these are ways to make using Epic easier.

EMR Interfacing Seamlessly

If orders are placed in the practice’s EMR system, Lifepoint can build an order interface from the vendor to create the order within our database. Lifepoint will normalize the messages and send the data to the laboratory in the same format each time. This saves the lab time and resources as you will not need to code to separate vendor formats (e.g., eClinicalWorks, Athenahealth, Practice Fusion, etc.).

Results can be delivered back to the EMR system, where one format is received from EPIC and filed into the Lifepoint database.  We will then code to each vendor’s specifications for how they need to receive those results.

Lifepoint keeps a database of all EMR vendor specifications, to speed up the integration process.

Registration Workflow

Lifepoint recommends using an ADT interface to create and register patients, as opposed to having users manually register patients. This helps prevent user errors.

For incoming orders, Epic’s auto-registration functionality can create and/or assign hospital accounts to the newly created lab requisition encounters. Which helps save time.

While we recommend the functionality outlined above, Lifepoint can support the following registration workflows based on your organization’s needs:

  • Automated registration
  • Manual registration
  • Requisition release registration

Configuring the Incoming Orders Interface

Typically, one Incoming Order interface is created to send orders from Lifepoint to Epic. The mode in which this interface is configured depends on your organization’s intended connection with Lifepoint.

Accessioning and Barcode Options

Lifepoint supports the following options for creating instrument-ready barcodes with incoming orders:

  • Lifepoint will assign an order number which will be sent to Epic in the interface message. Epic will track this number on the order record, using an identifier to link it back to Lifepoint.
  • Epic will send an ORM status update message back to Lifepoint with the accessioning number, along with other information needed (patient demographics, specimen type, department, test names etc.)
  • Lifepoint will generate a barcode label upon receiving the updated message and will print them remotely at the practice.  A slight delay (typically <5 seconds) in printing will occur with this choice due to message processing time.

Configuring the Outgoing Results Interface

For bi-directional connections, outgoing result interfaces can be configured to send back results to Lifepoint from Epic.

  • Recommended outgoing results – Outgoing Lab Results and Orders to External Providers can be used to send results and cancel messages from Epic.
  • Reportable Results – Outgoing Clinical Results can be used to send results flagged as reportable to external systems.
  • Other general outgoing results –Outgoing Lab Orders and Results to External Providers for sending order updates and results from Epic.

Schedule a Demonstration