The 2016 implied-certification ruling read billing codes as statements about the service and who provided it

On June 16, 2016, the Supreme Court held that claims using specific service codes and provider identifiers can be misleading half-truths. In our reading, that put False Claims Act risk in claim data and the payer’s own record.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On June 16, 2016, the Supreme Court held that claims using specific service codes and provider identifiers can be misleading half-truths. In our reading, that put False Claims Act risk in claim data and the payer’s own record.

  1. The week On June 16, 2016, the Supreme Court decided No. 15-7, a False Claims Act case from the First Circuit about Medicaid claims for mental health counseling. [1] [2] The judgment of the court of appeals was vacated and the case remanded.
  2. What the claim says: codes and identifiers as representations The Court did not decide whether every claim implicitly represents that the billing party is legally entitled to payment. [1] It decided something narrower.
  3. What the claim leaves out: where the half-truth arises The second condition is an omission.
  4. Whether the omission matters: materiality as a record of behavior The third part is where the Court set real limits.
  5. Who knew: the knowledge standard and an organization’s own records The fourth part is knowledge.
  6. What the ruling left undecided The opinion settled a framework and left several questions open.
  7. How the ruling plays out across health organizations The four parts apply to anyone submitting claims to federal programs, but they land differently by type of organization.
  8. Objections to this reading Four objections deserve an answer.
  9. Checks a compliance or technology leader can run now These checks follow from the ruling’s structure.
  10. With hindsight The case returned to the First Circuit.

The week

On June 16, 2016, the Supreme Court decided No. 15-7, a False Claims Act case from the First Circuit about Medicaid claims for mental health counseling. [1] [2] The judgment of the court of appeals was vacated and the case remanded. Justice Thomas delivered the opinion for a unanimous Court. [2] The case had been argued on April 19, 2016. [1]

The case reached the Court at the pleading stage, so its facts were allegations. As the Court described them, a teenage beneficiary of the Massachusetts Medicaid program received counseling for several years at a satellite mental health facility. [1] The facility was owned and operated by a subsidiary of the petitioner, the health care company Universal Health Services, Inc. [1]

The relators, the patient’s mother and stepfather, learned, as the Court recounted, that few of the facility’s employees were actually licensed to provide mental health counseling and that supervision of them was minimal. The complaint alleged that unlicensed staff counseled patients and prescribed drugs without supervision, despite regulatory requirements. [1] According to the Court’s summary, the patient had an adverse reaction to a medication prescribed by a purported doctor, her condition worsened, and she died. [1]

The relators filed a qui tam suit under the False Claims Act. The Act imposes liability on anyone who knowingly presents a false or fraudulent claim for payment or approval to the federal government. [1] The Court noted that a claim includes reimbursement requests made to recipients of federal funds under federal benefits programs. [1]

The relators relied on what the Court called the implied false certification theory. Under it, a defendant that submits a claim impliedly certifies compliance with all conditions of payment. [1] If the claim fails to disclose a violation of a material statutory, regulatory or contractual requirement, the theory holds that the claim is a misrepresentation that makes it false or fraudulent. [1]

The district court dismissed the case because, with one exception not relevant to the appeal, none of the regulations allegedly violated was a condition of payment. [1] The First Circuit reversed in relevant part. As the Supreme Court described it, that court observed that each claim implicitly communicates conformity with the relevant program requirements, and asked whether the defendant knowingly misrepresented compliance with a material precondition of payment. [1]

The Supreme Court took a middle course. It held that implied certification can be a basis for liability, at least where two conditions are satisfied. [1] First, beyond requesting payment, the claim makes specific representations about the goods or services provided. [1] Second, the failure to disclose noncompliance with material requirements makes those representations misleading half-truths. [1]

The Court applied that test to the claims at issue. It said that by using payment codes corresponding to specific counseling services, the company represented that it had provided individual therapy, family therapy, preventive medication counseling and other treatment. [1] It said staff allegedly made further representations by using National Provider Identification numbers corresponding to specific job titles. [1]

The Court rejected the company’s argument that liability should be limited to requirements expressly designated as conditions of payment. [1] It also rejected the government’s and the First Circuit’s view that any violation is material if the defendant knows the government could refuse payment. [1]

