+
## {{page-title}}
| Change | Description | Impact |
@@ -14,6 +17,8 @@ topic: TRN-Core-1.3.0
| Standard Pattern Cancellation updated | Standard Pattern Cancellation updated to reference the new Find Resource Standard Pattern | Non-breaking |
| Appointment Foundation updated | Appointment Foundation updated to reference the new Find Resource Standard Pattern | Non-breaking |
+
+
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml
index 992406c8..c4319218 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml
+++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml
@@ -1,5 +1,7 @@
- name: Index
filename: Index.page.md
+- name: 1.3.1
+ filename: 1.3.1.page.md
- name: 1.3.0
filename: 1.3.0.page.md
- name: 1.0.7
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md
index fc55201e..95bbe9bf 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/2.0.0.page.md
@@ -16,8 +16,12 @@ This is a major release with a significant change to the Implementation Guidance
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
-| Patient.identifier.extension.valueCodeableConcept.coding.code | Follow UK Core guidance for populating this element | 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 | breaking |
-| Patient.identifier.extension.valueCodeableConcept.coding.display | Follow UK Core guidance for populating this element | 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 | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.code | Follow UK Core guidance for populating this element | 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 | Validation Request |Accommodate NHS No. Requirement | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.display | Follow UK Core guidance for populating this element | 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 | Validation Request |Accommodate NHS No. Requirement | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.code | Follow UK Core guidance for populating this element | 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 | Intermin Validation Response |Accommodate NHS No. Requirement | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.display | Follow UK Core guidance for populating this element | 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 | Intermin Validation Response |Accommodate NHS No. Requirement | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.code | Follow UK Core guidance for populating this element | 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 | Full Validation Response |Accommodate NHS No. Requirement | breaking |
+| Patient.identifier.extension.valueCodeableConcept.coding.display | Follow UK Core guidance for populating this element | 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 | Full Validation Response |Accommodate NHS No. Requirement | breaking |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md
index fd54d14c..66dfcebe 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.6.page.md
@@ -12,6 +12,7 @@ This is a minor "patch" with clarifications to limited areas of the Implementati
|
| FHIR BaRS CodeSystem values added for Location Types | Values for Helimed From and Helimed To added | non-breaking |
| FHIR BaRS CodeSystem value added for Flag Categories | Value for Call Warning added | non-breaking |
+| Updated FHIR Questionnaire and QuestionnaireResponse guidance | Guidance updated to reflect Nature of Call published Questionnaire being removed for beta | non-breaking |
### Payload Change Log
@@ -19,6 +20,9 @@ This is a minor "patch" with clarifications to limited areas of the Implementati
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
|------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------|
| patient.identifier.system | | This SHOULD be populated with the namespace for the Identifier | Update | Referral Request |Implementation Guidance consistent across all applications | correction |
+| QuestionnaireResponse.extension.valueCodeableConcept.text | This SHOULD be populated with the name of the questionnaire responses contained within. | This SHOULD be populated with the name of the questionnaire responses contained within. For the Nature-of-call response this MUST be set to 'Nature of Call (NOC)' | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking |
+| QuestionnaireResponse.questionnaire | Example updated - https://fhir.nhs.uk/Questionnaire/NOC | Example updated - https://fhir.nhs.uk/Questionnaire/PTS | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking |
+| QuestionnaireResponse.questionnaire | Necessity Updated - MUST | Necessity Updated - MAY | Update | Referral Request |Changes to use of QuestionnaireResponse for Nature-of-call | non-breaking |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP1/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP1/Index.page.md
index 7e130353..d56cd154 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP1/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP1/Index.page.md
@@ -20,8 +20,8 @@ topic: Application1
@@ -27,7 +27,13 @@ topic: Application5
-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.
+
Important: Notice for suppliers
+
+ 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.
+
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Payloads-for-Referrals.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Payloads-for-Referrals.page.md
index e670d99a..1692359a 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Payloads-for-Referrals.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Payloads-for-Referrals.page.md
@@ -143,7 +143,7 @@ The level of consent currently supported by BaRS is for 'Direct Care' only. In e
### Questionnaire
A Questionnaire is an organised collection of questions intended to solicit information from patients, providers or other individuals involved in the healthcare domain. They may be simple flat lists of questions or can be hierarchically organised in groups and sub-groups, each containing questions. The Questionnaire defines the questions to be asked, how they are ordered and grouped, any intervening instructional text and what the constraints are on the allowed answers. The results of a Questionnaire can be communicated using the QuestionnaireResponse resource.
-The Questionnaire resource is used to covey the Pre Triage Sieve and Nature of Call (NOC) questions and the potential responses as detailed below:
+The Questionnaire resource is used to covey the Pre Triage Sieve and the potential responses as detailed below:
#### Pre Triage Sieve
| Question | Answer| Code |
@@ -154,14 +154,30 @@ The Questionnaire resource is used to covey the Pre Triage Sieve and Nature of C
| | No|419045004 Loss of consciousness|
|Is their breathing noisy?| Yes| 248573009 Noisy respiration|
| | No| 248573009 48348007 Normal breath sounds|
+|Is their breathing effective?| Yes| 20716004 Respiratory rate normal (finding)|
+| | No| 20716004 Difficulty breathing (finding)|
This is an [example](https://simplifier.net/NHSBookingandReferrals/9749ae76-28f7-4b8a-863f-aba64d19d678/~json) of the Pre triage Sieve questionnaire.
*Only the nationally agreed answers and associated codes in this table are valid to be sent. No locally defined responses can be sent.*
+Nature of call (NOC) responses are not defined in a published Questionnaire but can be sent using a QuestionnaireResponse. See QuestionnaireResponse guidance.
+
+### Questionnaire Response
+The Questionnaire Response resource is used to convey the PTS and NOC responses given by the patient (or their representative).
+
+The extension *questionnaireresponse-reason* **must** be populated to indicate which data is contained within, as outlined in the resource element guidance below.
+
+Using a nested set of *questionnaireResponse.item*, *questionnaireResponse.linkId* and *questionnaireResponse.answer* complex structured data can be generated and processed, by the Sender and Receiver, respectively. The element guidance for this resource below goes into detail but, essentially, the item and linkId can be continually nested to convey various types of information. The item indicates a new answer, linkId **may** correspond with the questionnaire question linkId, forging the relationship between the questionnaire and questionnaireResponse, and answer contains any the value recorded. The *questionnaireResponse.item.answer* datatype **must** correspond with that defined in the *questionnaire.item.answerOption*.
+
+We have published examples of [Pre Triage Sieve](https://simplifier.net/NHSBookingandReferrals/Examples-QuestionnaireResponse-for-PTS/~json) and [Nature of Call](https://simplifier.net/NHSBookingandReferrals/Examples-QuestionnaireResponse-for-NOC/~json) questionnaire responses.
+
+Pre Triage Sieve (PTS) responses will link directly to the associated published Questionnaire, while Nature of Call (NOC) responses are transfered in a QuestionnaireResponse without reference to a published Questionnaire.
+
#### Nature of Call (NOC)
-Nature of call types are nationally agreed by ECPAG for ASTs using both AMPDS and NHS Pathways as their CDSS. Receivers **MUST** be able to process and display NOC types and their associated code for both NHS Pathways and AMPDS NOC types detailed below.
+Nature of call types are nationally agreed by ECPAG for ASTs using both AMPDS and NHS Pathways as their CDSS. Receivers **MUST** be able to process and display NOC types and their associated code for both NHS Pathways and AMPDS NOC types detailed below, as well as locally agreed NOC codes.
+
##### AMPDS NOC Types
| Question | Answer (NOC type)| Code |
@@ -181,11 +197,9 @@ Nature of call types are nationally agreed by ECPAG for ASTs using both AMPDS an
This is an [example](https://simplifier.net/NHSBookingandReferrals/81599e54-c713-4f3e-bca9-90225657f18d/~json) of the Nature of Call questionnaire.
-*Only the nationally agreed answers and associated codes in this table are valid to be sent. No locally defined responses can be sent.*
##### NHS Pathways NOC Types
-
| Question | Answer (NOC type) | Code |
| -------------------------| ------| -------|
|What is the Nature of Call?| Anaphylaxis| ANAP|
@@ -203,20 +217,6 @@ This is an [example](https://simplifier.net/NHSBookingandReferrals/81599e54-c713
This is an [example](https://simplifier.net/NHSBookingandReferrals/81599e54-c713-4f3e-bca9-90225657f18d/~json) of the Nature of Call questionnaire.
-*Only the nationally agreed answers and associated codes in this table are valid to be sent. No locally defined responses can be sent.*
-
-
-
-### Questionnaire Response
-The Questionnaire Response resource is used to convey the PTS and NOC responses given by the patient (or their representative).
-
-The extension *questionnaireresponse-reason* **must** be populated to indicate which data is contained within, as outlined in the resource element guidance below.
-
-Using a nested set of *questionnaireResponse.item*, *questionnaireResponse.linkId* and *questionnaireResponse.answer* complex structured data can be generated and processed, by the Sender and Receiver, respectively. The element guidance for this resource below goes into detail but, essentially, the item and linkId can be continually nested to convey various types of information, as guided by the corresponding questionnaire. The item indicates a new answer, linkId **must** correspond with the questionnaire question linkId, forging the relationship between the questionnaire and questionnaireResponse, and answer contains any the value recorded. The *questionnaireResponse.item.answer* datatype **must** correspond with that defined in the *questionnaire.item.answerOption*.
-
-We have published examples of [Pre Triage Sieve](https://simplifier.net/NHSBookingandReferrals/Examples-QuestionnaireResponse-for-PTS/~json) and [Nature of Call](https://simplifier.net/NHSBookingandReferrals/Examples-QuestionnaireResponse-for-NOC/~json) questionnaire responses.
-
-*Only the nationally agreed answers and associated codes in the associated Questionnaire are valid to be sent in the QuestionnaireResponse.*
### Condition
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Referral-Payload.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Referral-Payload.page.md
index 93188b30..d844892c 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Referral-Payload.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP6/Referral-Payload.page.md
@@ -873,8 +873,8 @@ This payload is used to transmit all the necessary information that is required
| QuestionnaireResponse.extension | | MUST | 0..* | |
| QuestionnaireResponse.extension.url | This MUST be populated with Structure Definition 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-reason' - FIXED VALUE | MUST | 1..1 | http://hl7.org/fhir/StructureDefinition/questionnaireresponse-reason |
| QuestionnaireResponse.extension.valueCodeableConcept | | MUST | 0..* | |
-| QuestionnaireResponse.extension.valueCodeableConcept.text | This SHOULD be populated with the name of the questionnaire responses contained within | SHOULD | 0..1 | Pre Triage Sieve |
-| QuestionnaireResponse.questionnaire | This MUST be populated with the Canonical value of the Questionnaire resource the responses relate to | MUST | 0..1 | https://fhir.nhs.uk/Questionnaire/NOC |
+| QuestionnaireResponse.extension.valueCodeableConcept.text | This SHOULD be populated with the name of the questionnaire responses contained within. For the Nature-of-call response this MUST be set to 'Nature of Call (NOC)' | SHOULD | 0..1 | Pre Triage Sieve |
+| QuestionnaireResponse.questionnaire | This MUST be populated with the Canonical value of the Questionnaire resource the responses relate to | MAY | 0..1 | https://fhir.nhs.uk/Questionnaire/PTS |
| QuestionnaireResponse.status | This MUST be populated with 'completed' - Fixed Value | MUST | 1..1 | completed |
| QuestionnaireResponse.subject | Follow UK Core guidance for populating this element | MUST | 0..1 | |
| QuestionnaireResponse.subject.reference | This SHOULD be populated with a Reference to the Patient resource | MUST | 0..1 | urn:uuid:41e591ab-d333-4fb8-87b4-d35f740b6bfc |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
index 1fda5652..51530c6b 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md
@@ -13,7 +13,7 @@ This page provides a catalogue of implementation guides that have been developed
-These guides are designed to be used in conjunction with the documentation for {{pagelink:design-core-1.0.7}}.
+These guides are designed to be used in conjunction with the documentation for {{pagelink:design-core-1.3.1}}.
@@ -23,7 +23,7 @@ These guides are designed to be used in conjunction with the documentation for {
| {{pagelink:application2, text: Booking and Referrals into UEC (Application 2)}} |
111 Online - ED 111 Online - UTC S&R - ED S&R - UTC
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 549e25c4..a2a604f8 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
@@ -171,6 +171,10 @@ Table detailing active versions of the latest Applications in Production (or cur
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md
index ea3ceb80..a413dd57 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md
@@ -6,6 +6,9 @@ topic: Connect-as-a-receiver
BaRS uses TLS-MA to communicate with Receiving endpoints. Receiving endpoints need a certificate under the NHS Root CA to facilitate TLS-MA. The receiver needs to follow these steps to access Integration (INT) and Production (PROD) environments.
+
+
+
### How to connect to the BaRS proxy as a Receiver:
Step 1: Apply for your domain [apply for a new nhs.uk domain](https://digital.nhs.uk/services/networking-addressing/apply-for-an-nhs.uk-domain-for-websites-and-web-applications). You must complete Section 5: For website or application records visible on the public internet.
@@ -22,13 +25,15 @@ Step 3: Create a Certificate Signing Request (*.csr). This is the file you will
openssl genpkey -algorithm RSA -out private.key -aes256
```
Create the *.csr, use the following command:
-**Note:** _Generate the CSR with only the common name field populated, which must match the FQDN. All other fields can remain blank. The email field MUST be blank. Please note FQDNs MUST be in the .nhs.uk domain as we can only issue certificates in this domain._
+
```
openssl req -new -key private.key -out request.csr
```
-
+**Note:** _Generate the CSR with only the common name field populated, which must match the FQDN. All other fields can remain blank. The email field MUST be blank. Please note FQDNs MUST be in the .nhs.uk domain as we can only issue certificates in this domain._
Step 4: Send the .csr file to be signed by NHS England and get the client certificate. To do this, follow these environment specific steps:
+
+
#### Client certificate: Integration (INT)
Step 1: Contact ITOC to make a [Combined endpoint and service registration request](https://digital.nhs.uk/services/path-to-live-environments/path-to-live-forms/combined-endpoint-and-service-registration-request)
@@ -38,13 +43,16 @@ In the form:
* Select Create/renew a certificate only (No endpoint)
* Specify Integration environment
* FQDN must match your domain and CN on the cert e.g. '**BaRS-INT-\.\.thirdparty.nhs.uk**'
-* In Additional comments/notes, state ‘BaRS’ certificate request
-Add ‘N/A’ in the Party Key field because there is no relation to SDS endpoints
+* In "Additional comments/notes" state ‘BaRS’ certificate request
+*Add ‘N/A’ in the "Existing party key" field because there is no relation to SDS endpoints.
Step 2: Receive certificate from ITOC
Step 3: Email with Receiver URL for BaRS/API-M to add to the Endpoint Catalogue
+
+
+
#### Client certificate: Production (PROD)
**Production endpoints can only be requested when Solution Assurance issue the supplier with the Technical Conformance certificate**
@@ -62,6 +70,9 @@ Step 3: Email with Receiver URL for
Step 4: Make changes to your [firewall exceptions](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Deploy/Technical-deployment\Firewallexceptions) to receive messages from the BaRS proxy.
+
+
+
#### Installing and configuring your application to use the certificate
Step 1: INT and PROD copy the cert text inlcuding `-----BEGIN CERTIFICATE` as the first line and `END CERTIFICATE-----` as the last. Save this text locally as a file called barsinreceiver.cer (change the name to suit).
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md
index 12e944fe..5ba4d947 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md
@@ -14,7 +14,7 @@ The BaRS Proxy uses the ServiceId in the HTTP Header to reference the BaRS Endpo
* 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)
-* Email bookingandreferralstandard@nhs.net with the serviceid and endpoint details. State the environment to be configured, INT or PROD, and include planned dates for testing.
+* Email: with the ServiceId and endpoint details. State the environment to be configured, INT or PROD, and include planned dates for testing.
**Note**: CareConnect configuration must be maintained alongside the BaRS configuration. This is so senders who are not yet BaRS compliant can still work with CareConnect and GP Connect.
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/DirectoryOfServiceConfiguration.md b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/DirectoryOfServiceConfiguration.md
index 7aeda3a1..d113f743 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/DirectoryOfServiceConfiguration.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/DirectoryOfServiceConfiguration.md
@@ -1,6 +1,6 @@
## {{page-title}}
-If the Receiving provider operates within Urgent and Emergency Care (UEC), they are likely to have a UEC Directory of Services (DoS) entry. DoS leads must configure Service Providers who wish to use BaRS in the standard way, as the service dictates, but their DoS ServiceId will also need to exist in the BaRS Endpoint Catalogue.
+Each service delivered by an Urgent and Emergency Care (UEC) provider has an entry in the UEC Directory of Services (DoS). DoS Leads will continue to configure new UEC providers and services in the DoS, issuing each service with a DoS ServiceID. If the provider is going to use receive BaRS messages, the DoS ServiceId will also need to exist in the BaRS Endpoint Catalogue.
Find out more about the [Directory of Service](https://digital.nhs.uk/services/directory-of-services-dos#top)
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Firewallexceptions.md b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Firewallexceptions.md
index 529cbc23..48726ed8 100644
--- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Firewallexceptions.md
+++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Firewallexceptions.md
@@ -1,6 +1,6 @@
## {{page-title}}
-BaRS receivers need to configure firewall exceptions for both Integration and Production environments.
+BaRS receivers need to configure firewall exceptions for both Integration (INT) and Production (PROD) environments.
Requests from the BaRS API Proxy will originate from: