Consent Lane
A consent queue should show version pressure and reset risk, not just who clicked agree.
Each row ties capture context to policy version, downstream usage pressure, and the next action needed to keep consent state audit-safe.
| Consent | Excerpt | Owner | Next Action | Risk |
|---|---|---|---|---|
| Remote cardiac monitoring CONS-201 PCM-4.2 | Updated consent version must propagate to patient messaging and monitoring workflows within 24 hours. | Patient Access | Confirm downstream messaging tool acknowledged the newest policy version. | watch |
| Behavioral intake portal CONS-214 BHP-2.8 | Revocation events must be exported to downstream intake and messaging tools within the same business day. | Privacy Ops | Route missing revocation export to the intake vendor before stale consent state persists. | critical |
| Specialty pharmacy refill reminders CONS-227 SPR-3.1 | Outbound reminders require channel-specific consent proof and vendor acknowledgement. | Growth Compliance | Attach SMS vendor acknowledgement to the audit packet. | watch |
| Women's health scheduling CONS-233 WHS-1.6 | Revocation state must suppress follow-up scheduling reminders across all outbound channels. | Care Navigation | Resolve call-center revocation lag before additional outbound reminders run. | critical |
| Population outreach analytics CONS-246 POA-5.0 | Analytics usage requires current consent version proof and reset confirmation when policy terms change. | Data Governance | Final audit packaging only; downstream resets are already confirmed. | low |