Practice management

Manage patient consents

Versioned consent templates, who has signed which version, and how to require a re-sign after a policy change.

Updated
Updated
Reading time
5 min read
Tags
consentcompliance

Consents are versioned templates plus the patient signatures attached to them. The system answers two questions every audit asks: what did this patient agree to, and when.

Consent templates

Consents · panel coverage
Coverage report

Telehealth consent · v3

Per visit · virtual

92%

HIPAA Notice of Privacy Practices · v2

Once · portal activation

78%

Financial responsibility · v4

Re-sign required

64%
Each consent is versioned - the audit always shows the exact body the patient signed and when

Establishment → Consents. Each template has a name, body (markdown), required-by rule (per visit type, per service, or one-time on portal activation), and a version number. Editing publishes a new version automatically — old versions stay for the audit trail. The coverage report shows what fraction of your panel is on the current version of each consent.

Collecting a signature

Patients see required consents at portal activation, before check-in for relevant visit types, or whenever a new version drops. They sign in the portal; in-room signing is supported for paper-driven moments — staff hands the patient a tablet logged into a check-in kiosk.

Auditing what was signed

Patient chart → Consents shows every signed version with timestamp, IP, signature image, and the exact body the patient saw. Run an establishment-wide report under Establishment → Consents → Coverage to see who is missing a current version.

Requiring a re-sign

When you publish a major revision (e.g. a privacy policy update with new scope), tap Require re-sign. Patients with a current signature see a banner the next time they open the portal asking them to review and re-sign before they can do anything else.