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)
• Impravata PatientSecure
• M2SYS RightPatient
• Safe Match (in progress)
• TASCET (in progress)

This flat file import from an external system allows organizations to automatically apply address corrections for account guarantors or flag bad addresses for follow-up. Current integrations include...

• Experian Health
• Patientco

This bi-directional real-time query is used to verify eligibility with clearinghouses and payors. It uses ANSI X12 270/271 transactions. Current integrations include...

• AccuReg
• Aetna
• Anthem
• Availity
• Change Healthcare
• Cigna
• ClaimLogic Patient Eligibility
• DCS Global AuditLogix
• Experian Health
• Gateway EDI
• Group Health Cooperative (Seattle)
• HDX
• Health Alliance Plan
• HealthCare Fiscal Management Inc.
• Healthcare IP
• HealthPartners
• Highmark
• InstaMed
• Loxogon
• MedAssets
• Medicaid Minnesota
• Medicaid New York
• Medicaid Pennsylvania
• Medicaid Texas
• Medicaid Washington
• Medicaid Wisconsin
• Medicare
• NEHEN
• nThrive
• Optima
• Optum
• Physicians Plus
• Post-n-track Eligibility
• Preferred One
• Provider Advantage
• Quadax
• Recondo Technology
• RelayHealth
• Rycan
• The Advisory Board Company
• The SSI Group
• TransUnion
• Tricare
• United Healthcare
• Unity
• UPMC Health Plan
• VisionShare (ABILITY Network)
• WayStar
• WNY HealtheNet

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

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

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.

This bidirectional X12 278 interface is used to notify a payor or health plan that a patient has been admitted. The request can be done real-time or in batches. Current integrations include...

• Aetna
• Experian Health
• Loxogon
• HealthCareIP
• Post-N-Track
• United Healthcare

This integration allows the active patient context to be shared among multiple systems. A CCOW context manager helps coordinate all applications to open the same patient record, streamlining end user workflows that cross system boundaries. Current integrations include...

• Caradigm
• CareFx

This basic FHIR service covers data about persons (or, technically, animals, although despite all our jokes about cows, we aren't really pursuing) receiving care or other health-related services. It focuses on the demographic information necessary to support administrative, financial, or logistic purposes. We support search, read, and create interactions for Patient, and search and read interactions for Provider.

Supports comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. This interface uses the XML message format.

Receives responses to the Outgoing Family Medical History interface, a comprehensive risk assessment following the HL7 Version 3 Implementation Guide for Family History/Pedigree Interoperability, Release 1 - US Realm April 2013. Enhancements in a future version will allow this interface to operate as an independent standalone interface with additional workflows. This interface uses the XML message format.