Compliance Guide · 2026

OASIS-E2 Compliance: Audits, Requirements, and How to Stay Clean

OASIS-E2 raises the stakes on documentation quality and CMS compliance. This guide walks through the requirements, the most common audit triggers, and the QA workflows that keep your agency out of trouble.

Key Takeaways

  • →5 core OASIS-E2 compliance requirements: complete assessments at all time points, timely submission, clinician training, supporting documentation, pre-submission QA workflow.
  • →Top audit triggers: outlier billing patterns, doc-OASIS mismatch, unusually high functional impairment scoring, ICD-10 / OASIS misalignment.
  • →HH QRP penalty for non-compliance: 2 percentage-point reduction to annual market basket update, direct revenue hit.
  • →Conditions of Participation directly tied to OASIS, §484.55 (assessment), §484.45 (reporting), §484.110 (clinical records).
  • →Real-time AI QA reviews 100% of charts, shifts compliance from reactive sample-based review to proactive prevention.

CMS OASIS-E2 Compliance Requirements

Per the CMS OASIS Data Sets page and 42 CFR Part 484 (Conditions of Participation), Medicare-certified home health agencies must comply with five core OASIS-E2 requirements:

  1. Complete and accurate OASIS-E2 assessments at all five time points, Start of Care (SOC), Resumption of Care (ROC), Recertification, Transfer to Inpatient Facility, and Discharge.
  2. Timely data submission, assessments must be submitted to the iQIES system within CMS-required timeframes.
  3. Clinician training on the OASIS-E2 item set, including the E2 changes: O0350 removed, A1255 Transportation, A0810 Sex, Language, Hearing, and Vision at ROC, and the revised fall items. See the OASIS-E2 Item Guide.
  4. Documentation that supports OASIS responses, every OASIS response should be defensible from the clinical record.
  5. QA workflow that catches errors before submission, relying on retrospective review alone is insufficient given the cost of a denial.

Agencies that fail to comply face Home Health Quality Reporting Program (HH QRP) penalties (a 2 percentage-point reduction to the annual market basket update) plus increased audit risk and potential survey deficiencies.

OASIS-E2 Audit Triggers

CMS, MACs (Medicare Administrative Contractors), RACs (Recovery Audit Contractors), and state survey agencies all use data analytics to identify agencies for review. Common triggers include:

  • Outlier billing patterns, average payment per 30-day period significantly higher than peer agencies in your geographic region
  • Unusually high functional impairment scoring, driving the High functional level under PDGM more often than peers
  • Documentation-OASIS mismatch, clinical narrative inconsistent with OASIS responses (the single most common audit citation)
  • ICD-10 / OASIS misalignment, an M1021 primary diagnosis that doesn't match the claim's principal diagnosis or the services in the plan of care
  • Patient complaints to state survey agencies
  • Prior survey deficiencies, agencies with recent CoP deficiencies face increased scrutiny
  • Whistleblower / employee complaints via OIG hotline
  • TPE (Targeted Probe and Educate) reviews by your MAC

Most Common OASIS-E2 Errors

Based on patterns from MAC and RAC reviews, these are the most common OASIS-E2 errors that lead to denials, ADRs, or compliance findings:

  1. Functional scoring inconsistencies, patient described as ambulating in the narrative but scored as requiring substantial assistance in M1860 or Section GG.
  2. Missing or incomplete social item responses, such as A1255 Transportation or B1300 Health Literacy skipped, or coded from a proxy after the patient declined.
  3. BIMS / PHQ administration errors, items completed without following standardized administration guidance.
  4. Timing errors, SOC assessments completed outside the 5-day window, or Discharge OASIS submitted late.
  5. Internal M-item contradictions, responses that logically conflict with each other.
  6. OASIS-to-ICD-10 misalignment, a principal diagnosis that maps to no PDGM clinical group, which gets the claim returned to the provider.
  7. Documentation that doesn't support functional scoring, the most common ADR finding.

OASIS-E2 and Conditions of Participation (CoPs)

Medicare CoPs for home health agencies (42 CFR §484) include requirements directly tied to OASIS:

  • §484.55 Comprehensive Assessment of Patients, requires comprehensive patient assessment at SOC, completed by an RN (or qualified therapist for therapy-only cases).
  • §484.45 Reporting OASIS Information, requires accurate, complete, and timely OASIS submission.
  • §484.110 Clinical Records, requires documentation that supports the assessment.

State surveyors evaluate OASIS-E2 documentation during routine surveys, complaint investigations, and validation surveys. Deficiencies can result in survey citations ranging from Standard Level (no penalty) to Condition Level (potentially threatening Medicare certification).

