Connect Your Medical Device to the EHR

Connecting a medical device to the EHR means device measurements are written into the patient's chart in systems like Epic or Oracle Health, and clinical context flows back into the device application. In practice that takes a FHIR R4, HL7 or open API interface, EHR authentication, bi-directional data flows and a certified security layer. BioT provides that as a configured platform capability: your device connects to the platform, and the platform speaks to the EHR. BioT customers have achieved FDA clearance and CE marking on the platform.

Talk to a solution architect

Station 01

Your Device and Its Data

Your device, companion app and clinician portal connect to the platform through APIs and SDKs. Measurements land in the platform data layer once, then serve every consumer from the same source.

One data layer feeds the EHR, your portal and your analytics, so the chart never diverges from your application. Device identity, consent and access rules are enforced before any record leaves the platform.

The connection runs on either deployment model: your own AWS account, or a BioT-managed account with a dedicated environment per customer.

Deployment models, on the compliance page

Station 02

The Platform Layer Speaks FHIR R4 and HL7

The integration is a configured platform capability, versioned and monitored like the rest of your deployment, rather than a custom point-to-point project.

The platform ships prebuilt FHIR R4 resource mapping for measurements, patient context and results, HL7 support for systems that expect it, and authentication over OAuth 2.0 server-to-server: the standard model for FHIR R4 backend integrations, and the one systems like Epic expect.

The interface is documented for self-serve use, and BioT's integration team works with your engineers on the technical integration work through go-live.

{
  "resourceType": "Observation",
  "status": "final",
  "code": { "coding": [ { "system": "http://loinc.org", "code": "8867-4", "display": "Heart rate" } ] },
  "subject": { "reference": "Patient/erXuFYUfucBZaryVksYEcMg3" },
  "valueQuantity": { "value": 72, "unit": "beats/minute" }
}

A FHIR Observation resource, as a heart-rate measurement lands on the chart.

See the platform documentation

The Interface

Flows Include

Four flows cover most device programs today. The interface is not limited to them; flows are configured per deployment.

Vitals write

Measurements and vitals from your device are written to the patient record as FHIR Observation resources.

Patient lookup

Your application pulls patient context from the record: demographics, diagnoses, medications and allergies, so data lands on the right chart.

Results read

Lab results and clinical data flow back from the EHR into your application.

Document upload

PDF reports, session summaries and ECG strips are pushed to the chart as FHIR DocumentReference resources.

Station 03

Any EHR Exposing FHIR R4, HL7 or Open APIs

The connection is standards-based rather than vendor-specific. If the EHR exposes FHIR R4, HL7 or open APIs, the platform is designed to connect to it. One deployment can connect to multiple EHRs at the same time.

Epic

Oracle Health

Athena Health

PointClickCare

Epic and Oracle Health are documented, named integrations. BioT customers have integrated with Athena Health and PointClickCare, among others.

Station 04

Compliance and Security for the EHR Connection

Every exchange with the EHR runs inside the certified platform layer: OAuth 2.0 server-to-server authentication, TLS 1.2 or higher in transit, and audit logging on each exchange. No passwords or API keys cross the network.

The full certification list, and the split between what the platform holds and what stays with your device, is on the compliance page.

See the compliance page

Common Questions on the EHR Connection

Which EHRs does BioT connect to?

The interface is standards-based, designed to connect to any EHR exposing FHIR R4, HL7 or open APIs. Epic and Oracle Health (Cerner) are documented, named integrations, and BioT customers have integrated with Athena Health and PointClickCare, among others. One deployment can connect to multiple EHRs at the same time.

What data can move between my device and the EHR?

Flows include measurements and vitals written to the patient record, patient lookup from the record into your application, lab results read back, and PDF reports pushed to the chart as clinical documents. The flows run through one platform interface, with audit logging on each exchange, and are configured per deployment.

Do I need to build a FHIR team?

No. FHIR resource mapping, authentication and monitoring are platform capabilities, configured per deployment. Your team defines the clinical workflow: which measurements matter, and where they belong in the record. Setup is documented step by step in the EHR integration module section of docs.biot-med.com.

Do we do the integration ourselves?

You can. The interface is documented for self-serve use in the EHR integration module section of docs.biot-med.com. In practice BioT's integration team works with your engineers through go-live, from EHR authentication setup to the first data on the chart.

Where is customer data hosted?

On AWS, with availability in the US, EU and Asia. In the customer-account model the deployment sits in your own AWS account. In the managed model it runs on a BioT-managed account with a dedicated environment per customer.

Can I get the BAA and the DPA?

Yes. Both ship in the compliance pack, along with current certificates. Ask through the contact page and the team will send everything.