Hi all. Currently we have got access to EMIS Partner API for multiple organizations with and without HSCN in AWS EC2. For our product, initially we got access to development environment and tested all the API methods and responses without HSCN connection and both outbound and inbound connections worked fine. In the same EC2,currently while integrating with HSCN we are not able to activate our product for the given organization. We are able to install and login in frontend but not backend. We connect to HSCN with Redcentric and they have confirmed that they have allowed all outbound ports in order to activate the product. But we are getting two types of errors
1.When EMIS Web is not opened
Activation screen pops up and if we input login credentials it is not returning activation success screen. We only get this response
(0, ‘0’, ‘EMISWeb API’, ‘3.1’, ‘’, ‘EMIS API Failed When Calling Clinical System , Method InitializeWithID. Error = Unable to Activate Product :Unable to connect to the remote server’, 1, ‘’)
2.When EMIS Web is open
We do not get activation screen. We only get this response
(0, ‘0’, ‘EMISWeb API’, ‘3.1’, ‘’, ‘EMIS API Failed When Calling Clinical System , Method InitializeWithID. Error = Invalid IP Address’, 2, ‘’)
As per the due process, we have activated the application inside EMAS Manager and setup API Passwords also.
Any guidance will be helpful as we are not able to identify the issue since in the same EC2 instance without HSCN everything works, but when connecting through HSCN endpoint only frontend is accessible but not able to activate Partner API. Thanks in advance.
Hi Bhargav,
Sorry for delayed response.
Looks like the issue you are having with the EMIS Partner API activation is probably a problem with your HSCN connection, specifically how it handles egress and source-IP validation. Its most likely your EC2 traffic exits to HSCN via Redcentric, but the NATed source IP seen by EMIS differs from the one they have or isn’t on HSCN.
EMIS does outline that HSCN integration requires correct source-IP allow-listing and NAT setup — refer to documentation in the EMIS Partner Portal where the specific references (activation errors, HSCN requirements, EMAS Manager steps) are officially documented.
You will need to contact the EMIS Partner Team to add/adjust the HSCN source IP allow-list for your Supplier/Products. If an outbound proxy/TLS inspection exists, bypass it for EMIS endpoints.
Additional info:
https://digital.nhs.uk/developer/api-catalogue/interface-mechanism-1-standards
Hope the above help.
Thanks,
NHS England API Platform team
Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.
Hi. Thanks for your reply. We will check this and come back. Thanks for your continuous guidance.