EMIS Partner API activation issue while EMIS Web is working

API Platform
1

Hello,

EMIS Web is working correctly in our environment, however the Partner API is not working for a newly provisioned setup.

While activating the Partner API, we receive the following error:

“EMIS API Failed When Calling Clinical System, Method InitializeWithID – Unable to Activate Product: Unable to connect to the remote server.”

For a previous Partner API integration, access was enabled by allow-listing our public IP and the integration works successfully.
For the current setup, the Partner API is associated with an HSCN connection. From our side, the HSCN connection is active and connectivity testing has been completed successfully.

Network routing and connectivity have been validated, and the same Partner API integration works in an existing environment.

Could you please advise whether any additional Partner API enablement or configuration is required for new environments using HSCN?

We have three EMIS environments hosted on the same system, with the following behaviour:

Environment 1 (Public Internet – EIP allow-listing)

  • EMIS Web is working correctly

  • Partner API access was enabled by allow-listing our EC2 public IP

  • Partner API activated successfully

  • Partner API is working as expected

Environment 2 (HSCN via AWS Direct Connect – Redcentric)

  • AWS Direct Connect to HSCN is configured and active

  • EMIS Web is working correctly

  • HSCN connectivity has been tested successfully

  • During Partner API activation, we receive an error indicating invalid IP / unable to connect

  • Partner API does not activate

Environment 3 (HSCN via AWS Direct Connect – Redcentric)

  • Same architecture and routing as Environment 2

  • EMIS Web works

  • Partner API activation fails in the same way

Thank you for your guidance.

2

Hi Abbas,

Thank you for contacting NHS England API Platform team via the NHSE Developer Community.

Based on what you have described, this issue is not related to the NHS API Platform, and there is nothing additional that API Platform team can help to enable or configure here. This sits squarely within EMIS Partner API provisioning and EMIS-side network controls.

The NHS API Platform does not:

  • Manage EMIS Partner API activation
  • Control EMIS IP validation or allow-listing
  • Control EMIS behaviour over HSCN vs public internet

Looks like Partner API fails only in new HSCN-based environments. In HSCN-connected setups, EMIS typically requires:

  • Explicit HSCN IP allow-listing for Partner API traffic
  • Correct identification of the outbound IP as seen by EMIS over HSCN
  • Environment-specific enablement

To request guidance and support with the above, you will have to raise this directly with EMIS Partner API Support team.

Hope the above helps.

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, CIS2, NHS Login specific queries, please reach out the relevant API / Service teams.