Pediatric Intake Forms: Parent/Guardian Authorization, Vaccine History, and Developmental Screening

Why Pediatric Practices Need Intake Forms Built for Guardian Authorization

A pediatric patient intake form is structurally different from an adult intake. The patient is the child; the consenting party is one or two legal guardians; the chart has to capture custody status, vaccine history, developmental milestones, and a record of which guardian can authorize what kind of care. A generic intake collects none of this. The result is a custody dispute that surfaces at the front desk, a vaccine record that is incomplete because the prior practice never sent it, and a developmental concern that should have triggered an early-intervention referral but never did.

The cost is paid in clinical missed catches and in front-office friction. A well-child visit that does not capture vaccine status accurately produces either over-vaccination (rare) or under-vaccination (common); a developmental screen that does not capture milestones systematically misses the early-intervention window; a custody dispute that surfaces at the front desk delays urgent care. Most pediatric practices today juggle a paper packet, a vaccine history call to the prior practice, a separate developmental screener, and an EHR that gets re-keyed from the paperwork. This means demographics get captured twice, custody status gets re-asked, and the audit trail lives in three places.

What a Complete Pediatric Intake Workflow Includes

A complete pediatric intake replaces a paper packet, a vaccine history phone call, a separate developmental screener, and the unstructured first half of the new-patient well-child visit.

A strong digital pediatric intake workflow typically covers these components:

1. Child demographics — legal name, preferred name, date of birth, sex assigned at birth, gender identity where the family elects to share, primary language at home.
2. Parent/guardian verification and custody status — each guardian's name, relationship, contact, and authority to consent; any custody order limiting authority.
3. Birth and developmental history — pregnancy and delivery summary, Apgar score if known, growth percentile history, developmental milestones to date.
4. Vaccination record and schedule — full vaccine history with dates and source (state immunization registry, prior practice, family record).
5. Allergy and medication tracking — food allergies (especially anaphylaxis-grade), medication allergies, current medications including dose by weight.
6. Family health history — first- and second-degree family medical history relevant to pediatric screening.
7. Consent to treat minor — primary guardian consent with a clear scope (well care, sick care, urgent care, mental health), plus any standing authorization for the other guardian, family member, or caregiver.
8. Electronic signature capture — timestamped acknowledgment tied to the version of the consent text the guardian actually saw.

Parent/Guardian Verification and Custody Status

Parent and guardian verification is the highest-friction part of pediatric intake and the most consequential. Capture each guardian by legal name, relationship to the child (biological mother, biological father, adoptive parent, legal guardian, stepparent without legal guardianship), contact information, and authority to consent for the child. Capture custody status explicitly: married parents living together, separated parents with shared custody, sole legal custody by one parent, legal guardianship by a non-parent, foster placement, kinship care.

For separated or divorced parents, capture whether a custody order limits one parent's authority to consent to medical care or to specific categories of medical care (mental health care, gender-affirming care, vaccinations, surgical care). Some custody orders require both parents' consent for non-emergency care; some assign sole medical decision-making authority to one parent. The intake should ask the guardian to upload or describe the operative custody order, and the front-office workflow should treat the order as authoritative when consent disputes arise.

For grandparents or other family caregivers, the intake should distinguish between legal guardianship (which carries authority to consent) and informal kinship care (which may not, and which often requires a power-of-attorney document for the practice to rely on). The related minor consent forms guide covers the wider considerations for consenting on behalf of a minor across practice types.

Birth and Developmental History

The birth and developmental history block supports the well-child visit and the early-intervention referral pathway. Capture pregnancy and delivery summary (full-term, premature with gestational age, mode of delivery, any complications), Apgar score if the family knows it, birth weight and length, NICU stay if applicable, and any neonatal screening results. Capture growth percentile history if the family has it (a child who has crossed major percentile lines on the growth curve is a different evaluation than a child following a stable curve).

Developmental milestones should be captured by age band and by domain: gross motor, fine motor, language and communication, social and emotional, cognitive. The CDC milestone checklists are a common reference; many pediatric practices integrate the M-CHAT-R for autism screening at appropriate ages and the ASQ for general developmental screening. The intake can deliver the structured screener as part of the new-patient packet so the clinician arrives at the visit with the screening done and any concerning answer flagged.

For practices that integrate behavioral health, the related counseling intake forms show the related architecture for capturing developmental and behavioral history in mental health work.

Vaccination Record and Schedule

