BLOG

Home Health PEPPER Report Analysis: How to Interpret Your Audit Risk Score (2026 Update)

High PEPPER percentile rankings do not confirm improper billing, but sustained outlier patterns may attract MAC and UPIC scrutiny. This article explains how to interpret target areas, identify documentation gaps, and use chart audits to reduce audit exposure.

IN THIS ARTICLE
AUTHOR
Dr. Anitha Arockiasamy
Founder & President, Red Road
DATE
March 23, 2026
READING TIME
12 min
SHARE THIS BLOG

The Program for Evaluating Payment Patterns Electronic Report (PEPPER) helps home health agencies analyze Medicare billing patterns that may attract audit scrutiny. Interpreting PEPPER data helps agencies understand how their billing patterns compare with peer organizations and whether any trends may warrant internal compliance review.

Key Takeaways

  • The PEPPER report analyzes three years of Medicare Fee-for-Service claims data to highlight potential billing outlier patterns for home health agencies.
  • PEPPER percentile rankings do not confirm fraud or improper billing, but high percentiles may signal patterns that attract scrutiny from MACs, RACs, UPICs, or OIG audits.
  • Agencies appearing at the 80th percentile or higher for certain PEPPER target areas should review clinical documentation, coding accuracy, and OASIS scoring alignment under PDGM requirements.
  • PEPPER data is most useful when incorporated into routine compliance monitoring, including targeted chart audits and documentation review.
  • Targeted clinical documentation reviews may help agencies address persistent outlier patterns before they lead to denials or recoupments.

What Is the PEPPER Report for Home Health Agencies?

The Program for Evaluating Payment Patterns Electronic Report (PEPPER) is produced under contract with CMS to analyze Medicare claims patterns at the provider level. The report is delivered as an Excel workbook containing three fiscal years of claims data. It compares an agency’s billing practices to national, MAC jurisdiction, and state peers, identifying potential outlier behavior in focus areas associated with improper payments.

PEPPER is intended as a monitoring tool to help providers identify unusual billing patterns before they trigger external medical review.

PEPPER is not a public dataset. Each organization receives its report through the PEPPER portal or CMS secure transfer systems, using credentials tied to the agency’s CMS Certification Number. This program has been used across multiple provider types for over two decades as part of ongoing monitoring efforts to identify payment patterns that may require additional review.

Why the PEPPER Report Matters for Home Health Compliance and Audit Risk

PEPPER allows healthcare providers to view their claims patterns the way Medicare contractors might analyze them during risk monitoring. CMS and oversight entities, including MACs, RACs, UPICs, and OIG investigators, use claims analytics to identify providers whose billing behavior deviates from peer norms.

High PEPPER scores do not automatically indicate noncompliance, but they increase the likelihood of receiving Targeted Probe and Educate reviews, Additional Documentation Requests, focused claim audits, or claim reviews or medical necessity audits. Agencies that regularly track PEPPER data are better positioned to respond to home health audits and demonstrate proactive compliance monitoring.

How Home Health Agencies Access and Download Their PEPPER Report

Agencies typically access their PEPPER through the official PEPPER portal or secure CMS file transfer systems such as QualityNet. Access requires credentials tied to the agency’s CCN and security permissions, often managed by a privacy and security officer or designated compliance staff.

The general access process involves logging into the portal, locating the most recent release, downloading the Excel workbook, and storing it securely for review by leadership and compliance teams. Agencies experiencing access issues should contact the PEPPER Help Desk or CMS technical support.

Key Target Areas in the Home Health PEPPER Report

PEPPER analyzes specific target areas associated with potential Medicare payment risk. These areas may change as CMS updates payment models and reporting methodologies.

Many PEPPER target areas reflect utilization patterns that may influence reimbursement under the Patient-Driven Groupings Model (PDGM).

Common target areas include:

Target Area What It Measures
Episodes with Outlier Payments Percentage of episodes receiving unusually high reimbursement
High Average Case-Mix Index Whether case-mix distribution exceeds peer benchmarks
High Resource Utilization Episodes with unusual visit numbers or service intensity
Clinical/Functional Severity Patterns Concentration in higher PDGM clinical groupings
Episode Duration Patterns Unusually short or long episodes relative to peers

For each target area, PEPPER compares agency data with national and regional benchmarks to determine percentile rankings.

Understanding PEPPER Percentile Rankings

PEPPER percentiles show where an agency falls relative to other providers. The core data elements include:

  • Numerator: Episodes meeting the target definition
  • Denominator: Total relevant episodes for that category
  • Provider Percent: Numerator divided by denominator
  • Percentile Ranking: Position compared with national, MAC, and state peers

These percentile thresholds are commonly used by compliance teams to identify areas that may warrant closer internal review.

These values allow agencies to understand how their claims patterns compare with peer agencies reporting similar Medicare data.

What Percentiles Typically Trigger Medicare Scrutiny

PEPPER documentation flags certain percentile thresholds as indicators of elevated audit interest:

  • Below 80th percentile: Generally within normal peer variation
  • 80th–89th percentile: Elevated outlier position warrants internal review
  • 90th percentile and above: Strong outlier pattern that may draw auditor's attention

