Patch testing extension specimen.container.location

.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:
 

.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
 

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."
       },
       {

StructureDefinition/NHSEngland-DiagnosticReport-GenomicReport.json

@@ -191,9 +191,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."
       },
       {

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
       },

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
       },

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"
-}
+}

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