Module, Digital Consents
Digital
Consents
Capture, sign, and revoke patient consents with full audit history, linked to the patient chart and gated by consents:* permissions.
What it covers
Structured consent records for procedures, anesthesia, data sharing, and other institutional templates. Staff create drafts, patients or authorized proxies sign digitally (consents:sign), and consents can be revoked with reason.
Why
- → Paper consents get lost before OT or high-risk procedures
- → Auditors need signed/revoked history with timestamps
- → Record scope keeps staff within allowed patients
Consent lifecycle
Technical Architecture
| Field | Type | Institutional Role |
|---|---|---|
| patientId | UUID | Patient the consent applies to. |
| status | Enum | Draft, signed, revoked. |
| signedAt | DateTime? | Signature timestamp when signed. |
| revokedReason | Text? | Required context when revoked. |
Note: Sensitive fields use AES-256 field-level encryption where applicable.
Governance & Power
consents:viewconsents:createconsents:signconsents:revoke Patient-scoped via consents record-scope permissions.