Care between visits, filed in your record.
The most common question a prospect asks is what actually reaches the chart. This page answers it end to end — what travels, where it lands, and who checks it on the way.
From an out-of-range reading to a filed charge.
From the alert to the encounter
- An alert firesA reading crosses its threshold. A navigator acts on it and documents the work.
- The note is reviewedChecked before it reaches your record — every note, not a sample of them.
- Vitals and note file to the encounterBoth land in a unique encounter in the patient’s record — not in a vendor portal.
- Your providers review it thereAll the vitals and documentation, inside the encounter.
Charges file to the same encounterThe billing support drops against the documentation your providers just reviewed — one place, organized for any audit.
80+ EHRs with bi-directional interfaces (acute and ambulatory)
Notes land in the right encounter, and charges ensure full visibility and compliant documentation directly in your EHR.
Three patents cover the revenue-cycle work behind it.
Intelligence that cannot write back into the record is a demonstration, not a platform.
What travels, and where it lands
| What | Where it lands | Checked by |
|---|---|---|
| Device readings — blood pressure, weight, glucose, pulse oximetry | A unique encounter in the patient’s record, not a vendor portal | Transmitted by the device itself, over its own cellular connection |
| The clinical note a navigator writes against an alert | The same encounter as the readings it refers to | Checked against documentation and compliance standards before it reaches your record — every note, not a sample |
| The charge that follows the documentation | The same encounter again, so the charge and its evidence sit together | It drops against documentation your own providers have already reviewed |
Readings arrive from the device over 4G LTE, so nothing depends on a patient pairing a phone or installing an app. What the interface consumes FROM your record, and the transport and message specification for a named EHR, are covered in a technical review — see below.
The shape of an integration here
True of the platform rather than of any one EHR.
Bi-directional, across 80+ EHRs
One encounter, not three
Reviewed before it files
No patient-side integration
Three patents cover the revenue-cycle automation and data aggregation behind this.
What your security review will ask for
HITRUST R2 certified, renewed 2025 — the third renewal. HIPAA-compliant and interoperable. The trust center carries the current posture, subprocessors and questionnaire responses.
Bring your integration analyst to the call.
The interface specification for your EHR, and what we consume from your record, are a conversation with our engineers rather than a page on a website.