You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -20,7 +20,9 @@ Implementation Guide | 1.11.0 | v1 | Live | Current Release | 26/03
20
20
21
21
### Overview of the release
22
22
23
-
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. Also included in this release are minor changes to BaRS Application 6 and bug fixes and corrections throughout the guide.
23
+
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.
24
+
25
+
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.
24
26
25
27
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 <ahref= "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>.
26
28
@@ -177,6 +179,10 @@ Table detailing active versions of the latest Applications in Production (or cur
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP5/1.1.4.page.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
<divclass="bars-blg-expander">
2
+
<divclass="bars-blg-expander-entry"id="v1.1.4">
1
3
## {{page-title}}
2
4
3
5
<br>
@@ -23,8 +25,11 @@ This stable release (v1.1.4) of Application 5 sees minor corrections.
23
25
| Patient.identifier.extension.valueCodeableConcept.coding.code | This SHOULD be populated. Where used this MUST either be number-present-and-verified or no NHS number MUST be sent, no other status is valid | This SHOULD be populated. Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. No other statuses are permitted. | Update | Referral Request |Accommodate NHS No. Requirement | <markstyle="background-color: Red">breaking</mark> |
24
26
| Patient.identifier.extension.valueCodeableConcept.coding.display | This SHOULD be populated. Where used this MUST either be populated with 'Number present and-verified' no other status is valid | This SHOULD be populated. Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. No other statuses are permitted. | Update | Referral Request |Accommodate NHS No. Requirement | <markstyle="background-color: Red">breaking</mark> |
| Update to use case status | Withdrawl of Blood Pressure Check Service and Pharmacy Contraception (Oral Contraception) use cases | <markstyle="background-color: LightGreen">non-breaking</mark> |
17
+
18
+
19
+
### Payload Change Log
20
+
21
+
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP5/Index.page.md
<divmarkdown="span"class="alert alert-warning"role="alert"><iclass="fa fa-warning"></i><b> Important: Notice for suppliers</b>
31
31
<p>
32
32
Any suppliers building to this application (Application 5) must engage with NHS England's Pharmacy First/Digital Services for Integrated Care teams prior to building Application 5.
33
+
34
+
The only use case suppliers can develop to in Application 5 is Primary Care to Community Pharmacy (Pharmacy First).
33
35
</p>
34
36
35
37
</div>
@@ -39,12 +41,12 @@ topic: Application5
39
41
40
42
This application supports the use of the following use cases:
| Deprecated - Primary Care to Community Pharmacy (Pharmacy First) | Primary Care to Community Pharmacy | referraltopharmacy |
45
-
| Primary Care to Community Pharmacy (Pharmacy First) | Primary Care to Community Pharmacy| A5T1 |
46
-
| Primary Care to Pharmacy Contraception (Oral Contraception for supply of initial or repeat prescriptions for Combined Oral Contraceptive (COC) or Proestogen Only Pill (POP)) | Primary Care to Pharmacy Contraception | A5T2 |
47
-
| Primary Care to Pharmacy Blood Pressure Check Service | Primary Care to Pharmacy Blood Pressure Check Service | A5T3 |
| Deprecated - Primary Care to Community Pharmacy (Pharmacy First) | Primary Care to Community Pharmacy | referraltopharmacy | Deprecated |
47
+
| Primary Care to Community Pharmacy (Pharmacy First) | Primary Care to Community Pharmacy| A5T1 | Live |
48
+
| Primary Care to Pharmacy Contraception (Oral Contraception for supply of initial or repeat prescriptions for Combined Oral Contraceptive (COC) or Proestogen Only Pill (POP)) | Primary Care to Pharmacy Contraception | A5T2 | Withdrawn |
49
+
| Primary Care to Pharmacy Blood Pressure Check Service | Primary Care to Pharmacy Blood Pressure Check Service | A5T3 | Withdrawn |
48
50
49
51
50
52
NB - 'Primary Care' currently includes GP Practice and Online Consultation, as described in the [BaRS Clinical Safety Case Report (CSCR)](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/onboarding-support-information#downloads)
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Index.page.md
|Improved Advice and Guidance to electronic-Referral Service (e-RS)|IAG to e-RS | A8T1 |
36
+
| Advice and Guidance to electronic-Referral Service (e-RS)|AG to e-RS | A8T1 |
37
37
| 111Online to electronic-Referral Service (e-RS)| 111online to e-RS | A8T2 |
38
38
| NHS.UK to electronic-Referral Service (e-RS)| nhs.uk to e-RS | A8T3 |
39
39
@@ -48,6 +48,4 @@ This page provides guidance for implementing the Referral Standard (BaRS) specif
48
48
49
49
NHS England teams within Referrals and Appointments, Digitial Urgent and Emergency Care and the National Pathway for Self-Referrals have co-produced the Application 8 standard to facilitate interoperability between existing systems for referral pathways.
50
50
51
-
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 Payload Definitions when developing to the standard.
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Payloads.page.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ There are two *coding* entries within *ServiceRequest.category* which are key to
20
20
1. Denotes the type of referral e.g. Transfer of care
21
21
2. Denotes the use case and must be populated with the relevant use case from [use-case CodeSystem](
). e.g. IAG to e-RS. Please refer to the guidance in {{pagelink:core-SPUseCaseCategories-1.4.0, text:use-case categories}}
23
+
). e.g. AG to e-RS. Please refer to the guidance in {{pagelink:core-SPUseCaseCategories-1.4.0, text:use-case categories}}
24
24
25
25
### Encounter Resource
26
26
The Encounter is used to represent the interaction between a patient and healthcare service provider. It links with numerous other resources, to reflect the assessment performed.
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Scope-and-Requirements.page.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ TOPIC: APP8-ScopeAndRequirements
6
6
7
7
### Scope Overview
8
8
This BaRS Application (Referrals from Advice and Guidance to eRS broker, Application 8) supports the following use case(s) ONLY:
9
-
*Improved Advice and Guidance to electronic-Referral Service (e-RS)
9
+
* Advice and Guidance to electronic-Referral Service (e-RS)
10
10
* 111Online to electronic-Referral Service (e-RS)
11
11
* NHS.UK to electronic-Referral Service (e-RS)
12
12
@@ -55,7 +55,7 @@ The payload and workflow have been designed to support these services. Other {{p
55
55
56
56
**Referral**
57
57
- The referral Receiver **must** accept the referral request regardless of whether the patient is known to the service provider
58
-
- The referral Receiver **must** only accept potential patients who do **<ins>have</ins>** a national validated identifier e.g. NHS Number
58
+
- The referral Receiver **must** only accept potential patients who **<ins>have</ins>** a national validated identifier e.g. NHS Number
59
59
- The national identifier **must** have a [verification status](https://simplifier.net/hl7fhirukcorer4/valueset-ukcore-nhsnumberverificationstatus) of 'Number present and verified' otherwise, the referral Sender **must <ins>not</ins>** include it in the request
60
60
- Any new or existing safeguarding concern, recorded as part of the assessment, **must** be included in the referral Sender's request
61
61
- The referral Receiver **must** clearly identify any included safeguarding concern to the end user
@@ -64,7 +64,7 @@ The payload and workflow have been designed to support these services. Other {{p
64
64
- Where the referral was <ins>not</ins> successful, the Receiver **must** send an appropriate response. See {{pagelink:core-failure_scenarios-1.4.0, text:failure scenarios}} for more detail
65
65
- Where the referral was <ins>not</ins> successful, the Sender **must** present an appropriate message to the end user. See {{pagelink:core-failure_scenarios-1.4.0, text:failure scenarios}} for more detail
66
66
- The referral Sender **must** indicate consent to share (for Direct Care) to the Receiver
67
-
- The referral Sender **must** indicate the urgency (using the agreed codeset) of the request to the Receiver
67
+
- The referral Sender **must** indicate the urgency (using the [agreed codesystem](https://simplifier.net/nhsbookingandreferrals/bars-broker-priority-status)) of the request to the Receiver
0 commit comments