MergeToMain7

CodeSystem/usecases-categories-bars.xml

@@ -126,7 +126,7 @@
   </concept>
   <concept>
     <code value="a8t1" />
-    <display value="IAG to e-RS" />
+    <display value="AG to e-RS" />
   </concept>
   <concept>
     <code value="a8t2" />

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Current-Releases.page.md

@@ -22,7 +22,7 @@ Implementation Guide   | 1.11.0   | v1      | Live     | Current Release | 26/03
 
 Release 1.11.0 of the BaRS Implementation Guide introduces BaRS Application 8 "Referrals to a broker for Healthcare Service selection" as an alpha release.  BaRS Application 8 is designed to create interoperability for referrals between NHS England products.  The next phase of content and navigation changes in the Implementation Guide are delivered.  They are focussed on: the Home page, the Analysis section (formerly About BaRS) and relocation of content from this area.  These changes are based on user feedback. 
 
-Application 5 is updated with the withdrawl of use cases for GP to Blood Pressure Check Service and GP to Pharmacy Contraception (Oral Contraception).  Also included in this release are minor changes to BaRS Application 6 and bug fixes and corrections throughout the guide.
+Application 5 is updated with the withdrawal of use cases for GP to Blood Pressure Check Service and GP to Pharmacy Contraception (Oral Contraception).  Also included in this release are minor changes to BaRS Application 6 and bug fixes and corrections throughout the guide.
 
 A clinical safety assessment of the scope of this release has determined that it has not significantly changed the clinical safety profile of the BaRS. No new hazards have been identified in this release. The latest version of the BaRS clinical safety case and hazard log can be downloaded from the <a href= "https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/onboarding-support-information#hazard-log-and-clinical-safety-case-report-cscr-" target="_blank"> BaRS FHIR API onboarding support information page </a>.
 

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.11.0.page.md

@@ -7,7 +7,7 @@
 | Bug fixes and corrections  |There have been several bug fixes and corrections in the guide, these includes typos, broken links or corrections.|
 | About BaRS renamed to Analysis  |Following user research into the experience of using the Implementation Guide, About BaRS is renamed Analysis to support users to locate information they need.|
 | Home page  |The Home page is restructured to include a step by step guide that supports users to identify where they are in the implementation process.|
-| FHIR Assets  |Content about FHIR formerly in the About BaRS section about is relocated to the FHIR Assets page.|
+| FHIR Assets  |Content about FHIR formerly in the About BaRS section is relocated to the FHIR Assets page.|
 | Roles and Responsibilities |Roles and Responsibilities content formerly in the Deploy section is relocated as a specific page in the Analysis section.|
 | Infrastructure  |Content about Infrastructure formerly in the About BaRS section about is relocated on a specific page in the Analysis section.|
 | Contact Us  |Improved content added in Help and Support with additional contact details for Digital Onboarding Service and Toolkit Work Bench queries.|

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md

@@ -1,5 +1,6 @@
 <div class="bars-blg-expander">
 <div class="bars-blg-expander-entry" id="v1.1.3">
+
 ## {{page-title}}
 
 <br>

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.4.page.md

@@ -1,5 +1,6 @@
 <div class="bars-blg-expander">
 <div class="bars-blg-expander-entry" id="v1.1.4">
+
 ## {{page-title}}
 
 <br>

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.2.0.page.md

@@ -1,7 +1,7 @@
 ## {{page-title}}
 
 <br>
-This stable release (v1.2.0) of Application 5 sees the withdrawl of Blood Pressure and Oral Contraception use cases.
+This stable release (v1.2.0) of Application 5 sees the withdrawl of Blood Pressure Check Service and Pharmacy Contraception (Oral Contraception) use cases.
 <br>
 
 

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Versioning.guide.md

@@ -24,7 +24,7 @@ The extensions ALPHA, BETA or RC (Release Candidate) will be used to indicate th
 An appreciation of the components involved in a released version must be understood when building solutions. These separate components come together under the umbrella of a given overall version but the components themselves are also versioned. This published implementation guide denotes the 'overall version' referenced. 
 
 Components involved in an overall version:- 
