Zedmed: independent guide for GP and specialist practices
Zedmed is one of Australia's longest-running GP and specialist practice management systems — Melbourne-based, 30+ years in the market, and still predominantly deployed as on-premises desktop software. This page is an independent reference covering what Zedmed does, who uses it, where it performs well, its structural limitations, and how practices on Zedmed are adding AI voice reception without replacing their clinical system.
Selected from networks we've advised across ANZ
A Melbourne-built GP and specialist PMS with three decades of clinical workflow depth
Zedmed is an Australian-developed practice management and clinical software system with origins in Melbourne in the 1990s. It covers the full GP and specialist clinical workflow: appointment scheduling, electronic health records, clinical notes, problem lists, medications, pathology and imaging orders and results, referral letters, MBS billing, Medicare online claiming, DVA billing, and private health fund claiming via HICAPS.
The product has historically been deployed as on-premises desktop software — installed on a local workstation or clinic server, with data stored on local hardware or a server in the practice's server room. This architecture is the dominant model across the Zedmed install base and reflects the broader AU GP market preference for on-premises systems through the 2000s and 2010s.
Zedmed has invested in a cloud-accessible option in recent years, allowing browser-based access to some functions, but the core install base remains predominantly on-premises. Practices evaluating Zedmed in 2025 should clarify the current deployment options and roadmap directly with the vendor.
ePrescribing is supported via the national Active Script List (ASL) and MedView integration. Medicare Online claiming, DVA, WorkCover, and OVHC billing are all supported within the billing module. The pathology and imaging results inbox integrates with major AU providers including Sonic, Australian Clinical Labs, and I-MED.
Specialist module capabilities cover appointment type templates, procedure billing, specialist letter templates, and outbound referral correspondence. Zedmed has a meaningful installed base in surgical, dermatology, ophthalmology, and gastroenterology practices that require deeper specialist billing and documentation templates than some GP-focused systems provide.
GP practices and specialist rooms with deep on-premises infrastructure investment
Zedmed's install base skews toward established practices that built out their clinical workflow on the system in the 2000s and have deep customisation investment — appointment type libraries, billing item mappings, letter templates, and practitioner preference configurations built up over years of use.
GP practices in metropolitan and regional Victoria and New South Wales represent the largest geographic concentrations, reflecting the Melbourne origin and historical sales focus. Queensland and South Australian practices are present but at lower density than the eastern seaboard.
Specialist rooms — particularly surgical, dermatology, and procedural specialties — are a significant Zedmed segment. The system's deep billing configuration capability and procedural item number handling suit specialist billing complexity better than some GP-first systems.
Multi-practitioner GP clinics with 5–15 consulting rooms and an existing server room infrastructure represent a common Zedmed profile. For these practices, the on-premises model has historically been a comfort factor around data control, even as cloud alternatives have matured.
Allied health practices — physiotherapy, occupational therapy, podiatry — appear in the Zedmed user base, often as part of a broader integrated health centre where the GP practice runs Zedmed and allied health practitioners access the same appointment system for scheduling coordination.
Where Zedmed performs well — particularly for established and specialist-heavy practices
Deep customisation depth is the headline Zedmed strength. Appointment types, billing item configurations, letter templates, clinical note templates, and recall protocols can all be configured to practice-specific workflows at a level of granularity that some more opinionated systems do not permit. For practices that have built workflows around specific configurations, this depth is genuinely valuable.
Specialist billing capability is a relative strength. Procedural item numbers, theatre billing, specialist consultation item numbers, and mixed private/Medicare billing scenarios are handled within the billing engine with less need for workarounds than in systems built primarily for bulk-billing GP.
On-premises data control remains a selling point for practices and practice owners who have a strong preference for physical data sovereignty — knowing exactly where the patient record data lives. Whether that preference is justified against a properly configured cloud system with AU-region hosting is a separate question, but it is a genuine decision factor for many owners.
Pathology and imaging inbox integration with major AU providers is well-established. Results routing, acknowledgement workflows, and critical result flags are mature in the Zedmed environment — practices that receive high volumes of results per day benefit from a stable, customisable inbox configuration.
The Zedmed support and training ecosystem in Australia is well-developed. Experienced Zedmed trainers, implementation consultants, and support staff are available in the major capital cities, which matters for practices that require hands-on onboarding or have complex migration requirements.
Honest assessment: structural limitations of on-premises architecture and market position
On-premises architecture creates operational overhead that cloud systems do not. Server hardware replacement cycles (typically every 5–7 years), IT contractor dependency for local network issues, backup and disaster recovery management, and the risk of a single-point-of-failure server outage are real costs that practices often undercount until they experience them.
Remote access requires additional infrastructure. A practitioner wanting to access Zedmed from home, a telehealth session, or a second site location needs a VPN, remote desktop configuration, or a cloud-access add-on — none of which are as seamless as a browser-based cloud system.
Third-party integration depth varies. Some modern telehealth platforms, patient engagement tools, and AI voice agents have more mature connectors for Best Practice and Medical Director (as the higher market-share alternatives) than for Zedmed. Middleware layers (such as Nuvolo, Appointuit, or custom API bridges) are often required to connect modern tools to Zedmed.
The cloud roadmap is less clearly communicated than some competitors. Practices considering Zedmed in 2025 for a new setup should seek specific commitment on the cloud product roadmap and migration path before committing to an on-premises deployment that may require re-migration within 3–5 years.
Mobile access is limited relative to cloud-native alternatives. Practitioners who expect to review clinical information, manage recalls, or approve results on a tablet or phone between sites will find the Zedmed mobile experience less capable than cloud-first systems.
How Zedmed practices are adding AI voice reception without a system migration
Connecting an AI voice agent to Zedmed's on-premises appointment calendar requires a middleware integration layer rather than a direct cloud API call. The most common approach Cadence deploys is a local agent or integration broker that reads and writes to the Zedmed appointment database in real time, exposing a secure API endpoint that the AI voice platform can call from the cloud.
The workflow is functionally identical to a cloud PMS integration from the patient's perspective: the AI agent answers the call, verifies the patient, checks real-time availability in Zedmed, offers slots, confirms the booking, and writes it to the schedule. The middleware layer handles the translation between the cloud AI platform and the on-premises Zedmed environment.
Security posture for on-premises integration requires additional attention. The integration broker must be configured with appropriate network access controls, encrypted transport, and audit logging. Cadence includes a security architecture review as part of the Zedmed integration build to ensure the Privacy Act / APP posture of the on-premises system is not weakened by the AI voice connection.
For Zedmed practices evaluating AI voice reception, the relevant advisory pages are the AI receptionist for Australia overview and the virtual medical receptionist page. The deployment methodology is the same — two-week diagnostic, vendor evaluation, integration build — with the Zedmed middleware layer scoped into the integration phase.
What the engagement looks like
Deep billing configuration
Procedural item numbers, specialist consultation billing, mixed private/Medicare scenarios, and DVA/WorkCover handling — configured to practice-specific workflows with high granularity.
Pathology and imaging inbox
Mature results routing, acknowledgement workflows, and critical result flags for high-volume results practices across major AU provider networks.
Specialist module depth
Appointment type templates, procedure billing, specialist letter templates, and outbound referral correspondence built for GP and specialist room workflows.
On-premises data control
Patient record data stored on local hardware with practice-controlled access. The trade-off versus cloud hosting is real — but on-premises remains the preference for a segment of AU clinic owners.
Middleware AI integration path
Zedmed on-premises instances connect to AI voice platforms via a local integration broker — enabling real-time appointment booking into the Zedmed schedule without a system migration.
Frequently asked
What is Zedmed?
Zedmed is an Australian practice management and electronic health record system developed in Melbourne with 30+ years of market presence. It covers appointment scheduling, clinical notes, MBS and DVA billing, Medicare online claiming, pathology/imaging results, ePrescribing, and specialist billing modules. It is predominantly deployed as on-premises desktop software across GP and specialist practices in Australia.
Is Zedmed cloud-based?
Primarily no — Zedmed's dominant deployment model is on-premises, with data stored on local hardware or a practice server room. The vendor has introduced cloud-accessible options in recent years, but the majority of the install base as of 2025 is on-premises. Practices evaluating Zedmed for a new deployment should ask the vendor specifically about the current cloud product and its roadmap.
How much does Zedmed cost?
Zedmed pricing is not publicly listed and is provided by the vendor on a per-practice basis, typically structured around practitioner count and module selection. As an independent advisor, Cadence does not resell Zedmed licences — contact Zedmed directly for current pricing. Our advisory role is on the AI voice layer that works alongside the existing PMS.
Can AI voice agents integrate with Zedmed?
Yes, via a middleware integration layer. Because Zedmed is predominantly on-premises, a direct cloud API call is not available in the same way as cloud-native systems. Cadence deploys a local integration broker that reads and writes to the Zedmed appointment database, exposing a secure API endpoint for the AI voice platform. The patient experience is the same: the AI answers the call, checks real availability, and books directly into Zedmed.
What is the difference between Zedmed and Best Practice?
Both are Australian-developed, on-premises-first GP practice management systems. Best Practice has higher market share overall (6,000+ practices) and a broader third-party integration ecosystem. Zedmed has deeper specialist billing configurations and is more commonly found in specialist rooms and practices with complex billing requirements. The right choice depends on practice type, specialty mix, and existing workflow investment.
Does Zedmed support ePrescribing?
Yes. Zedmed supports electronic prescribing via the national Active Script List (ASL) and MedView integration — a mandatory requirement for AU prescribers since the national ePrescribing rollout. Electronic scripts are transmitted to any participating pharmacy in the AU network without a printed script.
Is Zedmed suitable for specialists?
Yes — Zedmed has a meaningful installed base in specialist practices including surgical, dermatology, ophthalmology, and gastroenterology. The specialist billing module handles procedural item numbers, theatre billing, and mixed private/Medicare scenarios at a depth that suits specialist billing complexity. Practices should evaluate whether their specific specialty has dedicated templates and workflows in Zedmed before committing.
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 Zedmed and evaluating AI voice reception?
Cadence advises Zedmed practices on AI voice reception — including the middleware integration build that connects AI voice platforms to on-premises Zedmed installations. The two-week diagnostic scopes the integration, evaluates vendors, and produces a deployment plan. See the AI receptionist for Australia overview or the virtual medical receptionist page to start.
Book a discovery call