Validation Results for HL7FHIRNewZealandBaseImplementationGuide

Generated Fri Jul 24 15:58:55 NZST 2026, FHIR version 4.0.1 for fhir.org.nz.ig.base#3.1.0 (canonical = http://fhir.org.nz/ig/base (history)). See Full QA Report & IP

Quality Checks

Publisher Version:

IG Publisher Version: v2.2.11

Publication Code:

n/a . PackageId = fhir.org.nz.ig.base, Canonical = http://fhir.org.nz/ig/base

Realm Check for n/a:

Language Info:

This IG has no language information

Publication Request:

package-id

fhir.org.nz.ig.base

version

3.1.0

path

http://fhir.org.nz/ig/base/3.1.0

Pub-Mode

milestone

status

release

Release-Label

Release

Sequence (Group)

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

desc

Release 3.1.0 of the NZ Base Implementation Guide

descmd

Release 3.1.0 of the NZ Base Implementation Guide

RelatedIgs

(None Found)

Publication request category found (not allowed after first publication
Publication request title found (not allowed after first publication)
Publication request introduction found (not allowed after first publication)
Publication request ci-build found (not allowed after first publication)

Supressed Messages:

70 Suppressed Issues

Dependency Checks:

Package	Version	FHIR	Canonical	Web Base	Comment
fhir.org.nz.ig.base	3.1.0	R4	http://fhir.org.nz/ig/base
hl7.terminology.r4	7.2.0 M	R4	http://terminology.hl7.org	http://terminology.hl7.org/7.2.0
hl7.fhir.uv.extensions.r4	5.3.0 M	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/5.3.0
hl7.terminology.r4	7.1.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/7.1.0	Latest Release is 7.2.0
hl7.fhir.uv.extensions.r4	5.2.0 O	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/5.2.0	Latest Release is 5.3.0
hl7.fhir.uv.extensions.r4	5.3.0 M	R4	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/5.3.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: nz.fhir.template#0.1.0 -> 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:

http://hl7.org/fhir/5.0/StructureDefinition/extension-NamingSystem.url

Draft Dependencies:

hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), Condition (8 uses), CommonLanguages (17 uses), ConditionClinicalStatusCodes (1 uses), ConditionVerificationStatus (1 uses), ConditionCategoryCodes (1 uses), Condition/DiagnosisSeverity (1 uses), Condition/Problem/DiagnosisCodes (3 uses), SNOMEDCTBodyStructures (1 uses), Group (4 uses), Encounter (4 uses), Practitioner (15 uses), PractitionerRole (11 uses), RelatedPerson (12 uses), ConditionStage (1 uses), ClinicalImpression (1 uses), DiagnosticReport (2 uses), ConditionStageType (1 uses), ManifestationAndSymptomCodes (1 uses), Coverage (2 uses), FinancialResourceStatusCodes (1 uses), Organization (24 uses), SubscriberRelationshipCodes (1 uses), CoverageCopayTypeCodes (1 uses), ExampleCoverageFinancialExceptionCodes (1 uses), Contract (1 uses), HealthcareService (2 uses), ServiceCategory (1 uses), ServiceType (1 uses), Location (7 uses), ServiceProvisionConditions (1 uses), Program (1 uses), ReferralMethod (1 uses), Endpoint (4 uses), LocationStatus (1 uses), LocationMode (1 uses), LocationType (1 uses), Medication (5 uses), Medication Status Codes (1 uses), SNOMEDCTFormCodes (1 uses), Substance (1 uses), MedicationDispense (3 uses), Procedure (2 uses), MedicationDispense Status Codes (1 uses), DetectedIssue (3 uses), MedicationDispense Status Reason Codes (1 uses), MedicationDispense Category Codes (1 uses), SNOMEDCTMedicationCodes (3 uses), EpisodeOfCare (2 uses), MedicationDispense Performer Function Codes (1 uses), Device (3 uses), MedicationRequest (5 uses), Provenance (2 uses), medicationrequest Status (1 uses), medicationRequest Status Reason Codes (1 uses), medicationRequest Intent (1 uses), medicationRequest Category Codes (1 uses), RequestPriority (1 uses), CareTeam (1 uses), ProcedurePerformerRoleCodes (1 uses), CarePlan (2 uses), ServiceRequest (2 uses), ImmunizationRecommendation (1 uses), medicationRequest Course of Therapy Codes (1 uses), ClaimResponse (1 uses), MedicationStatement (2 uses), MedicationAdministration (1 uses), Medication Status Codes (1 uses), SNOMEDCTDrugTherapyStatusCodes (1 uses), Medication usage category codes (1 uses), OrganizationType (1 uses), ContactEntityType (1 uses), interpreterRequired (2 uses), PractitionerRole (1 uses), FHIR Defined Concept Properties (2 uses), PatientRelationshipType (1 uses)

Modifier Extensions:

(none)

Previous Version Comparison:

Comparison with version 3.0.1

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

Filename

Errors

Warnings

Hints

Build Errors

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

Acknowledge deprecated

The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead' (1 uses)
The extension http://hl7.org/fhir/StructureDefinition/regex|5.3.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex' (1 uses)

Acknowledge there are missing examples

The Implementation Guide contains no examples for this data type profile (2 uses)
The Implementation Guide contains no examples for this extension (8 uses)
The Implementation Guide contains no examples for this profile (11 uses)

Acknowledge this is draft

Reference to draft CodeSystem https://standards.digital.health.nz/ns/dhb-code|1.0.0 (0 uses)

