Validation Results for FHIRTerminologyEcosystemIG

Generated Sun Nov 15 11:07:02 UTC 2026, FHIR version 5.0.0 for hl7.fhir.uv.tx-ecosystem#1.11.1-snapshot (canonical = http://hl7.org/fhir/uv/tx-ecosystem (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v3.0.4
Publication Code:tx-ecosystem . PackageId = hl7.fhir.uv.tx-ecosystem, Canonical = http://hl7.org/fhir/uv/tx-ecosystem
Realm Check for UV:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 3 of 3 (100%) of resources have a language. Population Policy: ALL
Publication Request:
RelatedIgs(None Found)
  • Publication Request is for v'1.11.0' but package version is v1.11.1-snapshot ERROR!
  • Publication Request is for version v1.11.0 which is already published ERROR!
Supressed Messages:1 Suppressed Issue
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
hl7.fhir.uv.tx-ecosystem1.11.1-snapshotR5http://hl7.org/fhir/uv/tx-ecosystem
hl7.fhir.uv.tx-ecosystem / hl7.terminology.r57.5.0 Latest Milestone Release. R5http://terminology.hl7.orghttp://terminology.hl7.org/7.5.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.extensions.r55.4.0 Latest Milestone Release. R5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.4.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.extensions.r5 / hl7.terminology.r57.5.0 Latest Milestone Release. R5http://terminology.hl7.orghttp://terminology.hl7.org/7.5.0 (as above)
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.application-feature1.0.0 Latest Milestone Release. R5http://hl7.org/fhir/uv/application-featurehttp://hl7.org/fhir/uv/application-feature/STU1
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.application-feature / hl7.terminology.r57.1.0 Outdated Release. R5http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.5.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.application-feature / hl7.terminology.r5 / hl7.fhir.uv.extensions.r55.2.0 Outdated Release. R5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.4.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.application-feature / hl7.fhir.uv.extensions5.3.0 Outdated Release. R5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0Latest Release is 5.4.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.application-feature / hl7.fhir.uv.extensions / hl7.terminology.r57.1.0 Outdated Release. R5http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.5.0
hl7.fhir.uv.tx-ecosystem / hl7.fhir.uv.tools.r51.3.0 Latest Milestone Release. R5http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.3.0Internal Dependency
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):https://tx.fhir.org/r5 (details)
HTA Analysis:no Non-HL7 references found
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 1.11.0
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 1, warn = 6, info = 15, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors1014
/scratch/repo/input/resources/FeatureDefinition-CodeSystemAsParameter020
/scratch/repo/input/resources/FeatureDefinition-TestCasesVersion020
/scratch/repo/input/tx-ecosystem-ig021

n/a Show Validation Information

errorThere is no jira specification file defined with the expected name of FHIR-tx-ecosystem in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
en/requirements.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Most requirements apply to every server. Some apply only to a server that supports a particular code system or a particular feature, and those are stated conditionally - "if a server supports X, then it SHALL …". In the test cases these conditional requirements are gated by a mode: a test gated on a mode you do not pass to the runner does not run, and does not count as either a pass or a failure. So a server declares which of these sections apply to it by which modes it asks to be tested in. See Modes.' CONFORMANCE_STATEMENT_WORD
en/requirements.htmlinformationNo conformance term found in the text: A code in a reserved code space is a valid code in the code system, whether or not anything in scope defines it. When nothing does, its display is the code space's default display, which is a placeholder: another display is not an error or a warning CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: A global extension-codes supplement (marked with codesystem-supplement-global = true) is used for the code system it supplements whether or not it is referenced, as if the code system defined its codes: its display is the code's display, and a different display is an error (a warning with lenient-display-validation) CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: An extension-codes supplement that is not global is only used when it is referenced. Its display is then the code's display, but not the only correct one: a different display is a warning CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: The codes an extension-codes supplement defines are only in an expansion when they are listed in the value set (compose.include.concept), not when it includes all of the code system CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: A code in a reserved code space that a value set lists (compose.include.concept) is a member of it: it is in the expansion, and $validate-code accepts it. A filter never selects a code in a reserved code space - not even a concept in or code in filter that lists it - since such codes have no hierarchy or properties: it is not in the expansion, $validate-code rejects it, and the filter does not make the expansion unclosed CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: the latest version of that edition the server has CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: that version CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: the edition and version the request asks for with force-system-version, system-version or check-system-version, where it asks; otherwise the server's default edition CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: A concept matches when at least one of its active descriptions in the chosen language matches the pattern CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: and the match is case-sensitive CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: Only one language is searched CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationNo conformance term found in the text: the first language the request names - the displayLanguage parameter, or if there is none, the HTTP Accept-Language header - that the edition has descriptions in; if the request names none of the edition's languages, or no language at all, the edition's default language CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'CLASS SHALL be a string property whose value is the class name (e.g. PULM), in $lookup and in property filters. A server MAY also return the Part code for the class in $lookup, as a partCode part of the property (an informal extension)' CONFORMANCE_STATEMENT_WORD

input/resources/FeatureDefinition-CodeSystemAsParameter.json Show Validation Information (1)

PathSeverityMessageValidating
FeatureDefinition (l1/c2)warningWhen HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director' VALIDATION_HL7_PUBLISHER_MISSINGFeature Definition
FeatureDefinition (l1/c2)warningThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not found VALIDATION_HL7_WG_URLFeature Definition

input/resources/FeatureDefinition-TestCasesVersion.json Show Validation Information (1)

PathSeverityMessageValidating
FeatureDefinition (l1/c2)warningWhen HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director' VALIDATION_HL7_PUBLISHER_MISSINGFeature Definition
FeatureDefinition (l1/c2)warningThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not found VALIDATION_HL7_WG_URLFeature Definition

input/tx-ecosystem-ig.xml Show Validation Information (1)

PathSeverityMessageValidating
ImplementationGuide​.jurisdiction[0] (l1​/c2112)informationReference to deprecated ValueSet http://hl7.org/fhir/ValueSet/jurisdiction|5.0.0 (from https://tx.fhir.org/r5, see log, or see the servers logic) MSG_DEPRECATEDImplementationGuide
ImplementationGuide (l1/c11074)warningThe nominated WG 'fhir-pd' means that the publisher should be 'HL7 International / FHIR Product Director' but 'HL7 FHIR Product Director' was found VALIDATION_HL7_PUBLISHER_MISMATCHImplementationGuide
ImplementationGuide (l1/c11074)warningThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not found VALIDATION_HL7_WG_URLImplementationGuide

Suppressed Messages (Warnings, hints, broken links)

Don't care about experimental

Errors sorted by type


MSG_DEPRECATED

input/tx-ecosystem-ig.xmlReference to deprecated ValueSet http://hl7.org/fhir/ValueSet/jurisdiction|5.0.0ImplementationGuide

VALIDATION_HL7_PUBLISHER_MISMATCH

input/tx-ecosystem-ig.xmlThe nominated WG 'fhir-pd' means that the publisher should be 'HL7 International / FHIR Product Director' but 'HL7 FHIR Product Director' was foundImplementationGuide

VALIDATION_HL7_PUBLISHER_MISSING

input/resources/FeatureDefinition-CodeSystemAsParameter.jsonWhen HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director'Feature Definition
input/resources/FeatureDefinition-TestCasesVersion.jsonWhen HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director'Feature Definition

VALIDATION_HL7_WG_URL

input/resources/FeatureDefinition-CodeSystemAsParameter.jsonThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundFeature Definition
input/resources/FeatureDefinition-TestCasesVersion.jsonThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundFeature Definition
input/tx-ecosystem-ig.xmlThe nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundImplementationGuide