Skip to main content

Development environments

Find out how to connect to the development environments, services available, build version, maintenance slots and scheduled changes.

Page contents

How the development environments should be used

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

How to connect to the environment

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: [email protected])
  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: [email protected]
  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: [email protected] 

Connection information

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.

Portal URLs

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

Description URL DNS name IP address Port
Used for the CSA service https://nww.dev.spine2.ncrs.nhs.uk/summarycarerecord nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Used for self service https://nww.dev.spine2.ncrs.nhs.uk/spineselfservice nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Used for the alert service https://nww.dev.spine2.ncrs.nhs.uk/spinealertservice nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Used for the DSA service https://nww.dev.spine2.ncrs.nhs.uk/demographicspineapplication nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Used for the ETP admin service https://nww.dev.spine2.ncrs.nhs.uk/prescriptionsadmin nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Used for the SRS service https://nww.dev.spine2.ncrs.nhs.uk/spinereportingservice nww.dev.spine2.ncrs.nhs.uk 10.239.14.24 TCP 443
Portal page with links used to access Spine Core and CIS applications https://portal.vn03.national.ncrs.nhs.uk portal.vn03.national.ncrs.nhs.uk See system URL section below TCP 443

System URLs

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.57.0/24 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. 

Description URL DNS name IP address Port

This is the LDAPS protocol service to the directory.

This is a service used by other services accessing the SPINE for directory lookups.

ldaps://ldap.vn03.national.ncrs.nhs.uk/<LDAP QUERY>

<LDAP QUERY> - the query to the directory may be contained within the URL

ldap.vn03.national.ncrs.nhs.uk

 see above TCP 636
This name exists for Smart Card authentications from the PC and is not a user service

Client Side GAC URL:

https://gas.vn03.national.ncrs.nhs.uk/login/authactivate

https://gas.vn03.national.ncrs.nhs.uk/login/authlogout

Server Side GAS URL:

https://gas.vn03.national.ncrs.nhs.uk/login/authvalidate

 gas.vn03.national.ncrs.nhs.uk see above TCP 443

Used to access ID server and is not a user based service.

These URLs will only be used by application developers and are included here for completeness - this URL is case sensitive

Naming Service:

https://sbapi.vn03.national.ncrs.nhs.uk/amserver/namingservice

Role Assertion:

https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleAssertion

 sbapi.vn03.national.ncrs.nhs.uk see above TCP 443

Messaging URLs

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. 

Description URL DNS name IP address Port

Used for all domain synchronous messaging

This is also the service entry point for NN4B messages

 https://msg.dev.spine2.ncrs.nhs.uk/sync-service msg.dev.spine2.ncrs.nhs.uk 10.239.14.29 TCP 443
Used for all domain reliable messaging. https://msg.dev.spine2.ncrs.nhs.uk/reliablemessaging/reliablerequest msg.dev.spine2.ncrs.nhs.uk 10.239.14.29 TCP 443
Used for all domain unreliable messaging https://msg.dev.spine2.ncrs.nhs.uk/reliablemessaging/queryrequest msg.dev.spine2.ncrs.nhs.uk 10.239.14.29 TCP 443
Used for all domain intermediary messaging https://msg.dev.spine2.ncrs.nhs.uk/reliablemessaging/intermediary msg.dev.spine2.ncrs.nhs.uk 10.239.14.29 TCP 443

Used to access the gazetteer postcode look up service

Gazetteer is a web service so will be called by other applications using this URL. This is not a user service

 https://msg.dev.spine2.ncrs.nhs.uk/addressfinder/query msg.dev.spine2.ncrs.nhs.uk 10.239.14.29 TCP 443

Used for all SMSP messaging.

Now uses TLS1.2

 https://simple-sync.dev.spine2.ncrs.nhs.uk/smsp/pds simple-sync.dev.spine2.ncrs.nhs.uk 10.239.14.39 TCP 443