On materiality the Court wrote, “The materiality standard is demanding.” [1] It said the Act is not an all-purpose antifraud statute or a vehicle for punishing garden-variety breaches of contract or regulatory violations. [1] A condition-of-payment label was relevant but not automatically dispositive. [1]

The Court said that if the government pays a particular claim in full despite actual knowledge that certain requirements were violated, that is very strong evidence that those requirements are not material. [1] It sent the case back for the lower courts to decide whether the relators had sufficiently pleaded a violation under its standard. [1]

The June 2016 ruling is first a legal test. The Court set two conditions for implied false certification and a demanding standard for materiality. [1] Applying them to particular facts is work for courts and counsel.

For a health system’s compliance and technology leaders, our argument is that the ruling also moved False Claims Act risk into the claim data. The Court treated the codes and identifiers on a claim as specific representations about the service and who provided it. [1] The truth of those representations depends on records kept in other systems: licensure, credentialing, supervision and staffing.

The ruling then tied liability to how the government actually behaves. Materiality would turn on whether the government pays such claims when it knows of a violation. [1] In our reading, that made a provider’s record of what payers knew and did part of its defense.

We take the ruling in four parts, each a separate question a court would ask about a claim:

  1. What the claim says: which fields on a claim carry specific representations.
  2. What the claim leaves out: where the qualifying facts sit, and how a half-truth arises between systems.
  3. Whether the omission matters: how materiality is judged, and what evidence bears on it.
  4. Who knew: how the Act’s knowledge standard reaches an organization’s own records.

The four questions are distinct. The first concerns the content of the claim, the second the facts outside it, the third the payer’s decision, and the fourth the claimant’s state of mind. In our reading, a claim creates liability under the theory only when all four line up against the claimant.

After the four parts we cover what the ruling left undecided, how it plays out for different kinds of health organization, the strongest objections, and checks a compliance or technology leader can run. This is analysis of a court decision, not legal advice, and organizations should rely on counsel for their own position.

What the claim says: codes and identifiers as representations

The Court did not decide whether every claim implicitly represents that the billing party is legally entitled to payment. [1] It decided something narrower. The claims at issue did more than demand payment. They described specific services by code and specific providers by identifier. [1]

That reasoning gives each field on a claim a potential meaning beyond billing. A procedure code says what was done. A provider identifier, as the Court read the allegations, says what kind of professional did it. [1]

Which fields carry meaning

In our reading, the fields that most clearly carry representations are those that describe the service and the person who delivered it. The Court named payment codes for counseling services and provider identification numbers tied to job titles. [1]

By the same logic, other fields could carry meaning too: a modifier that signals supervision, a place-of-service code, or a rendering provider separate from the billing provider. The Court did not address those fields. Whether a court would treat them the same way depends on the program’s rules and the facts.

The point for a compliance leader is that billing data is not neutral. Each field that describes a service or a provider is a statement a court might read. The team that maps clinical events to claim fields is, in effect, drafting those statements.

How claims are assembled

In a health system that bills electronically, a claim is assembled rather than typed. A clinician documents care in the electronic health record. Coding staff or software assign codes. A billing system attaches provider identifiers from a master file and sends the claim, often through a clearinghouse.

Each step draws on a different system. The clinician’s credentials are in a credentialing database. The provider’s enrollment is in a payer file. The supervision relationship may be recorded only in a schedule or a policy. The claim combines them without checking that they agree.

That assembly line is where the Court’s reasoning bites, in our reading. The claim may say that a licensed professional provided a service when the underlying records, if anyone compared them, would show otherwise. Nobody intended a false statement, yet the claim makes one.

The identifier as a promise about a person

The Court gave weight to the allegation that staff used provider identification numbers corresponding to specific job titles. [1] An identifier attached to a claim links the service to a person with stated qualifications.

Health systems manage provider identifiers through enrollment and credentialing. When a professional’s license lapses, their supervision arrangement ends, or their role changes, the identifier on the claim may no longer match the facts. Keeping those records current is ordinary operations. After the ruling it was also a way to keep claims truthful.

Electronic claims and attestations

Providers that bill federal programs typically do so under enrollment terms and standard claim formats, in our understanding. The Court’s reasoning did not depend on any signed certification on the claim itself. [1] It rested on what the codes conveyed. In our reading, that means an organization cannot rely on the absence of an express certification to limit what its claims say.

Default mappings and charge masters

