PACE False Audit Service Request Records: When the Request Disappears From the Submission

False service request records in a PACE audit can conceal what a participant asked for and whether the organization delivered it. If you prepared the spreadsheet, reviewed the original requests or questioned a completion date, you may know where the account changed before the Centers for Medicare & Medicaid Services saw it. The care team and the auditor should be looking at the same events. An omitted request leaves them looking at different stories.

This page follows audit submissions in the Programs of All-Inclusive Care for the Elderly, from original communications to the account sent to oversight and its connection to government payments. Our broader account of PACE whistleblower evidence follows the records across clinical, enrollment and finance roles. Here the question is narrower: what did the organization tell the people checking its work, and who knew whether that account was true?

What Is a PACE Service Request?

A PACE service request asks the organization to start, change or continue care. It can be oral or written and can reach a direct-care employee or contractor at home, at the center or during transportation. The original request may therefore begin with a driver or home care worker before it reaches the interdisciplinary team.

The request, assessment, decision, notice, scheduling and actual delivery answer different questions. A decision records what the team approved. A scheduling entry records what someone arranged. Actual delivery records whether the participant received the service. PACE’s rules require delivery as quickly as the participant’s health needs it.

A grievance concerns a complaint about health care or service, while an appeal challenges a decision about care or coverage. Those records can illuminate the same unmet need from different directions. For an audit employee, the useful comparison begins with what the participant actually communicated and how the organization categorized and handled it.

What Must Remain Behind the Audit Entry?

PACE organizations must preserve original written communications concerning a participant’s care, health or safety. The recordkeeping rules reach emails, faxes and letters from participants, caregivers and others supplying relevant information. They also require safeguards against loss, destruction and inappropriate alteration. An accurate audit account begins before anyone prepares the submission.

The medical record can contain a thorough, accurate summary while the original communication remains elsewhere. The original still has to be accessible to staff and contractors when needed, and to CMS and the state agency on request. A shortened account can change the apparent problem as well as the word count.

Medical records must show what staff and contractors recommended, what was provided, and why a recommended service was not approved or provided. Entries must be dated and authenticated by the primary author through a signature or secured computer entry. Those details let us connect an entry to the person who reviewed and approved it, then examine what happened when the information moved into an audit file.

What Goes Into a PACE Audit Submission?

A PACE audit submission includes the requested universes and supporting quality and compliance information. A universe is the submitted set of records from which CMS can select cases to review. The CMS audit overview describes engagement and data submission, field work, analysis and reporting, then corrective action and closeout. The submission shapes what auditors initially see and select.

The overview names the Service Determination Requests, Appeals and Grievances element. The audit team posts sample selections in the Health Plan Management System, and the organization uploads requested information, including case files, there. Those files connect the submitted rows to the care records behind them.

Before field work, the agency requests supplemental answers, a pre-audit issue summary, quality-improvement plans, participant advisory committee minutes and compliance documentation. The issue summary describes previously disclosed problems and the status of correction. The overview distinguishes issues the organization reported to CMS before the engagement letter from problems CMS or the state identified through monitoring.

The agency checks universes for blank entries and formatting problems and analyzes them against compliance standards. Its overview allows up to three attempts to supply complete and accurate universes and says CMS uses the last version submitted. For an insider who saw a request disappear between versions, the earlier file, the revision instructions and the final submission answer different parts of the story. The audit instructions for the period identify which records belong in each universe. The scope, collection dates and definitions belong beside the actual submission when we examine an omission.

What Do Original Service Requests Missing From a PACE Audit Universe Reveal?

PACE original service requests missing from an audit universe can reveal a gap between the care record and the account supplied to oversight. We compare the original receipt, the request’s handling, the applicable inclusion instructions and the submitted entry. Authorship, changes between versions and internal warnings help explain how the gap arose and who understood it.

The whistleblower complaint concerning InnovAge alleged that service-request information was withheld from CMS and that a regional operating executive was asked to falsify logs. It described a Services Delivery Requests Record with fields for the request, assessment, decision, notice and actual delivery. The whistleblower also alleged concealment of corrective-action information from CMS.

