Health Connect Australia Provider Directory FHIR Implementation Guide - Local Development build (v26.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://digitalhealth.gov.au/fhir/hcpd/CapabilityStatement/health-connect-provider-directory-responder | Version: 26.0.0 | |||
| Active as of 2026-04-29 | Computable Name: HealthConnectProviderDirectoryResponder | |||
Usage:Jurisdiction: Australia |
||||
Copyright/Legal: Copyright © 2026 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ |
||||
This CapabilityStatement resource defines the expected capabilities of the Health Connect Provider Directory Responder Actor when conforming to this implementation guide. The listed FHIR profiles, RESTful operations, and search parameters describe only those capabilities exposed for responding to Requester Actor requests. The Health Connect Provider Directory Responder supports additional internal and publishing operations that are not shown here; these are out of scope for this IG and are documented separately for publishing systems. The requirements of the Health Connect Provider Directory Responder may also be impacted by the rules of local jurisdictions or other contextual requirements.
Raw OpenAPI-Swagger Definition file | Download
json, SHALL support xmlNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
serverOAuthAll interactions SHALL be secured using OAuth protocols. It SHALL support authentication, authorisation, and audit logging in accordance with local policy and regulatory requirements.
| Conformance | Operation | Documentation |
|---|---|---|
| SHALL | $export | This bulk data export operation expects request parameters conforming to the HCPD Export Request Parameters profile which defines the required parameter structure for _outputFormat, _type, _typeFilter, and optional _since parameters. The server returns URLs to ndjson files containing the requested resource types. When applicable, the server may automatically inject HCPD Export Response List resources into the output to indicate resource identifiers marked for removal from downstream client systems. |
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| Provenance | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-provenance|26.0.0 | y | y | target | Provenance:target | ||||
| Organization | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-organization|26.0.0 | y | y | identifier, name, type | Organization:partOf | Location:organization, Provenance:target | |||
| Location | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-location|26.0.0 | y | y | locmailaddress, locationamenities, name, address, type, locationphysicaltype, near | Location:organization, Location:endpoint | HealthcareService:location, Provenance:target | |||
| HealthcareService | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-healthcareservice|26.0.0 | y | y | languages, hsbilling, allday, daysofweek, starttime, endtime, service-type | HealthcareService:location, HealthcareService:organization, HealthcareService:endpoint, HealthcareService:organization | PractitionerRole:service, Provenance:target | |||
| PractitionerRole | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-practitionerrole|26.0.0 | y | y | languages, allday, daysofweek, starttime, endtime, identifier, role | PractitionerRole:practitioner, PractitionerRole:service, PractitionerRole:organization, PractitionerRole:location, PractitionerRole:endpoint | Provenance:target | |||
| Practitioner | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-practitioner|26.0.0 | y | y | identifier, regprof, rsg, identifier-r5, name | PractitionerRole:practitioner, Provenance:target | ||||
| Endpoint | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-endpoint|26.0.0 | y | y | epurl, payloadmimetype, hcepi, name, connection-type, payload-type | HealthcareService:endpoint, Location:endpoint, PractitionerRole:endpoint, Provenance:target | ||||
| List | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-export-response-list|26.0.0 | y | |||||||
| Parameters | http://digitalhealth.gov.au/fhir/hcpd/StructureDefinition/hcpd-export-request-parameters|26.0.0 | y | y | Provenance:target, Organization:partOf, Location:organization, Location:endpoint, HealthcareService:location, HealthcareService:organization, HealthcareService:endpoint, PractitionerRole:practitioner, PractitionerRole:service, PractitionerRole:organization, PractitionerRole:location, PractitionerRole:endpoint | Location:organization, Provenance:target, HealthcareService:location, PractitionerRole:service, PractitionerRole:practitioner, HealthcareService:endpoint, Location:endpoint, PractitionerRole:endpoint |
readRead HC Provenance records
search-typeSearch HC Provenance records by various parameters
HC Provenance resources track the lineage of data retrieved, updated, or verified from external systems of record.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | target | reference |
read, search-type.This section defines the supported interactions for the HCPD Organization profile of the Organization resource type.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | identifier | token | |
| SHALL | name | string | |
| SHALL | type | token |
read, search-type.This section describes the supported interactions for the HCPD Location profile. Each Location resource conforming to this profile identifies a physical or virtual place associated with healthcare services in the Health Connect Provider Directory, enabling clients to discover, filter, and reference service delivery sites.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | locmailaddress | string | |
| SHALL | locationamenities | token | |
| SHALL | name | string | |
| SHALL | address | string | |
| SHALL | type | token | |
| SHALL | locationphysicaltype | token | |
| SHALL | near | special |
read, search-type.This section describes the supported interactions for the HCPD Healthcare Service profile. Each HealthcareService resource conforming to this profile identifies a healthcare service in the Health Connect Provider Directory, enabling clients to discover, filter, and reference healthcare services that are provided.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | languages | token | |
| SHALL | hsbilling | token | |
| SHALL | allday | token | |
| SHALL | daysofweek | token | |
| SHALL | starttime | number | |
| SHALL | endtime | number | |
| SHALL | service-type | token |
read, search-type.This section defines the supported interactions for the HCPD Practitioner Role profile of the PractitionerRole resource type. Each PractitionerRole resource conforming to the HCPD Practitioner Role profile describes a practitioner in a role at a healthcare service.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | languages | token | |
| SHALL | allday | token | |
| SHALL | daysofweek | token | |
| SHALL | starttime | number | |
| SHALL | endtime | number | |
| SHALL | identifier | token | |
| SHALL | role | token |
read, search-type.This section describes the supported interactions for the HCPD Practitioner profile. Each Practitioner resource conforming to this profile represents an individual healthcare provider registered in the Health Connect Provider Directory, enabling clients to search, identify, and reference practitioners and their associated roles and service locations.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | identifier | token | |
| SHALL | regprof | string | |
| SHALL | rsg | token | |
| SHALL | identifier-r5 | token | |
| SHALL | name | string |
read, search-type.This section describes the supported interactions for the HCPD Endpoint profile. Each Endpoint resource conforming to this profile provides connection details for electronic services available through the Health Connect Provider Directory, allowing clients to discover and interact with service endpoints in a standardised way.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | epurl | uri | |
| SHALL | payloadmimetype | token | |
| SHALL | hcepi | token | |
| SHALL | name | string | |
| SHALL | connection-type | token | |
| SHALL | payload-type | token |
readRead access to HCPD Export Response List resources obtained through bulk export operations
This resource declares support for the HCPD Export Response List profile. List resources conforming to this profile are automatically generated and included as part of bulk data export operations to communicate which resource identifiers should be removed from downstream client systems. These List resources are not directly searchable or accessible via standard FHIR REST operations, but are provided exclusively through the bulk export process.
readsearch-typeProcess HCPD Export Request Parameters as input to bulk export operations
This resource declares support for processing HCPD Export Request Parameters resources as input to bulk data export operations. Parameters resources conforming to this profile are used to control the scope, format, and filtering criteria for bulk exports. These resources are processed as part of the $export operation and are not directly stored or searchable.