Synchronising updates
There are various business processes that require the National Proxy Service to inform integrated clinical systems of changes to a proxy role. Notifications will be facilitated through the Multicast Notification Service (MNS), a national service for allowing publishers and subscribers to coordinate healthcare-related events.
Multicast Notification (MNS)
Onboarding and general specifications
Documentation regarding MNS and how to onboard can be found on their API catalogue page.
National Proxy Service Events
The National Proxy Service currently publishes three types of events as described below. For further context of where these would fit in the broader business process, see the Managing proxy access business process.
| Event name | Description | Specification |
|---|---|---|
| Proxy Role Changed event | Event will be published whenever a proxy role is updated | Event specification |
| Proxy Role Deleted event | In rare cases a proxy role will be deleted due to scenarios such as an invalidated NHS number | Event specification |
Filtering - general
In general you should subscribe to all events and determine if the NHS number of the subject (the patient) is relevant to your context e.g. do you hold a proxy role for them. If you do then you will want to process the event and update your local records accordingly. If it is not relevant to your context then the event can be discarded.
It's important to note that all events currently do not support an origin filter field. Because the messaging service cannot filter out notifications based on who originally triggered the action, events are routed to all subscribed systems based purely on the data content, such as the NHS number.
Filtering - Primary Care suppliers
Primary Care suppliers can benefit from configuring filtering rules on the MNS subscription based on the ODS code of patient.
Edit this page on GitHub