What makes a good pediatric booking flow

Pediatric booking is a study in who the user actually is. The patient is a child; the user is the parent. Most pediatric booking flows confuse the two — fields labeled "your first name", an intake form that talks to the patient in second person, no place to record that the parent is the one filling out the form. The result is a flow the parent has to mentally translate at every step, and a record that doesn't cleanly distinguish parent identity from patient identity for downstream HIPAA workflows.

The right shape is parent-first by data model and by copy. The form opens with the parent's name ("your name as the parent or guardian"), then transitions to a separate fieldset for the child (first name, last name, age). The schema has corresponding distinct columns — parent_or_guardian (encrypted PHI), patient first/last (encrypted PHI), child_age (plain integer because HIPAA Safe Harbor permits ages under 90 without aggregation). The clinic-side review surface labels the parent as the requestor and the child as the patient throughout.

Age routing is the second-tier consideration: under-5 cases benefit from developmental questions (eating habits, thumb- sucking, sleep patterns); school-age cases benefit from vaccination and medication context; teen cases approach adult intake. v1 of Dream Create's pediatric flow collects the bare minimum at booking; the deeper intake form ships per-clinic on request. The hard rule is that photos and video — common for special-needs visit prep — go through the same encrypted PHI posture as everything else, never through marketing analytics.

COPPA is the hard line. The platform never collects data directly from a child under 13. The booking form's copy is explicit ("the parent or guardian fills this in"); the schema enforces it (the bookingSubmissionSchema fail-closes when isPediatric=true without a parent_or_guardian); the studio review surface mirrors the parent-first labels. None of these alone is enough. The combination of copy, schema, and chrome makes the parent-first model the easy path, and any other flow requires explicit deviation.

The conversion payoff is real: a parent who submits a booking and feels the form understood their role calls back at higher rates than one who had to fight the form's pronouns to make their case. Pediatric clinics that have switched to the parent-first model report fewer abandoned submissions and more patient-side context in the reason-for-visit field.