By Interface Type

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.
All web services require a client ID to identify the calling application as part of the Epic authorization framework. When you are ready to use the web services listed below with an Epic customer, please submit an email request to be provisioned an Epic client ID.
Sign up with our App Orchard developer program for access to a sandbox to test with these services.

Encoder Interface API read the specRead the technical specs

The GetEncoderMessage and SetEncoderMessage APIs are used to integrate with encoders and computer-assisted coding systems to exchange information for Hospital Coding workflows. Epic offers front-end integrations through web services as well as back-end integration methods. To see the HL7 payload, check out the HL7v2 - Coding-Bidirectional spec.

Patient Lookup and Identifiers read the specRead the technical specs

Search for patients and obtain or assign identifiers. If no patient can be found for the given criteria, a patient record can be created.

Personnel Management read the specRead the technical specs

Create, update, and delete user records in Epic. With this suite of services, you can also view and update user groups, pager IDs, user login departments, and departments the user has access to.

Phone System Pause/Resume read the specRead the technical specs

When collecting credit card payments over the phone, you may not want the credit card number (as read by the patient) to be contained in the customer service recording files. This web service can be setup to send a request to the phone system to pause the recording when the staff's credit card entry form opens, and send another request to the phone system to resume the recording when the credit card form closes.

Print Job Status read the specRead the technical specs

Use the UpdatePrintJobStatus API to send back information about the status of the print job that you received from Epic through Epic Print Service (EPS).

Release of Information read the specRead the technical specs

Create and update release of information (ROI) requests.

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 use our simple testing harnessto help you validate that your web application can be successfully embedded.
Current integrations include...
  • Agfa IMPAX, Agfa IMPAX Cardiovascular Web Viewer, Agfa ICIS
  • Ambra Health
  • Amicas Vericis
  • BRIT
  • Carestream
  • DR Systems
  • Epiphany Cardio
  • eUnity (Client Outlook)
  • Fuji Synapse
  • GE MUSE
  • GE CV Web 2.0
  • GE CCI
  • HeartIT WebPAX
  • Hyland Healthcare NilRead Enterprise Viewer
  • 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

Active Guidelines read the specRead the technical specs

The Active Guidelines (AGL) activity in the Epic EHR 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.
Current integrations include...
  • Clin-eguide
  • ClinicalKey
  • Dynamed
  • Facts & Comparisons
  • Isabel
  • KidsHealth
  • Lexicomp
  • MedlinePlus
  • Micromedex
  • Pub Med
  • UpToDate
  • VisualDx

Content Linking read the specRead the technical specs

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 read the specRead the technical specs

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

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

Epic provides support for credit cards to be used with the Epic system 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 Epic system 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...
  • ABILITY Network
  • Bluefin Payment Systems
  • ClaimsXpress
  • CORE Business Technologies
  • DivDat Healthcare Solutions
  • eBizCharge
  • Elavon
  • Experian Health
  • HealthPay24
  • InstaMed Connect
  • iPayX
  • Merchant e-Solutions
  • MyVirtualMerchant
  • Patientco
  • Paymentus
  • PayPal
  • Phreesia
  • RevSpring
  • Salucro
  • Tempus Technologies
  • TrustCommerce
  • US Bank
  • Wells Fargo
  • VirtualMerchant
  • WayStar

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 Computer-Telephony Integration explore the specExplore the technical specs

Epic integrates with your organization’s phone system to automatically open the appropriate chart or another activity in Epic when calls are received.
Current integrations include...
  • Atos
  • Avaya
  • Cisco
  • Mitel

Outgoing Computer-Telephony Integration read the specRead the technical specs

Epic integrates with your organization’s phone system so users can place or end a call directly from a patient chart or another activity in Epic, and details about the call are logged. Your phone system can also update Epic with the call identifier after the call.

Outbound Fax Services with Epic Print Service read the specRead the technical specs

Epic integrates with fax management systems using the outbound faxing web service. This web service allows Epic community members to fax documents generated by various applications from their instance of Epic, and receive back information about whether the transmission was successful.

SAML 2.0 Reauthentication for Haiku and Canto EPCS read the specRead the technical specs

Haiku and Canto, Epic's mobile apps for physicians on iOS and Android devices, support launching a web portal during e-prescribing controlled substances (EPCS) to verify the physician's identity with an EPCS-qualified identity provider (IdP). The IdP returns a valid SAML assertion to Haiku or Canto, which allows the physician to continue placing orders. This process follows the SP-initiated Web Browser SSO profile defined in the OASIS SAML 2.0 specification. The workflow is also supported in Rover, Epic's mobile app for nurses, on iOS devices only.

Image Retrieval read the specRead the technical specs

This web integration enables Epic to request images, image pages, and thumbnails for images in an external system. Epic will then display these images inline within the user's workflow.

Outgoing MDS Data for MDS Scrubbers read the specRead the technical specs

The Minimum Data Set (MDS) scrubber interface allows MDS coordinators to send in-progress and completed MDS assessments electronically to a 3rd-party MDS scrubbing vendor and receive real-time feedback.

EPS Document Retrieval Web Service read the specRead the technical specs

This web service 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.