Informed consent systems
Consent capture with versioning and a full audit trail — so proving what was explained, to whom and when becomes a query rather than a search through scanned images.
What a consent system has to guarantee
Consent capture and versioning
The exact document version presented to the patient stored with the signature, so the wording shown at the time can be reproduced years later.
Audit trails for every signature
Who signed, who witnessed, when, where and against which version — recorded immutably rather than assembled afterwards from several systems.
Clinic and hospital workflows
The differing paths for outpatient, inpatient and procedure consent, including where a clinician must be present and where they need not be.
Remote and in-person consent
Consent given at home with time to read, or at the bedside, with the same evidential weight and the same record structure.
Withdrawal and re-consent
Withdrawal recorded as an event rather than a deletion, and re-consent triggered automatically when a document version changes materially.
Reporting for regulators
Queryable evidence of consent coverage and currency, produced on demand instead of compiled for each inspection.
Don’t see your challenge here? Talk to us about your project
Signed, scanned and filed turns a question into a search
Paper consent answers the question at the time and almost nothing afterwards. Establishing which version a patient saw, whether it was current, or whether consent was later withdrawn means opening images one by one.
Capturing consent structurally — version, timestamp, signatory, witness, basis — makes the same question a query, and makes coverage reportable across a department rather than provable only case by case.
- Versioned documents
- The exact wording shown is stored with the signature.
- Immutable audit
- Records are appended, never altered.
- Withdrawal as event
- History preserved rather than deleted.
- Automatic re-consent
- Triggered when a document materially changes.
- Coverage reporting
- Gaps visible before an inspection finds them.
- Remote or bedside
- One record structure for both routes.
A consent system for fertility treatment, where the evidence has to last
Fertility treatment consent is the strictest version of this problem: what was explained, to whom, in which wording, with whose agreement, has to be provable long after the fact and often involves more than one consenting party. Building it meant treating the audit trail as the product and the signature capture as a detail.
Common questions
Is an electronic signature legally sufficient?
In the European countries we work in, yes, when the identity assurance and the audit trail meet the relevant standard. The specific requirements vary by country and by procedure, and we design to the strictest one in scope.
What happens when the consent document changes?
The old version is retained and remains linked to everyone who signed it. Whether a change requires re-consent is a clinical and legal judgement, and the system supports triggering it rather than deciding it.
Can consent involve more than one person?
Yes. Multi-party consent — both partners, a parent and a guardian, a patient and a legal representative — is modelled explicitly, including the case where the parties consent at different times or in different places.
Let's talk about your healthcare platform
Tell us where the friction sits in the pathway today and what the regulatory position requires. We will come back with an honest read on the integration work, the identity problem underneath it, and what a realistic first phase looks like.
