Version Hazard Log - Notifications (1.1)

14 Hazards, 32 Causes, 60 Controls

New hazard added covering appointment data integrity during SSIS to HL7 migration (three causes, six controls). Prompted by a customer query and a prior migration incident.

Approved Jul 02, 2026 by Joe Horne


HAZ-NOTIF-35	Appointment data is not available within the DrDoctor platform, resulting in failure to generate or send appointment-related notifications.	3	8	Closed
HAZ-NOTIF-36	SMS/email notification is not received by the patient	3	6	Closed
HAZ-NOTIF-37	Incorrect appointment location or format information is presented to the patient.	3	4	Closed
HAZ-NOTIF-38	Incorrect appointment date or time is presented to the patient in SMS or portal communications.	1	4	Closed
HAZ-NOTIF-39	Incorrect appointment format (e.g., in-person, telephone, or virtual) is presented to the patient.	3	4	Closed
HAZ-NOTIF-40	Appointment communications do not clearly identify the originating Trust.	1	4	Closed
HAZ-NOTIF-41	Unauthorised individual gains access to patient appointment information.	1	2	Closed
HAZ-NOTIF-42	Patient-initiated cancellation or rescheduling via SMS fails to complete successfully.	2	3	Closed
HAZ-NOTIF-43	Patient cancellation or reschedule request is not visible to the booking team.	4	5	Closed
HAZ-NOTIF-44	Cancellation or reschedule request is received but not actioned by the booking team.	3	4	Closed
HAZ-NOTIF-45	Cancellation or reschedule request is incorrectly applied to a different patient’s appointment.	1	3	Closed
HAZ-NOTIF-46	Incorrect update is applied to the patient’s appointment record in PAS following a cancellation or reschedule request.	3	4	Closed
HAZ-NOTIF-48	Secondary appointment reminder batch fails to execute fully or partially due to technical fault.	1	3	Closed
HAZ-NOTIF-49	Appointment data is incorrectly or incompletely transformed from SSIS via JSON to HL7 format during migration, resulting in data integrity loss or corruption.	3	6	Closed