MESH API conformance testing - who is the current assurance contact?

Message Exchange for Social Care and Health (MESH)
,
1

Hi all,

We are working through MESH API conformance for our new product and we’ve stalled on finding the right assurance contact.

Where we are:

  • INT mailbox provisioned (I7D4HOT001), workflow ID DISCH_KET, connecting over the internet
  • Internal harness passing on test cases 01, 02 and 03
  • Evidence for those three test cases prepared and sent to the assurance lead we were given, but no response in over five weeks
  • Two further INT mailboxes requested from ITOC for the remaining test cases
  • ITOC have confirmed they only handle mailbox provisioning, not conformance

Our original contact’s inbox is no longer monitored, and the replacement address we were given hasn’t responded. We have NHS customers going live next month so are keen to get the evidence reviewed and a witness test booked.

Could anyone from the MESH or Solutions Assurance team confirm the correct route for submitting conformance evidence in 2026 - is it still by email to an assurance lead, or should this go through the Digital Onboarding Service?

Happy to share the evidence and mailbox details directly with whoever picks this up.

Thanks,
Theo

2

We have reached out separately to Theo, but for those viewing this…

For MESH API conformance testing the contact is Paul Butterworth (paul.butterworth@nhs.net).

Following the approval of a developer’s use case for the MESH API he will email them details of the conformance tests that will need to be witnessed, along with guidance on how to request test mailboxes and a tls certificate in the Path to Live Integration environment.

Paul should be contacted to arrange a witness test once enough evidence has been gathered to demonstrate that the product is able to make calls to the MESH API in accordance with the documented specifications.