Validation Results for AITransparency

Generated Tue Apr 21 21:03:00 UTC 2026, FHIR version 4.0.1 for hl7.fhir.uv.aitransparency#1.0.0-ballot (canonical = http://hl7.org/fhir/uv/aitransparency (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.2.6
Publication Code:aitransparency . PackageId = hl7.fhir.uv.aitransparency, Canonical = http://hl7.org/fhir/uv/aitransparency
Realm Check for UV:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 26 of 38 (68%) of resources have a language. Population Policy: NONE
Publication Request:
RelatedIgs(None Found)
  • Version 1.0.0-ballot has already been published
  • This is not the first publication, so first must not be true
  • Publication Request is for version v1.0.0-ballot which is already published
Supressed Messages:34 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.aitransparency1.0.0-ballotR4http://hl7.org/fhir/uv/aitransparency
... hl7.terminology.r47.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.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.security-label-ds4p1.0.0 MR4http://hl7.org/fhir/uv/security-label-ds4phttp://hl7.org/fhir/uv/security-label-ds4p/STU1
.... hl7.terminology5.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.1.0Latest Release is 7.1.0
Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir2.base.template#current
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 (details)
HTA Analysis:no Non-HL7 references found
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison:
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 0, warn = 1, info = 1, broken links = 0, pinned = 4 (when multiples).
FilenameErrorsWarningsHints
Build Errors011

n/a Show Validation Information

warningThe jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
en/general_guidance.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'In general, inputs should be captured using a Input-Prompt DocumentReference linked through the Provenance, but when specific clinical data is involved a FHIR Bundle or other resource MAY also be linked.' CONFORMANCE_STATEMENT_WORD

Suppressed Messages (Warnings, hints, broken links)

02 some examples refer to the huggingface github

03 some examples refer to the CHAI github

06 Example that uses import to binary ising ig-loader that has no way to provide a definition

07 This is a pattern profile that can't be actually applied. It is thus purely illustrative

08 These are made up codesystems for examples

09 known issue in an examples

10 inherited from FHIR core

11 Pinning versions when there are multiples

12 These have been reviewed and are okay for our use-case

13 Examples with extra elements beyond minimal slices

14 We should do this, but after public comments. Some of the codes will go into existing codeSystems in THO and thus not new codeSystems.

Errors sorted by type