ARCHIVE Orders and Observations Work Group
- Brett Esler
Co-chairs: Dr Michael Legg & Dr Andrew McIntyre
This group was formed as one of its first by HL7 Australia to address transmission of observation requests and reports. It mirrors the Hl7.org working group "Orders and Observations".
The mission of the Orders and Observation work group is to define information exchange capabilities to support the order/scheduling and clinical event management/reporting requirements between the stakeholders in healthcare organizations regarding patients, non-patients, people, other species, or inanimate objects. These information exchanges are not limited to intra-organizational transactions, but cross organizational boundaries. These information exchanges may involve messages, documents, services, profiles and other HL7 constructs.
The initial focus is pathology but as for the Hl7.org O&O the scope may cover general observations, findings, impressions recorded as quantitative, qualitative, codes, or narrative text. HL7 v2 is now being used for such content in Australia.
The first activity of the Hl7.au O&O group is to develop the 'Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4' with the support of the RCPA led PITUS project. Published at HL7AUSD-STD-OO-ADRM-2021.1
All Publications Listed at HL7 Australia V2 Standards Development
Published Standards by the HL7AU Orders and Observation Working Group
Active/Approved
Past - Replaced/Retired
HL7AUSD-STD-OO-ADRM-2017.1 Australian Pathology Messaging - Localisation of HL7 Version 2.4 (Superseded)
Upcoming meetings:
TBD
Join the ongoing conversations in our HipChat rooms.
-
2 Patient Administration for PathologyNov 28, 2024 • commented by Anonymous
-
Australian Diagnostics and Referral Messaging - Localisation of HL7 Version 2.4Sept 11, 2024 • contributed by HL7 V2 Work Group
-
HL7 V2 Work GroupDec 21, 2023 • contributed by HL7 V2 Work Group
-
HL7AU - HL7V2 WGJul 14, 2023 • contributed by Brett Esler
-
ARCHIVE Orders and Observations Work GroupJul 11, 2023 • contributed by Brett Esler
View current issues in JIRA here