# Health Connect Australia Provider Directory FHIR Implementation Guide

0.2.0-preview - Preview

Health Connect Australia Provider Directory FHIR Implementation Guide, published by Australian Digital Health Agency. This guide is not an authorized publication; it is the continuous build for version 0.2.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/steveswinsburg/HealthConnect/ and changes regularly. See the Directory of published versions

## CapabilityStatement: Health Connect Provider Directory Requester

Official URL: http://ns.electronichealth.net.au/hc/CapabilityStatement/health-connect-provider-directory-requester | Version: 0.2.0-preview
Standards status: Draft | Computable Name: HealthConnectProviderDirectoryRequester
Usage:Jurisdiction: Australia
Copyright/Legal: Copyright © 2025 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 Requester Actor when conforming to this implementation guide. The complete list of FHIR profiles, RESTful operations, and search parameters supported by Health Connect Provider Directory Requester Actor are defined in this CapabilityStatement. The requirements of the Health Connect Provider Directory Requester actor may also be impacted by the rules of local jurisdictions or other contextual requirements.

Raw OpenAPI-Swagger Definition file | Download

## Health Connect Provider Directory Requester

- Implementation Guide Version: 0.2.0-preview
- FHIR Version: 4.0.1
- Supported Formats: SHALL support `json`, SHOULD support `xml`
- Published on: 2025-11-27
- Published by: Australian Digital Health Agency

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

## FHIR RESTful Capabilities

### Mode: `client`

Security
Enable CORS: no
Security services supported: `OAuth`

> All interactions SHOULD be secured using OAuth protocols. It SHOULD support authentication, authorisation, and audit logging in accordance with local policy and regulatory requirements.

Summary of System-wide Interactions

- Supports the `search-system`interaction described as follows:

  Definition:

  This operation is a RESTful search interaction (whole system interaction), across multiple resource types (as described in the FHIR specification).

  Behaviour:

  This operation is used by a client system operated by a Health Connect Provider Directory Requester to get resources that match the specified search parameters. .

  The following search parameters are supported:

  - _lastUpdated is used to get the resources that have been added or changed since the requesting system last synchronised their local data store with Health Connect Provider Directory Requester. This search parameter supports the `gt` and `lt` comparison prefixes.

  - _type is used to filter the resources returned by their resource type. The available types are:

    - `HealthcareService` (returns resources conforming to the HC Healthcare Service profile)

    - `PractitionerRole` (returns resources conforming to the HC Practitioner Role profile)

    - `Organization` (returns resources conforming to the HC Organization profile)

    - `Location` (returns resources conforming to the HC Location profile)

    - `Practitioner` (returns resources conforming to the HC Practitioner profile)

    - `Provenance` (returns resources conforming to the HC Provenance profile)

  All of the following query parameters are required in order to receive the complete set of resources that have been created, changed or published since [last_synchronized]:

  `_lastUpdated=[last_synchronized]`

  `_type=HealthcareService,PractitionerRole,Practitioner,Organization,Location,Provenance`

  `_include=Location:organization`

  `_include=HealthcareService:organization`

  `_include=HealthcareService:location`

  `_include=PractitionerRole:organization`

  `_include=PractitionerRole:location`

  `_include=PractitionerRole:service`

  `_include=PractitionerRole:practitioner`

  `_include=Provenance:target`

  `_include:iterate=HealthcareService:organization`

  `_include:iterate=HealthcareService:location`

  `_include:iterate=PractitionerRole:organization`

  `_include:iterate=PractitionerRole:location`

  `_include:iterate=PractitionerRole:service`

  `_include:iterate=PractitionerRole:practitioner`

  As described above the resources returned in the Bundle exclude any Identifiers (e.g. HPI-Is) that cannot be disclosed to the subscriber.

  This operation supports 'paging' (see FHIR specification). If there are too many resources to return in one `Bundle`, the FHIR server adds a next link to the response `Bundle`. The contents of the result `Bundle` therefore comprise all instances of the requested resource types whose lastUpdated timestamp is greater than the <lastSync> in the request query expression and less than or equal to <lastInBundle> where <lastInBundle> is the greatest lastUpdated value of all resources included in the result `Bundle`. The Subscriber Agent FHIR server sets the next link to the filter expression that was used in the original request except that <lastSync> is replaced with <lastInBundle>. If the next link is not present in the Bundle, then there are no more service offerings available.

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Provenance | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-provenance|0.2.0-preview | y | y |  |  | target |  |  |
Organization | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-organization|0.2.0-preview | y | y |  |  | identifier, name, type | `Organization:partOf` | `Location:organization`, `Provenance:target` |
Location | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-location|0.2.0-preview | y | y |  |  | locmailaddress, locationamenities, name, address, type, locationphysicaltype, near | `Location:endpoint` | `HealthcareService:location`, `Provenance:target` |
HealthcareService | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-healthcareservice|0.2.0-preview | y | y |  |  | languages, hsbilling, allday, daysofweek, starttime, endtime, service-type | `HealthcareService:location`, `HealthcareService:providedBy`, `HealthcareService:endpoint` | `PractitionerRole:healthcareService`, `Provenance:target` |
PractitionerRole | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-practitionerrole|0.2.0-preview | y | y |  |  | languages, allday, daysofweek, starttime, endtime, identifier, roletype, identifier-r5 | `PractitionerRole:practitioner`, `PractitionerRole:healthcareService`, `PractitionerRole:organization`, `PractitionerRole:location`, `PractitionerRole:endpoint` | `Provenance:target` |
Practitioner | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-practitioner|0.2.0-preview | y | y |  |  | identifier, regprof, rsg, genderIdentity, name, identifier-r5 |  | `PractitionerRole:practitioner`, `Provenance:target` |
Endpoint | http://ns.electronichealth.net.au/hc/StructureDefinition/hc-endpoint|0.2.0-preview | y | y |  |  | epurl, payloadmimetype, hcepi, name, connection-type, payload-type |  | `HealthcareService:endpoint`, `Location:endpoint`, `PractitionerRole:endpoint`, `Provenance:target` |

