By Interface Type

Other Integrations

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

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.

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. This interface uses messages expresssed in XML encoding syntax.
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 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. This interface uses the XML message format.
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. This interface uses the XML message format.
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

Health Care Claim Code Editor - Outgoing

Tapestry sends outgoing health care claim code edit requests through proprietary transactions.

Health Care Claim Grouper and Pricer - Outgoing

Tapestry sends outgoing health care claim grouper and pricer requests through proprietary transactions.

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 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.
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.

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. This interface uses the Medcom XML/EDIFACT standard.
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. This interface uses the Medcom XML/EDIFACT standard.
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. This interface uses the Medcom XML/EDIFACT standard.
Current integrations include...
  • MEDCOM Information Systems

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. This interface uses messages expressed in XML encoding syntax.
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. This interface uses the Medcom XML/EDIFACT standard.
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

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

Sends Dialysis data to CMS from the Dialysis Module. Requires Nephrology license. This interface uses the XML message format.
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. This interface uses the MedCom XML standard.
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. This interface uses the MedCom XML Web Service 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.
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 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. This interface uses the XML message format.

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

This interface 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. The interface can be configured with a set of conditions for which treatment data should be sent to your public health agency.
Current integrations include...
  • Merge
  • Oregon Health Authority

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 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.

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

The Outgoing Death Notification interface sends notifications of patient death to the Population Register Centre in Finland.
Current integrations include...
  • Digi- ja väestötietovirasto

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

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

QRDA

Users can create QRDA Idocuments from data in their Epic EMR. 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 Social Care Document Query

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

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

External Application Linking

The Epic EMR provides a robust framework for launching external applications via OASIS SAML 2.0’s Identity Provider-initiated use case with HTTP Post binding as well as the HL7 SMART on FHIR profile of the OAuth 2.0 authorization code grant type. The launch, because it is triggered from within the EMR, can provide simple contextual information based 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.

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

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.