Search loading...


Explore and Make use of Nationally Defined Messaging APIs


Introduction to National Events Management Service


The National Events Management Service (NEMS) is a national service implemented on the Spine allowing for patient centric event messages to be published from one system and distributed to a number of other subscriber systems.

The NEMS is designed to be a generic transport mechanism which can support a variety of use cases and event types from a number of different care settings. This specification focuses on the transport mechanism and the common event message elements:

The specific event messages which have been defined for use through the NEMS can be found in the Event Message Implementation Guides listed below. If the event messages currently defined do not meet your needs you can contact us using the details on the Help & Support page to discuss how NEMS could be enhanced to meet your requirements.

NEMS Events


The NEMS is designed to allow a provider to share that an event has occurred for a patient, without knowing who might be interested in that information. The NEMS is intended for use where an event may result in immediate action by another provider.

For example:

  1. A patient is admitted to hospital and as a result of their registration within the hospital system an ‘Admission’ event is sent to the NEMS.
  2. A subscriber to the ‘Admission’ event is a health visitor service who provides care for that patient, therefore the NEMS forwards the ‘Admission’ event to the health visiting service.
  3. When the health visiting service receives the ‘Admission’ event they can make appropriate changes to scheduled home visits with that patient while they are in hospital and make better use of the health visitors time.

This is the sort of use cases that would be considered an event and a suitable use of the NEMS.

None Events

Where a provider records an encounter or information about a patient and the information would be useful for other providers to have access to, but where that data is not identified as something which would result in immediate action by another provider, this would not be considered an event or appropriate for sharing over the NEMS. There is complimentary Spine service along side the NEMS on Spine called the National Record Locator (NRL) which is designed to help make this data sharing possible. The NRL is a collection of pointers to patient information within other systems. These pointers within NRL contain the information required to retrieve the patient information from the original source when it is required.

Event Message Implementation Guides

The following implementation guides give detail around the content and use of the event messages defined by different programs. The Supported Event Messages page list the event messages currently supported by the NEMS for publication and subscription.

Implementation Guide Description Date Events Available
Demographic Update Event Messages Specification for demographic events published by the Spine, such as birth notification and demographic change notification. March 2019
Digital Child Health This specification contains the event messages defined by the Digital Child Health program to support the care of children. May 2019 to
TBC 2020
(see guide for specific events)
National Population Failsafe Management Specification containing information around the national population failsafe functionality and the event messages the service will publish to the EMS. TBC 2019

The Date events available column in the table is the date when the events specified within the implementation guide will be supported by the NEMS. This date does not indicate that suppliers will be publishing the event messages, only that the NEMS will accept the event message from the publishers and will distribute the event messages to the subscribers. The dates included are indicative of the current timeline for development but may change depending on priorities and feedback during development.

Implementation guides such as Digital Child Health which contain a large number of events may be implemented incrementally. Events will be released for use once they have been implemented within the NEMS, while other event messages are still being developed. The Event Message Implementation Guides will contain specific detail around development and release dates for the individual event messages which are part of an incremental release process.

Tags: overview

All content is available under the Open Government Licence v3.0, except where otherwise stated