.

SIU Spotlight

The Age of Automated Fraud: Defending Against Documentation Cloning and AI-Generated Claims

May 15, 2026

by Ariel C. Brownstein

For years, healthcare payers have treated note cloning—the practice of copying and pasting electronic health record (EHR) text—as a primary red flag in fraud, waste, and abuse (FWA) investigations. Today, as the industry races to embrace Artificial Intelligence (AI) for documentation, the threat of "cloning" is not disappearing; it is simply evolving. For insurance carriers facing healthcare fraud costs estimated to exceed $400 billion annually in the U.S., understanding this new and evolving technological risk is paramount to effective claims denial and successful defense litigation

The core issue with cloned documentation is its immediate challenge to the medical necessity of billed services. When medical records contain identical or near-identical entries across multiple dates of service, the documentation cannot support the premise that unique, individualized care was provided at each encounter. This practice undermines the credibility of the entire record.

Traditional copy-and-paste charting, where clinicians simply copy-forward prior entries or borrow from templates, was quickly identified by the Centers for Medicare & Medicaid Services (CMS) and the Office of Inspector General (OIG) as a priority for audit and enforcement. Its misuse often results in a form of fraud known as up-coding—the insertion of false or irrelevant details to justify a higher, more expensive level of service than was actually rendered. Simply put, manufactured records support inflated billing.

Cloning 2.0: AI and the New Red Flags

The rapid adoption of AI-assisted documentation tools presents carriers with a new, but strikingly familiar, compliance pitfall. Just as a keyboard shortcut once generated a suspiciously repetitive note, a sophisticated machine learning algorithm can now produce a grammatically flawless but equally generic summary.

Insurance carriers must equip claims auditors with a new playbook for identifying these high-tech red flags:

  • Repetitive and Boilerplate Phrasing: Like cut-and-paste, AI tools tend to reuse stock language verbatim—for instance, identical descriptions of a patient's presentation across many different encounters. The presence of uniform, verbose, or overly formal language that clashes with an experienced auditor's knowledge of a physician's typical "voice" should raise suspicion. These generic statements does not reflect individual patient encounters, creates the assumption that the narrative was manufactured to support, higher E/M coding and supports the appearance of a systematic inflation by a provider, not an isolated error.
  • Overly Complete Documentation: A hallmark red flag for potential upcoding is extreme documentation thoroughness. Unlike human clinicians, who focus on relevant positives and negatives, AI systems frequently generate exhaustive, boilerplate reviews of systems. Such documentation can misrepresent the scope of the encounter, creating the appearance of higher-level services and automatically inflating the reported E/M code—despite no corresponding increase in clinical work. An example of this would be a patient presenting with a sore throat and congestion, but the note documents a 14-system Review of Symptoms (ROS), all marked negative. A routine upper respiratory complaint does not clinically justify a full multi-system ROS. This level of detail artificially supports a higher E/M level without corresponding medical necessity.
  • Internal Inconsistencies: Because AI relies on patterns, it can fail to reconcile contradictory information or carry forward fabricated or outdated details. For instance, one section of an AI-generated note might state "no extremity pain," while another later mentions "episodes of upper extremity discomfort". These internal contradictions are destructive to a record's credibility and are prime targets for counsel in deposition.
  • Metadata Trails: Crucially, the technology that enables AI documentation also leaves an audit trail. Carriers must leverage the power of discovery to review system logs and timestamps that reveal when AI tools were used to generate text. This metadata can prove the extent of a provider's reliance on automated shortcuts, flagging instances of potential overreliance.

Fighting Fire with Fire: The Carrier's AI Defense

The growing sophistication of provider fraud demands that insurance carriers evolve beyond static, rules-based fraud detection to advanced analytical models. The best defense against AI-driven fraud is often the strategic use of defensive AI.

  • Carriers must transition to modern FWA prevention strategies by:
  • Pre-Payment FWA Preventive Analytics: Moving beyond traditional post-pay audits, carriers are now leveraging machine learning models to score and flag claims for high-risk behavior before adjudication. This shift prevents the improper payment from ever being made.
  • Leveraging Natural Language Processing (NLP): NLP is essential for analyzing the unstructured data in medical records, specifically clinical notes. These tools can scan millions of provider notes to detect the subtle anomalies that human auditors might miss, such as:
    • Identification of repetitive and cloned phrases across a provider's patient roster.
    • Flagging medical codes that do not align with the narrative diagnosis or description in the note.
  • Predictive Behavioral Modeling: AI systems can track a provider's historical billing and documentation patterns, automatically identifying statistically significant deviations from their peers. When a provider suddenly increases their volume of complex E/M codes (a classic up-coding indicator) or exhibits unusual service combinations, the system flags the provider as a high-risk outlier for focused investigation.
  • Network Link Analysis: Advanced analytics can uncover collusive networks of providers who might be sharing patients or services to perpetrate fraud.

