The Five-Layer Claims Editing Framework: How Intelligent Adjudication Eliminates the Denial-and-Resubmit Cycle

By Mishe · Clinical Operations

The Five-Layer Claims Editing Framework: How Intelligent Adjudication Eliminates the Denial-and-Resubmit Cycle

Every claim that moves through a health plan passes through a series of editing layers before it pays, pends, or denies. Most members never see these layers. Most providers encounter them only when something goes wrong — a denial lands in the queue, a remark code requires interpretation, a corrected claim has to be submitted weeks after the original. The administrative cost of that cycle, multiplied across millions of claims, is one of the most significant and least visible sources of waste in U.S. healthcare.

At Mishe, we've built our adjudication engine around a five-layer framework that applies each editing rule in sequence — and, critically, resolves many issues automatically rather than generating a denial and waiting for a resubmission. This post explains each layer, why it exists, and how Mishe's approach differs from the traditional payer model.

Five Layer Stack

Layer 1: Eligibility and Enrollment

The threshold question for every claim is simple: does a valid coverage relationship exist at the date of service? No clinical editing logic runs until this layer is satisfied. This is not a medical question — it is a data integrity question.

Key checks at this layer include confirming the member ID is active, the employer group is enrolled, the plan effective date precedes the date of service, and no termination record exists prior to the DOS. Dependent age-outs and COBRA status changes are caught here as well.

The most common failure mode at this layer is the gap between when a termination event occurs and when it is reflected in the eligibility system. A claim submits on day 45, but the member termed on day 10. Without a clean real-time eligibility feed, the adjudication engine pays a claim that should have rejected — creating recovery liability and disrupting employer funding.

The Mishe difference: Mishe's first-party enrollment data eliminates the latency inherent in third-party eligibility feeds. Real-time group and member status is held natively in our platform — no 270/271 HIPAA transaction required to resolve basic coverage questions.

Layer 2: Benefits Categories and Prior Authorization

Once a member is confirmed eligible, the adjudication engine evaluates whether the service category is a covered benefit under the plan design, and whether any pre-service authorization requirements were satisfied. This is where plan document language and employer-specific benefit carve-outs live.

Plan documents define which service categories are in scope: professional services, facility, DME, behavioral health, pharmacy, vision, and dental. Exclusions — cosmetic surgery, weight loss programs, experimental treatments — are configured at this layer and evaluated before any clinical editing begins.

Prior authorization requirements are a contractual obligation between the plan and the member — not a clinical determination. A claim for an MRI may be clinically appropriate and still deny at this layer if no authorization was obtained. It's important to understand that the PA requirement is a cost management tool; clinical appropriateness is evaluated separately at Layers 3 and 4.

One important constraint at this layer is parity compliance. The Mental Health Parity and Addiction Equity Act (MHPAEA) prohibits applying more restrictive PA requirements to behavioral health services than to comparable medical and surgical services. Mishe enforces parity compliance as a hard constraint — PA rules that violate parity are flagged before a claim ever adjudicates.

The Mishe difference: Rather than surface an after-the-fact denial for missing PA, Mishe's care navigation layer alerts a member before scheduling that a specific service requires authorization. The goal is to eliminate the scenario where a member receives care in good faith and then learns their claim is denied.

Layer 3: Clinical Appropriateness Guidelines

This is the layer where the historical tension between cost containment and clinical standards has been most weaponized. Milliman Care Guidelines (MCG) and InterQual represent two of the most widely-used evidence-based frameworks for determining whether a service is clinically indicated for a given patient presentation. When applied correctly, they are a codification of best practice — not a rationing mechanism.

Milliman Care Guidelines (MCG)

MCG criteria define the clinical thresholds that support inpatient admission, continued stay, and level-of-care decisions. They are built from peer-reviewed literature and designed to align care with the lowest clinically appropriate setting. The problem historically has not been the guidelines themselves, but payers applying them selectively to generate denials rather than to genuinely guide care.

InterQual Criteria