Billing systems rely on tables. A charge master links services to codes. A provider file links clinicians to identifiers. Rules in the billing system decide which identifier appears as rendering provider when a service involves more than one person.

Those tables are configuration, maintained by analysts and changed through tickets. A default that lists a supervising physician as the rendering provider, when a supervised clinician delivered the care, changes what the claim says. The Court’s reasoning makes such defaults more than technical choices, in our reading. [1]

A change log for billing tables is therefore a compliance record. It shows who changed a mapping, when and why. If a mapping later proves wrong, the log helps separate an honest error from a pattern someone knew about. That separation matters for the fourth part of this analysis.

What the representation does not cover

The Court was careful about scope. It declined to decide whether every claim implicitly represents that the billing party is legally entitled to payment. [1] Its holding applied at least where a claim makes specific representations and omissions make them misleading. [1]

That leaves a range of claims outside the holding’s clear core. A claim with only a generic payment request, and no field describing the service or provider, is not what the Court analyzed. How courts treat such claims is outside this article and should be assessed with counsel.

The Court also noted that the parties had assumed the 2009 amendments to the Act applied, even though some claims predated 2009, and it did not consider whether older conduct should be treated differently. [1] Small notes like that one show how closely the holding was tied to the case before the Court.

What the claim leaves out: where the half-truth arises

The second condition is an omission. The Court described half-truths as representations that state the truth only so far as it goes, while omitting critical qualifying information. [1] It gave common-law examples, including a seller who mentions two roads near a property but not a third that might bisect it. [1]

Applied to the case, the Court said anyone told that a social worker at a Massachusetts clinic provided individual counseling would probably conclude the clinic had complied with core program requirements. [1] Those included specialized training for counselors treating children and minimum qualifications for the job. [1]

The qualifying facts live elsewhere

In the Court’s example, the facts that made the claims half-truths were not on the claims. They were in staffing and licensing records. More generally such facts live in licensure records, supervision logs, staffing rosters and facility certifications. The Court’s example turned on staff qualifications and licensing requirements for mental health facilities. [1]

For a health system, that means the integrity of a claim depends on systems the billing office does not own. Human resources holds licenses. Medical staff services holds credentials. Clinical operations holds schedules and supervision plans. Each can drift from the others.

Linking billing to the records behind it

One response is to link the systems so that a claim cannot be released for a provider whose qualifying records are missing or expired. That is a design choice, not a legal requirement, and it has costs. False holds delay revenue, and the rules for what qualifies vary by program and state.

A lighter response is periodic reconciliation. A compliance team can compare billed services against the licensure and supervision records for the providers named on them, and investigate mismatches. The ruling did not prescribe either approach. Both follow from its focus on what the claim conveys and what it omits, in our reading. [1]

Satellite sites and supervision

The case involved a satellite facility, and the regulations the Court cited dealt with staff qualifications and supervision. [1] Satellite clinics, telehealth arrangements and staff working under another clinician’s supervision each add a place where the facts can change without the claims changing.

Those arrangements create more places for drift. A supervising clinician leaves, and the supervised staff continue to bill. A satellite opens before its staffing meets the program rules. The claims look the same as before. Under the ruling, what they omit may make them misleading.

Clinicians who cross state lines

Telehealth adds a licensing question the 2016 case did not raise. A clinician may be licensed in one state and see a patient located in another. Whether the service meets each program’s rules depends on state law and payer policy, which change.

For the analysis here, the point is structural. The claim will describe the service and the provider in the same fields as an in-person visit. The facts that qualify it, licensure where the patient is located, sit in yet another record. The same reconciliation logic applies, with one more field to check.

Contracted and temporary staff

Locum clinicians, agency staff and contracted therapists bill under arrangements that vary. Their credentials may be verified by an agency rather than the organization itself. The claim still names a provider and a service.

In our reading, relying on an agency’s verification does not change what the organization’s own claim says. The contract with the agency should give the organization access to the qualifying records and prompt notice of any change, so the organization can keep its claims accurate.

Unfavorable facts and favorable statements

The company argued that a misleading partial disclosure is fraudulent only when the first statement partially disclosed unfavorable information. The Court rejected that. [1] It cited the rule that a statement containing only favorable matters and omitting all unfavorable ones can be as false as one in which every fact is untrue. [1] A routine, clean-looking claim can still be a half-truth.

Who owns the reconciliation

Comparing claims with the records behind them crosses departments. Billing owns the claims. Medical staff services owns credentials. Human resources owns licenses for employed staff. Clinical leaders own supervision plans.

Without a named owner, the comparison falls between those groups. A compliance office can own the method and the reporting while each department owns its data. That division is a design choice. It should be written down so that, if questions arise later, the organization can show who was responsible for what.

Evidence that the comparison happened

A reconciliation program leaves records: the sample drawn, the mismatches found, the investigation of each, and the corrections made. Those records support the organization in two ways.

First, they show attention to the risk the Court described, which bears on knowledge. Second, they create a trail of corrections, including repayments where required. HHS-OIG’s guidance describes repayment of identified overpayments as a duty with its own deadline. [7] A reconciliation that finds problems and does not lead to repayment decisions would be hard to explain.

Facility rules and claim rules

Some requirements apply to a facility as a whole, such as staffing ratios or a licensed director. Others apply to each service, such as the qualifications of the person who delivered it. The regulations the Court cited covered both kinds: which types of clinicians a satellite facility must have on staff, and the licensing and supervision required for particular positions. [1]

In our reading, both kinds can make a claim misleading if the claim implies compliance and the facts are otherwise. Facility-level gaps may be harder to see from billing data, because nothing on the claim changes when a facility falls out of compliance. That makes survey findings and licensing correspondence important inputs to a compliance review.

Whether the omission matters: materiality as a record of behavior

The third part is where the Court set real limits. It said a misrepresentation about compliance must be material to the government’s payment decision to be actionable. [1] It described the standard as demanding and tied it to common-law ideas of what would affect a reasonable payer’s decision. [1]

What does not settle materiality

The Court listed things that are not enough. A requirement is not material merely because the government labels it a condition of payment. [1] It is not enough that the government would have the option to decline payment if it knew. [1] Materiality cannot be found where noncompliance is minor or insubstantial. [1]

The Court used an example from the government’s own argument. If a health services contract required American-made staplers, the government’s test would make an undisclosed use of foreign staplers a False Claims Act violation. [1] The Court said the Act does not adopt such an extraordinarily expansive view. [1]

What counts as evidence

The Court said proof of materiality can include evidence that the defendant knows the government consistently refuses to pay claims in the mine run of cases based on noncompliance with the requirement. [1] Conversely, payment of a particular claim in full despite actual knowledge of the violation is very strong evidence that the requirement is not material. [1] Regular payment of a type of claim despite actual knowledge, with no signaled change in position, is strong evidence too. [1]

Those sentences turn materiality into a question about behavior over time: what the payer knew, what it did, and whether it signaled a change. In our reading, the answers live in audit reports, payer correspondence, recoupment letters and survey findings.

Records a provider may need

A health system facing a claim may need to show what the government knew about a practice and how it responded. That record is spread across the organization: survey and certification findings, contractor audits, prepayment reviews, and letters from state Medicaid agencies.

Those records may be filed by department and by date rather than by requirement. Gathering them after a lawsuit begins is slow. A compliance office that indexes payer findings by requirement can answer the materiality question faster. That is our suggestion, not something the ruling required.

Materiality at the pleading stage

The Court rejected the argument that materiality is too fact-intensive for courts to dismiss cases before trial. [1] It said plaintiffs must plead their claims with plausibility and particularity under Federal Rules of Civil Procedure 8 and 9(b), for instance by pleading facts to support materiality. [1]

That footnote matters to defendants and to relators. A complaint that names a regulation and asserts it was material may not be enough. A complaint that alleges how the program treats violations of that regulation stands on firmer ground. How lower courts applied the footnote is outside the sources we checked.

State programs and federal money

The claims in the case went to MassHealth, the state Medicaid program, which is funded with federal money. [1] [3] The state’s own payment behavior therefore mattered to materiality. On remand, the Commonwealth appeared as amicus curiae. [3]

For a provider billing several state Medicaid programs, that creates variation. A requirement one state enforces strictly may be one another state pays through. Materiality could differ by program, in our reading, which makes program-by-program records more useful.

Thousands of requirements

The Court acknowledged the burden on billing parties. It said they are often subject to thousands of complex statutory and regulatory provisions. [1] It said that facing liability for violating any of them would hardly help defendants anticipate and prioritize compliance obligations. [1]

