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
.
AU Core Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-core/ and changes regularly. See the Directory of published versions ( src
)
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
)
There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed. ( src
)
AU Core Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-core/
and changes regularly. See the Directory of published versions
The codes SHOULD be taken from For example codes, see
Adverse Reaction Clinical Manifestation http://hl7.org/fhir/ValueSet/clinical-findings|4.0.1
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/adverse-reaction-clinical-manifestation-1
)
When populating MedicationRequest.medicationCodeableConcept
responders SHALL
correctly populate MedicationRequest.medicationCodeableConcept.coding
with either a code from Australian Medication
or PBS Item Codes
, or both, if a coded value is known and MAY
populate with a code from another code system.
Responders MAY
populate with only text if no coded value is known.
When populating MedicationStatement.medicationCodeableConcept
responders SHALL
correctly populate MedicationStatement.medicationCodeableConcept.coding
with either a code from Australian Medication
or PBS Item Codes
, or both, if a coded value is known and MAY
populate with a code from another code system.
Responders MAY
populate with only text if no coded value is known.
When selecting a code for Organization type, if a system is unable to provide a code from the preferred value set Healthcare Organisation Role Type
because the implementation context is not restricted to healthcare practitioner providers then it is recommended to select from the wider set available in SNOMED CT. If a suitable code from SNOMED CT is not available, a code from the code system Australian and New Zealand Standard Industrial Classification (ANZSIC), 2006 (Revision 2.0)
may be used.
When selecting a code for Organization type, if a system is unable to provide a code from the preferred value set Healthcare Organisation Role Type
because the implementation context is not restricted to healthcare practitioner providers then it is recommended to select from the wider set available in SNOMED CT. If a suitable code from SNOMED CT is not available, a code from the code system Australian and New Zealand Standard Industrial Classification (ANZSIC), 2006 (Revision 2.0)
may be used.
The individual's gender identity is populated in the extension:value.value[x]
of the Individual Gender Identity
extension and shall contain one of the codes from the Gender Identity Response
value set if any of the codes within the value set can apply.
The individual's pronouns are populated in the extension:value.value[x]
of the Individual Pronouns
extension and shall contain one of the codes from the Australian Pronouns
value set if any of the codes within the value set can apply.
Unless not suitable, these codes SHALL be taken from For codes, see
Biological Sex
( extensible
to https://healthterminologies.gov.au/fhir/ValueSet/biological-sex-1
)
Unless not suitable, these codes SHALL be taken from
Biological Sex
( extensible
to https://healthterminologies.gov.au/fhir/ValueSet/biological-sex-1
)
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.
AU Core Responders SHALL
correctly populate Medication.code.coding
with either a code from Australian Medication
or PBS Item Codes
, or both, if a coded value is known.
AU Core Requesters SHALL
accept a Medication resource without error if Medication.code.coding
is present and containing any valid value. A valid value may be text, or may be a code from Australian Medication
or PBS Item Codes
, or both, or some other code.
This implementation guide is under development through the AU Core 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.
AUCDI
aims to define requirements underlying the standardisation of the capture, structure, usage, and exchange of health data to counteract the current fragmentation of Australia’s health data systems. The AUCDI forms a basis for clinical data requirements for AU Core.
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 Medicines Terminology (AMT) is the national terminology for identification and naming of medicines in clinical systems for Australia.
The AMT is published monthly to include new items on the Australian Register of Therapeutic Goods from the TGA, as well as items listed on the Pharmaceutical Benefits Scheme.
The AMT is published as part of SNOMED CT-AU (Australian edition of SNOMED CT) and can be downloaded in a variety of formats from the National Clinical Terminology Service (NCTS)
. For more information on using SNOMED CT-AU in FHIR, see the guidance defined in AU Base SNOMED CT Australian Edition
.
The primary intent of the AUCDI
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 data entry, data use, and sharing of information supporting healthcare delivery. However, it does not specify "how" the data is exchanged; this is the role fulfilled by the FHIR standard. AUCDI is not required to be implemented as a whole single product. Parts can be
implemented as required for specific use cases.
Systems SHOULD
use the Australian Cyber Security Centre (ACSC) TLS configuration guidelines
that include recommendations for configuring protocol features and acceptable cipher suites when implementing TLS.
(
extensible
)
