NAIC Section 4 Mandate
Section 4 of the NAIC AI Model Bulletin mandates that insurers establish a rigorous third-party vendor risk management program. Carriers must verify vendor data lineage, test for algorithmic bias, obtain explicit audit rights, and verify that human adjusters retain independent review authority over all software findings.
Category 1: Statutory Adjuster Licensing & Human Authority
State insurance laws require discretionary adjusting to be performed by licensed natural persons. Ask every vendor:
- Does the software generate automated settlement offers, valuation targets, or denial recommendations without prior human review?
Compliant Answer: No. The software provides clerical document indexing, chronology structuring, and evidence reconciliation. All valuation, coverage, and settlement decisions are reserved exclusively for licensed examiners. - Does the platform allow adjusters to easily reject, edit, or override any suggested finding, code, or timeline entry?
Compliant Answer: Yes. Adjusters retain complete supervisory control, and all edits are recorded in an audit log. - Does the software enforce human attribution for every action taken on the claim file?
Compliant Answer: Yes. The system records the licensed adjuster ID associated with every validated record or escalated deadline. - Does your marketing or technical documentation claim “autonomous claims settlement”?
Compliant Answer: No. The software is strictly marketed and configured as decision-support technology.
Category 2: Evidentiary Provenance & UCSPA Compliance
Under Unfair Claims Settlement Practices Acts (NAIC Model #900), insurers must provide factual, case-specific explanations for any claim compromise:
- Is every extracted medical charge, date, and diagnostic code linked directly to the underlying source document page?
Compliant Answer: Yes. Clicking any extracted data point immediately opens the exact Bates-numbered PDF page with visual bounding-box verification. - Does the system apply synthetic “regional customary haircuts” or ungrounded benchmark discounts?
Compliant Answer: No. The system reconciles verified itemized charges from the actual medical bills submitted in the claim. - Can the system automatically detect and flag duplicate provider bills across multiple submissions?
Compliant Answer: Yes. The system identifies cross-provider billing duplicates, collection notices, and unbundled codes with visual source links. - Can an adjuster produce an evidence-backed audit report suitable for exhibit submission in a bad-faith deposition?
Compliant Answer: Yes. The software exports clean, court-ready exhibits citing exact document pages.
Category 3: Data Custody, Privacy & Model Training Boundaries
Claim files contain highly sensitive Protected Health Information (PHI) subject to HIPAA, GLBA, and NAIC Model #668:
- Are claimant medical records transmitted to multi-tenant public AI APIs (e.g., commercial LLM endpoints)?
Compliant Answer: No. Processing is conducted within private, isolated single-tenant VPCs or on-premise infrastructure. - Does the vendor retain customer claim documents or extracted data to train, fine-tune, or benchmark external models?
Compliant Answer: No. The vendor contractually commits to a strict Zero-Retention Guarantee. - Is data encrypted in transit, in memory, and at rest with tenant-isolated cryptographic keys?
Compliant Answer: Yes. Single-tenant cryptographic separation is enforced across all storage and vector databases. - Does the vendor sign a formal HIPAA Business Associate Agreement (BAA) and provide an audited SOC 2 Type II report?
Compliant Answer: Yes. Comprehensive compliance documentation is provided prior to contract execution.
Category 4: Algorithmic Fairness & Model Governance
State laws such as Colorado SB 21-169 forbid unfair discrimination in predictive models and claims algorithms:
- Has the vendor conducted quantitative empirical testing to demonstrate the model does not disproportionately bias valuations based on protected classes?
Compliant Answer: Yes. Documented algorithmic fairness testing reports are available for carrier inspection. - Can the vendor explain the exact computational method used to extract and classify documents?
Compliant Answer: Yes. The architecture is transparent and auditable, avoiding unexplainable neural black boxes. - Does the vendor maintain a continuous monitoring program for model drift and extraction error rates?
Compliant Answer: Yes. Automated monitoring logs track accuracy metrics across document categories. - Does the vendor contractually grant the carrier and state insurance commissioners full audit rights?
Compliant Answer: Yes. Section 4 audit rights are explicitly incorporated into the master service agreement.
Category 5: Legal Defensibility & Operational Resilience
- Does the vendor provide contractual indemnification for regulatory fines arising from systemic software calculation errors?
Compliant Answer: Yes. Clear liability boundaries and indemnification protections are provided. - Can the software handle complex supplemental demand submissions without overwriting the original intake record?
Compliant Answer: Yes. Immutable version control preserves the original submission and highlights newly submitted records. - Are operational deadlines (e.g., time-limited demands under Cal. CCP § 999 or Georgia § 9-11-67.1) flagged with exact source text?
Compliant Answer: Yes. Deadlines are captured alongside quoted conditions and routed for immediate human confirmation. - Has the software been reviewed and approved by insurance defense counsel for litigation defensibility?
Compliant Answer: Yes. The platform is designed from inception to meet the evidentiary standards of state and federal courts.