Export a Patient's Record as FHIR

Who / when: an integration administrator (or your hospital IT integrator), when an external system — a health information exchange, a referral hospital, a research registry, a national reporting platform — needs to read a patient’s record out of Veona. Rather than learn Veona’s internal data model, the partner reads the record in FHIR R4, the international standard for exchanging health data.

FHIR (Fast Healthcare Interoperability Resources) is HL7’s modern web-based health-data standard; R4 is its current released version. The whole-patient export returns one patient’s record as a single FHIR Bundle — a FHIR container that wraps many resources at once.

Note

There is no screen for this in the staff app — it is an integration capability that a partner system reads, not a button a clinician presses. Your integration administrator shares the connection details; the partner’s software does the reading.

Steps

1. Use an account with export access. Exporting is restricted to the integration administrator capability, which is off by default. An Administrator grants it to the integration or service account that will feed the partner — and to no one who does not need it. No clinical role can export.
2. Connect the partner system. The partner reads only the record for one facility, so every export returns just that facility’s data. Your integration administrator gives the partner the connection details Veona provides; no patient data leaves until the partner reads it.
3. Export the whole patient record. The export returns a single FHIR Bundle holding the patient, encounters, conditions, observations (lab results and vital signs), service requests, lab and imaging diagnostic reports, and medication requests. For a large record the export can be narrowed to a date window so the partner pulls only the period it needs.
4. Know that every export is audited as a disclosure. Each export is recorded in Veona’s tamper-evident audit trail as a disclosure of Protected Health Information (PHI), naming who exported which patient’s record and how much was disclosed. Treat each export as an accountable release of patient data to an outside system.

What happens next

The partner system receives the FHIR Bundle and ingests it on its side. Each resource carries a stable, Veona-namespaced identifier, so the partner can recognise the same record across repeated exports and pull only what changed by re-running with a later date window. On Veona’s side, the disclosure now sits in the audit trail — so anyone reviewing access can see exactly who exported the record, for which patient, and when.

Follow the trail

• Related module: Veona Integrations