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

Relationships to Other Specifications

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 local concepts from AU Base, specifying the elements, extensions, vocabularies, and value sets that SHALL be present and how they SHALL be used, along with the RESTful API interactions.
• Use case IGs (AU eRequesting and AU Provider Directory) build on AU Core to address specific use cases, defining a set of conformance requirements on top of AU Core, 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.

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

Relationship to AUeReqDI and other IGs

Australian eRequesting Data for Interoperability (AUeReqDI) builds upon and complements the foundational Australian Core Data for Interoperability (AUCDI) and focuses on the specific use case of eRequesting. The first release of AUeReqDI is focused on electronic pathology and medical imaging requests in primary and community-based care provision.

AUeReqDI defines the clinical data requirements for eRequesting, incorporating relevant data groups from AUCDI and contains additional data groups and elements that facilitate the exchange of a pathology test or medical imaging request.

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

Updates to AU eRequesting depend upon community input and we encourage our audience to submit questions and feedback to AU eRequesting specifications by clicking on the Propose a change link in the footer of every page. In addition, we encourage requesting any necessary clarifications to AUeReqDI through the AUeReqDI process that helps inform future updates to AU eRequesting.

See AU eRequesting data for interoperability for the relationship between AUeReqDI data groups, elements, and AU eRequesting profiles.

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

Figure 3: Relationship to AUeReqDI and Other IGs