Part of Child Health Interoperability (CHI) implementation guide for health visiting services
PDS death notification
PDS death notification
PDS death notification event messages are generated by the Spine and published to the NEMS when a patient’s death notification status is changed within PDS.
1. Data fields available in this message
This table lists the data fields in the PDS death notification message.
Death date |
Death time |
Notified date |
Status of death notification |
4. What benefits can be achieved
Do you currently? | With NEMS | Which means | What may be impacted/ | Possible measures before and after |
---|---|---|---|---|
Receive death notifications from different sources? | You will receive informal and formal death notifications as they are updated on the Spine for your whole population | As an additional failsafe and/or opportunity to redefine the process | Timeliness and completeness of notifications received | Number of death notifications received. |
Ever receive death notifications late? | You will receive informal and formal death notifications as they are updated on the Spine | There is less risk of contacting a family inappropriately. You can pro-actively follow up with your usual source, for example CDOP. | enhanced robustness through additional data source need for additional checks. |
Any late notifications Any occurrences of inappropriate contact |
Inform other parties and carry out failsafe/checking? | All interested parties (GPs, health visitors, SN, child health information services) will receive the notifications at the same time as you. (When they are live on NEMS). | Everyone will have consistent information and some failsafe/checking or communication may be reduced (this will require some process SOP review). | Timeliness of notifications enhanced robustness time involved in notifying others. | Effort before and after. |
Last edited: 17 January 2022 2:54 pm