Consent forms
E-signed consent that holds up under audit.
Schema-versioned templates for intake and per-treatment consent. Sent as tokenized links, signed on a tablet, snapshotted at the moment of signing. Audit trail captures IP, user-agent, and timestamp on every signature — the kind of record a medical board or HIPAA reviewer expects.
Botox & Neurotoxin Consent
Version 4 · For: Sarah Chen · Tokenized link
Signature
Versioned
Templates evolve; signed forms stay frozen.
Tokenized
No login required for the client.
Audited
IP, user-agent, timestamp, signature image.
Template management
Build forms once, version them as your practice evolves.
Lumè ships with a library of starter templates: general intake, Botox consent, filler consent, laser consent, photo release. Edit any starter, save it as your own version, and the system auto-bumps the version number on schema changes.
Per-service consent forms auto-assign when an appointment with that service is booked. Lifetime intake forms assign once, on first visit.
- Starter library: intake, Botox, filler, laser, photo release
- Auto-versioning on schema changes
- Per-service auto-assignment
- Lifetime vs per-visit recurrence rules
Tokenized fill flow
Send a link. The client signs on any device.
The front desk sends the form via SMS or hands the client an iPad. The fill page works without a login — a 256-bit URL token is the credential. The client fills the form, signs with their finger or a stylus, and the signed copy lands in the chart.
Tokens are single-use for signing. Once signed, the form is immutable; reopening it returns the signed view, not the editable view.
- No client login required
- Single-use tokens (256-bit entropy)
- Works on iPad, phone, or laptop
- Signed copy emailed on operator request
Sarah Chen
Client since Mar 2024 · 12 visits · Member
Phone
(555) 234-1180
sarah.chen@…
Date of birth
Jan 14, 1989
Allergies
Penicillin
Pending forms
Botox consent · per-visit · expires today
Audit trail
Every signature, immutable and reviewable.
When a form is signed, Lumè captures: the IP address, the user-agent string, the timestamp, the signature image, and a snapshot of the template at the moment of signing. That snapshot means an evolving template never rewrites a signed past — what the client signed is what stays.
Voids are a separate transition with a required reason. Voided forms remain in the audit log; they don't get deleted.
- IP + user-agent + timestamp on every signature
- Schema snapshot at signing — historically legible
- Void with required reason; never hard-deleted
- Audit log accessible from the chart
See it in 30 minutes