FHIR Workflows
Read and write structured patient data to the EHR using FHIR — the modern data standard behind today's health apps.
About FHIR
FHIR (Fast Healthcare Interoperability Resources) is the modern standard behind today's health apps and APIs. Instead of pipe-delimited messages, FHIR represents clinical data as structured, web-friendly resources — Patient, Observation, Encounter, Condition and more — exchanged over a REST API.
These workflows read and write FHIR resources to the EHR: turning a device reading or an app event into a properly coded Observation, finding the right encounter to attach it to, and creating it in the chart — all authenticated and standards-based.
What you can do
- Read and write FHIR R4 resources — Observation, Encounter, Patient and more
- Map device and app data to coded, standards-based FHIR
- Authenticate with the EHR via SMART backend (B2B) tokens
- Encounter-link every reading so it lands in the right place
Requirements
Set up these connections in the Workflow Builder before running any workflow in this category.
EHR Connection with FHIR R4 API
A connection to an EHR that exposes a FHIR R4 REST API (Epic, Cerner, Azure Health, etc.). Used to read and write resources like Observation, Encounter, and Patient.
SMART Backend (B2B) Credentials
Client credentials issued by the EHR for system-level access — no user login required. The workflow exchanges these for an OAuth token before every FHIR call.
Workflows
2 ready-to-use workflows — open any to see the full flow and download it.
Apple HealthKit Vitals, Straight Into Epic
Turn an Apple Watch or wearable reading into a coded FHIR Observation in the patient's Epic chart — authenticated, encounter-linked, automatic.
Finding a Patient in Cerner
Look up a patient in Cerner by ID, or search by name, birthdate, or identifier — with built-in checks for missing patients, bad requests, and expired logins.