From 8603d7bded6e9983fc5207b6bda627a09383f3fa Mon Sep 17 00:00:00 2001 From: luci-davies Date: Tue, 28 Oct 2025 13:16:10 +0000 Subject: [PATCH 1/5] Fixes for small bugs identified in testing --- .../Releases/Current-Releases.page.md | 30 ++++++++--------- .../BaRS-APP6/Payloads-for-Referrals.page.md | 2 +- .../Applications/Index.page.md | 31 +++++++++--------- .../BaRS-Pre-releases/Index.page.md | 32 +++++++++---------- .../Environments.page.md | 6 +++- .../DirectoryOfServiceConfiguration.md | 2 +- 6 files changed, 53 insertions(+), 50 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md index 22f21922..d0e85374 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md @@ -65,11 +65,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 1 v1.0.8 - v1.9.0 + v1.9.0 Application 1 v2.0.0 - v1.10.0 + v1.10.0 Application 2 v1.0.1 @@ -93,11 +93,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 2 v1.0.8 - v1.9.0 + v1.9.0 Application 2 v2.0.0 - v1.10.0 + v1.10.0 Application 3 v1.0.0 @@ -109,7 +109,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.2 - v1.8.1 + v1.8.1 Application 3 v1.0.3 @@ -117,11 +117,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.4 - v1.9.0 + v1.9.0 Application 3 v2.0.0 - v1.10.0 + v1.10.0 Application 4 v1.0.0 @@ -133,7 +133,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.1 - v1.8.1 + v1.8.1 Application 4 v1.2.2 @@ -141,11 +141,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.3 - v1.9.0 + v1.9.0 Application 4 v2.0.0 - v1.10.0 + v1.10.0 Application 5 v1.0.0-beta.4 @@ -163,7 +163,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.1 - v1.8.1 + v1.8.1 Application 5 v1.1.2 @@ -171,19 +171,19 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.3 - v1.9.0 + v1.9.0 Application 5 v1.1.4 - v1.10.0 + v1.10.0 Application 6 v1.0.0-beta.6 - v1.10.0 + v1.10.0 Application 7 v1.0.0-alpha.4 - v1.9.0 + v1.9.0 v1.0.0 1.0.0 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 1692359a..23be064b 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 the potential responses as detailed below: +The Questionnaire resource is used to convey the Pre Triage Sieve and the potential responses as detailed below: #### Pre Triage Sieve | Question | Answer| Code | 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 51530c6b..4ca83b96 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 @@ -66,11 +66,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 1 v1.0.8 - v1.9.0 + v1.9.0 Application 1 v2.0.0 - v1.10.0 + v1.10.0 Application 2 v1.0.1 @@ -94,11 +94,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 2 v1.0.8 - v1.9.0 + v1.9.0 Application 2 v2.0.0 - v1.10.0 + v1.10.0 Application 3 v1.0.0 @@ -110,7 +110,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.2 - v1.8.1 + v1.8.1 Application 3 v1.0.3 @@ -118,11 +118,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.4 - v1.9.0 + v1.9.0 Application 3 v2.0.0 - v1.10.0 + v1.10.0 Application 4 v1.0.0 @@ -134,7 +134,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.1 - v1.8.1 + v1.8.1 Application 4 v1.2.2 @@ -142,11 +142,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.3 - v1.9.0 + v1.9.0 Application 4 v2.0.0 - v1.10.0 + v1.10.0 Application 5 v1.0.0-beta.4 @@ -164,7 +164,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.1 - v1.8.1 + v1.8.1 Application 5 v1.1.2 @@ -172,19 +172,19 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.3 - v1.9.0 + v1.9.0 Application 5 v1.1.4 - v1.10.0 + v1.10.0 Application 6 v1.0.0-beta.6 - v1.10.0 + v1.10.0 Application 7 v1.0.0-alpha.4 - v1.9.0 + v1.9.0 v1.0.0 1.0.0 @@ -198,3 +198,4 @@ Table detailing active versions of the latest Applications in Production (or cur + 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 a2a604f8..3e2e2795 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 @@ -63,11 +63,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 1 v1.0.8 - v1.9.0 + v1.9.0 Application 1 v2.0.0 - v1.10.0 + v1.10.0 Application 2 v1.0.1 @@ -91,11 +91,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 2 v1.0.8 - v1.9.0 + v1.9.0 Application 2 v2.0.0 - v1.10.0 + v1.10.0 Application 3 v1.0.0 @@ -107,7 +107,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.2 - v1.8.1 + v1.8.1 Application 3 v1.0.3 @@ -115,11 +115,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.4 - v1.9.0 + v1.9.0 Application 3 v2.0.0 - v1.10.0 + v1.10.0 Application 4 v1.0.0 @@ -131,7 +131,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.1 - v1.8.1 + v1.8.1 Application 4 v1.2.2 @@ -139,11 +139,11 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.3 - v1.9.0 + v1.9.0 Application 4 v2.0.0 - v1.10.0 + v1.10.0 Application 5 v1.0.0-beta.4 @@ -161,7 +161,7 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.1 - v1.8.1 + v1.8.1 Application 5 v1.1.2 @@ -169,19 +169,19 @@ Table detailing active versions of the latest Applications in Production (or cur Application 5 v1.1.3 - v1.9.0 + v1.9.0 Application 5 v1.1.4 - v1.10.0 + v1.10.0 Application 6 v1.0.0-beta.6 - v1.10.0 + v1.10.0 Application 7 v1.0.0-alpha.4 - v1.9.0 + v1.9.0 v1.0.0 1.0.0 @@ -193,5 +193,3 @@ Table detailing active versions of the latest Applications in Production (or cur - - diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md index c66b24ea..63ccfba0 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Environments.page.md @@ -1,6 +1,10 @@ ## {{page-title}} -The principle environment for development and testing is the INT (integration) environment. This is a like-live environment, harnessing full security and functionality that can expect to be encountered in Production. In addition, the [BaRS API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0) links to the Sandbox environment, which is capable of demonstrating the key functionality but without the security overhead. +BaRS Sandbox is available from the [BaRS API specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0). It demonstrates key functionality without the overhead of security requirements, giving developers the opportunity to understand the product before progressing development. + +BaRS Integration (INT) is a live-like environment for suppliers progressing with development and testing to use. To use INT, you will need to follow the instructions to [Connect as a sender](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md) or [Connect as a receiver](https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md). + +BaRS Production (PROD) is the live environment. Suppliers will need to have progressed through assurance before applying to connect to the PROD environment. [Path-to-Live](https://digital.nhs.uk/services/path-to-live-environments#environments) has full details of all available testing environments and the functionality they offer. 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 d113f743..2a422d40 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}} -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. +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 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)
From 05e0d762c7961b9cc42f4d88e928f7b8039fee45 Mon Sep 17 00:00:00 2001 From: luci-davies Date: Tue, 28 Oct 2025 18:45:23 +0000 Subject: [PATCH 2/5] Edits to improve reading --- .../Home/Build/Testing-and-Environments/TKW.page.md | 2 +- .../Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/TKW.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/TKW.page.md index 53fd3a9c..98c2f130 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/TKW.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/TKW.page.md @@ -4,7 +4,7 @@ TKW - Toolkit Workbench - is a tool to assist development and assurance of supplier solutions to meet BaRS (Booking and Referral Standard) requirements. -The tool supports testing of key high-level workflows e.g. a booking routine, including some of asynchronous ones, but is also capable of inspecting low level technical requirements. It reports the output in Validation Reports which clearly indicates to the reader where and why a test has failed. In addition, it supports consistent error states which are often difficult to create but required for development and assurance. +The tool supports testing of key high-level workflows e.g. a booking routine, including some asynchronous ones, and is also capable of inspecting low level technical requirements. It reports the output in Validation Reports which indicate where and why a test has failed. In addition, it supports consistent error states which are often difficult to create but are required for development and assurance. The BaRS TKW tooling is embedded into the INT environment, encompassing all the same end-to-end BaRS infrastructure that is mirrored in Production, rather than being downloaded and used in isolation. This ensures the same steps to deploy solutions to Production are followed during deployment to INT, and allowing testing of requests/responses to occur under Production-like conditions. Similarly, we're able to incorporate other key components, similar to those used in Production workflows, such as the [UserTest Directory of Services (DoS)](https://usertest.directoryofservices.nhs.uk/app/controllers/home/home.php). In the current {{pagelink:Applications, text:BaRS Applications}}, the TKW tool relies on values in the UserTest DoS to elicit particular behavioural responses. The Sender will populate what are termed 'sentinel' values, such as the NHSD-Target-Identifier, with a particular value and TKW will respond with a certain Capability Statement, MessageDefinition etc. (See the 'Scenarios' section for detail). 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 5ba4d947..9485464f 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md @@ -16,6 +16,6 @@ The BaRS Proxy uses the ServiceId in the HTTP Header to reference the BaRS Endpo * 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. +**Note**: CareConnect configuration must be maintained alongside the BaRS configuration. This is to ensure senders who are not yet BaRS compliant can still work with CareConnect and GP Connect.
From 1757a36b949c1d29c39d3f0ace7d6a1cd04bbefd Mon Sep 17 00:00:00 2001 From: luci-davies Date: Wed, 29 Oct 2025 09:53:07 +0000 Subject: [PATCH 3/5] Capitalisation in titles changed to match accessibility guidance --- .../Home/Build/Testing-and-Environments/toc.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/toc.yaml index bff31f33..672497ec 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/toc.yaml @@ -4,9 +4,9 @@ filename: Environments.page.md - name: Connecting to environments filename: Onboarding.page.md -- name: Connect as a Sender +- name: Connect as a sender filename: Connect-as-a-sender.page.md -- name: Connect as a Receiver +- name: Connect as a receiver filename: Connect-as-a-receiver.page.md - name: TKW filename: TKW.page.md \ No newline at end of file From 2eda307c07264d3119ea5d381a2a1f8363021093 Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Wed, 29 Oct 2025 16:14:27 +0000 Subject: [PATCH 4/5] Deploy-Assur-updates Updates to Technical Deployment Guide and Assurance Disclaimer --- .../1.10.0.page.md | 3 ++- .../Home/Assure/Assure/Assure.page.md | 15 +++++++++++++-- .../Connect-as-a-sender.page.md | 13 +++++++++++++ .../Technical-deployment/BaRSEndpointCatalogue.md | 4 ++++ .../Technicaldeployment.page.md | 13 +++++++++++++ 5 files changed, 45 insertions(+), 3 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md index 59f7cd96..181c567f 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/Implementation-Guide-Change-Log/1.10.0.page.md @@ -6,7 +6,8 @@ |---------------------------------------|---------------------------------------------------------------------------------------------------------| | Bug fixes and corrections |There have been several bug fixes and corrections in the guide, these includes typos, broken links or corrections.| | Home page |The heading has been updated to make it clear to users that they are in the BaRS Implementation Guide, quick start guide link has been separated to improve direct navigation and content has been transformed based on user feedback| -| Deploy |New pages for Technical deployment have been added to support suppliers and providers through specific technical steps in their implementation journey. +| Deploy |New pages for Technical deployment have been added to support suppliers and providers through specific technical steps in their implementation journey.| +| Assure |Provided clarity on the expectations and limitation of the assurance process.|
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md index 30e89ab1..2b251b91 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md @@ -1,5 +1,16 @@ ## {{page-title}} -Assurance is central to building a BaRS solution, inherent in both documentation and tooling. +Assurance is central to developing a BaRS compliant solution. -The assurance process exists to ensure solutions are compliant with the Standard and robust enough to interoperate with each other in a Live environment. The rationale for stringent assurance is to ensure solutions who have never engaged before will work with each other. BaRS is a truly interoperable Standard that will work across many areas of the Health & Care space and certain solutions may interact infrequently. \ No newline at end of file +The assurance process exists to ensure solutions adhere to the Standard and are compatible with each other, when they integrate in the Production environment. The compatibility guarantee is essential where interactions exist between systems which have never engaged with each before, something BaRS supports and encourages through dynamic, real-time, service discovery. + +The purpose of assurance is to: +* Validate conformance to the requirements and specifications of the Standard +* Assess higher-risk and/or complex workflow scenarios, to ensure technical and clinical readiness +* Serve as a final quality assurance checkpoint prior to deployment to Production + + +There are limitations to this (self) assurance process, which does **not** extend to: +* Validation of every individual workflow scenario or minor message variation within an assured solution +* Review of all message content against the Standard, either visually or through tooling. This **must** be included in supplier's functional testing +* Regression testing of supplier solution to ensure that existing functionality has not been adversely affected diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md index f21430ca..ef77a61a 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md @@ -16,4 +16,17 @@ Step 2: trust the Certificate Authorities (CA) mentioned below. For INT this wil openssl x509 -in barsintreceiver.cer -text -noout ``` +Step 3: The above steps enables access to the APIM platform. To authorise the access to the BaRS Proxy (which is hosted on the APIM Platform), you must provide the following to the BaRS Team (via email ): +* App Name* +* App ID (PROD)* +* App ID (INT) (both App IDs are needed to connect to PROD)* +* App Description* +* Name of the Organisation +* ODS code of the Organisation +* Product Name (as stated in the SCAL or TCC) +* JWKS resource URL (if self hosting) +* KID for JWKS (if APIM host and defined in earlier steps) +* Public key (if APIM host and generated in earlier steps) + +The starred (\*) items can be found by logging into the [Digital Onboarding Service](https://onboarding.prod.api.platform.nhs.uk) and selecting 'Environment access' under the *Introduction and onboarding* section. \ No newline at end of file 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 5ba4d947..c6fdcf11 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/BaRSEndpointCatalogue.md @@ -1,3 +1,7 @@ +--- +topic: configure-endpoint-catalogue +--- + ## {{page-title}} Every service receiving messages through BaRS will need their ServiceId and endpoint added to the BaRS Endpoint Catalogue. This enables the BaRS Proxy to direct messages to the service. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Technicaldeployment.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Technicaldeployment.page.md index 798d9da7..cddd66d8 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Technicaldeployment.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Deploy/Technical-deployment/Technicaldeployment.page.md @@ -9,5 +9,18 @@ This page is intended as guidance for all parties involved in deployments of BaR