That observation supports a practical approach. An organization cannot monitor every requirement with equal intensity. It can rank requirements by how central they are to the services it bills and by how payers have treated violations. The ruling’s materiality factors offer a starting list for that ranking, in our reading. [1]

When the payer knows only part of the story

The Court’s strongest evidence against materiality involved payment despite actual knowledge. [1] Partial knowledge is harder. A payer may know that a provider had staffing problems at one site but not that claims from that site continued.

The First Circuit’s remand illustrates the point. It said that, at the pleading stage, it saw no evidence that the program had actual knowledge of the violations, as opposed to awareness of allegations. [3] A provider relying on payer knowledge would need records showing what the payer actually knew, rather than proof that some concern had been raised.

Who knew: the knowledge standard and an organization’s own records

The fourth part is knowledge. The Court described the Act’s scienter requirement as covering actual knowledge, deliberate ignorance of the truth or falsity of information, and reckless disregard of it. [1]

The Court tied knowledge to materiality. It said what matters is whether the defendant knowingly violated a requirement it knows is material to the government’s payment decision. [1] A defendant can know a requirement is material even if the government never called it a condition of payment. [1]

How an organization comes to know

Organizations learn through people and systems. A billing auditor finds that a provider billed without a current license. A hotline caller reports unsupervised staff. A credentialing analyst notices an expired certification. Each report is information that could later be cited as knowledge.

What the organization does next matters. A report that is logged, investigated and resolved shows attention. A report that sits unread may later be described as deliberate ignorance or reckless disregard. Which label a court would apply depends on the facts, and counsel should assess any specific case.

Overpayments and the clock

HHS-OIG’s general compliance guidance describes a separate duty. It says entities must report and repay Medicare and Medicaid overpayments by the later of 60 days after the overpayment was identified or the date a corresponding cost report is due. [7] It says an entity that identifies billing mistakes or noncompliance leading to an overpayment must repay to avoid False Claims Act liability. [7]

That duty links the fourth part of the ruling to everyday operations. Once a compliance review finds that claims were billed under a lapsed license or without required supervision, the organization holds knowledge. The repayment process becomes part of how it shows good faith.

Audits as knowledge

HHS-OIG’s guidance recommends regular reviews to keep billing and coding practices current and regular internal billing and coding audits. [7] It describes the guidance as voluntary and not binding. [7] Audits create knowledge, and knowledge creates duties. That is a reason to plan, before an audit begins, how findings will be escalated and resolved.

An organization might hesitate to audit for fear of what it will find. The ruling’s knowledge standard cuts against that. Reckless disregard covers a failure to look where looking was reasonable, in our reading. The safer course is to look and act. [1]

Knowledge across a corporate group

The case involved a facility owned and operated by a subsidiary of the company that petitioned the Court. [1] Health systems can be organized the same way, with hospitals, physician groups and clinics held in separate entities.

Which entity knew what, and when, can matter in a dispute. The Court did not address corporate knowledge across a group. In our reading, a group-wide compliance function that receives reports from every entity both helps and creates obligations: it can see patterns, and it can be said to have known them.

The guns example

The Court gave an example of knowledge without an express condition. If the government failed to specify that guns it orders must actually shoot, but the defendant knows the government routinely rescinds contracts when guns do not shoot, the defendant has actual knowledge. [1]

The Court added that, because a reasonable person would realize the imperative of a functioning firearm, a failure to appreciate the materiality of that condition would amount to deliberate ignorance or reckless disregard. [1] The health care equivalent, in our reading, is a requirement so basic that no reasonable provider could think it unimportant, such as a license to practice. Licensing and supervision sit close to that end of the range.

Designing escalation before it is needed

Knowledge becomes a problem when it arrives without a path. A coder notices that a clinician’s claims list a credential the clinician does not hold. If the coder does not know whom to tell, the information stays in one person’s head and in one system’s notes.

A written escalation path fixes that. It names who receives billing integrity concerns, how fast they must be reviewed, who decides whether claims must be held, and who decides whether a repayment review is needed. HHS-OIG’s guidance discusses compliance officers and reporting mechanisms as parts of a compliance program. [7]

Technology teams can support the path. A ticket category for billing integrity concerns, with required fields and an owner, creates a record of when the organization learned something and what it did. That record is evidence in both directions, which is why its design deserves care.

