Compliance SSA-3373
Validation Checks by Instafill.ai
1
Disabled Person Name Completeness and Character Validation
Validate that the disabled personâs name includes at least a first and last name, and that the middle initial (if provided) is a single alphabetic character. Reject or flag entries containing invalid characters (e.g., excessive punctuation, numbers) or placeholder text. This matters because the name is a primary identifier used to match the form to the correct claim record; failures should trigger a request for correction or manual review.
2
Social Security Number (SSN) Format and Disallowed Values Check
Ensure the SSN is exactly 9 digits (or formatted as XXX-XX-XXXX) and contains only numeric characters aside from optional hyphens. Flag known invalid patterns such as all zeros in any group (e.g., 000-xx-xxxx, xxx-00-xxxx, xxx-xx-0000) or 123-45-6789. This is critical for identity matching and downstream eligibility processing; failures should block submission or route to exception handling.
3
Daytime Telephone Number Structure and Selection Consistency
Validate that the phone number includes a valid area code and 7-digit local number (10 digits total) and contains only digits and standard separators. If the form allows selecting âYour Number,â âMessage Number,â or âNone,â ensure exactly one option is selected and that a phone number is present unless âNoneâ is selected. This prevents unreachable claimants and reduces adjudication delays; failures should prompt the user to correct the number or confirm âNone.â
4
Living Arrangement (Where Do You Live) Single-Choice and 'Other' Detail Requirement
Confirm that exactly one residence type is selected (House, Apartment, Boarding House, Nursing Home, Shelter, Group Home, Other). If âOtherâ is selected, require a non-empty explanation in the âWhat?â field with meaningful text (not just 'N/A'). This ensures accurate context for functional limitations and contact logistics; failures should require completion before acceptance.
5
Household Composition (With Whom Do You Live) Single-Choice and Relationship Detail Requirement
Ensure exactly one option is selected (Alone, With Family, With Friends, Other). If âOtherâ is selected, require a relationship description (e.g., roommate, caregiver) and flag vague entries like âsomeoneâ without clarification. This is important for interpreting assistance levels and daily functioning; failures should trigger a correction request or manual follow-up.
6
Work Limitation Narrative (Question 5) Non-Blank and Minimum Information Check
Validate that the response describing how conditions limit ability to work is not blank and is not only a placeholder (e.g., empty, 'â', or whitespace). If the user enters ânone/does not apply,â require confirmation because the form is for disability-related limitations and such an answer may be inconsistent. This narrative is central to disability evaluation; failures should prevent submission or be flagged for adjudicator review.
7
Daily Routine Description (Question 6) Completeness Check
Require a non-empty description of activities from waking to bedtime, and flag responses that are too short to be meaningful (e.g., single word answers) unless âdonât know/noneâ is explicitly used with explanation. This information supports functional assessment across the day; missing or minimal content reduces decision accuracy. If validation fails, prompt for additional detail or route to manual review.
8
Conditional Detail Enforcement for Yes/No Questions (Caregiving, Pets, Sleep, Assistance)
For questions 7, 8, 9, and 11, enforce that a Yes/No selection is made and that any âYESâ answer includes the required follow-up details (who/what/how). For example, if âYesâ to caring for pets, require what tasks are performed; if âYesâ to help from others, require who helps and what they do. This prevents incomplete branching data that adjudicators rely on; failures should block submission until follow-ups are completed.
9
Personal Care Section Consistency (No-Problem Checkbox vs. Explanations)
If the âNO PROBLEM with personal careâ checkbox is selected, ensure no personal care limitations are described in the explanation fields (Dress, Bathe, etc.), or require the user to reconcile the contradiction. If the checkbox is not selected, require at least one personal care impact to be described or an explicit ânone/does not apply.â This consistency is important for accurate functional scoring; failures should prompt correction.
10
Meals Preparation Logic and Follow-Up Completeness (Question 13)
If the user answers âYesâ to preparing meals, require entries for type of food, frequency, time to prepare, and changes since onset (or explicit 'none'). If the user answers âNo,â require a reason in 13b and ensure the âYesâ detail fields are not filled in a conflicting way. This ensures the record clearly reflects independent living skills; failures should require completion or clarification.
11
House and Yard Work Detail Requirements and Contradiction Check (Question 14)
If chores are listed in 14a, require corresponding frequency/time details in 14b and ensure the âI donât do house or yard workâ explanation (14d) is not simultaneously provided without clarification. If no chores are listed, require 14d to explain why not. This matters because household activity is a key functional indicator; failures should prompt the user to add missing details or resolve contradictions.
12
Getting Around and Driving Consistency (Question 15)
Require an answer for how often the person goes outside, and if they indicate they do go out, require at least one travel method selection (walk/drive/ride/public transit/other). If âDo you drive?â is âYes,â ensure âDrive a carâ is selected as a travel method or require an explanation; if âNo,â require a reason. This prevents inconsistent mobility data; failures should trigger correction prompts.
13
Shopping Section Completeness When Applicable (Question 16)
If any shopping method is selected (in stores/phone/mail/computer), require what they shop for and how often/how long it takes. If no method is selected, require an explicit statement that they do not shop (or 'does not apply') to avoid ambiguity. Shopping ability is used to assess independence and cognitive/physical capacity; failures should require completion.
14
Money Management Explanation Requirement for Any 'No' (Question 17)
For each money-handling item (pay bills, count change, handle savings, use checkbook/money orders), require a Yes/No response and enforce that any âNoâ has an explanation in the provided field. If the ability changed since onset is âYes,â require a description of what changed and when/why if provided. This is important for evaluating cognitive functioning and representative payee needs; failures should block submission or be flagged.
15
Abilities Section (Question 20) Checked-Item Explanation and Quantitative Fields Validation
If any ability items are checked (e.g., lifting, walking, concentration), require an explanation for each checked item and flag missing explanations. Validate quantitative responses where expected: walking distance should be a positive number with units (feet/yards/miles), rest duration and attention span should include time units (minutes/hours). This ensures the data is actionable for functional capacity assessment; failures should prompt for units/details or route to manual review.
16
Assistive Devices Section (Question 21) Prescription and Usage Detail Validation
If any assistive device is checked, require completion of: which were prescribed by a doctor, when prescribed (at least month/year or a valid date), and when the aids are needed (frequency/conditions). If âOtherâ is checked, require a description of the device. This is important for corroborating severity and treatment history; failures should require additional detail or be flagged for follow-up.
17
Medicines and Side Effects Branching Completeness (Question 22 and Page 10 Side Effects Table)
Require a Yes/No answer to whether medicines are currently taken; if âYes,â require a Yes/No answer for side effects. If side effects are âYes,â require at least one row in the medicine/side effects table with both fields populated, and discourage listing all medicines by flagging unusually long lists for review. This supports symptom evaluation and credibility of limitations; failures should prompt completion or clarification.
18
Person Completing the Form Identity and Submission Date Validation (Page 10)
Require the name of the person completing the form and a valid date in MM/DD/YYYY format, ensuring the date is a real calendar date and not in the future. If the completer is not the disabled person (implied by differing names if available), require a complete mailing address (street, city, state, ZIP) and validate state as a 2-letter code and ZIP as 5 digits (optionally ZIP+4). This is essential for follow-up contact and evidentiary integrity; failures should block submission until corrected.