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

Test Cases

This page links to a readable, narrative-first rendering of every TestScript in this package - what each one actually does, step by step - instead of raw JSON or the IG Publisher's default per-artifact table view.

Browse by resource

Resource	Test Case
AllergyIntolerance	SHALL-level conformance plus chained identifier search
Condition	SHALL-level conformance
Encounter	SHALL-level conformance
HealthcareService	SHALL-level conformance
Immunization	SHALL-level conformance plus vaccineCode slice coverage
Location	SHALL-level conformance
Medication	SHALL-level conformance
MedicationRequest	SHALL-level conformance
MedicationStatement	SHALL-level conformance
Observation — Diagnostic Result	Search & obligation-pair conformance
Observation — Pathology Result	Search & obligation-pair conformance
Observation — Smoking Status	SHALL-level conformance
Observation — Sex Assigned at Birth extension	Presence & profile conformance
Observation — Imaging Result	Optionality-discovery template
Organization	SHALL-level conformance
Patient	SHALL-level conformance
Practitioner	SHALL-level conformance
PractitionerRole	Core search & profile conformance
Procedure	SHALL-level conformance
RelatedPerson	SHALL-level conformance

See Test Targets for what these actually validate and which servers they've been run against, and Test Procedure for how a run works end to end.

How these pages are generated

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.