Holding claims while facts are checked

When a concern is credible, an organization may choose to hold affected claims until the facts are checked. Holding claims delays revenue. Releasing them while a known question is open may later be described as reckless disregard, depending on the facts. [1]

The choice is a judgment for compliance and counsel. The technology question is whether the billing system can hold claims for a specific provider, site or service quickly, and release them in a controlled way. A system that can only hold everything or nothing makes the judgment harder.

What the ruling left undecided

The opinion settled a framework and left several questions open. Each leaves room for argument in later cases, and each is a reason not to over-read it.

Liability in this case. The Court vacated the First Circuit’s judgment and remanded for reconsideration of whether the relators had sufficiently pleaded a violation. [1] It did not find the company liable.

Generic claims. It did not decide whether every claim implicitly represents legal entitlement to payment. [1] Claims with less specific content are outside its clear holding.

The weight of particular evidence. It listed kinds of evidence that bear on materiality but set no formula for weighing them. [1] Courts would apply the factors to each record.

The application to particular fields. It discussed payment codes and provider identification numbers. [1] It did not address other fields, modifiers or attestations. Their treatment depends on later cases and program rules.

For a compliance leader, those gaps argue for a conservative reading of what claims convey and a careful record of how payers behave. They do not support assuming that any particular field is safe.

How the ruling plays out across health organizations

The four parts apply to anyone submitting claims to federal programs, but they land differently by type of organization.

Health systems and hospitals

A large system bills under many provider identifiers, across facilities, departments and employed physician groups. Its exposure is breadth: many fields, many systems and many people whose qualifications must match what the claims say. Its advantage is scale. It can afford integrated credentialing and billing systems and a dedicated audit team.

Behavioral health and ambulatory networks

The case itself involved a behavioral health facility with satellite sites. [1] Behavioral health relies on varied license types and supervision rules, which differ by state. Ambulatory networks open and close sites and move staff between them. Both have more points where the claim and the facts behind it can drift apart.

Life sciences and other indirect participants

The Act reaches anyone who knowingly presents, or causes to be presented, a false claim. [1] A manufacturer or supplier that does not submit claims for patient services can still affect claims others submit. Their exposure under the implied certification theory depends on facts beyond this analysis, and counsel should assess it.

State Medicaid agencies

Public agencies sit on the other side. In our reading, a state Medicaid agency’s payment and enforcement behavior is evidence of materiality under the ruling. [1] An agency that knows of a widespread violation and keeps paying may weaken later cases. An agency that wants a requirement enforced has reason to act consistently and to record that it does.

Public hospitals and county clinics

Government-owned hospitals and county behavioral health clinics bill Medicaid and Medicare like other providers. The same four questions apply to their claims. Their records may sit in public systems subject to records laws, which can make them easier for others to obtain.

A county that operates clinics and also administers parts of a public health program may hold knowledge in two roles. Keeping clear records of which office knew what, and in which capacity, is part of managing that dual position, in our reading.

Objections to this reading

Four objections deserve an answer. The first three are numbered below, and the fourth follows them.

  1. The ruling made liability harder, not easier. In part it did. The Court rejected the government’s broad materiality test and called the standard demanding. [1] Our argument does not depend on more liability. It depends on where the evidence sits. A demanding materiality test makes the payer’s behavior and the claim’s content more important, and both are records.
  2. Claims are submitted by software, not people. Much billing is automated. The Act asks whether a person or entity knowingly presented a false claim. [1] Automation does not remove the organization’s knowledge of its own records. It can make that knowledge easier to show, because systems keep logs of what they knew.
  3. This is a compliance matter, not a technology one. The legal judgments belong to counsel and compliance. The records that answer the four questions are kept in technology systems, and the links between them are designed by technology teams. Both functions own part of the answer.

A limit on our argument should be stated. The ruling decided a pleading question and sent the case back. [1] It did not decide that the company was liable, and nothing here should be read as saying it was.

A fourth objection is cost. Linking billing to credentialing, indexing payer findings and building escalation paths take money and staff. The ruling does not require any of it. [1] Our answer is that each step also serves ordinary revenue integrity and payer audits. The marginal cost of designing them with the four questions in mind is small compared with building them twice.

Checks a compliance or technology leader can run now

These checks follow from the ruling’s structure. They are good practice that follows from it, not requirements stated in this form. Each organization should confirm its obligations with counsel.

