Update guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md

accepted

Co-authored-by: luci-davies <lucinda.davies5@nhs.net>

Author: cda69

guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP8/How-does-it-work.page.md

@@ -24,7 +24,7 @@ To aid the workflows for this Application of the Standard the operations that ne
 
 The referral request is directed to a broker in this Application, rather than directly to the healthcare service expected to engage with the patient. The broker negotiates the next step in the patient’s care journey, offering optional healthcare services and allowing them to choose how to proceed. Service discovery still occurs during the assessment, undertaken by the Sender, but, instead of selecting a service at this stage, selection happens later in the workflow with the broker.
 
-The Sender will establish the patient need, prepare a shortlist of healthcare services to support them and package these in the referral request. The request is sent from the Sender to the broker (Receiver) and then onto the selected healthcare service (through [e-RS](https://digital.nhs.uk/services/e-referral-service) ). 
+The Sender will establish the patient need, identify a specific service or prepare a shortlist of healthcare services to support them, and package these in the referral request. The request is sent from the Sender to the broker (Receiver) and then onto the selected healthcare service (through [e-RS](https://digital.nhs.uk/services/e-referral-service) ). 
 
 Directing the referral request will still engage the same BaRS mechanisms; utilising the NHSD-Target-Identifier. However, the Receiver is a consistent, known entity, rather than dynamically established during workflow.