Validation Results for AUPatientSummaryImplementationGuide

Generated Mon Aug 04 12:48:55 UTC 2025, FHIR version 4.0.1 for hl7.fhir.au.ps#0.3.0-ballot (canonical = http://hl7.org.au/fhir/ps (history)). See Errors Only & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.0.12
Publication Code:n/a . PackageId = hl7.fhir.au.ps, Canonical = http://hl7.org.au/fhir/ps
Realm Check for n/a:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: n/a. 2 of 25 (8%) of resources have a language. Population Policy: NONE
Publication Request:
package-idhl7.fhir.au.ps
version0.3.0-ballot
pathhttp://hl7.org.au/fhir/ps/0.3.0-ballot
Pub-Modeworking release
statusballot
Release-LabelBallot
Sequence (Group)R1 (current: n/a, others = 'R1')
descThis snapshot is published for the August 2025 ballot and September 2025 Connectathon.
RelatedIgs(None Found)
  • The file package-list.json should not exist in the root folder
  • This release is labelled as a working release in the sequence 'R1'. This is an unexpected workflow - check that the sequence really is correct.
  • Dependency on hl7.fhir.uv.ips is to the current version - not allowed
Supressed Messages:159 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.au.ps0.3.0-ballotR4http://hl7.org.au/fhir/ps
... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0
... hl7.fhir.uv.ipscurrent VR4http://hl7.org/fhir/uv/ipshttps://build.fhir.org/ig/HL7/fhir-ips/Cannot be published with a dependency on a current build version
.... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above)
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... hl7.fhir.au.core2.0.0-ballot IR4http://hl7.org.au/fhir/corehttp://hl7.org.au/fhir/core/2.0.0-ballot
.... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above)
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
.... hl7.fhir.au.base6.0.0-ballot IR4http://hl7.org.au/fhirhttp://hl7.org.au/fhir/6.0.0-ballot
..... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above)
..... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
.... hl7.fhir.uv.smart-app-launch2.2.0 MR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.2
..... hl7.fhir.uv.extensions5.1.0-snapshot1 OR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.2.0
...... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 6.5.0
..... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 6.5.0
...... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.2.0
.... hl7.fhir.uv.ipa1.1.0 MR4http://hl7.org/fhir/uv/ipahttp://hl7.org/fhir/uv/ipa/STU1.1
..... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
..... hl7.fhir.uv.smart-app-launch2.0.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
Templates: hl7.au.sparked.template#0.6.0 -> hl7.au.fhir.template#0.11.0 -> hl7.au.base.template#0.10.0 -> fhir.base.template#0.8.1. Tools: 0.7.1
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4, https://tx.fhir.org/r4, https://tx.ontoserver.csiro.au/fhir (details)
HTA Analysis:no Non-HL7 references found
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 0.2.0-preview
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 5, warn = 0, info = 0, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/examples/Bundle-aups-basicsummary000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/examples/Bundle-aups-gpvisit-retrieval000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/examples/Bundle-aups-referral-endoconsult-autogen000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/examples/Bundle-aups-referral-endoconsult-curated000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/examples/Bundle-aups-section-emptyreason000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/ig000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-actor-consumer000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-actor-producer000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-allergyintolerance000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-bundle100
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-composition000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-condition000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-diagnosticresult-path100
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-encounter000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-immunization000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-medication000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-medicationrequest100
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-medicationstatement100
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-organization000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-patient000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-practitioner000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-practitionerrole000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-procedure000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-relatedperson000
/__w/au-fhir-ps/au-fhir-ps/hl7au/au-fhir-ps/input/resources/au-ps-smokingstatus100

n/a Show Validation Information


input/examples/Bundle-aups-basicsummary.xml Show Validation Information (31)


input/examples/Bundle-aups-gpvisit-retrieval.xml Show Validation Information (317)


input/examples/Bundle-aups-referral-endoconsult-autogen.json Show Validation Information (240)


input/examples/Bundle-aups-referral-endoconsult-curated.xml Show Validation Information (119)


input/examples/Bundle-aups-section-emptyreason.xml Show Validation Information (11)


input/ig.xml Show Validation Information (1)


input/resources/au-ps-actor-consumer.xml Show Validation Information (1)


input/resources/au-ps-actor-producer.xml Show Validation Information (1)


input/resources/au-ps-allergyintolerance.xml Show Validation Information (1)


input/resources/au-ps-bundle.xml Show Validation Information (1)

PathSeverityMessage
StructureDefinitionerrorThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Bundle-uv-ips'

