NBRS-4758

Added link for Hazard Log
Added definitions text
Edited typo to improve readability

Author: luci-davies

guides/Live-ImplementationGuide-BaRS/Home/Analysis/Releases/Technical-Release-Notes/TRN-APP8/1.0.0-alpha.3.page.md

@@ -12,6 +12,7 @@ This is a pre-release of v1.0.0-alpha.3 - Referrals into a broker for Healthcare
 | Change                                    | Description                                     | Impact                                                                  | 
 |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------|
 | Patient Identifier Resource | Updates to Referral Payload Implementation Guidance for multiple elements to improve clarity.|<mark style="background-color: Yellow">correction</mark>
+| Scope and Requirements | Minor text changes and link to Hazard Log added|<mark style="background-color: Yellow">correction</mark>
 
 ### Payload Change Log
 

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/Scope-and-Requirements.page.md

@@ -42,21 +42,26 @@ The payload and workflow have been designed to support these services. Other {{p
 - BaRS currently supports the communication of consent for direct care only
 - Certificates for Receiving messages to use nhs.uk domains only
 - Receiving endpoints are to be internet facing
-- Clincial Constraints exist - See Hazard Log
+- Clincial Constraints exist - See [Hazard Log](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/onboarding-support-information#downloads)
 - No element level 'updates' to requests are supported. A new request must be generated to change information in the referral request
 - No digital support to remove or cancel a referral are offered (this would need to be achieved manually)
 - The service discovery tool for establishing services for onward care must be the [e-RS Service Search API A010](https://digital.nhs.uk/developer/api-catalogue/e-referral-service-fhir#post-/STU3/HealthcareService/$ers.searchHealthcareServicesForPatient)
 
 ### Requirements
 
+Definitions used in these requirements:
+- The referral Sender is the system/organisation making the referral request  
+- The referral Receiver is the system/organisation the referral is being sent to, in this specific case - the broker (e-RS)
+- The end user is a person in an organisation using BaRS 
+
 **Service Discovery** 
 - Where more than one service is shortlisted, the maximum number of services allowed on a given shortlist is 20.
 
 **Referral**
 - The referral Receiver **must** accept the referral request regardless of whether the patient is known to the service provider
 - The referral Receiver **must** only accept potential patients who **<ins>have</ins>** a national validated identifier e.g. NHS Number
 - The national identifier  **must** have a [verification status](https://simplifier.net/hl7fhirukcorer4/valueset-ukcore-nhsnumberverificationstatus) of 'Number present and verified'.
-- Any new or existing safeguarding concern, recorded as part of the assessment, **must** be included in the referral Sender's request
+- Any new or existing safeguarding concern, recorded as part of the assessment, **must** be included in the referral request
 - The referral Receiver **must** clearly identify any included safeguarding concern to the end user
 - The referral Receiver **must** accurately represent information made by the Sender to the end user.
 - The referral Sender **must** make available the human readable identifier for the referral, included in the HTTP synchronous response, to the end user