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
The resource CodeSystem/ontoserver-rf2-index should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource CodeSystem/syndication-content-type should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
ImplementationGuide/aehrc.syndication: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
Resource
information
The resource ImplementationGuide/aehrc.syndication could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/syndication-category could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/syndication-entry could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/syndication-feed could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/syndication-feed-metadata could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/syndication-link could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/bundle-interpretation should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/ontoserver-rf2-index should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/syndication-content-type should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
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)
aehrc.syndication
hl7.terminology.r4