Used for all SMSP messaging.
Now uses TLS1.2		 https://proxy.dev.spine2.ncrs.nhs.uk/[provider service root url]/[fhir request] proxy.dev.spine2.ncrs.nhs.uk 10.239.14.34 TCP 443
Used for internet facing messaging 

https://msg.devspineservices.nhs.uk

https://proxy.devspineservices.nhs.uk

https://simple.devspineservices.nhs.uk

msg.devspineservices.nhs.uk

proxy.devspineservices.nhs.uk

simple.devspineservices.nhs.uk

 Varies TCP 443

Outbound Network Address Translation (NAT) addresses

Local firewall administrators should allow communication from these IP addresses.

Description URL DNS name IP address Port

All messages will be sent out as coming from msg-out.dev.spine2.ncrs.nhs.uk

Nothing will ever be sent to this domain name. This is included for clarity and firewall rules only

 No URL msg-out.dev.spine2.ncrs.nhs.uk 10.239.14.104 TCP 443

Outbound token events to registered listeners will be sent from this address

Nothing will ever be sent to this domain name. This is included for clarity and firewall rules only

CIS will respond on the port number specified by the client request

 No URL Not applicable 10.239.57.0/24 Any

Spine application URLs

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

Area URL

Summary Care Record (SCR)

https://nww.dev.spine2.ncrs.nhs.uk/summarycarerecord/

SCR 1-Click

http://nww.dev.spine2.ncrs.nhs.uk/oneclickscr/LSPValidator.jsp

SAML

https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleAssertion

EPS Prescription Tracker

https://nww.dev.spine2.ncrs.nhs.uk/prescriptionsadmin/

Care ID Service (Smartcard Management)

https://uim.vn03.national.ncrs.nhs.uk/urswebapp/

End Point Registration Service (EPR)

https://uim.vn03.national.ncrs.nhs.uk/eprwebapp/

Spine Reporting Service

https://nww.dev.spine2.ncrs.nhs.uk/spinereportingservice/

Demographic Spine Application (DSA)

https://nww.dev.spine2.ncrs.nhs.uk/demographicspineapplication/

TES Alert Viewer

https://nww.dev.spine2.ncrs.nhs.uk/spinealertservice/

Development NHS e-Referral Service (e-RS) URLs

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

ERSDEV

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.

Description URL DNS name IP address Port
Professional webapp

https://dev-ers.nhs.uk/

dev-ers.nhs.uk

 Variable TCP 443
Patient Webapp https://dev-refer.nhs.uk/ dev-refer.nhs.uk/ Variable

TCP 433

ERSALPHA

The party key is: YEF-820397

The Accredited System ID (ASID) is: 200000000296.

The ERSALPHA environment can only be used at the invitation of NHS England for specified pre-release testing. Connection details will be sent with invitations when required. 

 

RootCA and SubCA Certificates 

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'

RootCA (NHS PTL Root)

