Omnicare: A Verification System That Lost the Drug’s Identity

Omnicare agreed to an $8 million settlement in its automated verification fraud case over allegations that its software put the wrong drug identity on government claims and patient labels. The government said a system designed to improve efficiency and profit used a less specific drug code during pharmacist verification. The government alleged that the resulting mismatch followed the medication into the billing records, the patient’s label and the information needed to track a recall.

The Justice Department announced the agreement on May 16, 2017 after whistleblowers brought a False Claims Act qui tam case in New Jersey. For someone who knows the pharmacy’s software or dispensing workflow, the central question is concrete: what drug did the system say went out, and what drug actually went out?

What Omnicare’s Automated Verification Changed

The government alleged that Omnicare used MEDID, a less specific drug code, instead of the more specific National Drug Code during its automated Stage II pharmacist verification process. The allegation concerned an automated label-verification system at certain locations.

That choice of code is the heart of the case. According to the government, Omnicare designed and implemented the system to increase business efficiency and profit. The verification step was supposed to check the medication’s identity, yet the alleged design used a code that carried less identifying detail.

This differs from Omnicare’s separate Lodi drug-code case, announced in 2016. There, employees allegedly changed the National Drug Code field on rejected claims before resubmitting them to Medicare, Medicaid and TRICARE. Here, the government’s allegation reached the verification system itself and the drug information it produced.

How the Wrong Drug Identity Reached the Claim

The government alleged that Omnicare submitted claims for generic drugs different from those actually dispensed to Medicare and Medicaid beneficiaries. It also alleged that patient-specific labels displayed the wrong manufacturer or National Drug Code, and that false manufacturer and code information appeared in the electronic dispensing information.

The billing claim and the patient label described the same dispensing event to different audiences. One told the government health care program what it was being billed for. The other identified the medication supplied to the patient. In the government’s account, the wrong identity reached both.

The Omnicare announcement identifies Medicare Part D and Medicaid. Its allegation concerns the pharmacy’s drug claims and dispensing records.

The Recall Problem Behind the Label

False drug identities also affected Omnicare’s ability to track medications and, if necessary, conduct patient-level recalls, the government alleged. That made the verification issue a patient-safety problem as well as a billing problem.

A manufacturer or drug code on a label connects a patient to a particular product. If that information points to a different product, the dispensing history can lead the pharmacy away from the people it needs to reach. The government specifically identified false information in the electronic records as well as on the physical labels. Rechecking a label against a matching electronic entry would miss the underlying problem if both carried the wrong identity.

Taxpayers were billed for one drug identity while patients received another, according to the government’s allegations. A step built to verify the label allegedly made the drug harder to trace.

What Is the Reward for a Medicare Fraud Whistleblower?

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. In this case, the announcement said the whistleblowers would receive more than $2 million covering both their statutory shares of the recovery and the resolution of employment-based claims.

What Evidence Is Needed to Prove Fraud?

For an automated pharmacy verification allegation, we connect the drug actually dispensed with the code used at verification, the patient label, the electronic dispensing entry and the claim sent for payment. Those connections show where an identity changed and how far the change traveled.

We examine how the verification rule was chosen, where it operated and what the dispensing and healthcare billing records show for the same medication. A pharmacist may recognize the product mismatch, a billing employee may know the code transmitted, and a systems employee may understand why the software accepted it. Our work is to connect that knowledge to the claims and the decisions behind them.

Other Omnicare Cases, Different Decisions

Omnicare’s pharmacy cases involve distinct business decisions: how to win a facility’s business, which drugs to promote and what the dispensing system allows. Their differences help an insider identify the transaction that matters.

In the earlier Mariner and SavaSeniorCare case, the government alleged that Omnicare disguised a payment for long-term pharmacy contracts as the purchase of a small business.

A later Omnicare settlement in 2014 concerned allegedly below-cost facility drug contracts used to obtain other reimbursable pharmacy business. During a covered Medicare Part A skilled nursing stay, the facility’s payment ordinarily bundles drugs with nursing and other services. Medicare pays the facility, whose contract governs payment to an outside supplier. That helps explain the alleged bargain: a cheaper facility contract bought access to separately reimbursed pharmacy business.

The 2016 Depakote settlement concerned alleged manufacturer inducements, including grants, educational funding and rebates linked to use.

A separate case against Omnicare and CVS concerned drugs dispensed without valid prescriptions in assisted living and other residential settings. The government’s complaint quoted an internal compliance officer describing what the software allowed:

The government alleged that the system kept prescriptions going after they expired or ran out of authorized refills. In 2025, a jury found Omnicare liable for false claims and CVS liable for causing Omnicare’s false claims. That case concerned prescription validity. The automated verification settlement concerned drug identity. Both put the software’s treatment of medication records at the center of the pharmacy’s billing.

You Know What the System Accepted

If you can explain why a pharmacy’s verification system accepted one drug identity while another drug went out the door, speak with our whistleblower experts about what the system accepted. We develop your case around that knowledge, bring in pharmacy fraud whistleblower lawyers who understand dispensing systems and government billing, and stay beside you through the pursuit of a recovery.