Skip to content

Commit d19a1e6

Browse files
luci-daviesluci-davies
committed
Fixes from testing
1 parent 58ffaed commit d19a1e6

4 files changed

Lines changed: 13 additions & 11 deletions

File tree

‎guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@
33
Product Link | Version | Handle | Phase | State | Release Date | Stability | Change Log Link
44
-----------------------|---------|---------|----------|-----------------|--------------|------------|-----------------
55
Implementation Guide | 1.10.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-General}}
6-
[FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.35.0) | 1.37.0| v1 | Live | Current Release | 12/11/2025 | Stable |
6+
[FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.37.0) | 1.37.0| v1 | Live | Current Release | 12/11/2025 | Stable |
77
{{pagelink:design-core-1.3.1, text:BaRS Core}} | 1.3.1 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-core, text: BaRS Core Change Log}}
8-
[API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_3_0) | 1.3.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-api}}
8+
[API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1.3.0) | 1.3.0 | v1 | Live | Current Release | 02/07/2025 | Stable |{{pagelink:trn-api}}
99
{{pagelink: build-testing, text: TKW}} | 1.0.19 | v1 | Live | Current Release | 28/03/2025 | Stable |{{pagelink:trn-tkw}}
1010
{{pagelink:application1, text:BaRS-APP1}} | 2.0.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-app1,text:BaRS APP1 Change Log}}
1111
{{pagelink:application2, text:BaRS-APP2}} | 2.0.0 | v1 | Live | Current Release | 12/11/2025 | Stable |{{pagelink:trn-app2,text:BaRS APP2 Change Log}}

‎guides/Live-ImplementationGuide-BaRS/Home/Assure/Assure/Assure.page.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ The assurance process ensures solutions adhere to the Standard and are compatibl
66

77
The purpose of assurance is to:
88
* Validate conformance to the requirements and specifications of the Standard
9-
* Assess higher-risk and/or complex workflow scenarios, to ensure technical and clinical readiness
9+
* Assess higher-risk and/or complex workflow scenarios, ensuring patient safety and technical and clinical readiness
1010
* Serve as a final quality assurance checkpoint prior to deployment to Production
1111

1212
There are limitations to this (self) assurance process, which does **not** extend to:
1313
* Validation of every individual workflow scenario or minor message variation within an assured solution
14-
* Review of all message content against the Standard, either visually or through tooling. This **must** be included in supplier's functional testing
14+
* Review of all message content against the Standard, either visually or through tooling. This **must** be included in the supplier's functional testing
1515
* Regression testing of supplier solution to ensure that existing functionality has not been adversely affected

‎guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-receiver.page.md‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ BaRS uses TLS-MA to communicate with Receiving endpoints. Receiving endpoints ne
1111

1212
### How to connect to the BaRS proxy as a Receiver:
1313

14-
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.
14+
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 domain names visible only on the public internet
1515

1616
Step 2: Request a certificate under the NHS Root CA. The FQDN must be an nhs.uk address.
1717
There are different certificate chains for INT and PROD:
@@ -30,6 +30,7 @@ Create the *.csr, use the following command:</br>
3030
openssl req -new -key private.key -out request.csr
3131
```
3232
**Note:** <small>_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._</small>
33+
3334
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:
3435

3536
<br>
@@ -60,21 +61,22 @@ Step 3: Email <england.bookingandreferralstandard@nhs.net> with Receiver URL for
6061
Step 1: Send the .csr to <dir@nhs.net>, indicating this is for a BaRS Receiver endpoint
6162

6263
Formats for FQDN on PROD:
64+
6365
* Supplier hosted (multi-tenanted) solutions ‘**BaRS-PROD-\<ODS Code\>.\<Supplier name\>.thirdparty.nhs.uk**’
6466

65-
* Service Provider hosted (on-premise) solutions‘**BaRS-PROD-\<ODS Code\>.\<Provider name\>.nhs.uk**’
67+
* Service Provider hosted (on-premise) solutions ‘**BaRS-PROD-\<ODS Code\>.\<Provider name\>.nhs.uk**’
6668

6769
Step 2: Receive certificate from DIR Team
6870

6971
Step 3: Email <england.bookingandreferralstandard@nhs.net> with Receiver URL for BaRS/API-M to add to the Endpoint Catalogue
7072

71-
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.
73+
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.
7274

7375
<br>
7476

7577

7678
#### Installing and configuring your application to use the certificate
77-
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).
79+
Step 1: INT and PROD copy the cert text including `-----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).
7880

7981
Step 2: Create a .pfx file so you can serve HTTPS (TLS) endpoints. You can use the command below to export a *.pfx file from the *.key file you made earlier (when you made the *.csr file) along with the *.cer file you were emailed.
8082

@@ -86,7 +88,7 @@ Step 3: Create a password for your .pfx file.
8688

8789
Step 4: Make configuration changes to reference the *.pfx file and password
8890

89-
(C# example, Other launguages will vary but be similar)
91+
(C# example, Other languages will vary but be similar)
9092

9193
``` c#
9294

‎guides/Live-ImplementationGuide-BaRS/Home/Build/Testing-and-Environments/Connect-as-a-sender.page.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ topic: connect-as-a-sender
44

55
## {{page-title}}
66

7-
API-M provides the [security model](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication) for BaRS.
7+
APIM provides the [security model](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication) for BaRS.
88

99
To connect to the BaRS proxy as a sender follow these steps:
1010

11-
Step 1: follow the NHS Developer authenitication and authorisation process [NHS Developer authentication and authorisation](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/user-restricted-restful-apis-nhs-login-separate-authentication-and-authorisation#step-1-register-your-application-with-nhs-login)
11+
Step 1: follow the NHS Developer authentication and authorisation process [NHS Developer authentication and authorisation](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/user-restricted-restful-apis-nhs-login-separate-authentication-and-authorisation#step-1-register-your-application-with-nhs-login)
1212

1313
Step 2: trust the Certificate Authorities (CA) mentioned below. For INT this will be downloadable from http://pki.nhs.uk/int/G2/auth/NHSINTAuthG2.crt
1414
( you can examine the .cer file if you have one )

0 commit comments

Comments
 (0)