{relative link to description of changes} (optional)
category
{category} (only for first release)
title
{title} (only for first release)
introduction
{intro} (only for first release)
ci-build
{link to ci-build location} (only for first release) -- http://build.fhir.org/ig/IHE/Profile
RelatedIgs
(None Found)
Error fetching package-list from https://fhir.north-west.england.nhs.uk: fhir.north-west.england.nhs.uk
This IG has never been published, so the version should start with '0.' or include a patch version e.g. '-ballot'
This appears to be the first publication, so first must be true
Publication Request is for '{pid} -- ihe.domain.profile' but package is north-west.england.nhs.uk
Publication Request is for v'{version to release}' but package version is v0.0.1
Proposed path for this publication does not start with the canonical URL ({path} -- https://profiles.ihe.net/Domain/Profile/1.0.0 vs https://fhir.north-west.england.nhs.uk)
Proposed path for this milestone publication should usually be canonical with either sequence or version appended
This IG is not yet published at all, so there must be "first" : true in the publication request
Unable to compare with previous version: Unable to find version history at https://fhir.north-west.england.nhs.uk (Problem #1 with package-list.json at https://fhir.north-west.england.nhs.uk: fhir.north-west.england.nhs.uk)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
The canonical URL for an Implementation Guide must point directly to the implementation guide resource, not to the Implementation Guide as a whole
warning
Unable to find ImplementationGuide.definition.resource.description for the resource Binary/837d78a0-30cd-478c-83a8-f83d16fc4443. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
Observation.extension.extension
error
The reference http://hl7.org/fhir/ValueSet/observation-triggeredbytype could not be resolved
package.tgz
error
Error converting pacakge to R4B: Error processing example/Bundle-FHIRDocumentGeneticReportBundle.json:
The html source has duplicate anchor Ids: Composition-GenomicsReport-OctaviaCHISLETT,Composition-GenomicsReport-OctaviaCHISLETT-en-GB,Composition_Composition-GenomicsReport-OctaviaCHISLETT,Patient-OctaviaCHISLETT-9449305552,Patient-OctaviaCHISLETT-9449305552-en-GB,Patient_Patient-OctaviaCHISLETT-9449305552,hcComposition-GenomicsReport-OctaviaCHISLETT,hcPatient-OctaviaCHISLETT-9449305552
1
warning
The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
2
warning
An HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide
4
warning
The HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide
ActorDefinition/OrderResultTracker: ActorDefinition: Validated against fhir.ActorDefinition
Path
Severity
Message
ActorDefinition.jurisdiction[0] (l1/c1254)
information
Reference to deprecated ValueSet http://hl7.org/fhir/5.0/ValueSet/jurisdiction|5.0.0 (from http://tx.fhir.org/r4, see log) MSG_DEPRECATED
ActorDefinition (l1/c1272)
warning
Constraint failed: cnl-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation' (defined in http://hl7.org/fhir/StructureDefinition/ActorDefinition)http://hl7.org/fhir/StructureDefinition/ActorDefinition#cnl-0
None of the codings provided are in the value set 'FHIR Document Type Codes' (http://hl7.org/fhir/ValueSet/doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'LOINC Diagnostic Report Codes' (http://hl7.org/fhir/ValueSet/report-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory#R240.1)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)Terminology_TX_NoValid_3_CC
Bundle.entry[6] (l459/c6)
error
Entry 'urn:uuid:ee9b8fcc-c233-43e1-b7fb-b58ce4cf1db8' isn't reachable by traversing links (forward or backward) from the CompositionBundle_BUNDLE_Entry_Orphan_DOCUMENT
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#721965002)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)Terminology_TX_NoValid_3_CC
A definition for CodeSystem 'https://mft.nhs.uk/Id/IGEAP' could not be found, so the code cannot be validated (from http://tx.fhir.org/r4) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'https://mft.nhs.uk/Id/IGENE' could not be found, so the code cannot be validated (from http://tx.fhir.org/r4) UNKNOWN_CODESYSTEM
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)Terminology_TX_NoValid_3_CC
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#721965002)Terminology_TX_NoValid_3_CC
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/DomainResource#dom-6
None of the codings provided are in the value set 'LOINC Diagnostic Report Codes' (http://hl7.org/fhir/ValueSet/report-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory#R240.1)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)Terminology_TX_NoValid_3_CC
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)Terminology_TX_NoValid_3_CC
Bundle.entry[6] (l445/c6)
warning
Entry 'urn:uuid:ee9b8fcc-c233-43e1-b7fb-b58ce4cf1db8' isn't reachable by traversing links (forward or backward) from the MessageHeader, so its presence should be reviewed (is it needed to process the message?)Bundle_BUNDLE_Entry_Orphan_MESSAGE
Constraint failed: cpb-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation'http://hl7.org/fhir/StructureDefinition/CapabilityStatement#cpb-0
Conformance resource /home/runner/work/LTW-Genomics/LTW-Genomics/fsh-generated/resources/CodeSystem-nhsengland-genomic-test-directory.json - the canonical URL (https://fhir.north-west.england.nhs.uk/CodeSystem/nhsengland-genomic-test-directory) does not match the URL (https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory)RESOURCE_CANONICAL_MISMATCH
URL Mismatch https://fhir.north-west.england.nhs.uk/CodeSystem/nhsengland-genomic-test-directory vs https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory
Profile https://fhir.north-west.england.nhs.uk/StructureDefinition/DiagnosticReport|0.0.1, Element matches more than one slice - deviceReference, performerFunctionValidation_VAL_Profile_MatchMultiple
ImplementationGuide/north-west.england.nhs.uk: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
ImplementationGuide.dependsOn[3] (l1/c2561)
warning
The ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent version is 4.0.0-ballot. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
Wrong Display Name 'Identifier (property) (qualifier value)' for http://loinc.org#80398-1. There are no valid display names found for language(s) 'en-GB'. Default display is 'Unique identifier for Current sample' (from http://tx.fhir.org/r4, see log) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR
The questionnaire 'https://hl7.mft.nhs.uk/Questionnaire/NW-Genomics-Test-Order' could not be resolved, so no validation can be performed against the base questionnaireQuestionnaire_QR_Q_NotFound
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: 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/workflow-supportingInfo'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/workflow-supportingInfo'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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 discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
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: 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
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: 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: 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: 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://terminology.hl7.org/ValueSet/v2-0003'. 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://terminology.hl7.org/ValueSet/v2-0003'. 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/organization-period'. 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-cadavericDonor'. 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-interpreterRequired'. 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://hl7.org/fhir/StructureDefinition/patient-birthTime'. 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-proficiency'. 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-LanguageAbilityProficiency'. 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: 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-LanguageAbilityMode'. 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: 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/designNote'. 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/designNote'. 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-ServiceDeliveryLocationRoleType'. 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: 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/specimen-specialHandling'. 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/v2-0916'. 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://terminology.hl7.org/ValueSet/v2-0371'. 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
Review the extension type for ext-codeable-reference: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/v2-0203'. 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 '4.0.0', found versions: 2.9, 4.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/v2-0487'. 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
Entry 'urn:uuid:ee9b8fcc-c233-43e1-b7fb-b58ce4cf1db8' isn't reachable by traversing links (forward or backward) from the MessageHeader, so its presence should be reviewed (is it needed to process the message?)
This element does not match any known slice defined in the profile https://fhir.north-west.england.nhs.uk/StructureDefinition/Patient|0.0.1 (this may not be a problem, but you should check that it's not intended to match a slice)
This element does not match any known slice defined in the profile https://fhir.north-west.england.nhs.uk/StructureDefinition/Patient|0.0.1 (this may not be a problem, but you should check that it's not intended to match a slice)
This element does not match any known slice defined in the profile https://fhir.north-west.england.nhs.uk/StructureDefinition/ServiceRequest|0.0.1 (this may not be a problem, but you should check that it's not intended to match a slice)
This element does not match any known slice defined in the profile https://fhir.north-west.england.nhs.uk/StructureDefinition/ServiceRequest|0.0.1 (this may not be a problem, but you should check that it's not intended to match a slice)
The ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent version is 4.0.0-ballot. This reference is getting old and the more recent version should be considered
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
Wrong Display Name 'Identifier (property) (qualifier value)' for http://loinc.org#80398-1. There are no valid display names found for language(s) 'en-GB'. Default display is 'Unique identifier for Current sample'
The questionnaire 'https://hl7.mft.nhs.uk/Questionnaire/NW-Genomics-Test-Order' could not be resolved, so no validation can be performed against the base questionnaire
Conformance resource /home/runner/work/LTW-Genomics/LTW-Genomics/fsh-generated/resources/CodeSystem-nhsengland-genomic-test-directory.json - the canonical URL (https://fhir.north-west.england.nhs.uk/CodeSystem/nhsengland-genomic-test-directory) does not match the URL (https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory)
Review the extension type for ext-codeable-reference: extensions should not have a context of Element unless it's really intended that they can be used anywhere
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
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-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: 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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/workflow-supportingInfo'. 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/event-performerFunction'. 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/event-performerFunction'. 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/event-performerFunction'. 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: 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: 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: 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: 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://terminology.hl7.org/ValueSet/v2-0003'. 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://terminology.hl7.org/ValueSet/v2-0003'. 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/organization-period'. 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-cadavericDonor'. 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-interpreterRequired'. 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-birthTime'. 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-proficiency'. 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-LanguageAbilityProficiency'. 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: 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-LanguageAbilityMode'. 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: 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/designNote'. 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/designNote'. 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-ServiceDeliveryLocationRoleType'. 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: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/specimen-specialHandling'. 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/v2-0916'. 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://terminology.hl7.org/ValueSet/v2-0371'. 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
None of the codings provided are in the value set 'FHIR Document Type Codes' (http://hl7.org/fhir/ValueSet/doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)
None of the codings provided are in the value set 'LOINC Diagnostic Report Codes' (http://hl7.org/fhir/ValueSet/report-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory#R240.1)
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#721965002)
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#721965002)
None of the codings provided are in the value set 'LOINC Diagnostic Report Codes' (http://hl7.org/fhir/ValueSet/report-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory#R240.1)
None of the codings provided are in the value set 'Document Type Value Set' (http://hl7.org/fhir/ValueSet/c80-doc-typecodes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#1054161000000101)
None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = https://fhir.hl7.org.uk/CodeSystem/UKCore-PracticeSettingCode#100)
Profile https://fhir.north-west.england.nhs.uk/StructureDefinition/DiagnosticReport|0.0.1, Element matches more than one slice - deviceReference, performerFunction
north-west.england.nhs.uk
hl7.fhir.r4.examples