Guide
DG-3088
Status
Active
Version
1.0
Created
Updated
This is the current version.
Quick intro
This section explains how to configure Provider Connect Australia™ (PCA™) for publisher operations.
Publisher steps
The following table lists the high level steps a Publisher can implement with PCA, along with the supported channels:
| Ref | Steps to implement | Type | Channel | Volume |
|---|---|---|---|---|
| 1 | Publisher capability statement | Information | API only | Low |
| 2 | Create a location for an organisation | Required | Portal & API | Low |
| 3 | Create healthcare service for a location | Required | Portal & API | Med |
| 4 | Search for partner services that we want to disclose the information to | Required | Portal & API | Med |
| 5 | Get the information use statement of the partner service | Required | Portal & API | Med |
| 6 | Find a practitioner | Required | Portal & API | High |
| 7 | Using the found practitioner, create a practitioner role | Required | Portal & API | High |
| 8 | Authorise publication to business partner | Required | Portal only | Low |
| 9 | Get status of business partner matched records | Optional | API only | High |
For all operations, including management of subscriber information, refer to publisher operations in the API reference.
Publisher capability statement
The capability statement of the Publisher Agent will be specific to the organisation and can be accessed using the command:
| FHIR server | Capability Statement |
|---|---|
| Publisher Agent | ${env}/PcaFhirApi/v2/publisher/${org_id}/fhir/metadata |
Please note the FHIR ${base} URL will be different as per environments in Getting started section.
Home | Back: Subscriber (Business partner) | Next: Create location