-* **{{pagelink:design-core-1.0.7, text:Core}}**: BaRS Core components - API Spec, Endpoint Catalogue etc.
+* **{{pagelink:design-core-1.4.0, text:Core}}**: BaRS Core components - API Spec, Endpoint Catalogue etc.
 * **[Package](https://simplifier.net/NHSBookingandReferrals/~packages)**: FHIR package
 * **{{pagelink:applications, text:Application}}**: the use cases i.e. '111 to ED'
 * **{{pagelink:fhir_assets, text:FHIR Assets}}**: MessageDefinitions and profiles

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP1/How-does-it-work.page.md

@@ -247,7 +247,7 @@ X-Correlation-Id = <GUID_00002>
 
 ### Make a booking
 
-Making a booking for this Application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a booking for this Application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this Application is: [BARS Message Definition - Booking Request](https://simplifier.net/nhsbookingandreferrals/messagedefinition-bars-messagedefinition-booking-request)
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP2/How-does-it-work.page.md

@@ -13,7 +13,7 @@ To support the workflows for this Application of the standard the operations tha
 
 ### Make a Referral
 
-Making a referral for this Application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a referral for this Application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The message definition that defines this payload for this Application is: {{link:https://fhir.nhs.uk/MessageDefinition/bars-message-servicerequest-request-referral}}
 
@@ -140,7 +140,7 @@ X-Correlation-Id = <GUID_00002>
 
 ### Make a booking
 
-Making a booking for this Application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a booking for this Application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The message definition that defines this payload for this Application is: {{link:https://fhir.nhs.uk/MessageDefinition/bars-message-servicerequest-request-referral}}
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP3/How-does-it-work.page.md

@@ -30,7 +30,7 @@ To support the workflows for this application of the standard the operations tha
 
 ### Make a Referral
 
-Making a referral for this application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a referral for this application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
 <p>

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/How-does-it-work.page.md

@@ -68,7 +68,7 @@ To support the workflows for this application of the standard the operations tha
 
 ## Make a Validation Request
 
-Making a Validation Request for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a Validation Request for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Validation}}
 <p>

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/How-does-it-work.page.md

@@ -162,7 +162,7 @@ When a service is chosen, the "Service ID" field in the DOS data will be used as
 
 ### Make a Referral
 
-Making a referral for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a referral for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
 <p>

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/How-does-it-work.page.md

@@ -118,7 +118,7 @@ To support the workflows for this application of the standard the operations tha
 
 ## Make a Referral
 
-Making a referral for this application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a referral for this application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
 <p>

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Index.page.md

@@ -5,7 +5,7 @@ topic: Application6
 # Referrals into an Ambulance Service Trust (Application 6)
 
 
-<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important:</b> This guide is currently under development <hr><p> This is a preview of a developing guide for information only. With the exception of those involved in developing solutions for the first of type (private beta), It is not intended to be used until the completed v1.0.0 documentation for this application is released <p> If you are interested in developing a BaRS compliant solution right now for the use cases covered by this application, please use the contact form <a href="https://digital.nhs.uk/services/booking-and-referral-standard/enquiry-form" target="_blank">here</a> and the team will be in touch
+<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important:</b> This guide is currently under development <hr><p> This is a preview of a developing guide for information only. With the exception of those involved in developing solutions for the first of type (private beta), it is not intended to be used until the completed v1.0.0 documentation for this Application is released <p> If you are interested in developing a BaRS compliant solution right now for the use cases covered by this Application, please use the contact form <a href="https://digital.nhs.uk/services/booking-and-referral-standard/enquiry-form" target="_blank">here</a> and the team will be in touch
 
 <p>
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/How-does-it-work.page.md

@@ -78,7 +78,7 @@ X-Correlation-Id = <GUID_00002>
 
 ### Make a booking
 
-Making a booking for this Application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a booking for this Application follows the {{pagelink:Core-StandardPattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this Application is: [BARS Message Definition - Booking Request](https://simplifier.net/nhsbookingandreferrals/messagedefinition-bars-messagedefinition-booking-request)
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/Index.page.md

@@ -4,7 +4,7 @@ topic: Application7
 
 # Bookings and Referrals into GP (Application 7)
 
-<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important:</b> This guide is currently under development <hr><p> This is a preview of a developing guide for information only. With the exception of those involved in developing solutions for the first of type (private beta), It is not intended to be used until the completed v1.0.0 documentation for this application is released <p> If you are interested in developing a BaRS compliant solution right now for the use cases covered by this application, please use the contact form <a href="https://digital.nhs.uk/services/booking-and-referral-standard/enquiry-form" target="_blank">here</a> and the team will be in touch
+<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important:</b> This guide is currently under development <hr><p> This is a preview of a developing guide for information only. With the exception of those involved in developing solutions for the first of type (private beta), it is not intended to be used until the completed v1.0.0 documentation for this Application is released <p> If you are interested in developing a BaRS compliant solution right now for the use cases covered by this Application, please use the contact form <a href="https://digital.nhs.uk/services/booking-and-referral-standard/enquiry-form" target="_blank">here</a> and the team will be in touch
 
 <p>
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md

@@ -6,7 +6,7 @@ topic: APP8-HowDoesItWork
 
 This section describes how the primary operations used in this Application work. 
 
-This diagram illustrates the workflow and interactions of a referral request where healthcare options are offered to a patient by a clinician:
+This diagram illustrates the workflow and interactions of a referral request where a shortlist of healthcare service options are offered to a patient by a clinician:
 <br>
 
 <img src="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/WorkFlows/Internal-Broker-AG-To-e-RS-1.0.0-alpha.svg" width="1500"></img></a>
@@ -26,20 +26,22 @@ The referral request is directed to a broker in this Application, rather than di
 
 The Sender will establish the patient need, identify a specific service or prepare a shortlist of healthcare services to support them, and package these in the referral request. The request is sent from the Sender to the broker (Receiver) and then onto the selected healthcare service (through [e-RS](https://digital.nhs.uk/services/e-referral-service) ). 
 
+Alternatively, where a self-referral workflow is undertaken, the steps are the same but only one healthcare service option is included in the referral request. 
+
 Directing the referral request will still engage the same BaRS mechanisms; utilising the NHSD-Target-Identifier. However, the Receiver is a consistent, known entity, rather than dynamically established during workflow.
 
 *NB - The definition of the broker NHSD-Target-Identifier has not yet been agreed.*
 
 ### Make a Referral
 
-Making a referral for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS operations}}.
+Making a referral for this application follows the {{pagelink:core-standardpattern-1.4.0, text:standard pattern for BaRS Composite Messages}}.
 
 The Message Definition that defines this payload for this application is: {{link:MessageDefinition-BARS-MessageDefinition-ServiceRequest-Request-Referral}}
 <p>
 
 <hr>
 
-In addition to that the specific workflow parameters that are required are as follows:
+In addition, the specific workflow parameters that are required are as follows:
 
 <div class="nhsd-m-emphasis-box">
     <div class="nhsd-a-box nhsd-a-box--border-grey">

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Index.page.md

@@ -4,9 +4,13 @@ topic: Application8
 
 # Referrals into a broker for Healthcare Service selection (Application 8)
 
- <div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important: Versioning information</b> 
- <p>
- <table>
+<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important:</b> This guide is currently under development <hr><p> This is a preview of a developing guide for information only. With the exception of those involved in developing solutions for the first of type (private beta), it is not intended to be used until the completed v1.0.0 documentation for this Application is released <p> If you are interested in developing a BaRS compliant solution right now for the use cases covered by this Application, please use the contact form <a href="https://digital.nhs.uk/services/booking-and-referral-standard/enquiry-form" target="_blank">here</a> and the team will be in touch
+
+<p>
+
+<b> Important: Versioning information</b> 
+<p>
+<table>
 <thead>
 	<tr>
 		<th data-no-sort="">Application Version</th>
@@ -34,15 +38,15 @@ This application supports the use of the following use cases:
 |Use case                                                                        | Name | Code|
 |--------------------------------------------------------------------------------|------|------|
 | Advice and Guidance to electronic-Referral Service (e-RS)| AG to e-RS  | A8T1 |
-| 111Online to electronic-Referral Service (e-RS)| 111online to e-RS  | A8T2 |
+| 111 Online to electronic-Referral Service (e-RS)| 111 online to e-RS  | A8T2 |
 | NHS.UK to electronic-Referral Service (e-RS)| nhs.uk to e-RS  | A8T3 |
 
 
 ## Introduction
 
 ### Overview
 
-This page provides guidance for implementing the Referral Standard (BaRS) specifically for the use cases listed above. It should be used alongside the {{pagelink:design-core-1.4.0, text:BaRS Core implementation guide}} and API Specification when developing to the standard. 
+This page provides guidance for implementing the Referral Standard (BaRS) specifically for the use cases listed above. It should be used alongside the {{pagelink:design-core-1.4.0, text:BaRS Core implementation guide}} and [API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.4.0) when developing to the standard. 
 
 ### Data model endorsements
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Payloads.page.md

@@ -58,7 +58,7 @@ When a BARS Receiver processes information in a Flag resource;
 * rendering of Flag information must be in line with the {{pagelink:Home/Analysis/BaRS-Principles-and-Prerequisites/Principles-for-rendering-BaRS-payloads.page.md, text:Principles for rendering BaRS Payload }}.
 
 ### Consent 
-In the BaRS UEC Applications the level of consent is stipulated to be for 'Direct Care' only. A referral **must** contain a Consent resource and it **must** adhere to the [example](https://simplifier.net/NHSBookingandReferrals/8fc39b95-89a6-45fb-914f-1458a10e9e14/~json) provided under the BaRS FHIR assets. 
+In BaRS Applications the level of consent is stipulated to be for 'Direct Care' only. A referral **must** contain a Consent resource and it **must** adhere to the [example](https://simplifier.net/NHSBookingandReferrals/8fc39b95-89a6-45fb-914f-1458a10e9e14/~json) provided under the BaRS FHIR assets. 
 <br>
 
 <hr>