|  | Wards | Totals | |||
---|---|---|---|---|---|---|
 |  | Ward X | Ward Y | Ward Z | Expected (n) | Actual (n) |
1. | System triggers one alert for patient on test ward once a new HbA1c result is reported in the EHR | 11 | 7 | 14 | 32 | 32 |
2. | System triggers one alert for patient on test ward if no new HbA1c result is reported on EHR after 4 days post-admission | 14 | 15 | 20 | 49 | 49 |
3. | System triggers weekly alert reminders for patients on test ward if HbA1c result is not reported on EHR, after the initial reminder alert described in (2) | 7 | 4 | 9 | 20 | 20 |
4. | Alerts triggered include a summary of previous HbA1c reports if reported on EHR | 32 | 26 | 43 | 101 | 101 |
5. | Alert triggered for new HbA1c provides HbA1c value and suggestion for which threshold range this fits into ie normal, pre-diabetes, diabetes, or severe dysglycaemia as per alerting algorithm | 11 | 7 | 14 | 32 | 32 |
6. | Alert provides prompts on recommended actions in line with clinical algorithm | 32 | 26 | 43 | 101 | 101 |
7. | Alert contains factually correct clinical and patient identifier information (correct HbA1c result, correct name, correct NHS number) | 32 | 26 | 43 | 101 | 101 |
8. | Alert does not contain incorrect clinical information or incorrect identifiers (name and NHS number) | 32 | 26 | 43 | 101 | 101 |
9. | Alerts are only triggered as per the algorithm (no additional or unexpected alerts triggered) | 32 | 26 | 43 | 101 | 101 |
10. | Alerts are not triggered once patients are discharged from ward | 0 | 0 | 0 | 0 | 0 |