Clinical Information

Sending and receiving clinical data.

HL7v2

Traditional HL7v2 interfaces can cover all types of clinical findings for patients already established within the Epic system.

Outgoing interfaces refer to interfaces in which the Epic system sends the message. Incoming interfaces refer to interfaces in which the Epic system receives the message.

Outgoing Documentation read the spec

Notifies external systems of documentation recorded in Epic. Sends MDM messages with notes and transcriptions as they are saved and modified, and can send a document summary upon close of an encounter in EpicCare Ambulatory EHR. Documents are sent in either RTF or PDF format.

Current integrations include

Outgoing Provider Communications Interface read the spec

Notifies external systems of provider communications written in the Communication Management activity in Epic. The interface sends letter attachments as PDF documents to recipients.

Current integrations include

Argus
Caresharing
CareSource
Cerner
Clevermed
E.Novation
E-Health
eMDs
HealthLink
iD
Iuvo
Medicus
NHS Digital
Ontario Ministry of Health
Ontario Patient Data Reporting
PharmOutcomes
Synedra

Incoming Medical Device Waveform Interface read the spec

Receives data from monitors as a live stream and renders it as a wave form in the Epic monitoring activity. Unlike the Incoming Device Data (HL7 v2) interface, it doesn't store discrete instances of patient vitals. This interface requires the Inpatient/ICU advanced device license.

Incoming Provider Communications Interface read the spec

Notifies Epic users of provider communications written in other systems. Communications can have attached letters or documents and are routed to the recipient (Provider, Department, etc) based on preferences (In Basket, Fax, Mail, etc) the same as if the communication was written in Epic and routed with the Communication Management activity.

Current integrations include

Eon
SAP

Outgoing Infusion Orders read the spec

Sends infusion order details to infusion pump gateways for the purposes of prepopulating infusion parameters on associated infusion pumps. When an infusion order message is sent on the Outgoing Infusion Orders interface, an immediate response is expected back from the infusion pump gateway via the Incoming Verification interface. These are advanced interfaces with a particular set of pre-requisites for successful implementation.

Current integrations include

B. Braun
Baxter
BD
ICU Medical
Smiths Medical

Incoming Patient Education Interface read the spec

Integrates Epic's Patient Education activity with a third-party education content management or content delivery system. The interface is used to record whether the patient has completed an educational assignment, and it can also be used to record ad hoc educational activities that were not assigned by the clinician.

Current integrations include

Aceso
Avidex
GetWellNetwork
MDM Healthcare
Mytonomy
OneView
Optimal Solutions
pCare by Uniguest
Redox
Skylight
SONIFI Solutions
Wolters Kluwer

Outgoing Patient Education Interface read the spec

Integrates the Patient Education Activity with a third-party education content management or delivery system. This interface is used to send clinician-initiated education assignments to a third-party system so that the content can be viewed and acted upon there.

Current integrations include

Aceso
API Healthcare
Avidex
GetWellNetwork
MDM Healthcare
Mytonomy
OneView
Optimal Solutions
pCare by Uniguest
QuadraMed
Skylight
SONIFI Solutions
Wolters Kluwer

Incoming Problem List read the spec

Used to add, modify, or remove problems from the patient-level problem list. This interface works specifically with the longitudinal problem list, not problems specific to a particular hospitalization. This integration has been implemented only for conversions.

Current integrations include

OncoChart

Outgoing Problem List read the spec

Sends notification of added, modified, or deleted problems from the patient-level problem list in the EHR to an external system. This interface works specifically with the longitudinal problem list, not problems specific to a particular hospitalization.

Current integrations include

Allscripts
GE
Harris
HealthInfoNet
IBM
Jvion
Microsoft
MyHealth Access Network
New York City - Public Health Agencies
SONIFI Solutions
XSOLIS

Incoming Clinical Observations read the spec

Receives and processes clinical observations (past medical history, smoking history, and so on), that do not fit into other tools. This interface is typically used for filing clinical data for the purposes of a conversion. The Incoming Clinical Documentation Flowsheet interface is recommended if the data will be filed only to a documentation flowsheet.

Current integrations include

Allscripts
Ambulancezorg Nederland
Astraia
GE
Lameris Ootech
PDHI
Salesforce

Outgoing Medication Administration Notification read the spec

Sends medication administration notification when a clinician marks a medication as administered on the MAR. This interface also sends updates regarding prior administrations, and change of status notifications for medications previously marked as administered. It does not send due times for medications that need to be administered in the future. The interface does not send messages when clinicians document the administration of blood products on the MAR or patient-controlled analgesia (PCA) medications on a documentation flowsheet.

Current integrations include

Outgoing Scanned Document Link Maintenance read the spec

Sends updated document link keywords to an external document management system (DMS) when key information about where the content is located changes, for example, if a scan that originated in the DMS is moved from one encounter to another by HIM Chart Correction processes.