The vaccination block should capture the full vaccine history with dates and source. The CDC schedule is the reference standard, and most state immunization registries (IIS) serve as the authoritative source for vaccines administered in that state. The intake should ask the family to upload a vaccine record from their prior practice, capture which state immunization registry the family has used (if any), and provide an explicit field for any vaccine the family has elected to defer or decline.

Vaccine refusal documentation is a sensitive but necessary part of pediatric intake in 2026. The intake should capture which vaccines the family has elected not to administer, the reason if the family wishes to share it, and the practice's standard counseling approach (which varies by practice). A practice that requires a signed vaccine refusal acknowledgment should capture the signed document at intake; a practice that uses a different counseling approach should capture the family's preferences.

For families relocating from another state, the intake should request the family pull the prior state's IIS record where possible. The practice's workflow can then reconcile the prior IIS record against the current state's IIS for completeness. Vaccination records are the most-requested record in pediatric practice, and a strong intake architecture saves hours of phone calls per week.

Allergy and Medication Tracking

The allergy block on a pediatric intake is the safety screen. Capture food allergies with the specific food, the reaction type (hives, GI symptoms, anaphylaxis with epinephrine use), and the date and detail of any prior anaphylactic reaction. Capture medication allergies with the drug class and the specific reaction. Capture environmental allergies (pollen, dust, animal dander) where the family knows them.

For anaphylaxis-grade food allergies, the intake should also capture whether the family has an epinephrine auto-injector in date, whether the school or daycare has a plan on file, and whether the practice has previously prescribed an EAP (emergency action plan). The related daycare liability permission forms show the related architecture for integrating allergy plans with childcare settings.

Current medications should be captured with dose by weight where applicable (pediatric medications are often dosed in mg/kg, and a dose recorded in mg without the corresponding weight is harder to verify against current weight at the visit). Build the intake to ask for the date of the dose calculation and the weight at calculation, so the prescribing clinician can verify the dose against current weight.

Consent to Treat Minor

Consent to treat a minor should clearly state who is consenting (the legal guardian by name), what scope of care is consented to (well care, sick care, urgent care, mental health care, surgical care, vaccination), and whether a second guardian's signature is required for any category. The consent should describe the limits of confidentiality for the minor (especially adolescents, where state law often gives minors confidentiality for specific care categories such as reproductive health and substance use treatment), the practice's policy on parental access to the chart, and any practice-specific telehealth consent.

Standing authorization for non-guardian caregivers is a separate document. A grandparent who picks the child up from daycare and brings them to a sick visit should have a standing authorization on file that authorizes the grandparent to consent to specific kinds of care in the parent's absence. The intake should support this by collecting standing authorization as a separate document with named caregivers, scope, and expiration.

For practices handling PHI under HIPAA, the related HIPAA-compliant intake forms guide covers the additional digital intake requirements, including the special rules for minors' protected health information.

The Thin-Form Problem in Pediatrics

Generic form builders ship with contact-form templates that are not built for pediatrics. The thin form gets a child's name, a parent's email, and a paragraph of free text. Compare to a workflow built for a pediatric practice:

The thin form costs nothing the day a parent registers a child. It costs a great deal the day a custody dispute surfaces, a vaccine is missed, or an anaphylactic reaction happens at school without a current EAP on file. Cheap on the front end, expensive on the back end.

Adolescent Confidentiality, Minor Consent Categories, and Mature-Minor Doctrine

Adolescent intake adds layers that pediatric intake for younger children does not have. State law typically grants minors specific confidentiality categories — reproductive and sexual health care, mental health treatment, substance use treatment, and care for sexually transmitted infections are the most common — where the adolescent's information is confidential from the parent. The intake should capture the adolescent's awareness of these confidentiality categories, the practice's policy on each, and the adolescent's preferred contact method (some adolescents prefer text rather than calls home for appointment reminders).

The mature-minor doctrine applies in some states for specific care decisions, allowing a minor with sufficient maturity to consent to specific care without parental involvement. The intake should reflect state law and the practice's policy. For practices that work alongside school-based health centers or adolescent-specific programs, the intake architecture has to support different consent paths for different care categories within the same patient.

Telehealth Pediatric Visits and School-Form Workflow

Pediatric telehealth grew significantly during the pandemic and remains a substantial portion of pediatric primary care. Telehealth intake adds the parent's location during the visit, the child's location during the visit, the technology platform being used, and an explicit acknowledgment of telehealth limitations (some pediatric assessments require in-person evaluation). For minor adolescents on telehealth, the intake adds confidentiality considerations for the household — an adolescent on telehealth in a shared bedroom may not feel comfortable discussing sensitive topics.