-----BEGIN CERTIFICATE-----
MIIDgjCCAmqgAwIBAgIEXR9LkDANBgkqhkiG9w0BAQsFADA8MQwwCgYDVQQKEwNu
aHMxCzAJBgNVBAsTAkNBMR8wHQYDVQQDExZOSFMgUFRMIFJvb3QgQXV0aG9yaXR5
MB4XDTE5MDcwNTEyMzcyOFoXDTM5MDcwNTEzMDcyOFowPDEMMAoGA1UEChMDbmhz
MQswCQYDVQQLEwJDQTEfMB0GA1UEAxMWTkhTIFBUTCBSb290IEF1dGhvcml0eTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJkUOEvituvw0SSmU4adXDnP
SXiaLsQb8CPZwLylSYqumfIzSjsxkktJsekegF6ybtGRMPWW+zBXMI15C3cT+tn8
gpCNYyn1P8/+oNgxtqTLYjxackfU6S8AL+6d39grDd6PlI5ILvCZko82m23cUx2y
2aRnpAIBgDk518tWLTZbMuM14bza/QvYVeX5DqW9gsz947opb6FYRe3MjeHiQmxq
GvWfPY/yb/cggo5y8m2fTQa6dencHeFwnmwbX6nwbrFx8UXzflD0Yke4i5Z2NN4C
xmgAqtxSu5Bz9f7ZQLPPBT5FL+pvxkAu4cEHma4JDD3KayhxzxigKbQcnQpXWEcC
AwEAAaOBizCBiDArBgNVHRAEJDAigA8yMDE5MDcwNTEyMzcyOFqBDzIwMzkwNzA1
MTMwNzI4WjALBgNVHQ8EBAMCAQYwHwYDVR0jBBgwFoAUz4gDrKnt3tEACoCAAEC4
A4jIkFIwHQYDVR0OBBYEFM+IA6yp7d7RAAqAgABAuAOIyJBSMAwGA1UdEwQFMAMB
Af8wDQYJKoZIhvcNAQELBQADggEBAJU06JOPpBMgj/Owzd2aDDIlzEjHDyBx0UOa
xcIeeAT/ByYkTuPees9b5vsPmUwVuNzKscChQ9tvuugPPoTu9gXQfLldKTLlPqOf
+VCghQhM4H+i9+JyK7iKYN7xdVJLjH0AIgpNLwNN/2pnZ+69dOU4G7W0+NYT4e/w
wDcJSq0fi8dwixDTYU8DkFCfEyahEqeuNPp9X3ddWZryq3XjbR3n0YA1sUmnuwiT
ruMNXR0m34pt0nFLQFz57+dLWhAsB5xQdLPc1AuWwK/R8jnHh3+Q/RXOnXG4NNmn
RKYUDjLpFTnWmiZfGyX6edIrjN72M3Guu5cAs0pD/2d6QFsp1Dg=
-----END CERTIFICATE-----

SubCA (NHS DEV Level 1C)

-----BEGIN CERTIFICATE-----
MIIDrzCCApegAwIBAgIEXR9MizANBgkqhkiG9w0BAQsFADA8MQwwCgYDVQQKEwNu
aHMxCzAJBgNVBAsTAkNBMR8wHQYDVQQDExZOSFMgUFRMIFJvb3QgQXV0aG9yaXR5
MB4XDTE5MDcxMjEzNDgyNVoXDTI5MDcxMjE0MTgyNVowNjEMMAoGA1UEChMDbmhz
MQswCQYDVQQLEwJDQTEZMBcGA1UEAxMQTkhTIERFViBMZXZlbCAxQzCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBAKdTQFJTAhjZ/+GdqkS6yE47xSF0VC8H
3ktAISj5BWmm+73vJtAioTm1s9TocR5+mQ4olZNnJ4vX0Z+Wc3QOq4/4ZLMb/nOO
mBcWsIABbsNoSwVKu9MbxtXNtSuxMt0biAWx2t9BLiHJDTtPG149K+b+RIyd0x3y
ZRypP3JTr1+hPq14GG2+aGMBTXwPnglWfpXIdv8p/PU2P/ka8y4bwjMGtBB3iE3O
H1jxk70RO+UcLBCcftRZJ4AAKCxohBjf7z31gx50Lp9Y+Dcooae3P51McOmpFd8y
/YTn/YTFaYHMlVHoO8rYcYJswcBtpa+H+ON7fvaEYtLAgH/GGNlkecUCAwEAAaOB
vjCBuzBeBgNVHR8EVzBVMFOgUaBPpE0wSzEMMAoGA1UEChMDbmhzMQswCQYDVQQL
EwJDQTEfMB0GA1UEAxMWTkhTIFBUTCBSb290IEF1dGhvcml0eTENMAsGA1UEAxME
Q1JMMTALBgNVHQ8EBAMCAQYwHwYDVR0jBBgwFoAUz4gDrKnt3tEACoCAAEC4A4jI
kFIwHQYDVR0OBBYEFF7z2lL2Ai7amiZSUf9JNcgMdw12MAwGA1UdEwQFMAMBAf8w
DQYJKoZIhvcNAQELBQADggEBACOcohf06LEnxo8JlemqDnOYRxixoXAHwf256Yzr
0/NbpltYXMlYE2jJg3ldsZFYsNxP5ysizxgrkW4B6oRBjhqvAZlSzYEiUsEP2LDA
8UpmDdX3XurB/OGRDuqxSqoqezEHpaTs0ERpkTZdZL/kYQED6+N7mQcUWZrPYYvv
ANa1z5PZuAFIezskfOfFIuzWws/2V0SCCxfUyoLizVH55Wp6ETYmGA28R5tUXsWk
GAH4zSEDczXJkdHwK3sXYyqjjUAyQcGwcknK+DyUYube3S9lzORgU82lI1W+cjFq
NTZjuJNqIkoGR0YTIpylcAGayVQ2OP5Snt2PpyI0QoA3PHU=
-----END CERTIFICATE-----

