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.Sign up with our App Orchard developer program for access to a sandbox to test with these services.
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
- Ambra Health
- Amicas Vericis
- 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
- Siemens MagicWeb
- Siemens Syngo
- Vital Images VitreaView
- Xcelera WebForum
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.
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.
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.
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.
Credit Card and Bank Account Integration
read the spec
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...
- ABILITY Network
- Bluefin Payment Systems
- CORE Business Technologies
- DivDat Healthcare Solutions
- Experian Health
- InstaMed Connect
- Merchant e-Solutions
- Tempus Technologies
- US Bank
- Wells Fargo
Outgoing COV Verification Query
The interface queries Vecozo and uses the VZ37/VZ38 standard to retrieve and store insurance information for a patient.
Incoming Computer-Telephony Integration
explore the spec
Epic integrates with your organization’s phone system to automatically open the appropriate chart or another activity in Epic when calls are received.
Outgoing Computer-Telephony Integration
read the spec
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.
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).