A008 API – Service ID Setup and INT Environment Access Clarification

e-Referral Service (e-RS) e-Referral Service FHIR API
,
1

Hi Team,

We are currently working on the A008 API and have reached the stage where we are receiving the error:

“Service ID does not exist”

We are currently using a test Service ID; however, this is not working, so we require guidance on how to set up and manage Service IDs correctly.

We would also appreciate some clarification regarding access to the Integration Test (INT) environment, as we do not currently have an authentication method such as smartcards or security keys.

Could you please advise on the following:

  1. Do we need a separate login/account with the appropriate role (e.g. Service Definer) in order to create and manage Service IDs?

  2. Is the developer account created during the initial onboarding process sufficient, or is additional access required?

  3. Do we need to complete the below Integration Test Environment access form before the necessary permissions can be granted and Service IDs created?

    Access to e-RS FHIR API Integration test environment - NHS England Digital

We would be grateful for any guidance on the correct process and next steps.

Thank you for your assistance.

2

Hello,

We can help with that. Based on the information provided in your form, which you do not need to resubmit, I believe you intend to use security keys. I can see our team did previously send an instruction to the ITOC team for this to be setup for you, did this not happen?

If this hasn’t happened, the ITOC team will be able to further assist. We will send an email with you copied in tomorrow, and they will arrange a short call to bind your profile to your UUID. Once this has been completed, you will be able to access the INT web application.

You will then have the Service Definer role, which will allow you to create and configure services in whatever way best meets your needs. If you require support with service configuration, we would recommend contacting your local e-RS team.

Once your access is in place, you will also be able to explore the user-restricted API endpoints. Things should become much clearer once you have access to the web application and can see how the different components fit together.

3

being address via email/ITOC