Mediflowly integrates via HL7 FHIR R4 and ADT messaging — the standards your EHR already supports. No custom builds, no parallel data warehouse, no 6-month IT project.
Each integration uses the EHR's native data interface — no custom API builds required from your IT team.
Connects via Epic's FHIR R4 API and ADT event feed. Mediflowly reads Encounter, Location, Appointment, and Schedule resources. Compatible with Epic versions 2018 and later. Integration reviewed against Epic's standard FHIR scope definitions.
Connects via Cerner's Millennium FHIR R4 interface and HL7 ADT event stream. Compatible with both legacy Millennium and current Oracle Health branding. Reads patient encounter, admission, and scheduling data streams.
Integrates via Meditech Expanse's HL7 ADT interface and FHIR R4 endpoint available in Expanse version 6.15 and later. Reads bed management, patient flow, and scheduling data. Common deployment at community and critical access hospitals.
Connects via Allscripts Sunrise's HL7 v2.x interface layer and REST API. Reads ADT messages, encounter data, and surgical scheduling feeds. Tested against Sunrise Acute Care environment.
Mediflowly is built FHIR-first. Any EHR with a conformant FHIR R4 endpoint can connect directly — including EHRs not listed here. Key resources used: Encounter, Location, Patient (de-identified), Appointment, Schedule, Slot.
Legacy HL7 v2 ADT messaging is supported as the fallback path for any EHR. All A0x event types consumed and mapped to Mediflowly's ops schema. Supports both real-time event feeds and batch file delivery patterns for constrained environments.
Mediflowly's data ingestion layer is built on HL7 FHIR R4 — the current interoperability standard mandated by CMS and ONC for certified health IT systems. This means no translation middleware, no proprietary connectors, and no format negotiation for modern EHRs.
All data in transit between your EHR and Mediflowly is encrypted with TLS 1.3. Authentication uses OAuth 2.0 / SMART on FHIR where supported, or mutual TLS certificate authentication for HL7 v2 feed connections. De-identification at ingestion ensures operational analytics do not require access to identified patient data.
Mediflowly is designed with HIPAA controls in mind. We execute a Business Associate Agreement (BAA) with all health system customers prior to integration initiation.
Full security architecture