CMS ODAG Audit Guide: Requirements, Universes, and Prep Checklist

ODAG Universe Tables Overview

This guide helps you prepare accurate ODAG universes that align with CMS Audit Protocols. It explains required table content, timing, data quality controls, and how to avoid Invalid Data Submission findings during a program audit.

What ODAG universes cover

ODAG universes document organization determinations, reconsiderations (appeals), and grievances for Part C. They capture intake through final outcome, including timeliness, notices, outreach, and resolution details for each case in scope.

Typical ODAG table families

• Organization determinations (standard and expedited; pre- and post-service/payment).
• Reconsiderations/appeals, including escalations and dismissals.
• Grievances and coverage-related complaints tracked to closure.
• Notices, outreach, and physician/provider contact attempts tied to each case.
• Delegated entity activity and oversight where processing is outsourced.
• Special populations (for example, Dual Special Needs Plan Data when applicable).

Inclusions, exclusions, and traceability

Include one record per unique case with stable case IDs. Exclude non-ODAG issues (e.g., pure customer service calls) unless they meet ODAG definitions. Ensure every row is traceable to source systems and artifacts used in Data Integrity Testing.

ODAG prep checklist

• Map intake, clinical, appeals, and grievance systems to the correct ODAG tables.
• Define Universe Data Fields precisely; build a data dictionary and value crosswalks.
• Confirm how you flag standard vs. expedited, reopenings, withdrawals, and dismissals.
• Identify delegated sources early; validate completeness and key alignment.
• Tag special populations (e.g., D-SNP) and any Applicable Integrated Plan Reductions implications.
• Dry-run export and perform integrity checks against CMS Audit Protocols before submission.

Universe Submission Deadlines

Your deadline is set in CMS’s engagement letter. Treat the Engagement Letter Date as the anchor and follow the explicit due date and time communicated by CMS. Submit via the designated secure portal and follow file naming and packaging instructions precisely.

Readiness before you upload

• Validate record counts against operational reports and prior extracts.
• Confirm date/time zones and effective period logic match audit instructions.
• Eliminate duplicate case IDs and confirm referential consistency across tables.
• Document known limitations and prepare a concise cover note if CMS permits.
• Stage an internal “go/no-go” with compliance and IT at least one business day early.

If delays are likely

Escalate immediately through your audit lead. Provide a concrete plan, affected tables, and a revised timeline. Keep version control tight so any partial submissions can be reconciled during resubmission if requested.

Universe Period Determination Criteria

CMS defines the audit period in the protocols and engagement letter. Anchor inclusion rules to the Engagement Letter Date and the specified look-back window, then apply consistent business logic across all ODAG tables.

Core inclusion logic

• Decide whether inclusion is based on date received, date decided, or another specified milestone.
• Include reopenings or corrected determinations if directed; otherwise treat each case once with the final disposition.
• Apply uniform definitions of “standard” and “expedited” across determinations and appeals.

Boundary and edge cases

• For cases crossing the boundary (received in-period, decided out-of-period), follow the rule prescribed by CMS; do not mix rules across tables.
• For D-SNP or integrated processes, align Dual Special Needs Plan Data handling with CMS Audit Protocols to avoid under- or over-inclusion.

Universe Data Field Requirements

Accurate Universe Data Fields are the backbone of ODAG integrity. Define each field’s purpose, allowable values, format, and source system—and enforce them consistently across all files.

Common fields to specify

• Case identifiers: unique case ID, parent/child IDs for escalations, delegated entity ID.
• Member identifiers: enrollee ID, dual eligibility indicator, contact/representative indicators.
• Key dates/times: intake/receipt, requests for info, decision, notice sent, outreach attempts.
• Classification: determination vs. appeal vs. grievance; standard vs. expedited; pre/post service.
• Outcome and timeliness: approved/denied/withdrawn/dismissed; timeliness met (Y/N) and days.
• Clinical/utilization context: service type/category, reason codes, physician/provider involvement.

Formatting and validation rules

• Use the exact date/time formats specified by CMS; keep a single time zone unless directed.
• Apply controlled vocabularies (e.g., Y/N, enumerated codes); avoid free text where a code exists.
• Prohibit blanks for required fields; use the specified null indicator instead of empty strings.
• Preserve leading zeros, punctuation, and case in identifiers where meaningful.

Documentation and security

• Maintain a current data dictionary and transformation logic for every field.
• Record-source lineage for each field to support Data Integrity Testing and tracer requests.
• Protect PHI/PII using the secure channel defined by CMS; never email raw universes.

Universe Integrity Testing Process

Integrity testing verifies that your files are complete, accurate, and consistent with CMS Audit Protocols. Treat this as both a pre-submission discipline and a CMS-led validation during audit fieldwork.

Your pre-submission tests

• Structural checks: headers, column order, data types, required vs. optional fields.
• Quality checks: duplicates, missing required values, invalid codes, orphaned foreign keys.
• Logic checks: date sequences (received ≤ decision ≤ notice), timeliness math, status coherence.
• Reconciliation: compare counts to operational dashboards and sampling frames.
• Tracer readiness: confirm each sampled record can be evidenced with source artifacts.

How CMS tests integrity

CMS performs automated structure and logic validations, cross-file linkage checks, and targeted tracers back to source systems and artifacts. Failures can trigger expanded samples, clarifying questions, and remediation or resubmission cycles.

Universe Resubmission Policies

If CMS flags issues, you may be instructed to correct and resubmit impacted tables. Expect short turnaround windows and precise instructions on scope, naming, and versioning. Keep a change log that explains every correction and the controls added to prevent recurrence.

Effective resubmission practices

• Isolate root causes (e.g., extract logic, mapping, delegation gaps) and confirm the fix in test.
• Highlight changed rows/fields if CMS requests, preserving stable case IDs across versions.
• Re-run your full integrity suite and reconcile totals to prior submissions before uploading.

Consequences of Inaccurate Universe Submissions

Inaccurate or incomplete universes can lead to an Invalid Data Submission determination, expanded samples, delayed fieldwork, and corrective action requirements. Repeated or material issues can elevate compliance risk and may contribute to broader oversight or financial impacts.

Where applicable, sponsors should assess downstream implications, including potential effects on performance measures and any Applicable Integrated Plan Reductions determinations. Strong preventive controls and timely, transparent remediation reduce these risks.

Conclusion

Center your ODAG work on crystal-clear Universe Data Fields, disciplined pre-submission testing, and schedules anchored to the Engagement Letter Date. When in doubt, align decisions with CMS Audit Protocols, document your logic, and be resubmission-ready—so you can pass Data Integrity Testing the first time.

FAQs.

What is the deadline for submitting ODAG universes?

The due date and time are specified in CMS’s engagement letter. Treat the Engagement Letter Date as the anchor, follow the stated submission window and instructions, and target early delivery to allow for any last-minute fixes.

How does CMS test the integrity of universe data?

CMS runs automated structural and logic validations, checks cross-file consistency, and traces sampled records back to source systems and artifacts. Results guide clarifying questions, expanded samples, or required corrections.

How many attempts are allowed for universe resubmission?

CMS sets resubmission expectations during the audit. You should assume limited opportunities and short turnaround windows; aim for first-pass accuracy and keep a rigorous change log if a resubmission is required.

What are the consequences of submitting inaccurate universe data?

Consequences can include an Invalid Data Submission finding, expanded sampling, corrective action requirements, schedule delays, and elevated compliance scrutiny. Accurate, well-documented universes help you avoid these outcomes.