By Interface Type

Other Integrations

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

Outgoing Real Time Prescription Benefit Inquiry and Response

Supports real-time prescription benefits checking (RTPB) during the prescriber ordering process. This feature lets prescribers see expected out-of-pocket costs, lower-cost medication suggestions, and whether additional approvals from the insurance company are needed before the prescription can be filled. Providers can share this information with patients before sending the order to the pharmacy, saving time and money for patients, and help improve medication adherence.
Payers/vendors who are interested in joining the RTPB network, please please reach out for more information.
Current integrations include...
  • CenterX
  • CoverMyMeds
  • DrFirst
  • Humana
  • RxRevu
  • Surescripts

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.
Current integrations include...
  • Digi- ja väestötietovirasto

Outgoing Death Notification and Response

Sends notifications of patient death to the Population Register Centre in Finland.
Current integrations include...
  • Digi- ja väestötietovirasto

Outgoing Provider Query

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 and Query

Queries the Kanta eArchive system for document metadata and content and sends new and updated documents to Kanta eArchive. Licensing for this interface includes the Outgoing eArchive Document Query interface.

Outgoing Demographics Query

Queries the Population Register Centre (VRK) in Finland for a patient's demographics or the patient's HETU.
Current integrations include...
  • Digi- ja väestötietovirasto

Outgoing QRDA Documents read the specRead the technical specs

Users can create QRDA Idocuments from data in their Epic EHR. Each QRDA I document is specific to one patient and contains data pertinent to quality measure reporting. Each QRDA III document includes aggregated quality measurement data for a provider or group of providers, including the quality measures they are reporting on and their performance rate. QRDA III documents are typically used by providers for quality measure submission. Many regulatory programs, including Meaningful Use, Core Measures, Inpatient Quality Reporting, ORYX Performance Measurement Reporting, and PQRS, accept QRDA documents to satisfy their quality reporting requirements.

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 Document Notification Interface - Finland

Sends document metadata to Navitas when Navitas queries Epic for a document ID.

Outgoing Social Care Document Query

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

Outgoing Dental Summary Interface - Singapore

Sends a PDF report of the state of the patient's teeth. Requires Wisdom, Epic's dental product.

Outgoing Referral and Provider Communication Notification Interface - Singapore

Sends a notification to the National Electronic Health Record (NEHR) when referrals are entered in Epic or provider communications are written in the Communication Management activity in Epic.
Current integrations include...
  • Singapore Ministry of Health Holdings

Outgoing Demographics Query Interface - Singapore

Queries the National Electronic Health Record (NEHR) system in Singapore for a patient's demographics information.
Current integrations include...
  • Singapore Ministry of Health Holdings

Outgoing Infection Reporting to NHSN Interface

Automates the reporting of Infection data to NHSN.

Outgoing Transaction Notification Interface - Belgium

Interface for Belgium. Sends metadata for notes, letters, results, and scans to the National Hub. This process allows the Hub to index references to the source content for external providers to request.

Outgoing Transaction Query Interface - Belgium

Interface for Belgium. A collection of web services invoked from the Chart Review activity that retrieve a list of documents for a patient from the National Hub and request the contents of specific documentation.

Outgoing Birth Notification and Medical Form Interface - Belgium

Sends birth notifications and birth-related medical forms to Belgium's eBirth registry according to the specifications in the eBirth Hospital Web Services Technical User Guide - Final version - 1.6 – 12/05/2016.

Outgoing Medication Orders Request and Response Interface - Belgium

Interface for Belgium. Sends e-prescribing messages to, and receives acknowledgements from, Recip-e. These interfaces can be used to create new prescriptions, cancel prescriptions, and query for a list of prescriptions that a pharmacy can dispense.

Outgoing Social Care Need Query Interface - Finland

Queries the eTotu Social Services system for patient referrals and documents.

Outgoing Financial Transactions Query Interface - Belgium

Sends charges to and receives charge verifications from an external system. Billing-related errors logged by this interface are routed to Charge Router workqueues, which enables users to correct errors and resubmit affected messages in real time.

Outgoing Imaging Document and Response Interface - Finland

Sends reference links for R2CDA imaging documents to Navitas and receives acknowledgements in return.

Outgoing External Encounters

Sends HL7v2 ADT messages using data filed as external encounters in Received Documents records and using message data filed on the Incoming External Encounters interface. This is intended for use with Payer Platform.

Tapestry External PPS Claims Pricer Interface (Generic)

Sends claims to external pricer system.

Incoming Health Care Services Authorization Interface - Netherlands

Receives notifications from VECOZO when the status of an authorization request has changed. The incoming interface can update authorization records (RFL or AUT) in Epic, which drive referral workqueue and scheduling workflows.

Incoming Scheduling Slot Availability Query

Receives requests from the United Kingdom's NHS e-Referral Service (also known as Choose and Book) to request appointment slots from Cadence, Epic's scheduling system.
Current integrations include...
  • National Health Service

Outgoing PDS Tracing Query

