Validation Results for FhirFrogAUCoreTests

Generated Fri Oct 23 03:18:11 UTC 2026, FHIR version 4.0.1 for fhirfrog.au-core-tests#0.1.0 (canonical = http://fhirfrog.org/fhir/au-core-tests (history)). See Errors Only & IP

Quality Checks
Publisher Version:IG Publisher Version: v3.0.1
Publication Code:n/a . PackageId = fhirfrog.au-core-tests, Canonical = http://fhirfrog.org/fhir/au-core-tests
Realm Check for n/a:
  • n/a
Language Info:This IG has no language information
Publication Request:
  • This IG has never been published
  • No publication request found
Supressed Messages:15 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
fhirfrog.au-core-tests0.1.0R4http://fhirfrog.org/fhir/au-core-tests
fhirfrog.au-core-tests / hl7.terminology.r47.4.0 Latest Milestone Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.4.0
fhirfrog.au-core-tests / hl7.fhir.uv.extensions.r45.3.0 Latest Milestone Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
fhirfrog.au-core-tests / hl7.fhir.uv.extensions.r4 / hl7.terminology.r47.1.0 Outdated Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.uv.extensions.r4 / hl7.terminology.r4 / hl7.fhir.uv.extensions.r45.2.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core2.0.0 Latest Milestone Release. R4http://hl7.org.au/fhir/corehttp://hl7.org.au/fhir/core/2.0.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.terminology.r47.0.1 Outdated Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.terminology.r4 / hl7.fhir.uv.extensions.r45.2.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.extensions.r45.2.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.au.base6.0.0 Latest Milestone Release. R4http://hl7.org.au/fhirhttp://hl7.org.au/fhir/6.0.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.au.base / hl7.terminology.r47.0.1 Outdated Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1 (as above). Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.au.base / hl7.fhir.uv.extensions.r45.2.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.smart-app-launch2.2.0 Latest Milestone Release. R4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.2
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.smart-app-launch / hl7.fhir.uv.extensions5.1.0-snapshot1 Outdated Release. R5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.smart-app-launch / hl7.fhir.uv.extensions / hl7.terminology.r55.3.0 Outdated Release. R5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.smart-app-launch / hl7.terminology5.5.0 Outdated Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.smart-app-launch / hl7.terminology / hl7.fhir.uv.extensions.r41.0.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.ipa1.1.0 Latest Milestone Release. R4http://hl7.org/fhir/uv/ipahttp://hl7.org/fhir/uv/ipa/STU1.1
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.ipa / hl7.terminology.r46.2.0 Outdated Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 7.4.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.ipa / hl7.fhir.uv.extensions.r45.2.0 Outdated Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
fhirfrog.au-core-tests / hl7.fhir.au.core / hl7.fhir.uv.ipa / hl7.fhir.uv.smart-app-launch2.0.0 Outdated Release. R4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
fhirfrog.au-core-tests / hl7.fhir.uv.tools.r41.3.0 Latest Milestone Release. R4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.3.0Internal Dependency
Templates: fhirfrog.au-core-tests.template#0.1.0 -> fhir.base.template#current
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):https://tx.fhir.org/r4, https://tx.hl7.org.au/fhir (details)
HTA Analysis:Non-HL7 Igs are exempt from terminology dependency analysis
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Unable to compare with previous version: Unable to find version history at http://fhirfrog.org/fhir/au-core-tests (Problem #1 with package-list.json at http://fhirfrog.org/fhir/au-core-tests: 404 Not Found)
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 340, warn = 95, info = 35, broken links = 29, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors226860
/scratch/repo/fsh-generated/includes/fsh-link-references000
/scratch/repo/fsh-generated/resources/ImplementationGuide-fhirfrog.au-core-tests001
/scratch/repo/input/includes/menu000
/scratch/repo/input/pagecontent/au-core-allergyintolerance000
/scratch/repo/input/pagecontent/au-core-condition000
/scratch/repo/input/pagecontent/au-core-diagnosticresult000
/scratch/repo/input/pagecontent/au-core-diagnosticresult-path000
/scratch/repo/input/pagecontent/au-core-encounter000
/scratch/repo/input/pagecontent/au-core-healthcareservice000
/scratch/repo/input/pagecontent/au-core-immunization000
/scratch/repo/input/pagecontent/au-core-location000
/scratch/repo/input/pagecontent/au-core-medication000
/scratch/repo/input/pagecontent/au-core-medicationrequest000
/scratch/repo/input/pagecontent/au-core-medicationstatement000
/scratch/repo/input/pagecontent/au-core-organization000
/scratch/repo/input/pagecontent/au-core-patient000
/scratch/repo/input/pagecontent/au-core-practitioner000
/scratch/repo/input/pagecontent/au-core-practitionerrole000
/scratch/repo/input/pagecontent/au-core-procedure000
/scratch/repo/input/pagecontent/au-core-relatedperson000
/scratch/repo/input/pagecontent/au-core-sexassignedab000
/scratch/repo/input/pagecontent/au-core-smokingstatus000
/scratch/repo/input/pagecontent/au-imagingresult000
/scratch/repo/input/pagecontent/index000
/scratch/repo/input/pagecontent/test-cases000
/scratch/repo/input/pagecontent/test-procedure000
/scratch/repo/input/pagecontent/test-targets000
/scratch/repo/input/resources/au-core-allergyintolerance301
/scratch/repo/input/resources/au-core-allergyintolerance-conformant200
/scratch/repo/input/resources/au-core-condition301
/scratch/repo/input/resources/au-core-condition-conformant300
/scratch/repo/input/resources/au-core-diagnosticresult501
/scratch/repo/input/resources/au-core-diagnosticresult-absent410
/scratch/repo/input/resources/au-core-diagnosticresult-conformant300
/scratch/repo/input/resources/au-core-diagnosticresult-path501
/scratch/repo/input/resources/au-core-diagnosticresult-path-absent411
/scratch/repo/input/resources/au-core-diagnosticresult-path-conformant201
/scratch/repo/input/resources/au-core-encounter701
/scratch/repo/input/resources/au-core-encounter-conformant1102
/scratch/repo/input/resources/au-core-encounter-location000
/scratch/repo/input/resources/au-core-encounter-participant000
/scratch/repo/input/resources/au-core-encounter-reason-condition200
/scratch/repo/input/resources/au-core-encounter-service-provider000
/scratch/repo/input/resources/au-core-healthcareservice201
/scratch/repo/input/resources/au-core-healthcareservice-conformant000
/scratch/repo/input/resources/au-core-immunization301
/scratch/repo/input/resources/au-core-immunization-conformant401
/scratch/repo/input/resources/au-core-location301
/scratch/repo/input/resources/au-core-location-conformant200
/scratch/repo/input/resources/au-core-location-organization000
/scratch/repo/input/resources/au-core-medication201
/scratch/repo/input/resources/au-core-medication-conformant000
/scratch/repo/input/resources/au-core-medicationrequest401
/scratch/repo/input/resources/au-core-medicationrequest-conformant400
/scratch/repo/input/resources/au-core-medicationrequest-medication100
/scratch/repo/input/resources/au-core-medicationstatement401
/scratch/repo/input/resources/au-core-medicationstatement-conformant500
/scratch/repo/input/resources/au-core-medicationstatement-reason-condition200
/scratch/repo/input/resources/au-core-organization201
/scratch/repo/input/resources/au-core-organization-conformant000
/scratch/repo/input/resources/au-core-patient201
/scratch/repo/input/resources/au-core-patient-conformant103
/scratch/repo/input/resources/au-core-patient-sexassignedab120
/scratch/repo/input/resources/au-core-practitioner201
/scratch/repo/input/resources/au-core-practitioner-conformant001
/scratch/repo/input/resources/au-core-practitionerrole401
/scratch/repo/input/resources/au-core-practitionerrole-conformant410
/scratch/repo/input/resources/au-core-practitionerrole-organization000
/scratch/repo/input/resources/au-core-practitionerrole-practitioner000
/scratch/repo/input/resources/au-core-procedure301
/scratch/repo/input/resources/au-core-procedure-conformant300
/scratch/repo/input/resources/au-core-relatedperson301
/scratch/repo/input/resources/au-core-relatedperson-conformant200
/scratch/repo/input/resources/au-core-relatedperson-patient000
/scratch/repo/input/resources/au-core-sexassignedab201
/scratch/repo/input/resources/au-core-smokingstatus501
/scratch/repo/input/resources/au-core-smokingstatus-absent310
/scratch/repo/input/resources/au-core-smokingstatus-conformant310
/scratch/repo/input/resources/au-imagingresult501
/scratch/repo/input/resources/au-imagingresult-conformant514
/scratch/repo/input/resources/au-imagingresult-minimal311
/scratch/repo/temp/pages/_includes/artifacts000
/scratch/repo/template/config000
/scratch/repo/template/config/_config000

