Validation Results for TerminologySyndicationFeed

Generated Sat May 09 20:24:22 UTC 2026, FHIR version 4.0.1 for aehrc.syndication#0.1.0 (canonical = https://ontoserver.csiro.au/syndication (history)). See Full QA Report & IP

Quality Checks
Publisher Version:	IG Publisher Version: v2.2.7
Publication Code:	n/a . PackageId = aehrc.syndication, Canonical = https://ontoserver.csiro.au/syndication
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:	28 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment aehrc.syndication 0.1.0 R4 https://ontoserver.csiro.au/syndication hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.tools.r4 1.1.2 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/1.1.2 Internal Dependency Templates: fhir.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:	Non-HL7 Igs are exempt from terminology dependency analysis
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses) hl7.fhir.uv.extensions.r4#5.2.0: SDTypeCharacteristics (5 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Unable to compare with previous version: Unable to find version history at https://ontoserver.csiro.au/syndication (Problem #1 with package-list.json at https://ontoserver.csiro.au/syndication: The requested content does not exist.)
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary:	errors = 0, warn = 0, info = 0, broken links = 0, pinned = n/a. Show Message Ids

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

Match by message ID — covers all SECURITY_STRING_CONTENT_WARNING variants

• %SECURITY_STRING_CONTENT_WARNING% (0 uses)

Optional template fragments we don't customise.

• An HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide (1 uses)
• An 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 (1 uses)
• The HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide (1 uses)
• The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide (1 uses)

constraint really targets canonical ElementDefinition.path on actual profiles.

• %eld-20% (125 uses)

embedded HTML. They aren't.

• The markdown contains content that appears to be an embedded HTML tag starting at '<a'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<b'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<c'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<d'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<e'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<f'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<g'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<h'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<i'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<k'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<l'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<m'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<n'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<o'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<p'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<r'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<s'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<t'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<u'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<v'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<w'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)
• The markdown contains content that appears to be an embedded HTML tag starting at '<y'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (0 uses)

Errors sorted by type