From 077a4435cb3cb8dd7f786cb92241fe21432a6c91 Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Thu, 9 Jul 2026 16:31:10 +0100 Subject: [PATCH 01/13] Remove empty slicing & R5 Extensions Remove empty slicing & R5 Extensions --- .github/workflows/firely-validation.yml | 10 ++--- .github/workflows/terminology.yml | 2 +- ...ngland-DiagnosticReport-GenomicReport.json | 18 --------- .../NHSEngland-Patient-Genomics.json | 3 -- .../NHSEngland-ServiceRequest-Genomics.json | 3 -- .../NHSEngland-Specimen-Genomics.json | 13 ------- package.json | 10 ++--- private.package.yaml | 39 +++++++++++++++++++ 8 files changed, 48 insertions(+), 50 deletions(-) create mode 100644 private.package.yaml diff --git a/.github/workflows/firely-validation.yml b/.github/workflows/firely-validation.yml index bb8cbd9..3e8518e 100644 --- a/.github/workflows/firely-validation.yml +++ b/.github/workflows/firely-validation.yml @@ -5,11 +5,11 @@ name: Firely Validation # Controls when the action will run. on: # Triggers the workflow on push or pull request events but only for the master branch - push: - branches: - - '**' - pull_request: - branches: [ master, main ] + #push: + #branches: + # - '**' + #pull_request: + #branches: [ master, main ] # Allows you to run this workflow manually from the Actions tab workflow_dispatch: diff --git a/.github/workflows/terminology.yml b/.github/workflows/terminology.yml index 5174c15..a6f2ed8 100644 --- a/.github/workflows/terminology.yml +++ b/.github/workflows/terminology.yml @@ -5,7 +5,7 @@ on: # Triggers the workflow on push or pull request events but only for the master branch # Allows you to run this workflow manually from the Actions tab - #push: + push: # Allows you to run this workflow manually from the Actions tab diff --git a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json index be3df23..8d9a8e7 100644 --- a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json +++ b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json @@ -61,21 +61,6 @@ "path": "DiagnosticReport.extension.value[x].type", "fixedCode": "citation" }, - { - "id": "DiagnosticReport.extension:diagnosticReportCompositionR5", - "path": "DiagnosticReport.extension", - "sliceName": "diagnosticReportCompositionR5", - "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: DiagnosticReport Profile). A reference to the Composition which wraps this report for data sharing.", - "type": [ - { - "code": "Extension", - "profile": [ - "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition" - ] - } - ], - "isModifier": false - }, { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", @@ -191,9 +176,6 @@ { "id": "DiagnosticReport.category", "path": "DiagnosticReport.category", - "slicing": { - "rules": "open" - }, "definition": "Potentially multiple categories to specify the specialty the report is relevant for. Different codings are expected by the Genomic Report and EU Lab profiles." }, { diff --git a/StructureDefinition/NHSEngland-Patient-Genomics.json b/StructureDefinition/NHSEngland-Patient-Genomics.json index 5bee313..53a7a56 100644 --- a/StructureDefinition/NHSEngland-Patient-Genomics.json +++ b/StructureDefinition/NHSEngland-Patient-Genomics.json @@ -107,9 +107,6 @@ { "id": "Patient.identifier", "path": "Patient.identifier", - "slicing": { - "rules": "open" - }, "definition": "SHALL be present for Patients within the Genomic Order Management ecosystem. It is preferred that all patients with an NHS number have this included within the Patient resource upon submission of a test order. Patient who do not have an NHS number SHOULD have a temporary one registered/assigned with PDS.\r\nFor patient records where the NHS number has been traced from PDS, the trace status SHOULD be provided within the NHS Number identifier slice.\r\n\r\nAdditional identifiers SHOULD include an appropriate naming system scheme which clearly identifies the assigner (to disambiguate the identifier from other resources where these are not nationally unique). Alternatively, the OID for local identifier MAY be used, with the 'assigner' organization explicitly referenced.", "min": 1 }, diff --git a/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json b/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json index 30c3dfe..bcdd207 100644 --- a/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json +++ b/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json @@ -222,9 +222,6 @@ { "id": "ServiceRequest.category", "path": "ServiceRequest.category", - "slicing": { - "rules": "open" - }, "definition": "Category SHALL be populated with the reason for the request being ordered e.g. Diagnostic, Carrier, Predictive, Stored DNA etc. The final list of applicable codes which can be selected is still under review, the Genomic-ReasonforTesting ValueSet SHOULD be used for this categorisation.", "min": 1 }, diff --git a/StructureDefinition/NHSEngland-Specimen-Genomics.json b/StructureDefinition/NHSEngland-Specimen-Genomics.json index 9aadddf..54dfe10 100644 --- a/StructureDefinition/NHSEngland-Specimen-Genomics.json +++ b/StructureDefinition/NHSEngland-Specimen-Genomics.json @@ -302,19 +302,6 @@ "definition": "The UK Core STU3 version of Specimen backports the R5 changes to the container BackboneElement to support capturing of storage location for a sample (through `container.location`) and recursive capture of device identifiers (e.g. tube, well, rack, freezer through `container.device`).\r\nThe container.identifier should match the identifier associated with the barcode for the tube/collection device. This can be searched using the container-id SearchParameter.\r\n\r\nAdditional examples/guidance will be provided within this IG once use of the fields has been appropriately tested.\r\n\r\nSample tracking information SHOULD be added to Tasks acting on Specimen resources, e.g. Tasks marked SamplePreparation or SampleProcessing, on either the output or input elements. This information MAY include consignment number, destination, date sent etc.\r\n\r\nIf known, the container type SHOULD be populated, using the example bound ValueSet, in SNOMED CT. If an appropraite code cannot be found, the specimen container type should be populated using free text, in Specimen.container.type.text. Additional container elements, such as capacity or specimenQuantity MAY be populated if known.", "max": "1" }, - { - "id": "Specimen.container.extension:specimenContainerLocationR5", - "path": "Specimen.container.extension", - "sliceName": "specimenContainerLocationR5", - "type": [ - { - "code": "Extension", - "profile": [ - "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" - ] - } - ] - }, { "id": "Specimen.condition", "path": "Specimen.condition", diff --git a/package.json b/package.json index 6510d2f..b83f8ec 100644 --- a/package.json +++ b/package.json @@ -3,19 +3,15 @@ "description": "FHIR Genomics Implementation Guide", "author": "nhsdigital", "dependencies": { - "hl7.fhir.r4.core": "4.0.1", - "hl7.fhir.uv.extensions.r4": "5.3.0-ballot-tc1", - "hl7.fhir.uv.xver-r5.r4": "0.1.0", +"hl7.fhir.r4.core": "4.0.1", "hl7.fhir.uv.genomics-reporting": "3.0.0", - "hl7.fhir.uv.ips": "2.0.0", "hl7.fhir.eu.laboratory": "2.0.0", "ihe.iti.pcf": "1.1.0", - "hl7.fhir.us.mcode": "4.0.0", "fhir.r4.nhsengland.pars": "0.1.2-alpha", - "fhir.r4.nhsengland.pathology": "0.1.4-alpha", "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.nhsengland.nhse-identifiers": "0.1.1-alpha", - "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release" + "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release", + "fhir.r4.nhsengland.pathology": "0.2.4-alpha" }, "fhirVersions": [ "4.0.1" diff --git a/private.package.yaml b/private.package.yaml new file mode 100644 index 0000000..789b101 --- /dev/null +++ b/private.package.yaml @@ -0,0 +1,39 @@ +implementationguides: + hl7-fhir-uv-extensions-r4: + name: hl7.fhir.uv.extensions.r4 + version: 5.3.0-ballot-tc1 + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-xver-r5-r4: + name: hl7.fhir.uv.xver-r5.r4 + version: 0.1.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-ips: + name: hl7.fhir.uv.ips + version: 2.0.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false + fhir-r4-nhsengland-pathology: + name: fhir.r4.nhsengland.pathology + version: 0.1.4-alpha + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-tools-r4: + name: hl7.fhir.uv.tools.r4 + version: 1.1.2 + installMode: STORE_AND_INSTALL + fhir-r4-nhsengland-nhse-identifiers: + name: fhir.r4.nhsengland.nhse-identifiers + version: 0.1.1-alpha + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7.fhir.us.core: + name: hl7.fhir.us.core + version: 6.1.0 + installMode: STORE_AND_INSTALL + hl7.fhir.us.mcode: + name: hl7.fhir.us.mcode + version: 4.0.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false \ No newline at end of file From a97d977f2a78c6530c81917281e91cb8d1e67e0d Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Thu, 9 Jul 2026 16:35:28 +0100 Subject: [PATCH 02/13] Pathology-nhse-as-private move Pathology-nhse-as-private package --- package.json | 3 +-- private.package.yaml | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/package.json b/package.json index b83f8ec..37dd20c 100644 --- a/package.json +++ b/package.json @@ -10,8 +10,7 @@ "fhir.r4.nhsengland.pars": "0.1.2-alpha", "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.nhsengland.nhse-identifiers": "0.1.1-alpha", - "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release", - "fhir.r4.nhsengland.pathology": "0.2.4-alpha" + "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release" }, "fhirVersions": [ "4.0.1" diff --git a/private.package.yaml b/private.package.yaml index 789b101..1ec8db8 100644 --- a/private.package.yaml +++ b/private.package.yaml @@ -16,7 +16,7 @@ implementationguides: fetchDependencies: false fhir-r4-nhsengland-pathology: name: fhir.r4.nhsengland.pathology - version: 0.1.4-alpha + version: 0.2.4-alpha installMode: STORE_AND_INSTALL fetchDependencies: false hl7-fhir-uv-tools-r4: From 2918efec105c47cb32aaf418fea9321facf78bba Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Thu, 9 Jul 2026 16:44:36 +0100 Subject: [PATCH 03/13] Empty Slicing issues Empty Slicing issues --- .../CodeSystem-Genomics-DGTS-testpackage-modality.json | 2 +- .../NHSEngland-Composition-GenomicsEULabReport.json | 6 ------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json b/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json index 75b16ca..30b67f4 100644 --- a/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json +++ b/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json @@ -26,7 +26,7 @@ "copyright": "Copyright © 2026+ NHS England Licensed under the Apache License, Version 2.0 (the \\\"License\\\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \\\"AS IS\\\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "caseSensitive": true, "content": "complete", - "count": 7, + "count": 9, "concept": [ { "code": "solid-cancer", diff --git a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json index c31e397..ca4fa03 100644 --- a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json +++ b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json @@ -174,9 +174,6 @@ { "id": "Composition.category", "path": "Composition.category", - "slicing": { - "rules": "open" - }, "definition": "Fixed codes for conformance to the EU Lab Composition profile (for cross border sharing of lab reports)." }, { @@ -268,9 +265,6 @@ { "id": "Composition.section", "path": "Composition.section", - "slicing": { - "rules": "open" - }, "definition": "To conform to EU Lab, SHOULD include references to the results that form part of the genomic report. For the UGR, will include sections that conform to the UGR folders, this work is currently in development." }, { From 95628a325266e07c28fdbc2b2d4796842c27ec6e Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Thu, 9 Jul 2026 18:17:04 +0100 Subject: [PATCH 04/13] Delete-CodeSystem-test-type-genomics Delete-CodeSystem-test-type-genomics --- ...em-Genomics-DGTS-testpackage-modality.json | 2 +- .../CodeSystem-Genomics-test-types.json | 37 ------------------- ...gland-Composition-GenomicsEULabReport.json | 6 --- ...ngland-DiagnosticReport-GenomicReport.json | 18 --------- .../NHSEngland-Patient-Genomics.json | 3 -- .../NHSEngland-ServiceRequest-Genomics.json | 3 -- .../NHSEngland-Specimen-Genomics.json | 13 ------- ValueSet/ValueSet-Genomics-test-types.json | 32 ---------------- 8 files changed, 1 insertion(+), 113 deletions(-) delete mode 100644 CodeSystem/CodeSystem-Genomics-test-types.json delete mode 100644 ValueSet/ValueSet-Genomics-test-types.json diff --git a/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json b/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json index 75b16ca..30b67f4 100644 --- a/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json +++ b/CodeSystem/CodeSystem-Genomics-DGTS-testpackage-modality.json @@ -26,7 +26,7 @@ "copyright": "Copyright © 2026+ NHS England Licensed under the Apache License, Version 2.0 (the \\\"License\\\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \\\"AS IS\\\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "caseSensitive": true, "content": "complete", - "count": 7, + "count": 9, "concept": [ { "code": "solid-cancer", diff --git a/CodeSystem/CodeSystem-Genomics-test-types.json b/CodeSystem/CodeSystem-Genomics-test-types.json deleted file mode 100644 index af1a974..0000000 --- a/CodeSystem/CodeSystem-Genomics-test-types.json +++ /dev/null @@ -1,37 +0,0 @@ -{ - "resourceType": "CodeSystem", - "id": "test-type-genomics", - "url": "https://fhir.nhs.uk/CodeSystem/test-type-genomics", - "version": "0.2.0", - "name": "TestTypeGenomics", - "title": "Test Type Genomics", - "status": "draft", - "date": "2022-12-21T11:27:52.3231281+00:00", - "publisher": "NHS England", - "contact": [ - { - "name": "NHS England", - "telecom": [ - { - "system": "email", - "value": "interoperabilityteam@nhs.net", - "use": "work" - } - ] - } - ], - "description": "A set of codes use to identify the category of genomic test types", - "copyright": "Copyright © 2023+ NHS England Licensed under the Apache License, Version 2.0 (the \\\"License\\\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \\\"AS IS\\\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", - "caseSensitive": true, - "content": "complete", - "concept": [ - { - "code": "RID-WGS", - "display": "Rare and Inherited Diseases - WGS" - }, - { - "code": "C-WGS", - "display": "Cancer (paired tumour normal) - WGS" - } - ] -} \ No newline at end of file diff --git a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json index c31e397..ca4fa03 100644 --- a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json +++ b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json @@ -174,9 +174,6 @@ { "id": "Composition.category", "path": "Composition.category", - "slicing": { - "rules": "open" - }, "definition": "Fixed codes for conformance to the EU Lab Composition profile (for cross border sharing of lab reports)." }, { @@ -268,9 +265,6 @@ { "id": "Composition.section", "path": "Composition.section", - "slicing": { - "rules": "open" - }, "definition": "To conform to EU Lab, SHOULD include references to the results that form part of the genomic report. For the UGR, will include sections that conform to the UGR folders, this work is currently in development." }, { diff --git a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json index be3df23..8d9a8e7 100644 --- a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json +++ b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json @@ -61,21 +61,6 @@ "path": "DiagnosticReport.extension.value[x].type", "fixedCode": "citation" }, - { - "id": "DiagnosticReport.extension:diagnosticReportCompositionR5", - "path": "DiagnosticReport.extension", - "sliceName": "diagnosticReportCompositionR5", - "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: DiagnosticReport Profile). A reference to the Composition which wraps this report for data sharing.", - "type": [ - { - "code": "Extension", - "profile": [ - "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition" - ] - } - ], - "isModifier": false - }, { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", @@ -191,9 +176,6 @@ { "id": "DiagnosticReport.category", "path": "DiagnosticReport.category", - "slicing": { - "rules": "open" - }, "definition": "Potentially multiple categories to specify the specialty the report is relevant for. Different codings are expected by the Genomic Report and EU Lab profiles." }, { diff --git a/StructureDefinition/NHSEngland-Patient-Genomics.json b/StructureDefinition/NHSEngland-Patient-Genomics.json index 5bee313..53a7a56 100644 --- a/StructureDefinition/NHSEngland-Patient-Genomics.json +++ b/StructureDefinition/NHSEngland-Patient-Genomics.json @@ -107,9 +107,6 @@ { "id": "Patient.identifier", "path": "Patient.identifier", - "slicing": { - "rules": "open" - }, "definition": "SHALL be present for Patients within the Genomic Order Management ecosystem. It is preferred that all patients with an NHS number have this included within the Patient resource upon submission of a test order. Patient who do not have an NHS number SHOULD have a temporary one registered/assigned with PDS.\r\nFor patient records where the NHS number has been traced from PDS, the trace status SHOULD be provided within the NHS Number identifier slice.\r\n\r\nAdditional identifiers SHOULD include an appropriate naming system scheme which clearly identifies the assigner (to disambiguate the identifier from other resources where these are not nationally unique). Alternatively, the OID for local identifier MAY be used, with the 'assigner' organization explicitly referenced.", "min": 1 }, diff --git a/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json b/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json index 30c3dfe..bcdd207 100644 --- a/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json +++ b/StructureDefinition/NHSEngland-ServiceRequest-Genomics.json @@ -222,9 +222,6 @@ { "id": "ServiceRequest.category", "path": "ServiceRequest.category", - "slicing": { - "rules": "open" - }, "definition": "Category SHALL be populated with the reason for the request being ordered e.g. Diagnostic, Carrier, Predictive, Stored DNA etc. The final list of applicable codes which can be selected is still under review, the Genomic-ReasonforTesting ValueSet SHOULD be used for this categorisation.", "min": 1 }, diff --git a/StructureDefinition/NHSEngland-Specimen-Genomics.json b/StructureDefinition/NHSEngland-Specimen-Genomics.json index 9aadddf..54dfe10 100644 --- a/StructureDefinition/NHSEngland-Specimen-Genomics.json +++ b/StructureDefinition/NHSEngland-Specimen-Genomics.json @@ -302,19 +302,6 @@ "definition": "The UK Core STU3 version of Specimen backports the R5 changes to the container BackboneElement to support capturing of storage location for a sample (through `container.location`) and recursive capture of device identifiers (e.g. tube, well, rack, freezer through `container.device`).\r\nThe container.identifier should match the identifier associated with the barcode for the tube/collection device. This can be searched using the container-id SearchParameter.\r\n\r\nAdditional examples/guidance will be provided within this IG once use of the fields has been appropriately tested.\r\n\r\nSample tracking information SHOULD be added to Tasks acting on Specimen resources, e.g. Tasks marked SamplePreparation or SampleProcessing, on either the output or input elements. This information MAY include consignment number, destination, date sent etc.\r\n\r\nIf known, the container type SHOULD be populated, using the example bound ValueSet, in SNOMED CT. If an appropraite code cannot be found, the specimen container type should be populated using free text, in Specimen.container.type.text. Additional container elements, such as capacity or specimenQuantity MAY be populated if known.", "max": "1" }, - { - "id": "Specimen.container.extension:specimenContainerLocationR5", - "path": "Specimen.container.extension", - "sliceName": "specimenContainerLocationR5", - "type": [ - { - "code": "Extension", - "profile": [ - "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" - ] - } - ] - }, { "id": "Specimen.condition", "path": "Specimen.condition", diff --git a/ValueSet/ValueSet-Genomics-test-types.json b/ValueSet/ValueSet-Genomics-test-types.json deleted file mode 100644 index b885e6d..0000000 --- a/ValueSet/ValueSet-Genomics-test-types.json +++ /dev/null @@ -1,32 +0,0 @@ -{ - "resourceType": "ValueSet", - "id": "genomics-test-types", - "url": "https://fhir.nhs.uk/ValueSet/genomics-test-types", - "version": "0.1.1", - "name": "GenomicsTestTypes", - "title": "Genomics Test Types", - "status": "draft", - "date": "2024-09-10T10:17:52.3231281+00:00", - "publisher": "NHS England", - "contact": [ - { - "name": "NHS England", - "telecom": [ - { - "system": "email", - "value": "interoperabilityteam@nhs.net" - } - ] - } - ], - "description": "A ValueSet to identify the category of genomic test types", - "copyright": "Copyright © 2023+ NHS England Licensed under the Apache License, Version 2.0 (the \\\\\\\"License\\\\\\\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \\\\\\\"AS IS\\\\\\\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", - "compose": { - "include": [ - { - "system": "https://fhir.nhs.uk/CodeSystem/test-type-genomics", - "version": "0.2.0" - } - ] - } -} \ No newline at end of file From d341d3ab4c5fdb14b877aecdae335f45f618c0f9 Mon Sep 17 00:00:00 2001 From: KazeemHamzat Date: Thu, 9 Jul 2026 18:53:45 +0100 Subject: [PATCH 05/13] Update fhirpkg.lock.json Update fhirpkg.lock.json --- fhirpkg.lock.json | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-) diff --git a/fhirpkg.lock.json b/fhirpkg.lock.json index 1237a67..64c0436 100644 --- a/fhirpkg.lock.json +++ b/fhirpkg.lock.json @@ -1,19 +1,27 @@ { - "updated": "2026-05-06T10:21:55.9845039+01:00", + "updated": "2026-07-09T18:47:18.0145474+01:00", "dependencies": { - "hl7.fhir.r4.core": "4.0.1", - "hl7.fhir.uv.extensions.r4": "5.3.0-ballot-tc1", - "hl7.fhir.uv.xver-r5.r4": "0.1.0", + "hl7.fhir.r4.core": "4.0.1", "hl7.fhir.uv.genomics-reporting": "3.0.0", - "hl7.fhir.uv.ips": "2.0.0", "hl7.fhir.eu.laboratory": "2.0.0", + "hl7.terminology.r4": "7.1.0", + "hl7.fhir.uv.extensions.r4": "5.2.0", + "hl7.fhir.uv.xver-r5.r4": "0.1.0", + "hl7.fhir.eu.extensions.r4": "1.3.0", + "hl7.fhir.eu.base": "2.0.0", + "ihe.pharm.mpd.r4": "1.0.0-comment-2", "ihe.iti.pcf": "1.1.0", - "hl7.fhir.us.mcode": "4.0.0", + "us.nlm.vsac": "0.9.0", + "ihe.iti.balp": "1.1.4", "fhir.r4.nhsengland.pars": "0.1.2-alpha", - "fhir.r4.nhsengland.pathology": "0.1.4-alpha", - "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.nhsengland.nhse-identifiers": "0.1.1-alpha", + "fhir.r4.ukcore.stu2": "2.0.2", + "hl7.fhir.uv.ips": "2.0.0", + "hl7.fhir.uv.ipa": "1.1.0", + "hl7.fhir.uv.smart-app-launch": "2.0.0", + "fhir.r4.nhsengland.stu1": "1.5.0", + "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release" }, "missing": {} -} \ No newline at end of file +} From 6566cf73c39258a2158f2eef48c0b1846d25d10b Mon Sep 17 00:00:00 2001 From: KazeemHamzat Date: Thu, 9 Jul 2026 18:59:25 +0100 Subject: [PATCH 06/13] Update fhirpkg.lock.json update --- fhirpkg.lock.json | 1 - 1 file changed, 1 deletion(-) diff --git a/fhirpkg.lock.json b/fhirpkg.lock.json index 69078a9..725585f 100644 --- a/fhirpkg.lock.json +++ b/fhirpkg.lock.json @@ -22,7 +22,6 @@ "hl7.fhir.uv.ipa": "1.1.0", "hl7.fhir.uv.smart-app-launch": "2.0.0", "fhir.r4.nhsengland.stu1": "1.5.0", - "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release" }, "missing": {} From 89f5909962e2e74a4136c7a8191fe15e11db47f4 Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Mon, 13 Jul 2026 09:18:51 +0100 Subject: [PATCH 07/13] Testing testing --- .../NHSEngland-Specimen-Genomics.json | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/StructureDefinition/NHSEngland-Specimen-Genomics.json b/StructureDefinition/NHSEngland-Specimen-Genomics.json index 54dfe10..9aadddf 100644 --- a/StructureDefinition/NHSEngland-Specimen-Genomics.json +++ b/StructureDefinition/NHSEngland-Specimen-Genomics.json @@ -302,6 +302,19 @@ "definition": "The UK Core STU3 version of Specimen backports the R5 changes to the container BackboneElement to support capturing of storage location for a sample (through `container.location`) and recursive capture of device identifiers (e.g. tube, well, rack, freezer through `container.device`).\r\nThe container.identifier should match the identifier associated with the barcode for the tube/collection device. This can be searched using the container-id SearchParameter.\r\n\r\nAdditional examples/guidance will be provided within this IG once use of the fields has been appropriately tested.\r\n\r\nSample tracking information SHOULD be added to Tasks acting on Specimen resources, e.g. Tasks marked SamplePreparation or SampleProcessing, on either the output or input elements. This information MAY include consignment number, destination, date sent etc.\r\n\r\nIf known, the container type SHOULD be populated, using the example bound ValueSet, in SNOMED CT. If an appropraite code cannot be found, the specimen container type should be populated using free text, in Specimen.container.type.text. Additional container elements, such as capacity or specimenQuantity MAY be populated if known.", "max": "1" }, + { + "id": "Specimen.container.extension:specimenContainerLocationR5", + "path": "Specimen.container.extension", + "sliceName": "specimenContainerLocationR5", + "type": [ + { + "code": "Extension", + "profile": [ + "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" + ] + } + ] + }, { "id": "Specimen.condition", "path": "Specimen.condition", From cd69ee4fadb120517793e3b1c20aaa8cb9e7ab94 Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Mon, 13 Jul 2026 09:23:32 +0100 Subject: [PATCH 08/13] Using JPA Validator Using JPA Validator --- .github/workflows/terminology.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/terminology.yml b/.github/workflows/terminology.yml index 5174c15..a6f2ed8 100644 --- a/.github/workflows/terminology.yml +++ b/.github/workflows/terminology.yml @@ -5,7 +5,7 @@ on: # Triggers the workflow on push or pull request events but only for the master branch # Allows you to run this workflow manually from the Actions tab - #push: + push: # Allows you to run this workflow manually from the Actions tab From b59031eed540b8e647e376ab6d292dd47300d7fa Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Mon, 13 Jul 2026 09:41:35 +0100 Subject: [PATCH 09/13] Testing JPA Validatoet Testing JPA Validatoet --- .github/workflows/firely-validation.yml | 10 +++---- package.json | 8 ++--- private.package.yaml | 39 +++++++++++++++++++++++++ 3 files changed, 46 insertions(+), 11 deletions(-) create mode 100644 private.package.yaml diff --git a/.github/workflows/firely-validation.yml b/.github/workflows/firely-validation.yml index bb8cbd9..3e8518e 100644 --- a/.github/workflows/firely-validation.yml +++ b/.github/workflows/firely-validation.yml @@ -5,11 +5,11 @@ name: Firely Validation # Controls when the action will run. on: # Triggers the workflow on push or pull request events but only for the master branch - push: - branches: - - '**' - pull_request: - branches: [ master, main ] + #push: + #branches: + # - '**' + #pull_request: + #branches: [ master, main ] # Allows you to run this workflow manually from the Actions tab workflow_dispatch: diff --git a/package.json b/package.json index ca7e1ce..85b7e92 100644 --- a/package.json +++ b/package.json @@ -3,14 +3,10 @@ "description": "FHIR Genomics Implementation Guide", "author": "nhsdigital", "dependencies": { - "hl7.fhir.r4.core": "4.0.1", - "hl7.fhir.uv.extensions.r4": "5.3.0-ballot-tc1", - "hl7.fhir.uv.xver-r5.r4": "0.1.0", +"hl7.fhir.r4.core": "4.0.1", "hl7.fhir.uv.genomics-reporting": "3.0.0", - "hl7.fhir.uv.ips": "2.0.0", "hl7.fhir.eu.laboratory": "2.0.0", "ihe.iti.pcf": "1.1.0", - "hl7.fhir.us.mcode": "4.0.0", "fhir.r4.nhsengland.pars": "0.1.2-alpha", "fhir.r4.nhsengland.pathology": "0.2.4-alpha", "hl7.fhir.uv.tools.r4": "1.1.2", @@ -21,4 +17,4 @@ "4.0.1" ], "jurisdiction": "urn:iso:std:iso:3166:-2#GB" -} +} \ No newline at end of file diff --git a/private.package.yaml b/private.package.yaml new file mode 100644 index 0000000..1ec8db8 --- /dev/null +++ b/private.package.yaml @@ -0,0 +1,39 @@ +implementationguides: + hl7-fhir-uv-extensions-r4: + name: hl7.fhir.uv.extensions.r4 + version: 5.3.0-ballot-tc1 + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-xver-r5-r4: + name: hl7.fhir.uv.xver-r5.r4 + version: 0.1.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-ips: + name: hl7.fhir.uv.ips + version: 2.0.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false + fhir-r4-nhsengland-pathology: + name: fhir.r4.nhsengland.pathology + version: 0.2.4-alpha + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7-fhir-uv-tools-r4: + name: hl7.fhir.uv.tools.r4 + version: 1.1.2 + installMode: STORE_AND_INSTALL + fhir-r4-nhsengland-nhse-identifiers: + name: fhir.r4.nhsengland.nhse-identifiers + version: 0.1.1-alpha + installMode: STORE_AND_INSTALL + fetchDependencies: false + hl7.fhir.us.core: + name: hl7.fhir.us.core + version: 6.1.0 + installMode: STORE_AND_INSTALL + hl7.fhir.us.mcode: + name: hl7.fhir.us.mcode + version: 4.0.0 + installMode: STORE_AND_INSTALL + fetchDependencies: false \ No newline at end of file From 1bd8faceb7d54172cd6376d379b3fc9fc4c8756f Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Mon, 13 Jul 2026 10:51:55 +0100 Subject: [PATCH 10/13] Re-instate extension:diagnosticReportCompositionR5 Re-instate extension:diagnosticReportCompositionR5 --- ...NHSEngland-DiagnosticReport-GenomicReport.json | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json index 8d9a8e7..02ae05c 100644 --- a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json +++ b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json @@ -61,6 +61,21 @@ "path": "DiagnosticReport.extension.value[x].type", "fixedCode": "citation" }, + { + "id": "DiagnosticReport.extension:diagnosticReportCompositionR5", + "path": "DiagnosticReport.extension", + "sliceName": "diagnosticReportCompositionR5", + "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: DiagnosticReport Profile). A reference to the Composition which wraps this report for data sharing.", + "type": [ + { + "code": "Extension", + "profile": [ + "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition" + ] + } + ], + "isModifier": false + }, { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", From d9ba6b3c2e6988a67073b244fb40cba06bd892fc Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Mon, 13 Jul 2026 12:21:53 +0100 Subject: [PATCH 11/13] Re-instate backported Extension Re-instate backported Extension --- ...NHSEngland-DiagnosticReport-GenomicReport.json | 15 +++++++++++++++ .../NHSEngland-Specimen-Genomics.json | 13 +++++++++++++ 2 files changed, 28 insertions(+) diff --git a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json index 8d9a8e7..02ae05c 100644 --- a/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json +++ b/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json @@ -61,6 +61,21 @@ "path": "DiagnosticReport.extension.value[x].type", "fixedCode": "citation" }, + { + "id": "DiagnosticReport.extension:diagnosticReportCompositionR5", + "path": "DiagnosticReport.extension", + "sliceName": "diagnosticReportCompositionR5", + "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: DiagnosticReport Profile). A reference to the Composition which wraps this report for data sharing.", + "type": [ + { + "code": "Extension", + "profile": [ + "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition" + ] + } + ], + "isModifier": false + }, { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", diff --git a/StructureDefinition/NHSEngland-Specimen-Genomics.json b/StructureDefinition/NHSEngland-Specimen-Genomics.json index 54dfe10..9aadddf 100644 --- a/StructureDefinition/NHSEngland-Specimen-Genomics.json +++ b/StructureDefinition/NHSEngland-Specimen-Genomics.json @@ -302,6 +302,19 @@ "definition": "The UK Core STU3 version of Specimen backports the R5 changes to the container BackboneElement to support capturing of storage location for a sample (through `container.location`) and recursive capture of device identifiers (e.g. tube, well, rack, freezer through `container.device`).\r\nThe container.identifier should match the identifier associated with the barcode for the tube/collection device. This can be searched using the container-id SearchParameter.\r\n\r\nAdditional examples/guidance will be provided within this IG once use of the fields has been appropriately tested.\r\n\r\nSample tracking information SHOULD be added to Tasks acting on Specimen resources, e.g. Tasks marked SamplePreparation or SampleProcessing, on either the output or input elements. This information MAY include consignment number, destination, date sent etc.\r\n\r\nIf known, the container type SHOULD be populated, using the example bound ValueSet, in SNOMED CT. If an appropraite code cannot be found, the specimen container type should be populated using free text, in Specimen.container.type.text. Additional container elements, such as capacity or specimenQuantity MAY be populated if known.", "max": "1" }, + { + "id": "Specimen.container.extension:specimenContainerLocationR5", + "path": "Specimen.container.extension", + "sliceName": "specimenContainerLocationR5", + "type": [ + { + "code": "Extension", + "profile": [ + "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" + ] + } + ] + }, { "id": "Specimen.condition", "path": "Specimen.condition", From 1c0b95ba7d5cc20ab90a45f038cb9ef5acf48765 Mon Sep 17 00:00:00 2001 From: KazeemHamzat Date: Tue, 14 Jul 2026 19:56:30 +0100 Subject: [PATCH 12/13] Profile NHSEngland-Composition-GenomicsEULabReport Profile NHSEngland-Composition-GenomicsEULabReport --- ...gland-Composition-GenomicsEULabReport.json | 159 +----------------- fhirpkg.lock.json | 6 +- 2 files changed, 10 insertions(+), 155 deletions(-) diff --git a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json index ca4fa03..6a5aaf5 100644 --- a/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json +++ b/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport.json @@ -2,11 +2,11 @@ "resourceType": "StructureDefinition", "id": "NHSEngland-Composition-GenomicsEULabReport", "url": "https://fhir.nhs.uk/StructureDefinition/NHSEngland-Composition-GenomicsEULabReport", - "version": "0.3.0", + "version": "0.4.0", "name": "NHSEngland_Composition_GenomicsEULabReport", "title": "NHSEngland Composition GenomicsEULabReport", "status": "active", - "date": "2026-04-16", + "date": "2026-07-15", "publisher": "NHS England", "contact": [ { @@ -32,81 +32,6 @@ "derivation": "constraint", "differential": { "element": [ - { - "id": "Composition.extension:basedOn-order-or-requisition", - "path": "Composition.extension", - "sliceName": "basedOn-order-or-requisition", - "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: Composition Profile). A reference to the ServiceRequest which this report is in response to." - }, - { - "id": "Composition.extension:basedOn-order-or-requisition.value[x]:valueReference", - "path": "Composition.extension.value[x]", - "sliceName": "valueReference", - "type": [ - { - "code": "Reference", - "targetProfile": [ - "https://fhir.nhs.uk/StructureDefinition/NHSEngland-ServiceRequest-Genomics", - "http://hl7.eu/fhir/laboratory/StructureDefinition/ServiceRequest-eu-lab" - ], - "aggregation": [ - "referenced", - "bundled" - ] - } - ] - }, - { - "id": "Composition.extension:information-recipient", - "path": "Composition.extension", - "sliceName": "information-recipient", - "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: Composition Profile). A reference to the recipient for a report, could potentially be used to reference additional recipients over the subject and original requester for the request." - }, - { - "id": "Composition.extension:information-recipient.value[x]", - "path": "Composition.extension.value[x]", - "type": [ - { - "code": "Reference", - "targetProfile": [ - "https://fhir.nhs.uk/StructureDefinition/NHSEngland-PractitionerRole-Genomics", - "http://hl7.eu/fhir/laboratory/StructureDefinition/Practitioner-eu-lab", - "http://hl7.org/fhir/StructureDefinition/Device", - "http://hl7.eu/fhir/laboratory/StructureDefinition/Patient-eu-lab", - "http://hl7.org/fhir/StructureDefinition/RelatedPerson", - "http://hl7.eu/fhir/laboratory/StructureDefinition/PractitionerRole-eu-lab", - "http://hl7.org/fhir/StructureDefinition/Organization" - ], - "aggregation": [ - "referenced", - "bundled" - ] - } - ] - }, - { - "id": "Composition.extension:diagnosticReport-reference", - "path": "Composition.extension", - "sliceName": "diagnosticReport-reference", - "definition": "TBC. Only relevant for EU Lab aligned reports (included in HL7 EU Laboratory Report: Composition Profile). A reference to the focal DiagnosticReport this Composition is for." - }, - { - "id": "Composition.extension:diagnosticReport-reference.value[x]", - "path": "Composition.extension.value[x]", - "type": [ - { - "code": "Reference", - "targetProfile": [ - "https://fhir.nhs.uk/StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport", - "http://hl7.eu/fhir/laboratory/StructureDefinition/DiagnosticReport-eu-lab" - ], - "aggregation": [ - "referenced", - "bundled" - ] - } - ] - }, { "id": "Composition.status", "path": "Composition.status", @@ -131,16 +56,6 @@ "rules": "open" } }, - { - "id": "Composition.type.coding.display.extension:translation", - "path": "Composition.type.coding.display.extension", - "sliceName": "translation" - }, - { - "id": "Composition.type.coding.display.extension:translation.extension", - "path": "Composition.type.coding.display.extension.extension", - "min": 2 - }, { "id": "Composition.type.coding:codingGenomics", "path": "Composition.type.coding", @@ -151,51 +66,11 @@ "display": "Genetic report" } }, - { - "id": "Composition.type.coding:codingGenomics.display.extension:translation", - "path": "Composition.type.coding.display.extension", - "sliceName": "translation" - }, - { - "id": "Composition.type.coding:codingGenomics.display.extension:translation.extension", - "path": "Composition.type.coding.display.extension.extension", - "min": 2 - }, - { - "id": "Composition.type.text.extension:translation", - "path": "Composition.type.text.extension", - "sliceName": "translation" - }, - { - "id": "Composition.type.text.extension:translation.extension", - "path": "Composition.type.text.extension.extension", - "min": 2 - }, { "id": "Composition.category", "path": "Composition.category", "definition": "Fixed codes for conformance to the EU Lab Composition profile (for cross border sharing of lab reports)." }, - { - "id": "Composition.category.coding.display.extension:translation", - "path": "Composition.category.coding.display.extension", - "sliceName": "translation" - }, - { - "id": "Composition.category.coding.display.extension:translation.extension", - "path": "Composition.category.coding.display.extension.extension", - "min": 2 - }, - { - "id": "Composition.category.text.extension:translation", - "path": "Composition.category.text.extension", - "sliceName": "translation" - }, - { - "id": "Composition.category.text.extension:translation.extension", - "path": "Composition.category.text.extension.extension", - "min": 2 - }, { "id": "Composition.category:studyType", "path": "Composition.category", @@ -233,10 +108,9 @@ "code": "Reference", "targetProfile": [ "https://fhir.nhs.uk/StructureDefinition/NHSEngland-Patient-Genomics", - "http://hl7.eu/fhir/laboratory/StructureDefinition/Patient-eu-lab", - "http://hl7.eu/fhir/laboratory/StructureDefinition/Patient-animal-eu-lab", + "http://hl7.eu/fhir/base/StructureDefinition/patient-eu-core", "http://hl7.org/fhir/StructureDefinition/Group", - "http://hl7.org/fhir/StructureDefinition/Location", + "http://hl7.eu/fhir/base/StructureDefinition/location-eu-core", "http://hl7.org/fhir/StructureDefinition/Device" ], "aggregation": [ @@ -267,38 +141,19 @@ "path": "Composition.section", "definition": "To conform to EU Lab, SHOULD include references to the results that form part of the genomic report. For the UGR, will include sections that conform to the UGR folders, this work is currently in development." }, - { - "id": "Composition.section.code.coding.display.extension:translation", - "path": "Composition.section.code.coding.display.extension", - "sliceName": "translation" - }, - { - "id": "Composition.section.code.coding.display.extension:translation.extension", - "path": "Composition.section.code.coding.display.extension.extension", - "min": 2 - }, - { - "id": "Composition.section.code.text.extension:translation", - "path": "Composition.section.code.text.extension", - "sliceName": "translation" - }, - { - "id": "Composition.section.code.text.extension:translation.extension", - "path": "Composition.section.code.text.extension.extension", - "min": 2 - }, { "id": "Composition.section:sectionUGR", "path": "Composition.section", "sliceName": "sectionUGR", - "definition": "Sections included within the UGR: patient-demographics | investigations-and-procedures-requested | investigation-results | consent-for-information-sharing | family-history " + "min": 0, + "max": "*", + "definition": "Sections used to represent UGR folders." }, { "id": "Composition.section:sectionUGR.code", "path": "Composition.section.code", "binding": { "strength": "extensible", - "description": "UK Core Composition Section Codes", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-CompositionSectionCode" } } diff --git a/fhirpkg.lock.json b/fhirpkg.lock.json index 725585f..500f706 100644 --- a/fhirpkg.lock.json +++ b/fhirpkg.lock.json @@ -1,5 +1,5 @@ { - "updated": "2026-07-09T18:47:18.0145474+01:00", + "updated": "2026-07-13T13:22:07.8769811+01:00", "dependencies": { "hl7.fhir.r4.core": "4.0.1", "hl7.fhir.uv.genomics-reporting": "3.0.0", @@ -14,14 +14,14 @@ "us.nlm.vsac": "0.9.0", "ihe.iti.balp": "1.1.4", "fhir.r4.nhsengland.pars": "0.1.2-alpha", - "fhir.r4.nhsengland.pathology": "0.2.4-alpha", - "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.nhsengland.nhse-identifiers": "0.1.1-alpha", "fhir.r4.ukcore.stu2": "2.0.2", "hl7.fhir.uv.ips": "2.0.0", "hl7.fhir.uv.ipa": "1.1.0", "hl7.fhir.uv.smart-app-launch": "2.0.0", "fhir.r4.nhsengland.stu1": "1.5.0", + "fhir.r4.nhsengland.pathology": "0.2.4-alpha", + "hl7.fhir.uv.tools.r4": "1.1.2", "fhir.r4.ukcore.stu3.currentbuild": "0.29.0-pre-release" }, "missing": {} From 32a15f2f6b22266f50618c88a79f619f23554821 Mon Sep 17 00:00:00 2001 From: Kazeem Hamzat Date: Tue, 14 Jul 2026 19:59:17 +0100 Subject: [PATCH 13/13] Adding Firely Adding Firely --- .github/workflows/firely-validation.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/firely-validation.yml b/.github/workflows/firely-validation.yml index 3e8518e..bb8cbd9 100644 --- a/.github/workflows/firely-validation.yml +++ b/.github/workflows/firely-validation.yml @@ -5,11 +5,11 @@ name: Firely Validation # Controls when the action will run. on: # Triggers the workflow on push or pull request events but only for the master branch - #push: - #branches: - # - '**' - #pull_request: - #branches: [ master, main ] + push: + branches: + - '**' + pull_request: + branches: [ master, main ] # Allows you to run this workflow manually from the Actions tab workflow_dispatch: