AU eRequesting Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 0.2.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

Home

Official URL: http://hl7.org.au/fhir/ereq/ImplementationGuide/hl7.fhir.au.ereq				Version: 0.2.0-ci-build
IG Standards status: Draft			Maturity Level: 0	Computable Name: AUeRequestingImplementationGuide
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License. HL7 Australia© 2024+; Licensed Under Creative Commons No Rights Reserved.

Introduction

AU eRequesting is provided to support the use of HL7^® FHIR^®© for diagnostic requesting in an Australian context. It sets the minimum expectations on FHIR resources to support conformance and implementation in systems.

AU eRequesting defines the Data model and RESTful API interactions that set minimum expectations for placing and accessing electronic requests.

The focus AU eRequesting Release 1 (R1) is support of pathology and medical imaging requests in community-based care provision, and developing a foundational request model that can be applied beyond diagnostic requesting.

Project background

This implementation guide is under development through the AU eRequesting project as part of the Sparked AU FHIR Accelerator. The Sparked AU FHIR Accelerator is a community comprising government, technology vendors, provider organisations, peak bodies, practitioners, and domain experts, to accelerate the creation and use of national FHIR standards in health care information exchange.

The Sparked AU FHIR Accelerator includes:

• AU eRequesting Data for Interoperability - clinician focussed data requirements
• AU eRequesting FHIR Implementation Guide - HL7 Australia technical data access and exchange specification

The Australian eRequesting Data for Interoperability (AUeReqDI) 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. AUeReqDI outputs form a set of data requirements to be considered and referred to as part of the development and definition of AU eRequesting.

Dependencies

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.au.base#4.2.2-ci-build This implementation guide is provided to support the use of FHIR®© in an Australian context. (built Fri, Nov 15, 2024 02:47+0000+00:00)

Package hl7.fhir.uv.ipa#current This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Thu, Oct 3, 2024 12:52+0000+00:00)

Package hl7.fhir.au.core#1.0.0-ci-build This implementation guide is provided to support the use of FHIR®© in an Australian context, and defines the minimum set of constraints on the FHIR resources to create the AU Core profiles. This implementation guide forms the foundation to build future AU Realm FHIR implementation guides and its content will continue to grow to meet the needs of AU implementers. (built Wed, Nov 20, 2024 23:07+0000+00:00)

AU eRequesting FHIR RESTful interactions

The RESTful interaction requirements for AU eRequesting actors, such as read and search operations, are outlined in the AU eRequesting CapabilityStatements. AU eRequesting Actors and their respective CapabilityStatements are defined in Actors and Capabilities.

The diagram below illustrates the interactions between the various actors:

Figure 1: FHIR RESTful interactions

Note: AU eRequesting Actor interactions will transition with the introduction of the Task resource, which will become central to fulfilment.

AU eRequesting typical sequence

The AU eRequesting Placer actor can create and update ServiceRequest details by calling the AU eRequesting Server actor.

The AU eRequesting Patient actor can search for ServiceRequest details by calling the AU eRequesting Server actor.

The AU eRequesting Filler actor can retrieve ServiceRequest details by calling the AU eRequesting Server actor.

Actors operate in a typical sequence where placers initiate a request by creating (and updating) service requests, patients may access details of their requests and fillers retrieve service request details to enable fulfillment of the requests.

This sequence is shown in the diagram below:

Figure 2: Actors Typical Sequence

How to read this guide

This guide is divided into several pages which are listed at the top of each page in the menu bar.

• Home: This page provides the introduction and scope for this guide.
• Conformance: This page describes the set of rules to claim conformance to this guide
• Guidance: These pages list the guidance for this guide.
  • AU eRequesting Data for Interoperability: This page maps AUeReqDI data groups and elements to FHIR artefacts in AU eRequesting.
  • Relationships to Other Specifications: This page provides guidance on the relationship between AU eRequesting, AUeReqDI, and other implementation guides.
  • AU eRequesting Data for Interoperability Mappings: This page maps AUeReqDI data groups and elements to FHIR artefacts in AU eRequesting.
  • Relationship with other IGs: This page provides guidance on the relationship between AU eRequesting, AUeReqDI, and other implementation guides.
  • AU Variance Statement: This page documents variance from AU Base and AU Core.
  • Future of AU eRequesting: This page outlines the approach to developing AU eRequesting and yearly update cycle.
• Use Cases: This page describes the use cases in scope of eRequesting R1.
• FHIR Artefacts: These pages provide detailed descriptions and formal definitions for all the FHIR artefacts defined in this guide.
  • Profiles and Extensions: This page describes the profiles and extensions that are defined in this guide to support electronic requesting. Each profile page includes a narrative description and guidance, formal definition and a “Notes” section which summarises the supported search transactions for each profile. Although the guidance typically focuses on the profiled elements, it may also may focus on un-profiled elements to aid with implementation.
  • Terminology: This page lists the value sets and code systems supported in this guide.
  • Actors and Capabilities: This page defines the AU eRequesting actors and their respective CapabilityStatements.
• Examples: This page lists all the examples used in this guide.
• Support: These pages provide supporting material for implementation of AU eRequesting.
  • Downloads: This page provides links to downloadable artefacts.
  • License and Legal: This page outlines the license and legal requirements for material in AU eRequesting.

Collaboration

This guide is the product of collaborative work undertaken with participants from:

• Sparked HL7 AU Technical Design Group
• HL7 Australia FHIR Working Group
• Australian FHIR Implementers Community

Primary Editors: Brett Esler, Danielle Tavares-Rixon, Dusica Bojicic.