MediRecords: what it does, who uses it, and how AI voice fits in
MediRecords is one of the few genuinely cloud-native clinical systems built in Australia from the ground up. This page is an independent reference: what MediRecords does, who it is built for, where it performs best, where its limits are, and how clinics already on MediRecords are layering AI voice reception to close the inbound call gap without switching systems.
Selected from networks we've advised across ANZ
A cloud-native EHR built for Australian general practice and specialists
MediRecords was founded in Sydney in 2014 with a specific design goal: build a clinical system that lives entirely in the browser, with no local server requirement, no VPN dependency, and no on-premises hardware footprint. In an industry still dominated by desktop-installed software (Best Practice, Medical Director, Zedmed), that positioning was deliberate and early.
The core product is an electronic health record covering clinical notes, encounter documentation, problem lists, medications, allergies, investigations, and care plans. It is built to Australian clinical workflows, supports MBS item number billing, Medicare Online claiming, DVA claiming, and WorkCover documentation.
ePrescribing is native via MedView and eRx integration — prescriptions are transmitted electronically to any participating pharmacy in the AU network without a printed script. This is a mandatory capability for any system operating in the post-2020 ePrescribing environment and MediRecords was an early adopter.
The private health insurance claiming module supports HICAPS and direct fund claiming for practices billing private patients. Tyro terminal integration is available for in-clinic card payments tied directly to the patient account.
MediRecords has a hospital module (MediRecords Hospital) used by a small number of private hospital and day procedure centre operators who want a single longitudinal patient record across community and inpatient settings. This is less mature than the GP/specialist module but represents a strategic direction toward care continuity.
600+ clinics — GP, specialist, and allied health — predominantly metro and regional AU
The user base as of 2025 sits at approximately 600 to 700 clinics. That is a fraction of the total AU primary care market (Best Practice alone claims 6,000+ practices), but MediRecords has grown meaningfully since 2020 as practices that were already cloud-comfortable post-pandemic reassessed their desktop EHR lock-in.
General practice is the largest segment, particularly bulk-billing and mixed-billing practices that have moved to fully paperless workflows and want clinical records accessible from any device without a site-specific server room. The cloud model is operationally attractive for practices with multiple consulting rooms, fly-in fly-out practitioners, or telehealth as a significant proportion of their consult mix.
Specialist practices — particularly dermatology, psychology, and allied health networks — are a growing segment. The referral letter module and outbound fax integration (via eFax) support the specialist correspondence workflow. Psychology practices value the mental health care plan templates aligned to MBS items 2700–2717.
Multi-site corporate GP groups have been an active evaluation segment. For a group running 5–20 clinics, the absence of per-site server infrastructure is a meaningful operational and IT cost reduction. MediRecords' cloud architecture also simplifies remote monitoring, centralised IT governance, and practitioner credentialing across the network.
Aboriginal Community Controlled Health Organisations (ACCHOs) and community health services have adopted MediRecords in some jurisdictions for its ability to operate on limited local infrastructure in remote settings where maintaining on-premises hardware is impractical.
Where MediRecords performs best — and why some practices choose it over incumbents
No on-premises infrastructure is the headline benefit. Practices that have experienced the cost of server replacement cycles, IT contractor callouts for local network failures, or disaster recovery complexity after a flood or fire understand what it means to have the clinical record in a properly managed cloud environment with documented uptime SLAs.
Browser-based access means any device, any location. A practitioner doing a telehealth consult from home, a locum working their first shift, or a practice manager reviewing billing from a second site all access the same live system without a VPN client or remote desktop session.
The onboarding experience for new practices is faster than legacy desktop systems. There is no installation, no site-specific configuration of local file paths, and no dependency on a single workstation. A new practitioner can be credentialed and seeing patients the same day.
Integration via the MediRecords API is documented and available. For practices that want to connect third-party tools — including AI voice agents for appointment management — the API provides calendar read/write, appointment creation, patient record lookup, and practitioner availability queries. This is the integration layer Cadence uses when deploying AI voice for MediRecords clinics.
The MediRecords patient portal allows patients to complete intake forms, view their health summary, and manage some appointment functions online. Reducing paper intake in the waiting room and pre-populating clinical data before the consult are meaningful workflow improvements for high-volume practices.
Honest assessment: where MediRecords lags the incumbent desktop systems
Market share means third-party integrations are less mature than Best Practice or Medical Director. Some pathology providers, specialists software tools, and allied health-specific add-ons have Best Practice or Medical Director connectors that don't yet have an equivalent MediRecords connector. Practices switching from a desktop incumbent should audit their specific integration dependencies before committing.
The billing module is functional but has historically been less feature-rich than the dedicated billing engines in Medical Director or the Best Practice billing module — particularly for complex mixed-billing practices with high DVA, WorkCover, or overseas visitor health cover (OVHC) volumes. This gap has narrowed in recent product releases but is worth evaluating in a trial period.
Reporting and population health tools are less developed than some competitors. Practices with active chronic disease management programs that rely heavily on recall lists, population cohort queries, and MBS billing optimisation reports may find the reporting module requires supplementation with a third-party analytics layer.
The hospital module is early-stage relative to enterprise hospital information systems. MediRecords Hospital suits small private hospitals and day procedure centres but is not positioned as a replacement for Cerner, Epic, or Meditech in a mid-to-large hospital environment.
Internet dependency is the architectural trade-off. Clinics in locations with unreliable NBN or mobile data coverage carry operational risk that on-premises systems do not. MediRecords has an offline mode for some functions, but clinicians should treat consistent, high-quality internet connectivity as a hard requirement, not a nice-to-have.
How clinics on MediRecords are connecting AI voice reception to close the call gap
MediRecords' API-first architecture makes it one of the more straightforward PMS environments to connect an AI voice agent to. The agent reads live practitioner availability from the MediRecords calendar API, presents real appointment slots to the caller, writes confirmed bookings back to the schedule in real time, and updates the patient record with appointment metadata.
The workflow Cadence deploys for MediRecords clinics follows the same pattern as other PMS integrations: inbound call answered by the AI agent, patient identity verified against the MediRecords patient record, appointment type and preferred practitioner confirmed, slot offered and confirmed, booking written to the PMS, SMS confirmation sent to the patient.
After-hours coverage is where the value is clearest. A MediRecords clinic running a 9–5 human reception team and no after-hours answering is losing an estimated 40–55% of inbound booking intent that falls outside business hours. An AI agent covering after-hours costs a fraction of a human FTE and produces bookings that are in the MediRecords schedule before the front desk opens in the morning.
If your practice runs MediRecords and is evaluating AI voice reception, the relevant pages are the AI receptionist for Australian clinics advisory and the virtual medical receptionist overview. Cadence runs the vendor evaluation, integration build, and deployment governance — the clinical system stays as-is.
What the engagement looks like
Cloud-native API access
MediRecords exposes a documented API for calendar read/write, patient lookup, and appointment management — the integration layer AI voice agents use to book directly into the schedule.
ePrescribing native
MedView and eRx integration built in. Electronic scripts transmitted to any participating AU pharmacy without a printed script — mandatory capability in 2025.
Medicare and DVA claiming
Online Medicare claiming, DVA billing, and HICAPS private health insurance claiming all built into the core product, no separate billing module required.
Multi-site cloud architecture
No per-site server. A corporate GP group operating 10 sites on MediRecords has the same IT footprint as a single-site practice — one cloud account, centralised governance.
Patient portal and intake
Online intake forms, health summary access, and appointment functions reduce paper handling and pre-populate clinical data before the consult.
Frequently asked
What is MediRecords?
MediRecords is an Australian cloud-native electronic health record (EHR) and practice management system founded in Sydney in 2014. It covers clinical notes, appointment management, MBS and DVA billing, ePrescribing via MedView/eRx, HICAPS private health claiming, and patient portal functions. It is used by approximately 600+ clinics across general practice, specialist, and allied health settings.
Is MediRecords cloud-based?
Yes. MediRecords is fully cloud-hosted — there is no local server, no VPN requirement, and no software installation. Practitioners access it via any modern browser on any device. This is its primary architectural differentiator from the dominant AU GP software (Best Practice, Medical Director, Zedmed), which are predominantly desktop-installed with local or server-room data storage.
How much does MediRecords cost?
MediRecords does not publish a public pricing schedule. Pricing is typically structured per-practitioner per-month, with tiered rates for solo practitioners versus multi-practitioner and multi-site groups. As an independent advisor, Cadence does not resell MediRecords licences — contact MediRecords directly at medirecords.com for a current pricing proposal. Our advisory role is on the AI voice layer that sits alongside the PMS, not the PMS licence itself.
Does MediRecords have an API?
Yes. MediRecords provides a documented REST API that supports patient record lookup, appointment calendar read/write, practitioner availability queries, and appointment creation. This is the integration layer used when connecting AI voice agents to MediRecords for automated appointment booking. API access terms and rate limits should be confirmed with MediRecords directly before any integration build.
What PMS systems does MediRecords integrate with?
MediRecords is a standalone EHR rather than an integration layer — the question is which third-party tools integrate with MediRecords. Pathology providers (including Sonic, Australian Clinical Labs), imaging providers, MedView for ePrescribing, HICAPS for private health claiming, Tyro for payment terminals, and a range of specialist tools have connectors. Practices should audit their specific workflow dependencies against the current MediRecords integration catalogue before migrating from another system.
Can AI voice agents book appointments into MediRecords?
Yes — via the MediRecords API. An AI voice agent reads live practitioner availability from the MediRecords calendar, offers real slots to the caller, and writes confirmed bookings back in real time. Cadence deploys and governs this integration for MediRecords clinics as part of the AI voice reception advisory engagement. See the virtual medical receptionist and AI receptionist for Australia pages for the full deployment methodology.
Is MediRecords suitable for specialists?
Yes, for many specialist practice types. Dermatology, psychology, physiotherapy, and allied health networks are active MediRecords users. The referral letter module, mental health care plan templates (MBS items 2700–2717), and outbound correspondence tools suit specialist workflows. The fit varies by specialty — some specialist-specific software categories (e.g. ophthalmology, orthopaedics) have incumbent niche systems with deeper specialty-specific templates that MediRecords does not replicate.
How does MediRecords compare to Best Practice and Medical Director?
Best Practice and Medical Director are the two dominant AU GP systems by market share, both desktop-installed with on-premises or server-room data storage options. MediRecords is cloud-native with no local infrastructure requirement. Best Practice and Medical Director have deeper third-party integration ecosystems (more tools have connectors built to them due to market share). MediRecords has the architectural advantage for multi-site groups, remote access, and practices prioritising IT simplicity. The right choice depends on your specific workflow, integration, and infrastructure context.
Are you a vendor or an independent advisor?
Independent advisor. We don't build the AI voice platform — we evaluate the market on your behalf, select the right vendor, and run the deployment to a published bar. No referral fees from vendors.
Is the data hosted in Australia?
Yes — every shortlisted vendor has to demonstrate AU-region hosting (or NZ for NZ clients), AHPRA-aligned consent flows and Privacy Act 1988 / APP compliance before they make our list.
Running MediRecords and want to close the after-hours call gap?
Cadence advises MediRecords clinics on AI voice reception — vendor evaluation, API integration build, and deployment governance. The diagnostic takes two weeks and gives you a named vendor recommendation and integration plan whether you engage us for the rollout or not. Start at the AI receptionist for Australia page or the virtual medical receptionist overview.
Book a discovery call