Australian healthcare APIs by MediRecords
Build around documented FHIR R4 and REST APIs. Explore booking, intake and interoperability examples, with live calls, application logic and simulations clearly distinguished.
What is Connect by MediRecords?
Connect by MediRecords is the developer platform for MediRecords, an Australian cloud practice-management and electronic health record (EHR) system. It provides open FHIR R4 and REST APIs so authorised healthcare applications can work with supported patient, appointment and clinical resources. Your integration owns patient matching, consent, access controls and orchestration.
Get started with MediRecords APIs
Ensure
you have an account — set up for your practice
Request
a security key and certification to access your practice information
Connect
your internal applications for interoperability
Build more connected healthcare workflows
Open APIs
Documented APIs give authorised applications a defined way to work with MediRecords data. Your organisation controls the purpose, permitted data and access decisions for each integration.
Defined resources and interactions
The FHIR R4 guide defines supported profiles, searches and interactions. The separate REST reference covers practice workflows, helping teams check the API contract before they build.
Reduced costs and improved efficiencies
Well-designed integrations can reduce repeated data entry and manual hand-offs. Matching, validation and exception handling still need to be designed for your practice workflow.
Rich integrations and experiences
Specialty applications can be built on top of MediRecords to enhance the product like never before. From integrating into internal applications, to external third parties, innovating your business has never been easier.
FHIR R4 and REST API documentation
For our API Reference documentation & FHIR Implementation Guide, visit our developer sites below.
FHIR API (R4)
Industry-standard interoperability. Query patient demographics, conditions, medications, schedules, and slots directly mapped to HL7 FHIR R4 resources.
Read the FHIR R4 guideDeveloper API
Extended capabilities specifically designed for practice management. Handle billing, webhooks, secure messaging, and complex administrative workflows.
Read the REST API referenceHealthcare API integration examples
Select a use case to see how it works and what resources are required.
Appointment Booking API
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.
HubSpot Healthcare CRM Integration
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.
Patient Intake API Workflows
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.
Telehealth EHR Integration
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.
Cross-EMR Data Exchange
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.
Salesforce Healthcare Integration
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.