Validation Results for FHIRClinicalDocumentIG

Generated Wed Jan 28 13:07:42 UTC 2026, FHIR version 4.0.1 for hl7.fhir.uv.fhir-clinical-document#1.0.1 (canonical = http://hl7.org/fhir/uv/fhir-clinical-document (history)). See Full QA Report & IP

Quality Checks

Publisher Version:

IG Publisher Version: v2.0.30

Publication Code:

fhir-clinical-document . PackageId = hl7.fhir.uv.fhir-clinical-document, Canonical = http://hl7.org/fhir/uv/fhir-clinical-document

Realm Check for UV:

Language Info:

Stated Languages: n/a. IG Resource Lang: en. 35 of 35 (100%) of resources have a language. Population Policy: ALL

Publication Request:

package-id

hl7.fhir.uv.fhir-clinical-document

version

1.0.1

path

http://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1

Pub-Mode

technical-correction

status

trial-use

Release-Label

STU 1

Sequence (Group)

STU1 (current: 'STU1', others = n/a)

desc

Technical correction release for FHIR Clinical Documents STU 1. For a detailed list of the changes for this version, see the Change Log: http://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1/change-log.html

descmd

RelatedIgs

(None Found)

Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')

Supressed Messages:

29 Suppressed Issues

Dependency Checks:

Package	Version	FHIR	Canonical	Web Base	Comment
hl7.fhir.uv.fhir-clinical-document	1.0.1	R4	http://hl7.org/fhir/uv/fhir-clinical-document
hl7.terminology.r4	7.0.1 M	R4	http://terminology.hl7.org	http://terminology.hl7.org/7.0.1
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	0.9.0 M	R4	http://hl7.org/fhir/tools	http://hl7.org/fhir/tools/0.9.0	Internal 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):

http://tx.fhir.org/r4, https://tx.fhir.org/r4 (details)

HTA Analysis:

no Non-HL7 references found

R5 Dependencies:

Draft Dependencies:

hl7.fhir.r4.core#4.0.1: GuideParameterCode (16 uses), AllergyIntoleranceType (5 uses), CompositionAttestationMode (5 uses), Practitioner (14 uses), PractitionerRole (14 uses), RelatedPerson (14 uses), Device (11 uses), Organization (18 uses), CommonLanguages (2 uses), Composition (5 uses), CompositionStatus (1 uses), FHIRDocumentTypeCodes (1 uses), Group (2 uses), Encounter (1 uses), CompositionAttestationMode (3 uses), DocumentRelationshipType (3 uses), DocumentSectionCodes (1 uses), ListMode (1 uses), ListOrderCodes (1 uses), ListEmptyReasons (1 uses), Consent (2 uses)
hl7.fhir.uv.extensions.r4#5.2.0: SDStatusDerivation (16 uses)
hl7.terminology.r4#7.0.1: DoseAndRateType (5 uses)

Modifier Extensions:

(none)

Previous Version Comparison:

Comparison with version 1.0.0

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 = 5, broken links = 0, pinned = n/a.

Filename

Errors

Warnings

Hints

Build Errors

n/a Show Validation Information

en/StructureDefinition-clinical-document-bundle.html

information

The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' A FHIR Clinical Document is a FHIR bundle of type=document where the first entry is a composition. In addition, this implementation guide requires that when communicating a FHIR Clinical Document, the sender SHALL include the direct targets of all composition references in the bundle. ' CONFORMANCE_STATEMENT_WORD

en/StructureDefinition-clinical-document-composition.html

information

The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'SHALL place attested narrative into Composition.section.text.' CONFORMANCE_STATEMENT_WORD

en/index.html

information

The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'FHIR core narrative guidance stipulates that a resource's narrative "SHALL reflect all content needed for a human to understand the essential clinical and business information for the resource". In addition, to ensure the unambiguous communication of a clinical document's attested narrative, this IG requires that:' CONFORMANCE_STATEMENT_WORD

en/mapping.html

information

The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'CDA NonXMLBody: A CDA document with a nonXMLBody MAY be represented in FHIR using a DocumentReference that points to the information contained in the CDA's nonXMLBody. If the unstructured CDA document needs to be persisted as a “whole, authenticated document” (for example a previously digitally signed unstructured CDA document), it MAY be represented in FHIR using a DocumentReference that points to the complete CDA document.' CONFORMANCE_STATEMENT_WORD

en/versioning.html

information

The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'While out of scope for this IG, good practice suggests that where revision scenarios are possible, those resources subject to revision SHOULD carry a persistent resource identifier (.identifier).' CONFORMANCE_STATEMENT_WORD

Suppressed Messages (Warnings, hints, broken links)

Conformance clauses will be added in the next full release of this specification

INFORMATION: en/StructureDefinition-clinical-document-bundle.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause (0 uses)
INFORMATION: en/StructureDefinition-clinical-document-composition.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause (0 uses)
INFORMATION: en/index.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause (0 uses)
INFORMATION: en/versioning.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause (0 uses)

The extension is defined in the base resource. Our profile inherits this

INFORMATION: StructureDefinition/clinical-document-bundle: StructureDefinition.snapshot.element[4].binding.extension[0]: The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)

These slices are additional demonstration slices and not meant to match the declared slice

INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[10]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[11]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[3]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[4]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[5]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[6]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[7]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[8]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-example1: Bundle.entry[9]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[10]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[11]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[3]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[4]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[5]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[6]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[7]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[8]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Bundle/clinical-document-bundle-revision: Bundle.entry[9]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/fhir-clinical-document/StructureDefinition/clinical-document-bundle|1.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)

intended reference to draft codesystem

Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/dose-rate-type|1.0.0 (5 uses)

intended use of unity UCUM value with annotation for tablet

UCUM Codes that contain human readable annotations like {tablet} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked (5 uses)

Errors sorted by type