Outgoing PDS Tracing interface sends queries to the Personal Demographics Services (PDS) master index for National Health Service (NHS) patient records in the United Kingdom. PDS Trace Response messages are 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 messages expressed in XML encoding syntax.
Current integrations include...
  • National Health Service
  • PDS

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 National Health Service (NHS) patient records in the United Kingdom. PDS Synchronisation Response messages are 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 messages expressed in XML encoding syntax.
Current integrations include...
  • National Health Service
  • PDS

Outgoing PDS Number Allocation Request for Acute Care

Sends requests to the Personal Demographics Services (PDS) to generate a new National Health Service (NHS) number for an adult patient in an acute care setting in the United Kingdom. PDS NHS Number Response messages are 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 messages expressed in XML encoding syntax.

Outgoing PDS Newborn Notification

Sends requests to the Personal Demographics Services (PDS) to generate a new National Health Service (NHS) number for a newborn delivery documented in Stork within the United Kingdom. PDS Create Initial Record Response messages are 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 messages expressed in XML encoding syntax.
Current integrations include...
  • National Health Service
  • PDS

Outgoing Medication Orders

Sends outgoing e-prescribed medication orders, following Dutch HL7 v3 Standards
Current integrations include...
  • CompuGroup Medical
  • Nictiz

Outgoing Medication Dispense 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.

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

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.
Current integrations include...
  • Singapore Ministry of Health Holdings

Tapestry Outgoing Health Care Claim: Professional - 837 (batch)

Sends professional claim information to payers. The 837 transmits claim information either for the purpose of payment, such as a provider sending a bill to a payer, or for the purpose of reporting, such as a delegated risk payer sending payment information to a health plan or the government.

Outgoing Health Care Claim Code Editor

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

Outgoing Health Care Claim Grouper and Pricer

Bidirectional interface that analyzes claims to determine which codes and prices are appropriate, and can work with various external systems.

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.
Current integrations include...
  • MEDCOM Information Systems

Bidirectional Correspondence 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.
Current integrations include...
  • MEDCOM Information Systems

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 Web Service 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.
Current integrations include...
  • autonik ab
  • CGI
  • Databyrån AB
  • DXC Technology
  • Region Midtjylland Microbiology Department

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.
Current integrations include...
  • autonik ab
  • CGI
  • Databyrån AB
  • DXC Technology
  • Region Midtjylland Microbiology Department

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. 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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • General Data
  • LUMEDX
  • Philips
  • TSG Integrations

Incoming Referral Scheduling Request Query

Receives requests from the United Kingdom's NHS e-Referral Service (also known as Choose and Book) to book an appointment in Cadence, Epic's scheduling system.
Current integrations include...
  • National Health Service

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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • MEDCOM Information Systems

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 & Human Services in Australia. Additionally, this interface receives asynchronous acknowledgments and error information from VINAH. This interface uses messages expressed in XML encoding syntax.
Current integrations include...
  • Victoria Department of Health and Human Services

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 FMK Medication Card Services Request and Response read the specRead the technical specs

Manages interactions between Epic and the Danish medication database Falles 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.

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