School forms are a recurring pediatric workflow: sports physicals, camp forms, college health forms, immunization records for school enrollment, accommodations forms for IEP and 504 plans, medication-administration authorizations. The intake architecture should support a structured school-form workflow with the relevant clinical fields auto-populated from the chart and the parent's signature captured digitally.

Common Implementation Mistakes Pediatric Practices Make on First Digital Intake

The most common mistake on a first digital pediatric intake is collecting parent contact information without explicit custody status. Custody disputes surface later and the intake should capture enough to resolve them at the front desk. The second mistake is treating vaccine history as a free-text field; structured per-vaccine capture with date and source is materially more useful. The third mistake is omitting standing authorization for non-guardian caregivers; a grandparent picking up a sick child without standing authorization on file creates friction at the worst moment.

The fourth mistake is failing to support the school-form workflow. Schools, camps, and sports programs request forms continuously, and a practice without a structured school-form workflow ends up retyping clinical information for each request.

Migration Path for Practices Adding Behavioral Health Integration

Pediatric practices adding behavioral health integration (a behavioral health clinician embedded in the practice) should plan the intake architecture to support the integration. Phase one: confirm consent text for the integrated behavioral health service with the lead clinician and with counsel. Phase two: build the behavioral health add-on so a child seeing both the pediatrician and the behavioral health clinician completes the core pediatric intake plus the behavioral health add-on. Phase three: pilot with families who have already engaged with both services.

How Formfy Handles Pediatric Intake Workflows

Formfy is built for vertical-specific workflows rather than generic form fields, which means a pediatric practice can build a complete intake without writing custom logic.

Prompt-based creation: Describe the practice, the populations served (general pediatrics, adolescent medicine, special-needs care, behavioral health integration), the well-child schedule, and any state-specific consent rules for minors, and Formfy's AI Copilot generates a draft intake covering child demographics, guardian and custody capture, birth and developmental history, vaccine record, allergies and medications, family history, and consent to treat minor. The draft can be edited line by line before the first family ever sees it.

Upload and convert: Pediatric practices with existing PDF intake packets can upload them and have Formfy convert each page into a digital form, preserving the consent text verbatim while turning checkboxes and signature fields into native digital inputs. This is usually the faster path for practices where the consent has been reviewed by counsel.

Best for pediatric practices that want vertical-specific defaults rather than building a generic form and adding compliance language afterward.

Building a Multi-Visit Pediatric Intake System

Practices that handle well-child, sick, urgent, and behavioral health visits benefit from a system rather than a single mega-form.

1. Core intake form — child demographics, guardian and custody, birth and developmental history, vaccine record, allergies and medications, family history, and base consent collected once and reused across visit types.
2. Visit-type add-ons — separate documents for well-child screeners by age band (M-CHAT-R, ASQ), sick-visit symptom capture, urgent-visit triage, behavioral health intake, and adolescent confidential intake.
3. Standing authorization — collected separately so non-guardian caregivers (grandparents, after-school staff) have specific scope and expiration.
4. Annual review cycle — forms reviewed when CDC vaccine schedule, state immunization registry rules, or pediatric consent law change so consent on file always matches current practice.

Most pediatric practices find this system pays for itself the first time a custody dispute is resolved by an order on file or the first time a returning family arrives with a clean vaccine record from the prior practice. See Formfy pricing for the plan that fits a solo pediatrician or a multi-physician practice.

Key Takeaways

• Pediatric intake forms must be vertical-specific — generic forms miss custody documentation, structured vaccine capture, developmental milestone screening, and standing authorization for non-guardian caregivers.
• Generic intake templates leave gaps in anaphylaxis EAP capture, pediatric dose-by-weight, vaccine refusal documentation, and adolescent confidentiality scope.
• A complete workflow includes child demographics, guardian and custody capture, birth and developmental history, vaccine record, allergies and medications, family history, consent to treat minor, standing authorization, and electronic signature capture.
• Formfy generates tailored pediatric intake forms from prompts or converts existing paper and PDF forms into digital workflows.
• Multi-visit pediatric practices benefit from a system with a core intake plus visit-type add-ons and a separate standing authorization document.
• Pediatric intake forms should be reviewed regularly as CDC vaccine schedule, state immunization registry rules, and pediatric consent law change.

This article is for informational purposes only and does not constitute legal or medical advice. Consult a licensed attorney for jurisdiction-specific guidance.

This article is for informational purposes only and does not constitute legal advice. Consult a licensed attorney for jurisdiction-specific guidance.