n/a Show Validation Information

warningUnable to find ImplementationGuide.definition.resource.description for the resource Organization/au-core-encounter-service-provider. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Organization/au-core-organization-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Location/au-core-encounter-location. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Location/au-core-location-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Organization/au-core-location-organization. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource HealthcareService/au-core-healthcareservice-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Organization/au-core-practitionerrole-organization. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource AllergyIntolerance/au-core-allergyintolerance-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Condition/au-core-condition-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-diagnosticresult-absent. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-diagnosticresult-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-diagnosticresult-path-absent. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-diagnosticresult-path-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Encounter/au-core-encounter-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Practitioner/au-core-encounter-participant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Condition/au-core-encounter-reason-condition. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Immunization/au-core-immunization-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Medication/au-core-medication-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource MedicationRequest/au-core-medicationrequest-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Medication/au-core-medicationrequest-medication. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource MedicationStatement/au-core-medicationstatement-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Condition/au-core-medicationstatement-reason-condition. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Patient/au-core-patient-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Patient/au-core-patient-sexassignedab. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Practitioner/au-core-practitioner-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource PractitionerRole/au-core-practitionerrole-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Practitioner/au-core-practitionerrole-practitioner. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Procedure/au-core-procedure-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource RelatedPerson/au-core-relatedperson-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Patient/au-core-relatedperson-patient. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-smokingstatus-absent. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-core-smokingstatus-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-imagingresult-conformant. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warningUnable to find ImplementationGuide.definition.resource.description for the resource Observation/au-imagingresult-minimal. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
AllergyIntolerance-au-core-allergyintolerance-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 562errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Condition-au-core-condition-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 1111errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Condition-au-core-encounter-reason-condition​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 400errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Condition-au-core-medicationstatement-reason-condition​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 420errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Encounter-au-core-encounter-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 789errorThe link 'Patient/patient-fixture' for "Sample Frog" cannot be resolved HTML_LINK_CHECK_FAILED
Encounter-au-core-encounter-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 1129errorThe link 'Practitioner/frog-participant' for "Perry Frog" cannot be resolved HTML_LINK_CHECK_FAILED
Encounter-au-core-encounter-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 1416errorThe link 'Condition/frog-reason-condition' for "Synthetic reason for encounter (Frog test data)" cannot be resolved HTML_LINK_CHECK_FAILED
Encounter-au-core-encounter-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 1656errorThe link 'Location/frog-location' for "Frog Medical Centre" cannot be resolved HTML_LINK_CHECK_FAILED
Encounter-au-core-encounter-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 1757errorThe link 'Organization/frog-service-provider' for "Frog Health Service" cannot be resolved HTML_LINK_CHECK_FAILED
Immunization-au-core-immunization-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 764errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Location-au-core-location-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 1340errorThe link 'Organization/location-organization-fixture' for "Frog Medical Group" cannot be resolved HTML_LINK_CHECK_FAILED
MedicationRequest-au-core-medicationrequest-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 229errorThe link 'Medication/medication-fixture' for "Medication/medication-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
MedicationRequest-au-core-medicationrequest-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 325errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
MedicationStatement-au-core-medicationstatement-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 354errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
MedicationStatement-au-core-medicationstatement-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 643errorThe link 'Condition/medicationstatement-reason-fixture' for "Condition/medicationstatement-reason-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-absent​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 780errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-absent​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 1060errorThe link 'Observation/diagnosticresult-fixture' for "Observation/diagnosticresult-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 787errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-path-absent​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 875errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-path-absent​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 1155errorThe link 'Observation/diagnosticresultpath-fixture' for "Observation/diagnosticresultpath-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-diagnosticresult-path-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 880errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-smokingstatus-absent​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 785errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-core-smokingstatus-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 793errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-imagingresult-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 846errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Observation-au-imagingresult-minimal​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 752errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
PractitionerRole-au-core-practitionerrole-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 928errorThe link 'Practitioner/practitionerrole-practitioner-fixture' for "Practitioner/practitionerrole-practitioner-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
PractitionerRole-au-core-practitionerrole-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 1196errorThe link 'Organization/practitionerrole-organization-fixture' for "Organization/practitionerrole-organization-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
Procedure-au-core-procedure-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/p​/a at Line 327, column 621errorThe link 'Patient/patient-fixture' for "Patient/patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
RelatedPerson-au-core-relatedperson-conformant​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/table​/tr​/td​/a at Line 327, column 748errorThe link 'Patient/relatedperson-patient-fixture' for "Patient/relatedperson-patient-fixture" cannot be resolved HTML_LINK_CHECK_FAILED
output​/TestScript-au-core-diagnosticresult-path​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</h2>" at line 322 column 7 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult-path​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 324 column 15 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult-path​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 325 column 13 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult-path​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 326 column 11 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult-path​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 327 column 9 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</h2>" at line 322 column 7 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 324 column 15 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 325 column 13 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 326 column 11 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-diagnosticresult​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 327 column 9 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-practitionerrole​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</h2>" at line 322 column 7 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-practitionerrole​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 324 column 15 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-practitionerrole​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 325 column 13 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-practitionerrole​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 326 column 11 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-practitionerrole​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 327 column 9 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-sexassignedab​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</h2>" at line 322 column 7 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-sexassignedab​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 324 column 15 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-sexassignedab​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 325 column 13 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-sexassignedab​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 326 column 11 HTML_NOT_WELL_FORMED
output​/TestScript-au-core-sexassignedab​.change​.history​.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 327 column 9 HTML_NOT_WELL_FORMED
output/au-core-allergyintolerance.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-allergyintolerance​.html (l296​/c6)errorThe heading <h1> 'AU Core AllergyIntolerance — SHALL-level conformance plus...' is at a higher level than the first heading on the page (<h2> 'AU Core AllergyIntolerance'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-allergyintolerance​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l312​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l319​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l332​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l349​/c6)errorThe page has more than one top level heading: <h2> 'SearchByClinicalStatus' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l366​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientIdentifierIHIChain' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l383​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-allergyintolerance​.html (l428​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core AllergyIntolerance'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-core-condition.html (l296/c6)errorThe heading <h1> 'AU Core Condition — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Condition'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-core-condition.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l312/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l319/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l332/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l349/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientAndCategory' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l366/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientAndClinicalStatus' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l383/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientAndCode' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l400/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-condition.html (l445/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Condition'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-diagnosticresult-path​.html (l296​/c6)errorThe heading <h1> 'AU Core Pathology Result Observation — search & obligatio...' is at a higher level than the first heading on the page (<h2> 'AU Core Pathology Result Observation'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-diagnosticresult-path​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l321​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l334​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCode' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategory' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l368​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategoryDate' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l385​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l470​/c6)errorThe page has more than one top level heading: <h2> 'MustSupportObligationPair' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l491​/c6)errorThe page has more than one top level heading: <h2> 'ObligationNoError' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l508​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult-path​.html (l521​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidationObligationPair' is at the same level as the first heading on the page (<h2> 'AU Core Pathology Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-diagnosticresult.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-diagnosticresult​.html (l296​/c6)errorThe heading <h1> 'AU Core Diagnostic Result Observation — search & obligati...' is at a higher level than the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-diagnosticresult​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l321​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l334​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCode' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategory' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l368​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategoryDate' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l385​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l438​/c6)errorThe page has more than one top level heading: <h2> 'MustSupportObligationPair' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l459​/c6)errorThe page has more than one top level heading: <h2> 'ObligationNoError' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l476​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-diagnosticresult​.html (l489​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidationObligationPair' is at the same level as the first heading on the page (<h2> 'AU Core Diagnostic Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-core-encounter.html (l296/c6)errorThe heading <h1> 'AU Core Encounter — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Encounter'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-core-encounter.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l316/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l323/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l336/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l353/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientAndDate' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l370/c6)errorThe page has more than one top level heading: <h2> 'SearchByDateMultipleAnd' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l387/c6)errorThe page has more than one top level heading: <h2> 'SearchByStatusMultipleOr' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l404/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-encounter.html (l465/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Encounter'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-healthcareservice.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-healthcareservice​.html (l296​/c6)errorThe heading <h1> 'AU Core HealthcareService — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core HealthcareService'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-healthcareservice​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l311​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l317​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l330​/c6)errorThe page has more than one top level heading: <h2> 'SearchByName' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l347​/c6)errorThe page has more than one top level heading: <h2> 'SearchByIdentifier' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l364​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l381​/c6)errorThe page has more than one top level heading: <h2> 'SearchByServiceType' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l398​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-healthcareservice​.html (l423​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core HealthcareService'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-immunization.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-immunization​.html (l296​/c6)errorThe heading <h1> 'AU Core Immunization — SHALL-level conformance plus vacci...' is at a higher level than the first heading on the page (<h2> 'AU Core Immunization'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-immunization​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l312​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l319​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l332​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l349​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientAndStatus' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l366​/c6)errorThe page has more than one top level heading: <h2> 'SearchByDate' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l383​/c6)errorThe page has more than one top level heading: <h2> 'SearchByVaccineCode' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l400​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-immunization​.html (l445​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Immunization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-core-location.html (l296/c6)errorThe heading <h1> 'AU Core Location — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Location'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-core-location.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l312/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l318/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l331/c6)errorThe page has more than one top level heading: <h2> 'SearchByAddress' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l348/c6)errorThe page has more than one top level heading: <h2> 'SearchByName' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l365/c6)errorThe page has more than one top level heading: <h2> 'SearchByAddressCity' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l382/c6)errorThe page has more than one top level heading: <h2> 'SearchByAddressState' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l399/c6)errorThe page has more than one top level heading: <h2> 'SearchByAddressPostalcode' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l416/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-location.html (l445/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Location'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-medication.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-medication​.html (l296​/c6)errorThe heading <h1> 'AU Core Medication — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Medication'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-medication​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Medication'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medication​.html (l311​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Medication'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medication​.html (l317​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Medication'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medication​.html (l330​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Medication'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medication​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Medication'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-medicationrequest.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-medicationrequest​.html (l296​/c6)errorThe heading <h1> 'AU Core MedicationRequest — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core MedicationRequest'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-medicationrequest​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l320​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l333​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l350​/c6)errorThe page has more than one top level heading: <h2> 'SearchByAuthoredOn' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l367​/c6)errorThe page has more than one top level heading: <h2> 'SearchByIntent' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l384​/c6)errorThe page has more than one top level heading: <h2> 'SearchByStatus' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l401​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l418​/c6)errorThe page has more than one top level heading: <h2> 'SearchWithIncludeMedication' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l439​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationrequest​.html (l496​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core MedicationRequest'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-medicationstatement.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-medicationstatement​.html (l296​/c6)errorThe heading <h1> 'AU Core MedicationStatement — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core MedicationStatement'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-medicationstatement​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l320​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l333​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l350​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l367​/c6)errorThe page has more than one top level heading: <h2> 'SearchByEffective' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l384​/c6)errorThe page has more than one top level heading: <h2> 'SearchByStatus' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l401​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-medicationstatement​.html (l450​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core MedicationStatement'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-organization.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-organization​.html (l296​/c6)errorThe heading <h1> 'AU Core Organization — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Organization'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-organization​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l311​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l317​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l330​/c6)errorThe page has more than one top level heading: <h2> 'SearchByIdentifier' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l347​/c6)errorThe page has more than one top level heading: <h2> 'SearchByName' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l364​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-organization​.html (l409​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Organization'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-core-patient.html (l296/c6)errorThe heading <h1> 'AU Core Patient — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Patient'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-core-patient.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l311/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l317/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l330/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l347/c6)errorThe page has more than one top level heading: <h2> 'SearchByIdentifier' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l364/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-patient.html (l449/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Patient'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-practitioner.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-practitioner​.html (l296​/c6)errorThe heading <h1> 'AU Core Practitioner — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Practitioner'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-practitioner​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l311​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l317​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l330​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l347​/c6)errorThe page has more than one top level heading: <h2> 'SearchByIdentifier' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l368​/c6)errorThe page has more than one top level heading: <h2> 'SearchByName' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l385​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitioner​.html (l410​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Practitioner'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-practitionerrole.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-practitionerrole​.html (l296​/c6)errorThe heading <h1> 'AU Core PractitionerRole — core search & profile conformance' is at a higher level than the first heading on the page (<h2> 'AU Core PractitionerRole'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-practitionerrole​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l321​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l334​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'SearchByIdentifier' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l368​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPractitioner' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l385​/c6)errorThe page has more than one top level heading: <h2> 'SearchBySpecialty' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l402​/c6)errorThe page has more than one top level heading: <h2> 'SearchByRole' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l419​/c6)errorThe page has more than one top level heading: <h2> 'SearchByOrganization' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l436​/c6)errorThe page has more than one top level heading: <h2> 'ChainedPractitionerIncludePractitioner' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l457​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-practitionerrole​.html (l498​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core PractitionerRole'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-core-procedure.html (l296/c6)errorThe heading <h1> 'AU Core Procedure — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Procedure'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-core-procedure.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l312/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l319/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l332/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l349/c6)errorThe page has more than one top level heading: <h2> 'SearchByCode' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l366/c6)errorThe page has more than one top level heading: <h2> 'SearchByDate' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l383/c6)errorThe page has more than one top level heading: <h2> 'SearchByStatus' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l400/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-procedure.html (l437/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Procedure'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-relatedperson.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-relatedperson​.html (l296​/c6)errorThe heading <h1> 'AU Core RelatedPerson — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core RelatedPerson'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-relatedperson​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l312​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l319​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l332​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatient' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l349​/c6)errorThe page has more than one top level heading: <h2> 'SearchById' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l366​/c6)errorThe page has more than one top level heading: <h2> 'SearchByName' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l383​/c6)errorThe page has more than one top level heading: <h2> 'SearchByRelationship' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l400​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-relatedperson​.html (l445​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core RelatedPerson'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-sexassignedab.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-sexassignedab​.html (l296​/c6)errorThe heading <h1> 'AU Core Sex Assigned at Birth extension — presence & prof...' is at a higher level than the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-sexassignedab​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-sexassignedab​.html (l311​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-sexassignedab​.html (l317​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-sexassignedab​.html (l330​/c6)errorThe page has more than one top level heading: <h2> 'ExtensionPresence' is at the same level as the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-sexassignedab​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Sex Assigned at Birth extension'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-core-smokingstatus.htmlwarningIllegal HTML: Illegal HTML element: section
output​/au-core-smokingstatus​.html (l296​/c6)errorThe heading <h1> 'AU Core Smoking Status — SHALL-level conformance' is at a higher level than the first heading on the page (<h2> 'AU Core Smoking Status Observation'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output​/au-core-smokingstatus​.html (l305​/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l313​/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l321​/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l334​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCode' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l351​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategory' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l368​/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategoryDate' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l385​/c6)errorThe page has more than one top level heading: <h2> 'MustSupport' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l422​/c6)errorThe page has more than one top level heading: <h2> 'MustSupportAbsent' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l435​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output​/au-core-smokingstatus​.html (l448​/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidationAbsent' is at the same level as the first heading on the page (<h2> 'AU Core Smoking Status Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.htmlwarningIllegal HTML: Illegal HTML element: section
output/au-imagingresult.html (l296/c6)errorThe heading <h1> 'AU Imaging Result Observation — optionality discovery tem...' is at a higher level than the first heading on the page (<h2> 'AU Imaging Result Observation'). The first heading on a page must be its top level heading (WCAG compliance test) HTML_HEADING_ABOVE_ROOT
output/au-imagingresult.html (l305/c6)errorThe page has more than one top level heading: <h2> 'Fixtures' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l313/c6)errorThe page has more than one top level heading: <h2> 'Variables' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l321/c6)errorThe page has more than one top level heading: <h2> 'Read' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l334/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCategory' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l351/c6)errorThe page has more than one top level heading: <h2> 'SearchByPatientCode' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l368/c6)errorThe page has more than one top level heading: <h2> 'OptionalElementsProbeGenerous' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l409/c6)errorThe page has more than one top level heading: <h2> 'OptionalElementsProbeMinimal' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l446/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidation' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/au-imagingresult.html (l459/c6)errorThe page has more than one top level heading: <h2> 'ProfileValidationMinimal' is at the same level as the first heading on the page (<h2> 'AU Imaging Result Observation'). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test) HTML_HEADING_MULTIPLE_ROOTS
output/searchform.htmlwarningThe html source is not well formed: Found "</a>" expecting "</img>" at line 34 column 177 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 79 column 10 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 80 column 9 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 109 column 8 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 111 column 12 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 112 column 20 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 113 column 16 HTML_NOT_WELL_FORMED
output/searchform.htmlwarningThe html source is not well formed: Found "</div>" expecting "</body>" at line 115 column 12 HTML_NOT_WELL_FORMED
1warningThe HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
2warningAn HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide
3warningAn HTML fragment from the set [dependency-table.xhtml, dependency-table-short.xhtml, dependency-table-nontech.xhtml] is not included anywhere in the produced implementation guide
4warningThe HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide

fsh-generated/includes/fsh-link-references.md Show Validation Information (0)

✓

fsh-generated/resources/ImplementationGuide-fhirfrog.au-core-tests.json Show Validation Information (1)

PathSeverityMessageValidating
ResourceinformationThe resource ImplementationGuide/fhirfrog.au-core-tests could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/includes/menu.xml Show Validation Information (0)

✓

input/pagecontent/au-core-allergyintolerance.md Show Validation Information (0)

✓

input/pagecontent/au-core-condition.md Show Validation Information (0)

✓

input/pagecontent/au-core-diagnosticresult.md Show Validation Information (0)

✓

input/pagecontent/au-core-diagnosticresult-path.md Show Validation Information (0)

✓

input/pagecontent/au-core-encounter.md Show Validation Information (0)

✓

input/pagecontent/au-core-healthcareservice.md Show Validation Information (0)

✓

input/pagecontent/au-core-immunization.md Show Validation Information (0)

✓

input/pagecontent/au-core-location.md Show Validation Information (0)

✓

input/pagecontent/au-core-medication.md Show Validation Information (0)

✓

input/pagecontent/au-core-medicationrequest.md Show Validation Information (0)

✓

input/pagecontent/au-core-medicationstatement.md Show Validation Information (0)

✓

input/pagecontent/au-core-organization.md Show Validation Information (0)

✓

input/pagecontent/au-core-patient.md Show Validation Information (0)

✓

input/pagecontent/au-core-practitioner.md Show Validation Information (0)

✓

input/pagecontent/au-core-practitionerrole.md Show Validation Information (0)

✓

input/pagecontent/au-core-procedure.md Show Validation Information (0)

✓

input/pagecontent/au-core-relatedperson.md Show Validation Information (0)

✓

input/pagecontent/au-core-sexassignedab.md Show Validation Information (0)

✓

input/pagecontent/au-core-smokingstatus.md Show Validation Information (0)

✓

input/pagecontent/au-imagingresult.md Show Validation Information (0)

✓

input/pagecontent/index.md Show Validation Information (0)

✓

input/pagecontent/test-cases.md Show Validation Information (0)

✓

input/pagecontent/test-procedure.md Show Validation Information (0)

✓

input/pagecontent/test-targets.md Show Validation Information (0)

✓

input/resources/au-core-allergyintolerance.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1690)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1827)errorUnable to resolve resource with reference 'au-core-allergyintolerance-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[5]​.action[1]​.assert​.validateProfileId (l1​/c5173)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-allergyintolerance' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-allergyintolerance could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-allergyintolerance-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
AllergyIntolerance.patient (l31/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AllergyIntolerance
AllergyIntolerance.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-condition.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1521)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1640)errorUnable to resolve resource with reference 'au-core-condition-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c5255)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-condition' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-condition could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-condition-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Condition.code (l47/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 32570581000036105" is not understood or supported (from server, see log) AU Core Condition
Condition.subject (l56/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Condition
Condition.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-diagnosticresult.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c2739)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c2872)errorUnable to resolve resource with reference 'au-core-diagnosticresult-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c3008)errorUnable to resolve resource with reference 'au-core-diagnosticresult-absent'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[7]​.action[1]​.assert​.validateProfileId (l1​/c7511)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
TestScript​.test[8]​.action[1]​.assert​.validateProfileId (l1​/c7897)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-diagnosticresult could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-diagnosticresult-absent.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.subject (l31/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Diagnostic Result Observation
Observation.hasMember[0] (l67/c6)errorUnable to resolve resource with reference 'Observation/diagnosticresult-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Diagnostic Result Observation
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --
Observation.text.diverrorHyperlink 'Observation/diagnosticresult-fixture' at 'div/p/a' for 'Observation/diagnosticresult-fixture' does not resolve --

input/resources/au-core-diagnosticresult-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.subject (l31/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Diagnostic Result Observation
Observation.bodySite (l46/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 6021000036108" is not understood or supported (from server, see log) AU Core Diagnostic Result Observation
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-diagnosticresult-path.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c2323)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c2465)errorUnable to resolve resource with reference 'au-core-diagnosticresult-path-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c2610)errorUnable to resolve resource with reference 'au-core-diagnosticresult-path-absent'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[7]​.action[1]​.assert​.validateProfileId (l1​/c7931)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult-path' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
TestScript​.test[8]​.action[1]​.assert​.validateProfileId (l1​/c8316)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult-path' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-diagnosticresult-path could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-diagnosticresult-path-absent.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/v2-0074#CH) Terminology_TX_NoValid_3_CCAU Core Pathology Result Observation
Observation.subject (l40/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Pathology Result Observation
Observation.hasMember[0] (l76/c6)errorUnable to resolve resource with reference 'Observation/diagnosticresultpath-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Pathology Result Observation
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --
Observation.text.diverrorHyperlink 'Observation/diagnosticresultpath-fixture' at 'div/p/a' for 'Observation/diagnosticresultpath-fixture' does not resolve --

input/resources/au-core-diagnosticresult-path-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/v2-0074#CH) Terminology_TX_NoValid_3_CCAU Core Pathology Result Observation
Observation.subject (l40/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Pathology Result Observation
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-encounter.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1709)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1828)errorUnable to resolve resource with reference 'au-core-encounter-participant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c1941)errorUnable to resolve resource with reference 'au-core-encounter-location'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[3]​.resource (l1​/c2070)errorUnable to resolve resource with reference 'au-core-encounter-service-provider'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[4]​.resource (l1​/c2199)errorUnable to resolve resource with reference 'au-core-encounter-reason-condition'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[5]​.resource (l1​/c2318)errorUnable to resolve resource with reference 'au-core-encounter-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c6061)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-encounter' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-encounter could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-encounter-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Encounter.serviceType (l15/c4)informationNone of the codings provided are in the value set 'Service Type' (https://healthterminologies.gov.au/fhir/ValueSet/service-type-1|1.0.0), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/service-type#124) Terminology_TX_NoValid_3_CCAU Core Encounter
Encounter.subject (l24/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Encounter
Encounter​.participant[0]​.individual (l41​/c8)errorUnable to resolve resource with reference 'Practitioner/frog-participant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Encounter
Encounter.reasonCode[0] (l52/c6)errorError from https://tx.fhir.org/r4: Error: Invalid ECL expression: '^ 32570581000036105|Problem/Diagnosis reference set| OR ^ 32570141000036105|Procedure foundation reference set| OR ^ 1244621000168103|Australian emergency department reference set|': (The SNOMED CT Concept 32570581000036105 is not known) (from server, see log) AU Core Encounter
Encounter.reasonCode[0] (l52/c6)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/reason-for-encounter-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Core Encounter
Encounter.reasonReference[0] (l63/c6)errorUnable to resolve resource with reference 'Condition/frog-reason-condition'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Encounter
Encounter.location[0].location (l70/c8)errorUnable to resolve resource with reference 'Location/frog-location'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Encounter
Encounter.serviceProvider (l76/c4)errorUnable to resolve resource with reference 'Organization/frog-service-provider'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Encounter
Encounter.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Sample Frog' does not resolve --
Encounter.text.diverrorHyperlink 'Practitioner/frog-participant' at 'div/table/tr/td/a' for 'Perry Frog' does not resolve --
Encounter.text.diverrorHyperlink 'Condition/frog-reason-condition' at 'div/p/a' for 'Synthetic reason for encounter (Frog test data)' does not resolve --
Encounter.text.diverrorHyperlink 'Location/frog-location' at 'div/table/tr/td/a' for 'Frog Medical Centre' does not resolve --
Encounter.text.diverrorHyperlink 'Organization/frog-service-provider' at 'div/p/a' for 'Frog Health Service' does not resolve --

input/resources/au-core-encounter-location.json Show Validation Information (1)

✓

input/resources/au-core-encounter-participant.json Show Validation Information (1)

✓

input/resources/au-core-encounter-reason-condition.json Show Validation Information (1)

PathSeverityMessageValidating
Condition.subject (l22/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		Condition
Condition.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-encounter-service-provider.json Show Validation Information (1)

✓

input/resources/au-core-healthcareservice.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1787)errorUnable to resolve resource with reference 'au-core-healthcareservice-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c4947)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-healthcareservice' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-healthcareservice could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-healthcareservice-conformant.json Show Validation Information (1)

✓

input/resources/au-core-immunization.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c2523)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c2648)errorUnable to resolve resource with reference 'au-core-immunization-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c6405)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-immunization' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-immunization could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-immunization-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Immunization.vaccineCode (l10/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 1156291000168106" is not understood or supported (from server, see log) AU Core Immunization
Immunization.vaccineCode (l10/c4)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/amt-vaccine-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Core Immunization
Immunization​.vaccineCode​.coding[1]​.code (l10​/c4)errorUnknown code '1525011000168107' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		AU Core Immunization
Immunization.patient (l24/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Immunization
Immunization.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-location.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1673)errorUnable to resolve resource with reference 'au-core-location-organization'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1790)errorUnable to resolve resource with reference 'au-core-location-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[7]​.action[1]​.assert​.validateProfileId (l1​/c5161)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-location' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-location could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-location-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Location.managingOrganization (l44/c4)errorUnable to resolve resource with reference 'Organization/location-organization-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		Location
Location.text.diverrorHyperlink 'Organization/location-organization-fixture' at 'div/table/tr/td/a' for 'Frog Medical Group' does not resolve --

