ConsentLedger
Every yes, captured and provable
Captures, versions, and stores every consent the clinic asks patients for: telehealth, data sharing, AI-assisted triage, minors. Auditable, retrievable, and linked to the actions it authorised.
- Append -only, tamper-evident
- Exact Text preserved per version
- Linked To every action it authorises
ConsentLedger is the truth of "did the patient agree to X?". It stores the exact text the patient saw, the timestamp, and the action consent was granted for. Every consent is versioned — the text that was signed is the text that will come back in an audit.
Other services ask the ledger before doing consent-gated actions, and log back into it when they do. The result is a clean, linkable chain: "this triage ran because of this consent"; "this data was shared because of that consent".
Everything ConsentLedger handles for you
-
Versioned text
The exact consent text is stored with the signature — not a reference to a PDF that might move.
-
Action-linked
Every consent is tied to the actions it authorises — consent becomes traceable.
-
Audit-grade
Append-only store, tamper-evident, with structured export for compliance reviews.
-
Multilingual
Same consent, multiple languages, each version stored and auditable separately.
How ConsentLedger plugs into the clinic stack
ConsentLedger is consulted before consent-gated actions and written back to when those actions happen.
- PatientPortal presents the consent text and captures the signature.
- SymptomRouter verifies the AI-triage consent before running the flow.
- PHIVault checks the data-sharing consent before granting cross-service reads.
- SecureInbox verifies messaging consent before storing the thread.
Wire ConsentLedger into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.