Australian Digital Health Agency
The Australian Digital Health Agency (ADHA) is the Australian Government statutory agency responsible for national digital health infrastructure and standards. It operates and stewards My Health Record (the national shared health record), the Healthcare Identifiers (HI) Service, the National Authentication Service for Health (NASH) PKI, electronic prescribing, and the National Clinical Terminology Service (NCTS). ADHA publishes machine-readable APIs for connecting conformant clinical software to these national systems, centred on HL7 FHIR (R4) alongside legacy HL7 CDA document exchange. Its developer surface spans the My Health Record FHIR Gateway (B2B and Mobile), the NCTS FHIR terminology server and Atom syndication feed (SNOMED CT-AU, AMT, LOINC), and conformance profiles for electronic prescribing. Home market is Australia. Authentication to the national record systems uses NASH SHA-2 PKI certificates (mutual TLS), while the NCTS terminology server uses SMART-on-FHIR OAuth2. Production onboarding is gated behind registration, conformance testing, and PKI issuance; ADHA aligns to the AU Base / AU Core FHIR implementation guides stewarded through HL7 Australia and the Sparked national FHIR accelerator.
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 Australian Digital Health Agency the way a machine reads it — 10 machine-readable artifacts across 6 APIs, 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 — Australian Digital Health Agency scores 29.0/100 (emerging), with a separate agent-readiness read of 46/100 (agent ready). 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 Australian Digital Health Agency
Each block below is one kind of artifact we hold for Australian Digital Health Agency. 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 6
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.
My Health Record FHIR Gateway (B2B)
The business-to-business FHIR Gateway for connecting conformant clinical software to the My Health Record national shared health record. Exposes FHIR-based read and upload inter...
My Health Record FHIR Mobile Gateway
The FHIR Mobile Gateway lets mobile and consumer applications connect to the My Health Record system to retrieve documents and health information on behalf of individuals. Regis...
NCTS FHIR Terminology Server
The National Clinical Terminology Service (NCTS) FHIR terminology server, operated by ADHA on CSIRO Ontoserver. A FHIR R4 (4.0.1) terminology service supporting CodeSystem, Valu...
NCTS National Syndication Server
The NCTS National Syndication Server, an Atom Publishing Protocol profile for interrogating terminology content feeds and downloading FHIR terminology resource bundles (SNOMED C...
Electronic Prescribing
ADHA's electronic prescribing service and conformance profiles enabling electronic prescriptions, dispensing and the Active Script List across prescribing and dispensing softwar...
Healthcare Identifiers (HI) Service
The national Healthcare Identifiers Service, providing unique identifiers for individuals (IHI), healthcare providers (HPI-I) and organisations (HPI-O) that underpin My Health R...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
australian-digital-health-agency-mcp.yml
MCP SERVERSecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Australian Digital Health Agency — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/australian-digital-health-agency · machine-readable index on apis.io