Patient consent that protects.
ConsentWave turns a consent agreement into a short teach-back that a clinician approves. Patients answer it before they sign, and every step lands in one evidence bundle.
No sign-up. The demo uses a fictional patient and a simulated signature.
Teach-back complete
5 of 5 correct. Attestation unlocked.
Made for the consent conversation.
A signature shows someone signed. A teach-back shows what they understood. ConsentWave keeps the discussion with the clinician at the center and checks the key terms afterwards.
- Interactive teach-back
- Scenarios in plain language, each linked to the clause it checks. The agreement stays one tap away.
- Human approval
- AI can draft questions. Only an authorized reviewer can approve them.
- Evidence bundle
- Agreement version, approved questions, every attempt, the attestation and the signature, in order.
How ConsentWave works
Six steps. The last three stay locked until the one before is done, and the server checks it every time.
- 1
Supply the agreement
The clinic picks the consent agreement. ConsentWave freezes it as a numbered version.
- 2
Draft the teach-back
Five plain-language questions are drafted from that version. Each one cites the clause it checks.
- 3
A person approves
The reviewer checks every question, answer and explanation, then approves that exact revision.
- 4
Locked until a person approves the set
The patient answers
They read the agreement and answer the approved questions. They can pause, ask, or decline at any point.
- 5
Locked until every answer is correct
Attestation
They read a short statement and tick the box themselves. Nothing is prechecked.
- 6
Locked until the attestation is accepted
Signature
Signing is a separate, deliberate step. The evidence bundle closes around it.
Software drafts. A person decides.
Generated questions can be wrong, so generation is only a drafting aid. It can't approve, publish, attest or sign. Four rules hold no matter what:
- 1
No unapproved questions reach a patient.
That includes replacement sets after a missed attempt. Each one is reviewed on its own.
- 2
Every question cites the agreement.
A question that points at a clause that doesn't exist can't be approved until someone fixes it.
- 3
Approval covers exact content.
Edit one word of a question, answer, pass rule or attestation and it needs approving again.
- 4
A missed attempt never unlocks signing.
The attempt is kept on record. The pass rule isn't lowered to get someone through.
Who can do what
The clinic reviewer and the patient get separate views. The reviewer never answers, and the patient never sees the answer key.
| Action | Clinic reviewer | Patient |
|---|---|---|
| Choose the agreement version | ||
| Approve or reject question sets | ||
| See the answer key | ||
| Answer the questions | ||
| Ask for clarification or decline | ||
| Accept the attestation and sign | ||
| Download the evidence bundle |
The evidence bundle
Which words the patient saw, which questions they answered, who approved those questions and when. Failed attempts stay on the record. If the agreement changes later, finished records keep their original version.
Rhinoplasty Procedure Agreement
Demo record- 09:02Agreement version 3 frozen4be1…07
- 09:14Question set rev 2 approved by Dana Reyes9f2c…e1
- 10:31Attempt 1 submitted, not passed4 of 5
- 10:33Replacement set rev 3 approved2d70…9a
- 10:48Attempt 2 submitted, passed5 of 5
- 10:49Attestation acceptedatt-1
- 10:50Signature recorded (simulated)
What a pass means
It records
- How the patient answered questions about the text in front of them
- That a named reviewer approved those exact questions
- The order of answers, attestation and signature
It doesn't establish
- Legal validity, or legally sufficient informed consent
- Medical suitability or decision-making capacity
- Whether the agreement itself is fair or complete
ConsentWave checks comprehension of the supplied text only. It doesn't give medical or legal advice, recommend treatment, or claim compliance with any standard.
Roadmap
We're starting with one fictional cosmetic surgery agreement. Everything after it follows the same rule: a person approves before anyone is asked.
Now
- Interactive walkthrough
A fictional rhinoplasty agreement, end to end, with simulated signatures.
Next
AI-drafted question sets
Teach-back drafted from your own agreements. Approval stays mandatory.
Smart templates
Curated consent agreements to start from, versioned each time you issue one.
Clinic workspaces
Sign-in for clinicians, patients and administrators, with private storage.
Later
E-signature integrations
Hand the final signature to a signing provider.
Analytics dashboard
Comprehension, clarification requests and time spent waiting on approval.
Consumer agreements
Leases, service contracts and other everyday agreements.
“Nobody told me that” should never be the story.
Try the walkthrough as the clinic reviewer, then as the patient. It takes about three minutes.
Try the demo