The complaint connected allegedly falsified or omitted audit and correction information to continued government reimbursement. If you worked on those records, you may recognize the difference between reporting a backlog and removing the evidence of it. We see the absurdity in the alleged fix: the care stayed missing, and the record was asked to catch up.

CMS can test beyond the initial sample. Its overview describes requests for supporting case files, root-cause analyses explaining why a problem occurred, and impact analyses identifying affected participants or personnel. The agency may validate those analyses against additional case files or medical records. A later answer about the scope of a problem is another representation to compare with the underlying service records.

Which Records Connect Care Failures to Government Payment?

Original care records, the actual oversight submission and the payment or repayment records connect care failures to government money. PACE organizations receive prospective monthly capitation to provide an integrated benefit, with separate Medicare and Medicaid payment streams. An audit representation becomes financially significant through the statement made, the applicable obligation and the payment decision it could influence.

We look at what the submission left out, who knew, and how it affected government payments or money owed back. Internal warnings can connect knowledge of the care problem to the person responsible for the submission. Accepted enrollment records, capitation receipts, adjustments and reconciliation records identify the affected payment period and payer.

PACE’s financial-record rules require accurate reports, an audit trail to source documents and access to original books concerning services, benefit liabilities and Medicare and Medicaid amounts payable. That financial trail belongs beside the care and audit trail. We identify the particular paid months and the basis for any claimed loss, keeping the targeted audit findings tied to the cases they actually describe.

What Does a PACE Part D Attestation Certify?

A certification’s wording, signatory, covered data and payment purpose determine what it represents. PACE drug-payment reporting supplies a concrete example: CMS’s attestation memorandum for Part D reconciliation requires electronic attestations to receive risk-sharing and reinsurance payment adjustments. The memorandum includes PACE and describes attachments for known errors where CMS has received prior notice and correction is underway.

For an audit or compliance employee, the signed attestation and any error attachment show what management actually represented. The notice of the error, correction work and resulting payment adjustment extend that account. We examine the certification attached to the particular payment stream, including its qualifications.

What Does Acceptance of a Corrective Action Plan Mean?

Acceptance means CMS has reviewed the proposed corrective action and found the plan acceptable. Its audit overview says the audit closes when the corrective action plans are accepted, while organizations are expected to complete implementation within 60 days of acceptance. The file gets to finish first.

The plan, implementation evidence and validation results answer separate questions about correction. A plan can identify the root cause, responsible staff, system changes and monitoring. Implementation records show what changed in operation. Validation tests whether the correction reached the affected work, including the tracking and delivery of care that government payments support.

InnovAge’s Sacramento and Colorado enrollment sanctions illustrate that sequence. CMS required corrective action and later validation, then reviewed organizational attestations and validation audits before releasing the sanctions. Its Sacramento release and Colorado release restored normal enrollment after CMS found the sanction-related deficiencies sufficiently corrected.

PACE4DC’s Tracking Problem Reached the Correction Record

CMS’s PACE4DC sanction notice described failures to provide, track and monitor approved services and to categorize and process service determination requests correctly. The organization had disclosed that self-monitoring audits and service and appointment trackers remained unimplemented.

CMS later reviewed a validation audit and ongoing monitoring before releasing PACE4DC’s enrollment sanction on February 26, 2026. The agency concluded that the sanction-related deficiencies were sufficiently corrected and restored normal enrollment. The progression gives an insider distinct records to compare: what management said would change, what it said had changed, and what the agency subsequently tested.

Who Knew What the Submission Left Out?

The person compiling a universe may see something that the clinician, finance employee and auditor each see only in part. The original request, earlier spreadsheet, correction instructions and final submission can connect those separate views. We work with you on the authorship, review and signoff, the warnings that preceded submission, and the government payments affected by the account sent outside the business.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. If you are considering reporting PACE program fraud, we assess that case with you from the actual submission and payment evidence. Your knowledge of how the audit file was assembled can give those records the context a reviewer outside the organization lacks.

When You Know What Changed Before Submission

If you worked on PACE audit files and know which requests, failures or warnings were left out, speak with our whistleblower experts about the submission you saw. We connect your operational knowledge to the government-payment evidence and bring in healthcare fraud whistleblower lawyers who understand capitation and false reporting. We stay beside you as partners in building and pursuing the case.