Aeion Health + FHIR R4
Pull patient demographics, providers, encounters, and problem-list conditions out of Epic and Oracle Health (Cerner) over SMART on FHIR and land them in native Aeion Health records — no CSV exports, no screen-scraping. This is a read-only inbound connector today: Aeion imports FROM a hospital's FHIR endpoint, it does not yet publish its own FHIR API, export FHIR resources, or exchange HL7v2 messages. Read the honesty note below before you plan a bidirectional interface.
What Connects
`
Setup
Configure the connector once per source system through Aeion Singularity:
What This Integration Does NOT Do (yet)
FHIR and interoperability claims deserve precision in a clinical product. Here is the honest boundary as of this review:
Where Imported Data Lands
Imported FHIR resources become first-class Aeion Health records, so everything the platform does natively applies to them immediately:
FAQ
No. This connector imports FHIR R4 data from certified source systems (Epic, Oracle Health) over SMART on FHIR, but Aeion Health does not carry ONC Health IT certification and should not be represented as certified. Certification status is a formal regulatory determination.
Not today. The connectors request read-only scopes (`*.read`) and there is no write-back path. Treat this as a one-way import/onboarding tool.
Patient, Practitioner, Encounter, and Condition (R4). Vitals and labs (Observation), allergies, medications, documents, and immunizations are not yet imported over FHIR — they are entered or captured through Aeion Health's native workflows (for example, vitals via BLE devices through Aeion Bridge).
No. There is no HL7v2 message pipeline. Interoperability today is FHIR R4 inbound import via Singularity only.
Yes. Imports run inside your Aeion tenant, land in tenant-scoped collections, and every touch of imported PHI is captured in the immutable audit trail.
Migrate off your incumbent EHR — read-only, over standards.
Import patients, providers, encounters, and conditions from Epic and Oracle Health over SMART on FHIR. Honest about the boundary: inbound R4 import today, native FHIR export on the roadmap.