From 3763b5288816e4e9a55479c18e3148cf010a2c71 Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Mon, 3 Nov 2025 10:16:25 +0000 Subject: [PATCH 1/6] Assurance-Clinical-change --- .../Home/Assure/Assure/Assure.page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md index 5bf5edf9..a8ed7900 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md @@ -6,7 +6,7 @@ The assurance process ensures solutions adhere to the Standard and are compatibl The purpose of assurance is to: * Validate conformance to the requirements and specifications of the Standard -* Assess higher-risk and/or complex workflow scenarios, to ensure technical and clinical readiness +* Assess higher-risk and/or complex workflow scenarios, ensuring patient safety and technical and clinical readiness * Serve as a final quality assurance checkpoint prior to deployment to Production There are limitations to this (self) assurance process, which does **not** extend to: From c2e56f174c1caed13869d7459c285ed287257f1d Mon Sep 17 00:00:00 2001 From: luci-davies Date: Wed, 5 Nov 2025 09:43:27 +0000 Subject: [PATCH 2/6] Typo fixes --- .../1.3.1/Appointment-StandardPattern/Introduction.page.md | 2 +- .../DocumentReference-StandardPattern/Introduction.page.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/Appointment-StandardPattern/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/Appointment-StandardPattern/Introduction.page.md index 01a7f501..3d370d27 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/Appointment-StandardPattern/Introduction.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/Appointment-StandardPattern/Introduction.page.md @@ -12,7 +12,7 @@ topic: core-StandardPattern-appointment-Introduction-1.3.1 The [BaRS API](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir) suite can be used where there is no specific use-case supported by the {{pagelink:Home/Applications/BaRS-Applications, text:Applications}} to fulfil generic Appointment workflows, referred to as Appointment Management Foundation. This section outlines the functionality supported, workflows involved and how these correspond with the [API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0). -This includes using {{pagelink:core-StandardPattern-document-reference-1.3.1, text: DocumentReference Standard Pattern}} to write pointers for bookings to a central respository, commonly referred to as the Registry. +This includes using {{pagelink:core-StandardPattern-document-reference-1.3.1, text: Standard Pattern DocumentReference}} to write pointers for bookings to a central respository, commonly referred to as the Registry. The Appointment Management Foundation is based on {{pagelink:design-core-1.3.1, text:BaRS Core}} and an understanding of the central tenets is essential before beginning. This includes: - * {{pagelink:core-EndToEndWorkflow-1.3.1, text:End to end workflow }} - how Senders and Receivers, interacting through the central Proxy, negotiate compatibility and engage diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/DocumentReference-StandardPattern/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/DocumentReference-StandardPattern/Introduction.page.md index caef46e2..a0bad8db 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/DocumentReference-StandardPattern/Introduction.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.1/DocumentReference-StandardPattern/Introduction.page.md @@ -5,12 +5,12 @@ topic: core-StandardPattern-document-reference-Introduction-1.3.1 # Standard Pattern - DocumentReference ## Introduction -There is functionality in BaRS to accommodate the use of pointers (DocumentReference resources), to locate existing bookings and referrals from a central Registy. +There is functionality in BaRS to accommodate the use of pointers (DocumentReference resources), to locate existing bookings and referrals from a central Registry. This section will walk you through the process of using FHIR DocumentReferences, from the central Registry, to find and retrieve bookings and referrals held at Receiver services. From 44d342f0dd7079ec61c52e73a46e40cb3000c8df Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Wed, 5 Nov 2025 13:03:05 +0000 Subject: [PATCH 3/6] TKW-ReleaseNote 1.0.21 --- .../TKW-Change-Log/1.0.19.page.md | 6 +++- .../TKW-Change-Log/1.0.21.page.md | 29 +++++++++++++++++++ .../TKW-Change-Log/toc.yaml | 2 ++ 3 files changed, 36 insertions(+), 1 deletion(-) create mode 100644 guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.21.page.md diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md index ecf22cd8..d08ede89 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md @@ -1,3 +1,6 @@ +
+
+ ## {{page-title}} ### Workflow and payload developments @@ -34,11 +37,12 @@ Support for Application5 TKW Receiver and Use-Case Category (UCC) functionality |Bug |NBRS-3964 |TKW Receiver - Remove need for double 'context' parameter in MessageDefinition GET| |Bug |NBRS-3876 |Slot.id from GET /Slot not being included in booking request bundle| +
+

