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

AU eRequesting Data for Interoperability Mappings

Australian eRequesting Data for Interoperability (AUeReqDI) is the product of a national clinician focussed requirements gathering project operating as part of the Sparked AU FHIR Accelerator. AUeReqDI outputs form a set of data requirements to be considered and referred to as part of the development and definition of AU eRequesting.

The primary intent of AUeReqDI 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 eRequests. However, it does not specify “how” the data is exchanged; this is the role fulfilled by the FHIR standard. AUeReqDI is not required to be implemented as a whole single product. AUeReqDI builds upon and complements the foundational Australian Core Data for Interoperability (AUCDI) and focuses on the specific use case of eRequesting.

AUeReqDI Release 1 (R1) is focused on an agreement of the minimum data required to support standardised eRequesting within the Australian health context, and forms a common language foundation that allows systems to exchange semantically accurate data for eRequests. It incorporates and builds upon prior work from national and international programs and initiatives, including the Royal College of Pathologists of Australiasia (RCPA)’s Pathology information, Terminology and Units Standardisation (PITUS) framework and the Royal Australian New Zealand College of Radiology (RANZCR’s) Radiology Referral Set.

With AUeReqDI defining clinical data requirements and FHIR AU eRequesting providing the Implementation Guide for FHIR-based electronic requesting of diagnostic imaging and pathology services, an interpretation of AUeReqDI is necessary which is undertaken through the community.

Updates to AU eRequesting and AU Core depend upon community input and we encourage our audience to submit questions and feedback on implementation guides by clicking on the Propose a change link in the footer of every page. We encourage requesting any necessary clarifications to AUeReqDI or AUCDI through through the respective process that helps inform future updates to FHIR AU eRequesting and AU Core.

AUeReqDI mappings into AU eRequesting

The table below shows the relationship between AUeReqDI and AUCDI Data Groups and Elements and AU eRequesting and AU Core profiles.
Column attribute descriptions are as follows:

• AUeReqDI/AUCDI Data Group: Represents a grouping of one or more AUeReqDI or AUCDI Data Elements.
• AUeReqDI/AUCDI Data Element: Represents a single, discreet clinical concept defined by AUeReqDI or AUCDI.
• AU eRequesting Profile(s)/AU Core Profile(s): Represents the mapping of AUeReqDI or AUCDI Data Groups and Data Elements to AU eRequesting or AU Core FHIR artefacts.
• FHIR Path: The specific path in the FHIR standards for each AUeReqDI or AUCDI Data Element within, showing where and how to implement these elements in FHIR-based systems.
• Comment: Additional information about the mapping including an explanation of where an element or group is not yet mapped.