Practice management

Build intake and consent forms

Create digital intake and consent forms patients fill before the visit — branching, signatures, attached to a visit type.

Updated
Updated
Reading time
6 min read
Tags
formsintakeconsentbuilder
A look at the form builder
Goodbye clipboard

Intake forms, finished before the visit

Drag-and-drop fields, branching for what actually applies, signatures captured in the chart

EnWella replaces the clipboard. The form builder lives in Establishment → Forms; each form is a sequence of fields with optional branching, optional signature, and an attachment policy that decides which visit types it gets sent on.

Create a form

Establishment → Forms → New. Pick a starting point — Generic intake, ROS, Pain assessment, Consent — or start blank. Forms have a title visible to the patient, an internal name visible only to staff, and a "send when" rule: per visit type, per provider, or manual.

Fields and branching

Field palette
Drag · drop · reorder
Short text
Long text
Number
Multi-choice
Single-choice
Scale 0 - 10
Date
Phone
File upload
Signature
Drag any field type into your form - text, choice, scale, signature

Drag any field in: short text, long text, number, single/multi choice, scale, signature, file upload, date, address. Each field can be marked required, marked PHI-sensitive (so it never appears in the print-summary), and made conditional — show only if a previous answer matched. Use branching for sections like "If you answered Yes to chest pain, please describe…" so the patient sees only what is relevant. The fewer questions a patient sees, the more answers you actually get.

How branching looks to the patient

Branching preview · Pain assessment
Branch active
1

Have you experienced chest pain in the last 24 hours?

Selected:Yes

Because answer was Yes
2

Describe the pain - duration, severity, what makes it worse

Because answer was Yes
3

On a 0 - 10 scale, how severe?

012345678910

If "No": questions 2 and 3 are hidden. Patient skips to next section.

Branching keeps the form short - patients only see what's relevant to their answers

Branching evaluates as the patient answers — a hidden question stays hidden until the trigger answer flips, then it slides in inline (no page reload, no jarring jump). You can branch on any answer type: a Yes/No that reveals follow-ups, a scale that gates a free-text "tell us more" if they pick a 7 or higher, a multi-choice that opens different sections per choice. The patient never sees "Question 12 of 47" when their actual path is 9 questions — the counter follows the active branch.

Signatures and consent

Add a Signature field at the end of consent forms. Patients sign with finger or mouse; we stamp a SHA-256 hash of the signed text plus IP and timestamp. The signed PDF lands in the chart under Documents and is referenced by the consent record so audit reports can prove a specific version was signed.

Attach a form to a visit type

Establishment → Visit templates → pick the template → Forms tab → Attach. The form goes out with the booking confirmation and is required before check-in (unless you mark it optional). Patients see "Forms to complete" in their portal; staff see completion status on the day sheet.

Reviewing responses

Open the patient chart → Forms. Each completed form renders as a one-page summary with diff highlights from the prior version (helpful for ROS where most answers stayed the same). Pin an answer into the visit note with one click — keeps you from retyping.