The Consultation Note, Before the Consultation
Every experienced clinician writes consultation notes in roughly the same shape: the complaint, the story around it, the systems check, the background. The structure exists because it works — and because a clinic where every clinician documents differently is a clinic where records can’t be compared, audited, or trusted at handover.
This template applies that canonical structure to the intake itself. Patients answer history questions in the note’s own order before the visit, so the appointment begins with a pre-built draft of the story instead of a blank page. What the clinician adds is the part no form can do: examination, interpretation, judgment.
From Chief Complaint to Review of Systems
Each section of the record maps to a specific question format:
| Note Section | How the Form Captures It |
|---|---|
| Chief complaint | A dropdown of common presentations plus free text for anything atypical |
| History of present illness | Guided prompts: onset date, severity, what worsens it, what eases it |
| Review of systems | A fast yes/no battery organized by body system |
| Past history | Checklist of prior conditions, surgeries, hospitalizations |
| Medications & allergies | Structured short text lines with room for doses |
Building the review-of-systems battery is straightforward once you add questions system by system — cardiovascular, respiratory, gastrointestinal — and the consistent wording pays off every time a second clinician reads the record.
Two Forms, One Record
The cleanest setup uses a pair. The patient completes the pre-visit history at home; a duplicated clinical version captures the provider’s findings during or after the consultation. Reviewed side by side — both live in the response dashboard — they form a complete encounter record: the patient’s account and the clinician’s assessment, each in its own words.
Keep the Systems Review Painless
A thorough review of systems can run past forty items, and a wall of checkboxes is how intakes die. One screen at a time — which is exactly how navigation arrows pace the form — turns the battery into a series of quick taps rather than a form-length commitment. A visible progress indicator helps too, and only the clinically critical items should be required; forcing every field guarantees abandoned submissions.
One Standard, Every Clinician
The value compounds when the whole practice documents identically. Setting up an organization ties every clinician’s forms to one shared structure, and renaming forms by template version — ROS v3, 2025 edition — keeps audits unambiguous. Completed records flow onward through webhooks into practice systems, and the front desk can be alerted to each new intake via self notifications.
Related Templates
The broader consultation family covers specialty intakes, and visit follow-ups pair naturally with patient satisfaction surveys that measure how the experience actually landed.
Frequently Asked Questions
What belongs in the chief complaint field?
The patient’s reason for the visit in their own words, backed by structure: what the symptom is, where it is, and when it started. The dropdown handles the common cases so free text stays reserved for the presentations that genuinely need description.
Should patients complete the review of systems themselves?
Yes — it transfers forty questions of chair time to the patient’s sofa. The clinician’s job at the visit becomes verifying the positives and probing them, which is where the clinical value actually sits.
Does this replace an electronic health record?
No, and it shouldn’t try. It is the structured front door: histories arrive complete and standardized, then pass into existing systems through exports or webhooks. The EHR stores the record; this form guarantees the record starts full.
What about patients who can't complete it independently?
Reception tablets cover most cases — the form works on any device, and staff can assist without transcribing a thing. For interpreters or caregivers, completing it together at the desk still beats handwriting, because the answers land in the same structured record.