input/resources/au-core-location-organization.json Show Validation Information (1)

✓

input/resources/au-core-medication.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1669)errorUnable to resolve resource with reference 'au-core-medication-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[2]​.action[1]​.assert​.validateProfileId (l1​/c2914)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medication' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-medication could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-medication-conformant.json Show Validation Information (1)

✓

input/resources/au-core-medicationrequest.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c3117)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c3245)errorUnable to resolve resource with reference 'au-core-medicationrequest-medication'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c3380)errorUnable to resolve resource with reference 'au-core-medicationrequest-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[8]​.action[1]​.assert​.validateProfileId (l1​/c8036)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationrequest' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-medicationrequest could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-medicationrequest-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
MedicationRequest​.medication​.ofType(Reference) (l6​/c4)errorUnable to resolve resource with reference 'Medication/medication-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		MedicationRequest
MedicationRequest.subject (l9/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		MedicationRequest
MedicationRequest.text.diverrorHyperlink 'Medication/medication-fixture' at 'div/p/a' for 'Medication/medication-fixture' does not resolve --
MedicationRequest.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-medicationrequest-medication.json Show Validation Information (1)

PathSeverityMessageValidating
Medication.code.coding[0].code (l4/c4)errorUnknown code '23525011000036109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		Medication

input/resources/au-core-medicationstatement.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1740)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1892)errorUnable to resolve resource with reference 'au-core-medicationstatement-reason-condition'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c2031)errorUnable to resolve resource with reference 'au-core-medicationstatement-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c5732)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationstatement' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-medicationstatement could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-medicationstatement-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
MedicationStatement​.medication​.ofType(CodeableConcept)​.coding[0]​.code (l5​/c4)errorUnknown code '6632011000036102' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		MedicationStatement
MedicationStatement.subject (l19/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		MedicationStatement
MedicationStatement​.reasonReference[0] (l42​/c6)errorUnable to resolve resource with reference 'Condition/medicationstatement-reason-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		MedicationStatement
MedicationStatement.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --
MedicationStatement.text.diverrorHyperlink 'Condition/medicationstatement-reason-fixture' at 'div/p/a' for 'Condition/medicationstatement-reason-fixture' does not resolve --

input/resources/au-core-medicationstatement-reason-condition.json Show Validation Information (1)

PathSeverityMessageValidating
Condition.subject (l22/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		Condition
Condition.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-organization.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1577)errorUnable to resolve resource with reference 'au-core-organization-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[4]​.action[1]​.assert​.validateProfileId (l1​/c4243)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-organization' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-organization could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-organization-conformant.json Show Validation Information (1)

✓

input/resources/au-core-patient.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1114)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[4]​.action[1]​.assert​.validateProfileId (l1​/c4546)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-patient' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-patient could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-patient-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Patient​.extension[1]​.extension[0]​.value​.ofType(CodeableConcept) (l18​/c12)informationReference to draft CodeSystem http://hl7.org/fhir/gender-identity|4.0.1 MSG_DRAFTPatient
Patient​.extension[1]​.extension[0]​.value​.ofType(CodeableConcept) (l18​/c12)informationReference to draft CodeSystem http://hl7.org/fhir/gender-identity|4.0.1 from active ValueSet http://terminology.hl7.org/ValueSet/gender-identity|2.0.0 MSG_DRAFT_SRC_STATUSPatient
Patient​.extension[1]​.extension[0]​.value​.ofType(CodeableConcept) (l18​/c12)informationNone of the codings provided are in the value set 'Gender Identity' (http://terminology.hl7.org/ValueSet/gender-identity|2.0.0), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/gender-identity#female) Terminology_TX_NoValid_3_CCPatient
Patient​.extension[2]​.extension[0]​.value​.ofType(CodeableConcept)​.coding[0]​.system (l38​/c75)errorNo definition could be found for URL value 'http://terminology.hl7.org/CodeSystem/pronouns'

Editor's Comment: Real, valid Australian identifier/terminology namespaces not present in this build's terminology server registry - confirmed via CSIRO's Ontoserver (tx.ontoserver.csiro.au) and HL7 Australia's/Australian Digital Health Agency's own published namespaces Type_Specific_Checks_DT_URL_Resolve		Patient

input/resources/au-core-patient-sexassignedab.json Show Validation Information (1)

PathSeverityMessageValidating
Patient​.extension[0]​.extension[1]​.value​.ofType(CodeableConcept)​.coding[0]​.code (l27​/c12)errorUnknown code '1515311000168102' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		AU Core Patient
Patient.identifier[0] (l41/c6)warningFound multiple matching profiles among 2 choices: http://hl7.org.au/fhir/StructureDefinition/au-ihi, http://hl7.org/fhir/StructureDefinition/Identifier Validation_VAL_Profile_MultipleMatchesAU Core Patient
Patient (l1/c2)warningConstraint failed: inv-pat-3: 'Recorded sex or gender type shall be a member of the AU Recorded Sex or Gender Type value set if any codes within that value set can apply (extension('http://hl7.org/fhir/StructureDefinition/individual-recordedSexOrGender').extension('type').empty() or extension('http://hl7.org/fhir/StructureDefinition/individual-recordedSexOrGender').extension('type').value.all(memberOf('http://terminology.hl7.org.au/ValueSet/rsg-type')))' (defined in http://hl7.org.au/fhir/StructureDefinition/au-patient) http://hl7.org.au/fhir/StructureDefinition/au-patient#inv-pat-3AU Core Patient

input/resources/au-core-practitioner.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1758)errorUnable to resolve resource with reference 'au-core-practitioner-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[5]​.action[1]​.assert​.validateProfileId (l1​/c4510)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitioner' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-practitioner could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-practitioner-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Practitioner​.qualification[0]​.code (l23​/c8)informationReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/v2-0360|2.7 from active ValueSet http://terminology.hl7.org/CodeSystem/v2-0360/vs|2.7 (from https://tx.fhir.org/r4) MSG_DRAFT_SRC_STATUSPractitioner

