# Relationship With Other IGs - AU Core Implementation Guide v3.0.0-ballot1

* [**Table of Contents**](toc.md)
* [**Guidance**](guidance.md)
* **Relationship With Other IGs**

## Relationship With Other IGs

| |
| :--- |
| *Page standards status:*[Informative](http://hl7.org/fhir/R4/versions.html#std-process) |

This guide is built on top of the FHIR standard and, where available, [AU Base](https://build.fhir.org/ig/hl7au/au-fhir-base/).

### Relationship to HL7 AU Base

**AU Base:**

* defines Australian realm concepts (e.g. Medicare card number) as an additional set of options to what is available in the FHIR standard including extensions and terminology.
* provides ‘Base’ profiles to inform a reader of which added concepts are considered relevant to a particular resource type.
* does not apply cardinality constraints or required binding strengths that enforce conformance to those concepts except in rare circumstances. Must support flags are not utilised in AU Base profiles.
* does not recommend or mandate any particular resource, element, or interactions.

**AU Core:**

* defines a set of conformance requirements that enforce a set of 'minimum requirements' on the local concepts from AU Base, specifying rules for the elements, extensions, vocabularies, and value sets, and the RESTful API interactions.
* for use by Australian stakeholders when implementing FHIR to provide a common implementation and to be built upon when creating further Australian profiles and implementation guides.
* conformance may become tied to regulatory and/or contractual agreements in order to necessitate adoption to this more prescriptive specification.

The context of AU Core within the set of HL7 AU standards is shown in the figure below.

**Figure 1: Context of AU Core within the set of HL7 AU FHIR standards** 

### Relationship to AUCDI and Other IGs

The primary intent of the [AUCDI](https://sparked.csiro.au/index.php/sparked-products-resources/aucdi/) is to design and govern a collection of coherent, reusable building blocks known as data groups. These data groups specify “what” the clinical requirements of the clinical information that should be included for data entry, data use, and sharing of information supporting healthcare delivery. However, it does not specify "how" the data is exchanged; this is the role fulfilled by the FHIR standard. AUCDI is not required to be implemented as a whole single product. Parts can be implemented as required for specific use cases.

AUCDI R1 (published in June 2024) concentrated on identifying essential 'core of the core' data elements; already present within most existing clinical systems. These data elements represented the absolute minimum data required to support standardised clinical information capture at the point of care and for safe and meaningful exchange of information to other care providers. AUCDI R2 builds upon R1, expanding on the initial 'core', introducing additional data groups to support different use cases including 'Patient summary'.

AU Core is intended to provide an implementable standard for FHIR based interfaces for provider and patient information systems in Australia​ providing:

* an exchange standard for AUCDI (the underpinning clinical data model)
* Data model and RESTful API interactions that set minimum expectations for a system to record, update, search, and retrieve core digital health and administrative information​
* be built on top of for standards development for specific use cases

With AUCDI defining clinical data requirements and FHIR AU Core providing detailed FHIR-based profiles for meeting clinical data requirements and administrative data requirements, an interpretation of AUCDI is necessary which is undertaken through the community.

See the [AUCDI](aucdi.md) page for the relationship between the 'Core' AUCDI data groups, elements, and AU Core profiles.

AU Core aligns to, and leverages international standards and other national standards. Corresponding profiles included in relevant FHIR implementation guides were reviewed and considered during the development process to ensure alignment and to facilitate adoption of this standard. These implementation guides include:

* [HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation, Edition 1](https://hl7.org/xprod/ig/uv/gender-harmony/informative1/)
* [International Patient Access 1.1.0](https://hl7.org/fhir/uv/ipa/STU1.1/)
* [International Patient Summary 2.0.1](https://hl7.org/fhir/uv/ips/2.0.1/)
* [US Core 8.0.1](https://hl7.org/fhir/us/core/STU8.0.1/)

The relationship of AU Core to AUCDI and other implementation guides is shown in the figure below.

**Figure 2: Relationship to AUCDI and Other IGs** 

| | |
| :--- | :--- |
| [AU Base](https://build.fhir.org/ig/hl7au/au-fhir-base/) | This IG defines Australian realm concepts including terminology, identifiers, and extensions. AU Core uses AU Base, where available, as the basis for profiles that define the FHIR resources to be supported, and the elements, extensions, vocabularies, and value sets, and how they are used is defined. Where available and applicable, AU Base concepts are profiled in AU Core. |
| [HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation](https://hl7.org/xprod/ig/uv/gender-harmony/informative1/) | This IG provides definitive guidance on how to exchange clinical sex and gender affirming information using HL7 models. Sex and gender concepts from this IG have been reviewed for the potential for adoption in Australia. Where adopted, these concepts are included by reference in AU Base and are available for use in AU Core via inheritance from AU Base. |
| [International Patient Access 1.1.0](https://hl7.org/fhir/uv/ipa/STU1.1/) | This IG describes how an application acting on behalf of a patient can access information about the patient from a clinical records system using a FHIR based API. The REST API and profiles in this IG were reviewed and considered during development of AU Core. AU Core is designed to be compatible with IPA, e.g. AU Core conformant data can be accessed by an IPA conformant client. |
| [International Patient Summary 2.0.1](https://hl7.org/fhir/uv/ips/2.0.1/) | This IG describes how to represent in HL7 FHIR the International Patient Summary (IPS). An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. The profiles in this IG were reviewed and considered during development of AU Core. AU Core is designed to be compatible with IPS, e.g. AU Core conformant data can be used to generate a patient summary that is conformant to IPS. |
| [US Core 8.0.1](https://hl7.org/fhir/us/core/STU8.0.1/) | This IG is the foundation for US Realm FHIR implementation guides. It defines the minimum constraints on the FHIR resources to create the US Core Profiles. The elements, extensions, vocabularies, and value sets, and how they are used is defined. It also documents the minimum FHIR RESTful interactions for each US Core Profiles to access patient data. The REST API and profiles in this IG were reviewed and considered during development of AU Core. AU Core is compatible where possible. |

See [Comparison with other national and international IGs](comparison.md) for a comparison between AU Core profiles and profiles in other implementation guides.

