How to build a HIPAA-compliant patient registration and insurance verification intake in Formaloo

By the end of this guide, you'll have a patient registration form that captures insurance and ID uploads directly into admin-only fields, so protected health information stays out of view until your front-desk team verifies it. Verification status changes trigger the right email automatically, PHI anonymizes itself after your retention window closes, and each location's front-desk team only ever sees the patients assigned to them.

This is the form that becomes your patient database. It captures the patient's details, routes them to the right location, and gates the insurance section behind a simple yes/no question so patients who self-pay never see irrelevant fields. The fastest way to build it is with Magic Create, Formaloo's AI form builder, so you're verifying a generated form rather than dragging in fields one at a time.

1. Open Magic Create: From your Formaloo homepage, click Magic Create.

2. Describe the form: Paste a prompt describing the intake, for example: "A patient registration form for a multi-location clinic. Start with a yes/no consent question for HIPAA and GDPR processing. Then collect full name, date of birth, phone number, email, home address, a dropdown for which clinic location the patient is registering at (options: Downtown clinic, Uptown clinic), reason for visit, and a yes/no for whether the patient has insurance. If yes, show insurance provider, policy or member ID, and file uploads for the front and back of the insurance card. Also collect a file upload for a government ID. Make the insurance card uploads, ID upload, verification status dropdown (Not started, Pending review, Verified, Needs follow-up), an assignee field, and an internal notes field all admin-only."

3. Generate the form: Click Create and let Magic Create build the form.

4. Verify your fields: Your form should look like this, Magic Create will have generated most of it. Verify each field and field ID matches exactly.

5. Publish the form: Click Publish in the island bar at the top of the editor. Publish is different from Save, Save applies to logic rules, email templates, and PDF templates, not the form itself.

This is where the form stops being a static list of questions and starts behaving like a real intake process. You'll gate the whole form behind consent, show the insurance section only when it's relevant, and route each new registration to the right location's front-desk team automatically. The fastest way to do this is Magic Logic, which turns a plain-language description into a set of rules you can review before saving.

1. Open advanced logic: In your form editor, open Advanced logic from the settings panel on the right side, then go to the Logic tab.

2. Open Magic Logic: Click Magic Logic in the top right corner of the Logic panel.

3. Describe the rules: Paste a prompt describing all four rules at once: "If 'Do you consent to Formaloo storing and processing this information under HIPAA and GDPR?' is No, hide every field below it and show a message that registration can't continue without consent. Default: rest of the form is visible. If 'Does the patient have health insurance?' is Yes, show the insurance provider, policy or member ID, and both insurance card upload fields. Default: those four fields are hidden. On submit, if 'Which location is this registration for?' equals Downtown clinic, assign 'Who's the assigned staff member?' to the Downtown front desk team. If it equals Uptown clinic, assign to the Uptown front desk team. On update, if 'What's the verification status?' is changed to Verified, send the insurance verified email to the patient's email. If it's changed to Needs follow-up, send the needs follow-up email to the patient's email."

4. Generate and review the rules: Click Generate rules. Review the AI's preview of each rule, and approve, redo, or cancel as needed.

5. Make the consent question required: While you're in the form editor, open "Do you consent to Formaloo storing and processing this information under HIPAA and GDPR?" and turn on Required, so nobody can submit without answering it.

6. Save your logic: Once you're satisfied with the generated rules, click Save in the top right corner.

Four emails carry this workflow from submission through verification: one confirms the registration, one alerts front-desk staff that a new patient is waiting on them, and two follow up on whatever the verification outcome turns out to be.

1. Open email templates: Click your profile icon, go to Apps & integrations, then Email templates.

2. Create the registration received template: Click + Add new template, name it "Registration received." Set the subject to "Your registration at @registration_location is confirmed." Add an AI block and prompt it to write a warm, brief confirmation to @patient_full_name confirming their registration for @visit_reason was received and that staff will verify their insurance before the visit. Save.

3. Create the front-desk alert template: Add another template named "New registration alert." Subject: "New patient registration at @registration_location." Prompt it to write a short, factual internal alert referencing @patient_full_name, @visit_reason, and @registration_location, noting that insurance verification is pending. Save.

