New example workloads: AU eRequesting pipelines for Harmony

Australia’s AU eRequesting work is building a shared, standards-based way to place and access electronic diagnostic requests—starting with pathology and medical imaging requests in community-based care.

The AU eRequesting Implementation Guide (currently under development) captures the emerging expectations for how systems place, exchange, and access eRequests, and is part of the broader Sparked program of Australian national FHIR standards.

The work is being developed in the open through the Sparked AU FHIR Accelerator community: a collaborative group spanning government, practitioners, domain experts, technology vendors, and provider organisations.

• AU eRequesting Implementation Guide: https://build.fhir.org/ig/hl7au/au-fhir-erequesting/
• Sparked AU FHIR Accelerator: https://sparked.csiro.au/

Two AU eRequesting example workloads in the catalogue

We’ve added two new AU eRequesting pipelines that help you integrate eRequesting workloads with existing services.

These are intended as example starting points you can deploy and adapt for your environment—so teams can trial the flows early, understand how the message shapes fit together, and iterate alongside the evolving AU eRequesting specifications.

1) AU eRequesting: HTTP to FHIR

This workload is aimed at the “edge” of an application: accept a conventional HTTP request (for example, from a lightweight UI or an existing service) and produce an AU eRequesting-aligned FHIR Bundle.

Typical reasons you might start here:

• You want to generate a compliant request bundle while keeping your upstream integration surface simple.
• You need a clear place to apply mapping and validation rules before publishing bundles further downstream.

2) AU eRequesting: FHIR to HTTP

This workload does the inverse: accept an AU eRequesting FHIR Bundle and convert it into downstream HTTP API calls for backend services.

Typical reasons you might start here:

• You already exchange FHIR bundles but still need to integrate with HTTP-based backends.
• You want a controlled gateway point that can route, transform, and audit requests before they reach internal systems.

Demonstrated at the HL7 Connectathon (Melbourne, December 2025)

These two example workloads were demonstrated at the HL7 Connectathon in Melbourne in December 2025, alongside community work progressing AU eRequesting.

Christopher Skene (Runbeam) is an AU eRequesting Co-Chair, and we’re using these examples to make it easier for implementers to test ideas quickly and share repeatable patterns.

How to try them

1. Select a Workload on this page, or go to the Workloads page and search for AU eRequesting.
2. Open the workload and review the template name and data flow.
3. Deploy the template, then customise routes, transforms, and upstream/downstream endpoints to match your environment.

If you’d like, tell us what system pairing you’re integrating (requester, fulfilment system, lab/radiology, and transport constraints) and we can point you to the fastest path to a working proof-of-flow.