Unable to compare with previous version: Unable to find version history at https://fhir-ig.digital.health.nz/nzps (Problem #1 with package-list.json at https://fhir-ig.digital.health.nz/nzps: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Unable to find ImplementationGuide.definition.resource.description for the resource Communication/NZPSCommunicationExample. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warning
Unable to find ImplementationGuide.definition.resource.description for the resource Communication/NZPSCommunicationExampleTwo. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/CodeSystem-nzps-list-empty-reason-cs.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/CodeSystem/nzps-list-empty-reason-cs) does not match the URL (https://standards.digital.health.nz/ns/nzps-list-empty-reason)RESOURCE_CANONICAL_MISMATCH
URL Mismatch https://fhir-ig.digital.health.nz/nzps/CodeSystem/nzps-list-empty-reason-cs vs https://standards.digital.health.nz/ns/nzps-list-empty-reason
A definition for CodeSystem 'http://acme.org/messagetypes' could not be found, so the code cannot be validated (from http://tx.fhir.org/r4) UNKNOWN_CODESYSTEM
Communication.subject (l79/c4)
error
Unable to resolve resource with reference 'Patient/example'Reference_REF_CantResolve
Communication.recipient[0] (l28/c6)
error
Unable to resolve resource with reference 'Practitioner/example'Reference_REF_CantResolve
Communication.sender (l84/c4)
error
Unable to resolve resource with reference 'Patient/example'Reference_REF_CantResolve
A definition for CodeSystem 'http://acme.org/messagetypes' could not be found, so the code cannot be validated (from http://tx.fhir.org/r4) UNKNOWN_CODESYSTEM
Communication.subject (l45/c4)
error
Unable to resolve resource with reference 'Patient/example'Reference_REF_CantResolve
Communication.recipient[0] (l28/c6)
error
Unable to resolve resource with reference 'Practitioner/example'Reference_REF_CantResolve
Communication.sender (l50/c4)
error
Unable to resolve resource with reference 'Patient/example'Reference_REF_CantResolve
value should not start or finish with whitespace ' A record of a clinical assessment of an allergy or intolerance; a propensity, or a potential risk to an individual, to have an adverse reaction on future exposure to the specified substance, or class of substance.\n\nWhere a propensity is identified, to record information or evidence about a reaction event that is characterized by any harmful or undesirable physiological response that is specific to the individual and triggered by exposure of an individual to the identified substance or class of substance.'Type_Specific_Checks_DT_String_WS
ImplementationGuide (l1/c26601)
warning
Constraint failed: ig-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation'http://hl7.org/fhir/StructureDefinition/ImplementationGuide#ig-0
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/OperationDefinition-NZPSSummaryOperation.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/OperationDefinition/NZPSSummaryOperation) does not match the URL (https://standards.digital.health.nz/fhir/OperationDefinition/nzps-summary)RESOURCE_CANONICAL_MISMATCH
URL Mismatch https://fhir-ig.digital.health.nz/nzps/OperationDefinition/NZPSSummaryOperation vs https://standards.digital.health.nz/fhir/OperationDefinition/nzps-summary
OperationDefinition.text.div
error
Hyperlink './StructureDefinition-nzps-bundle.html' at 'div/table/tr/td/div/p/a' for 'Bundle profile' does not resolve
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ParticipationMode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPriority'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
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 riskSECURITY_STRING_CONTENT_WARNING
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
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 regexMSG_DEPENDS_ON_DEPRECATED_NOTE
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-GTIN'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-GTIN'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/ValueSet-nzps-list-empty-reason-vs.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/ValueSet/nzps-list-empty-reason-vs) does not match the URL (https://nzhts.digital.health.nz/fhir/ValueSet/nzps-list-empty-reason)RESOURCE_CANONICAL_MISMATCH
URL Mismatch https://fhir-ig.digital.health.nz/nzps/ValueSet/nzps-list-empty-reason-vs vs https://nzhts.digital.health.nz/fhir/ValueSet/nzps-list-empty-reason
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/ValueSet-nzps-vaping-current-status.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/ValueSet/nzps-vaping-current-status) does not match the URL (https://nzhts.digital.health.nz/fhir/ValueSet/vaping-status)RESOURCE_CANONICAL_MISMATCH
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
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/CodeSystem-nzps-list-empty-reason-cs.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/CodeSystem/nzps-list-empty-reason-cs) does not match the URL (https://standards.digital.health.nz/ns/nzps-list-empty-reason)
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/OperationDefinition-NZPSSummaryOperation.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/OperationDefinition/NZPSSummaryOperation) does not match the URL (https://standards.digital.health.nz/fhir/OperationDefinition/nzps-summary)
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/ValueSet-nzps-list-empty-reason-vs.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/ValueSet/nzps-list-empty-reason-vs) does not match the URL (https://nzhts.digital.health.nz/fhir/ValueSet/nzps-list-empty-reason)
Conformance resource /home/runner/work/fhir-ig-builder/fhir-ig-builder/fhir-nzps/fsh-generated/resources/ValueSet-nzps-vaping-current-status.json - the canonical URL (https://fhir-ig.digital.health.nz/nzps/ValueSet/nzps-vaping-current-status) does not match the URL (https://nzhts.digital.health.nz/fhir/ValueSet/vaping-status)
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
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ParticipationMode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPriority'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-GTIN'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-GTIN'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2.0.0, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '5.2.0', found versions: 4.0.1, 5.2.0
value should not start or finish with whitespace ' A record of a clinical assessment of an allergy or intolerance; a propensity, or a potential risk to an individual, to have an adverse reaction on future exposure to the specified substance, or class of substance.\n\nWhere a propensity is identified, to record information or evidence about a reaction event that is characterized by any harmful or undesirable physiological response that is specific to the individual and triggered by exposure of an individual to the identified substance or class of substance.'