Agencies appearing in these percentile ranges should confirm that documentation and coding practices appropriately support billed services.

CMS does not treat percentile thresholds as automatic indicators of improper billing, but sustained outlier patterns often prompt additional data review.

Common Reasons Home Health Agencies Become PEPPER Outliers

High percentiles often result from operational patterns rather than intentional improper billing. Common drivers include:

  • High therapy utilization patterns compared with peer agencies
  • Case-mix distribution shifts toward higher PDGM clinical groupings
  • LUPA or episode pattern anomalies in low utilization payment adjustments
  • Documentation and OASIS inconsistencies creating misalignment between clinical notes and coded diagnoses
  • Recertification or episode sequencing patterns without clear clinical justification

Identifying these drivers requires chart-level claims review, not just data analysis. Compliance teams should determine whether patterns reflect legitimate clinical complexity or indicate documentation gaps, coding inaccuracies, or unusual service utilization patterns.

Step-by-Step: How to Interpret Your PEPPER Target Area Data

Administrators can interpret PEPPER results using the following workflow:

  1. Identify High Percentile Targets – Flag areas at or above the 80th percentile
  2. Examine Year-Over-Year Trends – Compare three years of data to determine trajectory
  3. Analyze Numerator Cases – Identify which patient episodes contribute to outlier values
  4. Conduct Targeted Chart Audits – Review documentation, OASIS assessments, and visit patterns
  5. Determine Operational Drivers – Assess whether patterns relate to referral sources, coding practices, or inadequate documentation
  6. Document findings and corrective actions for internal compliance records

This approach helps agencies identify whether patterns require corrective action or reflect documented clinical complexity.

Using PEPPER Data to Prioritize Internal Compliance Audits

PEPPER becomes a valuable resource when integrated into structured compliance programs. Agencies should:

  • Identify target areas with elevated percentiles
  • Rank them by financial impact and audit exposure
  • Select subsets for quarterly chart audits
  • Assign review responsibilities across clinical leadership, QA teams, and billing staff

Findings should lead to clinician education, OASIS scoring review, and coding policy adjustments. Documenting these efforts helps demonstrate ongoing compliance monitoring during external audits.

Linking PEPPER Findings to Coding Accuracy and Documentation Quality

PEPPER outlier patterns often trace back to documentation and billing practices. High case-mix percentiles may reflect coding decisions requiring stronger documentation support. Resource utilization outliers may indicate inconsistencies in visit scheduling or medical necessity documentation. Recertification patterns may highlight gaps in homebound status documentation.

Documentation should clearly support medical necessity, homebound status, and the skilled services provided.

Aligning clinical documentation, OASIS assessments, and coding decisions helps ensure claims are supported by the medical record. Pre-billing chart reviews can help agencies identify documentation gaps before claims are submitted.

Example: Reducing PEPPER Outlier Status Through Documentation Review

An agency identifying high-percentile patterns in resource utilization target areas conducted targeted chart audits focusing on visit frequency and skilled need documentation. The review identified documentation gaps in skilled need explanations and inconsistent visit justification in several charts.

Following clinician education and documentation improvement initiatives, the agency tracked improved percentile positions over subsequent PEPPER cycles, demonstrating that structured documentation review processes can reduce compliance exposure.

How External Compliance Review Can Help Agencies Act on PEPPER Findings

Some home health and hospice agencies lack the internal capacity to analyze PEPPER data comprehensively or conduct detailed chart reviews. External review support may help agencies:

  • Analyzing PEPPER trends and identifying high-risk target areas
  • Performing targeted coding and documentation audits
  • Validating OASIS accuracy
  • Identifying root causes of outlier patterns
  • Supporting audit preparedness and denial prevention

External review support focuses on improving documentation defensibility, strengthening coding accuracy, and helping agencies address patterns that may increase audit risk.

Frequently Asked Questions About Home Health PEPPER Reports

PEPPER for home health is typically updated annually using three completed fiscal years of Medicare claims data. Agencies access reports through the secure PEPPER portal using provider-specific credentials. For additional information or access assistance, contact the PEPPER Help Desk.

Appearing at high percentiles in multiple areas should trigger a structured internal review process that includes chart audits, documentation validation, and coding review: confirm data accuracy, perform focused chart reviews, analyze whether documentation supports services billed, and document corrective actions.

Low percentile positions indicate billing patterns closer to peer averages but do not guarantee full compliance. Agencies can still face denials based on individual documentation deficiencies, undercoding issues, or claims failing medical necessity requirements.

Agencies with limited claim volumes may see unstable PEPPER metrics because small numerator changes significantly shift percentages. Smaller facilities should focus on persistent outlier trends across multiple report cycles rather than minor year-to-year fluctuations.

PEPPER is a monitoring tool and does not replace claim-level documentation when appealing denials. However, agencies can reference PEPPER-driven compliance efforts as context demonstrating proactive monitoring. Successful appeals depend on strength of medical record documentation, OASIS accuracy, and coding support for each denied claim.

Looking to
read more?