TwinEthos homeAPI access

Law

Texas SB 815 (Ins. Code 4201.156, automated decision systems in utilization review)

Texas Department of Insurance (Commissioner of Insurance) · Texas (US-TX) · 1 provision encoded · verified against the official source as of 2026-10-03.

Informational data, not legal advice. Summaries and rules have not been reviewed by a lawyer: always verify official law text for decisions. A suggested guard is intended to address each rule; adding it is not a statement of compliance to that law.

Official text: capitol.texas.gov, tcss.legis.texas.gov.

Trust and provenance 2 official sources · last verified 3 Oct 2026 · not reviewed by a lawyer · 1 of 1 provision audit-grade · release 2026.10.03.4

Where this instrument's data comes from, how current it is, and what has and has not been checked. Each provision below has its own panel.

Official sources
Lanes
Binding law — in force 1
Verification
Sources last verified 3 Oct 2026; each provision states how.
Data release
Data release 2026.10.03.4, data as of 3 Oct 2026, schema 0.3.9.
Legal review
None of the 1 provision has been reviewed by a lawyer; no TwinEthos rule has been legally reviewed yet. Treat each as research to check against the official text; it is not legal advice. Open questions for counsel on them: 1.
Audit standard
1 of 1 provision audit-grade. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors
2 detectors, all experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify. Each provision lists its detectors' known limits.
Changes
  • 2026.10.03.4 (3 Oct 2026): 1 provision added

Each data release records which provisions changed; the full list is on Changes.

Binding law — in force

A utilization review agent may not use an automated decision system to make an adverse determination, wholly or partly (Texas SB 815)

Tex. Ins. Code 4201.156(a) · official text · In force: applies since 1 Jan 2026 · Texas (US-TX)

Ins. Code 4201.156(a), added by SB 815 (effective 2025-09-01; applies to utilization review for health benefit plans delivered, issued or renewed on or after 2026-01-01, SB 815 sec. 4): a utilization review agent may not use an automated decision system (an algorithm, including one incorporating an artificial intelligence system, that uses data-based analytics to make, suggest or recommend determinations, 4201.002(1-c)) to make, wholly or partly, an adverse determination (a determination that services are not medically necessary or appropriate, or are experimental or investigational). The Commissioner may audit and inspect its use at any time (4201.156(b)); algorithms, AI and automated decision systems may still be used for administrative support or fraud detection (4201.156(c)). Detect automated output that sets an adverse status and prompts or schemas that ask a model to return a denial.

Trust and provenance not reviewed by a lawyer · audit-grade · source verified 3 Oct 2026 · release 2026.10.03.4
Lane
Binding law — in force In force: applies since 1 Jan 2026
Official source
Tex. Ins. Code 4201.156(a) · captured 3 Oct 2026 · anchor hash (SHA-256) 1e3f94e9989f… · 18 more anchors in the data release
Verification
Quoted text found word for word in the captured official document (3 Oct 2026). Source last verified 3 Oct 2026: checked against the captured official document.
Data release
Data release 2026.10.03.4, data as of 3 Oct 2026, schema 0.3.9.
Legal review
Not reviewed by a lawyer. TwinEthos derived this rule from the official text it cites: treat it as research to check against that text; it is not legal advice. No TwinEthos rule has been legally reviewed yet. Open questions for counsel on this rule: 1.
Audit standard
Audit-grade: meets all 10 checks of the TwinEthos audit standard that apply to it. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors

2 detectors (code pattern), experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify.

Known limits:

  • Review routing in a separate workflow service or BPM engine
  • Denials applied by a downstream claims system from an exported score
  • The clinical review may live in another module (a workflow engine or a separate review service); confirm the adverse status cannot be reached without it before reporting. Clinician tokens anywhere in the file suppress t…

2 more known limits in the data release.

