Every year, thousands of clinical trial patients are treated under expired, superseded, or missing informed consent — a silent regulatory crisis that can invalidate years of research data and, more critically, exposes patients to risks they never agreed to. This is the UX process behind a system that made consent failures visible before they happened, reducing IRB-reportable consent violations by 89% and catching 214 at-risk patients in its first six months.
Informed consent isn't just paperwork — it is the legal and ethical bedrock of every human subjects research trial. When a protocol amendment changes the risk profile of a study, every enrolled participant must re-consent under the new document before continuing treatment. Miss that window, and patients receive interventions they have not legally agreed to. The data collected is potentially invalid. The trial may be halted. Careers end. This is not a hypothetical risk — the FDA issues clinical hold orders for consent violations every year.
| FAILURE MODE | HOW IT HAPPENS | REGULATORY RISK |
|---|---|---|
| Version currency lag | IRB approves amendment; coordinator updates the "master" spreadsheet but misses 3 patients who were "on hold" and not on the active list | Critical — FDA 483 observation |
| Re-consent timing gap | Protocol amendment allows a 30-day window for re-consent; site forgets to track against this window per-patient; window closes unnoticed | Critical — may require IRB reporting |
| Superseded ICF administered | Coordinator prints consent packets in bulk; amendment arrives; old packets still in folder; new patient consented on v2.0 after v3.0 was approved | Critical — invalid consent |
| Missing signature documentation | Patient signs; coordinator forgets to scan; paper copy lost during site move; no digital audit trail | High — audit findability failure |
| Capacity re-assessment gap | Patient's cognitive status changes during trial; no system flags for re-evaluation of consent capacity; prior consent may no longer be valid | High — ethics board concern |
The consent lifecycle has five distinct phases, each with specific failure modes. I mapped all five, then prioritized the amendment rollout flow and the re-consent tracking flow as the two highest-risk, highest-frequency intervention points. These became the first prototype targets.
| STATUS | DEFINITION | REQUIRED ACTION | UI TREATMENT |
|---|---|---|---|
| Valid | Signed on current IRB-approved ICF version, within validity period | None — monitor for amendment | Green border · chip-valid |
| Re-consent due | Amendment approved; patient signed prior version; window open | Schedule re-consent visit | Amber border · countdown visible |
| Re-consent overdue | Re-consent window has closed without new signature | Halt treatment + report deviation | Red border · treatment block indicator |
| Version expired | Signed on a version IRB has since superseded; no new signature | Immediate re-consent required | Deep red border · urgent flag |
| Signature gap | ICF version is current but signature documentation is missing or invalid | Locate original or re-administer | Red border · document missing badge |
Clinical compliance interfaces have a paradox: the more alerts they generate, the more they're ignored. Alert fatigue is the design failure that turns a safety system into a liability. The consent platform's color and status system was built around a single constraint: every color represents exactly one level of action urgency, and that mapping never changes anywhere in the product.
Production-fidelity prototype of the Consent Integrity Dashboard. Click any patient row to open the detail panel with full consent history, ICF version tracking, and required actions. Use filters to triage by consent status. The treatment block logic, version mismatch detection, and AI risk signals all function as they would in the shipped product.
The prototype was validated with 8 coordinators and 3 CRAs across two trial sites over six weeks. All outcome metrics were defined before the study began. The post-deployment data (6 months after pilot launch) is sourced from the site's own deviation and monitoring reports.
| FEATURE | WHY CUT | V2 PATH |
|---|---|---|
| eSignature capture | Wet signature and witnessed consent remain the gold standard at most IRBs. Building eSign into V1 would require IRB-by-IRB approval negotiation, adding 6–18 months of compliance validation. The platform tracks consent; it doesn't replace the consent process itself. | V2 — FDA 21 CFR Part 11-compliant e-consent module |
| Automated IRB reporting | Deviation reporting requires coordinator review and PI sign-off before IRB submission — automating the filing step creates accountability ambiguity. The system generates the draft; humans approve and submit. | V2 — pre-filled deviation report with single-click submission queue |
| Capacity assessment tracking | Cognitive capacity re-evaluation is a nuanced clinical judgment, not a database field. Building a checklist tool for it creates false precision and potential liability. Requires ethics board involvement before UX design begins. | V3 — collaborative design with IRB ethics committee |