By Interface Type

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 download a 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
  • Patientco
  • Salucro
  • Tempus Technologies
  • TrustCommerce

Fax Integration

This functionality is used to integrate Epic with an organization’s faxing solution. Epic software can currently be set up for integrated faxing with the following vendors in addition to any fax solutions that use Common Alerting Protocol (CAP) standard XML. Example documents for our CAP XML integration can be provided upon request. For solutions not using CAP XML, integration with individual vendors is developed by Epic at the request of Epic customers. Current integrations include...
  • Biscom
  • Concord Fax
  • Faxination
  • FaxPress
  • Genifax
  • GFI FaxMaker
  • InterFAX
  • Passport
  • RightFax
  • Streem
  • XMediusFAX

Outgoing Procedure Log Data read the specRead the technical specs

Sends data for configured case tracking events from a Cupid Procedure Log case to external ancillary systems mainly for reporting purposes. The messages contain data on the case including Panels, Staff, Timeouts, Implants, Equipment, Radiation, Verifications, Flowsheets, Events, Medications, and Labs. This interface uses the XML message format.

Outgoing Initial Public Health Case Report

Sends reportable results to public health agencies. This interface uses the XML message format.

Data Exchange with 3M Core Grouping Software

This is a proprietary specification to/from 3M's Core Grouping Software. Medicare OP claims data is sent to the 3M CGS Module. CSG performs APC/APG grouping, reimbursement calculations, OCE and proprietary clams scrubbing; the results are loaded back into Epic where errors can drive claim edits.

Outgoing Dialysis Updates to CMS

Sends Dialysis data to CMS from the Dialysis Module. Requires Nephrology license. This interface uses the XML message format.

Outgoing Family Medical History read the specRead the technical specs

Supports comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. This interface uses the XML message format.

Incoming Family Medical History read the specRead the technical specs

Receives responses to the Outgoing Family Medical History interface, a comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. Enhancements in a future version will allow this interface to operate as an independent standalone interface with additional workflows. This interface uses the XML message format.

Claims Editing Interface (OptumInsight iCES)

Bidirectional claim code editing interface to the OptumInsight iCES code editing product. A code editor is used to scrub a submitted claim and check for errors in coding. Tapestry can then make automatic edits to the claim or hold it for manual review.

Code Editor (Generic)

Bidirectional claim code editing interface that can work with various external systems.

ECG Integration Module (with MidMark)

Midmark ECG system that integrates directly with EpicCare Ambulatory.

Spirometry Integration Module (with MidMark)

Midmark Spirometry system that Integrates with EpicCare Ambulatory.

Holter Integration Module (with MidMark)

Midmark Holter monitor system that Integrates with EpicCare Ambulatory.

Outgoing IHI Verification Query read the specRead the technical specs

Queries the Australian Healthcare Identifiers (HI) Service to retrieve and validate a patient's Individual Healthcare Identifier (IHI) Number. The main goal of this query is to allow modules such as Care Everywhere to interact with PCEHR, which requires valid IHI Numbers for patients when uploading documents. This interface uses the XML message format.

Outgoing Medication Orders to Prescription Exchange Service read the specRead the technical specs

Sends medication orders and receives acknowledgements from a prescription exchange service (currently supported service is eRx). When clinicians create, cancel, or amend medication orders, this XML interface relays the ePrescription information to eRx, which forwards the medication information to the appropriate dispensing facility. This interface uses the XML message format.

Outgoing PAS Data and Response Interface read the specRead the technical specs

Sends patient, referral, administrative pathway, and encounter data grouped by patient episode to the Victorian Integrated Non-Admitted Health (VINAH) database, which is run by the State of Victoria Department of Health. Additionally, this interface receives asynchronous acknowledgments and error information from VINAH. This interface uses the XML message format.

Outgoing Referrals and Booking Confirmation

Manages outgoing referrals communication with external systems according to established MedCom protocols. The interface facilitates sending new referrals composed in Epic and forwarding copies of previously received referral messages. Supported outgoing referral types include hospital, specialist, imaging, physiotherapy, podiatry, and psychology referrals. The interface can also send booking confirmations to inform a patient's referring and primary care physicians when a referral is being acted on in Epic. These notifications can be sent automatically when an appointment has been scheduled, or when a patient is preadmitted or arrived in the ED for an issue relating to the referral. This interface uses the Medcom XML/EDIFACT standard.

