From c0e15f9ea79da5e6ec04d26ebd17bfbbfcdc4ac8 Mon Sep 17 00:00:00 2001 From: Jack Plowman <62281988+JackPlowman@users.noreply.github.com> Date: Wed, 24 Sep 2025 13:53:49 +0100 Subject: [PATCH] NPA-5575: Remove Team Email from spec --- specification/validated-relationships-service-api.yaml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/specification/validated-relationships-service-api.yaml b/specification/validated-relationships-service-api.yaml index b3ee4944..85dfc18f 100644 --- a/specification/validated-relationships-service-api.yaml +++ b/specification/validated-relationships-service-api.yaml @@ -151,11 +151,17 @@ info: * includes authorisation with NHS Login ## Onboarding - You must get your software onboarded before it can go live. - For more details, contact us at [england.vrs-team@nhs.net](mailto:england.vrs-team@nhs.net). + You need to get your software approved by us before it can go live with this API. We call this onboarding. The onboarding process can sometimes be quite long, so it's worth planning well ahead. + + As part of this process, you need to demonstrate your technical conformance to the requirements for this API. + + You also need to demonstrate that you can manage risks. This might impact the design of your software. + + To understand how our online digital onboarding process works, see [digital onboarding](https://digital.nhs.uk/developer/guides-and-documentation/digital-onboarding). ## Contact us + For help and support connecting to our APIs and to join our developer community, see [Help and support building healthcare software](https://digital.nhs.uk/developer/help-and-support). contact: