AU eRequesting
0.1.0-ci-build - ci-build Australia flag

AU eRequesting, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 0.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-erequesting/ and changes regularly. See the Directory of published versions

Relationship with other HL7 AU FHIR IGs

This guide is built on top of the FHIR standard and AU Base.

Relationship with HL7 AU Base

Figure 1: Relationship with HL7 AU Base and AU Core

The context of AU eRequesting within the set of HL7 AU standards is shown in the figure below:

  • the FHIR standard is the foundation, which creates a common platform or foundation on which a variety of different solutions are implemented.
  • AU Base defines local concepts for use in an Australian context introducing relevant identifiers, terminology, extensions.
  • AU Core defines a set of conformance requirements that enforce a set of ‘minimum requirements’ on the Australian localised concepts from AU Base through cardinality constraints, must support flags, required/extensible binding strengths, and capability statements.
  • Provider Directory defines a set of conformance requirements for the purpose of implementation of provider directory services.
  • AU eRequesting (and other use case IGs) build on AU Core to address specific use cases, defining a set of conformance requirements for electronic requesting, using additional building blocks from AU Base as needed.

This layering of IGs balances relative adoption and implementation maturity of FHIR and requirements of the use cases involved.

Context of AU Core within the set of HL7 AU standards

Figure 2: Context of AU eRequesting within the set of HL7 AU standards

Relationship to AUeReqDI and other IGs

TBD AU eRequesting Data for Interoperability (AUeReqDI) statement.

TBD statement on relationship between AUeReqDI and AU eRequesting IG.

​See AU eRequesting data for interoperability for the relationship between the AUeReqDI Data Groups and Elements and AU eRequesting profiles.

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

Relationship to AUeReqDI and Other IGs

Figure 3: Relationship to AUeReqDI and Other IGs

Implementation Guide Relationship
AU Base This IG defines Australian realm concepts including terminology, identifiers, and extensions. AU Core uses AU Base as the basis for profiles that define the FHIR resources to be supported, and the elements, extensions, vocabularies, and value sets that SHALL be present are identified, and how they are used is defined.
AU Core This IG defines a set of conformance requirements that enforce a set of ‘minimum requirements’ on the Australian localised concepts from AU Base through cardinality constraints, must support flags, required/extensible binding strengths, and capability statements. AU Core uses AU Base as the basis for profiles that define the FHIR resources to be supported, and the elements, extensions, vocabularies, and value sets that SHALL be present are identified, and how they are used is defined.
HL7 Cross Paradigm Implementation Guide: Gender Harmony - Sex and Gender Representation 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 AU Base.