In conclusion, the ultimate lesson for carriers is that documentation is not merely about filling space; it is about telling the patient's distinctive and current story. Anything—whether a copy-paste command or a machine learning algorithm—that dilutes that unique story and creates repetitive or over-documented records is a pathway to claims failure and potential fraud. Insurance carriers must treat AI documentation with the same rigorous scrutiny once reserved for chart cloning, updating audit protocols to focus on individualized clinician attestation, customization, and metadata that reveals overreliance on automation.

Firm Highlights

Thought Leadership

Two Tracks, No Preclusion: Ohio Supreme Court Preserves Separate Damages Claims After Chapter 2506 Appeals

The Supreme Court of Ohio has clarified that an administrative appeal under Ohio Revised Code Chapter 2506 does not bar a separate action for damages and declaratory relief that could not have been pursued in the administrative appeal. The Ohio Supreme Court considered Sheetz, Inc. v. Centerville (2026-Ohio-3531) as a result of a certified question from the Southern District of Ohio. The question was whether Sheetz, the gas station/convenience store brand, was barred from seeking damages in a separate action since damages were not sought in their administrative appeal. Ultimately, the Ohio Supreme Court ruled that res judicata does not bar a separate action for damages after ruling on an administrative appeal because R.C. Chapter 2506 is limited to judicial review and cannot grant affirmative relief. The case arose after Centerville’s city council rejected a site plan proposed by Sheetz, Inc. that had received unanimous approval from the City’s planning commission. Sheetz filed an administrative appeal pursuant to R.C. 2506 in the Montgomery County Court of Common Pleas, and two months later filed a complaint for damages and declaratory relief under 42 USC § 1983 as a takings action with the city, city council, and other objectors as improper takings and a violation of due process, as well as interference with business and contractual relationship. The city and city council removed the § 1983 action for damages to federal court. Montgomery County Court of Common Pleas reversed the city council’s denial, and allowed the Sheetz project to move forward. Upon that ruling, the federal court issued a show-cause order questioning whether the § 1983 action was barred by the doctrine of res judicata via claim preclusion (which includes all theories of recovery).  Sheetz argued that Ohio courts of common pleas do not have authority to award damages or declaratory relief as party of the R.C. Ch. 2506 appeal, therefore res judicata could not be triggered to apply to the § 1983 action. Additionally, Sheetz moved to certify the issue to the Ohio Supreme Court, citing differing results between the second and sixth districts on this same issue. Centerville approached the question, not from a claim preclusion standpoint, but from the holding in Grava v. Parkman, Twp which states that a final judgment rendered on the merits bars all subsequent action based on the same transaction or occurrence.  In yet another approach, an objector argued that claim preclusion was satisfied because Sheetz could have raised its damages claims in the administrative appeal – Sheetz disagrees. In their analysis, the Supreme Court of Ohio broke down the elements of a claim preclusion analysis: 1) a prior final, valid decision on the merits by a court of competent jurisdiction; (2) a second action involving the same parties, or their privies, as the first; (3) a second action raising claims that were or could have been litigated in the first action; and (4) a second action arising out of the transaction or occurrence that was the subject matter of the previous action. The Court held that R.C. Ch. 2506 does not permit a party to argue damages as R.C. Ch. 2506 limits the common pleas jurisdiction as if it were sitting on appeal, and therefore can only affirm, reverse, vacate, or modify the appealed order, or can remand the case to the administrative body. Further, the Court held that Grava’s conclusion that a final judgment precludes additional litigation for different relief is inapplicable under this fact pattern because it was meant only to apply to those matters in which the plaintiff brings the exact same case twice, but for new relief. The Court found Grava was inapplicable because Sheetz could have requested damages or declaratory relief in the R.C. 2506 appeal. Therefore, Grava would be nothing more than dicta if it even did apply. Going further, the Ohio Supreme Court disavowed Sixth Circuit precedent which, in reliance on Grava and other district court decisions, permitted an owner to seeking relief under 42 U.S.C. § 1983 alongside an administrative appeal. See Moore v Hiram Twp., 988 F.3d 353 (6th Cir.2021). The Ohio Supreme Court found that the Sixth Circuit had disregarded a critical decision in Community Concerned Citizens, Inc. v. Union Twp. Bd. of Zoning Appeals, 1993-Ohio-115, which clearly held that a R.C. Ch. 2506 appeal cannot be combined with a complaint seeking other claims for relief. Id. at ¶ 11. To that end, the Ohio Supreme Court has determined that the decisions Moore relied on (outside of Grava) are no longer good law, and that Moore was wrongly decided. The decision draws a clear procedural boundary: Chapter 2506 provides judicial review of an administrative decision, not a forum for independent claims seeking affirmative relief. Although Grava may place claims arising from a single transaction within the potential scope of claim preclusion, those claims are not barred unless the complete claim-preclusion test is satisfied. Because Sheetz could not have pursued damages or declaratory relief in its Chapter 2506 appeal, the separate action was not precluded. The remaining question for practitioners looking to apply or defend against this exception is when does the statute of limitations begin to run on damages and declaratory relief claims related to an administrative decision on appeal? A takings action in federal court has a 2-year statute of limitations, or as a state claim, 4 years (like the other tortious claims raised therein). Correlating this case with others, an administrative appeal will not likely toll the statute of limitations on claims based on a final decision by a municipal authority. Therefore, practitioners should look for these cases to be brought simultaneously.

