Real-Time Remote Patient Monitoring in Epic
Stream vitals from remote monitoring devices straight into the patient's Epic chart — the visit is created and every reading filed automatically.
The workflow
The complete flow, exactly as it runs in the Workflow Builder. Scroll to explore, or use the zoom controls.
Requirements
Set up these connections in the Workflow Builder before importing or running this workflow.
Used to authenticate with Epic and obtain a system access token for all EHR write operations.
Required to submit the standard HL7 messages that open the patient's visit and file each vital reading.
About this workflow
Remote patient monitoring only pays off if the readings actually reach the chart. This workflow takes vitals streamed from a patient's home device — blood pressure, heart rate, oxygen and more — and lands them in Epic in real time. The encounter is created, every reading is filed against it, and nobody has to re-type a single number.
The problem
RPM and home-monitoring devices generate a constant stream of vitals, but that data almost always ends up stranded in a device vendor's portal, disconnected from the EHR. To act on it, a clinician has to log in to yet another system, or someone on staff has to copy the numbers into Epic by hand. That's slow, it's easy to forget, and every manual step is a chance to mistype a value that a care decision depends on.
How it works
A device partner posts a simple JSON payload — the patient, a timestamp, and a list of readings — to a single secure endpoint. The workflow authenticates with Epic to get a system access token, then generates a unique Visit ID that ties everything together.
It builds a standard "open a visit" HL7 message to create the encounter, then maps the readings into a standard "file these results" HL7 message and sends them against that same visit. Each step checks the response before moving on, and a final summary node spells out exactly what was created.
From the device sending data to the reading appearing in Epic, the whole round trip happens in seconds.
Why it matters
Vitals show up where care actually happens — the patient's chart — in seconds rather than hours or days. There's no duplicate data entry, no separate portal for nurses to remember to check, and far fewer transcription errors. Because every message is standard HL7, it works with Epic's existing interfaces and leaves a clean, auditable trail of exactly what was filed and when.
Who it's for
Care teams running remote-monitoring, chronic-care, or hospital-at-home programs, and the device and MedTech partners who need a dependable, standards-based way to push readings into Epic — without building and maintaining a custom integration of their own.
How to build this workflow
Recreate it in the Workflow Builder by wiring these steps in order — or download it above and import it directly.
Step 1: Ingest & Authenticate
Receive the incoming device data over a simple web request, then securely sign in to the EHR to get an access token.
Step 2: Create Encounter Context
Generate a unique Visit ID so the new visit and its clinical data always stay linked to the same patient encounter.
Step 3: Create the Patient Visit
Turn the data into a standard "open a visit" HL7 message and send it to create the patient's visit in the EHR.
Step 4: File the Clinical Data
Map the readings into a standard "file these results" HL7 message and file them against that same visit.
Step 5: Confirm & Summarize
Check the EHR's response and produce a clear success summary so you can see exactly what was filed.