IP Review

Unattributed Code Systems

Copyright Fragment

This fragment is not visible to the reader

This publication includes IP covered under the following statements.

Copyright (c) Department of Health, Commonwealth of Australia.
Show Usage
- PBS Item Codes : Medication/au-core-medication-conformant and MedicationStatement/au-core-medicationstatement-conformant
HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.
Show Usage
- IdentifierType AU : Frog Health Service and PractitionerRole/au-core-practitionerrole-conformant
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
Show Usage
- Unified Code for Units of Measure (UCUM) : Observation/au-core-diagnosticresult-conformant and Observation/au-core-diagnosticresult-path-conformant
This material contains content from LOINC . LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license . LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
Show Usage
- LOINC : Observation/au-core-diagnosticresult-absent , Observation/au-core-diagnosticresult-conformant , Observation/au-core-diagnosticresult-path-absent and Observation/au-core-diagnosticresult-path-conformant
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 .
Show Usage
- SNOMED Clinical Terms® (SNOMED CT®) : AllergyIntolerance/au-core-allergyintolerance-conformant , Condition/au-core-condition-conformant ... Show 18 more
This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
Show Usage
This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org
Show Usage
- Gender identity : Patient/au-core-patient-conformant

Copyright and Registered Trademark Uses

IG © 2026+ FHIR Frog. Package fhirfrog.au-core-tests#0.1.0 based on FHIR 4.0.1. Generated 2026-08-16 Links: Table of Contents | QA Report ( src )
hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
FHIR Frog AU Core Conformance Tests, published by FHIR Frog. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jgsuess/au-core-tests/ and changes regularly. See the Directory of published versions ( src )

External References

Type Reference Content

web gitlab.com contact : FHIR Frog: https://gitlab.com/fhirfrog

web github.com FHIR Frog AU Core Conformance Tests, published by FHIR Frog. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jgsuess/au-core-tests/ and changes regularly. See the Directory of published versions

web gitlab.com IG © 2026+ FHIR Frog . Package fhirfrog.au-core-tests#0.1.0 based on FHIR 4.0.1 . Generated 2026-08-16
Links: Table of Contents | QA Report

web gitlab.com The TestScripts here are generated for and executed by fhir-frog — a JUnit 5 extension and standalone CLI for authoring and running FHIR TestScripts against a real server, built on the HAPI FHIR client. Where a typical clinical IG's content is profiles and examples read by humans and validators, this IG's content is executable — every resource under input/resources/ is either a TestScript or a fixture instance it depends on, and running this package means literally sending FHIR requests to a server and checking the responses.

web github.com That's also this project's answer to a real gap: Inferno's own AU Core test kit ( au-fhir-core-inferno ) is a Ruby gem with its own bespoke packaging — it can't be resolved as a FHIR dependency by canonical URL/version the way any other IG can. Because a TestScript is itself a valid FHIR resource, this Test IG can be distributed, versioned, and depended upon exactly like any other IG.

web gitlab.com See docs/planning-strategy.md in the source repo for the full rationale behind this repo's existence and how the GitLab → GitHub → build.fhir.org pipeline is wired up.

web gitlab.com Each Test Case page is rendered directly from its TestScript resource by fhir-frog 's fhir-frog-testscript-render module - the same narrative-first content model frog-runner 's own UI uses for execution results, just applied here to the test definition rather than a run's outcome. They're generated by a CI step that builds that module from fhir-frog 's main and runs it against this repo's input/resources/ , and the resulting .md files are committed to this repository (regenerated and re-committed whenever input/resources/ or fhir-frog 's renderer changes) - see docs/planning-strategy.md for the full mechanism.

web sparked.csiro.au SPARKED 's FHIRFROG test tenant

web gitlab.com The three-way gap analysis that originally produced these TestScripts (AU Core "as specified" vs. Inferno's own AU Core test kit "as implemented" vs. fhir-frog "as executable") lives in a separate repo, fhirfrog/au-core-compiler — Inferno's test kit was a comparison point during that analysis, not a server this suite runs against.

Internal Images