Building an OASIS-E2 Compliance Program

A defensible OASIS-E2 compliance program includes:

  1. Written OASIS-E2 policies and procedures, updated to reflect the OASIS-E2 item set, with version control and clinician sign-off.
  2. Initial clinician training, see the OASIS-E2 Training Guide for a 90-day curriculum.
  3. Ongoing competency validation, annual recompetency for all OASIS-completing clinicians.
  4. QA workflow, pre-submission review of every assessment, ideally with real-time AI assistance via automated OASIS QA.
  5. ADR / audit response procedures, documented playbook for responding to additional documentation requests.
  6. Quarterly internal audits, sample-based review of submitted OASIS data with feedback to clinicians.
  7. Audit trail, comprehensive logging of every OASIS edit, approval, and submission.

How AI Improves OASIS-E2 Compliance

Manual QA review alone cannot keep up with the volume of OASIS-E2 assessments a typical agency produces. AI-powered QA tools improve compliance by:

  • Reviewing 100% of assessments, not just a 10% sample.
  • Real-time error detection, flagging issues during the visit, not days later.
  • Documentation-OASIS cross-validation, comparing visit narrative to OASIS responses for consistency.
  • PDGM scoring sanity checks, catching responses likely to misclassify functional level.
  • Complete audit trail, every flag, edit, and approval logged automatically.

Lime's OASIS-E2 ambient scribe includes real-time QA built in, OASIS Scribe drafts responses from the visit conversation, flags inconsistencies so your QA team corrects them, and the clinician confirms every final response before submission.

Related OASIS-E2 Resources

OASIS-E2 Compliance, FAQ

What are the OASIS-E2 compliance requirements?
OASIS-E2 compliance requires that Medicare-certified home health agencies (1) submit complete and accurate OASIS-E2 assessments at all five required time points (SOC, ROC, Recertification, Transfer, Discharge), (2) submit data within CMS-required timeframes, (3) ensure clinician training on the OASIS-E2 item set, including the E2 changes such as A1255 Transportation, the ROC additions, and the new fall definition, (4) maintain documentation that supports OASIS responses, and (5) operate a QA workflow that catches errors before submission. Failure to comply can trigger Home Health Quality Reporting Program penalties (a 2 percentage-point reduction to the annual market basket update) and increased audit risk.
What triggers an OASIS-E2 audit?
Common OASIS-E2 audit triggers include: outlier billing patterns relative to peer agencies, unusually high functional impairment scoring that drives PDGM payment, inconsistencies between OASIS responses and clinical documentation, ICD-10 coding patterns that don't match the assessment data, complaints to state survey agencies, prior survey deficiencies, and Recovery Audit Contractor (RAC) and Medicare Administrative Contractor (MAC) targeted reviews. Agencies that maintain consistent OASIS-to-documentation alignment and operate strong QA workflows minimize audit risk.
What are the most common OASIS-E2 errors?
The most frequent OASIS-E2 errors include: inconsistencies between Section GG functional scoring and the patient's described abilities in the visit narrative, M1800-M1860 responses the narrative does not support, missing or incomplete social items such as A1255 Transportation, BIMS or PHQ-2/9 items completed without proper administration, timing errors (assessments submitted outside the required window), conflicting M-item responses, and a primary diagnosis that does not match the claim or maps to no PDGM clinical group. Real-time AI QA flags these so your QA team corrects them before submission.
How does OASIS-E2 affect Conditions of Participation?
Medicare Conditions of Participation (CoPs) for home health agencies include requirements related to the comprehensive assessment, which OASIS-E2 directly fulfills. CoP §484.55 requires a comprehensive assessment at SOC, with subsequent reassessments. State surveyors evaluate OASIS-E2 documentation as part of CoP compliance, and deficiencies can result in survey citations. Agencies should ensure clinician documentation supports every OASIS response and that QA workflows identify gaps before survey.
How can AI tools help with OASIS-E2 compliance?
AI tools improve OASIS-E2 compliance by (1) running real-time QA on every assessment instead of sample-based review, (2) cross-validating OASIS responses against clinical documentation and visit narratives, (3) flagging inconsistencies in M1800-M1860 and Section GG functional scoring before submission, (4) checking that social items and BIMS are completed properly, and (5) maintaining a complete audit trail of every change and approval. This shifts QA from a downstream catch-up activity to an upstream prevention activity.

Want OASIS-E2 compliance on autopilot?

See OASIS Scribe