input/resources/au-core-practitionerrole.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c2460)errorUnable to resolve resource with reference 'au-core-practitionerrole-practitioner'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c2608)errorUnable to resolve resource with reference 'au-core-practitionerrole-organization'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c2741)errorUnable to resolve resource with reference 'au-core-practitionerrole-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[9]​.action[1]​.assert​.validateProfileId (l1​/c8097)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitionerrole' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-practitionerrole could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-practitionerrole-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
PractitionerRole.identifier[0] (l10/c6)warningFound multiple matching profiles among 2 choices: http://hl7.org.au/fhir/StructureDefinition/au-medicareprovidernumber, http://hl7.org/fhir/StructureDefinition/Identifier Validation_VAL_Profile_MultipleMatchesAU Core PractitionerRole
PractitionerRole.practitioner (l24/c4)errorUnable to resolve resource with reference 'Practitioner/practitionerrole-practitioner-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core PractitionerRole
PractitionerRole.organization (l27/c4)errorUnable to resolve resource with reference 'Organization/practitionerrole-organization-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core PractitionerRole
PractitionerRole.text.diverrorHyperlink 'Practitioner/practitionerrole-practitioner-fixture' at 'div/table/tr/td/a' for 'Practitioner/practitionerrole-practitioner-fixture' does not resolve --
PractitionerRole.text.diverrorHyperlink 'Organization/practitionerrole-organization-fixture' at 'div/table/tr/td/a' for 'Organization/practitionerrole-organization-fixture' does not resolve --