InterQual covers both acute episode criteria and procedure-specific criteria — including imaging, surgical procedures, and DME. Criteria are organized by clinical condition and updated annually. Where MCG focuses primarily on inpatient utilization, InterQual has broader applicability across the outpatient procedure landscape.

Medical Necessity as Quality, Not Gatekeeping

Managed care was introduced precisely to eliminate unnecessary care — not to delay or deny necessary care. The Brent James and IHC Quality Science framework identifies three distinct classes of healthcare waste: efficiency waste (doing things wrong), within-case waste (doing unnecessary things in an otherwise appropriate case), and case-rate waste (treating a patient in the wrong care setting). These are quality failures. They are not insurance policy decisions — and treating them as such is one of the original sins of how managed care has been practiced.

The Mishe difference: Mishe applies MCG and InterQual criteria at the point of care navigation — surfacing them to members and providers as clinical guidance, not as denial criteria waiting to be triggered post-service. A provider who understands that a 23-hour observation admission doesn't meet inpatient criteria can make a better care decision in real time rather than fight a retroactive denial 60 days later.

The Brent James and IHC Quality Science framework identifies three distinct classes of healthcare waste: efficiency waste (doing things wrong), within-case waste (doing unnecessary things in an otherwise appropriate case), and case-rate waste (treating a patient in the wrong care setting).

Layer 4: Payable Diagnoses and Local Coverage Determinations

Even if a service is clinically appropriate in the abstract, Medicare and commercial payers maintain procedure-level coverage policies that tie payment to specific diagnosis code combinations. Local Coverage Determinations (LCDs) and National Coverage Determinations (NCDs) define which ICD-10 diagnosis codes unlock payment for a given CPT code. This layer is where coding accuracy directly affects payment — and where most providers are most undertrained.

An LCD for a specific CPT code will enumerate the ICD-10 codes that support medical necessity for that procedure. A claim that lists a CPT code covered under an LCD but includes a diagnosis that is not on the covered list will deny — even if the procedure was clinically appropriate for the patient's actual condition. In most cases, the problem is documentation and coding accuracy, not the care itself.

Many self-funded employers configure their adjudication rules to mirror Medicare LCDs — both because they represent defensible, evidence-based coverage standards and because they reduce the administrative overhead of maintaining custom coverage policies. Mishe's adjudication engine incorporates LCD logic as a configurable layer, with the ability to map employer-specific overrides.

The Mishe difference: Rather than denying a claim for a payable-diagnosis mismatch and waiting for a corrected claim, Mishe's engine surfaces the covered diagnosis list at adjudication time and, where clinical documentation supports it, applies the appropriate covered diagnosis automatically — with a full audit trail and explanation to the provider.

Layer 5: CPT and Diagnosis Code Editing

The innermost and most technically complex layer. CPT code edits enforce billing accuracy through three distinct mechanisms: NCCI bundling rules, multiple procedure reduction, and code fusion (resequencing). These rules exist because CPT codes are not independent atomic units — they have defined relationships that reflect how medical procedures actually occur. Billing them as independent units misrepresents the work performed.

NCCI: National Correct Coding Initiative Bundling

CMS's NCCI edits define pairs of CPT codes where one code is considered a component of the other. Billing both separately is considered unbundling — a misrepresentation of the services rendered. NCCI tables exist for physician services and outpatient hospital services and are updated quarterly. When a claim is received with a component code that is bundled into an already-billed comprehensive code, the component should be automatically removed with a line-level edit explanation provided to the provider.

Multiple Procedure Reduction

When a provider performs multiple procedures in the same session, payment rules typically reimburse the primary procedure at 100% and apply a reduction — commonly 50% — to secondary procedures. This reflects the shared overhead of prep, anesthesia, and positioning that does not simply double when a second procedure is performed in the same session. The same logic applies to bilateral procedures.

Code Fusion: The 20610 + 76942 → 20611 Example

Code fusion — sometimes called resequencing — occurs when a provider submits two CPT codes that together represent a single, more accurate combination code. The most illustrative example involves a common outpatient procedure: a major joint injection performed under ultrasound guidance.

