Operational Integrity Is the New Payment Integrity

For years, “payment integrity” has been framed too narrowly. Most people hear the term and think fraud, waste, abuse, coding edits, or post-pay recovery.

But the signal coming from regulators right now is much broader: they are increasingly treating payer operations themselves as a payment-integrity issue.

Slow reimbursements, weak denial controls, poor complaint handling, noncompliant downcoding, and flawed mental health parity processes are no longer operational footnotes. They are becoming enforcement matters.

That is why one of the more important payer stories from last week was not a splashy M&A headline or another AI announcement. It was a state-regulatory pattern. A recent roundup of 2026 state actions showed penalties tied not only to parity violations, but also to slow reimbursements, provider payment disputes, complaint handling, prior authorization and claims-processing failures, and provider-directory accuracy.

In other words, the market is widening the definition of integrity from “Was the claim expensive?” to “Was the decision process lawful, timely, explainable, and operationally sound?”

Two examples make the point clearly.

In Maryland, regulators fined Cigna $80,000 and ordered it to stop automatically reducing billed evaluation and management code levels. https://insurance.maryland.gov/Pages/Bulletins/Bulletin-26-9.aspx

The Maryland Insurance Administration’s consent order states that the insurer had been adjusting claims to lower-paid code levels based on its own internal assessment, then forcing the provider to appeal if they disagreed. Maryland also said that the practice caused delays in the amounts properly owed and required Cigna to cease the automatic reduction of billed code levels and to align its reimbursement policy with Maryland law. The state then followed with a bulletin reminding payers that they may not unilaterally modify a service code on their own assessment and push the burden back to the provider; they must either pay or formally dispute and request the information needed to determine reimbursement.

In Pennsylvania, the Insurance Department fined Aetna $550,000 after a market conduct exam found several problems that went well beyond a simple pricing dispute. https://www.pa.gov/agencies/insurance/newsroom/shapiro-admin-protects-consumers-fines-aetna-violation-mental-health-parity-laws

The state cited incomplete claims files, delays in approving or denying claims, improper denials due to poor internal communication, failure to clearly explain members’ cost-sharing for autism services, and mental health parity violations involving incorrect or incomplete analysis and application of benefit limits.

Pennsylvania’s remedy was also telling: reprocess affected claims, pay members what they are owed with interest, fix internal systems, improve denial letters, and provide proof of repayment. That is not just a fine.

That is a regulatory statement that process quality is part of payment integrity.

This is the part that many in the industry still miss.

The real issue is not only whether a payer gets to the “right” answer often enough. The issue is whether the payer can show its work. Can it prove why a code was changed? Can it demonstrate that parity analysis was complete? Can it explain why a service was denied, what rule was applied, what information was missing, who made the change, and whether the workflow complied with state and federal requirements? Increasingly, regulators are saying that if you cannot answer those questions, you do not have a payment-integrity program. You have an audit exposure.

That is also why the discussion around AI in payer operations is about to get much more serious.

The American Medical Association recently highlighted new Indiana legislation that requires health plans to notify physicians when claims are downcoded, establish a clear appeals process, and prohibits a plan from using an automated process, program, or tool, including AI, as the sole basis for downcoding a claim. That is an important signal.

The industry is moving toward a standard that allows automation but not opaque automation.

This is exactly where Nēdl Labs fits.

At Nēdl, we believe payment integrity should not be built on black-box outputs, manual guesswork, or “trust us” edits. It should be built on computable policy, deterministic execution, and evidence-backed decisions.

That means turning policy, contract, coding, and clinical logic into executable rules. It means producing an evidence pack that shows the clause, the fact pattern, the applied logic, and the line-by-line rationale behind the result. It means a payer should be able to answer, with precision, “What rule fired?” Which facts mattered? What was adjusted, denied, or approved? Why? Under which version of the policy?

That is how you make decisions that can withstand provider abrasion, appeals, audits, and regulatory review.

In a world shaped by the actions of Maryland and Pennsylvania, payers need more than analytics.

They need infrastructure for operational integrity.

They need systems that can:

• distinguish between a legitimate partial denial and an impermissible unilateral code downgrade;
• preserve traceability across claim intake, policy interpretation, adjudication, and communication;
• generate denial rationales that are specific enough to be defensible;
• enforce parity and utilization rules consistently, not selectively; and
• prove that automation is supporting compliant decision-making rather than hiding noncompliant behavior.

That is the opportunity. And it is a big one.

The next era of payment integrity will not be won by whoever finds the most anomalies. It will be won by whoever can make reimbursement decisions quickly, correctly, explainably, and governable.

Savings still matter. But proof is becoming the product.

My view is simple: payment integrity is no longer just about dollars saved. It is about whether the decision engine itself is trustworthy.

Regulators are expanding the aperture from pricing outcomes to adjudication controls, process compliance, and communication quality. Payers that continue to treat this as a narrow FWA or coding problem will fall behind.

Payers that build for deterministic reasoning, operational transparency, and evidence-backed decisions will be far better positioned for the world that is clearly arriving now.