Current integrations include

3M
Civica
FOTO Inc.
Fujifilm
Hyland
IBM
Lexmark Enterprise Software
MedPlus
OpenText
Paragon
Quest Diagnostics
RVC
Synedra

Incoming Device Data read the spec

Receives discrete measurements from patient monitoring and documentation devices. The messages file to the application, where the data can be validated by the user and added to the chart, or in the case of surgical procedures, can be set to automatically validate and file to the chart. This type of integration is usually done with device aggregators to file samples from continuous physiological monitoring. It is not used for consumer-initiated monitoring or home monitoring. Test your implementation with our HL7 V2 Validator.

Current integrations include

Outgoing Clinical Documentation Flowsheet Data read the spec

Sends discrete documentation flowsheet data to another system.

Current integrations include

Incoming Clinical Documentation Flowsheet Data read the spec

Receives discrete patient data from an external system (where a user has previously validated the data), and files directly to the documentation flowsheet. This interface can also be used with clinically regulated home monitoring device vendors for post discharge monitoring programs, home care, home hospice, or other types of patient monitoring episodes.

Current integrations include

Incoming Procedure Log Data read the spec

Receives information about cardiac catheterization, electrophysiology and interventional radiology procedures when using the Cupid (CVIS) procedure log for intra-procedure documentation. This information is sent from a hemodynamic product that collects vitals and pressures during the procedure. This interface can file information to flowsheets and free text events such that it appears on the Cupid procedure log. This interface is typically not used if Cupid's procedure log is not in use and the procedure log is being completed in the hemodynamic system.

Current integrations include

Abbott Diagnostics
Change Healthcare
GE
IBM
McKesson
Medtronic
Merge Healthcare
Philips
Schwarzer Cardiotek
Siemens
St. Jude's
Vyaire Medical
Xperthis

Outgoing Registration to Home Device Data Concentrator read the spec

Sends registration information to a device data concentrator system to register patients and devices. This interface would be used instead of the standard Patient Administration interface when collecting data from patient home monitoring devices using an external system.

Current integrations include

Aetonix
Cardiocom
Health Recovery Solutions
Honeywell (Intermec)
Medtronic
Philips
Resideo
Vivify Health

Incoming Infusion Documentation read the spec

Receives discrete measurements from an infusion pump gateway associated with the administration of an infusion order. This is an advanced interface with a particular set of prerequisites for successful implementation.

Current integrations include

Ascom
B. Braun
Baxter
BD
Capsule Technologies
Fresenius Medical Care
ICU Medical
NantHealth
Smiths Medical

Incoming Medication Administration Notification read the spec

Files administration information to a medication order created and acted on in an external system. The read-only orders appear on the MAR for reference.

Current integrations include

Merge Healthcare
Quantum Secure

Incoming Transcriptions read the spec

In this scenario, an external system has findings in a text or image format. These findings are either observations from a given contact with a patient (such as a visit or a hospitalization) or observations specific to a clinical order. Traditionally, this interface was used to match dictations with their eventual transcription (hence the name), but it can be used for a broader range of clinical findings. The EHR receives and files documents from a transcription system, scanned documents from an external document management system, or notes generated in another clinical system. This interface is often used for clinical findings that don't neatly fit into more specific data elements. Notes created or updated by the transcription interface can trigger deficiency updates.

If your intent is to file findings against a specific order, please email us to learn more. Other interfaces may be more appropriate for your use case.

Current integrations include

Incoming Scanned Document Link read the spec

Receives and files scan pointers from an external document management system. This interface can also receive base64 encoded documents and store them to an Epic server. This interface does not file textual data intended for use in Radiant or Cupid; those documents must be processed by the Incoming Ancillary Results and Orders interface set up as an Incoming Ancillary Results and Orders - Imaging interface. Messages must be in HL7 MDM format. Documents processed by this interface can satisfy deficiencies in the Health Information Module.

Current integrations include

Smoking Cessation Integration read the spec

This is a group of three interfaces that together can be used to integrate with quit line vendors to communicate an order for cessation counseling, and receive in response the followup documented by the quit line and any medications, such as nicotine gum, given to the patient as part of the protocol.

Current integrations include

California State Quit Line
National Jewish Health
Optum

Incoming Medical Device Waveforms Interface read the spec

The Epic Monitor can receive streaming waveform data from device and middleware vendors for displaying in the Waveform widget in the Epic Monitor.

Electronic Fetal Monitoring

Epic integrates electronic fetal monitoring systems more tightly with inpatient workflows in the Epic EHR. The interfaces control establishing a shared identity with the EFM system, transmitting monitor vitals information from the fetal monitor to Epic, and associated documentation done in Epic with the fetal strip.

Current integrations include

CCSI OBIX
GE Centricity Perinatal
Hill-Rom NaviCare WatchChild
PeriGen
Philips OB TraceVue