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
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Current-Releases.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 @@ Implementation Guide | 1.11.1 | v1 | Live | Current Release | 19/05
20
20
21
21
### Overview of the release
22
22
23
-
Release 1.11.1 of the BaRS Implementation Guide is a patch release including an additional encounter.status value for Application 6 CAD-CAD Out of Area Referral, published with supporting documentation. BaRS Core version is uplifted to 1.4.1 in line with an update to the BaRS FHIR API OAS file.
23
+
Release 1.11.1 of the BaRS Implementation Guide is a patch release including an additional encounter.status value for Application 6 CAD to CAD Out of Area Referral, published with supporting documentation. BaRS Core version is uplifted to 1.4.1 in line with an update to the BaRS FHIR API OAS file. Updates to the BaRS FHIR API OAS file are limited to changes relating to internal endpoint catalogue management and do not affect supplier development.
24
24
25
25
Also included in this release are minor changes to BaRS Application 8 and bug fixes and corrections throughout the guide.
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.11.1.page.md
| Bug fixes and corrections |There have been several bug fixes and corrections in the guide, these includes typos, broken links or corrections.|
8
-
| 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.|
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP8/1.0.0-alpha.2.page.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,21 @@ This is a pre-release of v1.0.0-alpha.2 - Referrals into a broker for Healthcare
| Application 8 released | Referrals into a broker for Healthcare Service selection||
14
+
| Patient Identifier Coding | Removed "Number present but not traced" from the guidance, as it is not valid in this scenario.|<markstyle="background-color: LightGreen">non-breaking</mark>|
15
+
| Additional Patient Information Link | Added a link to the simplifier example for Additional Patient Information referenced in the Flag section |<markstyle="background-color: LightGreen">non-breaking</mark>|
16
+
| Removed specific Pharmacy References | Removed references to Pharmacy in the guidance where the implication was that it was Pharmacy exclusive. |<markstyle="background-color: LightGreen">non-breaking</mark>|
15
17
16
18
### Payload Change Log
17
19
18
20
19
21
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
| Patient.identifier.extension.valueCodeableConcept.coding.code | Where used this MUST be 'number-present-and-verified' or 'number-present-but-not-traced', else no NHS number MUST be sent. | Where used this MUST be 'number-present-and-verified' else no NHS number MUST be sent. | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
24
+
| Patient.identifier.extension.valueCodeableConcept.coding.display | Where used this MUST be populated with 'Number present and verified' or 'Number present but not traced'. | Where used this MUST be populated with 'Number present and verified'. | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
25
+
| ServiceRequest.occurencePeriod | Timeframe within which pharmacy must manage the referral | Timeframe within which the referral must be managed | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
26
+
| Task.code | This MUST be populated with the action (by the specific Pharmacy Service (Referral Type)) the Sender is requesting of the Receiver | This MUST be populated with the action the Sender is requesting of the Receiver | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
27
+
| Task.code.coding.code | This MUST be populated with the Code (SNOMED) of action by the Pharmacy Service | This MUST be populated with the Code (SNOMED) of action | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
28
+
| Task.code.coding.display | This MUST be populated with the human readable Display (SNOMED) of action by the Pharmacy Service | This MUST be populated with the human readable Display (SNOMED) of action | Update | Referral Response |Change | <markstyle="background-color: LightGreen">non-breaking</mark> |
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/How-does-it-work.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
@@ -15,7 +15,7 @@ This section describes how the primary operations used in this application work.
Copy file name to clipboardExpand all lines: guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.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
@@ -16,7 +16,7 @@ The BaRS Proxy uses the ServiceId in the HTTP Header to reference the BaRS Endpo
16
16
17
17
* Note the ServiceId used in Service Discovery (NHS Directory of Service or other Service Discovery tool)
18
18
19
-
* Obtain the service's URL endpoint details from the Receiving supplier or provider. The endpoint will need to be certified and meet the criteria for connection to the BaRS Proxy. More details are available in [Connecting as a receiver](https://simplifier.net/guide/nhsbookingandreferralstandard/Home\Build\Testing-and-Environments\Connect-as-a-receiver.page.md)
19
+
* Obtain the service's URL endpoint details from the Receiving supplier or provider. The endpoint will need to be certified and meet the criteria for connection to the BaRS Proxy. More details are available in [Connecting as a receiver](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Build/Testing-and-Environments/Connect-as-a-receiver)
20
20
21
21
* Email: <england.bookingandreferralstandard@nhs.net> with the ServiceId and endpoint details. State the environment to be configured, INT or PROD, and include planned dates for testing.
0 commit comments