4. Create the insurance verified template: Add a template named "Insurance verified." Subject: "Your insurance is verified, @patient_full_name." Prompt it to write a short, reassuring confirmation that insurance is verified ahead of the visit. Save.

5. Create the needs follow-up template: Add a template named "Needs follow-up." Subject: "We need a bit more info before your visit." Prompt it to write a clear, non-alarming message asking the patient to call or reply with missing insurance details. Save.

6. Connect the confirmation and alert emails to submission: Back in Advanced logic, under On submit, add a Send email rule using the "Registration received" template to the patient's email field, and a second Send email rule using the "New registration alert" template to the assigned staff member.

Front-desk staff need one document per patient that pulls together identity, insurance, and consent for the chart, not four separate screenshots.

1. Open PDF templates: Click your profile icon, go to Apps & integrations, then PDF templates.

2. Add a new template: Click + Add new template, name it "Patient registration & insurance verification summary."

3. Switch to HTML view: Toggle the editor to HTML and paste your design, using @patient_full_name, @patient_dob, @registration_location, @insurance_provider, @verification_status, and PR-@rowid as the reference number for the header.

4. Save the template.

5. Generate the PDF automatically: In Advanced logic, under On submit, add a Generate PDF rule using this template. The file appears on the response row for every new registration.

This is the part that actually satisfies a retention policy instead of just talking about one. Once it's on, any record older than the number of days you set gets its protected health information anonymized automatically, per record, counted from the day it was submitted.

1. Open privacy and compliance settings: From the island toolbar at the top of the form editor, open the form settings icon and find the Privacy and compliance section.

Note: If this section shows a prompt instead of the settings, your workspace doesn't have the automatic anonymization add-on yet. You'll see a prompt and the option to contact sales support to add it.

2. Turn on automatic anonymization: Enable the toggle for automatic anonymization.

3. Set the retention window: In the Anonymize after (days) field, enter how many days after submission a record should be anonymized, anywhere from 1 to 3,350 days.

4. Choose which fields to anonymize: Under Select fields to anonymize, click Select fields and choose the PHI fields, at minimum the insurance card uploads, ID upload, insurance policy or member ID, and insurance provider.

5. Confirm the warning: Review the confirmation modal, this action can't be undone once a record is anonymized, then save your settings.

Patients never log in anywhere in this workflow, they only fill out the public form. What needs a portal is the internal side: front-desk staff should only see the patients assigned to them, and that assignment already routes by location thanks to the logic rule from Part 2.

1. Activate the portal: Open your project and click the gear icon in the top right corner, then click Activate portal.

2. Keep the intake page public: On the page holding your registration form, set external access to Public, so patients never need to log in to register.

3. Create a team per location: In your workspace member settings, create a team for each clinic location (for example, Downtown front desk and Uptown front desk) and add each location's staff to their team.

4. Add a shared assigned-patients page: Add a Kanban data block connected to your form, grouped by verification status. This is the one page every front-desk team member opens.

5. Restrict it to assigned records only: Switch the data block to Edit mode, click Options, scroll to Manage access, select the assignee field, and turn on Allow assignees to view only their data. Because the Downtown team is only ever assigned Downtown registrations, each team automatically sees just their own location's patients on this same shared page, no duplicate pages required.

6. Restrict the page to internal staff: Click the three-dot menu next to the page in the portal navigation, select Access, and set it to internal workspace team members only, not public or anyone with the link.

7. Give compliance staff full visibility: Add a second Kanban or table page with no assignee restriction, and set its access to a compliance or records-admin team so they can see every location's registrations for auditing.

Patients register once, from any device, without ever creating an account or seeing a single admin field. Insurance cards and IDs land directly in admin-only fields, invisible until a staff member opens the record to verify them, and both sides get an automatic email the moment verification status changes. Records older than your retention window anonymize themselves without anyone remembering to run a cleanup job. Front-desk staff at every location open the same shared page and only ever see the patients assigned to their site.

Don't build this from scratch, we've already put it together for you.