Editor's Comment: ERROR: Bundle.entry slicing discriminator mismatch. IPS slices Bundle.entry using both type:resource and profile:resource discriminators. AU PS uses only type:resource to enforce stricter control over allowed entry types. This causes a mismatch with IPS, but is intentional to ensure AU PS-specific profiles are used. === Show Reasoning SD_EXTENSION_COMPLIES_WITH_ERROR

input/resources/au-ps-composition.xml Show Validation Information (1)


input/resources/au-ps-condition.xml Show Validation Information (1)


input/resources/au-ps-diagnosticresult-path.xml Show Validation Information (1)

PathSeverityMessage
StructureDefinitionerrorThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Observation-results-laboratory-pathology-uv-ips'

Editor's Comment: ERROR: AU PS profile asserts compliance with IPS but there are some structural differences that cause the tooling validation error: a) Observation.category slicing discriminator mismatch. IPS slices using pattern:$this while AU PS inherits slices by code/system from AU Core. b) For Observation.value[x], IPS labels data types string, Quantity and CodeableConcept as MS. AU PS is stronger by placing the rule on the element i.e. every data type has obligations on it not just the three IPS. These differences trigger validation errors but the profiles are functionally compatible. === Show Reasoning SD_EXTENSION_COMPLIES_WITH_ERROR

input/resources/au-ps-encounter.xml Show Validation Information (1)


input/resources/au-ps-immunization.xml Show Validation Information (1)


input/resources/au-ps-medication.xml Show Validation Information (1)


input/resources/au-ps-medicationrequest.xml Show Validation Information (1)

PathSeverityMessage
StructureDefinitionerrorThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/MedicationRequest-uv-ips'

Editor's Comment: ERROR: doNotPerform mismatch in AU PS MedicationRequest. IPS now sets doNotPerform = false (pre-applied block vote 12 tracker FHIR-51483), but AU PS hasn’t applied this change yet. This is a known difference and will be resolved in a future update.=== Show Reasoning SD_EXTENSION_COMPLIES_WITH_ERROR

input/resources/au-ps-medicationstatement.xml Show Validation Information (1)

PathSeverityMessage
MedicationStatement.reasonReferenceerrorError at http://hl7.org.au/fhir/ps/StructureDefinition/au-ps-medicationstatement#MedicationStatement.reasonReference: The target profile http://hl7.org/fhir/uv/ips/StructureDefinition/DiagnosticReport-uv-ips is not a valid constraint on the base ([CanonicalType[http://hl7.org.au/fhir/core/StructureDefinition/au-core-condition], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org.au/fhir/StructureDefinition/au-diagnosticreport]])

Editor's Comment: === ERROR: Target profile in MedicationStatement.reasonReference is flagged due to IPS profile not being derived from AU Core base profile. This is a known cross-profile compatibility limitation when constraining to both AU Core and IPS derived targets. ===

input/resources/au-ps-organization.xml Show Validation Information (1)


input/resources/au-ps-patient.xml Show Validation Information (1)


input/resources/au-ps-practitioner.xml Show Validation Information (1)


input/resources/au-ps-practitionerrole.xml Show Validation Information (1)


input/resources/au-ps-procedure.xml Show Validation Information (1)


input/resources/au-ps-relatedperson.xml Show Validation Information (1)


input/resources/au-ps-smokingstatus.xml Show Validation Information (1)

PathSeverityMessage
StructureDefinitionerrorThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Observation-tobaccouse-uv-ips'

Editor's Comment: ==== ERROR: This warning occurs because AU PS Smoking Status inherits SNOMED patternCodeableConcept from AU Core where IPS requires a LOINC pattern on Observation.code. AU PS profiles support both SNOMED and LOINC codings to satisfy both AU Core and IPS requirements.==== Show Reasoning SD_EXTENSION_COMPLIES_WITH_ERROR

Suppressed Messages (Warnings, hints, broken links)

=== # Warning about IPS profile compliance. This occurs because the IPS profile is imposed via structuredefinition-compliesWithProfile, which is not fully understood or enforced by the validator. The warning is expected and safe to ignore, manual validation confirms the profile is aligned with the imposed IPS profile. ===

=== ERROR: Target profile in MedicationStatement.reasonReference is flagged due to IPS profile not being derived from AU Core base profile. This is a known cross-profile compatibility limitation when constraining to both AU Core and IPS derived targets. ===

=== Examples are not included for these profiles and extensions ===

=== HL7 core known warnings ===

=== INFORMATION: Generated due to inherited slicing in the base profile. The AU Core profile remains valid without redeclaring the slicing discriminator. ===

