Cross-EMR Data Exchange
Explore clinical data exchange across system boundaries.
The Integration Pattern
Explore seven illustrative cross-EMR exchange scenarios for Australian healthcare: record transfer, longitudinal views, handovers, admissions, remote monitoring, medication reconciliation and correspondence. The player uses synthetic data, not live transfers to another EMR. Its labels distinguish documented MediRecords API capabilities, application-owned logic, partner operations and simulated writes. A confirmed capability label is not evidence that an API call ran. Patient matching, consent, external delivery and reconciliation remain the integration team's responsibility.
Illustrative Workflow Steps
Read and assemble
Illustrate supported FHIR reads and application-owned assembly of an exchange payload; the player uses synthetic responses.
Apply exchange controls
Show where matching, consent, authorisation and external transport belong to the connector—not an automatic MediRecords transfer.
Review inbound information
Distinguish documented operations from simulated writes; do not assume every clinical resource or attachment can be written back.
API and Application Boundaries
Coming soon