input/resources/au-core-practitionerrole-organization.json Show Validation Information (1)

✓

input/resources/au-core-practitionerrole-practitioner.json Show Validation Information (1)

✓

input/resources/au-core-procedure.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1629)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1748)errorUnable to resolve resource with reference 'au-core-procedure-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c4995)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-procedure' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-procedure could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-procedure-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Procedure.code (l10/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 32570141000036105" is not understood or supported (from server, see log) AU Core Procedure
Procedure.subject (l19/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Procedure
Procedure.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-relatedperson.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1755)errorUnable to resolve resource with reference 'au-core-relatedperson-patient'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1882)errorUnable to resolve resource with reference 'au-core-relatedperson-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c5402)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-relatedperson' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-relatedperson could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-relatedperson-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
RelatedPerson.patient (l9/c4)errorUnable to resolve resource with reference 'Patient/relatedperson-patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core RelatedPerson
RelatedPerson.text.diverrorHyperlink 'Patient/relatedperson-patient-fixture' at 'div/table/tr/td/a' for 'Patient/relatedperson-patient-fixture' does not resolve --

input/resources/au-core-relatedperson-patient.json Show Validation Information (1)

✓

input/resources/au-core-sexassignedab.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c2321)errorUnable to resolve resource with reference 'au-core-patient-sexassignedab'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[2]​.action[1]​.assert​.validateProfileId (l1​/c3838)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-patient' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-sexassignedab could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-smokingstatus.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c1732)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c1859)errorUnable to resolve resource with reference 'au-core-smokingstatus-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c1989)errorUnable to resolve resource with reference 'au-core-smokingstatus-absent'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c5650)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-smokingstatus' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
TestScript​.test[7]​.action[1]​.assert​.validateProfileId (l1​/c6022)errorid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-smokingstatus' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-core-smokingstatus could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-core-smokingstatus-absent.json Show Validation Information (1)

