Building consent forms

A consent is a form the patient reads and agrees to — consent to treatment, telehealth consent, a privacy acknowledgement. Ona sends it, the patient signs it, and the signed consent attaches to their record. It's the paperwork side of intake, handled without paper.

The Consents page

Go to Library → Consents — "create and manage consents with rich text content and checkboxes".

Like Templates and Questionnaires, the page has two parts: your consents along the top, each with a Send action, plus New Consent; and a Library of predefined consents "ready to import and customize".

Import a ready-made consent

The library is tagged All, Treatment, Telehealth, HIPAA Privacy, General, Custom. The five that ship cover the common cases:

• Consent to Treatment — general consent for assessments, recommendations, and follow-up care.
• Telehealth Consent — for remote care, technical limitations, and emergency guidance.
• Privacy Practices Acknowledgement — the patient acknowledges receiving your privacy and data-use information (HIPAA).
• General Consent — flexible consent for clinic policies, communication, and care coordination.
• Optional Research Participation — optional consent for anonymised research or service improvement.

Preview reads one; Import copies it into your own set, where you can edit the wording.

Have the imported wording reviewed before you use it. These templates are a strong starting point, but consent language often needs to match your jurisdiction and your practice's specifics — that's a check for whoever owns compliance, not something to send as-is on trust.

Rich text and checkboxes

Consents support formatted text and checkboxes — the discrete points a patient ticks to agree to, distinct from signing the whole form. Use checkboxes for anything the patient should affirm individually: consent to treatment, consent to telehealth, agreement to a cancellation policy. A single signature at the end says "I read it"; a checkbox says "I specifically agree to this."

Sending and signing

Send delivers a consent to a patient to sign. Once signed, it comes back to their record — the patient record has a Consents section under Inputs where signed consents are stored, and a completed consent can trigger a notification (see Notification settings).

Automatic sending

As with questionnaires, the efficient path is to not send consents by hand. Attach a consent to a Service (its Consents tab; see Setting up services), and it's selected automatically whenever that service is booked — the panel there says exactly this: consents are "auto-selected when this service is added to a visit." So a telehealth service can carry the Telehealth Consent, and booking it sends the consent without anyone remembering to.

Consents can also be selected ad hoc while creating a visit (see Creating a consultation / starting a visit).