Message Exchange for Social Care and Health (MESH) keystore files to download

MESH is no longer supported in the Development environment, please use the Integration or Deployment environments instead.

Registry settings required to connect to the spine development environments 

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.

Registry File HSCIC Identity Agent 2 (64-bit) Spine Development

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HSCIC\Identity Agent]
"ActivatePOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authactivate"
"LaunchAppsPath"="https://portal.vn03.national.ncrs.nhs.uk"
"MobilityPersistence_Available"="False"
"SessionLockPersistence_Enabled"="False"

Registry File HSCIC Identity Agent 2 (32-bit) Spine Development

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\HSCIC\Identity Agent]
"ActivatePOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authactivate"
"LaunchAppsPath"="https://portal.vn03.national.ncrs.nhs.uk"
"MobilityPersistence_Available"="False"
"SessionLockPersistence_Enabled"="False"

Registry File HSCIC Identity Agent 1 (64-bit) Spine Development

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HSCIC\Identity Agent]
"ActivatePOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authactivate"
"RoleSelectionGETPOSTURL"="https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleSelectionGP.jsp"
"LogoffPOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authlogout"
"LaunchAppsPath"="https://portal.vn03.national.ncrs.nhs.uk"

Registry File HSCIC Identity Agent 1 (32-bit) Spine Development

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\HSCIC\Identity Agent]
"ActivatePOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authactivate"
"RoleSelectionGETPOSTURL"="https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleSelectionGP.jsp"
"LogoffPOSTURL"="https://gas.vn03.national.ncrs.nhs.uk/login/authlogout"
"LaunchAppsPath"="https://portal.vn03.national.ncrs.nhs.uk"

Registry File BT Identity Agent (IA13) Spine Development

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Gemplus\GAC]
"Activate.URL"="https://gas.vn03.national.ncrs.nhs.uk/login/authactivate"
"Logout.URL"="https://gas.vn03.national.ncrs.nhs.uk/login/authlogout"
"Authentication.StartBrowser.Url"="https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleSelectionWT.jsp?token=<SSO_TICKET>"
"Device.id"="1ef2f9cc"
"UpdateWatcher.enable"=dword:00000000
"Device.id.URL"="https://sbapi.vn03.national.ncrs.nhs.uk/ssb/DeviceIDLogger?ipaddress=<IP_ADR>&latestdeviceid=<DEVICE_ID>&storeddeviceid=<OLD_DEVICE_ID>&token=<SSO_TICKET>"
"Authentication.StartBrowser.Url"="https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleSelectionWT.jsp?token=<SSO_TICKET>"
"RoleSelection.URL"="https://sbapi.vn03.national.ncrs.nhs.uk/saml/RoleSelectionGP.jsp?token=<SSO_TICKET>&selectedRoleUid=<ROLE_UID>&ssbMode=<MODE>&gacVersion=<GAC_VERSION>&fallbackStatus=<FALLBACK>"
"Portal.URL"="https://portal.vn03.national.ncrs.nhs.uk"

Services available in the development environments

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)

MESH is no longer supported in the Development environment, please use the Integration or Deployment environments instead.

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. 

Smartcard services

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: [email protected]

Environment build versions

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

Maintenance slots and scheduled changes

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)

Last edited: 11 April 2024 8:55 am