- What is medspa consent forms software?
- Medspa consent forms software is a system that captures, stores, and audits patient consent for aesthetic treatments. Delam's medspa consent forms software ships 30+ treatment-specific templates (Botox consent, filler consent, laser consent, body contouring, PRP, microneedling, chemical peel), an electronic signature pad, a timestamp plus IP metadata record, a patient-revocable flow, and an immutable audit trail aligned with PHIPA, PIPEDA, HIPAA, and CPSO rules.
- Is electronic consent legal in Canada?
- Yes. Electronic consent is legally binding under PIPEDA Part 2, Quebec Law 25 (LCCJTI), Ontario's Electronic Commerce Act, BC's Electronic Transactions Act, and every other provincial e-signature statute. Delam's medspa consent forms software captures the sign event with a timestamp plus IP metadata, user agent, device fingerprint, and consent version, which meets the evidentiary bar for CPSO, CNO, and Information and Privacy Commissioner reviews.
- Can patients revoke consent after signing in Delam?
- Yes. Every consent record in Delam is patient-revocable at any time from the branded patient app or a signed email link. Revocation writes a revokedAt timestamp, appends to the audit trail, hides the underlying asset from marketing surfaces, invalidates signed URLs within 60 seconds, and blocks downstream automations from reading the asset. The clinic admin receives a notification within 5 minutes.
- Does Delam include Botox, filler, and laser consent templates?
- Yes. Delam's medspa consent forms software includes Botox consent, filler consent, and laser consent templates out of the box, plus Dysport, Xeomin, Jeuveau, Sculptra, Radiesse, Bellafill, IPL, CO2, Fraxel, Morpheus8, BBL, CoolSculpting, Emsculpt, Sofwave, Ultherapy, NAD+ IV therapy, GLP-1 weight loss, microneedling, chemical peel, and PRP. Every template is bilingual (en-CA and fr-CA), editable per provider, and versioned so you can reproduce the exact wording a patient signed on a given date.
- Is before/after photo consent separate from treatment consent?
- Yes. Before/after photo consent lives on a dedicated PhotoConsent record, separate from the treatment consent. Photo consent captures scope (internal chart only, clinic marketing, public social), a name-publication toggle, and a revocation channel. The requirePhotoConsent middleware blocks uploads unless a valid non-revoked PhotoConsent exists, and revocation invalidates signed URLs within 60 seconds so a photo cannot drift from chart to Instagram.
- What makes Delam's medspa consent forms software different?
- Delam's medspa consent forms software is built into a membership-first medspa OS, not bolted on. Consent is a first-class primitive linked to every appointment, every photo, and every automation. Missing consent blocks the appointment from starting, which means your clinic is compliant by default, not by staff vigilance. Every consent event is written with auditPHIAccess() into an immutable ledger retained seven years.
- How does the consent audit trail work?
- Every consent event (view, sign, revoke, edit) writes a ledger row with staff ID, patient ID, action, IP, user agent, jurisdiction, purpose, and consent version. The ledger is append-only and retained seven years to match PHIPA O. Reg. 329/04 and CPSO Policy 4-12. Exports are available as CSV or JSON for complaint responses, Information and Privacy Commissioner audits, or internal QA reviews.