Who it applies to

  • Duty falls on: insurer, organization
  • Sectors: insurance, healthcare
  • Utilization review agents (entities conducting utilization review for an employer with covered employees in Texas, a payor, or a certificated administrator), including HMOs and insurers that perform utilization review, and utilization review of workers' compensation medical benefits (4201.054(a)), for utilization review conducted for a health benefit plan delivered, issued for delivery or renewed on or after 2026-01-01 (SB 815 sec. 4). The Act took effect 2025-09-01.
  • Not covered:
    • Administrative support or fraud-detection functions (Ins. Code 4201.156(c))
    • Persons who only provide information about scope of coverage or benefits and do not determine medical necessity or experimental status (4201.051)
    • Contracts with the federal government for utilization review of Medicare or Medicaid (Title XVIII or XIX) patients (4201.052)
    • The state Medicaid program and the other state programs listed in 4201.053(a), except as 4201.057 provides for HMOs
    • The terms or benefits of ERISA employee welfare benefit plans (4201.056)
  • Whether it applies depends on facts outside the code; a person has to decide.

The guard to add

Route every adverse outcome an AI or algorithm proposes in utilization review to a qualified clinical reviewer, and issue a denial only from that reviewer's recorded decision.

At the point where a model, rules engine or scoring tool returns its result for a prior-authorization, concurrent or retrospective review, the code may auto-approve (where the law allows) or route the case, but any result that would deny, delay, modify or downgrade the request is written as a pending clinical review (status 'pending_clinical_review', a review_queue entry with the tool's output attached as a recommendation), never as the determination. Only a review action by an authenticated reviewer whose role is physician, clinical peer or qualified reviewer, in the same or a similar specialty where the law requires, can set an adverse status; that action records reviewer_id, licence and specialty, the clinical documents opened, the decision and its clinical rationale, and the timestamp, and the adverse-determination notice is generated from it (with the reviewer's signature or attestation where the law requires). Where a law forbids the automated system from making an adverse determination even in part (Texas), the tool's output may only approve, route or support administrative and fraud-detection work; it is not shown to the reviewer as a proposed denial.

Where it goes: 1 application source code, 2 data models, 9 AI output handling, 14 user-facing text.

What this provision adds:

  • Keep any algorithm, AI system or automated decision system out of making an adverse determination, even in part; it may approve, route, or serve administrative support and fraud detection.
  • Keep records that let the Commissioner audit and inspect the agent's use of automated decision systems in utilization review at any time.

Example (Python + OpenAI SDK (prior-authorization service)), before:

result = client.chat.completions.create(model=MODEL, messages=build_pa_prompt(request)).choices[0].message.content
if json.loads(result)['decision'] == 'deny':
    prior_auth.update(request.id, status='denied')
    send_denial_letter(request)

After:

result = json.loads(client.chat.completions.create(
    model=MODEL, messages=build_pa_prompt(request, record=member_clinical_record(request))).choices[0].message.content)
if result['decision'] == 'approve' and AUTO_APPROVE_ALLOWED:
    prior_auth.update(request.id, status='approved', ai_assisted=True)
else:                                   # any non-approval goes to a clinician
    review_queue.enqueue(request.id, queue='pending_clinical_review',
                         specialty=request.specialty, ai_recommendation=result)

@app.post('/reviews/{case_id}/decision')
def record_clinical_decision(case_id: str, body: Decision, reviewer=Depends(licensed_clinical_reviewer)):
    decision = clinical_decisions.create(case_id=case_id, reviewer_id=reviewer.id, licence=reviewer.licence,
                                         specialty=reviewer.specialty, documents_reviewed=body.documents,
                                         outcome=body.outcome, rationale=body.rationale)
    if body.outcome in ('denied', 'downgraded'):
        send_adverse_determination(case_id, decision=decision, signed_by=reviewer)

Control: AI or algorithm denies, delays or downgrades care in utilization review without a licensed clinical reviewer deciding. The same guard addresses 9 items with binding law in 8 jurisdictions. Engineering guidance, not legal advice.

Related incidents

No guardrail sits on this exact control; these incidents are cited by guardrails on related controls.

Rule id tx-sb815.no-automated-adverse-determination · review status: primary source derived

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.