-
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Current-Releases.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Current-Releases.page.md
index 13a8d735..c4692e34 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Current-Releases.page.md
+++ b/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 BaRS FHIR API onboarding support information page .
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.11.0.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.11.0.page.md
index 3cfd1582..0e3768e2 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.11.0.page.md
+++ b/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.|
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md
index fcde596b..83a724c5 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.3.page.md
@@ -1,5 +1,6 @@
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/How-does-it-work.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/How-does-it-work.page.md index e594a64b..b40c2603 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/How-does-it-work.page.md +++ b/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}}
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 e5e1e947..0d8393d5 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 @@ -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}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/How-does-it-work.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/How-does-it-work.page.md index 22f3b220..83593c16 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/How-does-it-work.page.md +++ b/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}}
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Index.page.md index 5cb44f22..17fb92df 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Index.page.md +++ b/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) -
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
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 here and the team will be in touch +
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
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 here and the team will be in touch
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/How-does-it-work.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/How-does-it-work.page.md
index 779eb4b4..84d7046d 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/How-does-it-work.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP7/How-does-it-work.page.md
@@ -78,7 +78,7 @@ X-Correlation-Id = 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 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 here and the team will be in touch
+ 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 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 here and the team will be in touch
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md
index e6504b6f..4b581e42 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md
+++ b/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:
- 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 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 here and the team will be in touch
+
+
+
+ Important: Versioning information
+
+
111 Online - ED | 2.0.0 | 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 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.4 | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
-| {{pagelink:application8, text: Referrals into a broker for Healthcare Service selection (Application 8)}} | Advice and guidance referring into electronic Referral Service (eRS) | 1.0.0-alpha | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
+| {{pagelink:application8, text: Referrals into a broker for Healthcare Service selection (Application 8)}} | Advice and guidance referring into electronic Referral Service (eRS)
@@ -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}}
-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:
+
Application Version
@@ -34,7 +38,7 @@ 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 |
@@ -42,7 +46,7 @@ This application supports the use of the following use cases:
### 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
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Payloads.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Payloads.page.md
index eb011853..49e76f80 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Payloads.page.md
+++ b/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.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Referral-Payload.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Referral-Payload.page.md
index 845b4c2a..62c486f8 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Referral-Payload.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Referral-Payload.page.md
@@ -165,8 +165,8 @@ This payload is used to transmit all the necessary information that is required
| Encounter.status | This MUST be populated with 'finished' or 'triaged'. | MUST | 1..1 | finished |
| Encounter.class | | MUST | 1..1 | |
| Encounter.class.system | This MUST be populated with CodeSystem 'http://terminology.hl7.org/CodeSystem/v3-ActCode' - FIXED VALUE | MUST | 0..1 | http://terminology.hl7.org/CodeSystem/v3-ActCode |
-| Encounter.class.code | This MUST be populated with Code 'EMER'. See CodeSystem: 'http://terminology.hl7.org/CodeSystem/v3-ActCode' - FIXED VALUE | MUST | 0..1 | VR |
-| Encounter.class.display | This MUST be populated with Display 'emergency'. See CodeSystem: 'http://terminology.hl7.org/CodeSystem/v3-ActCode' - FIXED VALUE | MUST | 0..1 | Virtual |
+| Encounter.class.code | This MUST be populated with Code 'VR'. See CodeSystem: 'http://terminology.hl7.org/CodeSystem/v3-ActCode' - FIXED VALUE | MUST | 0..1 | VR |
+| Encounter.class.display | This MUST be populated with Display 'virtual'. See CodeSystem: 'http://terminology.hl7.org/CodeSystem/v3-ActCode' - FIXED VALUE | MUST | 0..1 | virtual |
| Encounter.subject | | MUST | 0..1 | |
| Encounter.subject.reference | This MUST be populated with a reference to the Patient resource. | MUST | 1..1 | urn:uuid:9589fb37-87a2-48d8-968f-b371429208a8 |
| Encounter.episodeOfCare | | MUST | 0..* | |
@@ -501,7 +501,7 @@ This payload is used to transmit all the necessary information that is required
| Flag.subject.reference | This MUST be populated with the subject that the flag refers to. Where the flag relates to the patient (e.g. reasonable adjustments) this will reference the Patient resource | MUST | 1..1 | urn:uuid:9589fb37-87a2-48d8-968f-b371429208a8 |
| Flag.period | | SHOULD | 0..1 | |
| Flag.period.start | Follow UK Core guidance for populating this element | SHOULD | 0..1 | 2023-03-08T12:01:08.4677672+00:00 |
-| Flag.period.end | Follow UK Core guidance for populating this element | MAY | 0..1 | 2023-03-08T12:01:08.4677672+00:00 |
+| Flag.period.end | Follow UK Core guidance for populating this element | MAY | 0..1 | 2024-03-08T12:01:08.4677672+00:00 |
111 Online - UTC
S&R - ED
S&R - UTC
| 2.0.0 | v1.0.0 | v1.0.0 |
| {{pagelink:application4, text: Referral into UEC for Validation (Application 4)}} |
| 2.0.0 | v1.0.0 | v1.0.0 |
-| {{pagelink:application5, text: Referrals into Pharmacy (Application 5)}} |
| 1.1.4 | v1.3.0 | {{pagelink:design-core-1.4.0, text:v1.3.0}} |
+| {{pagelink:application5, text: Referrals into Pharmacy (Application 5)}} |
| 1.2.0 | v1.3.0 | {{pagelink:design-core-1.4.0, text:v1.3.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 41204f5f..68011c43 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
@@ -16,7 +16,7 @@ These guides are designed to be used in conjunction with the documentation for {
| ----------------------------------------------------------------------------|--------------------------------------------------------------- | --------------- | --------------- | --------------- |
| {{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.7 | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
| {{pagelink:application7, text: Bookings into GP Practice (Application 7)}} |
111 Online referring into electronic Referral Service
nhs.uk referring into electronic Referral Service | 1.0.0-alpha | API Spec v1.3.0 and above | {{pagelink:design-core-1.1.4, text:Core v1.3.0 and above}} |
## Beta Deployment Guide
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md
index 63ccfba0..0d420280 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md
@@ -3,7 +3,7 @@
BaRS Sandbox is available from the [BaRS API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0). It demonstrates key functionality without the overhead of security requirements, giving developers the opportunity to understand the product before progressing development.
-BaRS Integration (INT) is a live-like environment for suppliers progressing with development and testing to use. To use INT, you will need to follow the instructions to [Connect as a sender](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md) or [Connect as a receiver](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md).
+BaRS Integration (INT) is a live-like environment for suppliers progressing with development and testing to use. To use INT, you will need to follow the instructions to {{pagelink:connect-as-a-sender, text:Connect as a sender}} or {{pagelink:connect-as-a-receiver, text:Connect as a receiver}}
BaRS Production (PROD) is the live environment. Suppliers will need to have progressed through assurance before applying to connect to the PROD environment.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.4.0/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.4.0/Index.page.md
index 5f5c7d27..bd8befc7 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.4.0/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.4.0/Index.page.md
@@ -14,7 +14,7 @@ topic: design-core-1.4.0
v1.4.0
- v1.10.0
+ v1.11.0
v1.4.0