FHIR R4 data: the foundation for exchange, with integration work still to be done

MedAgents organizes data on Medplum and FHIR R4. Patient records, visits, results, and prescriptions can be represented using the corresponding resource types. This is the basis for building data connections and reconciliation.

A shared structure alone is not enough for interoperability

The two systems still need to agree on patient identifiers, code lists, units, required fields, and how updates are made. The connection also depends on APIs, access rights, and the capabilities of the receiving system. Using FHIR does not mean interoperability with every HIS, LIS, PACS, or national system.

For example: transferring lab results

• Identify the correct patient and encounter.
• Reconcile test codes, units, values, and the time of sample collection or result release.
• Check amended results, duplicates, and attachments.
• Confirm that the receiving system displays all the information needed.

Data handover needs a defined scope

Before implementation, the parties should agree on the data types to be exported, the formats, the attached documents, the permissions required, and how the handover package will be verified. A server backup is not automatically a dataset that another system can use right away.

See Data and integration and Patient records to prepare the list of data to reconcile.