AU Core Implementation Guide
0.4.1-preview - Preview Australia flag

This page is part of the AU Core (v0.4.1-preview: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

Resource Profile: AU Core Practitioner

Official URL: http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitioner Version: 0.4.1-preview
Standards status: Draft Maturity Level: 1 Computable Name: AUCorePractitioner

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License. HL7 Australia© 2022+; Licensed Under Creative Commons No Rights Reserved.

This profile sets minimum expectations for a Practitioner resource to record, search, and fetch basic demographics and other administrative information about an individual practitioner. It is based on the AU Base Practitioner profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Practitioner when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Usage scenarios

The following are supported usage scenarios for this profile:

  • Record or update information about a practitioner referenced by another resource
  • Read information about a practitioner referenced by another resource

Comparison with other national and international IGs

A resource conforming to this profile is conformant to:

Conformance in reverse is not guaranteed, i.e. a resource conforming to International Patient Access, International Patient Summary, or US Core MAY NOT conform to AU Core.

Profile specific implementation guidance

  • Because PractitionerRole supplies a provider’s location, contact information, and reference to the Practitioner, it SHOULD be referenced in CareTeam.member instead of the Practitioner resource. If a system only supports Practitioner, the system SHALL provide implementation specific guidance how to access a provider’s location and contact information using only the Practitioner resource.
  • See guidance on the construction of an identifier on the relevant Identifier profile page and the section on Business Identifiers in AU Base.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from AUBasePractitioner

NameFlagsCard.TypeDescription & Constraintsdoco
.. Practitioner 0..* AUBasePractitioner A person with a formal responsibility in the provisioning of services
... Slices for identifier SO 0..* Identifier, AUHPII, AUPBSPrescriberNumber, AUCareAgencyEmployeeIdentifier, AUAhpraRegistrationNumber An identifier intended for computation
Slice: Unordered, Open by pattern:type
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
.... identifier:hpii SO 0..1 AUHPII Healthcare Provider Identifier – Individual (HPI-I)
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
... name SO 1..* HumanName The name(s) associated with the practitioner
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
.... family SO 1..1 string Family name (often called 'Surname')
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
.... given SO 0..* string Given names (not always 'first'). Includes middle names
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Below is an overview of the mandatory and optional search parameters and combined search parameters. See the AU Core CapabilityStatements for a complete list of supported RESTful interactions for this IG.

FHIR search operations are described here and the syntax used to describe AU Core interactions is defined here.

Any search parameter defined in FHIR may be ‘allowed’ by the system unless explicitly marked as “SHALL NOT”. A few items are marked as MAY in this implementation guide to highlight their potential relevance.

Parameter(s) Conformance Type(s) Requirements (when used alone or in combination)
identifier SHALL token The requester SHALL provide at least a code value and SHOULD provide both the system and code values. The responder SHALL support both.

The requester SHOULD support search using a HPI-I identifier as defined in the profile. The responder SHOULD support search using the using a HPI-I identifier as defined in the profile.
_id SHOULD token
name SHOULD string

Mandatory Search Parameters

The following search parameters SHALL be supported:

  1. SHALL support searching a practitioner by an identifier using the identifier search parameter:

    GET [base]/Practitioner?identifier={system|}[code]

    Example:

    1. GET [base]/Practitioner?identifier=http://ns.electronichealth.net.au/id/hi/hpii/1.0|8003619900015717

    Implementation Notes: Fetches a bundle containing any Practitioner resources matching the identifier (how to search by token)

Optional Search Parameters:

The following search parameters SHOULD be supported:

  1. SHOULD support fetching a Practitioner using the _id search parameter:

    GET [base]/Practitioner/[id] or GET [base]/Practitioner?_id=[id]

    Example:

    1. GET [base]/Practitioner/5678
    2. GET [base]/Practitioner?_id=5678

    Implementation Notes: Returns a single Practitioner resource (how to search by the logical id of the resource)

  2. SHOULD support searching for a practitioner based on text name using the name search parameter:

    GET [base]/Practitioner?name=[string]

    Example:

    1. GET [base]/Practitioner?name=Sandyson
    2. GET [base]/Practitioner?name=Sandyson&

    Implementation Notes: Fetches a bundle of all Practitioner resources matching the name (how to search by string)