-
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
+
+
+
+
-
+
+
+
+
+
+
+
+
+
+
+
-
+
+
+
+
+
-
+
In addition to that the specific workflow parameters that are required are as follows:
@@ -102,15 +102,11 @@ X-Correlation-Id =
In addition to that the specific workflow parameters that are required are as follows:
@@ -190,15 +190,11 @@ X-Correlation-Id = 111 - ED 111 Online - ED | 1.0.7 | v1.0.0 | v1.0.0 |
-| {{pagelink:application3, text: Referral into UEC (Application 3)}} | 999-CAS Referral 999-CAS Validation 999 AST to Falls Lifting Service 999 AST to Community Services Primary Care to Community Pharmacy (Pharmacy First) Primary Care to Pharmacy Contraception (Oral Contraception) Primary Care to Pharmacy Blood Pressure Check Service 111 - ED 111 Online - ED | 1.0.8 | v1.0.0 | v1.0.0 |
+| {{pagelink:application3, text: Referral into UEC (Application 3)}} | 999-CAS Referral 999-CAS Validation 999 AST to Falls Lifting Service 999 AST to Community Services Primary Care to Community Pharmacy (Pharmacy First) Primary Care to Pharmacy Contraception (Oral Contraception) Primary Care to Pharmacy Blood Pressure Check Service CAD to CAD Out of Area Referral Appointments for Patient facing services into GP Practice | 1.0.0-alpha.3 | API Spec v1.1.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.1.0 and above}} |
+| {{pagelink:application6, text: Referrals into an Ambulance Service Trust (Application 6)}} | CAD to CAD Out of Area Referral Appointments for Patient facing services into GP Practice | 1.0.0-alpha.4 | API Spec v1.1.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.1.0 and above}} |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Cancellation.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Cancellation.page.md
index 6e9a88e2..55c98fb7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Cancellation.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Cancellation.page.md
@@ -57,7 +57,7 @@ This payload is used to transmit all the necessary information that is required
| Bundle | The Bundle resource is the container for the event message https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
-| Bundle.meta.versionId | | MUST | 1..1 | |
+| Bundle.meta.versionId | | MUST | 0..1 | |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/End-to-end-workflow/Logging.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/End-to-end-workflow/Logging.page.md
index f82ac3f8..b7bc0ed6 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/End-to-end-workflow/Logging.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/End-to-end-workflow/Logging.page.md
@@ -22,7 +22,7 @@ The elements for a ServiceRequest are:
The elements for an Appointment are:
-* Appointent.serviceCategory.coding (usecases-categories-bars)
+* Appointment.serviceCategory.coding (usecases-categories-bars)
* Appointment.status
* MessageHeader.eventCoding.code (message-event-bars)
* MessageHeader.reason.coding.code (message-reason-bars)
@@ -42,7 +42,7 @@ Example:
### Booking
```
- Appointent.serviceCategory.coding[usecases-categories-bars] | Appointment.status | MessageHeader.eventCoding.code | MessageHeader.reason.coding.code
+ Appointment.serviceCategory.coding[usecases-categories-bars] | Appointment.status | MessageHeader.eventCoding.code | MessageHeader.reason.coding.code
```
Example:
```
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Index.page.md
index f5de480d..25dc3dac 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Index.page.md
@@ -11,7 +11,7 @@ You will find here a set of documentation, specifications and services that desc
-
-This version of core is strictly a preview of what is currently in development for 1.2.2-alpha and should not be built against.
-
-This version of core is strictly a preview of what is currently in development for 1.2.0 and should not be built against.
+This version of core is strictly a preview of what is currently in development for 1.3.0 and should not be built against.
+The below diagram details the options for obtaining the booking (Appointment) or referral (ServiceRequest) resource, prior to cancellation. The Sender must know the (resource).status and (resource).id values, as minimum, to build a valid cancellation request.
+
@@ -142,15 +142,11 @@ X-Correlation-Id =
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Request-Payload.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Request-Payload.page.md
index e73dae8b..17a8c412 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Request-Payload.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Request-Payload.page.md
@@ -30,7 +30,7 @@ This payload is used to transmit all the necessary information that is required
| Bundle | https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
-| Bundle.meta.versionId | | MUST | 1..1 | |
+| Bundle.meta.versionId | This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing. | MUST | 0..1 | 1.0.0-beta |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Response-Payload.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Response-Payload.page.md
index 2a3a6db5..fc264548 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Response-Payload.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Validation-Response-Payload.page.md
@@ -30,7 +30,7 @@ This payload is used to transmit the outcome of the validation assessment back t
| Bundle | https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
-| Bundle.meta.versionId | | MUST | 1..1 | |
+| Bundle.meta.versionId | This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing. | MUST | 0..1 | 1.0.0-beta |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/How-does-it-work.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/How-does-it-work.page.md
index 9de967c0..e59a6f3e 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/How-does-it-work.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/How-does-it-work.page.md
@@ -164,7 +164,7 @@ When a service is chosen, the "Service ID" field in the DOS data will be used as
Making a referral for this application follows the {{pagelink:core-standardpattern-1.3.0, text:standard pattern for BaRS operations}}.
-The message definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
+The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
@@ -236,15 +236,11 @@ X-Correlation-Id =
-To cancel a booking this Application follows the {{pagelink:core-standardpattern-1.3.0, text:standard pattern for BaRS operations}} with an additional step. Before beginning the standard pattern as descbribed on the linked section, it is first necessary to retrieve the latest version of the booking from the **receiver** as it may have changed locally. This is done by performing a "GET Appointment by ID" call to the **receiving** system's corresponding API endpoint (via the BaRS proxy).
+To cancel a booking this Application follows the {{pagelink:core-SPCancellation-1.3.0, text:standard pattern for BaRS cancellation}}.
-The response to this request will be the requested Appointment resource which should be checked for its current status to ensure it does not already have a status of "cancelled". If not, this version of the Appointment should be used when re-submitting the modified resource in the POST bundle as described in the {{pagelink:Core-StandardPattern-1.3.0, text:standard pattern}}.
+The Message Definition that defines the payload for this Application is: [BARS Message Definition - Cancel Booking Request](https://simplifier.net/nhsbookingandreferrals/messagedefinition-barsmessagedefinitionbookingrequestcancelled)
-The message definition that defines this payload for this Application is: [BARS Message Definition - Cancel Booking Request](https://simplifier.net/nhsbookingandreferrals/messagedefinition-barsmessagedefinitionbookingrequestcancelled)
-
-
-As a general principle, when performing an update type of operation (of which cancellation is a special case), only the focus resource is altered. Any resources that are mandated due to contextual, linking or referential integrity reasons play a supporting role, although any resources that include elements that are being changed are included too. This is always defined within the relevant message definition.
+If the update-to-cancel is taking place as part of a re-book routine, once the cancellation is complete, the new booking request can be sent. This step in the workflow would follow the same process as 'Make a Booking' detailed above.
In addition the specific workflow parameters that are required are as follows:
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
index f65b2fb7..b557cfe7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
@@ -19,11 +19,11 @@ These guides are designed to be used in conjunction with the documentation for {
| Application | Use Cases | Current Release | Minimum API Spec | Minimum Core Version |
| ----------------------------------------------------------------------------|--------------------------------------------------------------- | --------------- | --------------- | --------------- |
-| {{pagelink:application1, text:Booking and Referrals into UEC (Application 1)}} |
111 - UTC
CAS - ED
CAS - UTC
999 - ED
999 - UTC
111 - SDEC
CAS - SDEC
999 - SDEC
111 Online - UTC
S&R - ED
S&R - UTC
| 1.0.3 | v1.0.0 | v1.0.0 |
-| {{pagelink:application4, text: Referral into UEC for Validation (Application 4)}} |
| 1.2.2 | v1.0.0 | v1.0.0 |
-| {{pagelink:application5, text: Referrals into Pharmacy (Application 5)}} |
| 1.1.2 | v1.1.0 | {{pagelink:design-core-1.3.0, text:v1.1.0}} |
+| {{pagelink:application1, text:Booking and Referrals into UEC (Application 1)}} |
111 - UTC
CAS - ED
CAS - UTC
999 - ED
999 - UTC
111 - SDEC
CAS - SDEC
999 - SDEC
111 Online - UTC
S&R - ED
S&R - UTC
| 1.0.4 | v1.0.0 | v1.0.0 |
+| {{pagelink:application4, text: Referral into UEC for Validation (Application 4)}} |
| 1.2.3 | v1.0.0 | v1.0.0 |
+| {{pagelink:application5, text: Referrals into Pharmacy (Application 5)}} |
| 1.1.3 | v1.1.0 | {{pagelink:design-core-1.3.0, text:v1.1.0}} |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md
index 9c93c1f2..6a6877b7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md
@@ -14,8 +14,8 @@ These guides are designed to be used in conjunction with the documentation for {
| Application | Use Cases | Current Release | API Specification | Core Version |
| ----------------------------------------------------------------------------|--------------------------------------------------------------- | --------------- | --------------- | --------------- |
-| {{pagelink:application6, text: Referrals into an Ambulance Service Trust (Application 6)}} |
CAD to CAD Call Assist Request
CAD to CAD Mutual Aid Request | 1.0.0-beta.4 | API Spec v1.1.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.1.0 and above}} |
-| {{pagelink:application7, text: Bookings into GP Practice (Application 7)}} |
CAD to CAD Call Assist Request
CAD to CAD Mutual Aid Request | 1.0.0-beta.5 | API Spec v1.1.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.1.0 and above}} |
+| {{pagelink:application7, text: Bookings into GP Practice (Application 7)}} | > Expand for full Core directory
-• {{pagelink:design-core-1.0.7 , text: Core 1.0.6}}
+• {{pagelink:design-core-1.0.7 , text: Core 1.0.7}}
• {{pagelink:core-EndToEndWorkflow-1.0.7 , text:End to end workflow}}
• {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.0.7 , text:Service Discovery}}
• {{pagelink:core-EndToEndWorkflow-BaRSAuth-1.0.7 , text:Authenticate with BaRS}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Standard-Pattern-Composite-Messages/Cancellation.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Standard-Pattern-Composite-Messages/Cancellation.page.md
index 0277191c..88f82480 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Standard-Pattern-Composite-Messages/Cancellation.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.7/Standard-Pattern-Composite-Messages/Cancellation.page.md
@@ -327,6 +327,7 @@ This payload is used to transmit all the necessary information that is required
| Bundle | The Bundle resource is the container for the event message https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
+| Bundle.meta.versionId | This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing. | MUST | 0..1 | 1.0.0-beta |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/End-to-end-workflow/Logging.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/End-to-end-workflow/Logging.page.md
index 07074fbb..60590682 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/End-to-end-workflow/Logging.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/End-to-end-workflow/Logging.page.md
@@ -22,7 +22,7 @@ The elements for a ServiceRequest are:
The elements for an Appointment are:
-* Appointent.serviceCategory.coding (usecases-categories-bars)
+* Appointment.serviceCategory.coding (usecases-categories-bars)
* Appointment.status
* MessageHeader.eventCoding.code (message-event-bars)
* MessageHeader.reason.coding.code (message-reason-bars)
@@ -42,7 +42,7 @@ Example:
### Booking
```
- Appointent.serviceCategory.coding[usecases-categories-bars] | Appointment.status | MessageHeader.eventCoding.code | MessageHeader.reason.coding.code
+ Appointment.serviceCategory.coding[usecases-categories-bars] | Appointment.status | MessageHeader.eventCoding.code | MessageHeader.reason.coding.code
```
Example:
```
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Index.page.md
index 4dd1d828..4a3475b9 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Index.page.md
@@ -3,9 +3,6 @@ topic: design-core-1.3.0
---
@@ -34,7 +31,7 @@ You will find here a set of documentation, specifications and services that desc
@@ -16,9 +13,9 @@ This version of core is strictly a preview of what is currently in development f
-
v1.2.2-alpha
+ v1.3.0
v1.8.2
- v1.2.0
+ v1.3.0
> Expand for full Core directory
-• {{pagelink:design-core-1.3.0 , text: Core 1.2.2}}
+• {{pagelink:design-core-1.3.0 , text: Core 1.3.0}}
• {{pagelink:core-EndToEndWorkflow-1.3.0 , text:End to end workflow}}
• {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.3.0 , text:Service Discovery}}
• {{pagelink:core-EndToEndWorkflow-BaRSAuth-1.3.0 , text:Authenticate with BaRS}}
@@ -83,9 +80,9 @@ You will find here a set of documentation, specifications and services that desc
• {{pagelink:Core-TransactionalIntegrity-Initial-1.3.0 , text:Initial Request}}
• {{pagelink:Core-TransactionalIntegrity-Update-1.3.0 , text:Sending an update}}
• {{pagelink:Core-TransactionalIntegrity-Feedback-1.3.0 , text:Feedback (response) requests}}
- • {{pagelink:Core-TransactionalIntegrity-Retry-1.3.0 , text:Retry Scenario}}
+ • {{pagelink:Core-TransactionalIntegrity-RetryScenario-1.3.0 , text:Retry Scenario}}
• {{pagelink:Core-TransactionalIntegrity-Onward-1.3.0 , text:Onwards Referrals}}
- • {{pagelink:Core-TransactionalIntegrity-retry-1.3.0 , text:Definition of a Retry}}
+ • {{pagelink:Core-TransactionalIntegrity-RetryDefinition-1.3.0 , text:Definition of a Retry}}
• {{pagelink:Core-TransactionalIntegrity-Receiver-1.3.0 , text:Receiver responsibilities}}
• {{pagelink:Core-TransactionalIntegrity-Sender-1.3.0 , text:Sender responsibilities}}
• {{pagelink:core-TIFailureScenarios-1.3.0 , text:Failure Scenarios}}
@@ -243,7 +240,7 @@ For more detail please visit the {{pagelink:core-StandardPattern-document-refere
-The below diagram details the options for obtaining the booking (Appointment) or referral (ServiceRequest) resource, prior to cancellation. The Sender **must** know the (resource).status and (resource).id values, as minimum, to build a valid cancellation request.
+
@@ -70,6 +73,7 @@ This payload is used to transmit all the necessary information that is required
| Bundle | The Bundle resource is the container for the event message https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
+| Bundle.meta.versionId | This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing. | MUST | 0..1 | 1.0.0-beta |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
@@ -340,6 +344,7 @@ This payload is used to transmit all the necessary information that is required
| Bundle | The Bundle resource is the container for the event message https://simplifier.net/nhsbookingandreferrals/barsbundlemessage | | 1..1 | |
| Bundle.id | This id is generated by the originating sender of the message, retained in subsequent messages.. | MUST | 1..1 | 79120f41-a431-4f08-bcc5-1e67006fcae0 |
| Bundle.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 0..1 | |
+| Bundle.meta.versionId | This MUST be populated with the version of the Application the bundle complies with. The Receiver will read this to know whether they are capable of processing. | MUST | 0..1 | 1.0.0-beta |
| Bundle.meta.profile | This MUST be populated with the structure definition for BaRSBundleMessage : 'https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/StructureDefinition/BARSBundleMessage |
| Bundle.meta.lastUpdated | All resources MUST include 'lastUpdated' value, under meta section which must be the same timestamp for each resource when created from new, but must be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Bundle.type | This must be populated with 'message' - FIXED VALUE | MUST | 1..1 | message |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/Howtousethisimplementationguide.guide.md b/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/Howtousethisimplementationguide.guide.md
index 45380b30..825d70e2 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/Howtousethisimplementationguide.guide.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/Howtousethisimplementationguide.guide.md
@@ -3,6 +3,9 @@
This section provides a generated site map of this implementation guide.
+## Searching the Implementation Guide
+
+A search feature is provided in the Implementation Guide to help find, and navigate to, specific content. Please note that results appear in date order and may reference earlier versions of the Implementation Guide. Always check that the result navigates you to the version you need.
## Intended Audience
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/toc.yaml
index af611472..73f721a5 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Helpandsupport/toc.yaml
@@ -6,5 +6,5 @@
filename: Glossary.guide.md
- name: Downloads
filename: Downloads.guide.md
-- name: ReportanIncident
+- name: Report an Incident
filename: ReportanIncident.guide.md