A provider submits CPT 20610 (arthrocentesis, major joint, without ultrasound guidance) and CPT 76942 (ultrasonic guidance for needle placement) as two separate line items. The correct code for this procedure is CPT 20611 — arthrocentesis with ultrasound guidance — which was created precisely to capture this combination. Billing 20610 and 76942 separately overstates the work and creates a payment differential.

The traditional approach: deny both codes with remark code CO-97 (payment included in the allowance for another service), send an explanation of benefits, and wait for the provider to submit a corrected claim with 20611. This introduces a 30-to-60 day delay, generates administrative cost on both sides of the transaction, and disrupts cash flow to the provider — with no change to the ultimate clinical or financial outcome.

The Mishe approach: the adjudication engine detects the 20610 + 76942 pair, fuses them to 20611 automatically, pays the correct fee schedule amount for 20611, and sends the provider a line-level edit explanation: CPT codes 20610 and 76942 have been combined to 20611 per NCCI code fusion rules. No resubmission required. Zero rework. Zero delay.

"CPT codes 20610 and 76942 have been combined to 20611 per NCCI code fusion rules. No resubmission required."

The Framework at a Glance

From Adjudication Logic to Member Care Navigation

The most important long-run application of this framework is not adjudication — it's pre-service transparency. The same code-relationship logic that powers Mishe's adjudication engine can be surfaced to members before they receive care.

If a member is being scheduled for a knee injection with ultrasound guidance, they can be shown: this procedure is typically billed as CPT 20611, your plan covers it at a specific cost share, no prior authorization is required for this diagnosis, and your in-network provider on the Weave network will charge a known rate. The member arrives informed. The provider bills correctly the first time. The claim adjudicates clean. No denial. No rework. No surprise bill.

This is what managed care was supposed to be: information asymmetry eliminated, care aligned with evidence, cost predictable. The traditional insurance model made that impossible because opacity was profitable. Mishe's direct contracting model makes transparency structurally possible for the first time.

Weave™ is Mishe's network architecture — the infrastructure layer where any contract, any fee schedule, and any network arrangement can be administered through a single adjudication engine — and where every claim makes the pricing intelligence underneath it smarter.

The Original Purpose of Managed Care — and What Went Wrong

Managed care was not invented as a profit mechanism. It emerged in the 1970s and 1980s as a response to a documented crisis in healthcare quality and cost: unnecessary procedures, inappropriate utilization, and wide geographic variation in care that had nothing to do with clinical need. The goal was quality, not rationing. Paul Ellwood, who coined the term in 1970, envisioned a system that aligned financial incentives with patient outcomes.

The mechanisms that followed — prior authorization, concurrent review, NCCI bundling, clinical necessity criteria — were designed to align care with evidence. NCCI edits exist because unbundling codes misrepresents the work performed. MCG and InterQual exist because a patient admitted to an inpatient bed who meets criteria for home health is in the wrong setting. That's a quality failure. It costs money precisely because it is poor care.

What perverted managed care into a profit center was a fundamental misalignment of incentives: payers who bore the financial risk of unnecessary care also controlled the authorization process, the denial process, and the appeals process. With no external accountability — and with ERISA preemption limiting state-level remedies for self-funded plans — managed care organizations discovered that denial rates directly improved margins. Clinical criteria became denial pretexts. PA requirements became administrative friction designed to reduce utilization through exhaustion rather than appropriateness.

Mishe's position is that managed care and clinical appropriateness are the same thing. A claim that pays correctly the first time because the code was fused properly is not a win for the payer over the provider — it is an accurate representation of the service performed. A member who knows upfront what is and is not covered, and why, based on evidence rather than insurance policy language, is receiving better care. The line between cost containment and clinical quality should not exist. It only exists because the parties who drew it had something to gain from the confusion.

Have questions about how Mishe's adjudication engine handles a specific claim type, or want to understand how your plan's benefit structure maps to these layers? Reach out to your Mishe care coordinator — we're here to help.