Incoming Referrals and Booking Confirmation

Manages incoming referrals communications with external systems according to established MedCom protocols. This interface can both create incoming hospital referrals and file booking confirmation messages for referrals originating in Epic. This interface uses the Medcom XML/EDIFACT standard.

Incoming Pathology Results

Receives pathology test results from a LIS for use in Epic. Results can be received for orders placed in Epic or placed elsewhere. Additionally, this interface can update the status of the results to In Process, Preliminary, Final, or Final-Edited. This interface uses the Medcom XML standard.

Incoming Lab Results Interface

Receives general chemistry, blood bank, and microbiology test results from LIS for use in Epic. Results can be received for orders placed in Epic or placed elsewhere. Additionally, this interface can update the status of the result to In Process, Preliminary, Final, or Final- Edited. This interface uses the Medcom XML standard.

Outgoing Order Requisitions

Sends orders placed by a clinical user to either an external LIS or Danish laboratory outside the organization. This interface supports general chemistry, blood bank, microbiology, and pathology laboratory procedures placed by users in EpicCare Inpatient and EpicCare Ambulatory, and pathology procedures placed by clinical users in OpTime. This interface uses the Medcom XML standard.

Outgoing Municipality Integrations

Manages communication with external municipal systems according to established MedCom protocols to coordinate the delivery of home care after discharge. The outgoing interface supports: Automatic admission and discharge notifications to alert municipalities when their citizens have been admitted to and discharged from the hospital, clinical reports by nursing staff to convey updated clinical information and home care needs to the home care system so they can prepare to assume responsibility for the patient, and administrative notifications to coordinate and document the extension of admissions if the municipality is not yet prepared to accept responsibility for patient care. This integration also includes an incoming interface for filing admission reports sent by municipality home care systems when they receive an admission notification from the hospital. Clinical staff can use these admission reports to review the current status of home care patients. This interface uses the Medcom XML/EDIFACT standard.

Outgoing FMK Medication Card Services Request and Response read the specRead the technical specs

Manages interactions between Epic and the Danish medication database Fælles Medicinkort (FMK), including: Filing medication lists for patients into Epic, pushing medication changes from Epic to the national database, and setting the reviewed status of the medication list by a clinician. This interface uses the Medcom XML standard.

Outgoing FMK Ordered Refill Request and Response

Sends refill requests to the Danish medication database Fælles Medicinkort (FMK) for a patient or an entire facility. This interface uses the Medcom XML standard.

Outgoing Newborn CPR Assignment Request and Response

Registers newborns in the Danish civil registration system (CPR) and reserves a corresponding CPR identifier (national ID). This interface uses the Medcom Webservice standard.

Outgoing ECPR Assignment Request and Response

Requests ECPR identifiers for request a new official ECPR from the Denmark national ECPR registry for non-Danish residents, anonymous, trauma, and unknown patients. This interface uses the MedCom XML Web Service standard.

Outgoing Birth Notification Interface read the specRead the technical specs

Sends a report to register newborns in the municipal child care system and begin coordination of home visits by municipal pediatric nursing after discharge. This interface uses the MedCom XML standard.

Outgoing Binary Documents

Sends binary attachment documents associated with a MedCom message. This interface must work in conjunction with one of the following MedCom interfaces: Outgoing Summary of Care, Outgoing Referrals and Booking Confirmation, Bidirectional Correspondence, and Outgoing Order Requisitions. This interface uses the Medcom XML/EDIFACT standard.

Incoming Binary Documents

Files the binary attachment documents associated with an incoming MedCom message to the Epic WebBlob server. This interface must work in conjunction with one of the following MedCom interfaces: Incoming Summary of Care, Incoming Referrals and Booking Confirmation, Bidirectional Correspondence, Outgoing Municipality Integrations - Incoming Response, Incoming Rehabilitation Plan Summary, Incoming Lab Results, and Incoming Pathology Results. This interface uses the Medcom XML/EDIFACT standard.

Incoming Summary of Care Interface