Thought Leadership

The Search-Incident-to-Arrest Doctrine Does Not License Strip Searches

In Beatty v. Gardner, No. 25-2860 (3d Cir. Sept. 16, 2026), Kyle Beatty sued police officers Clinton Gardner and Calvin Irvin under 42 U.S.C. § 1983 after they stopped, arrested, and searched him three times during a drug investigation in Williamsport, Pennsylvania. The officers initially smelled marijuana coming from the car in which Beatty was sitting and observed marijuana residue, giving them probable cause to arrest him. Beatty consented to the first pat-down, and the second search was conducted incident to his lawful arrest; neither search uncovered weapons or contraband. The officers then transported Beatty to the police station solely to strip-search him, but the strip search also revealed nothing. The District Court granted the officers summary judgment, concluding that the initial stop, arrest, and first two searches were reasonable and that qualified immunity protected the officers from liability for the strip search. The Third Circuit affirmed, but held that the strip search itself violated the Fourth Amendment. The court concluded that the search-incident-to-arrest doctrine does not automatically permit officers to strip-search an arrestee outside the jail or prison setting. Because strip searches are highly intrusive and the traditional justifications for searches incident to arrest (officer safety and preservation of evidence) did not justify the search of Beatty, the officers generally needed either the arrestee’s consent, exigent circumstances, or a warrant supported by probable cause to believe that a search beneath the clothing would reveal weapons, contraband, or evidence. Here, the officers had none of those justifications. Nevertheless, the court held that qualified immunity barred damages liability because, at the time of the search, the right against a warrantless strip search of an arrestee outside the institutional setting was not clearly established by Supreme Court or Third Circuit precedent. The court likewise upheld qualified immunity on Beatty’s First Amendment retaliation claim and affirmed summary judgment for the officers.

Thought Leadership

Pennsylvania Supreme Court to Review Whether Legal Malpractice Claims May Be Recast as Breach of Contract Claims

The Pennsylvania Supreme Court recently granted allowance of appeal to consider whether a plaintiff may pursue a breach of contract claim against an attorney based on allegations that the attorney failed to provide competent legal services. The issue is significant in professional liability litigation because it concerns whether a plaintiff may avoid the statute of limitations applicable to professional negligence claims by characterizing the alleged misconduct as a breach of contract. Antoine Poteat retained attorneys Gary Asteak and Nino V. Tinari to represent him in a criminal matter. After his conviction was subsequently overturned through a Post Conviction Relief Act proceeding, Poteat filed suit against his former attorneys alleging that they breached their retainer agreements by failing to provide competent legal services. The attorneys argued that the claims sounded in professional negligence, rather than breach of contract, and were therefore time-barred. The trial court dismissed Poteat’s complaint, but the Superior Court, sitting en banc, reversed. The Superior Court held that the gist-of-the-action doctrine did not bar Poteat’s breach of contract claim because the alleged failure to provide competent legal services could constitute a breach of the parties’ agreement. The Court further held that a legal-services agreement contains an implied duty requiring an attorney to provide competent legal services, even where the agreement does not contain an express provision requiring such services. The Pennsylvania Supreme Court granted review in July 2026 and will consider whether the Superior Court’s decision conflicts with Pennsylvania precedent distinguishing contract and tort claims, including Bruno v. Erie Insurance Co. The Supreme Court will also address whether a plaintiff may maintain a breach of contract claim based on an implied duty to provide competent legal services without identifying a specific contractual provision that was breached. The Supreme Court’s decision could have significant implications for professional liability litigation in Pennsylvania, particularly where plaintiffs seek to characterize claims arising from alleged professional negligence as contractual claims.