National Events Management Service (NEMS) v0.1.0
ID | S111 |
|---|---|
Version | 0.1.0 |
Type | Interoperability Standard |
Status | Draft |
Effective Date | TBC |
Framework(s) |
Introduction
The National Events Management Service (NEMS) allows digital health and care services to notify other digital services that an ‘event’ has occurred, using ‘publish-subscribe’ messages.
For further information, see National Events Management Service (NEMS).
Requirements
Applicable Suppliers | ID | Requirement | Level |
|---|---|---|---|
GP Suppliers | NEMS01 | Subscribe to and implement the receipt of Registration Request event messages inline with the latest specification version. Please see the Payload document attached. 
| MUST |
NEMS02 | Subscribe to and implement the receipt of PDS Record Change event messages inline with the latest specification version. | MUST |
Message Implementation
Dependent on the care setting or system, the messages needing to be subscribed to may differ. The table below shows which NEMS messages are required to be implement based on the Capability being delivered.
Capability | Applicable Requirement | Message |
|---|---|---|
NEMS01 | Registration Request | |
NEMS02 | PDS Record Change |
Compliance, Assurance and Testing
Onboarding and Assurance information can be found here.
Documentation
National Events Management Service - FHIR API Overview (developer.nhs.uk)
Personal Demographics Service Notifications - FHIR Overview (developer.nhs.uk)
Dependencies
Creating a compliant implementation requires implementing the following dependent interface standards:
Roadmap
Items on the Roadmap which impact or relate to this Standard |
|---|