Files a summary of care document (Epikrise) from an external hospital or specialist as a note to the patient's chart. These notes describe the care that the patient received from the external hospital or specialist and can be used as reference when providing care in Epic. This interface uses the Medcom XML/EDIFACT standard.

Outgoing Summary of Care Interface

Sends a summary of care document (Epikrise) to the patient's referring provider and primary care physician to report the outcome of an ED visit, admission, or ambulatory encounter using a combination of discrete and free-text information. Summary of care messages are automatically sent for the patient whenever a designated Epikrise note has been signed, and the patient's encounter is closed. This interface uses the Medcom XML/EDIFACT standard.

Outgoing Rehabilitation Plan Summary

Sends a summary of the physical therapy/rehabilitation (GGOP) provided for a patient and needs for ongoing therapy/rehab. Frequently used as a way for physical therapists to document ongoing care for a patient, provide progress updates to external parties such as their primary care physician, and transition responsibility for therapy to other entities such as other hospitals or municipality rehabilitation systems. This interface uses the XML (DGOP), GGOP (MedCom XML) standard.

Incoming Rehabilitation Plan Summary

Receives incoming summaries of physical therapy/rehabilitation (GGOP) from physical therapists. This interface can be configured to create scheduling orders, which users can use to plan future appointments for the patient's care. This interface uses the XML (DGOP), GGOP (MedCom XML) standard.

Bidirectional Correspondence Interface read the specRead the technical specs

Sends and receives patient-centric clinical correspondence messages to external parties, including other hospitals, general practitioners, and municipal systems. These messages are used for ad hoc communication to convey additional information beyond what is included in other specifications. This interface uses the Medcom XML/EDIFACT standard.

Outgoing COV Verification Query

The interface queries Vecozo and uses the VZ37/VZ38 standard to retrieve and store insurance information for a patient. This interface uses the VZ37 / VZ38 standard.

Outgoing Perinatal Data read the specRead the technical specs

Submits summary reports at the end of each pregnancy to Perined, a national registry in the Netherlands that records obstetric data. This interface uses the XML HL7 NL standard.

Outgoing Endoscopy Reporting

Sends documents containing colorectal cancer screening information. This interface follows the standards for colorectal cancer screening (ColonIS).

Outgoing Medication Orders

Sends ambulatory medication orders that are placed in Order Entry to the National Electronic Health Record (NEHR) in the format required by the NEHR putOrderedMedications service. This interface uses the XML message format.

Outgoing Medication Dispenses

Sends outpatient medication dispenses to the National Electronic Health Record (NEHR) in the format required by the NEHR putDispensedMedications service. Messages are sent whenever an outpatient medication dispense is received from an internal pharmacy system through an Incoming Medication Orders to EpicCare Ambulatory interface. This interface uses the XML message format.

Outgoing ED Summaries

Sends a clinical summary to the National Electronic Health Record (NEHR) in the format required by the NEHR putEDNotes service. The summary is generated when the patient is discharged or dismissed from the emergency department. This interface uses the XML message format.

Outgoing Discharge Summaries

Sends a clinical summary to the National Electronic Health Record (NEHR) in the format required by the NEHR putDischargeSummary service. The summary is generated upon discharge of a patient. This interface uses the XML message format.

Outgoing Surgical Summaries

Sends a surgical summary to the National Electronic Health Record (NEHR) in the format required by the NEHR putOTNotes service at the time that a surgical log is posted or addended. This interface uses the XML message format.

Outgoing Laboratory Results

Sends laboratory results to the National Electronic Health Record (NEHR) in the format required by the NEHR putLabResults service. This interface uses the XML message format.

Outgoing Radiology Results

Sends radiology results to the National Electronic Health Record (NEHR) in the format required by the NEHR putRadiologyResults service. This interface uses the XML message format.

Incoming Response from NEHR

Receives and files responses from the National Electronic Health Registry (NEHR) related to messages sent by the Outgoing Discharge Summaries, Outgoing ED Summaries, Outgoing Surgical Summaries, Outgoing Medication Dispenses, Outgoing Medication Orders, Outgoing Laboratory Results, or Outgoing Radiology Results interfaces to NEHR.

Incoming Remittance Advice Download to Willow Ambulatory

