AU PS Test Kit
Use this kit if your system produces or serves an AU Patient Summary document. It validates a patient summary Bundle against the AU PS 1.0.0 implementation guide and tells you exactly which element or section is wrong.
There are three ways to test, pick the one that matches what you have:
- Paste a Bundle. You have a patient summary document as JSON or XML. No server needed. Choose AU PS Bundle Instance.
- Fetch a Bundle from your server. Give Inferno a Bundle URL, or your FHIR base URL and a Bundle id. Choose Retrieve AU PS Bundle.
- Generate one with
$summary. Your server implements the IPS$summaryoperation. Give Inferno the base URL and a patient id or identifier. Choose Generate AU PS using IPS $summary.
A separate Retrieve Capability Statement group checks that a server advertises AU PS support. Run it alongside either server path.
What this test kit checks
Every path runs the same validation over the patient summary Bundle it obtains:
- The Bundle is a valid AU PS Bundle (and optionally a valid IPS Bundle as well).
- Must Support elements on the Bundle and the Composition are populated when a value is known.
- Mandatory sections (Problems, Allergies and Intolerances, Medication Summary) are present and populated with the right profiles. Recommended and optional sections are checked the same way when present.
- Mandatory sections use an explicit "no known ..." entry rather than
emptyReason = nilknown. This is a warning, not a failure. - The Composition subject, author, custodian and attester resolve to correctly populated AU PS Patient, Practitioner, PractitionerRole, Organization, RelatedPerson or Device resources, including identifier slices such as IHI, Medicare and DVA numbers.
The server path also checks that your CapabilityStatement declares the AU PS profiles and the IPS operations ($summary, $docref).
Open any test in the session to read exactly what it asserts and which part of the IG it comes from.
How to run a test
- Click Create Test Session. Inferno opens a new session with a shareable URL; keep it, it is your record of the run.
- In the left panel choose the group that matches how you want to test (see the three ways above). You do not need to run the whole suite.
- Click Run Tests and fill in the inputs. Only the fields for the path you chose are needed; leave the rest empty.
- Wait for the run to finish, then open any failed test and read the Messages tab. Validator messages point at the exact element in your Bundle.
Fix, re-run the same group, repeat. See Reading results for what pass, fail, skip and omit mean.
Before you start
- Use synthetic data only. This is a public service. Do not paste or expose real patient data.
- Server paths need a reachable endpoint. Inferno on hl7.org.au calls your server from the internet, so it cannot reach localhost or anything behind a VPN. Use the paste-a-Bundle path for local work, or run the kit locally.
- Authentication is optional. Supply a bearer token via OAuth credentials, or a custom header name and value, when the session asks.
- Need a sample? The AU PS IG examples and the HL7 AU FHIR test data repository have Bundles you can paste to see what a passing run looks like.
Feedback and issues
If a test fails and you believe your Bundle is right, or a check is missing, tell us. The fastest route is the Inferno Test Kit feedback and queries topic on chat.fhir.org. Include the session URL.
For bugs and requests open an issue in hl7au/au-ps-inferno. The README explains what to include.
Source, versions and licence
Tests AU PS 1.0.0. See the IG history for other publications.
Source: github.com/hl7au/au-ps-inferno, built on the Inferno Framework and released under the Apache License 2.0. Free to run locally or adopt in your own test programme.
This is a reference test kit, not a certification. Passing here does not confer conformance status; see About.
