This document guides the decision process for reversing support reductions. A rollback conversation is appropriate whenever data, consent, or clinical judgment indicates that current support levels should be restored.
| Trigger | Action |
|---|---|
| Missed safety event — the system failed to detect an event that required intervention | Immediately restore previous support level; investigate root cause; do not re-attempt reduction until issue is resolved |
| Increase in adverse outcomes — falls, injuries, emergency calls, or hospitalizations increase compared to baseline | Restore previous support level; review whether the reduction was premature or the system configuration needs adjustment |
| System reliability drop — uptime falls below 90% or connectivity gaps in monitoring | Restore previous support level until system reliability is restored above 95% |
| Loss of confidence — participant, family, or team no longer feels safe with reduced support | Restore previous support level; reassess through team conversation |
| Change in clinical status — seizure frequency increases, new medication, new diagnosis | Restore previous support level; reassess CtLC scorecard with updated clinical information |
| Consent withdrawal — participant or guardian withdraws consent for monitoring | Restore all prior supports immediately; follow data deletion procedures per DGSP |
| Situation | Recommended Response |
|---|---|
| Single missed alert | Investigate root cause (sensor placement, threshold, connectivity). One event is not a pattern — document and monitor. |
| Temporary spike in false positives | System may be recalibrating after an environment change (new furniture, pet, heating). Adjust thresholds; review after 7 days. |
| Family questions about privacy | Address with education — refer to playbook sections on thermal visibility and the two-layer privacy model. Privacy concerns alone do not require rollback. |
| Staff turnover | Retrain new staff on alert response protocol. Do not reduce supports further until new staff are fully onboarded. |
When any trigger above is met, follow these steps:
SSA, family/guardian, provider staff, Medforall representative, and clinical team (if seizure-related). Schedule within 5 business days of trigger event.
What triggered the concern? Present alert logs, staff response times, pattern changes, and any incident reports. Compare current data against the baseline established during the parallel operation period.
Full rollback: Restore all prior supports to pre-reduction levels.
Partial adjustment: Restore supports for specific time windows or specific concerns only.
Record in the ISP: date, participants, data reviewed, decision made, rationale, and next review date. This becomes part of the participant’s implementation record.
Implement restored human supports before reducing or removing technology monitoring. The safety net must be in place before any changes take effect.
Review within 30 days of rollback. Assess whether the underlying issue has been resolved and whether a new graduated reduction attempt is appropriate.