# Beyond the Basics: The Modern Approach to Payment Integrity (Payment Accuracy Edge)
## Key Facts
- **12 April 2023:** Gartner notes that *prospective payment integrity* (PPI) can “significantly improv[e] the accuracy of the initial claims determination and payment,” but measuring only post-payment recoveries can create a KPI conflict because effective PPI may “negatively affect traditional retrospective KPIs” (Section: “How Did We Get Here?”, Gartner quote block).
- **58%:** Payment integrity leaders say their improvement initiatives are often at odds with other departments’ initiatives (Section: “Payment Integrity Trends”).
- **97% (and 30%):** **97%** of health plans use **2 or more editors** to manage payment integrity, with **30%** using **5 or more editors** (Section: “Payment Integrity Trends”).
- **59%:** Health plans cite “in-sourc[ing] more of our payment integrity functionality” as a top goal—even though their top two biggest challenges relate to limited internal staff and knowledge (Section: “Payment Integrity Trends”).
- **Two solution categories:** The paper contrasts (1) a **single vendor with multiple disparate claims payment applications** (typically **10–20 independent modules**) vs. (2) a **single payment integrity platform with multiple interoperable solutions** (Section: “Which Approach is Right for Your Organization?”, “01” and “02”).
- **Update cadence:** The single platform approach described is cloud-based and delivers infrastructure, maintenance, and updates **every two weeks** (Section: “Infrastructure and Updates,” “02 Hosted vs. Cloud-Based”).
## Summary
## Why prospective payment integrity (PPI) is gaining attention
Healthcare claims payment accuracy is getting harder as complexity, data volume, consumer expectations, market demands, and government regulations increase. Many health plans have responded by segmenting work across specialized teams—such as routing pricing to reimbursement or claims operations and contracting terms to provider network teams—sometimes adding specialized payment integrity units to address over- and under-payments after payment. Over time, this specialization can create intricate IT ecosystems with multiple workflows, technology stacks, and vendor solutions that are difficult to adapt (Section: “How Did We Get Here?”).
The paper defines **prospective payment integrity (PPI)** as shifting more information and processes upstream in the adjudication process to ensure more accurate payments. It also notes a measurement challenge: PPI’s value is framed as **cost avoidance** (rather than cost recovery), which can be harder to calculate, even though the paper states cost avoidance can provide a larger benefit opportunity than revenue recovery (Section: “How Did We Get Here?”).
## Two approaches to payment integrity solutions
The content groups payment integrity solution providers into **two categories** (Section: “Which Approach is Right for Your Organization?”):
1. **Single vendor with multiple disparate claims payment applications:** Traditional providers may offer **10–20 independent modules**. The paper cautions that this can perpetuate fragmented infrastructure with inconsistent processes and siloed datasets, and that some tools may be hosted in the cloud without being built for cloud delivery (Section: “Which Approach…”, “01 Single Vendor…”).
2. **Single payment integrity platform with multiple interoperable solutions:** This model aims to reduce IT burdens and enable a more comprehensive view of claims payments. **Payment Accuracy Edge** is described as a cloud-based platform that can handle pricing, editing, and claims analysis “in a single pass,” and can incorporate additional third-party content “within a single call” (Section: “Which Approach…”, “02 Single Payment Integrity Platform…”, and Section: “Content Depth and Delivery”).
## What to evaluate: infrastructure, customization, content, and cost
The paper lays out evaluation criteria and then expands on several of them. Under **Infrastructure and Updates**, it contrasts products tied together versus a unified platform, hosted versus cloud-native delivery, and multiple instances versus a single instance across lines of business. A key operational difference highlighted is that the cloud-based platform approach can deliver infrastructure, maintenance, and updates **every two weeks**, reducing the need for additional IT resources (Section: “Infrastructure and Updates”).
For **Customization Capabilities**, it states that in the traditional approach, creating edits may require additional licensing and exporting files, and each update can require maintenance to keep customizations stable. In the single platform approach described, editing rules are managed in a single user interface, custom edits can be built without additional licensing, updates automatically apply without maintenance due to separation of rules and data, and audit trails provide visibility and reporting on custom edits (Section: “Customization Capabilities”).
For **Content Depth and Delivery** and **Cost**, the paper says single-vendor solutions may require separate policy content packages and professional services (including for Medicaid policies). By contrast, the platform approach is described as offering deep content with frequent, automatic updates—including Medicare and Medicaid reimbursement and clinical, billing, and validation edits—paired with a single subscription model that includes content updates and maintenance, helping reduce total cost of ownership by minimizing professional services needs (Sections: “Content Depth and Delivery” and “Cost”).