-### Previous Releases diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.21.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.21.page.md new file mode 100644 index 00000000..070cb331 --- /dev/null +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.21.page.md @@ -0,0 +1,29 @@ +## {{page-title}} + + +### General fixes + +| Issue Type | Issue key | Summary | +|------------|-----------|------------------------------------------------------------------------------| +|Bug |NBRS-3726 |MessageDefinition - Error scenarios tests for each Application | +|Bug |NBRS-3905 |When doing search free and busy slots, no Id are present | +|Bug |NBRS-3728 |Application 5 - Missing test 'Request using the same payload Id' | +|Bug |NBRS-4262 |Remove Additional ampersand character after 'start=ge' | +|Bug |NBRS-4266 |Observation.note to be removed from requests | +|Bug |NBRS-4261 |Missing patient:identifier parameter in requests | +|Bug |NBRS-3034 |App5 - Incorrect reference against ServiceRequest.performer | + + + + +
+
+ +### Previous Releases + + + + + + + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml index 7537651f..ab7ba1a3 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml @@ -1,5 +1,7 @@ - name: Index filename: Index.page.md +- name: 1.0.21 + filename: Index.page.md - name: 1.0.19 filename: 1.0.19.page.md - name: 1.0.12 From e92c5b2ea780e41c14a7b77ff4cdb458dd04edc4 Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Wed, 5 Nov 2025 13:05:42 +0000 Subject: [PATCH 4/6] CurrentReleaseTbl --- .../Home/About-BaRS/Releases/Current-Releases.page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md index d0e85374..4a99adb7 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md @@ -6,7 +6,7 @@ Implementation Guide | 1.10.0 | v1 | Live | Current Release | 12/11 [FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.35.0) | 1.37.0| v1 | Live | Current Release | 12/11/2025 | Stable | {{pagelink:design-core-1.3.1, text:BaRS Core}} | 1.3.1 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-core, text: BaRS Core Change Log}} [API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_3_0) | 1.3.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-api}} -{{pagelink: build-testing, text: TKW}} | 1.0.19 | v1 | Live | Current Release | 28/03/2025 | Stable |{{pagelink:trn-tkw}} +{{pagelink: build-testing, text: TKW}} | 1.0.21 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-tkw}} {{pagelink:application1, text:BaRS-APP1}} | 2.0.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-app1,text:BaRS APP1 Change Log}} {{pagelink:application2, text:BaRS-APP2}} | 2.0.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-app2,text:BaRS APP2 Change Log}} {{pagelink:application3, text:BaRS-APP3}} | 2.0.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-app3,text:BaRS APP3 Change Log}} From b63a41d9792e58217bd34b1debcd16a5440b2b6a Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Wed, 5 Nov 2025 13:07:32 +0000 Subject: [PATCH 5/6] Revert "Assurance-Clinical-change" This reverts commit 3763b5288816e4e9a55479c18e3148cf010a2c71. --- .../Home/Assure/Assure/Assure.page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md index a8ed7900..5bf5edf9 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md @@ -6,7 +6,7 @@ The assurance process ensures solutions adhere to the Standard and are compatibl The purpose of assurance is to: * Validate conformance to the requirements and specifications of the Standard -* Assess higher-risk and/or complex workflow scenarios, ensuring patient safety and technical and clinical readiness +* Assess higher-risk and/or complex workflow scenarios, to ensure technical and clinical readiness * Serve as a final quality assurance checkpoint prior to deployment to Production There are limitations to this (self) assurance process, which does **not** extend to: From baddfd9df9a44e7f38324a8d723735258cf85226 Mon Sep 17 00:00:00 2001 From: luci-davies Date: Wed, 5 Nov 2025 16:17:24 +0000 Subject: [PATCH 6/6] Change log fixes --- .../Implementation-Guide-Change-Log/1.10.0.page.md | 1 + .../Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md | 3 +-- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md index 181c567f..3354a34c 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md @@ -8,6 +8,7 @@ | Home page |The heading has been updated to make it clear to users that they are in the BaRS Implementation Guide, quick start guide link has been separated to improve direct navigation and content has been transformed based on user feedback| | Deploy |New pages for Technical deployment have been added to support suppliers and providers through specific technical steps in their implementation journey.| | Assure |Provided clarity on the expectations and limitation of the assurance process.| +| Testing and environments |Onboarding renamed to Connecting to environments. Specific sections created for Connecting as a sender and Connecting as a receiver to make navigation easier and give step by step guidance.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md index 66dfcebe..12490805 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md @@ -18,8 +18,7 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | -|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| patient.identifier.system | | This SHOULD be populated with the namespace for the Identifier | Update | Referral Request |Implementation Guidance consistent across all applications | correction | +|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| | QuestionnaireResponse.extension.valueCodeableConcept.text | This SHOULD be populated with the name of the questionnaire responses contained within. | This SHOULD be populated with the name of the questionnaire responses contained within. For the Nature-of-call response this MUST be set to 'Nature of Call (NOC)' | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking | | QuestionnaireResponse.questionnaire | Example updated - https://fhir.nhs.uk/Questionnaire/NOC | Example updated - https://fhir.nhs.uk/Questionnaire/PTS | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking | | QuestionnaireResponse.questionnaire | Necessity Updated - MUST | Necessity Updated - MAY | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking |