Compliance CPPA
Validation Checks by Instafill.ai
1
Applicant legal name completeness and character validation
Validates that Last Name and First Name are present and contain only expected characters (letters, spaces, hyphens, apostrophes) and are not placeholder values (e.g., “N/A”, “.”). Middle name/initial may be blank, but if provided it must follow the same character rules. This is important for identity matching across licensing, NPI, and payer enrollment systems. If validation fails, the submission should be rejected or routed to manual review because downstream primary source verification may not match.
2
Other names used required when indicated and properly formatted
If the applicant indicates they have been known under another name, the “Other Names Used” field must be populated with at least one non-empty name and separated by commas when multiple are provided. The check also flags entries that repeat the current legal name only or contain non-name placeholders. This matters because credentialing and sanctions checks often rely on historical names. If it fails, the system should require correction before submission to avoid incomplete background checks.
3
Date fields format and validity (DOB, issue/expiration, training, work history)
Ensures all date fields follow the form’s expected formats: full dates where requested (e.g., Birth Date, signature dates) and month/year where specified (mm/yyyy or mm/yy) for training, affiliations, and work history. It also validates that dates are real calendar dates and not future-dated where inappropriate (e.g., DOB cannot be in the future). Correct date formatting is critical for automated eligibility and timeline checks. If invalid, the system should block submission and highlight the specific field and required format.
4
Phone and fax number format validation across all contact fields
Validates that telephone, fax, cell, pager, medical staff phone, registrar phone, and administrator phone fields contain valid phone patterns (10 digits for US numbers, optional country code, and optional extension) and are not alphabetic strings. This prevents failed outreach to references, hospitals, and carriers during verification. If validation fails, the system should prompt for correction and optionally allow a “no fax” scenario only when the fax field is truly optional.
5
Email address format validation (practitioner, administrator, references, carriers, answering service)
Checks that all provided email addresses conform to standard email syntax (local@domain) and do not contain spaces or invalid characters. It should also flag obvious placeholders (e.g., test@test, none@none) if your business rules disallow them. Email accuracy is important for credentialing communications and document follow-ups. If validation fails, the system should require correction or mark the record for manual outreach depending on whether the email is required.
6
Address completeness and state/ZIP validation for US locations
Ensures that required addresses (home mailing, primary office, and any secondary/tertiary/billing/answering service/hospital addresses when provided) include street, city, state, and ZIP. State should be a valid US state/territory abbreviation (e.g., CA) and ZIP should be 5 digits or ZIP+4. This is important for network directory accuracy, service area validation, and correspondence. If validation fails, the system should block submission for required addresses and warn for optional sections that were partially completed.
7
SSN format and basic plausibility validation
Validates that Social Security Number is 9 digits (allowing hyphens) and rejects known invalid patterns (e.g., 000-00-0000, 123-45-6789) if your policy includes plausibility checks. SSN is used for identity verification and payer enrollment matching. If validation fails, the system should prevent submission and require correction because incorrect SSNs can cause verification failures and delays.
8
Driver’s license state/number structure validation
Checks that the driver’s license entry includes an issuing state (two-letter code) and a non-empty license number, and that the number matches expected alphanumeric patterns (without illegal characters). This supports identity verification and reduces manual follow-up. If validation fails, the system should request correction or allow omission only if the field is not required by the receiving organization.
9
Role selection and specialty consistency validation
Ensures at least one “intent to serve as” role is selected (Primary Care Provider, Specialist, Urgent Care, Hospitalist, Hospital Based) and that Specialty is provided when a clinical role is selected. If “Hospital Based” is selected, Department Name fields for applicable practice locations should be required or explicitly marked not applicable. This matters for correct network assignment, directory listing, and appropriate credentialing pathways. If validation fails, the system should block submission and prompt the applicant to reconcile role and specialty/department details.
10
Practice location section integrity (primary required; secondary/tertiary all-or-nothing)
Validates that the Primary Practice section has minimum required fields (office address, city/state/ZIP, phone, accessibility selection, and at least one practice type). For Secondary and Tertiary locations, if any key field is entered (e.g., address or phone), then the rest of the required location fields must also be completed to avoid partial, unusable locations. This prevents directory and claims routing errors caused by incomplete locations. If validation fails, the system should either require completion of the location or clear the partial entry.
11
Physical accessibility selection is mutually exclusive per office
Ensures exactly one accessibility option (Basic, Limited, None) is selected for each office location that is being submitted (primary and any completed secondary/tertiary). This is important for regulatory and directory accessibility reporting. If multiple or none are selected, the data becomes ambiguous and may violate directory requirements. If validation fails, the system should require the user to select one option only.
12
Mailing address selection and conditional mailing address requirement
Validates that exactly one option is selected for “Which practice is your primary mailing address?” (Primary/Secondary/Tertiary/Other). If “Other” is selected or if the applicant indicates the mailing address differs from practice, the separate mailing address fields must be completed with valid city/state/ZIP. This ensures correspondence and credentialing notices are sent to the correct address. If validation fails, the system should block submission until a single selection and any required address details are provided.
13
Billing responsibility selection and conditional billing company completeness
Ensures exactly one billing handler is selected (Primary/Secondary/Tertiary/None). If “None” is selected, then Billing Company Name, full billing address, contact person, phone, Federal Tax ID, and Name Associated with Tax ID must all be present and properly formatted. This is critical for claims payment setup and tax reporting. If validation fails, the system should prevent submission because incomplete billing data will cause payment and enrollment delays.
14
Federal Tax ID (EIN/TIN) format and name association validation
Validates that each Federal Tax ID Number provided (practice and billing) is 9 digits (allow hyphen) and that “Name Associated with Tax ID” is not blank when a TIN is present. It should also flag if the same TIN is used with conflicting associated names across sections, which may indicate data entry errors. Correct TIN/name pairing is essential for IRS reporting and payer contracting. If validation fails, the system should require correction or route to manual review for potential entity mismatch.
15
Licensure and identifier format validation (CA license, NPI, DEA, PTAN, Medi-Cal)
Checks that the California medical license number is present and matches expected state license patterns, and that issue/expiration dates are provided and valid. Validates NPI is exactly 10 digits and passes the NPI Luhn check, and that DEA number matches the standard format (2 letters + 7 digits) with a valid check digit; PTAN/Medi-Cal fields should meet length/character constraints if provided. These identifiers are core to credentialing, enrollment, and claims. If validation fails, the system should block submission for required identifiers (CA license, NPI if required by workflow) and warn for optional identifiers.
16
Expiration date logical checks (license/DEA/CDS/board cert/CLIA/insurance)
Ensures that expiration dates occur after their corresponding issue/effective dates and are not already expired as of the submission date (unless the workflow explicitly allows expired items with explanation). It also checks that professional liability policy expiration is after original effective date and that board certification expiration (if provided) is not earlier than certification date. This prevents credentialing with invalid or lapsed credentials and reduces rework. If validation fails, the system should block submission or require an explanation/updated document depending on policy.
17
Attestation questionnaire completeness and conditional addendum requirement
Validates that every attestation question (1–15, including 8a/8b and the Q13 follow-up when Q13 is Yes) has exactly one Yes/No selected. If any question is answered “Yes,” the system must require an attached/entered explanation and, for professional liability questions 9 or 10, require Addendum B completion (or an equivalent structured claim record) for each case. This is essential for compliance and risk assessment and prevents incomplete disclosures. If validation fails, the system should block submission until all attestations are answered and required explanations/addenda are provided.