=== INFORMATION: Information about the AU Core use of the discriminator type 'pattern,' which is fully valid and supported in FHIR R4 but deprecated in R5+. This does not affect the functionality or conformance in R4. Future updates will consider transitioning to the recommended 'type=value' approach to ensure compatibility with R5+. ===

=== INFORMATION: These informational messages are triggered due to the tooling setup in the IG Publisher, which infers the default language (en-AU) from the jurisdiction. The terminology server (tx.ontoserver) used for validation does not support en-AU for SNOMED CT lookups and instead expects en. This is a known limitation of the tooling and terminology server setup. See related Zulip chat: https://chat.fhir.org/#narrow/channel/437028-Terminology-Service-Test-Cases/topic/DisplayLanguage.20with.20Accept.20Header.20like.20Syntax ===

=== INFORMATION: This is HL7 Terminology managed content. IG Publisher generated a message when it detects artefacts with a status of 'draft' or 'deprecated'. This is known, accepted behaviour for IG Publisher. ===

=== Information related to digital signatures on example Bundles. ===

=== References to experimental SPIA ValueSets from RCPA. These ValueSets are pending change to active status in NCTS. Se related NCTS Jira: TOOL-61 ===

=== WARNING: Artefacts inherit multiple profiles for certain data types (e.g., Address, Identifier) from AU Base. The IG Publisher cannot match example instances to a single profile and generates these warnings. This behaviour is expected and consistent with the design of AU Core and AU Base. These warnings were accepted in AU Core v1.0.0. ===

=== WARNING: Examples that represent missing data using the Data Absent Reason extension as per AU Core rules. The IG Publisher triggers a warning because of this, but the example is intentionally designed to show the correct handling of missing data and does not indicate any issues with the IG. This warning by accepted in AU Core 1.0.0. ===

=== WARNING: The following warnings flag aspects of FHIR implementation of best practice. These warnings do not indicate an error in the specification, and ignore profiled requirements. These warnings were accepted in AU Core v1.0.0.==

=== WARNING: These ValueSets are pending change to active status in NCTS. Se related NCTS Jira: TOOL-61 ===

=== WARNING: These warnings are expected due to canonical URLs having no definition. These warnings were accepted by FHIR WG. ===

=== WARNING: These warnings are related to canonical version pinning and is expected for HL7 AU IGs. Accepted by AU Core TDG and FHIR WG, see FHIR WG meeting minutes July 2025. ===

=== Warnings related to digital signatures on example Bundles. Signature Verification is a work in progress. Feedback welcome at https://chat.fhir.org/#narrow/channel/179247-Security-and-Privacy/topic/Signature/with/524324965.=== #

==== ERROR: This warning occurs because AU PS Smoking Status inherits SNOMED patternCodeableConcept from AU Core where IPS requires a LOINC pattern on Observation.code. AU PS profiles support both SNOMED and LOINC codings to satisfy both AU Core and IPS requirements.====

==== These messages have been acknowledged for this release. After reviewing the implications for conformant systems and downstream publications, we will consider adopting the recommended replacement in a future release. ===

ERROR: AU PS profile asserts compliance with IPS but there are some structural differences that cause the tooling validation error: a) Observation.category slicing discriminator mismatch. IPS slices using pattern:$this while AU PS inherits slices by code/system from AU Core. b) For Observation.value[x], IPS labels data types string, Quantity and CodeableConcept as MS. AU PS is stronger by placing the rule on the element i.e. every data type has obligations on it not just the three IPS. These differences trigger validation errors but the profiles are functionally compatible. ===

ERROR: Bundle.entry slicing discriminator mismatch. IPS slices Bundle.entry using both type:resource and profile:resource discriminators. AU PS uses only type:resource to enforce stricter control over allowed entry types. This causes a mismatch with IPS, but is intentional to ensure AU PS-specific profiles are used. ===

ERROR: doNotPerform mismatch in AU PS MedicationRequest. IPS now sets doNotPerform = false (pre-applied block vote 12 tracker FHIR-51483), but AU PS hasn’t applied this change yet. This is a known difference and will be resolved in a future update.===

Errors sorted by type


SD_EXTENSION_COMPLIES_WITH_ERROR

input/resources/au-ps-bundle.xmlThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Bundle-uv-ips'
input/resources/au-ps-diagnosticresult-path.xmlThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Observation-results-laboratory-pathology-uv-ips'
input/resources/au-ps-medicationrequest.xmlThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/MedicationRequest-uv-ips'
input/resources/au-ps-smokingstatus.xmlThis profile does not comply with claimed profile 'http://hl7.org/fhir/uv/ips/StructureDefinition/Observation-tobaccouse-uv-ips'