Deprecated extension - unclear where it's coming from but safe to ignore

The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (0 uses)

Large code CodeSystem

The value set expansion is too large, and only a subset has been displayed (2 uses)

NZ Relationship code trigers this - unlikely to be moved to THO as an HL7 ig

Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)

OIDs are not required for these terminology resources

The resource CodeSystem/Ethnicity 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) (1 uses)
The resource CodeSystem/acc-patient-occupation-code 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) (1 uses)
The resource CodeSystem/alias-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) (1 uses)
The resource CodeSystem/citizenship-status 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) (1 uses)
The resource CodeSystem/contact-point-purpose 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) (1 uses)
The resource CodeSystem/coverage-category 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) (1 uses)
The resource CodeSystem/coverage-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) (1 uses)
The resource CodeSystem/datum-code 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) (1 uses)
The resource CodeSystem/dhb-code 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) (1 uses)
The resource CodeSystem/domicile-code 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) (1 uses)
The resource CodeSystem/ethnicityL4 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) (1 uses)
The resource CodeSystem/funded-programme 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) (1 uses)
The resource CodeSystem/hpi-practitionerRole-status-reason 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) (1 uses)
The resource CodeSystem/information-source 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) (1 uses)
The resource CodeSystem/iwi-code 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) (1 uses)
The resource CodeSystem/maoridescentcode 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) (1 uses)
The resource CodeSystem/nz-relationship-codes 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) (1 uses)
The resource CodeSystem/nz-residency 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) (1 uses)
The resource CodeSystem/pho-status 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) (1 uses)
The resource CodeSystem/practitioner-additional-authorisation 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) (1 uses)
The resource CodeSystem/practitioner-registration-status-code 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) (1 uses)
The resource CodeSystem/scopeOfPractice 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) (1 uses)
The resource ValueSet/Ethnicityfull 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) (1 uses)
The resource ValueSet/MaoriDescentValueset 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) (1 uses)
The resource ValueSet/acc-patient-occupation 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) (1 uses)
The resource ValueSet/contact-point-purpose 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) (1 uses)
The resource ValueSet/coverage-category 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) (1 uses)
The resource ValueSet/coverage-type-code 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) (1 uses)
The resource ValueSet/datumCode 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) (1 uses)
The resource ValueSet/dhb 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) (1 uses)
The resource ValueSet/dod-information-source-code 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) (1 uses)
The resource ValueSet/domicile-code 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) (1 uses)
The resource ValueSet/ethnicity 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) (1 uses)
The resource ValueSet/funded-programme 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) (1 uses)
The resource ValueSet/hpi-practitionerrole-status-reason 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) (1 uses)
The resource ValueSet/information-source 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) (1 uses)
The resource ValueSet/iwi 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) (1 uses)
The resource ValueSet/nhi-use 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) (1 uses)
The resource ValueSet/nz-citizenship-status-code 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) (1 uses)
The resource ValueSet/nz-relationship-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) (1 uses)
The resource ValueSet/nz-residency-code 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) (1 uses)
The resource ValueSet/org-and-location-alias-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) (1 uses)
The resource ValueSet/pho 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) (1 uses)
The resource ValueSet/practitioner-additional-authorisation-code 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) (1 uses)
The resource ValueSet/practitioner-registration-status-code 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) (1 uses)
The resource ValueSet/practitioner-scope-of-practice 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) (1 uses)

Regex deprecated. Unclear where this is coming form, but safe to ignore

The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex' (0 uses)

These are externally defined ValueSets

A definition could not be found for Canonical URL 'http://nzmt.org.nz/vs' (8 uses)
A definition could not be found for Canonical URL 'https://nzhts.digital.health.nz/fhir/ValueSet/atc-code' (2 uses)
A definition could not be found for Canonical URL 'https://nzhts.digital.health.nz/fhir/ValueSet/nzmt-type' (2 uses)
The valueSet reference http://nzmt.org.nz/vs on element Medication.code could not be resolved (0 uses)
The valueSet reference http://nzmt.org.nz/vs on element MedicationDispense.medication[x] could not be resolved (0 uses)
The valueSet reference http://nzmt.org.nz/vs on element MedicationRequest.medication[x] could not be resolved (0 uses)
The valueSet reference http://nzmt.org.nz/vs on element MedicationStatement.medication[x] could not be resolved (0 uses)
The valueSet reference https://nzhts.digital.health.nz/fhir/ValueSet/atc-code on element Extension.value[x] could not be resolved (0 uses)
The valueSet reference https://nzhts.digital.health.nz/fhir/ValueSet/nzmt-type on element Extension.value[x] could not be resolved (0 uses)

These two have no naming system defined but are used in the coverage examples. TBC if we need to add these NamingSystems

No definition could be found for URL value 'https://standards.digital.health.nz/ns/csc-id' (1 uses)
No definition could be found for URL value 'https://standards.digital.health.nz/ns/huhc-id' (1 uses)

This codesystem is used to tag terminology on NZHTS for inclusion in NZ Base

A definition for CodeSystem 'https://standards.digital.health.nz/ns/nzhts-usage-tags' could not be found, so the code cannot be validated (46 uses)

This is correct

This element does not match any known slice defined in the profile http://hl7.org.nz/fhir/StructureDefinition/NzPatient|1.0.0 (this may not be a problem, but you should check that it's not intended to match a slice) (2 uses)

Use of HTML noted

The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk (1 uses)

Errors sorted by type