Files remittance advice retrieved from HAAD using a batch job. This interface uses the HAAD XML standard.

Outgoing Prescription Prior Authorization Request and Response

Submits prior authorization requests to the HAAD post office. This interface uses the HAAD XML standard.

Outgoing Claim Submission from Willow Ambulatory

Submits claims to the HAAD post office. This interface uses the HAAD XML standard.

Outgoing PDS Tracing Query

Outgoing PDS Tracing interface sends queries to the Personal Demographics Services (PDS) master index for NHS patient records. PDS Trace Response messages will be processed by the Incoming PDS Tracing interface. Message interactions follow HSCIC's Message Implementation Manual (MIM) version 7.2.02 and External Interface Specification 11.6. This interface uses the XML message format.

Outgoing PDS Demographics Synchronisation Query

Outgoing PDS Synchronisation interface sends queries for demographics and demographic updates to the Personal Demographics Services (PDS) master index for NHS patient records. PDS Synchronisation Response messages will be processed by the Incoming PDS Synchronisation interface. Message interactions follow HSCIC's Message Implementation Manual (MIM) version 7.2.02 and External Interface Specification 11.6. This interface uses the XML message format.

Outgoing PDS Number Allocation Request for Acute Care

Sends requests to the Personal Demographics Services (PDS) to generate a new NHS number for an adult patient in an acute care setting. PDS NHS Number Response messages will be processed by the Incoming PDS NHS Number Allocation interface. Message interactions follow HSCIC's Message Implementation Manual (MIM) version 6.3.01 and External Interface Specification 11.6. This interface uses the XML message format.

Outgoing PDS Newborn Notification

Sends requests to the Personal Demographics Services (PDS) to generate a new NHS number for a newborn delivery documented in Stork. PDS Create Initial Record Response messages will be processed by the Incoming PDS Create Initial Record Response interface. Message interactions follow HSCIC's Message Implementation Manual (MIM) version 7.2.02 and External Interface Specification 11.6. This interface uses the XML message format.

Incoming Scheduling Slot Availability Query

Receives requests from the eReferral system (aka Choose and Book) to request appointment slots from Cadence. This interface uses the XML message format.

Incoming Referral Scheduling Request Query

Receives requests from the eReferral system (aka Choose and Book) to book an appointment in Cadence. This interface uses the XML message format.

Outgoing Real Time Prescription Benefit Inquiry and Response read the specRead the technical specs

Queries a PBM for a patient's expected costs for a prescription based on their current pharmacy benefits when a clinician creates an order during an order.

Outgoing Newborn Personal Identity Code Request and Response

The Outgoing Newborn Personal Identity Code Request interface sends notifications of patient birth to the Population Register Centre (VRK) in Finland. The Incoming Newborn Personal Identity Code Response interface receives the response message from VRK that contains the HETU for the newborn and assigns the HETU to the patient in Epic.

Outgoing Death Notification

The Outgoing Death Notification interface sends notifications of patient death to the Population Register Centre in Finland.

Outgoing Provider Credential Update

This XML interface queries the Terhikki provider database to determine whether a provider has specific rights and restrictions. The rights and restrictions associated with a provider are used to determine which functionality in Epic the provider has access to.

Outgoing eArchive Documents

This XML interface queries the Kanta eArchive system for document metadata and content. It also sends new and updated documents to Kanta eArchive.

Outgoing Demographics Query

The Outgoing Patient Demographics Query and Incoming Response interface queries the Population Register Centre (VRK) in Finland for a patient’s demographics or the patient’s HETU.

Bidirectional Referrals

This pair of interfaces sends and receives referral and consultation requests, along with triage details and care summaries regarding those referrals.  These messages are structured according to the HL7-Finland PikaXML standard.

Outgoing Social Care Documents

This XML interface queries the Kanta Social Care system for document metadata and content.

Outgoing Prescription Upload Request and Response

Submits a prescription to the UAE Post Office hub for authorization.

Outgoing Prescription Download Request and Response

Downloads a patient's prescriptions from the UAE Post Office hub.

Incoming Receipts read the specRead the technical specs

Receives receipts for messages sent to the VANS network.

Outgoing Receipts read the specRead the technical specs

Sends positive or negative receipt messages for messages received from the VANS network.