diff --git a/guides/Live-ImplementationGuide-BaRS/Home/111-ED-backup-of-placeholder-content.page.md b/guides/Live-ImplementationGuide-BaRS/Home/111-ED-backup-of-placeholder-content.page.md
deleted file mode 100644
index ae690a4e..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/111-ED-backup-of-placeholder-content.page.md
+++ /dev/null
@@ -1,19 +0,0 @@
-## {{page-title}}
-
-### Application specific requirements
-
-In addition to the core requirements;
-
-A receiver must be capable of:
-
-- notifying a sender if a patient with identified prior safeguarding concerns fails to attend
-
-A sender must be capable of:
-
-- accepting a response concerning of a failed attendance for a patient with safeguarding concerns
-
-
-
-### Workflow
-
-{{render:referral-request-booking-111-ED-workflow}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/About-BaRS.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/About-BaRS.page.md
deleted file mode 100644
index e2dc2e6e..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/About-BaRS.page.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# {{page-title}}
-
-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
-
-It is common to use a recipe analogy to describe complex concepts. It is also possible to describe the payload entities within the BaRS standard using this analogy. In this analogy the recipe is for a specific cake which corresponds to a BaRS Application conformant solution developed by suppliers to enable the digitisation of a use case specific workflow.
-
-
-
-**Profiles**
-
-Profiles are the base **ingredients** for the BaRS and come from two sources.
-
-- **UK Core**
- specifies a set of constraints and/or extensions to specific base FHIR resources to enable consistent information flows across UK borders, to improve health and care outcomes for all citizens
-
-- **BaRS**
-specifies additional constraints and/or extensions to UK core profiles, that are common for all BaRS Applications
-
-**Cardinalities**
-
-All attributes defined in FHIR have cardinality as part of their definition - a minimum number of required appearances and a maximum number. These numbers specify the number of times the attribute may appear in any instance of the resource type. This equates to the **Quantity** in the recipe analogy. Failure to conform to the cardinality of a FHIR attribute will lead to a FHIR validation failure in the same was as altering the quantities of key ingredients will result in a failed cake. See https://hl7.org/fhir/conformance-rules.html for more details about cardinality in FHIR.
-
-**Necessity**
-
-Necessity is an additional layer of conformance and specifies if the population of an element by the SENDER is required for successful execution of the business process that the BaRS Application is enabling. This relates to optionality of ingredients in a recipe. If you want your cake to be a lemon cake, then you MUST add lemons! See Definition of conformance key words for more information.
-
-**Implementation guidance**
-
-Implementation guidance is provided at several levels in the BaRS, for example, at the FHIR element, resource and bundle levels. It describes how these attributes should be populated to support the business process that is used in each BaRS Application. It corresponds to the **Method** in the recipe analogy, which also can be at the ingredient level or the recipe level.
-
-**Core Payload definition**
-
-BaRS will have Core Payload Definitions that will relate to all BaRS Applications that are build on that definition, e.g. Urgent Referral. These correspond to a **Basic Recipe** in the recipe analogy. A good example would be a vanilla sponge. This recipe can be added to to make a variety of cakes for different occasions (or use cases). For BaRS v1.0.0 core payload definitions are not documented as they require more BaRS use cases to be defined so that the common elements can be identified.
-
-**Application**
-
-A BaRS Application consists of implementation guidance that describes how a supplier builds a BaRS conformant solution for a **specific workflow** using the BaRS toolbox. This corresponds to the **Full recipe** for a specific cake, potentially for a
-specific occasion.
-
-
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Definitions-of-Key-Terms.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Definitions-of-Key-Terms.page.md
deleted file mode 100644
index 98228aaa..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Definitions-of-Key-Terms.page.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-topic: definitions_key_terms
----
-
-# {{page-title}}
-
-The Booking and Referral Standard (BaRS) deals with 'bookings' and 'referrals' as they relate to a patient's journey. In the context of BaRS, we use these terms to mean the following:
-
-## Booking
-Booking is the administrative function of reserving time-based capacity at a service provider. It can take one of two forms:
-
-- the traditional appointment at a specified time
-- a timeframe within which the patient can expect to be seen, based on their assessed clinical severity (acuity) and capacity at the service
-
-Booking consists of the sender and receiver roles
-
-- the sender is the service assessing the patient and wishing to send them to another service
-- the receiver is the service the sender wishes to make the booking with
-
-When a booking is made in conjunction with a referral, the receiving service must link the booking and referral together.
-
-## Referral
-A referral is a request for a care service, other than a specific diagnostic investigation or diagnostic procedure, to be provided for a patient.
-
-The information included in the referral is primarily clinical and must allow the receiver to understand the reason for the referral and the detail of any assessment carried out by the sending service. This is key for patient care and experience as the patient transitions between services.
-
-The complete information transmitted in the referral depends on the use case. This is informed by user research and endorsed by specialist bodies in those fields.
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Elements-of-the-Standard.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Elements-of-the-Standard.page.md
deleted file mode 100644
index 73f5313e..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Elements-of-the-Standard.page.md
+++ /dev/null
@@ -1,47 +0,0 @@
- # {{page-title}}
-
-BaRS is made up of a set of documentation and optional infrastructure components
-
-## Documentation
-
-BaRS documentation is as follows:
-
-| Item | Description |
-|----------------------------------|------------------------------------------------------------------------------------------------------------|
-| [BaRS homepage]( https://digital.nhs.uk/services/booking-and-referral-standard) | An overview of the BaRS programme, the benefits of the standard and status of supplier development |
-| Implementation guide (this site) | You will need to use both the BaRS Core page and the BaRS Applications page specific to your use case. |
-| [API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0) | The specification for integrating with optional BaRS central infrastructure
-
-
-
-## Infrastructure
-
-The infrastructure components defined as parts of BaRS are offered for use as a set of centralised services that can support workflows and simplify integration between systems.
-
-There are two elements to this infrastructure:
-
-- **a routing proxy** that enables systems to connect to each other in a scalable way that does not require each side to have pre-configured direct connections
-- a set of enabling **discovery services** that allow BaRS clients to "discover" events, tasks and requests that have been made using BaRS compliant systems from a number of contexts
-
-The routing proxy is the main infrastructure component of BaRS and is hosted and maintained on the centralised NHS API Management platform. It is comprised of several components but, from a developer perspective, it can be thought of as a proxy. All requests are routed through it, it brokers the endpoint for a given service (on behalf of a sender) and delivers the request to the receiver. It can support both national and regional scale service implementations, including any type of service discovery tool. This centralised infrastructure speeds up your development and rollout by handling the burden of establishing endpoints and connectivity; a sender need only communicate with the BaRS proxy and a receiver only needs to accept requests from it.
-
-Components of BaRS centralised infrastructure are as follows:
-
-| Component | Description |
-|-----------------------|--------------|
-| BaRS Proxy API | Senders direct all requests to this Proxy API for all requests. |
-| Endpoint catalogue | A component that holds service identifiers and their corresponding physical addresses. It is capable of supporting national and local directory of services or even standalone endpoints configured within a single system. Providers will be able to manag their endpoints via an API. |
-| BaRS proxy | The proxy makes the request to the receiver |
-
-
-The following components are in development:
-
-| Component | Description |
-|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Registry | A store of pointers to bookings and referrals made through BaRS. Receivers will create and maintain the status of any pointers for the lifecycle of the events they refer to. It is a store of current active events and cannot be interrogated for historical ones. Access to the registry will be controlled by authentication at the API layer and authorisation to access the data will be delegated to the data owner. |
-| Events | Closely tied with the registry, this will notify parties (directly related or interested 3rd parties) of events occurring on pointers in the registry. |
-
-
-
-
-
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Index.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Index.guide.md
deleted file mode 100644
index bd5bd308..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Index.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
----
-topic: about_bars
----
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Quick-Start-Guide.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Quick-Start-Guide.page.md
deleted file mode 100644
index 070ec24b..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/Quick-Start-Guide.page.md
+++ /dev/null
@@ -1,66 +0,0 @@
-# {{page-title}}
-
-Follow this **Quick Start Guide** to best understand how to approach BaRS:
-
-### Discover
-We recommend reading the following documentation as part of the discovery stage to inform planning:
-
-* {{pagelink:definitions_key_terms, text:Definition of key terms}}
-* {{pagelink:design-core-1.0.7, text:BaRS Core}}
-* {{pagelink:applications, text:BaRS Applications}}
-* [BaRS FHIR API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0)
-
-### Onboarding
-{{pagelink:Testing-and-Environments, text:Connecting to environments}} on our platform is a self-service process. This step is required to make requests of the BaRS API and have requests forwarded to your endpoint, as a Receiver. This **must** occur on both Integration (INT) and Production environments.
-
-Full details of the security model adopted by the platform can be found under the [security](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication) section.
-
-### Design
-The following sections provide the essential information needed to design and build a BaRS compliant solution. BaRS is devised in a way to support re-use of functionality across multiple uses cases, to this end the implementation guidance is split into {{pagelink:design-core-1.0.7, text:BaRS Core}} and {{pagelink:applications, text:BaRS Application}} sections. All solutions **must** build the Core and add the specific requirements of the Application to support the given use case. BaRS Core is not sufficient on its own, an Application will always be required.
-
-### End-to-end workflow
-When developing against the standard, understanding the {{pagelink:core-EndToEndWorkflow-1.0.7, text:end-to-end workflow}} is key. This section of the guide describes how a solution interacts with the BaRS API, along with the assumptions and expectations of Senders and Receivers. These are the roles suppliers will adopt when building a solution. This guide is written predominantly from the perspective of the request; the Sender and Receiver of the request. However, if the BaRS Application include a response workflow these roles swap, the Sender becoming the Receiver and vice versa.
-
-BaRS includes several {{pagelink:applications, text:BaRS Application (use cases)}}, each of which supports multiple use cases that share a common workflow and data model.
-
-
-### API Spec
-The BaRS [API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0) provides detail of the structure of endpoints. The specification allows you to 'Try this API', calling endpoints to view anticipated responses. This is a purely technical document and must be read in conjunction with implementation guidance to build a compliant solution.
-
-### Security
-All {{pagelink:core-Security-1.0.7, text:security}} is provided through our platform. There are two methods for securing interactions via BaRS API:
-* senders will [generate an access token](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication#how-this-pattern-works) from the platform and use this to authenticate with the BaRS API. Additionally, requests will include HTTP header values identifying the organisation, software and user, which are passed through the BaRS API to Receivers who apply their own access control to the request based on the headers content.
-* for Receivers accepting requests, the BaRS API secures the connection with the Receiver using Transport Layer Security Mutual Authentication (TLS MA), using an [NHS Root CA issued certificate](https://digital.nhs.uk/services/path-to-live-environments/live-environment#rootca-and-subca-certificates). The HTTP header values (as described above) are also passed through. This provides the Receiver with sufficient information to accept or reject the request without having to inspect the payload body.
-
-#### Error Handling
-{{pagelink:core-ErrorHandling-1.0.7, text:Error handling}} is an important part of the standard for two key reasons:
-
-* to ensure workflow is as smooth and seamless as possible, the error responses returned **must** be clear to allow the appropriate next action to take place, for example, to include a missing element of information (highlighted by the error response).
-* there are several levels of interactions occurring from the Sender, through BaRS API to the Receiver and clearly identifying where the fault lies is important for swift resolution. All implementations **must** adhere to the {{pagelink:core-ErrorHandling-1.0.7, text:error handling guidance}} which is part of the {{pagelink:assure, text:assurance}} process.
-
-### Build
-#### Environments
-The principle environment for development and testing is the INT (integration) environment. This is a like-live environment, harnessing full security and functionality that can expect to be encountered in Production. In addition, the BaRS API specification links to the Sandbox environment, which is capable of demonstrating the key functionality but without the security overhead.
-
-
-
-#### Toolkit Workbench (TKW)
-{{pagelink:build-testing, text:TKW - Toolkit Workbench}} - is a tool to assist development and assurance of supplier solutions to become BaRS compliant.
-
-The tool supports testing of key high-level workflows e.g. a booking routine, including the asynchronous flows, as well as being capable of inspecting low level technical requirements. It reports the output in Validation Reports which clearly indicate to the reader where and why a test has failed. In addition, the tool supports consistent error states which are often difficult to create but required for development and assurance. TKW is deployed to the INT enviornment and, therefore, requests/responses will occur under Production like conditions.
-
-### Assure
-{{pagelink:assure, text:Assurance}} for BaRS is achieved by completing and providing evidence, via a Supplier Conformance Assessment List (SCAL), through the [Digital Onboarding Portal](https://digital.nhs.uk/developer/guides-and-documentation/digital-onboarding).
-
-**Supplier Conformance Assessment List (SCAL)**
-
-To complete assurance you need to:
-
-* complete all SCAL sections through the [Digital Onboarding Portal](https://digital.nhs.uk/developer/guides-and-documentation/digital-onboarding)
-* provide evidence and supporting diagrams which will enable the Solution Assurance Team to understand the solution and ensure it meets the required standard
-* demonstrate an end-to-end test of solution functionality within the integration environment (INT)
-* Provide evidence of compliance with DCB0129: Clinical Risk Management: its Application in the Manufacture of Health IT Systems
-* State that you have reviewed the BaRS Clinical Safety Case Report and Hazard Log, have integrated transferred risks into your own Hazard Log and have implemented appropriate mitigation as stipulated
-
-### Deploy
-Once a solution is developed (and assured, if deploying to Production) it can be deployed. This stage involves installing, configuring and thoroughly testing the solution to ensure it behaves as intended and users are conversant with all aspects of functionality. It is likely to involve numerous parties across multiple organisations and require meticulous planning. The guidance provided is a suggested check-list of steps to consider and is not exhaustive.
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/toc.yaml
deleted file mode 100644
index 3b1f4607..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/About-BaRS/toc.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-- name: Index
- filename: Index.guide.md
-- name: About BaRS
- filename: About-BaRS.page.md
-- name: Definitions of key terms
- filename: Definitions-of-Key-Terms.page.md
-- name: Elements of the standard
- filename: Elements-of-the-Standard.page.md
-- name: Quick Start Guide
- filename: Quick-Start-Guide.page.md
-
-
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/Sender-MessageDefiniton.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/Sender-MessageDefinition.page.md
similarity index 100%
rename from guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/Sender-MessageDefiniton.page.md
rename to guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/Sender-MessageDefinition.page.md
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/toc.yaml
index 7ab47e3c..6104751e 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Content-Negotiation/toc.yaml
@@ -3,7 +3,7 @@
- name: Mechanism
filename: Mechanism.page.md
- name: Workflow
- filename: Workflow.page.md
+ filename: WorkFlow.page.md
- name: Sender MessageDefiniton
filename: Sender-MessageDefinition.page.md
- name: Sender CapabilityStatement
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP1/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP1/toc.yaml
index 5a6c3a54..13b877d7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP1/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP1/toc.yaml
@@ -20,3 +20,5 @@
filename: 1.0.1.page.md
- name: 1.0.0
filename: 1.0.0.page.md
+- name:
+ filename: Archive.page.md
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/toc.yaml
index 3478d211..3f192295 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/toc.yaml
@@ -8,3 +8,7 @@
filename: Previous-Releases.page.md
- name:
filename: Technical-Release-Notes
+- name:
+ filename: Compatibility-Matrix.page.md
+- name:
+ filename: Pre-Releases.page.md
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/RolesAndResponsibilities.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/RolesAndResponsibilities.page.md
similarity index 100%
rename from guides/Live-ImplementationGuide-BaRS/Home/Analysis/RolesAndResponsibilities.md
rename to guides/Live-ImplementationGuide-BaRS/Home/Analysis/RolesAndResponsibilities.page.md
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/toc.yaml
index 7e782147..86b2a2e7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/toc.yaml
@@ -1,11 +1,11 @@
-- name: Analysis
- filename: Analysis
+- name: Index
+ filename: index.page.md
- name: BaRS Principles and Prerequisites
filename: BaRS-Principles-and-Prerequisites
- name: Infrastructure
filename: Infrastructure
- name: Roles and Responsibilities
- filename: RolesAndResponsibilities.md
+ filename: RolesAndResponsibilities.page.md
- name: Releases
filename: Releases
- name: Versioning
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/ARP-Priority-Codes.page.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/ARP-Priority-Codes.page.md
deleted file mode 100644
index 32e5548b..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/ARP-Priority-Codes.page.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/arp-priority-codes}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Consent-Categories-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Consent-Categories-BARS.guide.md
deleted file mode 100644
index 7536f41a..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Consent-Categories-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/consent-categories-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/DOS-Rejected-Reasons-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/DOS-Rejected-Reasons-BARS.guide.md
deleted file mode 100644
index 3b9da9d0..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/DOS-Rejected-Reasons-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/dos-rejected-reasons-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Flag-Categories-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Flag-Categories-BARS.guide.md
deleted file mode 100644
index 5f33aa82..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Flag-Categories-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/flag-categories-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/HTTPErrorCodes.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/HTTPErrorCodes.guide.md
deleted file mode 100644
index 76b3d243..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/HTTPErrorCodes.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/http-error-codes}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Household-Composition-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Household-Composition-BARS.guide.md
deleted file mode 100644
index 1cd9a60c..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Household-Composition-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/household-composition-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageCategoryServiceRequest.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageCategoryServiceRequest.guide.md
deleted file mode 100644
index 09207688..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageCategoryServiceRequest.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/message-category-servicerequest}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageEventsBARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageEventsBARS.guide.md
deleted file mode 100644
index 13798b2b..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageEventsBARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/message-events-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageReasonBARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageReasonBARS.guide.md
deleted file mode 100644
index 0a97b103..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/MessageReasonBARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/message-reason-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Reasonable-Adjustment-Codes-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Reasonable-Adjustment-Codes-BARS.guide.md
deleted file mode 100644
index e6109c42..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Reasonable-Adjustment-Codes-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/reasonable-adjustment-codes-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Safeguarding-Codes-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Safeguarding-Codes-BARS.guide.md
deleted file mode 100644
index 14f18d09..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Safeguarding-Codes-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/safeguarding-codes-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Scene-Safety-Codes-BARS.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Scene-Safety-Codes-BARS.guide.md
deleted file mode 100644
index aaa4e3e5..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/Scene-Safety-Codes-BARS.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/scene-safety-codes-bars}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeDXCodes.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeDXCodes.guide.md
deleted file mode 100644
index cb6eba9a..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeDXCodes.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/pathways-dx-codes, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomePathwaysCodes.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomePathwaysCodes.guide.md
deleted file mode 100644
index f3e17348..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomePathwaysCodes.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/pathways-pathway-codes, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSDCodes.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSDCodes.guide.md
deleted file mode 100644
index d9c234c8..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSDCodes.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/pathways-sd-codes, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSGCodes.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSGCodes.guide.md
deleted file mode 100644
index 5898c89f..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/TriageOutcomeSGCodes.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{render:https://fhir.nhs.uk/CodeSystem/pathways-sg-codes, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/toc.yaml
deleted file mode 100644
index 2ee35ca9..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllCodeSystems/toc.yaml
+++ /dev/null
@@ -1,32 +0,0 @@
-- name: Message Events BARS
- filename: MessageEventsBARS.guide.md
-- name: Message Reason BARS
- filename: MessageReasonBARS.guide.md
-- name: Message Category Service Request
- filename: MessageCategoryServiceRequest.guide.md
-- name: Triage Outcome DX Codes
- filename: TriageOutcomeDXCodes.guide.md
-- name: Triage Outcome Pathways Codes
- filename: TriageOutcomePathwaysCodes.guide.md
-- name: Triage Outcome SD Codes
- filename: TriageOutcomeSDCodes.guide.md
-- name: Triage Outcome SG Codes
- filename: TriageOutcomeSGCodes.guide.md
-- name: HTTP Error Codes
- filename: HTTPErrorCodes.guide.md
-- name: Consent Categories BARS
- filename: Consent-Categories-BARS.guide.md
-- name: DOS Rejected Reasons BARS
- filename: DOS-Rejected-Reasons-BARS.guide.md
-- name: Flag Categories BARS
- filename: Flag-Categories-BARS.guide.md
-- name: Household Composition BARS
- filename: Household-Composition-BARS.guide.md
-- name: Reasonable Adjustment Codes BARS
- filename: Reasonable-Adjustment-Codes-BARS.guide.md
-- name: Safeguarding Codes BARS
- filename: Safeguarding-Codes-BARS.guide.md
-- name: Scene Safety Codes BARS
- filename: Scene-Safety-Codes-BARS.guide.md
-- name: ARP Priority Codes
- filename: ARP-Priority-Codes.page.md
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/CDSSExtension.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/CDSSExtension.guide.md
deleted file mode 100644
index b8656305..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/CDSSExtension.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{tree:https://fhir.nhs.uk/StructureDefinition/CDSSExtension, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/Index.page.md
deleted file mode 100644
index 0248c13d..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/Index.page.md
+++ /dev/null
@@ -1 +0,0 @@
-## {{page-title}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/LocationExtension.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/LocationExtension.guide.md
deleted file mode 100644
index d47c2cec..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/LocationExtension.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## {{page-title}}
-
-{{tree:https://fhir.nhs.uk/StructureDefinition/LocationExtension, snapshot}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/toc.yaml
deleted file mode 100644
index 0afd4d94..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllExtensions/toc.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-- name: Index
- filename: Index.page.md
-- name: CDSS Extension
- filename: CDSSExtension.guide.md
-- name: Location Extension
- filename: LocationExtension.guide.md
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllProfiles/BARS-Flag-Scene-Safety.page.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllProfiles/BARS-Flag-Scene-Safety.page.md
deleted file mode 100644
index eea2adb7..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllProfiles/BARS-Flag-Scene-Safety.page.md
+++ /dev/null
@@ -1,28 +0,0 @@
-## {{page-title}}
-
-
Important: This page is under development by NHS Digital
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/Index.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/Index.guide.md
deleted file mode 100644
index 0248c13d..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/Index.guide.md
+++ /dev/null
@@ -1 +0,0 @@
-## {{page-title}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/toc.yaml
deleted file mode 100644
index a7d77953..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/AllValuesets/toc.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-- name: Index
- filename: Index-duplicate-2.guide.md
-- name: Index
- filename: Index.guide.md
-- name: All ValueSets
- filename: AllValueSets.guide.md
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/Index.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/Index.guide.md
deleted file mode 100644
index 9532a51d..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/Index.guide.md
+++ /dev/null
@@ -1,3 +0,0 @@
-### All Assets
-
-{{index:current}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/toc.yaml
deleted file mode 100644
index bbca32a0..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/AllAssets/toc.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-- name: Index
- filename: Index.guide.md
-- name: All Profiles
- filename: AllProfiles
-- name: All Valuesets
- filename: AllValuesets
-- name: All Extensions
- filename: AllExtensions
-- name: All CodeSystems
- filename: AllCodeSystems
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CapabilityStatements.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CapabilityStatements.guide.md
deleted file mode 100644
index c57f6632..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CapabilityStatements.guide.md
+++ /dev/null
@@ -1,5 +0,0 @@
-## CapabilityStatements
-
-A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server or Client for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
-
-{{xml:45bcbe62-718b-4874-a68c-b0fe39a76cf5}}
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CodeSystems.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CodeSystems.guide.md
deleted file mode 100644
index 8953b375..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/CodeSystems.guide.md
+++ /dev/null
@@ -1,82 +0,0 @@
-## CodeSystems
-
-### Workflow CodeSystems
-
-
-
Name
-
Description
-
-
-
{{pagelink:MessageEventsBARS}}
-
CodeSystem that drives the workflow for BARS MessageDefinition and MessageHeader
-
-
-
{{pagelink:MessageReasonBARS}}
-
CodeSystem that drives the workflow for BARS MessageHeader reasons
-
-
-
{{pagelink:MessageCategoryServiceRequest}}
-
CodeSystem that drives the workflow for BARS ServiceRequest category
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/Index.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/Index.guide.md
deleted file mode 100644
index 6cb235c0..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/Index.guide.md
+++ /dev/null
@@ -1,10 +0,0 @@
-
-## FHIR Assets
-
-
-This is a reference section providing information on a number of FHIR assests used by the booking and referral standard. The complete directory of FHIR assets can be found on the simplifier project page here
-
-{{index:current}}
-
-
-
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/MessageDefinition.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/MessageDefinition.guide.md
deleted file mode 100644
index c0e5d616..00000000
--- a/guides/Live-ImplementationGuide-BaRS/Home/FHIRAssets-bak/MessageDefinition.guide.md
+++ /dev/null
@@ -1,62 +0,0 @@
- ### Message Definition
-
-Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted.
-
-### ServiceRequest - Referral
-
-