Epic on FHIR

When everyone's on the same page, technology can make cool things happen. Epic is a strong supporter of the HL7® FHIR® standard as the future of REST-based interoperability. In addition to participating in the standards development process with HL7, Epic is also a member of the Argonaut Project and the Da Vinci Project, each aimed at accelerating the adoption of FHIR.

Epic's work with FHIR means that any health system, hospital, or clinic that uses Epic's comprehensive health record system can connect to any app that also supports FHIR to exchange health information, including but not limited to the U.S. Core Data for Interoperability – or USCDI - data classes and elements.

Interoperability Guide Check out our guide.

Sign Up to Access

Epic on FHIR is a free resource for developers who create apps for use by patients and healthcare organizations.

Sandbox logo

Testing Sandbox

Test APIs against example data

Registration logo

Client Registration

Software registration and client identifier management

Documentation logo

Documentation

Additional developer support documentation

Summary of Resources

  • Binary (CCDA Documents)

  • Read DSTU2
  • Binary (Clinical Notes)

  • Read R4
  • Read STU3
  • Binary (Correspondences)

  • Read R4
  • Read STU3
  • Binary (External CDAs)

  • Read R4
  • Binary (Handoff)

  • Read R4
  • Binary (HIS)

  • Read R4
  • Binary (Labs)

  • Read R4
  • Binary (OASIS)

  • Read R4
  • Binary (Practitioner Photo)

  • Read R4
  • Binary (Radiology Results)

  • Read R4
  • Read STU3
  • CarePlan (Encounter Level Care Plan)

  • Read, Search R4
  • CarePlan (Encounter-Level, Longitudinal)

  • Read, Search DSTU2
  • CarePlan (Inpatient CarePlan)

  • Read, Search R4
  • CarePlan (Inpatient Pathway)

  • Read, Search R4
  • CarePlan (Longitudinal Care Plan)

  • Read, Search R4
  • CarePlan (Outpatient CarePlan)

  • Read, Search R4
  • CarePlan (Questionnaires Due)

  • Read, Search R4
  • CareTeam (Episode Care Team)

  • Read, Search R4
  • CareTeam (Longitudinal Care Team)

  • Read, Search R4
  • Condition

  • Create CDS Hooks - STU3
  • Condition (Care Plan Problem)

  • Read, Search R4
  • Condition (Encounter Diagnosis, Problems)

  • Read, Search STU3
  • Condition (Reason for Visit)

  • Read, Search R4
  • Device (External Devices)

  • Read R4
  • Device (Implants and External Devices)

  • Read, Search STU3
  • DeviceUseStatement (External Devices)

  • Read, Search R4
  • DeviceUseStatement (Implants and External Devices)

  • Read, Search STU3
  • DeviceUseStatement (Implants)

  • Read, Search R4
  • DocumentReference (CCDA Documents)

  • Read, Search DSTU2
  • DocumentReference (External CDAs)

  • Read, Search R4
  • List (Patients With Questionnaires Due List)

  • Read, Search STU3
  • Observation (SmartData Elements)

  • Read, Search R4
  • Procedure (Surgical History)

  • Read, Search R4
  • Provenance

  • Read R4
  • Questionnaire (Patient-Entered Questionnaires)

  • Read, Search R4
  • QuestionnaireResponse (Code Status)

  • Read R4
  • QuestionnaireResponse (Patient-Entered Questionnaires)

  • Read, Search, Create R4
  • RelatedPerson

  • Read R4
  • Schedule

  • Read STU3
  • ServiceRequest (Community Resource)

  • Read, Search R4
  • ServiceRequest (Dental Procedure)

  • Read R4
  • ServiceRequest (Referral)

  • Read R4
  • ServiceRequest / ProcedureRequest

  • Read, Search STU3
  • ServiceRequest / ProcedureRequest (Orders)

  • Read, Search R4
  • Slot

  • Read STU3