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 Organization

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

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 Organization resource to record, search, and fetch information about an organisation. It is based on the AU Base Organization profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Organization 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:

  • Query for basic information for an organisation by name or identifier
  • Recording or updating basic information for an organisation
  • Read information about an organisation referenced by another resource

Comparison with other national and international IGs

A resource conforming to this profile is conformant to:

No equivalent International Patient Access profile.

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

Profile specific implementation guidance

  • See guidance on the construction of an identifier on the relevant Identifier profile page and the section on Business Identifiers in AU Base.
  • When constructing an address
    • an international address can be represented using the core Address data type
    • an Australian address SHOULD be represented using the Australian Address data type profile

Feedback is requested on the following search considerations:

  • Query if the existing recommendation in AU Core to support ABN identifiers in identifier parameter search should be removed.
Please comment on HL7 Jira FHIR-43837.

Usage:

Formal Views of Profile Content

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

This structure is derived from AUBaseOrganisation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Organization 0..* AUBaseOrganisation An organisation in an Australian healthcare context
... Slices for identifier SOC 0..* Identifier, AUHPIO, AUPAIOIdentifier, AUCSPRegistrationNumber, AUAustralianBusinessNumber, AUAustralianCompanyNumber, AUAustralianRegisteredBodyNumber, AUNATAAccreditationNumber, AUPharmacyApprovalNumber Identifies this organization across multiple systems
Slice: Unordered, Open by pattern:system
au-core-org-01: A National Organisation Identifier (type=NOI) shall be an HPI-O or PAI-O
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
.... identifier:hpio SO 0..1 AUHPIO Healthcare Provider Identifier – Organisation (HPI-O)
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
.... identifier:abn SO 0..* AUAustralianBusinessNumber Australian Business Number (ABN)
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
... type SO 0..* CodeableConcept Kind of organization
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
... name SO 1..1 string Name used for the organization
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester
... address SO 0..* Address, AustralianAddress An address expressed using postal conventions (as opposed to GPS or other location definition formats)
ObligationsActor
SHALL:populate-if-known AU Core Responder
SHALL:no-error AU Core Requester

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
au-core-org-01errorOrganization.identifierA National Organisation Identifier (type=NOI) shall be an HPI-O or PAI-O
: type.coding.where(code='NOI').exists() implies ((system='http://ns.electronichealth.net.au/id/hi/hpio/1.0') or (system='http://ns.electronichealth.net.au/id/pcehr/paio/1.0'))

 

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 HPI-O and ABN identifiers as defined in the profile. The responder SHOULD support search using the using HPI-O and ABN identifiers as defined in the profile.
address SHOULD string
name SHOULD string
_id SHOULD token

Mandatory Search Parameters

The following search parameters SHALL be supported:

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

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

    Example:

    1. GET [base]/Organization?identifier=http://ns.electronichealth.net.au/id/hi/hpio/1.0|8003621566684455
    2. GET [base]/Organization?identifier=http://hl7.org.au/id/abn|23964200000

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

Optional Search Parameters:

The following search parameters SHOULD be supported:

  1. SHOULD support searching for an organisation based on text address using the address search parameter:

    GET [base]/Organization?address=[string]

    Example:

    1. GET [base]/Organization?address=QLD

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

  2. SHOULD support searching for an organisation based on text name using the name search parameter:

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

    Example:

    1. GET [base]/Organization?name=Hospital

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

  3. SHOULD support fetching an Organization using the _id search parameter:

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

    Example:

    1. GET [base]/Organization?_id=5678

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