NEMS is available in Opentest for testing of subscribe message formats using the Toolkit Workbench (TKW).
You do not need access to MESH in Opentest for NEMS testing in Opentest.
Successful validation of subscribe messages in Opentest allows you to proceed to integration testing. For details, see the NEMS onboarding guide.
NEMS is also available for testing purposes in:
- development (DEV)
- integration (INT)
- deployment (DEP)
The base URLs are as follows:
Environment |
Network availability |
URL |
OpenTest |
OpenVPN |
https://msg.opentest.hscic.gov.uk/ |
Development |
HSCN |
https://msg.dev.spine2.ncrs.nhs.uk/ |
Integration |
HSCN |
https://msg.int.spine2.ncrs.nhs.uk/ |
Integration |
Internet |
https://msg.intspineservices.nhs.uk/ |
Deployment |
HSCN |
https://msg.dep.spine2.ncrs.nhs.uk/ |
Production |
HSCN |
Contact us |
Production |
Internet |
Contact us |
The base URL for the publishing and subscribing interactions are the same, but the path is different, for example:
- publish in integration over HSCN:
https://msg.int.spine2.ncrs.nhs.uk/STU3/Events/1/$process-message
- subscribe in integration over HSCN:
https://msg.int.spine2.ncrs.nhs.uk/STU3/Subscription
- publish in integration over the internet:
https://msg.intspineservices.nhs.uk/STU3/Events/1/$process-message
- subscribe in integration over the internet:
https://msg.intspineservices.nhs.uk/STU3/Subscription
There is a testing tool which allows you to simulate a provider publishing event messages. You can also simulate making changes on PDS to trigger PDS-published event messages so you can test event message consumption.
To get advice on how to begin testing, contact us.
For more details on getting access to test environments, see the NEMS onboarding guide.