Payment integrity SOP reasoner
Centene · payment integrity
Reasoning

SOP reasoner

Every claim is walked node by node through the procedure that governs its type. Deterministic checks resolve first; a node only needs a scoped model call where the rules cannot answer on the data available. Every terminal decision traces to the node that produced it, and every node carries what it cited.

Knowledge Center Open the queue
Claims walked
25
16 approved · 9 routed to a human
Resolved deterministically
97%
292 of 302 nodes · 0 model calls here. On the platform 80% of these nodes are deterministic — the gap is retrieval and drafting, which are scoped calls there and local code here.
Nodes that cite a source
79%
336 citations across the batch
Payload coverage
99%
435 of 438 claim paths resolved · 3 nodes took on_field_missing

How the batch terminated

25 claims

The agent never denies and never pends. APPROVE is the only disposition it reaches on its own; every negative outcome is a hand-off that carries what the agent recommends the human do. A single “route to a reviewer” would lose exactly that.

Approve APPROVE 16
Every check resolved and none found a variance. This is the only disposition the agent decides on its own.
Route to a human ROUTE_TO_HUMAN 2
The agent has no recommendation. Something on the claim needs a person's judgement and the rules do not reach it.
Route to a human — criteria not met ROUTE_TO_HUMAN_CRITERIA_NOT_MET 4
The agent recommends the claim does not meet the criteria. It does not deny — a person confirms.
Route to a human — pend ROUTE_TO_HUMAN_PEND 3
The agent recommends holding for missing information. A check could not be evaluated, so no recommendation on the merits is offered.

Missing information outranks a recommendation to deny: a walk that could not evaluate a material check does not recommend on the merits. The engine resolves that structurally, by whichever terminal the graph reaches first; a linear procedure has to choose, and this is the choice.

Traversal trace

CLM-0000018 · Inpatient DRG validation · v2.7
Open the claim
DRG-1 Rule on match
Active on the date of service
Coverage ran 2026-01-01 to 2026-12-31; the service on 07 Mar 2026 falls inside it. Re-verified at audit with no retroactive change.
Read $.eligibility.coverage_from$.eligibility.coverage_to$.service_date
pass [1] Enrolment system · 834 roster · 07 Mar 2026 06:00 [2] Re-verified for this audit · 02 Apr 2026 18:01
DRG-2 Rule on match
Covered under the plan
Inpatient admission — covered under Part A equivalent benefit. Wellcare Medicare Advantage HMO · Texas.
Read $.eligibility.benefit$.eligibility.plan
pass [3] Benefit configuration · plan build
DRG-3 Rule on match
Primacy confirmed
This plan is primary. Other coverage: None on file.
Read $.eligibility.primacy$.eligibility.other_coverage
pass [4] CPP-092 · coordination of benefits
DRG-4 Rule on match
Approved and matched
PA-2026-201800 valid 2026-03-01 to 2026-03-31. Inpatient admission, authorised length of stay — billed as authorised.
Read $.prior_auth.status$.prior_auth.required
pass [5] Authorization PA-2026-201800 [6] CPP-085 · prior authorization
DRG-5 Rule on match
No decisive policy
This claim is tested against supporting policies only.
Read $.policy_refs$.service_date
info
DRG-6 Lookup on match
DRG 378 priced from the grouper
378 — Gastrointestinal haemorrhage with CC. Relative weight 0.9807 at a base rate of $7,150.00.
Read $.lines
pass [7] CMS MS-DRG Definitions Manual v43
DRG-7 Rule on match
Present-on-admission indicators consistent
No secondary diagnosis driving the severity tier is reported POA = N or POA = U.
Read $.findings
pass [8] CPP-052 · present on admission
DRG-8 Needs a scoped call on match
Severity tier rests on more than one condition
No single complication carries this admission's tier, so removing any one of them does not reprice it.
On the platform this node is a scoped model call over the retrieved record.
Read $.drg
pass [9] CPP-047 · clinical validation of an MCC
DRG-9 Formula on match
No regroup
The billed DRG stands.
Read $.coding.supported
pass
DRG-10 Formula on match
No repricing
Paid $7,012.01 as grouped.
Read $.lines
pass
DRG-11 Retrieval on match
Nothing to retrieve against
This claim rests on no single decisive policy, so there is no version to scope a retrieval to. The supporting policies are cited on the claim without being quoted.
On the platform this node is a scoped model call against the indexed policy.
Read $.lines$.findings
info [10] Policies applied
DRG-12 Drafted on match
Closing letter drafted
No variance to report. The letter states the claim was reviewed and closed with no finding.
On the platform this node is a scoped model call that writes the finding and the letter.
pass
Terminal disposition
Approve APPROVE

Every node resolved and none found a variance. The claim was paid as the record and the fee schedule support. This is the only disposition the agent reaches on its own.

Every check resolved and none found a variance. This is the only disposition the agent decides on its own.

12 nodes
11 deterministic
0 model calls
10 citations
100% of paths resolved

Compiled procedures

Each declares its nodes and their order in the audit book; the evaluators live in services/sop.py. A key with no evaluator, or an evaluator with no key, fails a test.

Professional claims post-pay review v1.9 · 12 nodes · 15 claims in this batch Professional claims — office visits, procedures, laboratory, imaging Live signed off 2026-01-14
Inpatient DRG validation v2.7 · 12 nodes · 8 claims in this batch Institutional inpatient admissions priced by MS-DRG Live signed off 2025-12-04
Drug and biologic unit review v1.2 · 13 nodes · 2 claims in this batch Physician-administered drugs billed on the medical benefit Live signed off 2026-02-20

How nodes resolve

Across all 302 nodes walked in this batch. The engine's own taxonomy has two values, not six — deterministic (242) and llm_reasoning (60). The six below are this demo's sub-classification of them, which is why a node can be llm_reasoning on the platform and still resolve without a model here.

Rule 167
Lookup 42
Formula 33
Retrieval 25
Drafted 25
Needs a scoped call 10

Where a scoped call is genuinely needed

These are the nodes that took the on_field_missing branch — not because a check evaluated to false, but because the path it reads is not in the claim at all. The field it needed is named, so this is a demonstrated dependency rather than an assertion. The other 292 nodes resolved on what the claim carries.

on field missing Requires the inpatient record
Not in the claim $.record.inpatient.clinical_indicators

mcc_substantiation · 2 claims: CLM-0000013, CLM-0000014

on field missing Requires the medication administration record
Not in the claim $.record.medication_administration.administered_dose

dose_reconciliation · 1 claim: CLM-0000021

The three-way branch — on_match, on_no_match, on_field_missing — the four terminal dispositions, the two approaches and the path statuses are cgn-sop-reasoner's vocabulary, taken from the engine itself. What differs is what they resolve against: a synthetic claim in this audit book, not a payload assembled from upstream systems. A missing path below is a fact about this book.