#### Resource Conformance: SHOULDProvenance

Base System Profile
HC Provenanceversion: 0.2.0-preview)
Profile Conformance
SHOULD
Reference Policy

Interaction summary

- Supports
  `read`

  Read HC Provenance records to understand data lineage

  `search-type`

  Search for HC Provenance records by target resource or activity

Documentation

> This resource is used to track the provenance of data retrieved, updated, or verified from external systems of record for HC resources.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | target | `reference` |

#### Resource Conformance: SHOULDOrganization

Base System Profile
HC Organizationversion: 0.2.0-preview)
Profile Conformance
SHALL
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section defines the supported interactions by a Requester Actor for the HC Organization profile of the Organization resource type.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | identifier | `token` |
SHOULD | name | `string` |
SHOULD | type | `token` |

#### Resource Conformance: SHOULDLocation

Base System Profile
HC Locationversion: 0.2.0-preview)
Profile Conformance
SHOULD
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section introduces the supported interactions by a Requester Actor for the HC Location profile.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | locmailaddress | `string` |
SHOULD | locationamenities | `token` |
SHOULD | name | `string` |
SHOULD | address | `string` |
SHOULD | type | `token` |
SHOULD | locationphysicaltype | `token` |
SHOULD | near | `special` |

#### Resource Conformance: SHOULDHealthcareService

Base System Profile
HC HealthcareServiceversion: 0.2.0-preview)
Profile Conformance
SHOULD
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section introduces the supported interactions by a Requester Actor for the HC Healthcare Service profile.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | languages | `string` |
SHOULD | hsbilling | `token` |
SHOULD | allday | `token` |
SHOULD | daysofweek | `token` |
SHOULD | starttime | `number` |
SHOULD | endtime | `number` |
SHOULD | service-type | `token` |

#### Resource Conformance: SHOULDPractitionerRole

Base System Profile
HC PractitionerRoleversion: 0.2.0-preview)
Profile Conformance
SHOULD
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section defines the supported interactions for the HC Practitioner Role profile of the PractitionerRole resource type. Each PractitionerRole resource conforming to the HC Practitioner Role profile describes a practitioner in a role at a healthcare service.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | languages | `string` |
SHOULD | allday | `token` |
SHOULD | daysofweek | `token` |
SHOULD | starttime | `number` |
SHOULD | endtime | `number` |
SHOULD | identifier | `token` |
SHOULD | roletype | `string` |
SHOULD | identifier-r5 | `token` |

#### Resource Conformance: SHOULDPractitioner

Base System Profile
HC Practitionerversion: 0.2.0-preview)
Profile Conformance
SHALL
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section defines the supported interactions for the HC Practitioner profile of the Practitioner resource type.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | identifier | `token` |
SHOULD | regprof | `string` |
SHOULD | rsg | `token` |
SHOULD | genderIdentity | `token` |
SHOULD | name | `string` |
SHOULD | identifier-r5 | `token` |

#### Resource Conformance: SHOULDEndpoint

Base System Profile
HC Endpointversion: 0.2.0-preview)
Profile Conformance
SHOULD
Reference Policy

Interaction summary

- Supports `read`, `search-type`.

Documentation

> This section defines the supported interactions for the HC Endpoint profile of the Endpoint resource type. Each Endpoint resource conforming to the HC Endpoint profile is a read-only proxy for a corresponding Endpoint resource published by the HC portal.

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHOULD | epurl | `uri` |
SHOULD | payloadmimetype | `token` |
SHOULD | hcepi | `token` |
SHOULD | name | `string` |
SHOULD | connection-type | `token` |
SHOULD | payload-type | `token` |