The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed
or info@snomed.org
.
HL7 FHIR® Licensing and Legal Terms should also be referenced as the underlying standards published terms on which HL7 Australia FHIR Implementation Guides depend. ( src
)
HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR logo are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office. ( src
)
Most trademarks used in conjunction with HL7® products, services and activities are registered and/or owned by HL7 International, rather than by HL7 Australia, and their use is subject to the associated HL7 International IP policies and licensing terms. ( src
)
For example codes, see
Procedure http://hl7.org/fhir/ValueSet/procedure-code
( example
to https://healthterminologies.gov.au/fhir/ValueSet/procedure-1
)
The codes SHOULD be taken from For example codes, see
Reason for Request http://hl7.org/fhir/ValueSet/procedure-reason
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/reason-for-request-1
)
The codes SHOULD be taken from For example codes, see
Body Site http://hl7.org/fhir/ValueSet/body-site
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/body-site-1
)
The codes SHALL be taken from For codes, see
Pathology Fasting Status
( required
to https://healthterminologies.gov.au/fhir/ValueSet/pathology-fasting-status-1
)
The codes SHOULD be taken from For example codes, see
RANZCR Radiology Referral http://hl7.org/fhir/ValueSet/procedure-code
( preferred
to https://ranzcr.com/fhir/ValueSet/radiology-referral-1
)
Work is underway within RANZCR
to finalise the development of the Radiology Referral Set (RRS) with the aim of including all radiology procedures performed in Australia. The RANZCR Radiology Referral
value set published in the NCTS
is an evolving draft that is derived from the latest agreed set of concepts from the RRS. Implementers are advised to take note that concepts within the value set will continue to expand and evolve when further iterations of the Radiology Referral Set are available.
Work is underway within RANZCR
to finalise the development of the Radiology Referral Set (RRS) with the aim of including all radiology procedures performed in Australia. The RANZCR Radiology Referral
value set published in the NCTS
is an evolving draft that is derived from the latest agreed set of concepts from the RRS. Implementers are advised to take note that concepts within the value set will continue to expand and evolve when further iterations of the Radiology Referral Set are available.
Work is underway within RANZCR
to finalise the development of the Radiology Referral Set (RRS) with the aim of including all radiology procedures performed in Australia. The RANZCR Radiology Referral
value set published in the NCTS
is an evolving draft that is derived from the latest agreed set of concepts from the RRS. Implementers are advised to take note that concepts within the value set will continue to expand and evolve when further iterations of the Radiology Referral Set are available.
It is intended that this profile will always support the latest version of the SPIA Requesting Pathology Terminology Reference Set available. At this time the latest version of the SPIA Requesting Pathology Terminology Reference Set is v4.2. Implementers are advised to take note that the current binding RCPA - SPIA Requesting Pathology Terminology Reference Set
currently supports v3.1 and will be replaced with a version that support v4.2 as soon as it is available in the National Clinical Terminology Service.
The primary intent of AUeReqDI is to design and govern a collection of coherent, reusable building blocks known as ‘data groups’. These data groups specify “what” the clinical requirements of the clinical information that should be included for eRequests. However, it does not specify “how” the data is exchanged; this is the role fulfilled by the FHIR standard. AUeReqDI is not required to be implemented as a whole single product. AUeReqDI builds upon and complements the foundational Australian Core Data for Interoperability (AUCDI)
and focuses on the specific use case of eRequesting.
In addition to the examples defined in this implementation, synthetic (realistic but not real) test data for developers and testers that conforms to HL7 Australia FHIR implementation guides is maintained in the HL7 AU FHIR Test Data
repository.
This implementation guide is under development through the AU eRequesting project as part of the Sparked AU FHIR Accelerator
. The Sparked AU FHIR Accelerator is a community comprising government, technology vendors, provider organisations, peak bodies, practitioners, and domain experts, to accelerate the creation and use of national FHIR standards in health care information exchange.
The Australian eRequesting Data for Interoperability (AUeReqDI)
is focused on an agreement of the minimum data required to support standardised eRequesting within the Australian health context, and forms a common language foundation that allows systems to exchange semantically accurate data for eRequests. AUeReqDI outputs form a set of data requirements to be considered and referred to as part of the development and definition of AU eRequesting.
See How to Register - Participant Information
for information on how to participate in the AU Core Technical Design Group and Clinical Design Group as part of Sparked, the Australian FHIR Accelerator.
Once the issue is logged, you should discuss with the team on chat.fhir.org in the australia > AU Request topic
before attempting to make changes yourself. It’s important to coordinate with the other people working on the project. When everyone has agreed on a course of action, IG changes should be submitted as a pull request for review in the AU eRequesting repository
.
National Electrical Manufacturers Association ( NEMA
). This specification may reference content from DICOM, which is copyright NEMA, and distributed by agreement between NEMA/DICOM and HL7. Implementer use of DICOM is not covered by this agreement
Australian eRequesting Data for Interoperability (AUeReqDI)
builds upon and complements the foundational Australian Core Data for Interoperability (AUCDI) and focuses on the specific use case of eRequesting. The first release of AUeReqDI is focused on electronic pathology and medical imaging requests in primary and community-based care provision.
Updates to AU eRequesting depend upon community input and we encourage our audience to submit questions and feedback to AU eRequesting specifications by clicking on the Propose a change link in the footer of every page. In addition, we encourage requesting any necessary clarifications to AUeReqDI through the AUeReqDI process
that helps inform future updates to AU eRequesting.
(
required
)
