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.

Australian Digital Health Agency publishes 6 APIs on the APIs.io network. Tagged areas include Healthcare, Australia, National Health System, FHIR, and HL7.

Australian Digital Health Agency’s developer surface includes developer portal, documentation, API reference, getting-started guide, authentication, support, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub

33.9/100 thin ▬ flat Agent 23/100 agent aware library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessFree

6 APIs

Healthcare Australia National Health System FHIR HL7 Interoperability SMART on FHIRElectronic Health Recorde-Prescribing Terminology Government

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 33.9/100 · thin

Contract Quality 7.3 / 21

Developer Ergonomics 8.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 9.0 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/australian-digital-health-agency: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

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...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Australian Digital Health Agency Authentication

mutualTLS/oauth2/openIdConnect · 3 schemes

SECURITY

Australian Digital Health Agency Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Australian Digital Health Agency Scopes

2 scopes · authorizationCode

2 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Portal

Portal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

Idempotency

ErrorCatalog

Lifecycle

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

Authentication

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Support

Support

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: australian-digital-health-agency
url: https://raw.githubusercontent.com/api-evangelist/australian-digital-health-agency/refs/heads/main/apis.yml
name: Australian Digital Health Agency
kind: company
description: 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.
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: gated
  trial: false
  try_now: false
  public: false
  label: Government · Gated onboarding (registration + NASH PKI)
  confidence: high
  source:
  - authentication
  - documentation
  generated: '2026-07-24'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- Australia
- National Health System
- FHIR
- HL7
- Interoperability
- SMART on FHIR
- Electronic Health Record
- e-Prescribing
- Terminology
- Government
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: australian-digital-health-agency:my-health-record-fhir-gateway
  name: My Health Record FHIR Gateway (B2B)
  description: 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 interactions for clinical documents, mapping between HL7 CDA
    implementation guides and FHIR resources. Access is authenticated with NASH SHA-2 PKI certificates over mutual TLS and
    requires registration and conformance testing.
  humanURL: https://implementer.digitalhealth.gov.au/resources/services/my-health-record/my-health-record-fhir-gateway
  tags:
  - FHIR
  - My Health Record
  - EHR
  - Healthcare
  properties:
  - type: Documentation
    url: https://implementer.digitalhealth.gov.au/resources/services/my-health-record/my-health-record-fhir-gateway
  - type: APIReference
    url: https://implementer.digitalhealth.gov.au/resources/my-health-record-fhir-gateway-api-specification-v3-0-0
- aid: australian-digital-health-agency:my-health-record-fhir-mobile-gateway
  name: My Health Record FHIR Mobile Gateway
  description: 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. Registration and a developer welcome pack are required, and
    the interface is FHIR-based.
  humanURL: https://developer.digitalhealth.gov.au/developer-guide/introduction-my-health-record-fhir-gateway-developer-guide-1
  tags:
  - FHIR
  - My Health Record
  - Mobile
  - Healthcare
  properties:
  - type: Documentation
    url: https://developer.digitalhealth.gov.au/developer-guide/introduction-my-health-record-fhir-gateway-developer-guide-1
  - type: APIReference
    url: https://developer.digitalhealth.gov.au/resources/my-health-record-fhir-gateway-v4-0
- aid: australian-digital-health-agency:ncts-fhir-terminology-server
  name: NCTS FHIR Terminology Server
  description: 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, ValueSet, ConceptMap, OperationDefinition and StructureDefinition
    resources with $expand, $lookup, $validate-code, $translate and $closure operations over SNOMED CT-AU, AMT and LOINC.
    Authenticated with SMART-on-FHIR OAuth2. A live FHIR CapabilityStatement was harvested from the /metadata endpoint.
  humanURL: https://www.healthterminologies.gov.au/implementing-in-software/terminology-as-a-service/ncts-apis/
  baseURL: https://api.healthterminologies.gov.au/integration/R4/fhir
  tags:
  - FHIR
  - Terminology
  - SNOMED CT
  - SMART on FHIR
  properties:
  - type: CapabilityStatement
    url: fhir/ncts-terminology-server-capabilitystatement.json
  - type: SmartConfiguration
    url: fhir/ncts-terminology-server-smart-configuration.json
  - type: Documentation
    url: https://www.healthterminologies.gov.au/implementing-in-software/terminology-as-a-service/ncts-apis/
  - type: APIReference
    url: https://api.healthterminologies.gov.au/integration/R4/fhir/metadata