+This is an abbreviated deployment guide, focused exclusively on the technical steps, to connect and configure healthcare Service Providers utilising BaRS. It is aimed at Suppliers and Service Providers (Project Managers, Business Analysts, Application Delivery Specialists, etc.) connecting their solutions to the BaRS Proxy infrastructure and related components. + +* Supplier installs BaRS compliant solution to Sender system environment +* {{pagelink:connect-as-a-sender, text:Connect Sender}} to BaRS Proxy +* Supplier install BaRS compliant solution to Receiver system environment +* {{pagelink:Connect-as-a-receiver, text:Connect Receiver}} to BaRS Proxy +* Identify or create Service profile(s) for the Receiving service(s) on the chosen national or proprietary Directory of Service* +* Provide detail of configured services and systems to BaRS Team to {{pagelink:configure-endpoint-catalogue, text:configure in the Endpoint Catalogue}} +* Test configuration between newly configured systems + +\* If a Sender is to receive an asynchronous response from the Receiver, as part of the defined workflow, they will also require a Service profile. This will need configuration in the {{pagelink:configure-endpoint-catalogue, text:Endpoint Catalogue}} too. + +NB- These steps apply to connecting and configuring systems to both the Integration (INT) and Production (PROD) environment.
From d06ff0d8c5ee74311410d67c5c089d7e7a09f318 Mon Sep 17 00:00:00 2001 From: Carl De'ath <74620667+cda69@users.noreply.github.com> Date: Thu, 30 Oct 2025 09:58:10 +0000 Subject: [PATCH 5/5] updated-Assure-paragraph --- .../Home/Assure/Assure/Assure.page.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md index 2b251b91..5bf5edf9 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md @@ -2,14 +2,13 @@ Assurance is central to developing a BaRS compliant solution. -The assurance process exists to ensure solutions adhere to the Standard and are compatible with each other, when they integrate in the Production environment. The compatibility guarantee is essential where interactions exist between systems which have never engaged with each before, something BaRS supports and encourages through dynamic, real-time, service discovery. +The assurance process ensures solutions adhere to the Standard and are compatible with each other when they integrate in the production environment. This guarantee of compatibility is essential to enable interoperability between healthcare systems, which BaRS supports and encourages through dynamic, real-time, service discovery. The purpose of assurance is to: * Validate conformance to the requirements and specifications of the Standard * Assess higher-risk and/or complex workflow scenarios, to ensure technical and clinical readiness * Serve as a final quality assurance checkpoint prior to deployment to Production - There are limitations to this (self) assurance process, which does **not** extend to: * Validation of every individual workflow scenario or minor message variation within an assured solution * Review of all message content against the Standard, either visually or through tooling. This **must** be included in supplier's functional testing