Validation Results for InternationalPatientSummaryIG

Generated Sat Jun 13 22:59:33 UTC 2026, FHIR version 4.0.1 for hl7.fhir.uv.ips#2.0.1 (canonical = http://hl7.org/fhir/uv/ips (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.2.9
Publication Code:ips . PackageId = hl7.fhir.uv.ips, Canonical = http://hl7.org/fhir/uv/ips
Realm Check for UV:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 8 of 118 (6%) of resources have a language. Population Policy: NONE
Publication Request:
package-idhl7.fhir.uv.ips
version2.0.1
pathhttp://hl7.org/fhir/uv/ips/2.0.1
Pub-Modemilestone
statustrial-use
Release-LabelSTU 2
Sequence (Group)STU 2 (current: 'STU 2', others = 'STU 1')
descThis publication is the 2.0.1 STU errata release, which corrects the specification of the hl7.fhir.uv.extensions.r4 dependency, plus additional minor updates since the 2.0.0 release (see the change log).
descmd

This publication is the 2.0.1 STU errata release, which corrects the specification of the hl7.fhir.uv.extensions.r4 dependency, plus additional minor updates since the 2.0.0 release (see the change log).

changeschanges.html
RelatedIgs(None Found)
No Messages found - all good
Supressed Messages:166 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.ips2.0.1R4http://hl7.org/fhir/uv/ips
... hl7.terminology.r47.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
... hl7.fhir.uv.ipa1.1.0 MR4http://hl7.org/fhir/uv/ipahttp://hl7.org/fhir/uv/ipa/STU1.1
.... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 7.1.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.smart-app-launch2.0.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
.... hl7.terminology.r47.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above)
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:All OK
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 2.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 = 0, broken links = 0, pinned = 5056 (all).
FilenameErrorsWarningsHints
Build Errors000

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

01. EXAMPLES: Identifiers such as HPI facility, NHI, and professional board IDs are valid in the New Zealand context. Examples instances containing these identifiers are included as illustrative examples in the IG, even though the URIs for these identifier systems are not known to the IG publication build tooling.

02. EXAMPLES: Several example resources use European-specific identifier systems identified by OIDs. These are included for realism in examples but are not supported by the HL7 IG publication build tooling.

03. EXAMPLES: Several example resources use European-specific code systems (identified by OIDs or URLs). These are included for realism in examples but are not supported by the HL7 IG publication build tooling.

04. EXAMPLES: Examples intentionally illustrate the use of European or other local identifiers and custom extensions in Patient resource. This demonstrates flexibility for implementers, even though these URIs are not defined and known to the IG publication build tooling.

05. EXAMPLES: The IPS MedicationStatement profile directs implementers to use effectiveDateTime. Some examples use effectivePeriod to highlight some medications may not be for a specific date even though this generates profile slice messages.

06. OBLIGATIONS: The use of the obligation extension generates multiple slicing information messages in the snapshot. This extension is reused across many resources in IPS, leading to repeated validation messages that do not appear to indicate an actual problem. Other IGs that are using obligations (e.g., IPA, EPS) when rebuilt using the latest IG Publisher show similar sets of QA "element does not match any known slice" slicing information messages.

07. TERMINOLOGY: These ImagingStudy value set bindings (e.g., to RadLex and DICOM references) and element definitions are inherited from base FHIR and are not overridden in IPS. The resulting warnings are acknowledged but cannot be resolved within this IG.

08. TERMINOLOGY: R5 ActorDefinition points to a deprecated ValueSet, while the corresponding R6 ValueSet retains the required codes. This is a known transitional issue and is acceptable for IPS examples.

09. TERMINOLOGY: Some resources reference draft code systems from FHIR R4 (e.g., DiagnosticReport.status, ImagingStudy.status). These are inherited from base FHIR definitions and cannot be altered in the IPS guide.

10. TERMINOLOGY: Certain CDA OIDs are carried forward from prior IPS publications and are maintained in ART-DECOR. Their use here is consistent with historical precedent and does not require new definitions in this guide.

11. TERMINOLOGY: The IG defines these value sets with large expansions (> 1000 codes), which results in the publication build tooling generating these information messages and truncating the display of the value set expansions to 1000 codes (which does not affect the use of the value set).

12. TERMINOLOGY: The EDQM code system specifies the 'C' (Current), 'PDF', 'H+V' (Human and Veterinary), 'CMT', 'CDF', 'PFT' and 'ROA' codes as properties or property values, but those codes are not defined in the EDQM code system itself or in an external code system, and they are inconsistently and often incorrectly used in the EDQM CodeSystem resource that is loaded on tx.fhir.org. See discussion in the Zulip topic here: https://chat.fhir.org/#narrow/channel/179202-terminology/topic/EDQM.20Standard.20Terms.20as.20FHIR.20codesystem/with/370216547 (last post on 2023-07-03). Fixing this requires updating the EDQM code system resource as it is currently represented and loaded on tx.fhir.org, which is outside the direct scope of the IPS FHIR IG.

13. TERMINOLOGY: The International Standard Classification of Occupations (ISCO) vISCO-08 code system is loaded on tx.fhir.org as a CodeSystem resource with 'content' = 'fragment', so this information message is expected.

14. LOGICAL MODEL: As this is a logical model, the reference to 'ISO-27269_International_Patient_Summary' is not intended to be a valid uri, and no definition for it is provided or should be expected.

15. CANONICAL VERSIONS: The pin-canonical IG parameter 'pin-all' value is used, so these information messages are expected.

16. The language code 'fr-LU' code for French (Luxembourg) is a valid ISO 639-1 language code, but since it is not included in the 'Common Languages' (http://hl7.org/fhir/ValueSet/languages) value set. The new tx.fhir.org (FHIRsmith) terminology server is also not correctly handling non-English language parameter values. The display names specified are valid for SNOMED CT, regardless of whether an English or non-English language code is specified for the resource. See Zulip topic: https://chat.fhir.org/#narrow/channel/179202-terminology/topic/tx.2Efhir.2Eorg.20.24validate-code.20incorrect.20with.20non-English.20lang/with/602221523

17. These codes that are used in these example instances were chosen from a different code system or value set than the one specified in the preferred binding, so these information messages are expected.

18. The deprecated maxValueSet and regex extensions are introduced in the snapshot by the IG Publisher, and are not referenced in the IG profiles.

19. These NDC codes are apparently still active - see https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=7cba82f0-9886-46e9-8dbd-43a448aade29, https://ndclist.com/ndc/0781-1852/package/0781-1852-20.

20. It is not required to make the update to mark the conformance clause text as part of this errata release publication. This issue is intended to be addressed in a future ballot and updated release of the specification.

21. This is a known issue (previously reported by John Moehrke) that the attachment url doesn't always have to be a refrence type in a bundle (see FMG 2026/06/10 minutes - https://confluence.hl7.org/spaces/FMG/pages/453928617/2026-06-10+FMG+Agenda+Minutes).

Errors sorted by type