Guide · Core, Medicines and results, Pathways and documents

FHIR export and import: moving reports into the hospital record and records into a case

Written for
Hospital doctors, residents and the clinical informatics teams who support them
Reading time
6 minutes
Published
Updated

Written by the Sana Health team for clinicians. It summarises published guidance, is not a guideline and has not been peer reviewed. Check current local protocols before acting.

Key points

  • A report can be downloaded as an HL7 FHIR R4 document, a JSON file that hospital systems which accept FHIR R4 documents can import.
  • The exported document is marked preliminary, is authored by the Sana Health decision-support device and names no patient; the hospital system files it against its own record.
  • A FHIR R4 file exported from a hospital system can start a case: problems, medicines, allergies, results with their trends, reports, procedures and the reason for the encounter become a case summary.
  • On import, the name, identifiers such as the MRN or ABHA number, address and contact details are left out, age replaces date of birth, and dates become the time before the latest date in the record.
  • Both directions work with files. There is no live connection to any hospital system, nothing is sent automatically, and local information-governance rules apply.

Why a standard file format

A decision-support report is most useful when it can sit in the patient's record beside the notes and results it was based on, and a case is quicker to describe when the history does not have to be retyped from another screen. Both depend on a format that the two systems understand. HL7 FHIR (Fast Healthcare Interoperability Resources) describes health information as standard resources, such as a condition, a medication, an allergy or an observation, that can be gathered into a bundle and exchanged as a file. R4 is the release Sana Health reads and writes.

FHIR is increasingly used for exchanging clinical data: a scoping review identified 203 FHIR projects applicable to clinical research and described the standard as becoming an essential part of it [2], while mapping data from older record systems onto FHIR models and terminologies is a recognised problem with many proposed solutions [3]. The benefits of interoperable records for safety and quality remain unclear in the research literature, although some studies found improvements in medication safety [1]. Exchanging a file does not by itself make care safer; what matters is that the right information reaches the clinician who reviews it.

Exporting a report for the hospital record

  1. Open the report and choose Export for hospital record (FHIR) from its Export menu.
  2. A JSON file downloads: an HL7 FHIR R4 document Bundle containing the report.
  3. Import the file into the hospital system following your institution's procedure, where that system accepts FHIR R4 documents, and file it against the patient's record there.
Part of the documentWhat it holds
CompositionThe question that was asked, the report, and the verified references, as narrative text with the references as links
StatusPreliminary, because the clinician must review the report before relying on it
AuthorThe Sana Health decision-support device
PatientNone. The hospital system files the document against its own patient record

Leaving the patient out of the file is deliberate. Sana Health is not the record of who the patient is, and the person importing the document chooses the patient in the hospital system, just as they would for any external report.

Starting a case from a hospital record

  1. Export the patient's record from the hospital system as a FHIR R4 JSON file: a Bundle or a single resource.
  2. In the message box, choose Import from hospital record and select the file.
  3. A case summary built from the file appears in the message box.
  4. Read it, correct it and add what it lacks, such as examination findings, today's observations and the question you want answered.
  5. Send it when you are satisfied. Nothing is sent automatically.
Taken from the recordHow it appears in the summary
ProblemsThe patient's conditions and diagnoses
MedicinesThe medicines recorded
AllergiesRecorded allergies and intolerances
ResultsResults, with their trend where a test has been repeated
Reports and proceduresReports and the procedures recorded
EncounterThe reason for the current encounter

What is left out on import

  • The patient's name.
  • Identifiers, such as the hospital MRN or the ABHA number.
  • Address and contact details.
  • The date of birth, which is replaced by the patient's age.
  • Calendar dates, which become the time before the latest date in the record (in days, or in months and years for older entries), so that the order and spacing of results are kept.
  • Narrative text and notes, which are not imported, and any name, identifier or date that appears inside free text that is imported, such as a report conclusion, which is replaced by [removed].

These steps remove the direct identifiers, but a summary can still point to one person through a rare condition combined with other details. Read the summary as you would any case before sharing it, and remove anything that is not needed for the question.

What it is and is not

  • It works with files. There is no live connection to any hospital system and no automatic synchronisation in either direction.
  • It produces and reads HL7 FHIR R4 JSON. No claim is made of ABDM certification or of conformance to any national FHIR profile.
  • Hospital systems differ in what they put into an export, so check the summary against the record for anything important that is missing.
  • The exported report remains preliminary until a clinician has reviewed it, and the clinician remains responsible for every decision.

Moving patient records between systems is governed by local rules. Before exporting a record from the hospital system, or importing a Sana Health document into it, follow your institution's information-governance policy and the data protection law that applies to you.

How Sana Health helps

Once the clinician has checked an imported summary and added examination findings and observations, the Diagnostic Reasoning engine works through the case to a ranked differential, the reasoning behind it, the red flags and the tests that would change the picture. The report typically arrives in under a minute, ends with numbered references, and can then be exported as a FHIR R4 document for the hospital record.

Questions

Does Sana Health connect directly to our hospital system?

No. Export and import both work with files: the clinician downloads a FHIR R4 document from a report, or selects a FHIR R4 file exported from the hospital system. There is no live connection and no automatic synchronisation.

Is the patient's name or ABHA number imported?

No. The name, identifiers such as the MRN or ABHA number, address and contact details are left out, age replaces the date of birth, and dates become the time before the latest date in the record. The clinician reviews and edits the summary before anything is sent.

Why is the exported document marked preliminary?

Because a decision-support report has to be reviewed by the clinician before it is relied on. Marking it preliminary tells anyone reading it in the hospital record that it is not a final clinical document.

References