Form Filling & Form Processing

Form Filling & Form Processing

Who this is for: support staff, care-team staff, doctors, new hires.

Two form moments in a case

1. Pre-qualification questions happen before the case is even created, during “getting started” (see Onboarding & signup).
2. The intake form happens after the case is created and (usually) paid for. This is the official form whose answers feed directly into the government document the doctor will sign.

Patient side: filling out the intake form

1. The patient reaches the intake step from their case’s status page.
2. Questions are grouped into pages; each page can include multiple choice, checkboxes, short text, dates, name fields, and file uploads (ID, medical records, supporting documents).
3. As the patient completes each page, their answers are saved to that case so progress isn’t lost if they leave and come back.
4. Depending on the service, a review/confirmation step lets the patient look over their answers before finishing.
5. Some services also require a separate mental-health screening questionnaire, and/or a government ID upload and a medical-records upload, as distinct steps alongside the main intake form.
6. What questions appear can differ by state and by which specific version of the service the patient chose (see Services catalog) — the system loads the right question set based on the patient’s service, sub-type, and state, falling back to a general question set if no state-specific one exists.

Care team side: reviewing and processing the form

1. Once a patient completes intake, their case appears in the doctor’s task queue (and, depending on the case type, in care-team queues if outreach is needed first — see Care team workflows).
2. The doctor opens the case and sees the patient’s intake answers alongside any uploaded documents.
3. The doctor can add or correct medical-judgment fields that the patient wouldn’t fill in themselves, then approve the case to move it toward document generation.
4. For services where a state supports more than one official form variant (for example a placard form vs. a license-plate form, or a permanent vs. temporary disability form), the doctor can choose which variant applies to this patient, and the system can flag whether an additional form looks necessary based on the patient’s answers.
5. Approving the case in the care portal is the trigger that starts the government-form generation and signing process — covered in Document generation & e-signature.

Open questions

• The full list of validation rules that block a doctor from approving an incomplete case was not exhaustively traced.
• Exactly how “suggested additional forms” are surfaced to the doctor (automatic prompt vs. manual checklist) was not fully confirmed in the UI code reviewed.

Where this comes from

• parkingmd-patient-portal/documentation/service-flow.md (fulfillment path steps: intake, id-upload, medical-records-upload, mental-health-questionnaire)
• parkingmd-patient-portal/src/services/formConfigService/
• parkingmd-patient-portal/src/models/intake-forms.ts
• parkingmd-patient-portal/src/trpc/routers/ (intake.ts, onboarding.ts, assessment.ts, mental-health.ts)
• parkingmd-patient-portal/data/form-config/ (per-service, per-state question configs)
• parkingmd-care-portal/docs/MULTI_FORM_SYSTEM.md, MULTI_FORM_QUICK_REF.md
• parkingmd-care-portal/src/lib/intake/
• parkingmd-care-portal/src/lib/tasks/ (approve/status transitions)
• parkingmd-care-portal/docs/care-portal-kt-guide.md