MedicalDirector
MedicalDirector is an Australian clinical and practice-management software provider, owned by Telstra Health, that has served general practices, specialists, and day hospitals across Australia for more than 25 years. Its product family includes Helix (a cloud-based combined clinical and practice-management system), Clinical and Pracsoft (on-premise clinical and practice-management software), Bluechip (specialist practice management), and Day Surgery. Alongside Best Practice, MedicalDirector is one half of the dominant Australian GP-software duopoly. Its programmatic surface is delivered through Telstra Health Smart API+, a FHIR-native integration gateway that lets approved technology partners exchange data with MedicalDirector Helix (and, on a case-by-case basis, MedicalDirector Clinical) without bespoke, platform-specific integrations. Smart API+ is a gated, partner-onboarded API: it is publicly announced and described but has no self-serve public developer portal, and no FHIR CapabilityStatement or OpenAPI is published anonymously. Access is granted through a partner agreement, and the underlying FHIR version and SMART-on-FHIR auth specifics are not disclosed on public pages.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles MedicalDirector the way a machine reads it — 2 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MedicalDirector scores 24.3/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MedicalDirector
Each block below is one kind of artifact we hold for MedicalDirector. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Telstra Health Smart API+
FHIR-native integration gateway from Telstra Health that provides a single, standardized interface for approved technology partners to exchange data with MedicalDirector Helix c...
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for MedicalDirector — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/medical-director · machine-readable index on apis.io