CAPE resolves a healthcare claim into a final remittance through a deterministic pipeline. This page describes the architecture, the outputs, and the variance work that runs on top.
the equation
A claim is a state vector.
CAPE models a healthcare claim as an immutable state vector that accumulates structure as it passes through four operators. Each operator is a deterministic function over the controlling rule corpus. The composition is referentially transparent: the same claim, against the same corpus version, always produces the same final remittance.
The state vector is the tuple:
S=⟨C,P,E,F,R⟩
Component
Definition
C
Clinical data vector. CPT/HCPCS codes, modifiers, units, provider NPI, place of service, diagnosis pointers, line ordering.
P
Base price vector. Per-line reference price from the governing fee schedule. RVU-derived for procedural codes, ASP for drugs, ASC payment indicators for facility, contract tier for commercial payers.
Financial waterfall ledger. Per-line consumption of deductible, coinsurance, sequestration, and payer remittance.
R
Regulatory citation chain. Per-decision authority trace. Every adjustment populates this vector with the controlling CFR section, MPFS rule, NCCI policy, or contract clause.
The final state Sfinal contains the per-line payer remittance, the per-line patient responsibility, and the citation chain back to the controlling authority for every adjustment applied. No decision in the engine is unattributed.
the pipeline
Operators map to phases.
The four operators are implemented as an eight-phase pipeline. Phases 0–4 resolve the claim state Svalid. Phase 5 produces the base price vector P. Phase 6 applies interaction adjustments to produce E. Phase 7 runs the financial waterfall to produce F and the final remittance Rc.
engine outputs
A claim is not a number. It is a decision surface.
Every adjudicated claim emits a structured output object — a replayable decision surface with full citation provenance back to the controlling authority for every adjustment.
Field
Content
final remittance
Per-line and claim-level totals across the waterfall. Payer payment, patient responsibility, deductible consumption, sequestration, coinsurance.
line decision surface
Per-line payable-or-denied determination with mechanism attribution. Each denial carries the rule that produced it.
rule-hit trace
Every rule consulted in the adjudication. Includes rules that were evaluated and did not fire, marked accordingly.
citation chain
Per-decision authority trace. Each adjustment maps to its controlling CFR section, MPFS rule, NCCI policy entry, MUE table entry, LCD article, or contract clause.
source release lineage
Which version of which authority resolved each decision. Quarterly rule updates produce versioned source releases; the lineage records which release was active at adjudication time.
replay key
Persisted identifier permitting full trace retrieval and re-execution against any subsequent corpus version.
Every adjustment is reproducible from the trace. Traces persist across rule updates. Outputs are auditable by any third party with access to the same authoritative sources.
execution trace
One line, end to end.
The following trace shows the four operator transitions applied to a single line of a real claim: line 04 of a Connecticut orthopedic outpatient claim, 20610-RT-XS, joint injection with explicit-separate-structure modifier. Each transition shows the arithmetic, the controlling authority, and the resulting state change.
claim parameters
payerMedicare Part B
provider postureNON-PAR · assignment accepted
deductible$257.00 remaining (consumed earlier in claim)
line under trace04 · 20610-RT-XS · joint injection
A single trace is defensible. What makes the engine commercially useful is what happens when the trace runs across the entire claims file. Variance is the structured difference between what CAPE computed as correct and what the payer actually paid — surfaced not as scattered per-claim deltas, but as named patterns with attributed mechanism, controlling authority, and recovery posture.
Every variance finding answers four questions: what is happening, how much it costs, why it is happening, and what to do about it.
Five categories of variance.
01
underpayment patterns.
Payer remittance below CAPE-computed allowed across a stable cluster of claim characteristics — CPT family, modifier combination, provider, date range. Diagnostic of fee schedule version mismatch, locality misapplication, contract terms not propagated to the payer's claim system, or systematic application of the wrong reduction factor.
02
contract compliance failures.
Systematic divergence between the payer's behavior and the contract terms across an entire procedure family or relationship period. Diagnostic of unilateral payer policy changes, contract addendum not implemented in the payer's claim system, or stale fee schedule attached to the payer-product mapping.
03
denial patterns.
Claims denied that should pay. Diagnostic of bundling logic ignoring modifier bypass, medical-necessity denials against LCD coverage, prior-authorization denials on services that do not require prior authorization, timely-filing denials that miscalculate the window.
04
coding leakage.
Provider undercoding relative to documented work. Diagnostic of E/M codes systematically below documentation support, missed add-on codes for services routinely provided, modifiers not appended that would unlock separate payment.
05
overpayment exposure.
Payer paid more than contract or statute requires, or documentation does not support billing. Diagnostic of modifier overuse, medical-necessity gaps, duplicate billing patterns, services billed at higher levels than supported. Generates clawback liability bounded by the statutory recoupment window.
Representative findings — ortho/spine engagement.
finding 01 · underpayment pattern
MPPR factor misapplied to indicator-1 codes.
Payer's claim system applies the 50% MPPR reduction to all multi-procedure scenarios. The MPFS multi-procedure payment indicator schedule restricts the 50% factor to indicator-2 and indicator-3 codes; indicator-1 codes receive no reduction. The payer is reducing payment on indicator-1 codes that should pay at full allowed amount.
Payer bundling 29881 with 20610-XS regardless of modifier.
Payer's automated bundling logic denies the column-2 line on the 29881 → 20610 NCCI conflict even when modifier XS is present on the column-2 line. The XS modifier is the explicit-separate-structure bypass; the conflict should resolve to the bypass path, not denial. The payer's edit engine is not recognizing XS as a valid bypass for this CCMI=1 pair.
Modifier 25 overuse on E/M services with minor procedures.
Practice is appending modifier 25 to office-visit codes on the same day as minor procedures at a rate substantially above the specialty-regional benchmark. A documentation sample of these claims shows E/M documentation that does not support the separate-and-significant standard required by modifier 25. The pattern is an active OIG audit target as of the 2024 Work Plan.
Authority: CMS Pub. 100-04, Ch. 12, §30.6.6. NCCI modifier guidance. OIG Work Plan 2024 — modifier 25 audit target.
magnitude−$340,000
claims affected892
windowRAC 36 months
recovery postureEscrow / holdback
confidenceClawback risk
Three findings shown. A representative ortho/spine engagement surfaces 40 to 80 distinct named patterns across the five categories, each individually traced and cited. The diligence report consolidates these into the headline variance number.
representative aggregate
$4.21M
net recoverable
n = 219,847 claims·ortho/spine platform·24-month window
rule corpus
The unified source registry.
CAPE resolves claims against the unified rule corpus assembled from federal, regional, commercial, and engagement-specific sources. Each source is versioned and maintained against its authoritative publication. The corpus is the engine’s substrate; the engine is the computation over the corpus.
RAC statutory recoupment windows by claim type (3 or 5 years), MAC retro-review windows, commercial payer audit clauses extracted from practice contracts.
Sources are loaded, normalized, and versioned. The engine consults the source registry at adjudication time and persists the source release lineage in the citation chain. A claim adjudicated against the Q2 2026 corpus carries the Q2 2026 release lineage; the same claim adjudicated against a later corpus would produce a different result and a different lineage.