Connect by MediRecords
Request Access
Use Case Library

Healthcare API integration use cases

Explore the art of the possible for Australian healthcare, using MediRecords FHIR R4 and REST APIs. Each example distinguishes documented capabilities, application-owned logic and simulated behaviour.

Built around real API capabilitiesDesigned for practice teams

Explore the library

API patterns for better connected care

Each use case explains the patient or practice outcome, the integration steps and the MediRecords resources involved.

Demo available

Appointment Booking API

A connected, patient-first booking experience.

An illustrative use case showing one way a practice or integration partner could create a branded, embeddable appointment experience around the documented MediRecords appointment APIs. The widget shown is a concept demo—not a MediRecords-supplied product—and represents one elegant mechanism among many possible implementations. Availability is shown as an estimate unless the configured booking workflow confirms a time.

Demo available · Conditional live calls

How it connects

Welcome patients with clarity
Connect the right choices
Keep the moment moving
Appointment workflowPatient journeyMediRecords integration
Explore Use CaseOpen DemoTrial access required
Demo available

HubSpot Healthcare CRM Integration

Align clinical and marketing operations.

Explore how MediRecords patient and appointment data could support HubSpot contact management and patient engagement. The demo separates synthetic workflows from optional, authorised live calls. Clinical records stay in MediRecords; any HubSpot sharing must follow an approved, minimum-necessary data and consent policy.

Demo available · Conditional live calls

How it connects

Keep Contacts Current
Capture & Match
Track Appointments
PatientAppointmentWebhooks
Explore Use CaseOpen DemoTrial access required
Demo available

Patient Intake API Workflows

A clearer start to care, built around real patient answers.

Explore two patient intake API workflows for Australian practice teams: first-visit registration with an emergency contact, and referral letter upload into Correspondence In. The demo distinguishes documented MediRecords operations, authorised live calls and simulated outcomes. Referral letters are correspondence, not native Patients > Referrals records. No booking-triggered SMS or automatic invitations are implied.

Demo available · Conditional live calls

How it connects

Choose the patient journey
Capture answers with context
Trace each integration step
PatientEmergency contactREST correspondence
Explore Use CaseOpen DemoTrial access required
Coming Soon

Telehealth EHR Integration

A clearer path into virtual care.

Explore an illustrative telehealth EHR integration for Australian practices, from an appointment to a consultation link and clinician workflow. The demo application manages consultation links and session state; MediRecords appointment, patient and encounter calls are simulated, not live record updates. A production integration would need its own video service, orchestration and approved clinical workflow. The published FHIR webhook catalogue does not list appointment events, so this pattern does not promise an appointment webhook or automatic encounter synchronisation.

Coming soon

How it connects

Start from an appointment
Prepare a consultation link
Review the encounter workflow
Appointment (simulated)Encounter (simulated)Application-managed sessions
Available in a future release
Coming Soon

Cross-EMR Data Exchange

Explore clinical data exchange across system boundaries.

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.

Coming soon

How it connects

Read and assemble
Apply exchange controls
Review inbound information
FHIR readsREST correspondenceApplication-owned exchange
Available in a future release
Coming Soon

Salesforce Healthcare Integration

Member services and care coordination on Salesforce Health Cloud.

Explore an illustrative Salesforce Health Cloud member-care integration for Australian healthcare, with MediRecords as the clinical system of record. The scenario player uses synthetic data and simplified API examples; it does not authenticate with Salesforce or synchronise live records. Clinical reads, documented writes and appointment workflows are shown separately from Salesforce-owned cases and connector logic. Production matching, access controls and synchronisation require additional implementation; appointment webhook delivery is not a published FHIR capability.

Coming soon

How it connects

Map the care boundary
Plan synchronisation
Coordinate member care
PatientAppointmentWebhooks
Available in a future release

Ready to explore the technical layer?

Start with the APIs behind every use case.

Review the FHIR implementation guide or Developer API reference before connecting your own practice experience.

FHIR docsDeveloper API