The claim

  • List the claim fields that describe a service or a provider, and name the system and owner that supplies each one.
  • Confirm how provider identifiers on claims are updated when a license, role or supervision arrangement changes.

The records behind it

  • Confirm that licensure, credentialing and supervision records can be compared with billed services for a sample period.
  • For satellite and telehealth sites, confirm that staffing and supervision records meet each program’s rules before billing begins.

The payer’s behavior

  • Keep payer audit findings, recoupment letters and survey results indexed by the requirement they concern.
  • Record, by program and state, how the payer has treated known violations of the requirements that matter most to your services.

Knowledge

  • Confirm that the billing system can hold claims for a specific provider, site or service, and that holds and releases are logged.
  • Confirm that changes to charge master, provider file and rendering-provider rules are logged with the requester and reason.
  • Confirm that hotline reports and audit findings about billing reach compliance within a set time, with a named owner.
  • Confirm that identified overpayments enter a tracked repayment process with dates recorded.

With hindsight

The case returned to the First Circuit. On November 22, 2016, that court applied the Supreme Court’s guidance and again found that the relators’ complaint sufficiently stated a claim. [3] It reversed the district court’s dismissal and remanded for further proceedings. [3]

The First Circuit pointed to the centrality of the licensing and supervision requirements to the program. [3] It said that, for purposes of the motion to dismiss, it saw no evidence that MassHealth continued to pay claims despite actual knowledge of the violations. [3] That reasoning used the Supreme Court’s test as written: what the payer knew and did. [1] [3]

The cost of each false claim also rose that summer. On June 30, 2016, the Justice Department published an interim final rule adjusting civil monetary penalties for inflation under the Bipartisan Budget Act of 2015. [4] For the False Claims Act, the adjusted range was a minimum of $10,781 and a maximum of $21,563 per claim. [4]

Those amounts applied to civil penalties assessed after August 1, 2016, whose associated violations occurred after November 2, 2015. [4] The Supreme Court’s June 16 opinion had described penalties of up to $10,000 per false claim under the previous figures. [1]

The Act then turned toward cybersecurity. On October 6, 2021, the Justice Department announced a Civil Cyber-Fraud Initiative to use the False Claims Act against cybersecurity-related fraud by government contractors and grant recipients. [5]

The department said it would pursue entities or individuals that knowingly provide deficient cybersecurity products or services, knowingly misrepresent their cybersecurity practices, or knowingly violate obligations to monitor and report incidents and breaches. [5] In our reading, the second of those is an implied certification problem in a new setting: a claim for payment that says something about security practices the facts do not support.

For health organizations, that matters where they hold federal contracts or grants with security terms. A research hospital or academic medical center may be both a provider billing federal programs and a grant recipient. The initiative’s reach depends on the terms of each award. [5]

The qui tam mechanism itself was challenged. On September 1, 2026, the Eleventh Circuit decided an appeal from a Florida district court ruling that had held the Act’s qui tam provisions unconstitutional under the Appointments Clause. [6] The court held that relators are not officers of the United States because they do not occupy a continuing position established by law. [6]

The Eleventh Circuit joined other circuits in holding that the qui tam provisions do not violate the Appointments Clause. [6] It vacated the dismissal and remanded for the district court to consider the defendants’ Take Care Clause and Vesting Clause arguments. [6] As checked on 2026-11-16, those questions were sent back to the district court by that opinion; we did not review later filings.

HHS-OIG’s general compliance guidance now describes the Act in terms that echo the ruling’s knowledge standard. It says knowing includes actual knowledge, deliberate ignorance and reckless disregard, and that entities cannot avoid liability by deliberately ignoring inaccuracies in their claims. [7]

So what held up? The ruling’s structure did. Claims that describe specific services can carry implied representations, and materiality turns on the payer’s actual behavior. [1] [3] The First Circuit’s remand shows the test applied as the Court wrote it. [3]

What changed is the setting. The 2021 initiative said the Justice Department would use the Act against cybersecurity-related fraud by contractors and grantees. [5] The 2026 appellate ruling left the qui tam mechanism in place in that circuit, with other constitutional arguments still to be heard. [6] Organizations should follow those questions with counsel.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • False Claims Act
  • implied certification
  • Medicaid
  • materiality
  • credentialing
  • billing compliance