This page is part of the Australian Provider Directory IG (v0.3.0: PD 1 on FHIR STU3 Draft) based on FHIR R3. The current version which supercedes this version is 2.0.1. For a full list of available versions, see the Directory of published versions 
General Guidance and Definitions
Provider Directory Core Entity Relationships
For directory service profiles the PractitonerRole resource has constrained relationships to Location, Organization, and Practitioner resource types.
For directory service profiles the HealthcareService resource has constrained relationships to Location, and Organization resource types.
Simplified Provider Directory Sequence for Secure Messaging
Provider Directory Service Roles
This implementation guide is defined to allow multiple consumer systems to call multiple provider directory services reliably with a consistent interface and available data support.
Provider Directory Supplier implementations are server software systems that supply a provider directory service interface and data.
- AU Provider Directory Suppliers SHALL be capable of providing all resource types included in this guide.
- AU Provider Directory Suppliers SHALL be capable of providing all profile data elements marked as MUST SUPPORT.
- AU Provider Directory Suppliers SHALL comply to AU Provider Directory Implmementation Guide, AU Base Implmementation Guide and FHIR STU3 core constraints for all resource instances.
- AU Provider Directory Suppliers SHALL be capable of responding meaningfully to all search requests (in each resource definiition) that are marked as MUST SUPPORT.
- AU Provider Directory Suppliers MAY be capable of responding to search requests (in each resource definiition) that are marked as OPTIONAL.
- AU Provider Directory Suppliers MAY be capable of responding to other search requests that are FHIR core compliant OR custom searches (defined using CapabilityStatement supplied by the server).
Provider Directory Consumer implementations are client software systems that call provider directory services and consume data.
- AU Provider Directory Consumers SHALL support meaningful consumption of all data elements marked as MUST SUPPORT.
- AU Provider Directory Consumers SHALL allow receipt of the all resource types in this guide.
- AU Provider Directory Consumers SHALL allow receipt of resource instances that are valid according to the AU Provider Directory Implmementation Guide, including FHIR STU3 core compliant elements not defined in this guide.
- AU Provider Directory Consumers can assume that all search requests marked as MUST SUPPORT are available.
- AU Provider Directory Consumers may use search requests marked as OPTIONAL but MUST inform the user if the call is not supported by the server.
