🚀 DocRepute is in early access — free to startGet early access →
Custom form logic illustration
✨ Early access — free to start

Conditional logic and patient form branching, built for patient intake

The most valuable branch in a healthcare form is the one that removes a section, not the one that adds another. One document that adapts to the visit in front of it, instead of six near-identical PDFs drifting apart in a shared drive.

D
M
R
S
Join healthcare practices on the waitlist

Six versions of the same form, and none of them right

Look in the shared drive of almost any independent practice and you will find the same thing: new patient form, new patient form final, new patient form cosmetic, new patient form v3 USE THIS ONE. They exist because a single static document cannot serve every appointment type, so somebody made a copy and edited it, then somebody else did the same, and now the practice maintains six documents that have quietly drifted apart. Change your privacy wording and you have to change it six times, and you will miss one. The alternative most practices settle for is worse: one long form that asks everyone everything. A self-pay patient works through twelve insurance fields. An adult scrolls past a guardian section. Somebody booked for a video visit reads parking instructions. Length is the single biggest reason intake forms come back half finished, and every irrelevant question is a chance for someone to stop, guess, or write not applicable across a page your staff then has to interpret. Conditional logic is the way out of both traps, and patient form branching is what it looks like from the patient side: one document that rearranges itself around the visit in front of it.

  • Built for HIPAA-compliant workflows

  • Free to start — 50 patient actions each month

What conditional logic and patient form branching actually mean here

Both phrases describe one idea. The practice writes a rule in advance, the form follows it, and each patient sees only the questions that apply to them. The mechanic underneath is deliberately unglamorous: show/hide fields and sections, driven by answers the patient has already given. Choose self-pay and the insurance block disappears. Enter a date of birth under eighteen and the guardian and consent authority section appears. Pick a video appointment and the arrival instructions go, replaced by the details a remote visit actually needs. Say yes to taking regular medication and the list opens up; say no and the form moves on without leaving an empty table behind. Every rule is authored by your practice, visible to your practice and changed by your practice, which is what separates conditional patient intake forms from the vague, adaptive intelligence competing pages tend to advertise without ever explaining. There is no model deciding anything here. There is a rule you wrote, doing exactly what you told it to do.

The branch that removes a section beats the branch that adds one

Generic form builders sell branching as a way to ask more, revealing follow-up questions when an answer looks interesting. In healthcare intake the bigger win runs the other way. A returning patient confirming details does not need the full history they gave you two years ago. A cash patient does not need a payer, a member number, a group number, a subscriber relationship or a prior authorization question. An adult never needs the birth and guardian block. A telehealth visit never needs the arrival time, the parking note or the mask policy. Take those away and a form that ran to four pages for everyone becomes a page and a half for most people, without losing a single answer you would actually have used. Shorter forms come back completed, and completed forms are the whole point of the exercise. This is also how one document replaces six: the appointment type sits at the top, and everything downstream arranges itself around the answer, so there is one file to update when your policy changes.

How it works, step by step

First you build the form, starting from a healthcare-specific preset in the free form builder rather than a blank page, or from any template in the library. Second you add the rules, in plain terms: when this answer is given, show that section, or hide it. Rules attach to individual fields or to whole sections, and they can stack, so a self-pay patient under eighteen sees the guardian block without the insurance block. Third you preview the form as a patient would see it, walking each path to check that nothing important hides behind a rule nobody thought about. Fourth you publish it, and DocRepute digital patient intake sends it to the patient ahead of the visit. What comes back is structured and readable, with the fields the patient never saw simply absent rather than empty. Your staff review the completed submission before it goes anywhere near a chart. Conditional forms are a planned part of that intake workflow while DocRepute is in early access, and the branching rules are always yours to inspect and change.

A four-provider dermatology practice and its shared drive

A dermatology group with four providers ran six new patient documents: general medical, cosmetic self-pay, Mohs pre-surgical, teledermatology, a paediatric version and one nobody could account for. When their privacy notice changed, three of the six were updated and three were not, and it took a patient complaint to find out. They rebuilt it as one form. The first question is the visit type. Choosing cosmetic self-pay hides the entire insurance block, eleven fields that had never once been useful for those appointments, and shows their financial policy acknowledgement instead. A date of birth under eighteen shows guardian details and consent authority. Teledermatology hides arrival and parking and shows the details a video visit needs. Mohs shows the anticoagulant and prior biopsy questions their surgeon always chased by phone, and hides them for everyone else. One document, one privacy paragraph, one place to change it. The practice manager's summary was that they had not gained a feature so much as stopped losing an afternoon a month to version control.

The rules are administrative. The clinical judgement stays with you.

A rule that reveals a follow-up question can look, from the outside, like the form is reasoning about a patient. It is not, and the distinction matters enough to state plainly. Branching decides which administrative questions apply to a visit; it does not assess anyone. Nothing here diagnoses, triages, rates severity, assigns urgency, scores risk, flags a patient for attention, checks medication interactions, reproduces a validated screening instrument or recommends treatment, and none of that is on the roadmap for this feature. What the form does is collect the right information and hand it to a person. Your staff see the completed submission and review it before it is used, your clinicians decide what any of it means, and the answers a patient gave are recorded as they gave them, never rewritten or interpreted. Where AI intake is switched on as a paid capability, it works the same way: it asks follow-up questions your practice has approved in advance and prepares a structured handoff, and it does not invent clinical questions of its own.

Privacy, product status, and what it costs to start

Asking fewer questions is a privacy position as well as a usability one, and it is the reason data minimisation shows up in every serious HIPAA conversation: information you never collected cannot be mishandled. A patient who never sees an insurance section has no insurance data stored against that submission. DocRepute is HIPAA-focused, built for HIPAA-compliant workflows and designed for HIPAA-regulated patient intake, with BAA availability planned at launch, and it is in early access ahead of that launch: the form builder and template library are usable today, while branching inside digital patient intake is part of the planned core workflow. What DocRepute does not do is worth saying just as plainly. It is not an EHR or a practice management system, and it does not schedule, bill or chart. The free plan includes 50 action credits a month, used only when a patient completes a regular intake submission or a standard survey; building, editing and publishing your forms never uses one. Paid plans add AI intake, conversational surveys and sentiment analysis; the free tier has no AI.

Explore Related Resources

Digital patient intake workflow

Practice-approved AI intake assistant

Free healthcare form builder

Healthcare form template library

All DocRepute features

Practices DocRepute is built for

The DocRepute patient experience platform

Get early access

Be first to use DocRepute when it launches — including AI intake and conversational surveys on paid plans.

  • Free to start — 50 action credits a month
  • Building and publishing forms uses none of them
  • No card, and no sales call booked

No spam, ever. Unsubscribe anytime.

Frequently Asked Questions

They are two names for the same behaviour. Conditional logic is a rule your practice writes in advance, in the form of when this answer is given, show or hide that field or section. Patient form branching is what the patient experiences as a result: the form takes a different path depending on what they have already entered, so a self-pay patient never sees the insurance block and an adult never sees the guardian section. The important word is conditional. Every rule is authored, visible and editable by your practice, and the form has no opinion of its own about any answer.

View raw text version for AI/LLMs