Welcome to Multicast Notification Service (MNS).
Use MNS to publish or subscribe to lightweight healthcare related events.
MNS allows NHS England product teams to publish patient related events using ‘publish-subscribe’ messages.
Subscribers receive notification of the events that match their subscription criteria via their chosen delivery method (via MESH or AWS SQS).
Examples of events include:
In this category you can get support with your MNS queries by posting a question.
You can also find more detailed documentation in our API specification.
We’ve recently made several improvements to our documentation to make integrating with the Multicast Notification Service (MNS) as smooth as possible.
Key resources to help you get started:
-
Service Overview & Onboarding: Check the MNS Service Page for an overview of the service, onboarding guidance, and architecture.
-
Supported Events: Browse the MNS Events Catalogue to see all currently available event types, triggers, and filtering criteria.
We’re keen to ensure this documentation meets your needs. If anything is unclear, if you spot gaps, or if there is additional guidance or tooling that would help your integration, please reply to this thread or start a new topic.
Hello - Would you be able to direct me on how to onboard into MNS please?
If you’re looking to onboard as a subscriber to an existing event, the ServiceNow form is here and information on how to do this as well as creating a subscription can be found here.
To register as a publisher, you need to go through the Digital Onboarding Service. Further information to do this can be found on this page.
Thanks Paul. Could you assist again.
I have the mail box and I a, trying to get the workflow added to the mailbox but I cannot find the id from the spreadsheet shared by the support team - Message Exchange for Social Care and Health (MESH): Workflow Groups and Workflow IDs - NHS England Digital
I am looking to add PDSRECORDCHANGE_2 to our mailbox
Hi Nilesh,
You won’t find that ID in the spreadsheet, as that list only covers standard, preconfigured MESH messaging workflows.
When using MESH as the transport mechanism for MNS, a specific Workflow ID isn’t strictly required. You can define your own identifier if that helps with your internal routing or processing, but it isn’t mandatory—and there’s no need to have it configured against the mailbox beforehand.
There is a section about workflow IDs and MNS in this section of the “Subscribe to a MNS event” page
Thanks