-Once the appointment is cancelled, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.2, text: here}}.
\ No newline at end of file
+Once the appointment is cancelled, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.3, text: here}}.
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Index.page.md
index 1f276d0f..393bda4e 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Index.page.md
@@ -1,3 +1,3 @@
---
-topic: core-StandardPattern-appointment-1.2.2
+topic: core-StandardPattern-appointment-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Initial-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Initial-Booking.page.md
index 1f316cfd..fbf5b17b 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Initial-Booking.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Initial-Booking.page.md
@@ -1,5 +1,5 @@
---
-topic: core-StandardPattern-appointment-booking-1.2.2
+topic: core-StandardPattern-appointment-booking-1.2.3
---
## Appointment Resource
@@ -19,6 +19,6 @@ The method for the initial booking of an appointment depends on the {{pagelink:H
-Once the appointment is created, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.2, text: here}}.
+Once the appointment is created, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.3, text: here}}.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Introduction.page.md
index 806c54de..0ab37ab9 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: core-StandardPattern-appointment-Introduction-1.2.2
+topic: core-StandardPattern-appointment-Introduction-1.2.3
---
# Standard Pattern - Appointments
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Rebook-Methods.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Rebook-Methods.page.md
index 7b44b769..41995415 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Rebook-Methods.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Rebook-Methods.page.md
@@ -1,5 +1,5 @@
---
-topic: core-StandardPattern-appointment-rebook-1.2.2
+topic: core-StandardPattern-appointment-rebook-1.2.3
---
### Rebook
@@ -105,4 +105,4 @@ Using PATCH:
-Once the appointment is rebooked, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.2, text: here}}.
+Once the appointment is rebooked, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.3, text: here}}.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Update-Existing-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Update-Existing-Booking.page.md
index 10bab0f2..eb23575d 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Update-Existing-Booking.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Appointment-StandardPattern/Update-Existing-Booking.page.md
@@ -1,5 +1,5 @@
---
-topic: core-StandardPattern-appointment-update-1.2.2
+topic: core-StandardPattern-appointment-update-1.2.3
---
### Update
@@ -71,4 +71,4 @@ Request Body
```
-Once the appointment is updated, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.2, text: here}}.
+Once the appointment is updated, the Receiver is responsible for managing the pointer in the central Registry, as described {{pagelink:core-StandardPattern-document-reference-1.2.3, text: here}}.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Bundle.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Bundle.page.md
index b5d049ea..ef3f8889 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Bundle.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Bundle.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-bundle-1.2.2
+topic: core-FHIRUsage-bundle-1.2.3
---
## Bundle
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/FHIR-Operations-Framework.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/FHIR-Operations-Framework.page.md
index 945fde42..f09089ad 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/FHIR-Operations-Framework.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/FHIR-Operations-Framework.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-FHIR-Operations-1.2.2
+topic: core-FHIRUsage-FHIR-Operations-1.2.3
---
## FHIR Operations framework
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Frameworks.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Frameworks.page.md
index 58087e7f..e6dcd04a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Frameworks.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Frameworks.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-Framework-1.2.2
+topic: core-FHIRUsage-Framework-1.2.3
---
## Frameworks
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/How-to-handle-times.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/How-to-handle-times.page.md
index 23b786f1..c2ed61f6 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/How-to-handle-times.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/How-to-handle-times.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-Time-1.2.2
+topic: core-FHIRUsage-Time-1.2.3
---
## {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Index.page.md
index 68eaf0d0..063b601a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Index.page.md
@@ -1,4 +1,4 @@
---
-topic: core-FHIRUsage-1.2.2
+topic: core-FHIRUsage-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Introduction.page.md
index 08103c83..228820b9 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-Introduction-1.2.2
+topic: core-FHIRUsage-Introduction-1.2.3
---
# BaRS FHIR Usage
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Journey-ID.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Journey-ID.page.md
index 89035f9b..fa43c6d3 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Journey-ID.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/Journey-ID.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-JourneyID-1.2.2
+topic: core-FHIRUsage-JourneyID-1.2.3
---
## {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/LastUpdatedDate.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/LastUpdatedDate.page.md
index 072ebef0..aac1c92f 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/LastUpdatedDate.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/LastUpdatedDate.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-LastUpdated-1.2.2
+topic: core-FHIRUsage-LastUpdated-1.2.3
---
## {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/REST.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/REST.page.md
index 64add4af..902d2ba9 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/REST.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/REST.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-REST-1.2.2
+topic: core-FHIRUsage-REST-1.2.3
---
## REST
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/process-message.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/process-message.page.md
index 647990e7..c64419ab 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/process-message.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/BaRS-FHIR-Usage/process-message.page.md
@@ -1,5 +1,5 @@
---
-topic: core-FHIRUsage-Process-Message-1.2.2
+topic: core-FHIRUsage-Process-Message-1.2.3
---
## $process-message
@@ -14,7 +14,7 @@ The endpoint receives only POST requests of bundle type 'message', with the requ
You must implement a $process-message endpoint to be compliant with BaRS because it is used for initial requests (booking, service request etc.) but also for responses (validation outcome response etc.).
-Please see the {{pagelink:Core-StandardPattern-1.2.2, text: Standard Patterns}} for generic guidance for processing messages.
+Please see the {{pagelink:Core-StandardPattern-1.2.3, text: Standard Patterns}} for generic guidance for processing messages.
@@ -34,83 +34,83 @@ You will find here a set of documentation, specifications and services that desc
> Expand for full Core directory
-• {{pagelink:design-core-1.2.2 , text: Core 1.2.2}}
- • {{pagelink:core-EndToEndWorkflow-1.2.2 , text:End to end workflow}}
- • {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.2.2 , text:Service Discovery}}
- • {{pagelink:core-EndToEndWorkflow-BaRSAuth-1.2.2 , text:Authenticate with BaRS}}
- • {{pagelink:core-EndToEndWorkflow-API-1.2.2 , text:BaRS FHIR API}}
- • {{pagelink:core-EndToEndWorkflow-HTTPHeader-1.2.2 , text:HTTP Header}}
- • {{pagelink:core-EndToEndWorkflow-Routing-1.2.2 , text:Routing}}
- • {{pagelink:core-EndToEndWorkflow-Auth-1.2.2 , text:Authentication and Authorisation}}
- • {{pagelink:core-EndToEndWorkflow-Transactional-Integrity-1.2.2 , text:Transactional Integrity}}
- • {{pagelink:core-EndToEndWorkflow-HTTPResponseHeader-1.2.2 , text:HTTP Response Headers}}
- • {{pagelink:core-EndToEndWorkflow-Processing-1.2.2 , text:Processing Requests}}
- • {{pagelink:core-EndToEndWorkflow-Responses-1.2.2 , text:Responses}}
- • {{pagelink:core-EndToEndWorkflow-ReversingRoles-1.2.2 , text:Reversing Roles}}
- • {{pagelink:core-EndToEndWorkflow-AsyncWorkflow-1.2.2 , text:Asynchronous Workflow}}
- • {{pagelink:core-FunctionalityRequirements-1.2.2 , text:Core Functionality Requirements.}}
- • {{pagelink:core-FunctionalityRequirements-All-1.2.2 , text:All}}
- • {{pagelink:core-FunctionalityRequirements-Caching-1.2.2 , text:Caching}}
- • {{pagelink:core-FunctionalityRequirements-BookingSender-1.2.2 , text:Booking Sender}}
- • {{pagelink:core-FunctionalityRequirements-BookingReceiver-1.2.2 , text:Booking Receiver}}
- • {{pagelink:core-FunctionalityRequirements-ReferralSender-1.2.2 , text:Referral Sender}}
- • {{pagelink:core-FunctionalityRequirements-ReferralReceiver-1.2.2 , text:Referral Receiver}}
- • {{pagelink:core-FHIRUsage-1.2.2 , text:BaRS FHIR Usage}}
- • {{pagelink:core-FHIRUsage-Framework-1.2.2 , text:Frameworks}}
- • {{pagelink:core-FHIRUsage-REST-1.2.2 , text:REST}}
- • {{pagelink:core-FHIRUsage-FHIR-Operations-1.2.2 , text:FHIR Operations}}
- • {{pagelink:core-FHIRUsage-Process-Message-1.2.2 , text:$process-message}}
- • {{pagelink:core-FHIRUsage-bundle-1.2.2 , text:Bundle}}
- • {{pagelink:core-FHIRUsage-JourneyID-1.2.2 , text:Journey ID}}
- • {{pagelink:core-FHIRUsage-Time-1.2.2 , text:How to handle times}}
- • {{pagelink:core-FHIRUsage-LastUpdated-1.2.2 , text:LastUpdatedDate}}
- • {{pagelink:core-Security-1.2.2 , text:Security and Authorisation}}
- • {{pagelink:core-Security-Sender-1.2.2 , text:Sender}}
- • {{pagelink:core-Security-Oauth-1.2.2 , text:OAuth Endpoints}}
- • {{pagelink:core-Security-Receiver-1.2.2 , text:Receiver}}
- • {{pagelink:core-Security-Auth-1.2.2 , text:Authorisation}}
- • {{pagelink:core-ErrorHandling-1.2.2 , text:Error Handling}}
- • {{pagelink:core-ErrorHandling-Overview-1.2.2 , text:Overview}}
- • {{pagelink:core-ErrorHandling-IntS-1.2.2 , text:BaRS interactions(sending)}}
- • {{pagelink:core-ErrorHandling-OpOut-1.2.2 , text:OperationOutcome Example}}
- • {{pagelink:core-ErrorHandling-Diag-1.2.2 , text:Diagnostic Text}}
- • {{pagelink:core-ErrorHandling-Examples-1.2.2 , text:Example Errors}}
- • {{pagelink:core-ErrorHandling-SendResp-1.2.2 , text:Sender Responsibilities}}
- • {{pagelink:core-ErrorHandling-IntR-1.2.2 , text:BaRs interactions(receiving)}}
- • {{pagelink:core-ErrorHandling-RecResp-1.2.2 , text:Receiver responsibilities}}
- • {{pagelink:core-failure_scenarios-1.2.2 , text:Failure Scenarios}}
- • {{pagelink:Core-TransactionalIntegrity-1.2.2 , text:Transactional Integrity}}
- • {{pagelink:Core-TransactionalIntegrity-Initial-1.2.2 , text:Initial Request}}
- • {{pagelink:Core-TransactionalIntegrity-Update-1.2.2 , text:Sending an update}}
- • {{pagelink:Core-TransactionalIntegrity-Feedback-1.2.2 , text:Feedback (response) requests}}
- • {{pagelink:Core-TransactionalIntegrity-Retry-1.2.2 , text:Retry Scenario}}
- • {{pagelink:Core-TransactionalIntegrity-Onward-1.2.2 , text:Onwards Referrals}}
- • {{pagelink:Core-TransactionalIntegrity-retry-1.2.2 , text:Definition of a Retry}}
- • {{pagelink:Core-TransactionalIntegrity-Receiver-1.2.2 , text:Receiver responsibilities}}
- • {{pagelink:Core-TransactionalIntegrity-Sender-1.2.2 , text:Sender responsibilities}}
- • {{pagelink:core-TIFailureScenarios-1.2.2 , text:Failure Scenarios}}
- • {{pagelink:core-NFR-1.2.2 , text:Non functional Requirements}}
- • {{pagelink:core-NFR-Requirements-1.2.2 , text:Requirements}}
- • {{pagelink:core-NFR-Processing-Time-1.2.2 , text:Processing Times}}
- • {{pagelink:Core-StandardPattern-1.2.2 , text:Standard Pattern - Composite Messages}}
- • {{pagelink:core-SPComposites-1.2.2 , text:Standard Pattern for Composites}}
- • {{pagelink:core-SPMessageHeader-1.2.2 , text:Message Headers}}
- • {{pagelink:core-SPCancellation-1.2.2 , text:Cancellation}}
- • {{pagelink:core-SPUseCaseCategories-1.2.2 , text:Use Case Categories}}
- • {{pagelink:core-StandardPattern-appointment-1.2.2 , text:Standard Pattern - Appointments}}
- • {{pagelink:core-StandardPattern-appointment-booking-1.2.2 , text:Booking}}
- • {{pagelink:core-StandardPattern-appointment-update-1.2.2 , text:Updates}}
- • {{pagelink:core-StandardPattern-appointment-cancel-1.2.2 , text:Cancellations}}
- • {{pagelink:core-StandardPattern-appointment-rebook-1.2.2 , text:Rebook}}
- • {{pagelink:core-StandardPattern-document-reference-1.2.2 , text:Standard Pattern - DocumentReference}}
- • {{pagelink:core-StandardPattern-document-reference-Sender-1.2.2 , text:Sender}}
- • {{pagelink:core-StandardPattern-document-reference-Receiver-1.2.2 , text:Receiver}}
- • {{pagelink:core-StandardPattern-document-reference-interface-1.2.2 , text:Interface}}
- • {{core-StandardPattern-Endpoints-1.2.2 , text:Standard Pattern - Endpoints}}
- • {{pagelink:core-StandardPattern-Endpoint-Introduction-1.2.2 , text:Introduction}}
- • {{pagelink:core-StandardPattern-Endpoint-Interface-1.2.2 , text:Interface}}
- • {{core-StandardPattern-Endpoint-Data-1.2.2 , text:Data Model}}
- • {{pagelink:core-StandardPattern-Endpoint-Sequences-1.2.2 , text:Sequences}}
+• {{pagelink:design-core-1.2.3 , text: Core 1.2.2}}
+ • {{pagelink:core-EndToEndWorkflow-1.2.3 , text:End to end workflow}}
+ • {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.2.3 , text:Service Discovery}}
+ • {{pagelink:core-EndToEndWorkflow-BaRSAuth-1.2.3 , text:Authenticate with BaRS}}
+ • {{pagelink:core-EndToEndWorkflow-API-1.2.3 , text:BaRS FHIR API}}
+ • {{pagelink:core-EndToEndWorkflow-HTTPHeader-1.2.3 , text:HTTP Header}}
+ • {{pagelink:core-EndToEndWorkflow-Routing-1.2.3 , text:Routing}}
+ • {{pagelink:core-EndToEndWorkflow-Auth-1.2.3 , text:Authentication and Authorisation}}
+ • {{pagelink:core-EndToEndWorkflow-Transactional-Integrity-1.2.3 , text:Transactional Integrity}}
+ • {{pagelink:core-EndToEndWorkflow-HTTPResponseHeader-1.2.3 , text:HTTP Response Headers}}
+ • {{pagelink:core-EndToEndWorkflow-Processing-1.2.3 , text:Processing Requests}}
+ • {{pagelink:core-EndToEndWorkflow-Responses-1.2.3 , text:Responses}}
+ • {{pagelink:core-EndToEndWorkflow-ReversingRoles-1.2.3 , text:Reversing Roles}}
+ • {{pagelink:core-EndToEndWorkflow-AsyncWorkflow-1.2.3 , text:Asynchronous Workflow}}
+ • {{pagelink:core-FunctionalityRequirements-1.2.3 , text:Core Functionality Requirements.}}
+ • {{pagelink:core-FunctionalityRequirements-All-1.2.3 , text:All}}
+ • {{pagelink:core-FunctionalityRequirements-Caching-1.2.3 , text:Caching}}
+ • {{pagelink:core-FunctionalityRequirements-BookingSender-1.2.3 , text:Booking Sender}}
+ • {{pagelink:core-FunctionalityRequirements-BookingReceiver-1.2.3 , text:Booking Receiver}}
+ • {{pagelink:core-FunctionalityRequirements-ReferralSender-1.2.3 , text:Referral Sender}}
+ • {{pagelink:core-FunctionalityRequirements-ReferralReceiver-1.2.3 , text:Referral Receiver}}
+ • {{pagelink:core-FHIRUsage-1.2.3 , text:BaRS FHIR Usage}}
+ • {{pagelink:core-FHIRUsage-Framework-1.2.3 , text:Frameworks}}
+ • {{pagelink:core-FHIRUsage-REST-1.2.3 , text:REST}}
+ • {{pagelink:core-FHIRUsage-FHIR-Operations-1.2.3 , text:FHIR Operations}}
+ • {{pagelink:core-FHIRUsage-Process-Message-1.2.3 , text:$process-message}}
+ • {{pagelink:core-FHIRUsage-bundle-1.2.3 , text:Bundle}}
+ • {{pagelink:core-FHIRUsage-JourneyID-1.2.3 , text:Journey ID}}
+ • {{pagelink:core-FHIRUsage-Time-1.2.3 , text:How to handle times}}
+ • {{pagelink:core-FHIRUsage-LastUpdated-1.2.3 , text:LastUpdatedDate}}
+ • {{pagelink:core-Security-1.2.3 , text:Security and Authorisation}}
+ • {{pagelink:core-Security-Sender-1.2.3 , text:Sender}}
+ • {{pagelink:core-Security-Oauth-1.2.3 , text:OAuth Endpoints}}
+ • {{pagelink:core-Security-Receiver-1.2.3 , text:Receiver}}
+ • {{pagelink:core-Security-Auth-1.2.3 , text:Authorisation}}
+ • {{pagelink:core-ErrorHandling-1.2.3 , text:Error Handling}}
+ • {{pagelink:core-ErrorHandling-Overview-1.2.3 , text:Overview}}
+ • {{pagelink:core-ErrorHandling-IntS-1.2.3 , text:BaRS interactions(sending)}}
+ • {{pagelink:core-ErrorHandling-OpOut-1.2.3 , text:OperationOutcome Example}}
+ • {{pagelink:core-ErrorHandling-Diag-1.2.3 , text:Diagnostic Text}}
+ • {{pagelink:core-ErrorHandling-Examples-1.2.3 , text:Example Errors}}
+ • {{pagelink:core-ErrorHandling-SendResp-1.2.3 , text:Sender Responsibilities}}
+ • {{pagelink:core-ErrorHandling-IntR-1.2.3 , text:BaRs interactions(receiving)}}
+ • {{pagelink:core-ErrorHandling-RecResp-1.2.3 , text:Receiver responsibilities}}
+ • {{pagelink:core-failure_scenarios-1.2.3 , text:Failure Scenarios}}
+ • {{pagelink:Core-TransactionalIntegrity-1.2.3 , text:Transactional Integrity}}
+ • {{pagelink:Core-TransactionalIntegrity-Initial-1.2.3 , text:Initial Request}}
+ • {{pagelink:Core-TransactionalIntegrity-Update-1.2.3 , text:Sending an update}}
+ • {{pagelink:Core-TransactionalIntegrity-Feedback-1.2.3 , text:Feedback (response) requests}}
+ • {{pagelink:Core-TransactionalIntegrity-Retry-1.2.3 , text:Retry Scenario}}
+ • {{pagelink:Core-TransactionalIntegrity-Onward-1.2.3 , text:Onwards Referrals}}
+ • {{pagelink:Core-TransactionalIntegrity-retry-1.2.3 , text:Definition of a Retry}}
+ • {{pagelink:Core-TransactionalIntegrity-Receiver-1.2.3 , text:Receiver responsibilities}}
+ • {{pagelink:Core-TransactionalIntegrity-Sender-1.2.3 , text:Sender responsibilities}}
+ • {{pagelink:core-TIFailureScenarios-1.2.3 , text:Failure Scenarios}}
+ • {{pagelink:core-NFR-1.2.3 , text:Non functional Requirements}}
+ • {{pagelink:core-NFR-Requirements-1.2.3 , text:Requirements}}
+ • {{pagelink:core-NFR-Processing-Time-1.2.3 , text:Processing Times}}
+ • {{pagelink:Core-StandardPattern-1.2.3 , text:Standard Pattern - Composite Messages}}
+ • {{pagelink:core-SPComposites-1.2.3 , text:Standard Pattern for Composites}}
+ • {{pagelink:core-SPMessageHeader-1.2.3 , text:Message Headers}}
+ • {{pagelink:core-SPCancellation-1.2.3 , text:Cancellation}}
+ • {{pagelink:core-SPUseCaseCategories-1.2.3 , text:Use Case Categories}}
+ • {{pagelink:core-StandardPattern-appointment-1.2.3 , text:Standard Pattern - Appointments}}
+ • {{pagelink:core-StandardPattern-appointment-booking-1.2.3 , text:Booking}}
+ • {{pagelink:core-StandardPattern-appointment-update-1.2.3 , text:Updates}}
+ • {{pagelink:core-StandardPattern-appointment-cancel-1.2.3 , text:Cancellations}}
+ • {{pagelink:core-StandardPattern-appointment-rebook-1.2.3 , text:Rebook}}
+ • {{pagelink:core-StandardPattern-document-reference-1.2.3 , text:Standard Pattern - DocumentReference}}
+ • {{pagelink:core-StandardPattern-document-reference-Sender-1.2.3 , text:Sender}}
+ • {{pagelink:core-StandardPattern-document-reference-Receiver-1.2.3 , text:Receiver}}
+ • {{pagelink:core-StandardPattern-document-reference-interface-1.2.3 , text:Interface}}
+ • {{core-StandardPattern-Endpoints-1.2.3 , text:Standard Pattern - Endpoints}}
+ • {{pagelink:core-StandardPattern-Endpoint-Introduction-1.2.3 , text:Introduction}}
+ • {{pagelink:core-StandardPattern-Endpoint-Interface-1.2.3 , text:Interface}}
+ • {{core-StandardPattern-Endpoint-Data-1.2.3 , text:Data Model}}
+ • {{pagelink:core-StandardPattern-Endpoint-Sequences-1.2.3 , text:Sequences}}
@@ -130,7 +130,7 @@ This section covers the core elements of workflow outlined within the Booking an
- refer without booking
- book without referring
-For more detail please visit the {{pagelink:core-EndToEndWorkflow-1.2.2, text: End to End Workflow}} section.
+For more detail please visit the {{pagelink:core-EndToEndWorkflow-1.2.3, text: End to End Workflow}} section.
@@ -147,7 +147,7 @@ This list of functionality will expand in later versions of BaRS.
There are requirements in each of the central areas of functionality which every BaRS Application must adopt:
-For more detail please visit the {{pagelink:core-FunctionalityRequirements-1.2.2, text: Core Functionality Requirements}} section.
+For more detail please visit the {{pagelink:core-FunctionalityRequirements-1.2.3, text: Core Functionality Requirements}} section.
@@ -164,22 +164,22 @@ For more detail please visit the {{pagelink:core-content-negotiation, text: Cont
# BaRS FHIR usage
BaRS uses [FHIR](https://digital.nhs.uk/services/fhir-uk-core) to achieve interoperability between healthcare IT systems. This section explains how BaRS makes use of some key FHIR concepts which need to be understood by developers implementing the standard.
-For more detail please visit the {{pagelink:core-FHIRUsage-1.2.2, text: BaRS FHIR usage}} section.
+For more detail please visit the {{pagelink:core-FHIRUsage-1.2.3, text: BaRS FHIR usage}} section.
# Security and Authorisation
-For more detail on Security and Authorisation, please visit the {{pagelink:core-Security-1.2.2, text: Security and Authorisation}} section.
+For more detail on Security and Authorisation, please visit the {{pagelink:core-Security-1.2.3, text: Security and Authorisation}} section.
# Error Handling
-There are multiple points where an error may occur to prevent booking and referral operations from completing successfully. This section provides error handling guidance for BaRS and its associated API. For More Detail on error handling, there is specific information on failure scenarios available in the {{pagelink:core-failure_scenarios-1.2.2}} section in addition to information included on this page.
+There are multiple points where an error may occur to prevent booking and referral operations from completing successfully. This section provides error handling guidance for BaRS and its associated API. For More Detail on error handling, there is specific information on failure scenarios available in the {{pagelink:core-failure_scenarios-1.2.3}} section in addition to information included on this page.
-For more detail please visit the {{pagelink:core-ErrorHandling-1.2.2, text: Error Handling}} section.
+For more detail please visit the {{pagelink:core-ErrorHandling-1.2.3, text: Error Handling}} section.
@@ -187,7 +187,7 @@ For more detail please visit the {{pagelink:core-ErrorHandling-1.2.2, text: Erro
# Transactional Integrity
Transactional integrity is employed to ensure data integrity is maintained between two parties. It helps ensure that the success or failure of a message is known and can be confirmed.
-For more detail please visit the {{pagelink:Core-TransactionalIntegrity-1.2.2, text:Transactional Integrity}} section.
+For more detail please visit the {{pagelink:Core-TransactionalIntegrity-1.2.3, text:Transactional Integrity}} section.
@@ -196,7 +196,7 @@ For more detail please visit the {{pagelink:Core-TransactionalIntegrity-1.2.2, t
The non functional requirements apply to all APIs designed to receive requests from BaRS. This includes sender systems receiving asynchronous responses and feedback, as well as receiving systems. All items detailed will be adhered to.
-For more detail please visit the {{pagelink:core-NFR-1.2.2, text: Non Functional Requirements}} section.
+For more detail please visit the {{pagelink:core-NFR-1.2.3, text: Non Functional Requirements}} section.
@@ -206,7 +206,7 @@ Most implementations of the BaRS that are applying the standard to support a par
In order to establish a guarantee of compatibility between different solutions compliant with the standard, **all** implementations **must** support all the underlying foundational operations and patterns.
-For more detail please visit the {{pagelink:Core-StandardPattern-1.2.2, text: Standard Pattern - Composite Messages}} section.
+For more detail please visit the {{pagelink:Core-StandardPattern-1.2.3, text: Standard Pattern - Composite Messages}} section.
@@ -220,7 +220,7 @@ There are 4 capabilities that are required surrounding appointments. This sectio
* The ability to update an appointment.
* The ability to rebook an appointment.
-For more detail please visit the {{pagelink:core-StandardPattern-appointment-1.2.2, text: Appointment Standard Pattern}} section.
+For more detail please visit the {{pagelink:core-StandardPattern-appointment-1.2.3, text: Appointment Standard Pattern}} section.
@@ -231,7 +231,7 @@ In version 1.1.0 of the BaRS API Specification, functionality was added to accom
The FHIR DocumentReference resource allows you to reference and locate clinical documents or resources. This section will walk you through the process of using a FHIR DocumentReference to find a resource's location and retrieve it.
-For more detail please visit the {{pagelink:core-StandardPattern-document-reference-1.2.2, text: DocumentReference Standard Pattern}} section.
+For more detail please visit the {{pagelink:core-StandardPattern-document-reference-1.2.3, text: DocumentReference Standard Pattern}} section.
@@ -253,7 +253,7 @@ The BaRS endpoints will utilise not only service ids and a physical endpoint, bu
BaRS will expose an interface to manage this information in the format of FHIR resources. Each resource will have a corresponding endpoint on the Proxy to assist in managing these endpoints.
-For more detail please visit the {{pagelink:core-StandardPattern-Endpoints-1.2.2, text: Endpoint Standard Pattern}} section.
+For more detail please visit the {{pagelink:core-StandardPattern-Endpoints-1.2.3, text: Endpoint Standard Pattern}} section.
\ No newline at end of file
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Index.page.md
index ad239bdc..42455972 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Index.page.md
@@ -1,4 +1,4 @@
---
-topic: core-NFR-1.2.2
+topic: core-NFR-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Introduction.page.md
index 16b3e66e..6ff29951 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: core-NFR-Introduction-1.2.2
+topic: core-NFR-Introduction-1.2.3
---
## Non-Functional Requirements
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Processing-Times.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Processing-Times.page.md
index f5a3b5c1..b1e98da0 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Processing-Times.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Processing-Times.page.md
@@ -1,5 +1,5 @@
---
-topic: core-NFR-Processing-Time-1.2.2
+topic: core-NFR-Processing-Time-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Requirements.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Requirements.page.md
index 0fe56c28..6d6bd404 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Requirements.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Non-Functional-Requirements/Requirements.page.md
@@ -1,5 +1,5 @@
---
-topic: core-NFR-Requirements-1.2.2
+topic: core-NFR-Requirements-1.2.3
---
## {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Authorisation.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Authorisation.page.md
index 3bee358d..5c98fd46 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Authorisation.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Authorisation.page.md
@@ -1,5 +1,5 @@
---
-topic: core-Security-Auth-1.2.2
+topic: core-Security-Auth-1.2.3
---
## Authorisation
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Index.page.md
index c22c91f9..5414b288 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Index.page.md
@@ -1,4 +1,4 @@
---
-topic: core-Security-1.2.2
+topic: core-Security-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Introduction.page.md
index f8e3c458..4fc30dc8 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: core-Security-Introduction-1.2.2
+topic: core-Security-Introduction-1.2.3
---
# Security and Authorisation
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/OAuth-Endpoints.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/OAuth-Endpoints.page.md
index 61b004d4..c9010be1 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/OAuth-Endpoints.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/OAuth-Endpoints.page.md
@@ -1,5 +1,5 @@
---
-topic: core-Security-Oauth-1.2.2
+topic: core-Security-Oauth-1.2.3
---
## OAuth Endpoints
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Receiver.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Receiver.page.md
index e2bb6882..36c8d6f0 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Receiver.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Receiver.page.md
@@ -1,5 +1,5 @@
---
-topic: core-Security-Receiver-1.2.2
+topic: core-Security-Receiver-1.2.3
---
## Receiver
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Sender.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Sender.page.md
index 3a030525..9627e591 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Sender.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Security-and-Authorisation/Sender.page.md
@@ -1,5 +1,5 @@
---
-topic: core-Security-Sender-1.2.2
+topic: core-Security-Sender-1.2.3
---
## Sender
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Cancellation.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Cancellation.page.md
index 472de3eb..67ffbecc 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Cancellation.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Cancellation.page.md
@@ -1,5 +1,5 @@
---
-topic: core-SPCancellation-1.2.2
+topic: core-SPCancellation-1.2.3
---
@@ -9,12 +9,12 @@ The ability to reverse a digital request, by performing a cancellation, whether
Cancellation, for any referral type or booking, is a stripped back request, containing only the specific resources a Receiver requires to the fulfil the request. There are separate MessageDefinitions involved when engaged in [referral](https://simplifier.net/nhsbookingandreferrals/messagedefinition-barsmessagedefinitionservicerequestrequestcancelled/~json) and [booking](https://simplifier.net/NHSBookingandReferrals/MessageDefinition-BARSMessageDefinitionBookingRequestCancelled/~json) cancellation workflows.
-A prerequisite when performing a cancellation of any request is to perform a read (GET) of either the booking or referral to be cancelled. The Sender **must** only make a cancellation request if the entity has a status which means it is still current; 'active' in the case of a referral (ServiceRequest) and 'booked' for a booking (Appointment). This ensures the Sender has the latest version of the entity they are about to change or, if it is no longer current (because its been actioned by the Receiver), allows the Sender to advise the end user so an alternative (often manual) workflow can be started. The Receiver **must not** process a cancellation request for a booking or referral which is not current, instead they **must** return an appropriate {{pagelink:core-ErrorHandling-1.2.2, text:error}} response.
+A prerequisite when performing a cancellation of any request is to perform a read (GET) of either the booking or referral to be cancelled. The Sender **must** only make a cancellation request if the entity has a status which means it is still current; 'active' in the case of a referral (ServiceRequest) and 'booked' for a booking (Appointment). This ensures the Sender has the latest version of the entity they are about to change or, if it is no longer current (because its been actioned by the Receiver), allows the Sender to advise the end user so an alternative (often manual) workflow can be started. The Receiver **must not** process a cancellation request for a booking or referral which is not current, instead they **must** return an appropriate {{pagelink:core-ErrorHandling-1.2.3, text:error}} response.
## Cancellation Referral Request Payload
### MessageHeader Resource
-{{pagelink:core-SPMessageHeader-1.2.2, text:Standard Patterns for BaRS Operations}} explains in detail how the **MessageHeader** resource **must** be used.
+{{pagelink:core-SPMessageHeader-1.2.3, text:Standard Patterns for BaRS Operations}} explains in detail how the **MessageHeader** resource **must** be used.
When cancelling a referral, in conjunction with the guidance provided under the Standard Patterns, the four important elements which drive workflow **must** be used as follows:
* **eventCoding** - this **must** be the same code as used in the request.
@@ -286,7 +286,7 @@ The below diagram details the Cancellation Referral Request
## Cancellation Booking Request Payload
### MessageHeader Resource
-{{pagelink:core-SPMessageHeader-1.2.2, text:Standard Patterns for BaRS Operations}} explains in detail how the **MessageHeader** resource **must** be used.
+{{pagelink:core-SPMessageHeader-1.2.3, text:Standard Patterns for BaRS Operations}} explains in detail how the **MessageHeader** resource **must** be used.
When cancelling a booking, in conjunction with the guidance provided under the Standard Patterns, the three important elements which drive workflow **must** be used as follows:
* **eventCoding** - this **must** be the same code as used in the request.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Introduction.page.md
index e6c60901..4b3b5431 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-StandardPattern-Introduction-1.2.2
+topic: Core-StandardPattern-Introduction-1.2.3
---
## Standard Pattern - Composite Messages
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Message-Headers.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Message-Headers.page.md
index 845b8c14..dfd9124e 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Message-Headers.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Message-Headers.page.md
@@ -1,5 +1,5 @@
---
-topic: core-SPMessageHeader-1.2.2
+topic: core-SPMessageHeader-1.2.3
---
# {{page-title}}
@@ -20,7 +20,7 @@ When a Receiver begins to process the payload, they **must** initially ensure it
* check the **MessageHeader.destination.endpoint** is the Service ID they are expected to be processing the request on behalf of.
* Store **MessageHeader.source.endpoint** as NHSD-Target-Identifier to enable an asynchronous response back to the Sender. Not all workflows will require this type of response but this data must be stored for audit purposes.
-Certain elements in MessageHeader explicitly drive workflow, check **MessageHeader.eventCoding** to determine whether a booking or referral payload is being sent, and whether this is an initial or update request or an asynchronous response to a pre-existing request. There are various styles of referral too, a request could be made for a simple 'transfer of care' or, currently, something termed a 'validation', where one service requests another to validate the assessment outcome they have reached. The intention of supporting gradation of referral is to provide BaRS the malleability to support further subtlety of referrals for future use cases. Combining the **MessageHeader.eventCoding** with the **ServiceRequest.cateory** provides this functionality and, with the addition of {{pagelink:core-SPUseCaseCategories-1.2.2, text:use-case categories}} (again populated under **ServiceRequest.category**) specific services are pinpointed through every BaRS workflow.
+Certain elements in MessageHeader explicitly drive workflow, check **MessageHeader.eventCoding** to determine whether a booking or referral payload is being sent, and whether this is an initial or update request or an asynchronous response to a pre-existing request. There are various styles of referral too, a request could be made for a simple 'transfer of care' or, currently, something termed a 'validation', where one service requests another to validate the assessment outcome they have reached. The intention of supporting gradation of referral is to provide BaRS the malleability to support further subtlety of referrals for future use cases. Combining the **MessageHeader.eventCoding** with the **ServiceRequest.cateory** provides this functionality and, with the addition of {{pagelink:core-SPUseCaseCategories-1.2.3, text:use-case categories}} (again populated under **ServiceRequest.category**) specific services are pinpointed through every BaRS workflow.
Once the above checks have been made, the detail of the payload can start to be unpacked and processed. The structure of the payload **must** be checked first to ensure it adheres to the **MessageHeader.definition** it claims to. The [MessageDefinitions](https://simplifier.net/nhsbookingandreferrals/~resources?category=Example&exampletype=MessageDefinition&sortBy=DisplayName) will principally be defined by BaRS, at a national level (although bespoke definitions can be used through BaRS), and the Receiver is checking to ensure all mandatory FHIR resources are present and meet their assigned cardinality. This is a manual, business logic, check and not something which is supported through standard FHIR validation of the payload (bundle).
Next, **MessageHeader.focus** is the root resource through which the payload is intended to be understood. In an initial referral request, this will typically be the **ServiceRequest** FHIR resource. This root will link to other resources to build a narrative for the payload, for example, the **ServiceRequest** will link to the **Encounter** which led to the referral being made and the **Careplan** detailing next actions. The Entity Relationship Diagrams (included in each {{pagelink:Home/Applications/BaRS-Applications/Applications, text:Application}}) are used as a visual representation of the FHIR resource links in the payloads.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Standard-Pattern-For-Composites.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Standard-Pattern-For-Composites.page.md
index 902a0151..9971815a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Standard-Pattern-For-Composites.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Standard-Pattern-For-Composites.page.md
@@ -1,5 +1,5 @@
---
-topic: core-SPComposites-1.2.2
+topic: core-SPComposites-1.2.3
---
## {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md
index 8ec0251d..2ff4fa2a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md
@@ -1,5 +1,5 @@
---
-topic: core-SPUseCaseCategories-1.2.2
+topic: core-SPUseCaseCategories-1.2.3
---
# {{page-title}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/index.page.md
index ee9f49ee..189b44ad 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Standard-Pattern-Composite-Messages/index.page.md
@@ -1,3 +1,3 @@
---
-topic: Core-StandardPattern-1.2.2
+topic: Core-StandardPattern-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Definition-of-a-retry.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Definition-of-a-retry.page.md
index 644e32f8..746d19f1 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Definition-of-a-retry.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Definition-of-a-retry.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-retry-1.2.2
+topic: Core-TransactionalIntegrity-retry-1.2.3
---
## Definition of a retry
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Failure-Scenarios.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Failure-Scenarios.page.md
index ee12eed4..ee2eb826 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Failure-Scenarios.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Failure-Scenarios.page.md
@@ -1,5 +1,5 @@
---
-topic: core-TIFailureScenarios-1.2.2
+topic: core-TIFailureScenarios-1.2.3
---
## Failure Scenarios
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Feedback--response--requests.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Feedback--response--requests.page.md
index b04445db..d996dd8b 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Feedback--response--requests.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Feedback--response--requests.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Feedback-1.2.2
+topic: Core-TransactionalIntegrity-Feedback-1.2.3
---
## Feedback (response) requests
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Index.page.md
index cf67bcf7..09b5156f 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Index.page.md
@@ -1,3 +1,3 @@
---
-topic: Core-TransactionalIntegrity-1.2.2
+topic: Core-TransactionalIntegrity-1.2.3
---
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Initial-Request.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Initial-Request.page.md
index 9f79ab44..31924b68 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Initial-Request.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Initial-Request.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Initial-1.2.2
+topic: Core-TransactionalIntegrity-Initial-1.2.3
---
## Initial Request
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Introduction.page.md
index 38fff3db..e3b629dc 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Introduction.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Introduction.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Introduction-1.2.2
+topic: Core-TransactionalIntegrity-Introduction-1.2.3
---
## Transactional Integrity
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Onwards-Referrals.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Onwards-Referrals.page.md
index da4f4ee2..a3c9ae47 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Onwards-Referrals.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Onwards-Referrals.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Onward-1.2.2
+topic: Core-TransactionalIntegrity-Onward-1.2.3
---
## Onward Referrals
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Receiver-responsibilities.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Receiver-responsibilities.page.md
index ec695964..11a615f9 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Receiver-responsibilities.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Receiver-responsibilities.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Receiver-1.2.2
+topic: Core-TransactionalIntegrity-Receiver-1.2.3
---
## Receiver responsibilities
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Retry-Scenario.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Retry-Scenario.page.md
index 61fdba05..66e34fe0 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Retry-Scenario.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Retry-Scenario.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Retry-1.2.2
+topic: Core-TransactionalIntegrity-Retry-1.2.3
---
## Retry scenario
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sender-responsibilities.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sender-responsibilities.page.md
index 38a7c57a..ecffdfd7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sender-responsibilities.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sender-responsibilities.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Sender-1.2.2
+topic: Core-TransactionalIntegrity-Sender-1.2.3
---
## Sender responsibilities
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sending-an-update.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sending-an-update.page.md
index 40888a6d..b0a5d117 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sending-an-update.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.3/Transactional-integrity/Sending-an-update.page.md
@@ -1,5 +1,5 @@
---
-topic: Core-TransactionalIntegrity-Update-1.2.2
+topic: Core-TransactionalIntegrity-Update-1.2.3
---
## Sending an update