NHSDigital · cda69 · Oct 27, 2025 · Oct 24, 2025 · Oct 24, 2025 · Oct 24, 2025
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/About-BaRS/About-BaRS.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/About-BaRS/About-BaRS.page.md
@@ -1,67 +1,8 @@
 # {{page-title}}
 
-The NHS Booking and Referral standard (known as BaRS) is a **framework standard** for interoperability.
-
-- BaRS offers a **universal** standard way to **digitise workflows** that support all cross service patient journeys in the NHS
-- It is based on [FHIR R4]( https://hl7.org/fhir/R4/) and fully supports [UK Core]( https://simplifier.net/hl7fhirukcorer4)
-- It is a set of instructions, rules and guidance on how to use the building blocks of FHIR to **digitise workflows**
-- This provides a **framework** for suppliers to build solutions in a way that **guarantees compatibility**
-
-The majority of cross service flows in the NHS can be loosely defined as referrals however, there are many more formal definitions of referrals and BaRS is intended to support all of them and more. The primary goal is to create a framework that suppliers can operate within to share information about a patient, with some sort of directive or request for further care or tasks. This can optionally be supported by an appointment (e.g. the reservation of resource for an event at a specific time/place). 
-
-
-## Summary of the key features
-
-In order to achieve this, BaRS has adopted the approach of standardising everything that can and should be standardised whilst creating a safe space for solutions to have the necessary flexibility to support all flows whilst maintaining compatibility.
-
-There are three main "layers" that make up the framework within BaRS: 
-
-The **first** is the transport layer (referred to as BaRS Core). This is all the things that define the way two systems "talk" to each other and this layer is absolutely standardised. All systems will implement these things exactly the same way. 
-
-**Second** there is the "workflow" layer. This allows a specific BaRS compliant solution to support a particular patient journey. The *way* a workflow is articulated is standardised and each particular workflow is made up of a combination of underlying standard operations (defined in the "transport layer") in a particular sequence.
-
-**Third** there is the Payload layer. The "payloads" are collections of FHIR resources that make up the set of information that is required for the receiving system to complete or deliver the intended service or task that is being requested.
-
-The workflow and payload elements can be predefined or completely dynamic, enabled by the inbuilt content negotiation mechanism, as required by the needs of each specific use case and the sophistication of the systems implementing compliant solutions.
-
-The documentation for BaRS is separated into three groups (or "products"):
-
-- {{pagelink:design-core-1.0.7}} is the foundation containing all the things *everyone* has to do regardless of what flows BaRS is being used to support
-
-- {{pagelink:Applications}}, *apply* the standard to a specific problem and build on this to support specific use cases
-
-- {{pagelink:prereleases}}, this is the same as above but for applications that are in a *pre-release* state, so not generally available until private/public beta is complete.
-
-<br>
-
-## Foundation Principles
-
-During the design and development of the standard, all key decisions are being tested against a set of foundation principles. These were set out at the beginning as a way to ensure that the vision for BaRS is delivered and all decisions are guided by this vision.
-
-**Low Barrier to Entry**
-
-There is little point for a standard with the ambition and scope of BaRS being so difficult to implement that no one actually does. Therefore all decisions are made with the intention of making it as easy as possible for **all** suppliers to build solutions quickly and easily.
-
-**Any-to-Any Connectivity**
-
-From the beginning it has been very important to ensure that all solutions are easily scalable and it is possible to interoperate with another system without any prior knowledge or pre-configuration inplace. So that all interactions are:
-
-- live and "on-the-fly"
-- all information is available in realtime from the source
-- there is no prior knowledge required for transmission
-- there is no requirement for anything to use "point-to-point" interactions (although this approach is supported when approriate)
-
-**Universality**
-
-The primary vision for BaRS has always been to create one standard way of supporting movement of patients and their information accross services. Therefore all decisions have this idea at their heart. Research has allowed us to model the primary, high level steps as a sequence of discrete uncoupled processes that are the same every time these flows happen. 
-
-Additionally, in order to support all possible variations of these flows, the receiver *must* dictate the "payload". 
-
-Rather than the traditional approach of the sender sending everything they know, for the reciever to have to filter out everything they do not need to know, the reciever gets to state what they need to know to do the thing that is being requested of them. No more, no less.
-
-Finally, all decisions are tested against as many obscure and exotic "what-if" scenarios as possible. The intention is to avoid building a standard that only works in one care setting but not another.
-
-If you have come to this implementation guide directly it might be helpful to read some information about the program that is responsible for developing and maininting this standard, please see here: [Booking and Referral Standard (BaRS)](https://digital.nhs.uk/services/booking-and-referral-standard "Booking and Referral Standard (BaRS)") 
+The NHS Booking and Referral standard (BaRS) Implementation Guide is intended as a resource to support product and development teams in their BaRS development journey.  You can find out more about what BaRS is, how it works, who it's for and which system suppliers are already assured or working on their development on the [BaRS NHS Service Catalogue](https://digital.nhs.uk/services/booking-and-referral-standard) pages.
+
+This section provides information to help you use the Implementation Guide.
 
 
 ## Combining the elements together

diff --git a/...e-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.3.1.page.md b/...e-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.3.1.page.md
@@ -6,7 +6,8 @@ topic: TRN-Core-1.3.1
 
 | Change                                   | Description                            | Impact                          | 
 |------------------------------------------|----------------------------------------|---------------------------------|
-| ...  | ...|    <mark style="background-color: Yellow">correction</mark>  | 
+| Updated Appointment Management - Foundation Standard | Various updates and corrections throughout. Added Reschedule function.|    <mark style="background-color: Yellow">correction</mark>  | 
+| Updated Document Reference (Registry) - Foundation Standard  | Various updates and corrections throughout. |    <mark style="background-color: Yellow">correction</mark>  | 
 
 <br>
 <hr>

diff --git a/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/2.0.0.page.md b/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/2.0.0.page.md
@@ -9,15 +9,17 @@ This is a major release with a significant change to the Implementation Guidance
 
 | Change                                    | Description                                     | Impact                                                                  | 
 |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------|
-| NHSno  |  ??? |    <mark style="background-color: Red">correction</mark>  | 
+| Updated requirements to support additional NHS No. Status  |  Extended requirement to support NHS No. status of 'Number present but not traced' |    <mark style="background-color: Red">breaking</mark>  | 
 
 ### Payload Change Log
 
 
 | FHIR Element                                         | Previous | Current    | Other   | Referral/Booking | Rationale                                                                                       |  Impact  |
 |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
-| NHSNo  |          |            | Update        |          |   |   <mark style="background-color: Red">correction</mark>  |  
-
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   This SHOULD be populated. Where used this MUST either be number-present-and-verified or no NHS number MUST be sent, no other status is valid       | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   This SHOULD be populated. Where used this MUST either be populated with 'Number present and-verified' no other status is valid       |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   This SHOULD be populated. Where used this MUST either be number-present-and-verified or no NHS number MUST be sent, no other status is valid       | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Booking Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   This SHOULD be populated. Where used this MUST either be populated with 'Number present and-verified' no other status is valid       |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Booking Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
 
 <br>
 <hr>

diff --git a/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/2.0.0.page.md b/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/2.0.0.page.md
@@ -9,15 +9,17 @@ This is a major release with a significant change to the Implementation Guidance
 
 | Change                                    | Description                                     | Impact                                                                  | 
 |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------|
-| NHSno  |  ??? |    <mark style="background-color: Red">correction</mark>  | 
+| Updated requirements to support additional NHS No. Status  |  Extended requirement to support NHS No. status of 'Number present but not traced' |    <mark style="background-color: Red">breaking</mark>  | 
 
 ### Payload Change Log
 
 
 | FHIR Element                                         | Previous | Current    | Other   | Referral/Booking | Rationale                                                                                       |  Impact  |
 |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
-| NHSNo  |          |            | Update        |          |   |   <mark style="background-color: Red">correction</mark>  |  
-
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   This SHOULD be populated. Where used this MUST either be number-present-and-verified or no NHS number MUST be sent, no other status is valid       | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   This SHOULD be populated. Where used this MUST either be populated with 'Number present and-verified' no other status is valid       |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   This SHOULD be populated. Where used this MUST either be number-present-and-verified or no NHS number MUST be sent, no other status is valid       | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Booking Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   This SHOULD be populated. Where used this MUST either be populated with 'Number present and-verified' no other status is valid       |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Booking Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
 
 <br>
 <hr>

diff --git a/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/2.0.0.page.md b/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/2.0.0.page.md
@@ -9,14 +9,15 @@ This is a major release with a significant change to the Implementation Guidance
 
 | Change                                    | Description                                     | Impact                                                                  | 
 |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------|
-| NHSno  |  ??? |    <mark style="background-color: Red">correction</mark>  | 
+| Updated requirements to support additional NHS No. Status  |  Extended requirement to support NHS No. status of 'Number present but not traced' |    <mark style="background-color: Red">breaking</mark>  | 
 
 ### Payload Change Log
 
 
 | FHIR Element                                         | Previous | Current    | Other   | Referral/Booking | Rationale                                                                                       |  Impact  |
 |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
-| NHSNo  |          |            | Update        |          |   |   <mark style="background-color: Red">correction</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   Follow UK Core guidance for populating this element          | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   Follow UK Core guidance for populating this element          |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
 
 
 <br>

diff --git a/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md b/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md
@@ -9,14 +9,15 @@ This is a major release with a significant change to the Implementation Guidance
 
 | Change                                    | Description                                     | Impact                                                                  | 
 |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------|
-| NHSno  |  ??? |    <mark style="background-color: Red">correction</mark>  | 
+| Updated requirements to support additional NHS No. Status  |  Extended requirement to support NHS No. status of 'Number present but not traced' |    <mark style="background-color: Red">breaking</mark>  | 
 
 ### Payload Change Log
 
 
 | FHIR Element                                         | Previous | Current    | Other   | Referral/Booking | Rationale                                                                                       |  Impact  |
 |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
-| NHSNo  |          |            | Update        |          |   |   <mark style="background-color: Red">correction</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.code |   Follow UK Core guidance for populating this element          | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted.  | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  |  
+| Patient.identifier.extension.valueCodeableConcept.coding.display |   Follow UK Core guidance for populating this element          |  This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted.      | Update        | Referral Request         |Accommodate NHS No. Requirement  |   <mark style="background-color: Red">breaking</mark>  | 
 
 
 <br>

diff --git a/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md b/...de-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md
@@ -1,3 +1,5 @@
+<div class="bars-blg-expander">
+<div class="bars-blg-expander-entry" id="v1.1.3">
 ## {{page-title}}
 
 <br>
@@ -27,8 +29,10 @@ This stable release (v1.1.3) of Application 5 sees minor corrections.
 | MedicationStatement  |  https://simplifier.net/hl7fhirukcorer4/ukcoremedicationstatement         |   https://simplifier.net/hl7fhirukcorer4/ukcore-medicationstatement          | Update        | Referral Request         |FHIR link updated   |   <mark style="background-color: Yellow">correction</mark>  |  
 | bundle.meta.versionID |      |   This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing.        | Update        | Referral Request         |Implementation guidance added   |   <mark style="background-color: Yellow">correction</mark>  | 
 
+</div>
+</div>
+
 <br>
 <hr>
 
-### Previous Releases