PathSeverityMessageValidating
Observation​.code​.coding[0]​.code (l21​/c4)errorUnknown code '1747861000168109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		AU Core Smoking Status
Observation.subject (l30/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Smoking Status
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-core-smokingstatus-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Observation​.code​.coding[0]​.code (l21​/c4)errorUnknown code '1747861000168109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)

Editor's Comment: Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation. (from https://tx.fhir.org/r4, see log, or see the servers logic) Unknown_Code_in_Version		AU Core Smoking Status
Observation.subject (l30/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Core Smoking Status
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-imagingresult.json Show Validation Information (1)

PathSeverityMessageValidating
TestScript​.fixture[0]​.resource (l1​/c3057)errorUnable to resolve resource with reference 'au-core-patient-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[1]​.resource (l1​/c3179)errorUnable to resolve resource with reference 'au-imagingresult-conformant'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.fixture[2]​.resource (l1​/c3306)errorUnable to resolve resource with reference 'au-imagingresult-minimal'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		TestScript
TestScript​.test[5]​.action[1]​.assert​.validateProfileId (l1​/c7123)errorid value 'http://hl7.org.au/fhir/StructureDefinition/au-imagingresult' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
TestScript​.test[6]​.action[1]​.assert​.validateProfileId (l1​/c7487)errorid value 'http://hl7.org.au/fhir/StructureDefinition/au-imagingresult' is not valid Type_Specific_Checks_DT_ID_ValidTestScript
ResourceinformationThe resource TestScript/au-imagingresult could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) --

input/resources/au-imagingresult-conformant.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#43799004) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCAU Base Diagnostic Imaging Result
Observation.code (l30/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 32570361000036108" is not understood or supported (from server, see log) AU Base Diagnostic Imaging Result
Observation.code (l30/c4)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Base Diagnostic Imaging Result
Observation.subject (l40/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Base Diagnostic Imaging Result
Observation.bodySite (l45/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 6021000036108" is not understood or supported (from server, see log) AU Base Diagnostic Imaging Result
Observation.bodySite (l45/c4)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/body-site-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Base Diagnostic Imaging Result
Observation.component[0].code (l56/c8)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 32570361000036108" is not understood or supported (from server, see log) AU Base Diagnostic Imaging Result
Observation.component[0].code (l56/c8)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Base Diagnostic Imaging Result
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

input/resources/au-imagingresult-minimal.json Show Validation Information (1)

PathSeverityMessageValidating
Observation.code (l21/c4)errorError from https://tx.fhir.org/r4: Error: The filter "concept in 32570361000036108" is not understood or supported (from server, see log) AU Base Diagnostic Imaging Result
Observation.code (l21/c4)informationCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR) (from server, see log) Terminology_TX_Confirm_3_CCAU Base Diagnostic Imaging Result
Observation.subject (l31/c4)errorUnable to resolve resource with reference 'Patient/patient-fixture'

Editor's Comment: TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation. Reference_REF_CantResolve		AU Base Diagnostic Imaging Result
Observation (l1/c2)warningBest Practice Recommendation: In general, all observations should have a performer All_observations_should_have_a_performer--
Observation.text.diverrorHyperlink 'Patient/patient-fixture' at 'div/p/a' for 'Patient/patient-fixture' does not resolve --

temp/pages/_includes/artifacts.xml Show Validation Information (0)

✓

template/config Show Validation Information (0)

✓

template/config/_config.yml Show Validation Information (0)

✓

Suppressed Messages (Warnings, hints, broken links)

Deliberately non-slice-matching test data: AU Core Smoking Status's LOINC coding slice is optional (0..1) and these fixtures intentionally use SNOMED-only coding to test that scenario; the Immunization vaccineCode's SNOMED/AMT coding is valid (confirmed via Ontoserver) but this build's terminology server cannot check AU value-set membership for AU SNOMED extension codes

Genuine SNOMED CT-AU extension codes, confirmed real via CSIRO's Ontoserver (tx.ontoserver.csiro.au), not present in the SNOMED CT International Edition this build's terminology server validates against. NOTE: these are error-level messages (Unknown_Code_in_Version) - per the note above, they remain visible in the Errors count; this entry only adds the reason as an annotation.

Real, valid Australian identifier/terminology namespaces not present in this build's terminology server registry - confirmed via CSIRO's Ontoserver (tx.ontoserver.csiro.au) and HL7 Australia's/Australian Digital Health Agency's own published namespaces

TestScript.fixture references (bare ids and ResourceType/xxx-fixture ids) are resolved at test-execution time by frog-runner reading local fixture data, not by the IG Publisher's static reference checker. NOTE: these are error-level messages - the IG Publisher's suppression mechanism only ever filters warnings/hints from the main per-resource error list, so these remain visible in the Errors count even though they are confirmed false positives; this entry only adds the reason as an annotation.

Errors sorted by type

All_observations_should_have_a_performer

input/resources/au-core-diagnosticresult-absent.jsonBest Practice Recommendation: In general, all observations should have a performer--
input/resources/au-core-diagnosticresult-path-absent.jsonBest Practice Recommendation: In general, all observations should have a performer--
input/resources/au-core-smokingstatus-absent.jsonBest Practice Recommendation: In general, all observations should have a performer--
input/resources/au-core-smokingstatus-conformant.jsonBest Practice Recommendation: In general, all observations should have a performer--
input/resources/au-imagingresult-conformant.jsonBest Practice Recommendation: In general, all observations should have a performer--
input/resources/au-imagingresult-minimal.jsonBest Practice Recommendation: In general, all observations should have a performer--

MSG_DRAFT

input/resources/au-core-patient-conformant.jsonReference to draft CodeSystem http://hl7.org/fhir/gender-identity|4.0.1Patient

MSG_DRAFT_SRC_STATUS

input/resources/au-core-patient-conformant.jsonReference to draft CodeSystem http://hl7.org/fhir/gender-identity|4.0.1 from active ValueSet http://terminology.hl7.org/ValueSet/gender-identity|2.0.0Patient
input/resources/au-core-practitioner-conformant.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/v2-0360|2.7 from active ValueSet http://terminology.hl7.org/CodeSystem/v2-0360/vs|2.7Practitioner

Reference_REF_CantResolve

input/resources/au-core-allergyintolerance.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-allergyintolerance.jsonUnable to resolve resource with reference 'au-core-allergyintolerance-conformant'TestScript
input/resources/au-core-allergyintolerance-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AllergyIntolerance
input/resources/au-core-condition.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-condition.jsonUnable to resolve resource with reference 'au-core-condition-conformant'TestScript
input/resources/au-core-condition-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Condition
input/resources/au-core-diagnosticresult.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-diagnosticresult.jsonUnable to resolve resource with reference 'au-core-diagnosticresult-conformant'TestScript
input/resources/au-core-diagnosticresult.jsonUnable to resolve resource with reference 'au-core-diagnosticresult-absent'TestScript
input/resources/au-core-diagnosticresult-absent.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Diagnostic Result Observation
input/resources/au-core-diagnosticresult-absent.jsonUnable to resolve resource with reference 'Observation/diagnosticresult-fixture'AU Core Diagnostic Result Observation
input/resources/au-core-diagnosticresult-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Diagnostic Result Observation
input/resources/au-core-diagnosticresult-path.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-diagnosticresult-path.jsonUnable to resolve resource with reference 'au-core-diagnosticresult-path-conformant'TestScript
input/resources/au-core-diagnosticresult-path.jsonUnable to resolve resource with reference 'au-core-diagnosticresult-path-absent'TestScript
input/resources/au-core-diagnosticresult-path-absent.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Pathology Result Observation
input/resources/au-core-diagnosticresult-path-absent.jsonUnable to resolve resource with reference 'Observation/diagnosticresultpath-fixture'AU Core Pathology Result Observation
input/resources/au-core-diagnosticresult-path-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Pathology Result Observation
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-encounter-participant'TestScript
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-encounter-location'TestScript
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-encounter-service-provider'TestScript
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-encounter-reason-condition'TestScript
input/resources/au-core-encounter.jsonUnable to resolve resource with reference 'au-core-encounter-conformant'TestScript
input/resources/au-core-encounter-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Encounter
input/resources/au-core-encounter-conformant.jsonUnable to resolve resource with reference 'Practitioner/frog-participant'AU Core Encounter
input/resources/au-core-encounter-conformant.jsonUnable to resolve resource with reference 'Condition/frog-reason-condition'AU Core Encounter
input/resources/au-core-encounter-conformant.jsonUnable to resolve resource with reference 'Location/frog-location'AU Core Encounter
input/resources/au-core-encounter-conformant.jsonUnable to resolve resource with reference 'Organization/frog-service-provider'AU Core Encounter
input/resources/au-core-encounter-reason-condition.jsonUnable to resolve resource with reference 'Patient/patient-fixture'Condition
input/resources/au-core-healthcareservice.jsonUnable to resolve resource with reference 'au-core-healthcareservice-conformant'TestScript
input/resources/au-core-immunization.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-immunization.jsonUnable to resolve resource with reference 'au-core-immunization-conformant'TestScript
input/resources/au-core-immunization-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Immunization
input/resources/au-core-location.jsonUnable to resolve resource with reference 'au-core-location-organization'TestScript
input/resources/au-core-location.jsonUnable to resolve resource with reference 'au-core-location-conformant'TestScript
input/resources/au-core-location-conformant.jsonUnable to resolve resource with reference 'Organization/location-organization-fixture'Location
input/resources/au-core-medication.jsonUnable to resolve resource with reference 'au-core-medication-conformant'TestScript
input/resources/au-core-medicationrequest.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-medicationrequest.jsonUnable to resolve resource with reference 'au-core-medicationrequest-medication'TestScript
input/resources/au-core-medicationrequest.jsonUnable to resolve resource with reference 'au-core-medicationrequest-conformant'TestScript
input/resources/au-core-medicationrequest-conformant.jsonUnable to resolve resource with reference 'Medication/medication-fixture'MedicationRequest
input/resources/au-core-medicationrequest-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'MedicationRequest
input/resources/au-core-medicationstatement.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-medicationstatement.jsonUnable to resolve resource with reference 'au-core-medicationstatement-reason-condition'TestScript
input/resources/au-core-medicationstatement.jsonUnable to resolve resource with reference 'au-core-medicationstatement-conformant'TestScript
input/resources/au-core-medicationstatement-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'MedicationStatement
input/resources/au-core-medicationstatement-conformant.jsonUnable to resolve resource with reference 'Condition/medicationstatement-reason-fixture'MedicationStatement
input/resources/au-core-medicationstatement-reason-condition.jsonUnable to resolve resource with reference 'Patient/patient-fixture'Condition
input/resources/au-core-organization.jsonUnable to resolve resource with reference 'au-core-organization-conformant'TestScript
input/resources/au-core-patient.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-practitioner.jsonUnable to resolve resource with reference 'au-core-practitioner-conformant'TestScript
input/resources/au-core-practitionerrole.jsonUnable to resolve resource with reference 'au-core-practitionerrole-practitioner'TestScript
input/resources/au-core-practitionerrole.jsonUnable to resolve resource with reference 'au-core-practitionerrole-organization'TestScript
input/resources/au-core-practitionerrole.jsonUnable to resolve resource with reference 'au-core-practitionerrole-conformant'TestScript
input/resources/au-core-practitionerrole-conformant.jsonUnable to resolve resource with reference 'Practitioner/practitionerrole-practitioner-fixture'AU Core PractitionerRole
input/resources/au-core-practitionerrole-conformant.jsonUnable to resolve resource with reference 'Organization/practitionerrole-organization-fixture'AU Core PractitionerRole
input/resources/au-core-procedure.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-procedure.jsonUnable to resolve resource with reference 'au-core-procedure-conformant'TestScript
input/resources/au-core-procedure-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Procedure
input/resources/au-core-relatedperson.jsonUnable to resolve resource with reference 'au-core-relatedperson-patient'TestScript
input/resources/au-core-relatedperson.jsonUnable to resolve resource with reference 'au-core-relatedperson-conformant'TestScript
input/resources/au-core-relatedperson-conformant.jsonUnable to resolve resource with reference 'Patient/relatedperson-patient-fixture'AU Core RelatedPerson
input/resources/au-core-sexassignedab.jsonUnable to resolve resource with reference 'au-core-patient-sexassignedab'TestScript
input/resources/au-core-smokingstatus.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-core-smokingstatus.jsonUnable to resolve resource with reference 'au-core-smokingstatus-conformant'TestScript
input/resources/au-core-smokingstatus.jsonUnable to resolve resource with reference 'au-core-smokingstatus-absent'TestScript
input/resources/au-core-smokingstatus-absent.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Smoking Status
input/resources/au-core-smokingstatus-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Core Smoking Status
input/resources/au-imagingresult.jsonUnable to resolve resource with reference 'au-core-patient-conformant'TestScript
input/resources/au-imagingresult.jsonUnable to resolve resource with reference 'au-imagingresult-conformant'TestScript
input/resources/au-imagingresult.jsonUnable to resolve resource with reference 'au-imagingresult-minimal'TestScript
input/resources/au-imagingresult-conformant.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Base Diagnostic Imaging Result
input/resources/au-imagingresult-minimal.jsonUnable to resolve resource with reference 'Patient/patient-fixture'AU Base Diagnostic Imaging Result

Terminology_TX_Confirm_3_CC

input/resources/au-core-encounter-conformant.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/reason-for-encounter-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Core Encounter
input/resources/au-core-immunization-conformant.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/amt-vaccine-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Core Immunization
input/resources/au-imagingresult-conformant.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Base Diagnostic Imaging Result
input/resources/au-imagingresult-conformant.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/body-site-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Base Diagnostic Imaging Result
input/resources/au-imagingresult-conformant.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Base Diagnostic Imaging Result
input/resources/au-imagingresult-minimal.jsonCould not confirm that the codings provided are in the value set https://healthterminologies.gov.au/fhir/ValueSet/imaging-procedure-1 and a coding is recommended to come from this value set (class = SERVER_ERROR)AU Base Diagnostic Imaging Result

Terminology_TX_NoValid_3_CC

input/resources/au-core-diagnosticresult-path-absent.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/v2-0074#CH)AU Core Pathology Result Observation
input/resources/au-core-diagnosticresult-path-conformant.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/v2-0074#CH)AU Core Pathology Result Observation
input/resources/au-core-encounter-conformant.jsonNone of the codings provided are in the value set 'Service Type' (https://healthterminologies.gov.au/fhir/ValueSet/service-type-1|1.0.0), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/service-type#124)AU Core Encounter
input/resources/au-core-patient-conformant.jsonNone of the codings provided are in the value set 'Gender Identity' (http://terminology.hl7.org/ValueSet/gender-identity|2.0.0), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/gender-identity#female)Patient
input/resources/au-imagingresult-conformant.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#43799004)AU Base Diagnostic Imaging Result

Type_Specific_Checks_DT_ID_Valid

input/resources/au-core-allergyintolerance.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-allergyintolerance' is not validTestScript
input/resources/au-core-condition.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-condition' is not validTestScript
input/resources/au-core-diagnosticresult.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult' is not validTestScript
input/resources/au-core-diagnosticresult.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult' is not validTestScript
input/resources/au-core-diagnosticresult-path.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult-path' is not validTestScript
input/resources/au-core-diagnosticresult-path.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult-path' is not validTestScript
input/resources/au-core-encounter.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-encounter' is not validTestScript
input/resources/au-core-healthcareservice.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-healthcareservice' is not validTestScript
input/resources/au-core-immunization.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-immunization' is not validTestScript
input/resources/au-core-location.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-location' is not validTestScript
input/resources/au-core-medication.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medication' is not validTestScript
input/resources/au-core-medicationrequest.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationrequest' is not validTestScript
input/resources/au-core-medicationstatement.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationstatement' is not validTestScript
input/resources/au-core-organization.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-organization' is not validTestScript
input/resources/au-core-patient.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-patient' is not validTestScript
input/resources/au-core-practitioner.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitioner' is not validTestScript
input/resources/au-core-practitionerrole.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitionerrole' is not validTestScript
input/resources/au-core-procedure.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-procedure' is not validTestScript
input/resources/au-core-relatedperson.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-relatedperson' is not validTestScript
input/resources/au-core-sexassignedab.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-patient' is not validTestScript
input/resources/au-core-smokingstatus.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-smokingstatus' is not validTestScript
input/resources/au-core-smokingstatus.jsonid value 'http://hl7.org.au/fhir/core/StructureDefinition/au-core-smokingstatus' is not validTestScript
input/resources/au-imagingresult.jsonid value 'http://hl7.org.au/fhir/StructureDefinition/au-imagingresult' is not validTestScript
input/resources/au-imagingresult.jsonid value 'http://hl7.org.au/fhir/StructureDefinition/au-imagingresult' is not validTestScript

Type_Specific_Checks_DT_URL_Resolve

input/resources/au-core-patient-conformant.jsonNo definition could be found for URL value 'http://terminology.hl7.org/CodeSystem/pronouns'Patient

Unknown_Code_in_Version

input/resources/au-core-immunization-conformant.jsonUnknown code '1525011000168107' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)AU Core Immunization
input/resources/au-core-medicationrequest-medication.jsonUnknown code '23525011000036109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)Medication
input/resources/au-core-medicationstatement-conformant.jsonUnknown code '6632011000036102' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)MedicationStatement
input/resources/au-core-patient-sexassignedab.jsonUnknown code '1515311000168102' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)AU Core Patient
input/resources/au-core-smokingstatus-absent.jsonUnknown code '1747861000168109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)AU Core Smoking Status
input/resources/au-core-smokingstatus-conformant.jsonUnknown code '1747861000168109' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20250201' (International Edition)AU Core Smoking Status

Validation_VAL_Profile_MultipleMatches

input/resources/au-core-patient-sexassignedab.jsonFound multiple matching profiles among 2 choices: http://hl7.org.au/fhir/StructureDefinition/au-ihi, http://hl7.org/fhir/StructureDefinition/IdentifierAU Core Patient
input/resources/au-core-practitionerrole-conformant.jsonFound multiple matching profiles among 2 choices: http://hl7.org.au/fhir/StructureDefinition/au-medicareprovidernumber, http://hl7.org/fhir/StructureDefinition/IdentifierAU Core PractitionerRole