Contents
Contents
Medicaid encounter data fraud involves knowingly false reports about members’ care or its cost that support a plan’s payments, incentives or avoidance of penalties. The submitted record can say an assessment happened when the nurse never completed it. If you work in encounter submission, analytics or quality, you may know how that story entered the system, who approved it and where it went next. Those decisions can connect the data to fraud inside a managed care plan.
Encounter data tells the state what services a managed care plan reports for its members. The state sends the information to the Centers for Medicare & Medicaid Services through the Transformed Medicaid Statistical Information System. States also use payment data to develop the capitation rates paid to plans and monitor their services.
Capitation is a fixed periodic payment for each enrolled member, usually paid monthly. The plan receives that payment to arrange the health care its contract requires. Inside that arrangement, providers still send claims to the plan, which processes and pays them.
That makes the destination of a false number consequential. A service count can enter a quality measure. A reported provider payment can enter the information used to set future rates. A claimed assessment can help a plan meet a performance target attached to money it wants to keep.
Under the federal managed care rules, plans submit certified encounter data, capitation-rate base data and medical loss ratio data, along with other required information. The chief executive, chief financial officer or an authorized direct report signs off that, to the best of their knowledge, the data are accurate, complete and truthful. The submission staff and the person signing that certification may be looking at different versions of the story. We trace what each received.
The encounter’s path runs through the provider’s records, the plan’s systems and the state’s systems. Each transfer matters when the final record differs from the care or payment underneath it.
The federal government’s October 2000 managed care fraud guidelines described where data could break down: entering the plan’s system, moving through it, leaving it for the state and passing through the state’s system. The guidelines recommended checks on member and provider identifiers, service dates, procedure codes and enrollment. Records that failed those checks were to return to the plan for correction and resubmission.
The guidelines recommended putting encounter definitions and submission deadlines in the contract. We work from the terms that governed the plan during the period involved.
A rejected encounter and a denied provider claim also describe different decisions. One concerns whether the submission passes the system’s checks. The other concerns whether the payer pays for a service. In its 2023 Medicare Advantage review, the Health and Human Services Inspector General explained that Medicaid encounter records include denied-claim indicators. Those fields let investigators separate denied claims from paid claims and examine each. A submission analyst may understand a rejection message while a claims employee knows why the provider went unpaid.
The original record, the reason for rejection and the resubmitted version show what a correction changed. We follow that change back to the service record and forward to the report that used it.
When a field is missing, the first question is where it disappeared along the submission path. When a mapping rule translates a source value into a different reported value, the question is what the field meant at each end. When staff mark work complete, the question is who performed that work and what supports the entry. The staff member who understands the field can explain why the output changed.
The instruction behind a change can be as revealing as the changed value. A written workflow that directs staff to mark uncompleted assessments as finished tells us how a false service record was created. An internal warning followed by another submission tells us who had the chance to address it. We connect those decisions to the certification, rate calculation or performance payment that relied on the output.
CareSource agreed to a $26 million settlement with the United States and Ohio in February 2011 over allegations that it failed to provide required screening, assessment and case management, then submitted false data to make those services appear complete. The Justice Department’s account tied the alleged false data to retaining Ohio Medicaid incentives and avoiding penalties.
The whistleblowers’ complaint alleged that a compliance employee told them the company risked losing $6.3 million for each six-month reporting period in state fiscal year 2004 if it missed minimum performance measures.
The whistleblowers’ complaint described the work behind the numbers. It alleged that written workflows directed nurses to mark positively screened enrollees as assessed before an assessment occurred. Another instruction allegedly required nurses to turn screening sheets into computer entries showing completed baseline assessments.
The complaint described what happened when staff then failed to reach an enrollee:
If later attempts to contact the enrollee were unsuccessful, the enrollee’s information was left in the Missed Queue Call Bucket. Although the Missed Queue Call Bucket was periodically and systematically purged, the false record of Baseline Assessment remained in SACMS.
On the whistleblowers’ account, the missed-call entry disappeared. The assessment that never happened stayed. We call that success on paper, at the member’s expense.
The complaint also alleged that nurses assigned as case managers lacked the training and resources to provide case management. It alleged that false service data and certifications enabled the company to avoid monetary sanctions and receive performance bonuses or incentives. The service definition, workflow instruction, computer entry and performance report each supplied a different part of the alleged scheme.
For a quality employee, that is a recognizable payment connection. The reported result says the plan met a service target. The clinical staff’s account explains what actually happened. The incentive terms explain why the reported result mattered to the plan’s money.
Comparing encounter data with medical charts tests whether the submitted account matches the healthcare delivered.
The 1999 report Controlling Fraud and Abuse in Medicaid: Innovations and Obstacles, from Harvard’s Kennedy School of Government and sponsored by the Health Care Financing Administration, described an Oregon external-validation study. The study compared managed health and dental plans’ encounter data with medical charts and found a 32% discrepancy rate. The report made the direction explicit:
The medical records showed more services than the encounter data.
That historical comparison puts the patient record back in the picture. CareSource’s alleged false entries made unfinished work appear complete. In the Oregon study, the encounter data omitted services the charts recorded. The comparison tells us which direction to investigate.
The national payment-data problem remained visible in the Inspector General’s March 2021 review. It examined January 2020 encounter claims for the largest managed care plan in each of 39 states with comprehensive, risk-based managed care.
The findings separated amounts paid, allowed and billed. About half the states supplied incomplete or inaccurate information about what plans paid providers. Almost three-quarters did so for the maximum amounts plans allowed, and over a quarter for what providers billed.
An insider can explain what produced the missing or changed values, what the plan knew about them and which financial report used them.
Yes. Encounter checks include automated edits, comparisons with medical records, service verification and independent review.
Federal managed care rules require plans to have a method, using sampling or other approaches, to verify that members received services network providers represented as delivered. The state’s encounter and financial data audits address accuracy, truthfulness and completeness. For someone in quality assurance, the useful question is whether the review reached the underlying care record.
The National Health Law Program’s 2015 A Guide to Oversight, Transparency, and Accountability in Medicaid Managed Care explains that encounter data feeds quality metrics and capitation rates. It describes states using external quality review to validate encounter data, while criticizing reviews that rely on plans’ self-reported information. Our question is what the reviewer tested independently. Reusing the plan’s reported result can leave the original contradiction untouched.
Yes. Federal managed care rules make referral of potential fraud a required contract term. The plan’s internal findings and referral history can show what happened after staff identified a concern.
The Inspector General’s 2018 review found weaknesses in proactive data analysis, referrals, reporting actions against providers and overpayment recovery. It also explained the financial incentive: recovered overpayments enter the calculation of future state payments to plans. Money recovered from providers reduces the cost base used to set later capitation rates. A finance insider may know whether the recovery ever reached the data used for those rates. We examine the response to the finding alongside the data itself: what changed, what stayed in the next report and what happened to the payment.
Visiting Nurse Service of New York’s Far Rockaway Assertive Community Treatment program shows another way service records connect to capitation. A whistleblower started the case, and the government joined it. In its government complaint, the United States alleged that the provider claimed full monthly payments when the documented patient contacts supported only partial payment.
The complaint also alleged missing or delayed assessments, service plans, psychiatric visits and progress notes. Its payment theory followed what the program had provided or documented for the patient during the month. In the settlement announced in June 2024, VNS admitted and accepted responsibility for conduct alleged in the government’s complaint.
CareSource’s alleged false performance data concerned incentives and penalties. The VNS allegations concerned the monthly service payment itself. For an insider, identifying which payment depended on the record is part of making the account specific.
The useful evidence connects the underlying care, the submitted account, the people who knew about the difference and the money affected. We work through those connections with you, using the plan’s contract and the requirements for the period involved.
Submission staff can explain how a record moved through an edit and resubmission. Clinical staff can explain what an assessment required and whether it happened. Quality staff can connect that assessment to a performance measure. Finance can identify the incentive, reported medical spending or rate-base data affected. The person who raised the concern may also know who received it before the next certification. The Harvard seminar report emphasized the value of insiders who could describe company policy and practice. That explanation can connect a number in a file to the decision that put it there.
That is the substance of a Medicaid False Claims Act case built around false records: a representation tied to money, with an account of the decisions behind it. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.
If your work shows how missing care became a completed encounter or performance result, speak with our whistleblower experts about how the record changed. We build your Medicaid whistleblower case with you, connect the false report to the money and bring in Medicaid managed care whistleblower lawyers who understand those payment arrangements. You bring the inside account, and we stay beside you through the case.