by interface type

See our supported standards

web services

In some cases, we've found that standards didn't exist, weren't sufficient, or were too complicated technically for our customers' use cases. In those cases, we've developed custom web services to serve those needs.

Biometrics

Biometrics, or the reading and recognition of unique biological data, can be used to identify a patient in the EMR. In this scenario, a patient presents for the first time. As part of the registration process, the patient provides a biometric characteristic, such as a thumb scan or a palm vein scan, using an external system. When the patient presents for care in subsequent visits, the biometric characteristic is recalculated and either verified against the stored value or (more rarely) used to uniquely identify the patient again. Current integrations include...
  • Certify (in progress)
  • HT Systems PatientSecure
  • M2SYS RightPatient
  • Safe Match (in progress)
  • TASCET (in progress)

Patient Lookup

This Web service is called by an external system to find a patient record in the Epic EMR. The external system provides the patient name, an identifier, and certain identifying information such as the Social Security number, date of birth, sex, and any location restrictions. If a unique match can be found, the EMR responds with the matching patient's demographics, including name, Social Security number, date of birth, sex, marital status, addresses, emergency contacts, employment information, and care providers. We'll provide you with the specs for this interface at the time we've identified a mutual customer. Current integrations include...
  • InQuicker
  • iTriage

Create Patient

This Web service is used to create a pending patient record in the Epic EMR. The calling system should first determine that the patient record does not exist using the Patient Lookup API. The external system supplies the department, an identifier (such as a Social Security number), and demographics about the patient including the name, date of birth, gender, marital status, race, religion, and addresses. The response from the EMR includes an identifier for the newly created patient record. We'll provide you with the specs for this interface at the time we've identified a mutual customer. Current integrations include...
  • InQuicker
  • iTriage

Assign a Patient Identifier

This Web service is used to prompt the Epic EMR to assign a patient identifier to a patient record in Epic. Alternatively, the external system can provide the MRN to be assigned.

Enterprise Image Access

This web integration API provides the ability to generate dynamic, secure, contextual links used to launch the appropriate context in an enterprise image viewer. You can email us to receive a simple testing harness that will help you validate that your web application can be successfully embedded. Current integrations include...
  • Agfa IMPAX, Agfa IMPAX Cardiovascular Web Viewer, Agfa ICIS
  • Amicas Vericis
  • BRIT
  • Carestream
  • DR Systems
  • Epiphany Cardio
  • Fuji Synapse
  • GE MUSE
  • GE CV Web 2.0
  • GE CCI
  • HeartIT WebPAX
  • McKesson Horizon MI View / DX View
  • Merge / eMed Matrix
  • Merge iConnect
  • Merge Emageon AV Lite
  • Philips EasyVision
  • Philips EasyWeb
  • Philips iSite Enterprise
  • Sectra
  • Siemens MagicWeb
  • Siemens Syngo
  • Vital Images VitreaView
  • Xcelera WebForum

Dining on Demand / Food Service read the specRead the technical specs

If you provide dining on demand or food services to hospitals, this set of JSON-based web services allow you to serve up your menu (pardon the pun) and, if you support it, receive menu choices from a hospitalized patient based on that menu. The flexible architecture supports menus, submenus, nutrition information, and more.

Pharmacy Point of Sale System

This set of Web services are used to integrate Epic's outpatient pharmacy software with a point of sale system. This integration links the fill status of the prescription to the sale status communicated by the point of sale system. Current integrations include...
  • Emporos
  • RMS
  • Counterpoint Keystone
  • Patient Engagement Advisors

Interactive Voice Response

This set of Web services are used to integrate Epic's outpatient pharmacy software with an interactive voice response system. This integration allows the IVR system to initiate a prescription fill and refill authorization when needed. Current integrations include...
  • Ateb
  • Cisco
  • Smart Solutions
  • Symago
  • Telemanager
  • VoiceTech

Active Guidelines

The Active Guidelines (AGL) activity in the Epic EMR uses the HL7 InfoButton standard to allow clinicians to retrieve targeted information provided by third parties, specific to the context of the patient or clinical workflow. Rather than searching third party knowledge base, searches are performed automatically based off elements of the patient's chart like diagnoses or orders. The third party can also provide actionable links that queue up specific orders within the Epic EMR. Current integrations include...
  • Clin-eguide
  • ClinicalKey
  • Dynamed
  • Facts & Comparisons
  • Isabel
  • KidsHealth
  • Lexicomp
  • MedlinePlus
  • Micromedex
  • Pub Med
  • UpToDate
  • VisualDx

QRDA I

Users can create QRDA I documents from data in their Epic EMR. Each QRDA I document is specific to one patient and contains data pertinent to quality measure reporting. QRDA I documents are typically used by hospitals for quality measure submissions, and the format can also be used by individual providers. Many regulatory programs, including Meaningful Use, Core Measures, PQRS, Inpatient Quality Reporting, and ORYX Performance Measurement Reporting, accept QRDA I documents to satisfy their quality reporting requirements.

QRDA III

Users can create QRDA III documents from data in their Epic EMR. 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 and PQRS, accept QRDA III documents to satisfy their quality reporting requirements.

