NHSDigital · cda69 · Nov 7, 2025 · Nov 3, 2025 · Nov 5, 2025 · Nov 5, 2025
diff --git a/...Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md b/...Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md
@@ -5,8 +5,8 @@ Product Link           | Version | Handle  | Phase    | State           | Releas
 Implementation Guide   | 1.10.0   | v1      | Live     | Current Release | 12/11/2025 | Stable     |{{pagelink:trn-General}}
 [FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.37.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 | 02/07/2025  | Stable     |{{pagelink:trn-api}}
-{{pagelink: build-testing, text: TKW}}  | 1.0.19   | v1      | Live     | Current Release | 28/03/2025   | Stable     |{{pagelink:trn-tkw}}
+[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.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}}

diff --git a/...Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md b/...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. 
 
 <br>
 <hr>

diff --git a/.../Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md b/.../Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md
@@ -1,3 +1,6 @@
+<div class="bars-blg-expander">
+<div class="bars-blg-expander-entry" id="v1.0.19">
+
 ## {{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|
 
+</div>
+</div>
 
 <br>
 <hr>
 
-### Previous Releases
 
 
 

diff --git a/.../Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.21.page.md b/.../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 |
+
+
+
+
+<br>
+<hr>
+
+### Previous Releases
+
+
+
+
+
+
+
diff --git a/...tationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml b/...tationGuide-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

diff --git a/.../Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md b/.../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   |   <mark style="background-color: Yellow">correction</mark>  |   
+|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| 
 |     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   |   <mark style="background-color: LightGreen">non-breaking</mark>  | 
 |      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   |   <mark style="background-color: LightGreen">non-breaking</mark>  | 
 |     QuestionnaireResponse.questionnaire  | Necessity Updated - MUST         |     Necessity Updated - MAY        | Update        | Referral Request         |Changes to use of QuestionnaireResponse for Nature-of-call   |   <mark style="background-color: LightGreen">non-breaking</mark>  | 

diff --git a/...tionGuide-BaRS/Home/Core/1.3.1/Appointment-StandardPattern/Introduction.page.md b/...tionGuide-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/...ide-BaRS/Home/Core/1.3.1/DocumentReference-StandardPattern/Introduction.page.md b/...ide-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
 
 <div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b>Important:  Release information</b>
-<p>This Section of the Implementation Guide is currently a preview, in an Alpha state and subject to change. There is only currently support for Appointment (booking) pointers.</p>
+<p>This section of the Implementation Guide is currently a preview, in an Alpha state and subject to change. There is currently only support for Appointment (booking) pointers.</p>
 </div>
 
 ## 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.