Portal Forms

The Student Health Profile

Quick answer: Each student has a Health Profile that holds medical info — allergies, medications, doctor, insurance, emergency contact. Forms read from it and write back to it, so parents only enter this information once.

What it stores

The Health Profile holds these fields per student:

• Emergency contact (name, relationship, phone)
• Primary doctor (name, phone)
• Preferred hospital
• Health insurance provider and policy number
• Allergies (free-form list)
• Current medications (free-form list)
• Medical conditions (free-form)
• Standing permissions (OTC meds, sunscreen, insect repellent, transport)
• Last-reviewed date and which parent reviewed it

How it integrates with forms

Each form field can have a pre-fill source. For health-related fields, the source is one of the health.* options — like health.allergies or health.emergency_contact_name.

When a parent opens a form with these pre-fills:

1. The form pulls the latest value from the Health Profile and shows it pre-filled.
2. The parent reviews and either leaves it as-is or updates it.
3. When they submit, the form's answer is stored on the submission as usual AND writes back to the Health Profile so the next form sees the latest value.

This is the key trick: the Health Profile is automatically maintained through normal form submissions. Parents don't need to know it exists. They fill out the trip form, and the side effect is that next month's field-trip form pre-fills with the answers they gave today.

A worked example

Imagine you have three forms over the school year:

1. September: Health Form / Medical Information — a parent fills out allergies, doctor, insurance.
2. October: Field Trip Permission — Pumpkin Patch — the form reads from the Health Profile and shows the September allergies pre-filled. The parent confirms or updates.
3. March: Field Trip Permission — Spring Adventure — the form pre-fills with whatever was in the Health Profile after the October submission.

The parent never re-types "peanut allergy" three times. The information automatically stays current.

Who can see and edit the Profile

• Parents: indirectly — through the form they're filling out. Whatever they type in a health-pre-filled field becomes the new Health Profile value.
• School staff: can view (and in a future release, directly edit) the Health Profile from the admin dashboard.
• The Health Profile is per-student. Sibling 1's profile is separate from sibling 2's.

Best practices

• Use the same field key everywhere. If your Health Form calls the field allergies and your Field Trip Form also calls it allergies, the data shares the same Profile slot. If they have different field keys, they're separate fields and don't cross-pollinate.
• Use health.* pre-fills on every form that asks the same question. Even if the form's purpose is different, the medical questions should pre-fill from the Profile.
• Don't make Health Profile fields required on a form unless they need fresh confirmation. If a field is just for review, mark it optional and trust pre-fill.

What about families with no health information yet?

If a parent opens their first health-related form and the Health Profile is empty, the fields show up blank — just like a regular form. After they submit, the Profile is populated for next time. There's no setup step required.

Related articles

• Pre-filling parent and student data
• Field types in the form builder
• Connecting form data back to Growth Suite