Non-functional test environment

The non-functional test environment is available for use by suppliers to perform specific messaging integration testing.

This environment is only available by special request. Please email: [email protected]

What the non-functional test environments should not be used for

The non-functional test environments do not:

• replace the EMT environments as formal test and assurance environments
• provide right of access to any other environments during environment downtime or any other form of unavailability

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. register the messaging product using a Manufacturer, product and version (MPV) form if required
4. 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
5. register your Fully Qualified Domain Name (FQDN) with the NHS DNS team

There are no entry criteria for the non-functional test environment beyond having suitable test data available.

All endpoints and MPV requests will be processed in the integration environment and will replicate to the non-functional test environment.

A full list of URLs and associated IP addresses are provided below to help you connect to the non-functional test environment. 

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

The following IP addresses/ports need to be configured on the end user firewalls to form outbound firewall rules allowing endpoints to send messages from the development environments.

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.58.0/24 to ports 636 (LDAP) and 443 (sbapi and gas).  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. 

The Party Key for Spine is YES-0000806

The following IP addresses/ports need to be configured on the end user firewalls to form inbound firewall rules allowing endpoints to receive messages from development environments.

Use the RootCA and SubCA certificates in the integration environment to establish a chain of trust.

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. There are no Spine core applications for example, Summary Care Record application (SCRa) or Demographic Spine Application (DSA) available in the non-functional test environment. 

Spine Mini Service Provider

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

Spine Secure Proxy

The Spine Secure Proxy provides an access control layer required by certain programs where patient data may be made accessible to certified users and systems.