The development environments should be used by suppliers who are implementing the early design, development and system test phases within their own test environment(s) against the Spine Core, Spine Care Identity Service (CIS) and NHS e-Referral Service (e-RS) national systems.

The e-RS Dev1 environment provides e-RS services using the Spine Core development environment for messaging.

The e-RS Dev3 environment is specifically designed for e-RS API development and functionality testing also using the Spine Core development environment for messaging

What the development environments should not be used for

The development environments do not:

• replace the integration environments as the formal integration test environment
• provide right of access to any other environments during environment downtime or any other form of unavailability
• form part of the formal Path to Live - supplier testing in this type of environment is not mandatory for receiving any type of NHS Digital approval for rollout

Before you start

You will need to: 

1. have a connection to the Health and Social Care Network (HSCN) - the secure NHS network (if you do not have a connection or are experiencing problems connecting, contact your network provider)
2. request access to test data (email: testdata@nhs.net)
3. request smartcards if required - you must have a valid smartcard to user certain services, including the Care Identity Service (CIS) - if you do not have a valid smartcard please email: platforms.supportdesk@nhs.net
4. register the messaging product using a Manufacturer, product and version (MPV) form if required 
5. register your message handling service with the Spine by requesting an endpoint (an authorised connection to Spine) to be created unless you have an endpoint administrator in your organisation who can do this for you - please complete the endpoint admin access request form (epr) to manage your own endpoints
6. register your Fully Qualified Domain Name (FQDN) with the NHS DNS team
7. download Identity Agent Client software 

More detailed guidance of the connection process

Additional guidance to support the connection process

Further assistance

Contact us for further assistance. Email: platforms.supportdesk@nhs.net 

A full list of URLs and associated IP addresses are provided below to help you connect to the development environments.

Local firewall administrators should allow communication to the IP addresses as necessary using these details.

These are the connection URLs for the Care Identity Service (CIS) portal and associated applications. 

These are the connection URLs for the services required to run or connect to applications. Due to the move of this environment to AWS, the IP addresses of the following are not constant. Customers will need to open their firewalls to the IP address range of 10.239.67.128/25 to ports 636 (LDAP) and 443 (Sbapi, Gas and Dev Portal (see above)).  If you are using hard-coded IP addresses e.g. in a hosts file, you will need modify your application to use the DNS service names. 

These are the messaging URLs for all Spine services.

Spine party key

A party key is a unique reference for a particular organisation and set of contract properties. Several party keys can exist at the same organisation and will start with the Organisation Data Service (ODS) code.

For the development environment, the party key is: YES-0000806.

All messaging properties should be obtained from this party key using the Lightweight Directory Access Protocol (LDAP) service URL listed below. 

Local firewall administrators should allow communication from these IP addresses.

This is a full list of URLs for the applications in the development environment.

There are 2 e-RS environments associated with the development environments, Dev1 and Dev3.

Dev1

The party key is: YEU-1808939.

The Accredited System ID (ASID) is: 753468248012. This is a unique reference for a particular system. Different systems may have different ASIDs.

The IP addresses and URLs below are used to access e-RS.

Dev3

The party key is: YEF-820397

The Accredited System ID (ASID) is: 200000000296.

The IP addresses and URLs below are used to access e-RS.

In order to establish connection to the development environments, a chain of trust must be set up using the RootCA and SubCA certificates.

1. Copy the required RootCA or SubCA certificate
2. Open Notepad or similar and paste the certificate - save the file locally with a suitable file name
3. Locate the locally saved text file and change the file extension from .txt to .der
4. Import the certificate into the local trusted certificate store - use the documentation from your software supplier as this may vary between applications

Please note that the:

• RootCA should be placed in 'Trusted Root Certification Authorities' 
• SubCA should be placed in 'Intermediate Certification Authorities'

The following MESH keystore needs to be downloaded and installed as part of the MESH client installation. 

Full details can be found in the MESH client installation pack. The environment specific information required is listed below. The password should have been provided when the MESH mailbox was first requested.

If you have any questions, email: platforms.supportdesk@nhs.net

In order to access the Spine Development environment, changes are required to the user's computer registry.  The exact changes depend on the version of the Identity Agent (IA) Client being used, and whether the operating system is 32-bit or 64-bit. 

1. Copy the relevant text to a Notepad file and save it to your desktop
2. Rename the file, changing the file extension from .txt to .reg
3. Double-click on the file to run it

N.B. You will need administrator access to change registry settings on your computer. If you do not have this you should contact your local support team to run the file for you.

Spine Core Messaging and Spine Core applications

The Spine Core service provides a messaging service that allows certified endpoint message handling systems to query and update data held in the national demographic and prescriptions systems. 

The Spine Core systems also supports the e-RS national systems by providing a messaging interface between e-RS and referrers and providers. Also included in the Spine Core service are the Graphic User Interface (GUI) based Summary Care Record application (SCRa) and Demographic Spine Application (DSA). These allow Spine Core data to be manipulated without a messaging interface.

Spine Mini Service Provider

The Spine Mini Service Provider makes available an interface to submit a limited number of demographic messages in a simple format.

Spine Secure Proxy

The Spine Secure Proxy provides a simpler interface to local systems for demographic messaging, allowing quick recovery of details without the requirements of full integration. Messaging functionality is limited to retrievals and simple trace. Updates are not supported.

Message Exchange for Social Care and Health (MESH)

The Message Exchange for Social Care and Health (MESH) provides a workflow based data transfer service that allows registered users to exchange data between secure mailboxes. It is used to support services such as the transfer of Pathology data between labs and hospitals and electronic discharge notes to community medical teams for patients leaving hospital care.

Care Identity Service (CIS)

The Care Identity Service (CIS) controls user access to data held in the national systems. Users access is via a smartcard and uses Role Based Access Control. Both smartcards and Access control are managed within the CIS application. Certification and management of message handling systems is also managed within the CIS application.

NHS e-Referral Service (e-RS) 

The NHS e-Referral Service (e-RS) combines electronic booking with a choice of place, date and time for first hospital or clinic appointments. Patients can choose their initial hospital or clinic appointment, book it in the GP surgery at the point of referral, or later at home on the phone or online. 

NHS e-Referral Service Application Programming Interface (e-RS API)

The NHS e-Referral Service Application Programming Interface (e-RS API) service allows patient systems to perform clinical actions within the e-RS application via an external API interface. 

You will need a valid smartcard to use certain services including the Care Identity Service (CIS). 

If you do not have a valid smartcard, email: platforms.supportdesk@nhs.net

Current versions of the national system applications deployed in each Path to Live environment.

Although these are the scheduled maintenance slots, check the Forward Change Schedule to find out if any activities are planned to take place outside these scheduled slots.

Maintenance slots 

Spine Core

Tuesday 8pm to Wednesday 6am (weekly)

Spine CIS

Monday 8pm to Tuesday 6am (weekly)

e-RS Dev1

Monday 8pm to Tuesday 6am (the week following the live e-RS release)

e-RS Dev3

Thursday 8pm to Monday 6am (the week following the live e-RS release)

Forward change schedule

Find out details of planned changes and how these will impact on environment availability. 

Change success report

Find out the success status of changes made to the environments.