MHR AU Patient Summary Consultation - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Page standards status: Informative |
This page provides guidance for participants in the Sparked Testing Event, including key artefacts, assumptions, and setup notes.
⚠️ Please note: This is a temporary test server. It may be unavailable at times, and no conclusions should be drawn about the Agency’s future direction based on its configuration.
Postman Collection
A Postman collection is available in the GitHub repository associated with this Implementation Guide. It can be accessed from https://github.com/AuDigitalHealth/sparked-testing/tree/main/Postman%20Collection. The collection provides example requests and workflows to support testing activities.
document Bundle within the resulting searchset Bundle from the Named Query.FHIR Document Uploads for Testing
For the purposes of this event, it is assumed that the content required to generate the Patient Summary document is uploaded as FHIR documents.
In a real-world MHR scenario, this content would typically be in CDA format. One of the strengths of the FHIR Named Queries is that they abstract away the original format of the data, allowing for consistent access regardless of source format.
Patient Story Section
The Patient Story section assumes that patients or their carers can add annotations—such as personal stories and health goals—via a conformant portal. While this is not yet part of the final design, it is being actively explored. To support this scenario in testing, we assume that a Patient Summary document can be uploaded to MHR. This is not yet confirmed as a supported feature, but it enables testing of the Patient Story concept.
composition.patient.identifier Search ParameterYou do not need to execute this request—the Agency will run it once on the test server.
It’s included to highlight that the logic of the Named Query relies on thePatient.identifierto locate relevant documents. This identifier must match the one provided as a parameter when executing the query.
If you only want to test the Named Query using the preloaded patient "Mia", you can skip this step.
Composition.subject.identifier matches the Patient.identifier used in the Named Query.section-lookback parameter does not request the Immunisation section, the AIR document will not be included.
Also note the default lookback period if none is specified. These details are covered in the Named Query documentation.
Upload Patient-Annotated Patient Summary Document
If this request is executed and the Patient Story section is requested, the patient’s annotations (e.g. story and goals) will be included in the generated summary.