Updating a Subscription
The National Events Management Service does not support different versions of Subscriptions, therefore any changes to a subscription will require that the existing subscription is deleted, and a new one created.
Any NHS Numbers included within a subscription sent to the NEMS Subscription API MUST have been verified against the Spine PDS at the point of calling the subscription API.
Information on how to verify an NHS Number against the Spine PDS is available on the Spine Core specification.
To use the NEMS subscription API the submitting system will require national assurance and must be set up as a Spine Endpoint with an associated endpoint certificate (see here for details). The endpoint ASID on which the subscription API message set is register MUST contain the ODS Codes which will be used within the subscriptions and match the MESH mailbox ODS Code.
All requests SHALL include a JWT with information about the requesting system and user (see the Spine Core specification for details). Additional NEMS specific requirements for population of the JWT are outlined below.
|requesting_patient||Optional||If included the
NEMS Supported MIME-types
The supported MIME-types for the Subscription API are:
Where the MIME-type is not supplied the NEMS will default to
Providers using the subscription API MUST audit all interactions with the API, including
The audit data MUST include:
- who or what triggered the subscription create, read or delete
- the date and time when the subscription was created / read / deleted
- details about the subscription such as the event type, the start and end dates for the subscriptions if included and the NHS Number the subscription was for