Currently the only delivery method for sending an event message to a consumer is to send it to the consumer’s Message Exchange for Social Care and Health (MESH) mailbox. Other delivery channels may be developed in future if there is a demand for them.
The event information published to the NEMS will be unchanged and will conform to the requirements and guidance outlined in the event message specific guidance.
MESH mailbox configuration
The receiving MESH mailbox will need to be configured for each of the event message types the organisation wishes to receive from the NEMS. Each event message has its own WorkflowID as specified in the event message specific guidance. Configuration of the MESH mailbox will require a service request to be sent to the MESH management team at NHS Digital.
Functionality within MESH means messages are deleted after a period of time, if not picked up, therefore subscribers MUST ensure that received MESH messages are managed in a timely and appropriate manner to mitigate the risk of losing messages.
If the subscribing organisation wishes to use generic subscriptions, the request for setup of generic subscriptions should be submitted in addition to the request for creation or update of the MESH mailbox. Details of the information required to create generic subscriptions is outlined in the
Requesting generic subscriptions section below.
Requesting generic subscriptions:
As part of the Private Beta NHS Digital intends to validate the generic subscription functionality by working closely with suppliers and providers to identify and configure their generic subscriptions. As part of this collaborative approach, during private beta, an interim process for submitting generic subscriptions has been implemented as follows:
- providers are sent a “Generic Subscriptions” spreadsheet to complete for the rules they would like setting up
- once complete the spreadsheet is sent to NHS Digital asking for the generic subscriptions to be approved and configured
- NHS digital will validate then configure the generic subscriptions with the NEMS
The intention is to use this process during the Private Beta but an improved process is planned as part of the wider roll out of NEMS service.
More details relating to the columns within the spreadsheet are as follows:
|ServiceType||Mandatory||The following ServiceTypes are available for generic subscriptions:
GP_GP_GP - When you are a GP practice and wish to receive event messages for patients registered at your GP Practice.
UHV_POSTCODE_LACODE - When you are a health visitor service and you wish to recieve event messages for patients where their postcode is in the catchment area of your Local Authority.
CHO_GP_CCG - When you are a Child Health Organization and you wish to receive event messages for patients where their registered GP is in the catchment area of you CHO’s CCG.
CHO_POSTCODE_CCG - When you are a Child Health Organization and you wish to receive event messages for patients where the patients post code is in the catchment area of your CHO’s CCG.
|EventType||Mandatory||The event types which should be sent using this generic subscription.|
|idCode||Mandatory||LA Code, CCG code|
|ServiceProviderID||Mandatory||ODS code of the receiving organization.|
|MESH Mailbox||Mandatory||Indication of if a new MESH mailbox is required or if the events for this generic subscription should be sent to an existing MESH mailbox. For an existing mailbox please include the mailbox ID, for a new mailbox include the word “New Mailbox” and a number. The number is so that if you want to setup multiple generic subscription rules which go to different mesh mailboxes, you can indicate which mesh mailbox you want the event messages to go to, e.g. “New Mailbox1”, “New Mailbox2”.|
|fromAge||Optional||Youngest age of patients in years.|
|toAge||Optional||Oldest age of patient in years. This is inclusive so if the
|fromDate||Optional||Date when you wish the generic subscription rule to start sending event messages to the MESH mailbox.|
|toDate||Optional||Date when you wish the generic subscription rule to stop sending event messages to the MESH mailbox.|