Zedmed API
Zedmed has no developer portal, no public API docs, no SDKs, no public sandbox and no self-serve signup. There are two gated routes.
Frequently asked questions
Zedmed scores D on Supergood's API Report Card. Limited, Zedmed has no developer portal, no public API docs, no SDKs, no public sandbox and no self-serve signup. There are two gated routes.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Zedmed is an Australian all-in-one clinical and practice management system (EHR/PMS) for GPs, specialists and allied health, sold on-premise or as Zedmed Cloud (https://www.zedmed.com.au).
Healthcare, Australian general practices (2–20 practitioners), medical specialists/surgeons, nurse practitioners and allied health clinics; strongest in Victoria/SA, plus multi-site groups and rural practices wanting an on-premise option. Reception works the Appointment Grid and Waiting Room, registers patients, sends SMS reminders/recalls, and raises bulk-bill, DVA, ECLIPSE and private invoices with real-time Medicare claiming and Tyro EFTPOS.
Zedmed claims "800+ practices" and "10,000+ practitioners" (https://www.zedmed.com.au/); Tyro cites "over 1,000 clients" (https://www.tyrohealth.com/pms-partners/zedmed/).
Yes, Zedmed is the system of record for the whole practice: patient demographics and clinical records (notes, medications, allergies, immunisations, results, referrals, MHR uploads), the appointment book and waiting room, Medicare/DVA/ECLIPSE claims and private invoicing, receipts, banking and debtors, recalls and SMS history, surgical lists and stock.
Founded 1978 (Zedmed cites "over 45 years"; Zedmed Pty Ltd incorporated 2000), one of Australia's oldest PMS vendors.
Integrators must first be "an approved Partner of the relevant PMS"; staging is free only 6 months "after which an annual fee applies," and production needs a signed order form and PMS-set requirements. Third-party integrators pay "a set fee per practice per month based on the level of usage, with a corresponding daily query and bandwidth cap"; FHIR for Zedmed is only "planned.". Full sourced list under Sources below.
Common alternatives include Best Practice Software (Bp Premier), MedicalDirector (Telstra Health), Genie Solutions / Gentu (Magentus), MediRecords, Clinic to Cloud. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Zedmed MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Zedmed doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.