by interface type

See our supported standards

other integrations

But wait! There's more! We've also created custom integrations using the following approaches.

Communicate Clinical Context

This integration allows the active patient context to be shared among multiple systems. A CCOW context manager helps coordinate all applications to open the same patient record, streamlining end user workflows that cross system boundaries. Current integrations include...
  • Caradigm
  • CareFx

Outgoing BSN Verification Query

BSN or Burgerservicenummer verification is required in the Netherlands. There are two types of BSN queries: BSN request, and BSN verification. Using provided demographic data, a BSN request will retrieve and store the BSN for a patient, whereas the BSN verification serves to validate that the BSN a user has stored to the patient record is correct.

Voice Recognition and Dictation Integration

Integrated dictation/speech recognition solutions pass context information, and in some cases status updates, automatically between Epic and the dictation/speech recognition system. Epic offers several integrated third-party dictation/speech recognition solutions. Current integrations include...
  • Commisure RadWhere
  • Dolbey
  • M*Modal Fluency Direct
  • PowerScribe 360

Outgoing Medication Orders

Sends outgoing e-prescribed medication orders, following Dutch HL7 v3 Standards (NICTIZ Aorta 6.10.0.0). Can be connected point-to-point with an outpatient pharmacy system. Certification with VZVZ for communication through the Landelijk SchakelPunt (LSP) is in progress.

Mobile App Integration read the specRead the technical specs

Epic's mobile applications - Haiku, Canto, and Rover - can communicate with specialized clinical review applications like document or image viewers. This framework allows our applications to launch your app with context, making for a a smooth and seamless clinical experience for the user. Current integrations include...
  • Sectra Liteview PACS
  • Voalte

PC-based Vitals Integration

This interface is used to integrate real-time PC-based vitals machines in a clinic with the Epic EMR. Devices are used to record patient vitals and communicated to the device manufacturer's program. Vitals are then offered to the EMR and validated by the user before they are copied into the chart. Current integrations include...
  • Midmark IQVitals
  • Welch Allyn

Telephony

This interface allows for tighter integration between Epic's Home Health product and third-party telephony vendors. The EMR exports patient information about scheduled home health visits and tasks that need to be performed as a part of the visit. The caregiver performs the visit and records his or her actions through the telephony system, which then triggers the information back to the Epic EMR for charging and clinical documentation. Current integrations include...
  • CareWatch
  • CellTrak
  • Home Health Aide Exchange

External Application Linking

The Epic EMR provides a robust framework for launching external applications - desktop or web - via remote procedure call. The launch, because it is triggered from within the EMR, can provide dynamic contextual information based on the patient, visit, or order that is currently displayed in Epic.You can email us to receive a simple testing harness that will help you validate that your web application can be successfully embedded.
Epic's patient portal can link to other patient-specific websites through functionality known as Dynamic Links. Dynamic Links are used to launch external websites from within the portal. The link can be configured to pass context about the patient through query string parameters, optionally encrypted using RC4 or AES. Current integrations include...
  • Apex
  • Blackhawk
  • eHealth
  • HealthEquity
  • The Health Heritage Family Medical History Project
  • Health Media
  • Lasernet
  • MyPreventiveCare
  • RSA Access Manager
  • RxEOB
  • VisionTree

Outgoing Medication History Query

Queries the Landelijk SchakelPunt (LSP) to retrieve patient medication data. Certified with VZVZ. This interface follows the Dutch HL7 v3 standards implemented within AORTA.

DRG Grouper/Pricer

This bidirectional interface analyzes claims to determine which DRG codes and prices are appropriate. Current integrations include...
  • nThrive
  • OptumInsight HSS EasyGroup

APC Grouper/Pricer

This bidirectional interface analyzes claims to determine which APC codes and prices are appropriate. Current integrations include...
  • OptumInsight HSS EasyGroup

Interface Engines

Although Epic software can be interfaced point-to-point with external systems, interface engines can reduce implementation time and help avoid message customization costs. Interface engines also lower the number of interfaces that are required to support the healthcare delivery ecosystem. Current integrations include...
  • BizTalk (Microsoft)
  • Camel
  • Cloverleaf (Infor Global Solutions)
  • Corepoint Integration Engine
  • DataExchange (TIBCO)
  • Datagate (Sun)
  • e-Biz Impact (Sybase)
  • eGate Integrator (Sun)
  • eLink (Eclipsys)
  • Ensemble (InterSystems)
  • HL7Connect
  • Iatrics Engine
  • IGUANA
  • iWay
  • Instrument Manager (Data Innovations)
  • JBoss Fuse
  • JCAPS (Sun)
  • MD Link
  • MITS (Interlink)
  • MQSI (IBM)
  • Mirth (WebReach)
  • OPENLink (Siemens)
  • Rhapsody (Orion Health)
  • Summit Express Connect
  • Viaduct
  • WebSphere Message Broker (IBM)

Release of Information Copy Vendor Integration read the specRead the technical specs

Some organizations use a copy vendor’s system to complete some portion of their Release of Information workflow. Your organizations can use existing Epic functionality to integrate Epic and the copy vendor system and reduce duplicate work. Depending on your organization’s workflows and your copy vendor, you can utilize a text file and file transfer workflow or a web service workflow to expedite this process for your staff and patients. Current integrations include...
  • CIOX & Prism (fka HealthPort and IOD)
  • MRO

Credit Card and Check Scanning Device Integration read the specRead the technical specs

In addition to the Credit Card and Bank Account Integration specification, Epic provides separate and additional support for non-keyboard emulation credit card devices. This integration is handled through an interface between Epic and your gateway software. The gateway software integrates with the device and provides Epic with transaction results for the credit card payment. This integration is handled through the patient kiosk and by front desk personnel during check-in or check-out. This interface is supplemental to the generic credit card interface described above and should be implemented in addition to that interface if you want to provide support for EMV devices. Current integrations include...
  • CORE Business Technologies
  • DivDat Healthcare Solutions
  • Elavon
  • Experian
  • HealthPay 24
  • Instamed
  • Salucro
  • Tempus Technologies
  • TrustCommerce

Outgoing IRIS Ophthalmology Encounter Summary

Epic automatically generates a document that meets the specifications of the Intelligent Research in Sight (IRIS) registry. This highly specialized registry uses a documentation format that does not conform to the standards of other registries. The generated document contains a summary of the patient's ophthalmology-related encounter and is intended to be used only in the context of outpatient visits.