- aid: australian-digital-health-agency:ncts-syndication-server
  name: NCTS National Syndication Server
  description: The NCTS National Syndication Server, an Atom Publishing Protocol profile for interrogating terminology content
    feeds and downloading FHIR terminology resource bundles (SNOMED CT-AU, AMT, LOINC, RCPA SPIA and more). The syndication
    feed is generated by the Australian Digital Health Agency and served as an Atom feed.
  humanURL: https://www.healthterminologies.gov.au/implementing-in-software/terminology-as-a-service/ncts-apis/
  baseURL: https://api.healthterminologies.gov.au/syndication/v1
  tags:
  - Terminology
  - Syndication
  - FHIR
  properties:
  - type: Documentation
    url: https://www.healthterminologies.gov.au/implementing-in-software/terminology-as-a-service/ncts-apis/
  - type: APIReference
    url: https://api.healthterminologies.gov.au/syndication/v1/syndication.xml
- aid: australian-digital-health-agency:electronic-prescribing
  name: Electronic Prescribing
  description: ADHA's electronic prescribing service and conformance profiles enabling electronic prescriptions, dispensing
    and the Active Script List across prescribing and dispensing software. Conformant integration uses NASH PKI certificates
    and the Healthcare Identifiers Service.
  humanURL: https://implementer.digitalhealth.gov.au/resources/services/electronic-prescribing
  tags:
  - e-Prescribing
  - Pharmacy
  - Healthcare
  properties:
  - type: Documentation
    url: https://implementer.digitalhealth.gov.au/resources/services/electronic-prescribing
- aid: australian-digital-health-agency:healthcare-identifiers-service
  name: Healthcare Identifiers (HI) Service
  description: The national Healthcare Identifiers Service, providing unique identifiers for individuals (IHI), healthcare
    providers (HPI-I) and organisations (HPI-O) that underpin My Health Record, electronic prescribing and secure messaging.
    Access is authenticated with NASH PKI certificates.
  humanURL: https://implementer.digitalhealth.gov.au/resources/services/healthcare-identifiers-service-hi
  tags:
  - Identifiers
  - Healthcare
  - Directory
  properties:
  - type: Documentation
    url: https://implementer.digitalhealth.gov.au/resources/services/healthcare-identifiers-service-hi
common:
- type: DomainSecurity
  url: security/australian-digital-health-agency-domain-security.yml
- type: Website
  url: https://www.digitalhealth.gov.au/
- type: DeveloperPortal
  url: https://developer.digitalhealth.gov.au/
- type: Portal
  url: https://implementer.digitalhealth.gov.au/
- type: Documentation
  url: https://implementer.digitalhealth.gov.au/resources
- type: APIReference
  url: https://implementer.digitalhealth.gov.au/fhir-resources
- type: GettingStarted
  url: https://implementer.digitalhealth.gov.au/resources/guides
- type: Authentication
  url: https://implementer.digitalhealth.gov.au/resources/services/national-authentication-service-for-health-nash
- type: Support
  url: mailto:help@digitalhealth.gov.au
- type: GitHubOrganization
  url: https://github.com/AuDigitalHealth
- type: Packages
  url: packages/australian-digital-health-agency-packages.yml
- type: SDKs
  url: packages/australian-digital-health-agency-packages.yml
- type: WellKnown
  url: well-known/australian-digital-health-agency-well-known.yml
- type: Authentication
  url: authentication/australian-digital-health-agency-authentication.yml
- type: OAuthScopes
  url: scopes/australian-digital-health-agency-scopes.yml
- type: Conformance
  url: conformance/australian-digital-health-agency-conformance.yml
- type: Conventions
  url: conventions/australian-digital-health-agency-conventions.yml
- type: Idempotency
  url: conventions/australian-digital-health-agency-conventions.yml
- type: ErrorCatalog
  url: errors/australian-digital-health-agency-problem-types.yml
- type: Lifecycle
  url: lifecycle/australian-digital-health-agency-lifecycle.yml
- type: X-MCPServerCandidate
  url: mcp/australian-digital-health-agency-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/australian-digital-health-agency-llms.txt
- type: DataModel
  url: data-model/australian-digital-health-agency-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/australian-digital-health-agency"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/australian-digital-health-agency/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/australian-digital-health-agency/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.