Sends medication orders and receives acknowledgements from a prescription exchange service (the 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 Dialysis Updates to CMS read the specRead the technical specs

Sends Dialysis data to CMS from the Dialysis Module. Requires Nephrology license.
Current integrations include...
  • CMS
  • South Dakota Department of Health

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.
Current integrations include...
  • MEDCOM Information Systems

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.

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.
Current integrations include...
  • MEDCOM Information Systems

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.
Current integrations include...
  • MEDCOM Information Systems

Outgoing Prescription Prior Authorization Request and Response

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

Outgoing Claim Submission from Willow Ambulatory

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

Incoming Remittance Advice Download to Willow Ambulatory

Downloads remittance advices that are stored in HAAD post office using a batch job. This interface uses the HAAD XML 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 National Healthcare Survey Interface read the specRead the technical specs

Reports National Healthcare Survey data to the Centers for Disease Control and Prevention (CDC).

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 My Health Record, which requires valid IHI Numbers for patients when uploading documents.

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 Initial Public Health Case Report read the specRead the technical specs

Satisfies the Meaningful Use objective to send Electronic Case Reports to public health agencies using the HL7 Clinical Document - Electronic Initial Case Report (CDA-eICR) format.
Current integrations include...
  • APHL
  • Center for Disease Control
  • North Carolina Division of Public Health
  • Oregon Health Authority
  • Surescripts

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.

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.

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

Clinical Document Architecture (CDA) read the specRead the technical specs

Care Everywhere is used to exchange patient data with other healthcare institutions, HIEs, and government agencies during point-of-care treatment and care coordination workflows. We use Clinical Document Architecture (CDA) as the content standard. CDA is an XML-based markup standard defined by Health Level Seven (HL7), intended to specify encoding, structure and semantics of clinical documents for the purpose of exchange. Care Everywhere supports the exchange of document defined in the Consolidated CDA (C-CDA) framework, which is required for ONC 2015 Edition certification for Meaningful Use.
  • Epic's EHR can consume any valid C-CDA or CDA document.
  • Epic's EHR can create the following documents:
    • HL7/ASTM CCD (HITSP C32 Implementation)
    • HL7/IHE Consolidated CDA (CCD and Progress Notes Template)

Contact us if you have questions about our CDAs.

Clinical Context Manager Integration read the specRead the technical specs

CCOW (formerly known as Clinical Context Object Workgroup) is a vendor-independent HL7 standard protocol designed to allow disparate clinical applications to synchronize data in real-time at the point of care. Epic can integrate as a participant with a third-party clinical context manager.
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

Cash Management read the specRead the technical specs

This incoming batch interface creates a record of deposits for cash reconciliation using a configurable flat file format. The flat file is configurable and the preferred format is in the linked specification, however Epic can also support industry standard formats such as CCD+.

Incoming Claim Status - Flat File read the specRead the technical specs

This incoming batch interface loads information about claim status via a configurable flat file. This interface can update the status of claims in the system and is able to load claim error information from payer and intermediary systems.

The flat file format is configurable, but the common specification is pre-configured in the Foundation System for Epic customers and widely used with success.
Current integrations include...
  • Availity
  • Cirius
  • Change Healthcare
  • eSolutions
  • Experian Health
  • Healthcare IP
  • InstaMed
  • nThrive
  • Optum
  • Quadax
  • SSI
  • TriZetto Provider Solutions, a Cognizant Company
  • WayStar

Monthly Premium Withholding Report (MPWR) read the specRead the technical specs

Transmits premium information to Medicare Advantage plans.

Outgoing 1095-B (Simple) read the specRead the technical specs

The 1095-B is a flat file for tax information.

Outgoing 1099-MISC read the specRead the technical specs

The 1099-MISC tax form is used to report miscellaneous income for Vendors from an AP Cycle processing.

Batch Eligibility Query (BEQ) read the specRead the technical specs

Outbound BEQ request and Incoming BEQ response. BEQ is a way for plans to submit batches of individuals for verification of various eligibilities.

SAML 2.0 Idp-initiated Single Sign-On (SSO) read the specRead the technical specs

Epic supports launching an external app with SAML 2.0. The SAML 2.0 Identity Provider initiated workflow initiates from Epic, playing the SAML role of Identity Provider. Implementation requires the exchange of an x509 certificate, which is used to sign the SAML claims. This process follows the OASIS SAML 2.0 specification. Epic recommends the use of SMART on FHIR over SAML if possible.

Single Sign-On (SSO) into MyChart read the specRead the technical specs

Typically, the patient portal manages all aspects of patient and user identity. However, a single-sign on integrator could be used to link together the Epic patient portal with other portal-based functionality already in use. In this scenario, usernames and passwords are managed by an external system. The patient logs into the external system, which then can be used to also sign the patient into MyChart. A bundle of Web services are used to create and update patient records and to create and manage proxy relationships. We'll provide you with the specs for this interface at the time we've identified a mutual customer.
Other systems can provide SSO integration into Epic applications like EpicWeb, EpicCare Link, Tapestry Link, or OutReach by passing user and optionally patient context.

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.

Incoming Receipts read the specRead the technical specs

Receives receipts for messages sent to the VANS network in relation to the Medcom message sent.

Outgoing Receipts read the specRead the technical specs

Sends positive or negative receipt messages for Medcom messages received from the VANS network using the Medcom XML/EDIFACT standard.

Incoming External Clinical Data read the specRead the technical specs

As organizations extend Epic to affiliated practices in their communities, there has been an increasing need to convert historical patient-level data from other vendors' systems into Epic. This interface allows organizations to load patient-level data from organizations that do not otherwise support standards-based data exchange.

Paid Claims Import read the specRead the technical specs

Paid claim data can be imported into Epic to support population health and care management workflows by reconciling the data with the rest of the comprehensive medical record. This format is recommended when the data is can be manipulated or the extract is flexible to simplify the process of importing into Epic.
Current integrations include...
  • Health Data Innovations
  • Milliman

EDManager read the specRead the technical specs

This set of APIs allow external applications that are running alongside Epic Hyperspace to programmatically take certain actions, such as logging in/out and launching activities. They also provide the ability to query Epic Hyperspace for information, as well as to be notified when key events occur. These APIs are commonly used for automating external-driven workflows, most notably logins.

Desktop Generic Authentication read the specRead the technical specs

This interface allows external authentication software to implement authentication devices for use in Epic. The external authentication software can write installable devices that can be configured for use as devices to authenticate a user for login into Epic or to re-authenticate the user after login (for example, to sign off on medications).

Scan Acquisition read the specRead the technical specs

This COM integration enables users to seamlessly launch an external scan acquisition interface from Epic. Epic can pass the user's active context information, such as the patient, encounter, or order.

Scan Viewing read the specRead the technical specs

This COM integration enables Epic to display an ActiveX scan viewing control in a modeless floating window. The user can interact with both the viewer and Epic, and Epic will manage closing the window if the user's patient context changes.

EPS Document Retrieval Plugin read the specRead the technical specs

This .NET integration enables Epic print services (EPS) to query a document management system (DMS) for images or documents to insert into a print job. This is useful when you want a scan to be stored in your DMS, but want to include that scan in something you print. We recommend new implementations use the EPS Document Retrieval Web Service instead of this.