| Date |
Version |
Impact |
Description |
| 3 Apr 2026 |
1.2.60 |
|
- Updated
$submit_order operation response model: the single return output parameter type changed from Bundle to Resource so the operation can return either a transaction-response Bundle (directed order success) or an OperationOutcome (error or undirected order). The caller distinguishes between cases by inspecting resourceType.
- Added three
$submit_order response examples: directed order success (transaction-response Bundle), error (OperationOutcome severity error), and undirected order (OperationOutcome severity information). OperationOutcome examples use issue.details (CodeableConcept) rather than issue.diagnostics to support future coded error catalogue.
- Added notes pages for
$submit_order, $claim, $view_request, and $add_placer_subscription operations, surfacing response behaviour, parameters tables, result codes, and examples directly on each operation definition page.
- Updated
requesting.md Submit Order section to document the new response model with a condition/response table and added response examples table.
- Added parameters tables and result codes table to
requesting.md Claim Order section.
- Added parameters table to
requesting.md View Order section and corrected endpoint from POST [base]/$view to POST [base]/Task/$view_request.
- Updated CapabilityStatement: version aligned to IG, date updated, status promoted to
#active. Added all five custom operations: $claim (SHALL) and $view_request (SHOULD) under Task, $get_brands (SHALL) under Organization, $add_placer_subscription (SHALL) under new Subscription resource entry (read + search-type supported), and $submit_order (SHALL) at server level.
- Fixed malformed URL in
request-register.md (http://https:// → https://).
- Fixed grammar in Claim operation description (used create → used to create) and typo in View operation FSH (ciuld → could).
- Fixed four typos in changelog entry for v1.2.33 (seqnecing, teh, numberts, contigious).
- Fixed typos in eOrders profile metadata: disagnostic → diagnostic (
EOrdersCommunicationRequestPatient), Fulillment → Fulfillment (EOrdersCommunicationRequestPatient), Planer → Placer (EOrdersPlacerGroupNumber).
- Standardised eOrders tag code system references: replaced direct
EOrdersTagCodeSystem# references with $eorders-tag# alias throughout all Task instances and profile definitions, consistent with FSH alias conventions.
- Added
owner and _tag search parameter declarations to the Task resource entry in the CapabilityStatement (both SHALL) — these standard FHIR parameters are used in all documented subscription search patterns.
- Declared three custom SearchParameters in the CapabilityStatement:
copiesTo (SHALL) under ServiceRequest, about (SHALL) under CommunicationRequest, and study (SHALL) under a new DiagnosticReport resource entry.
- Populated
patientInstruction in the Pathology, Diagnostic, and Radiology request examples — this element is marked Must Support on the profile but was previously commented out.
- Removed
Bundle-EOrdersPathologyRequestTransaction.fsh — file contained only commented-out code with no explanation and produced no compiled output.
- Resolved consent data meaning uncertainty in both
EOrdersConsentWithdrawl examples: settled on #dependents and removed ambiguity comment referencing the Canadian example.
- Added explanatory NOTE comments to the two disabled task invariants (
task-cancel-detail-1, task-cancel-detail-2) in EOrdersTaskFulfillmentBase explaining why they are disabled and what they are intended to enforce.
- Replaced stale not available in Gentu/Genie comments in
EOrdersDiagnosticRequest with accurate descriptions of why performerType, performer, and reasonCode binding are not constrained.
- Expanded
request-register.md: added Transfer vs Claim Provenance profile table, workflow guidance on when to use each type, and explanation of filler privacy model.
- Corrected clinical error in
EBookingsInfectionRisk: MRSA slice short description incorrectly named Escherichia coli — corrected to Staphylococcus aureus to match SNOMED code 432415000.
- Fixed
ChargeItemDiffExample instance to use EBookingsChargeItem profile instead of the parent GSChargeItem; corrected status from #billed to #planned to conform to the profile's fixed value.
- Fixed typos in eBookings FSH and pagecontent: appintment → appointment (
EBookingsTheatreList), atatchment → attachment (EBookingsAppointment), sould → should (ebookings-difference-intro.md), precedure → procedure (EBookingsConsent).
- Replaced inline URIs with FSH aliases in
EBookingsConsent: $consentscope#treatment and $loinc#59284-0, consistent with FSH alias conventions in aliases.fsh.
- Fixed typos in eBookings narrative: HealthcareServive → HealthcareService and missing backtick around
Organization in bookings.md; mosified → modified and duplicate phrase removed in ebookings-difference-intro.md; invoced → invoiced in ebookings-difference-intro.md.
- Added AppointmentResponse creation workflow to
bookings.md: field reference table, POST and PUT examples, link to example instance.
- Added
Appointment.status transition table to bookings.md (pending → booked → cancelled) and defined what constitutes a 'change of significance' for the lastModified extension.
- Added undirected order lifecycle section to
requesting.md: explains lodging, discovery, claim, and how the placer detects when an undirected order has been claimed.
- Expanded PATCH section in
requesting.md with FHIR Patch (FHIRPath-based) format explanation, field reference table, and two inline examples.
- Added claim error recovery table to
requesting.md with recommended action for each $claim result code.
- Added Getting Started guide and Glossary to
index.md: role-based entry points (placer, filler, hospital, patient portal) and definitions for key terms (placer, filler, brand, directed/undirected order, requisition, group task, VMO).
- Fixed typo in
CapabilityStatement-eorders-capability-intro.md (statatement → statement) and expanded the intro to describe the statement's purpose.
- Fixed typos in
index.md: Interopability → Interoperability, Administative → Administrative.
|
| 1 Apr 2026 |
1.2.59 |
|
- Allow multiple
reasonCode values (0..*) on EOrdersDiagnosticRequestBase and legacy EOrdersDiagnosticRequest ServiceRequest profiles — aligns with base FHIR R4 and AU Base cardinality; child profiles EOrdersPathologyRequest and EOrdersRadiologyRequest inherit the change
- Update
EOrdersPathologyRequest Rule 3 Exemption example to demonstrate multiple reasonCode entries
|
| 27 Mar 2026 |
1.2.58 |
|
- Generalise
EBookingsConsent profile: remove fixed Healthscope-specific policy.authority and policy.uri values so any hospital can supply their own consent policy (backwards compatible relaxation)
- Delete Healthscope NamingSystem — hospital-specific NamingSystems should be managed outside the IG
- Update eBookings Consent examples to use RFC-reserved
example.com authority and policy URI
- Update eBookingsTransaction diagram to use generic consent policy label
|
| 18 Mar 2026 |
|
|
- Removed incorrect
text 1..1 constraint from EOrdersDiagnosticRequestBase and legacy EOrdersDiagnosticRequest ServiceRequest profiles — narrative text requirement applies to supportingInfo resources (EOrdersMedicationStatement, EOrdersAllergyIntolerance), not to ServiceRequest.text
|
| 6 Mar 2026 |
1.2.57 |
|
- Add
placer-family meta tag to EOrdersDiagnosticRequestBase and legacy EOrdersDiagnosticRequest ServiceRequest profiles
- Add
placer-family meta tag to all ServiceRequest examples (standalone and inline bundle instances)
- Define
consistent-placer-tag invariant on EOrdersSubmitOrderBundle ensuring Task and ServiceRequest placer-family tags match within a transaction bundle
- Update requesting page documentation with Placer Family Tag section and bundle profile notes
|
| 5 Mar 2026 |
1.2.56 |
|
- Add placer family tag to all Task examples in SubmitOrder bundles
- Add
$get_brands operation definition for Organization
- Add
$submit_order operation definition and EOrdersSubmitOrderBundle transaction bundle profile
- Add
$add_placer_subscription operation definition for Subscription
- Convert existing bundle examples to conform to
EOrdersSubmitOrderBundle profile
- Add Requesting page documentation with Requesting Service, Placer, Filler, and Patient integration sections
|
| 18 Feb 2026 |
1.2.55 |
|
- Update documentation across various profiles
- Update PATCH examples
- Add digitalonly extension to ServiceRequest for PathologyRequest and RadiologyRequest
- Add filler order to Task output
- Add occurrenceperiod to Task to set fulfilment date
- Make Practitioner optional in PractitionerRole for copyto
|
| 13 Feb 2026 |
1.2.54 |
|
- Update diagnostic request examples to use practitionerrole details
- Better support for contained practitionerrole details in service requests
- Optional report as Task output should actually reference a Task linked to the report as we need to track receipt
- Loosen organization requirement on practitionerrole to allow for copiesto
|
| 11 Feb 2026 |
1.2.53 |
|
- Make copy-to PractitionerRole.organization optional
|
| 11 Feb 2026 |
1.2.52 |
|
- Add details for copies-to PractitionerRole rather than just a name and identifier
- Allow for no selection on eBookings Consent
- Add example of slot/booking for Task.output
|
| 30 Jan 2026 |
1.2.51 |
|
- Add a slot/booking definition and example for use with eRequest Task.out
- Add medication and allergy ServiceRequest.supportingInfo
|
| 16 Jan 2026 |
1.2.50 |
|
- Add support for ADA chargeitem coding in ebooking
- Use correct speciality coding for healthcareservice in vmo org
- Add speciality ValueSet
|
| 07 Nov 2025 |
1.2.49 |
|
- Add contained HealthcareService into VMO practice Organization to carry speciality
- Create new Path and Imaging Organization profiles for eRequesting to support parent brands
- New VMO PractitionerRole and Organization profiles for eBooking to support contained HealthcareService speciality
- Separate tasks in report for receipt and copyto
- Update eBooking documentation with new diagram and search guidance
- Diagnostic reports now expect a separate practice organization resource
|
| 16 Oct 2025 |
1.2.48 |
|
- Fix to ebookings supportingInformation slicing to be by profile not type
|
| 08 Oct 2025 |
1.2.47 |
|
- Add an mbscodes alias to IG build
- Include dicom as dependency in sushi to fix publisher errors
- Remove a couple of invalid markdown references in documentation
- move to 2.0.20 version of publisher
- lock down task fulfilment base to get past publisher bug?
|
| 07 Oct 2025 |
1.2.46 |
|
- Add narrative to supportingInfo examples
- Make HRT have mandatory narrative
- Fix copyto reference to ValueSet
- Fix FAXWRITE code
|
| 01 Oct 2025 |
1.2.45 |
|
- add fax as an urgent results contact option
- Make note on ServiceRequest Must Support
- Add an HRT Observation to support HRT flag in Genie
- Remove old diagrams not used in IG anymore
- Add an option on an urgent results communication request to have a date by which it is needed
|
| 24 Jul 2025 |
1.2.44 |
|
- Fix Imaging Report transaction bundle example.
- Make requester and recipient of a CopyTo a PractitionerRole for Imaging Reports.
|
| 23 Jul 2025 |
1.2.43 |
|
- Make consistent references to ebookings-patient rather than gs-patient in EBookings.
|
| 16 Jul 2025 |
1.2.42 |
|
- Add $view_request operation to support patient portal access to requests and their fulfilment.
- Add copyto as new eorders task tag for processing reciept of report copies.
- Add employee number as an identifier for eorders PractitionerRole.
- Allow organization to be contained in a radiology request.
- Add CommunicationRequest and a tracking Task to be added into a report transaction to support CopyTo.
- Remove invariants from GSCoverage as erroring when Patient resource not in bundle.
|
| 25 May 2025 |
1.2.41 |
|
- Add naming system for practice identifiers like GEN/GTU.
- Add infection risk profile to cover HIV, Hep B, Hep C, and MRSA.
- Add adverse reaction profile.
- Add related person to cover next of kin and emergency contact.
- Add paediatrician and ICU as Appointment participants.
- Add extension for fasting time to booking ServiceRequest.
|
| 23 May 2025 |
1.2.40 |
|
- New diagram to better describe status changes between Appointment and AppointmentResponse for theatre bookings.
- New HealthcareService profile for organisation specialties.
- Updated requesting and booking documentation.
|
| 2 May 2025 |
1.2.39 |
|
- Modify booking diff to use a separate list for attributes.
- New search parameter for imaging study in DiagnosticReport. It is there in R5.
- Add NamingSystems to define URIs in use in IG.
- Create new businessStatus for claimed-cancel and remove invariants for now that restrict businessStatus claimed use while we transition.
|
| 27 Apr 2025 |
1.2.38 |
|
- Add new basic resource profile to store theatre booking diff. Note this is likely to fail if strict checking of valid references as a deleted resource, i.e. MBS code/ChargeItem, will be referenced but won't exist.
- Get sushi to structure artefact page rather than use defined groups.
- Add ImagingStudy to DiagnosticReport for imaging to so can store when images were collected. Create example.
- Remove slice on Patient address as fails on non AU address. Replace with Invariant checking for a residential address to be provided. Fix examples.
- Minor updates to fix descriptions and titles on some profiles.
|
| 1 Apr 2025 |
1.2.37 |
|
- Rename instances within RequestProvenance as had a repeat of names previously.
- Fix claim operation so based on Task not ServiceRequest
- Add cancel-handled in as businessStatus for Task so filler can use to differentiate processed cancelled Status's
- Fix claim example using GET rather than POST
|
| 3 Mar 2025 |
1.2.36 |
|
- Move to 1.2.36 to match jiang update to main branch structure. Pulls in 1.2.35 changes.
|
| 26 Feb 2025 |
1.2.35 |
|
- Fix spelling of claim error code of already-fulfiller
- Add more detail in documentation for various things
- Support initial claimed order status of requested rather than accepted
- Add displaySequence example for diagnostic requests
|
| 11 Feb 2025 |
1.2.34 |
|
- Make background ribbons the Magentus purple
- Some renaming to remove duplicate FHIR artefact names
- Add profile for request provenance which links to the stored request bundles
- Restructure artifacts page so it is grouped by artifact use
|
| 21 Jan 2025 |
1.2.33 |
|
- Add a sequenceNumber to ServiceRequests to provide sequencing information for tests. These are inherent on the paper form but natively, FHIR ServiceRequests have no explicit or implicit order. This extension adds this sequence information. The relative order of each ServiceRequest sequence number determines the order, from lowest to highest number. The numbers do not need to be contiguous.
|
| 19 Dec 2024 |
1.2.32 |
|
- Minor changes to titles and comments as they appear in the rendered IG.
- Align the PractitionerRole profile used in Reports with that used in Requests.
|
| 19 Nov 2024 |
1.2.31 |
|
- Make insurance optional in Diag Req as it is in Path and Rad Request.
- Make rcpa codes preferred rather than extensible in binding strength.
|
| 18 Nov 2024 |
1.2.30 |
|
- Add Radiology and Pathology Request profiles to work alongside the generic Diagnostic Request. This modifies Task, Consent, and CommunicationRequest profiles.
|
| 13 Nov 2024 |
1.2.29 |
|
- Fix search documentation for eRequest to include copiesto data.
- Fix display values in instances for various codes.
- Change to use value instead of pattern as slcing discriminator type as pattern is deprecated.
- Move PractitionerRole contact profile into CommuncationRequest for urgent communciation to provider.
- Overwrite comment field in profiles where an invalid html reference is generated (publisher bug but this at least removes issue).
- Update description of CommunicationRequest to restrict SMSs to patient.
|
| 31 Oct 2024 |
1.2.28 |
|
- Add pathology report example.
- Move to referring to named slices in fsh rather than anonymous slices.
- Use Canonical references rather than explicit references to structure definitions.
- Remove genie local fasting extension and use the published service request precondition extension.
- Add an example of using Appointment.lastModified extension.
- Add ACN as a named organization identifier.
|
| 23 Oct 2024 |
1.2.27 |
|
|
| 22 Oct 2024 |
1.2.26 |
Magentus |
- Replace GSCoverage use with EOrdersCoverage for requests.
|
| 22 Oct 2024 |
1.2.23 |
Magentus |
- Attempt to use both GSCoverage and EOrdersCoverage.
|
| 22 Oct 2024 |
1.2.22 |
Magentus
Partner |
- Add lastModified extension to Appointment.
- Move to AUBaseDiagnosticRequest to avoid R4 publisher warning.
- Add experimental status to various profiles to avoid publisher warnings.
- Introduce local IG pregnancy profiles for future use.
|
