Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

This file was deleted.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@ topic: APP8-EntityRelationshipDiagram
Entity maps detail the relationship of the resources and elements within resources in the payloads.
<br>
<br>
The below diagram details the ServiceRequest - Referral Request - Improved Advice and Guidance to e-RS (a8t1|IAG to e-RS)
The below diagram details the ServiceRequest - Referral Request - Improved Advice and Guidance to e-RS (a8t1|AG to e-RS)
<br>
<br>
<a href="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/EntityMaps/EntityMapIAGtoeRSReferralRequest-1.0.0-alpha.svg" target="_blank"><img src="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/EntityMaps/EntityMapIAGtoeRSReferralRequest-1.0.0-alpha.svg" width="1200"></img></a>
<a href="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/EntityMaps/EntityMapAGtoeRSReferralRequest-1.0.0-alpha.svg" target="_blank"><img src="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/EntityMaps/EntityMapAGtoeRSReferralRequest-1.0.0-alpha.svg" width="1200"></img></a>
<br>
<br>
<br>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ 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:
<br>

<img src="https://raw.githubusercontent.com/NHSDigital/NHSDigital-FHIR-BookingAndReferrals/main/BaRS-Images/WorkFlows/Internal-Broker-IAG-To-e-RS-1.0.0-alpha.svg" width="1500"></img></a>
<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>

The Application also supports a self-referral workflow:
<br>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ This payload is used to transmit all the necessary information that is required
| ServiceRequest.category.coding | BaRS Use Case | MUST | 0..* | |
| ServiceRequest.category.coding.system | This MUST be populated with CodeSystem 'https://fhir.nhs.uk/CodeSystem/usecases-categories-bars' - FIXED VALUE | MUST | 0..1 | https://fhir.nhs.uk/CodeSystem/usecases-categories-bars |
| ServiceRequest.category.coding.code | This MUST be populated with Code for the use-case. See CodeSystem: 'https://fhir.nhs.uk/CodeSystem/usecases-categories-bars' | MUST | 0..1 | A8T1 |
| ServiceRequest.category.coding.display | This MUST be populated with Display for the use-case. See CodeSystem: 'https://fhir.nhs.uk/CodeSystem/usecases-categories-bars' | MUST | 0..1 | Assessment to eRS broker |
| ServiceRequest.category.coding.display | This MUST be populated with Display for the use-case. See CodeSystem: 'https://fhir.nhs.uk/CodeSystem/usecases-categories-bars' | MUST | 0..1 | Assessment to e-RS broker |
| ServiceRequest.code | This MUST be populated, if including orderDetail | COULD | 0..1 | |
| ServiceRequest.code.coding | This MUST be populated with a SNOMED Coded Value. This should be kept generic with the main request and next step being reserved for Task.Code | MUST | 0..1 | |
| ServiceRequest.code.coding.system | This MUST be populated with the SNOMED Code System | MUST | 0..1 | http://snomed.info/sct |
Expand All @@ -140,7 +140,7 @@ This payload is used to transmit all the necessary information that is required
| ServiceRequest.requester | | MUST | 0..1 | |
| ServiceRequest.requester.reference | This MUST be populated with a reference to the Practitioner resource. This is the Healthcare Professional making the request. This does not strictly need to be a clinician. | MUST | 0..1 | urn:uuid:8c63d621-3424-4f57-8699-e8e22d32423g |
| ServiceRequest.performer | | MUST | 0..* | |
| ServiceRequest.performer.reference | This MUST be populated with a reference to Device resource e.g. eRS which will act as a broker. The Sender is not choosing the final healthcare service destination but offering options for the broker to resolve with the patient/client | MUST | 0..1 | urn:uuid:f014ff0a-f352-4b7d-9c22-171389875ab9 |
| ServiceRequest.performer.reference | This MUST be populated with a reference to Device resource e.g. e-RS which will act as a broker. The Sender is not choosing the final healthcare service destination but offering options for the broker to resolve with the patient/client | MUST | 0..1 | urn:uuid:f014ff0a-f352-4b7d-9c22-171389875ab9 |
</details>
<p>
<p>
Expand Down Expand Up @@ -390,7 +390,7 @@ This payload is used to transmit all the necessary information that is required
| Device.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 |
| Device.status | This MUST be populated with 'active' - Fixed Value | MUST | 1..1 | active |
| Device.deviceName | | | | |
| Device.deviceName.name | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | eRS |
| Device.deviceName.name | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | e-RS |
| Device.deviceName.type | This MUST be populated with 'user-friendly-name' - Fixed Value | MUST | 1..1 | user-friendly-name |
| Device.owner | | MUST | 1..1 | |
| Device.owner.reference | This MUST be populated with a reference to the Patient | MUST | 1..1 | urn:uuid:9589fb37-87a2-48d8-968f-b371429208a8 |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,12 @@ TOPIC: APP8-ScopeAndRequirements
## {{page-title}}

### Scope Overview
This BaRS Application (Referrals from Advice and Guidance to eRS broker, Application 8) supports the following use case(s) ONLY:

This BaRS Application (Referrals from Advice and Guidance to e-RS broker, Application 8) supports the following use case(s) ONLY:
* Advice and Guidance to electronic-Referral Service (e-RS)
* 111Online to electronic-Referral Service (e-RS)
* NHS.UK to electronic-Referral Service (e-RS)



The payload and workflow have been designed to support these services. Other {{pagelink:applications, text:BaRS Applications}} offer scope for alternative use cases.

### Functional Scope
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ topic: design-core-1.4.0
</thead>
<tbody>
<tr>
<td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Core/1.3.1" target="_blank">v1.3.1</a></td>
<td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Core/1.4.0" target="_blank">v1.4.0</a></td>
<td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.10.0" target="_blank">v1.10.0</td>
<td><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.4.0" target="_blank">v1.4.0</a></td>
</tr>
Expand All @@ -22,7 +22,7 @@ topic: design-core-1.4.0
</div>


# BaRS Core 1.3.1
# BaRS Core 1.4.0

BaRS consists of BaRS Core that provides a core set of functionality and BaRS Applications that provide distinct functionality for each use case.

Expand All @@ -31,7 +31,7 @@ You will find here a set of documentation, specifications and services that desc
<details>
<summary>> <b class="barslink">Expand for full Core directory</b></summary>

&bull; {{pagelink:design-core-1.4.0 , text: Core 1.3.1}}</br>
&bull; {{pagelink:design-core-1.4.0 , text: Core 1.4.0}}</br>
&nbsp;&nbsp;&bull; {{pagelink:core-EndToEndWorkflow-1.4.0 , text:End to end workflow}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.4.0 , text:Service Discovery}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-EndToEndWorkflow-BaRSAuth-1.4.0 , text:Authenticate with BaRS}}</br>
Expand Down Expand Up @@ -243,7 +243,7 @@ For more detail please visit the {{pagelink:core-StandardPattern-document-refere
<div markdown="span" class="alert alert-warning" role="alert"><i class="fa fa-warning"></i><b> Important: Versioning information - Preview</b>
<p>

This version of core is strictly a preview of what is currently in development for 1.3.1 and should not be built against.
This version of core is strictly a preview of what is currently in development for 1.4.0 and should not be built against.

</div>

Expand Down
Loading