Consent
Consent that holds up — every time, every version.
Consent in AestuteOS is a versioned, signed, event-bound record — never a static PDF. Every signature is time-stamped and linked to the exact treatment event it covers.
See it in action Connected flow
How Consent connects to the Treatment Event.
Every module in AestuteOS either feeds the Treatment Event or reads from it. Here is where Consent sits in that flow.
Consultation
Consent
Treatment Event
Audit
Key functions
The capabilities that make Consent work in practice.
Time-stamped patient signatures
Linked to the specific treatment event
Evidence trail for audits and incidents
Re-consent on plan changes
How it works in practice
How Consent runs in a clinic.
A typical flow from the moment the work begins to the moment it lands on the Treatment Event record.
- DraftConsent form generated from the treatment plan and current template version.
- SignPatient signs digitally — time-stamped and linked to the event.
- BindSigned consent is locked to the Treatment Event record.
- Re-consentPlan changes trigger re-consent automatically; old versions remain on file.
How it fits in the clinic
Consent inside the operating map.
Consent sits as part of the wider AestuteOS operating story. Every module either feeds the Treatment Event or reads from it.
Consent
Consent
Digital consent
Signatures
Versions
Linked evidence
Treatment Event
Clinical source of truth
Patient record
Consent linked
Products recorded
Why it matters
The operating story behind Consent.
Consent is not a PDF in a folder. It is a versioned, signed, event-bound record — and AestuteOS treats it that way so the audit story is always intact.
Related modules
Where Consent touches other parts of the operating map.
Everything orbits the Treatment Event.
See how this module sits inside the full AestuteOS operating map — and how every other module connects back to the same clinical source of truth.
Back to the operating map