External Decision Support Functionality

This family of APIs is used to provide external decision support to the clinician at the point of order entry. Possible uses include medical necessity checking or genomic analysis performed in an external system and used to inform better care in the EHR. We'll provide you with the specification for this integration as you work with a member of the Epic community. Current integrations include...
  • ACR Select
  • Medicalis

Clinical Reference Material read the specRead the technical specs

Epic's Active Guidelines activity allows providers to search clinical reference websites for information relevant to their patients. Searches are triggered from within the provider's workflow and are specific to the context of the medication, procedure, diagnosis, allergy, lab result, or symptom. Reference material can be further refined based on user, patient, or language. This is Epic's implementation of the InfoButton standard.

Single Sign On

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.

Content Linking

The patient portal provides patients with a view into the medical chart maintained by their healthcare organization. This information can be supplemented by educational materials that are specific to a patient's problems, medications, and other information. This functionality is called Content Linking. While many approaches have been used to achieve this integration in the past, Epic recommends that new organizations use the Infobutton APIs as they are implemented through the National Library of Medicine and MedlinePlus. Current integrations include...
  • A.D.A.M.
  • ExitCare
  • Healthwise
  • KidsHealth
  • Krames-Staywell
  • Lab Tests Online
  • McKesson
  • National Library of Medicine MedlinePlus

E-Signature

Epic's kiosk software can be used to collect signatures for consent or other purposes. These signatures can then be sent to an external document management system. The kiosk sends an image of the signature to the document management system, which in turn creates a reference to the signature document within the EMR.

Interactive Voice Response - Billing

This integration allows external interactive voice response systems to provide billing information to patients. While we have implemented both HL7v2 and Web service-based versions of this integration in the past, Web services are preferred for new collaborations. Current integrations include...
  • Cisco/Nexus
  • Digital DataVoice
  • Ergonomic Group, AT&T
  • Interactive Intelligence
  • Syntellect

Credit Card and Bank Account Integration read the specRead the technical specs

Epic provides support for credit cards to be used with the EMR to pay copays, hospital and outpatient bills, and for medications. This integration is handled through credit card gateway systems, which send payment data to processing services that verify the payments with appropriate banks. The gateway then sends the verified payment information back to the EMR to post the payment. This integration is handled through the patient portal and patient kiosk software as well as in over-the-phone and billing-office use cases. Epic software for credit card processing follows the PA-DSS requirements in its development. Current integrations include...
  • Authorize.Net
  • Bluefin Payment Systems
  • ClaimsXpress
  • CORE
  • CyberSource
  • DivDat Healthcare Solutions
  • eBizCharge
  • Experian Health
  • HealthPay24
  • InstaMed Connect
  • iPayX
  • Merchant e-Solutions
  • MyVirtualMerchant
  • Payflow Pro
  • PayPal
  • Salucro
  • Secure Bill Pay
  • Tempus Technologies
  • TrustCommerce
  • US Bank
  • Wells Fargo
  • VirtualMerchant

Outgoing COV Verification Query

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

Web Service Engines

Although Epic software comes with its own web service library and engine, Interconnect, an additional integration layer on top of these web services can be useful for orchestration, performance, and interpretation. Current integrations include...
  • MuleSoft

Computer-Telephony Integration explore the specExplore the technical specs

This functionality is used to integrate Epic with an organization's phone system. When your system receives an incoming communication about a patient, this service can open and populate an appropriate activity in Epic's desktop software for the user who receives the call. Epic can also interface with your web dialer to begin and log outgoing calls, based on your custom schema You can email us if you have a schema you are interested in integrating within Epic. Current integrations include...
  • Cisco (outgoing calls)

Environmental Services explore the specExplore the technical specs

This family of web services is used to integrate Epic's environmental services with an exteral call system. Current integrations include...
  • Vocera

System Health

This family of web services returns information about database server health. Callers can retrieve more information about the types of resources and logs available, as well as any current alerts. We'll provide you with the specs for this interface at the time we've identified a mutual customer.

Incoming Personnel Management explore the specExplore the technical specs

This interface is used to integrate more tightly with an external personnel management system. Unlike the Provider Information system, it is used more broadly to update the Epic system with any employee of the healthcare organization, including those who will not provide clinical care. It can be implemented through traditional HL7v2 interfaces or via Web services (recommended). Current integrations include...
  • Microsoft ProVision
  • Courion AccountCourier
  • Microsoft Forefront Identity Manager
  • NetIQ Identity Manager

Read a Provider's Schedule

This API is used by external systems that need to determine open slots on a provider's schedule for appointments. We'll provide you with the specs for this interface at the time we've identified a mutual customer. Current integrations include...
  • HealthGrades
  • iTriage
  • InQuicker

Schedule Appointment

This family of APIs is used by external systems to create an appointment for a provider. The caller provides a patient ID, the department, the provider, the visit type (which determines the visit length and other scheduling details), the time and date of the appointment, and any comments that should be displayed with the visit. A separate service is used to cancel scheduled appointments. We'll provide you with the specs for this interface at the time we've identified a mutual customer. Current integrations include...
  • HealthGrades
  • iTriage
  • InQuicker