Content Type: Article

  • European Union calls for evidence on simplifying medical device rules

    European Union calls for evidence on simplifying medical device rules

    ARTICLE / CLIENT ALERT

    European Union calls for evidence on simplifying medical device rules

    September 18, 2025

    Read time: 3 min

    Key takeaways
    Overview

    On September 8, 2025, the European Commission issued a “Call for Evidence” about ways to simplify the current European medical device and in vitro medical device regulations.

    In depth

    On September 8, 2025, the European Commissioned issued a “Call for Evidence” on the EU Medical Device Regulation 2017/745 (MDR) and the EU In Vitro Diagnostic Medical Device Regulation 2017/746 (IVDR).

    The European Commission acknowledges that while the regulations have been in place for several years, implementation has been challenging. The higher demands of both the MDR and IVDR have also led to the risk of shortages and the disappearance of critical devices from the market. At the same time, the transitional periods have been extended several times.

    Between December 2024 and March 2025, the European Commission conducted an evaluation of both regulations, and there have been multiple calls for a simplification of the framework.

    The Call for Evidence notes that while the overall objectives of the MDR and IVDR are shared by most stakeholders, there are concerns about: sufficiently predictable timelines for certification; diverging practices across the EU that are undermining the efficiency of obtaining CE marking; and, disproportionate costs relative to the risks presented by these devices.

    In this context, the Commission is considering an initiative to simplify and streamline both regulations to: reduce the administrative burden; enhance the predictability and cost efficiency of certification; enable further digitalisation; streamline procedures; and better align the framework with other legislation.

    This proposal will be widely welcomed. However, the proposed changes must be considered in the context of:

    • The UK’s plans to broadly align medical and in vitro medical device law with the EU MDR and IVDR
    • The new EU AI Act that imposes a dual layer of certification upon devices that are AI systems or have AI systems as safety components

    This Call for Evidence allows stakeholders, both in the EU and beyond, to give submissions that will be considered when preparing changes to the regulations.

    The Call for Evidence is open until 6 October, 2025. Feedback will be published on the website of the European Commission.

    The McDermott Will & Schulte team are advising clients and stakeholders on a wide range of regulatory matters relating to the MDR and IVDR.

    If you would like to contribute to this Call for Evidence, please access the link here or reach out to the authors for support on aspects to include in any submission.

    Authors

    Sharon Lamb

    Partner

    London – 22 Bishopsgate

    Bella North

    Senior Associate

    London – 22 Bishopsgate

    More insights

  • CMS launches $50 billion Rural Health Transformation Program

    CMS launches $50 billion Rural Health Transformation Program

    CLIENT ALERT / US POLICY

    CMS launches $50 billion Rural Health Transformation Program

    September 16, 2025

    Read time: 9 min

    Key takeaways
    Overview

    Public Law 119‑21 (also known as the One Big Beautiful Bill Act) created a $50 billion Rural Health Transformation (RHT) Program to strengthen healthcare across the rural United States. The $50 billion fund will be allocated to approved states, with 50% of the funding to be distributed equally across all states that have approved applications. The other 50% will be distributed by the Centers for Medicare & Medicaid Services (CMS) based on a variety of factors. To access the RHT Program funds, states must submit a one-time application to CMS. On September 15, 2025, CMS released a notice of funding opportunity (NOFO) with application details. Applications are due by November 5, 2025, with awards to be decided by December 31, 2025.

    While only states are eligible to apply, many states are soliciting feedback and comments from stakeholders on how RHT Program funds should be used. Interested stakeholders should provide input to the agency that is responsible for the application in their state.

    In depth

    Background

    As part of Public Law 119‑21, US Congress established the $50 billion RHT Program to help rural communities reimagine their healthcare delivery systems and improve health outcomes.

    The RHT Program seeks to advance five strategic goals outlined in Public Law 119‑21:

    Make rural America healthy again
    Support rural health innovations and new access points to promote preventative health and address root causes of diseases. Projects will use evidence-based, outcomes-driven interventions to improve disease prevention, chronic disease management, behavioral health, and prenatal care.
    Sustainable access
    Help rural providers become long-term access points for care by improving efficiency and sustainability. With RHT Program support, rural facilities work together – or with high-quality regional systems – to share or coordinate operations, technology, primary and specialty care, and emergency services.
    Workforce development
    Attract and retain a high-skilled healthcare workforce by strengthening recruitment and retention of healthcare providers in rural communities. Help rural providers practice at the top of their license and develop a broader set of providers to serve a rural community’s needs, such as community health workers, pharmacists, and individuals trained to help patients navigate the healthcare system.
    Innovative care
    Spark the growth of innovative care models to improve health outcomes, coordinate care, and promote flexible care arrangements. Develop and implement payment mechanisms incentivizing providers or accountable care organizations to reduce healthcare costs, improve quality of care, and shift care to lower cost settings.
    Tech innovation
    Foster use of innovative technologies that promote efficient care delivery, data security, and access to digital health tools by rural facilities, providers, and patients. Projects support access to remote care, improve data sharing, strengthen cybersecurity, and invest in emerging technologies.

    Although the goal of the RHT Program is to effectuate impact on rural communities, per CMS FAQs, the NOFO does not include specific restrictions on which provider organizations may be eligible to receive funding. Some stakeholders have expressed concerns that the funds may go to providers that are not located in rural areas or that only nominally serve rural communicates.

    Funding

    Funding allocation

    The RHT Program provides $50 billion in funding to be allocated to approved states:

    • CMS will distribute 50% of the funding ($25 billion) equally among all approved states. This suggests approved states will receive the same amount from this pool regardless of the size of their rural population, the number of rural health facilities in the state, or other factors. CMS refers to this funding in the NOFO as “baseline funding.”
    • CMS will allocate 50% of the funding ($25 billion) based on a variety of factors, including the content and quality of the state’s application and rural factors. In the NOFO, CMS refers to this funding as “workload funding.” CMS developed a point scoring methodology for workload funding in the NOFO that includes data driven metrics (based on rural facility and population factors), initiative-driven metrics (based on programmatic initiatives outlined in the state’s application and subsequent follow-through), and state policy metrics. CMS will recalculate each approved state’s technical score and corresponding workload funding amount for each subsequent budget period based on the information and data the approved state provides in the required annual reporting each year. A state’s rural facility and population score will only be calculated once as part of the application process.

    The funding will be allocated over five fiscal years, with $10 billion of funding available each fiscal year, beginning in fiscal year 2026 and ending in fiscal year 2030.

    Funding eligibility

    Only the 50 US states are eligible to receive an RHT Program award. The District of Columbia and US Territories are not eligible. Local governments, hospitals, universities, nonprofits, federally recognized Tribes, and individuals may not apply.

    Use of funds

    States must use RHT Program funds for three or more of the approved uses:

    • Prevention and chronic disease: Promoting evidence-based, measurable interventions to improve prevention and chronic disease management.
    • Provider payments: Providing payments to healthcare providers for the provision of healthcare items or services, subject to the restrictions described in the NOFO.
    • Consumer technology solutions: Promoting consumer-facing, technology-driven solutions for the prevention and management of chronic diseases.
    • Training and technological assistance: Providing training and technical assistance for the development and adoption of technology-enabled solutions that improve care delivery in rural hospitals, including remote monitoring, robotics, artificial intelligence, and other advanced technologies.
    • Workforce: Recruiting and retaining clinical workforce talent to rural areas, with commitments to serve rural communities for a minimum of five years.
    • IT advances: Providing technical assistance, software, and hardware for significant information technology advances designed to improve efficiency, enhance cybersecurity capability development, and improve patient health outcomes.
    • Appropriate care availability: Assisting rural communities to right size their healthcare delivery systems by identifying needed preventative, ambulatory, pre-hospital, emergency, acute inpatient care, outpatient care, and post-acute care service lines.
    • Behavioral health: Supporting access to opioid use disorder treatment services (as defined in Social Security Act § 1861(jjj)(1)), other substance use disorder treatment services, and mental health services.
    • Innovative care: Developing projects that support innovative models of care that include value-based care arrangements and alternative payment models, as appropriate.
    • Additional uses: Uses designed to promote sustainable access to high-quality rural healthcare services, as determined by the CMS administrator, including:
      • Capital expenditures and infrastructure: Investing in existing rural healthcare facility buildings and infrastructure, including minor building alterations or renovations and equipment upgrades to ensure long-term overhead and upkeep costs are commensurate with patient volume, subject to restrictions in the NOFO.
      • Fostering collaboration: Initiating, fostering, and strengthening local and regional strategic partnerships between rural facilities and other healthcare providers to promote quality improvement, improve financial stability of rural facilities, and expand access to care.

    Prohibited uses of funding

    The NOFO outlines unallowable costs, including the following:

    • Funding cannot be used for new construction. This prohibition includes supplanting funding for in-process or planned construction projects or directing funding toward new construction builds. Renovations or alterations are allowed if they are clearly linked to program goals in, and in accordance with, the requirements and limitations set forth in the NOFO. Capital expenditures and infrastructure funding cannot exceed 20% of the total funding that CMS awards to a state in a given budget period.
    • Funding cannot be used to replace payment for clinical services that could be reimbursed by insurance or another form of health coverage. CMS will not approve proposed initiatives that would pay for clinical services where payment for the services is available from another source of coverage, including where the initiative would increase the payment amount available from the other source of coverage. If a state plans to fund direct healthcare services, it must justify in its application why such services are not already reimbursable, how the payment will fill a gap in care coverage (such as uncompensated care or services not covered by insurance), and/or how such funding will transform the current care delivery model. Funding for provider payments cannot exceed 15% of the total funding that CMS awards to a state in a given budget period
    • Funding cannot be used for clinician salaries or wage supports for facilities that subject clinicians to noncompete contractual limitations.
    • No more than 5% of the total funding that CMS awards to a state in a given budget period can support the replacement of an electronic medical record (EMR) system if a previous HITECH-certified EMR system is already in place as of September 1, 2025.
    • To the extent a state seeks to implement a “rural tech catalyst fund initiative” or similar initiative for accelerating technology adoption, as described in the NOFO, funding for such initiative cannot exceed the lesser of 10% of total funding awarded to a state in a given budget period or $20 million. Funding for such an initiative is subject to all restrictions and requirements described in the NOFO.

    State application process

    CMS released the NOFO, including application instructions, for the RHT Program on September 15, 2025. Application submissions are due by November 5, 2025. There is only one opportunity to apply for funding and one application period for the RHT Program. Awards will be decided by December 31, 2025.

    To assist states with the application process, CMS has made available an FAQs document. The agency also will hold introductory webinars on September 19 and 25, 2025, and will continue to engage with states during the open application period to answer any questions. More details regarding webinars are available on CMS’s website.

    Each state must separately apply for its own funding. However, proposed initiatives could include multistate collaborations, such as regional networks or complementary workforce initiatives. States also may consult and involve partners, such as universities, local health departments, community-based organizations, and provider associations, in designing and implementing the planned activities proposed in the application, and may sub-award or contract RHT Program funds to such partners for various activities. Stakeholders interested in participating in their state’s application process should contact the state agency (or agencies) responsible for the application. The specific state agency may vary from state to state and may require some effort to identify. For example, some states have tasked the governor’s office with the application and others have tasked the state health services agency.

    Next steps for stakeholders

    As states prepare their RHT Program applications, many states are soliciting input from stakeholders and seeking feedback on how the state, if awarded, should use the federal funding to transform rural healthcare. Interested stakeholders should provide input to their applicable state agency.

    We will continue to monitor updates to the RHT Program. Please contact the authors of this article or your regular McDermott Will & Schulte lawyer with any questions.

    Authors

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Lisa Mazur

    Partner

    Chicago

    Jayda Greco

    Partner

    Chicago

    Grayson I. Dimick

    Associate

    Washington, DC

    Brigit Dunne

    Associate

    Chicago

    More insights

  • AI in employer-sponsored group health plans: Legal, ethical, and fiduciary considerations

    AI in employer-sponsored group health plans: Legal, ethical, and fiduciary considerations

    ARTICLE / CLIENT ALERT

    AI in employer-sponsored group health plans: Legal, ethical, and fiduciary considerations

    September 15, 2025

    Read time: 10 min

    Key takeaways
    Overview

    The ubiquity of artificial intelligence (AI) extends to tools used by, and on behalf of, employer-sponsored group health plans. These AI tools raise no shortage of concerns. In this article, we analyze key issues that stand out as requiring immediate attention by plan sponsors and plan administrators alike.

    In depth

    AI background

    On November 30, 2022, OpenAI released ChatGPT for public use. Immediately a consensus emerged that something fundamental had changed: For the first time an AI with apparent human – or at least near-human – intelligence became widely available. The release of an AI into the proverbial wild was not welcomed in all quarters. An open letter published in March 2023 by the Future of Life Institute worried that “AI labs [are] locked in an out-of-control race to develop and deploy ever more powerful digital minds that no one – not even their creators – can understand, predict, or reliably control.” Three years later, that concern may seem overstated. AI systems are now ubiquitous; the world has changed in ways that are so fundamental as to be unfathomable; and the true impact of AI may take decades to fully grasp.

    One of the many domains that AI will revolutionize is the workplace, which our colleagues, Marjorie Soto Garcia, Brian Casillas, and David P. Saunders, have previously addressed (see their presentation, “AI in the Workplace: How State Laws Impact Employers,” which considers the use of AI in human resources and workplace management processes). Marjorie and Brian had previously defined the various types of AI and their deployment in their article “Risk Management in the Modern Era of Workplace Generative AI,” which we recommend reading for helpful context. In this client alert, we examine an even narrower, though nevertheless critically important, subset of AI in the workplace: how AI affects employer-sponsored group health plans.

    Employer-sponsored group health plans are a central feature of the US healthcare landscape, covering more than 150 million Americans. These plans exist at the intersection of healthcare delivery, insurance risk pooling, and employment law. AI has emerged as a transformative technology in health administration. AI-enabled tools promise improved efficiency, cost savings, better clinical outcomes, and streamlined administrative processes. Yet, their adoption in group health plans raises complex regulatory, fiduciary, and ethical questions, particularly under the Employee Retirement Income Security Act of 1974 (ERISA), which governs virtually all workplace employee benefit plans.

    The use of AI tools by, and on behalf of, employer-sponsored group health plans raises no shortage of concerns. There are, however, three issues that require immediate attention by plan sponsors and plan administrators alike: claims adjudication, fiduciary oversight, and vendor contracts.

    Claims adjudication: Autonomous decision-making

    AI technology – defined as machine-based systems such as algorithms, machine learning models, and large language models – is increasingly used by insurers and third-party administrators (TPAs) to assess clinical claims on behalf of health plan participants.

    AI systems are likely to be used to make basic eligibility determinations, which are based on plan terms and relevant information about the employee and their beneficiaries. More substantively, AI systems may also be used to make clinical determinations. These systems could, for example, evaluate whether a particular treatment or service is deemed medically necessary based on training data and preprogrammed rules. For this purpose, an AI system might scan diagnostic codes, patient histories, and treatment guidelines to determine whether a claim aligns with standard clinical practice. AI is already being used to ease internal administrative functions for carriers and claims administrators, and its use is expected to expand significantly.

    There is a separate though equally important question of AI use in preauthorization. AI tools have the potential to improve this process by automating prior authorization requests, predicting approval likelihood, and flagging cases that require expedited human review. For example, AI could match a request for MRI imaging against clinical guidelines, patient history, and plan terms to recommend approval within seconds.

    If an AI tool is used for both initial claims adjudication and preauthorization, this poses some fundamental concerns relating to training data. There are currently three federal rules governing machine-readable files, the purpose of which is to make claims data widely available:

    • The hospital price transparency rule, requiring hospitals to disclose items and services, including the hospital standard (gross) charge, discounted cash price, and the minimum and maximum charge that a hospital has negotiated with a third-party payer.
    • The Transparency in Coverage final rule, requiring health plans to disclose in-network negotiated rates and historical out-of-network billed charges and allowed amounts.
    • The transparency rules under the Consolidated Appropriations Act, 2021, imposing additional disclosure obligations on plans and issuers.

    All three rules embed decades of provider and carrier practices that transparency was designed to expose. If these datasets are used to train AI tools, it could lead to a number of problems, including, for example, inherent biases and systemic flaws being baked in.

    Fiduciary oversight

    For fiduciaries of group health plans, any use of AI technology presents two fundamental problems. First, AI models are by their nature black boxes. And, second, there are limits to AI competence and accuracy that cannot be eliminated.

    The black-box nature of AI technology poses a significant problem for fiduciaries of group health plans. The opacity of the models makes ERISA-required monitoring and oversight extremely challenging. Robust third-party standards are needed to establish measurement science and interoperable metrics for AI systems. Further, independent certification of vendor AI systems would help fiduciaries meet ERISA standards. Ideally, the US Department of Labor (DOL) would issue guidance as it has done in related contexts, such as with cybersecurity threats involving ERISA-covered pension and later welfare plans.

    Questions about AI competence and accuracy are equally daunting to plan fiduciaries. The current crop of AI models relies heavily on a process of back propagation to continuously refine reliability. Even the most advanced AI models achieve, at best, an asymptotic approach to reliability. This raises a threshold legal question: whether and to what extent fiduciaries can prudently rely on AI technology. The practical answer is that they likely already do, sometimes unknowingly, which means that some validation of AI models is essential for a fiduciary to ensure they can meet ERISA’s requirements.

    According to the DOL, ERISA fiduciaries must ensure that plan decisions are made “solely in the interest of participants and beneficiaries” with prudence and diligence. Delegating critical claim denials to opaque AI models risks violating this duty. At minimum, AI tools should be limited to serving in a decision-support role, with final authority resting in human hands.

    Vendor contracts

    The generic reference to an ERISA-covered group health plan using AI masks an important reality: AI will typically be used on the plan’s behalf by TPAs and insurers and less often directly by the plan itself. For most large, multistate self-funded plans, this means large, national carriers acting in an administrative services only (ASO) capacity.

    ASO providers have significant leverage in negotiating contract terms. A plan delegating claims adjudication without inquiring whether and how that third party uses AI in claims adjudication risks violating fiduciary standards and facing scrutiny.

    Fiduciaries should work to understand and evaluate the risk that delegating plan functions to third parties poses and take appropriate steps in response. At a minimum, this would necessitate a group health plan insisting on AI-related contract provisions. For example, the group health plan should insist that:

    • Any claim denials must be reviewed and ultimately decided by a human clinician.
    • The ASO must disclose how AI is tested and audited.
    • Performance guarantees and indemnification provisions should cover AI-related failures.

    Given the infancy of AI in group health plan administration, ASOs are expected to resist comprehensive AI provisions, highlighting the need for federal guidance and clearer market standards.

    Legal landscape

    State law considerations

    The most prominent example of a state attempting to establish rules governing the use of AI for group health plans is California’s Physicians Make Decisions Act. Effective January 1, 2025, it prohibits the use of AI by insurance companies in certain instances of claim and utilization review for health plans and prohibits health insurers from solely relying on AI to deny any claim based specifically on medical necessity. This act is based on California Senate Bill 1120, which requires, at a high level, that medical professionals rather than AI make any determination as to whether a treatment is medically necessary.

    The act and similar laws being considered in other states, such as Arizona, Maryland, Nebraska, and Texas, highlight the need for group health plans to be aware of and ensure state law compliance, particularly as they review and negotiate ASO contracts.

    Federal agency guidance

    The DOL and the US Department of the Treasury have issued limited, indirect guidance on the use of AI. This guidance illustrates how the government might handle AI issues in the benefit plan context.

    A withdrawn DOL bulletin (Field Assistance Bulletin 2024-1) discussed the risks associated with using AI under the Family and Medical Leave Act. In the bulletin, the DOL generally warned that “without responsible human oversight, the use of such technologies may pose potential compliance challenges.” It noted that even though similar violations may occur under human decision-making processes, there is a higher risk that violations made when using AI would apply across the entirety of the task at hand or workforce.

    The Treasury department has studied AI in the financial services sector in a report, noting that while there are various benefits, the use of AI can raise concerns over bias, explainability, and data privacy, concerns that apply equally in health plan administration.

    Both agencies emphasized the need for human oversight, echoing ERISA fiduciary obligations.

    AI Disclosure Act

    Although not law, the proposed AI Disclosure Act of 2023 would require disclaimers on AI-generated content. If a version of this bill is passed, it would further require companies to disclose certain information about the use of AI. Even absent a mandate, plan sponsors may wish to consider voluntary disclosures when AI tools are used in communications or claims processes.

    * * * * *

    Next steps and action items

    While AI technology holds immense promise for employer-sponsored group health plans, its deployment carries significant fiduciary, ethical, and regulatory challenges. Plans must still meet their legal obligations under ERISA and other applicable laws and should ensure that AI does not autonomously make clinical or claims decisions, that preauthorization systems are transparent and fair, that data biases are identified and corrected, and that fiduciary oversight mechanisms are robust. Fiduciaries must balance innovation with prudence. They must ensure that AI is a tool to enhance – not replace – human judgment. Regardless, AI use likely increases fiduciary oversight obligations and necessitates ongoing monitoring.

    In light of the proliferation of AI and its impact on employee benefit plans, practical measures that plan sponsors should consider may include:

    • Inventory AI use: Identify where AI is being used by the plan and by TPAs, insurers, and other vendors in claims adjudication, preauthorization, and participant communications.
    • Update fiduciary processes: Incorporate AI oversight into plan committee charters, meeting agendas, and monitoring practices.
    • Review contracts: In new and existing contracts, negotiate for disclosure, audit rights, performance guarantees, and human review of denials in situations where AI is involved.
    • Validate outputs: Request disclosure of vendor documentation on testing, error rates, and mitigation of bias and review documentation with plan consultants during regular fiduciary committee meetings.
    • Stay informed on state laws: Monitor state legislative activity (e.g., California) and update compliance procedures.
    • Plan fiduciaries: Provide education to committee members on AI risks, limitations, and monitoring obligations under ERISA.
    • Maintain document oversight: Keep records of inquiries, discussions, and decisions relating to AI to demonstrate prudence.

    The use of AI in benefits is a complicated topic. For more information on considerations related to the use of AI in employee benefit plans, please contact your regular McDermott Will & Schulte lawyer or one of the authors listed below.

    Authors

    Jacob M. Mattinson

    Partner

    Chicago

    Sarah G. Raaii

    Partner

    Chicago

    Haley M. Dow

    Associate

    Chicago

    More insights

  • Rethinking transparency: How CRL publication could reshape sponsor disclosures

    Rethinking transparency: How CRL publication could reshape sponsor disclosures

    ARTICLE / CLIENT ALERT

    Rethinking transparency: How CRL publication could reshape sponsor disclosures

    September 15, 2025

    Read time: 6 min

    Key takeaways
    Overview

    In a marked departure from long-standing practice, the US Food and Drug Administration (FDA) has begun publishing stand-alone complete response letters (CRLs), formal communications that detail the deficiencies in a drug application preventing its approval. The FDA stated that this policy shift is intended to enhance regulatory transparency and consistency and could help guide the industry in structuring future clinical studies and FDA submissions. This change carries important legal and strategic implications, especially for public company sponsors that might need to alter their approaches to disclosure obligations in future securities filings.

    Background

    To obtain FDA approval for a new pharmaceutical product, sponsors are required to compile and submit applications containing comprehensive product information to the agency. These applications typically compile an array of data critical to the FDA’s evaluation of whether the new product meets regulatory standards, such as a description of the product’s chemical properties, research studies supporting the product’s safety and efficacy, details on the manufacturing process, and proposed packaging and labeling for the product. In situations where the FDA cannot approve a product based on the information provided in a sponsor’s initial application, the agency may issue a CRL to the sponsor. A CRL describes any deficiencies identified in the application and often suggests a course of action that the sponsor can take to bolster the product’s likelihood of approval. After receiving a CRL, a sponsor may choose to respond to the FDA’s suggestions and submit an updated application for review or request an administrative hearing to contest the denial.

    In depth

    Because of the sensitive commercial information CRLs might contain, the FDA has historically treated CRLs as confidential documents and refrained from publishing them unless part of a product’s final approval package. Although it has been common practice for sponsors to announce receipt of a CRL, the FDA’s position on confidentiality has left sponsors with broad leeway to decide how to characterize the agency’s primary reasons for issuing the CRL and its proposed remedial actions.

    Two press releases from July 2025 and September 2025 suggest that the agency believes that its historical policies have inadvertently afforded sponsors overly broad scope for “spinning” the content of unpublished CRLs, opening the door for sponsors to underplay legitimate concerns and otherwise withhold the important information CRLs contain. According to the FDA, this is not an isolated matter involving only a few entities. Internal analysis conducted by the agency in 2015 found that “sponsors avoided mentioning 85 percent of the FDA’s concerns about safety and efficacy” when publicly announcing their CRLs.

    Over recent months, to improve transparency for both industry actors and consumers, the FDA has moved away from its past reluctance to publish CRLs because of their presumed sensitivity and decided to publish close to 300 such letters issued between 2020 and 2025. The published CRLs relate not only to drugs that were ultimately approved, but also in some cases to those with pending or withdrawn applications. The FDA announced that it will begin publishing future CRLs in real time, soon after they are delivered to sponsors. Both previously issued CRLs and future CRLs will be available to the public on the openFDA website.

    By normalizing the publication of CRLs, the FDA will enable sponsors to better navigate the development and application processes and avoid common pitfalls that might unnecessarily burden their resources or otherwise delay the speed at which their product is approved. For example, published CRLs might reveal that FDA has consistently taken issue with a particular study design or objected to the lack of certain controls in a proposed manufacturing process. By learning from and acting on such insights, sponsors will be able to more effectively construct their own clinical trials and submissions ex ante, anticipating otherwise difficult-to-predict obstacles along the FDA’s review path and saving valuable time and capital.

    More broadly, the published CRLs may serve as an important indicator of FDA’s review priorities, keying sponsors in not only to the areas of their application that are more likely to receive agency pushback, but also to those that appear less important to the FDA’s ultimate disposition. Greater access to published CRLs could give sponsors a tool to contest denials more effectively, as they will become better equipped to scrutinize past FDA decisions for inconsistent treatment.

    The FDA’s move to publicize CRLs may also prompt publicly traded sponsors to reevaluate how they disclose CRLs in their regulatory filings. Under securities laws, public companies must ensure that their public filings are truthful and non-misleading. Failure to do so, including by misrepresenting the contents of CRLs, could expose sponsors to potential liability in the form of shareholder class actions or government enforcement.

    Because the FDA’s historical practice was to wait until a drug was approved to publish any associated CRLs, the first developers of a new product were able to exploit the significant lag time between a CRL’s issuance and its public availability. For example, even if a company glossed over a CRL in its disclosures, there was a very real chance that any issues or inconsistencies would be resolved over the next several years before the CRL’s publication or would simply go unnoticed by would-be plaintiffs. However, the FDA’s recent move to facilitate access to CRLs might alleviate some of the practical burdens for potential plaintiffs, encouraging closer scrutiny of disclosures and an elevated risk of litigation.

    Additionally, for public companies that voluntarily provide details in their disclosures related to their FDA applications, the agency’s new policy to promptly publish CRLs for unapproved products could entice the US Securities and Exchange Commission (SEC) to assess the accuracy of the information disclosed to investors prior to the release of the CRLs. The new SEC leadership continues to police FDA-related disclosures. Companies should reexamine their disclosure practices to account for CRL publication.

    Sponsors that believe a CRL discloses sensitive commercial information should proactively contact the FDA to request appropriate redactions under the Freedom of Information Act before the CRL’s public release.

    Next steps

    We will continue to monitor the FDA’s publication of CRLs and broader initiatives to promote regulatory transparency. If you have questions about how these initiatives might affect your business or its public filings, please contact a member of McDermott Will & Schulte’s Food, Drug & Medical Device Group or its Capital Markets & Public Companies Group.

    Authors

    James R. Ravitz

    Partner

    Washington, DC

    Paul S. Gadiock

    Partner

    San Francisco

    Jeff Weinstein

    Counsel

    Washington, DC

    Merrill M. Kraines

    Partner

    New York – One Vanderbilt Avenue

    Todd R. Kornfeld

    Partner

    New York – One Vanderbilt Avenue

    Marissa Hill Daley

    Law Clerk

    Washington, DC

    Henry Fisher

    Associate

    Washington, DC

    More insights

  • FTC chairman warns healthcare employers about noncompetes

    FTC chairman warns healthcare employers about noncompetes

    ARTICLE / CLIENT ALERT

    FTC chairman warns healthcare employers about noncompetes

    September 12, 2025

    Read time: 5 min

    Key takeaways
    Overview

    Key takeaways

    • On September 10, 2025, Federal Trade Commission (FTC) Chairman Andrew N. Ferguson sent letters to large healthcare employers and staffing firms encouraging them to review their noncompete agreements and restrictive covenants.
    • The letters warn that the FTC will take action against overbroad or unjustifiably restrictive noncompetes that limit worker mobility or patient choice.
    • The FTC highlighted concerns about noncompetes restricting clinicians in rural areas where patients already have fewer care options.
    • All employers – but especially healthcare employers – should review and update their restrictive covenants to ensure they are lawful and appropriately tailored.
    In depth

    What happened

    The FTC recently announced that Chairman Ferguson sent letters to multiple large healthcare employers and staffing companies. The template letter was released for public view. The letters encourage recipients to conduct a comprehensive review of employment agreements, including noncompetes and other post-employment restrictions, and eliminate provisions that are unfair or anticompetitive. The letters further suggest that employers should notify employees if they discontinue problematic restrictions.

    What do the letters say?

    The letters address healthcare employers’ restrictive covenants and include the following:

    • Chairman Ferguson emphasizes that enforcement against unreasonable noncompete agreements remains a top FTC priority. The agency has the authority to investigate unfair methods of competition, including noncompetes that are unjustified, overbroad, or otherwise unfair and anticompetitive.
    • Chairman Ferguson urges employers to carefully tailor restrictive covenants rather than impose broad bans on outside work.
    • While narrowly drawn restrictions may be valid, the FTC cautions that employers often rely on sweeping noncompetes without exploring less restrictive alternatives.
    • The letters specifically call out the healthcare sector, saying that noncompetes can limit clinician job opportunities and reduce patient choice, especially in rural areas.

    Who is impacted?

    The FTC did not disclose the companies that received letters but stated that they were sent to large healthcare employers and staffing firms. The agency also noted that enforcement will focus on roles such as nurses, physicians, and other medical professionals.

    The FTC is focused on both healthcare employers and the firms who provide staffing to them. Even if a healthcare employer does not use overbroad restrictive covenants, it may face compliance risk if its staffing partners use them.

    What can the FTC do if healthcare employers ignore its requests?

    The FTC does not have the authority to seek damages against employers for using noncompetes it views as overbroad. Instead, the agency is authorized to issue cease-and-desist orders and seek other civil remedies in federal court. This enforcement action does not create a private cause of action, and employees cannot sue their employers directly under the FTC Act.

    It is worth noting that the FTC does not have jurisdiction over nonprofit employers, which include many healthcare providers, and cannot seek enforcement against such organizations. That said, these nonprofit healthcare employers frequently compete with for-profit entities for talent, meaning they should still pay close attention to the FTC’s position and the practical impact of these warning letters on recruitment and retention efforts.

    Why now?

    This outreach comes just days after:

    • The FTC withdrew from its defense of its prior regulation banning noncompetes nationwide, which was first approved by FTC commissioners in April 2024 and originally slated to become effective in September 2024 but was blocked by multiple courts.
    • The agency brought an enforcement action against Gateway Services Inc., the nation’s largest pet cremation business, ordering the company to stop enforcing overbroad noncompetes binding nearly 1,800 workers.
    • The FTC invited employees and employers to comment generally on noncompetes in a public Request for Information.

    The letters also come on the heels of the FTC creating a Joint Labor Task Force in February 2025. That task force has been directed to prioritize prosecution of anticompetitive labor-market practices, including overbroad noncompetes and other restrictive covenants.

    Together, these moves signal that the FTC is pivoting from blanket restrictions to case-by-case enforcement against overly restrictive noncompetes used by employers in the healthcare sector and beyond.

    Next steps for employers

    • Review your agreements. Revisit noncompetes, nonsolicits, and other restrictive covenants to ensure their scope, duration, and geographical limitations are appropriately tailored.
    • Narrow where possible. Consider whether legitimate interests, such as protecting patient relationships or confidential information, could be addressed through less restrictive tools.
    • Be proactive. Document the reasons for any restrictions you keep and consider whether to notify employees of any changes you implement.
    • Get advice. The FTC has made it clear that healthcare employers and staffing firms will be under a microscope when it comes to case-by-case enforcement. Now is the time to make sure that your agreements hold up by conferring with legal counsel.

    Bottom line

    The FTC has put employers – especially healthcare employers – on notice that broad, overly restrictive noncompetes are at risk. Now is the time for healthcare companies and staffing firms to review and update their restrictive covenants.

    Our experienced McDermott Will & Schulte lawyers are available to help you evaluate existing agreements and design enforceable, tailored restrictions that protect your business while minimizing regulatory risk.

    Authors

    Barrick Bollman

    Partner

    Chicago

    Pankit J. Doshi

    Partner

    San Francisco, Silicon Valley

    Max Garfield

    Partner

    New York – 919 Third Avenue

    Ronald E. Richman

    Partner

    New York – 919 Third Avenue

    Martin L. Schmelkin

    Partner

    New York – 919 Third Avenue

    Stephen Wu

    Partner

    Chicago

    Nicholas Neathamer

    Associate

    San Francisco

    More insights

  • Salesloft Drift supply chain attack leads to widespread data theft

    Salesloft Drift supply chain attack leads to widespread data theft

    ARTICLE / CLIENT ALERT

    Salesloft Drift supply chain attack leads to widespread data theft

    September 10, 2025

    Read time: 4 min

    Key takeaways
    Overview

    Threat actors stole authentication tokens for Salesloft Drift, a popular marketing automation tool, leading to widespread data exfiltration from Salesforce customer instances that occurred mostly between August 8 and 18, 2025. Some affected companies believe that the threat actors targeted customer contact information and customer support information to use in subsequent attacks.

    This client alert outlines the incident and provides actionable recommendations to help clients protect themselves.

    In depth

    Salesloft confirmed that threat actors accessed Salesloft’s development platform between March and June 2025 and stole the OAuth tokens that connect Salesloft Drift to various applications, including Salesforce and Google Workspace. According to Google Threat Intelligence Group (GTIG), the threat actors exfiltrated data from Salesforce customer instances between August 8 and 18, 2025. GTIG also reports that threat actors used OAuth credentials to access a small number of Google Workspace email accounts.

    Numerous affected companies report that the affected data includes business contact information, customer relationship management information, and/or customer support information. Some companies have reported that the affected customer support information includes potentially sensitive information, such as system configurations, passwords, Application Programming Interface (API) keys, and other secrets.

    Security tips

    GTIG recommends that Drift customers take immediate action to review all third-party integrations connected to their Drift instance, revoke and rotate credentials for those applications, and investigate all connected systems for signs of unauthorized access. GTIG’s detailed instructions and Indicators of Compromise (IOCs) are available on Google’s blog. An FBI Flash report on the Drift campaign provides additional IOCs.

    Clients should assess whether their vendors send or receive sensitive information –such as configuration information, credentials, and API keys – through standard communications channels. If so, they may consider asking the vendor whether this information is stored in any application that is connected to Salesloft Drift.

    We urge all clients to take extra precautions against phishing, scams, and social engineering attacks.

    • Consider warning your vendor-facing employees that their contact information may have been compromised.
    • To help protect against the impersonation of your company and employees, consider a brand protection service to proactively identify and take down infringing domains and URLs.
    • Protect against invoice and funds transfer fraud by informing your customers in writing about how you will notify them of any updates to your banking information and how they can confirm banking instructions. Additionally, provide detailed instructions to your accounts payable team on how to confirm payment instructions from vendors.

    To reduce your exposure to future supply chain attacks, consider the following precautions.

    • Avoid transmitting passwords, encryption keys, and other secrets through standard support channels, or use an additional layer of end-to-end encryption, such as PGP encryption.
    • Review the configuration of your cloud applications and third-party integrations. Okta recommends inbound IP restrictions and client verification with DPoP (Demonstrating Proof of Possession), as described in their article on the subject.

    If you believe you or your vendors were affected by the Salesloft Drift campaign, McDermott Will & Schulte can advise you on next steps. For more information, please contact your regular lawyer or one of the authors.

    Authors

    Robert Duffy

    Counsel

    Washington, DC

    Katelyn N. Ringrose

    Associate

    Washington, DC

    David Sorenson

    Associate

    Los Angeles

    More insights

  • CMS to enforce MMSEA 111 reporting compliance beginning October 2025

    CMS to enforce MMSEA 111 reporting compliance beginning October 2025

    ARTICLE / CLIENT ALERT

    CMS to enforce MMSEA 111 reporting compliance beginning October 2025

    September 10, 2025

    Read time: 7 min

    Key takeaways
    Overview

    Beginning October 11, 2025, failure to comply with the statutory obligation that most insurers of medical claims (including self-insured entities) have to report claims under Section 111 of the Medicare, Medicaid and SCHIP Extension Act of 2007 (MMSEA 111) may result in the imposition of civil monetary penalties (CMPs). While this development does not change the existing federal False Claims Act liability risk for causing Medicare to overpay claims because of MMSEA 111 reporting errors, the addition of CMPs for MMSEA 111 noncompliance marks a significant shift in the MMSEA 111 risk profile for insurers, self-insured entities, and third-party administrators that are required to report under MMSEA 111. Stakeholders in the liability, no-fault, workers’ compensation, and group health plan spaces should take immediate steps to ensure compliance with reporting obligations to avoid substantial penalties.

    In depth

    Background

    MMSEA 111 requires certain entities, referred to as responsible reporting entities (RREs), to report information to the Centers for Medicare & Medicaid Services (CMS) about Medicare beneficiaries who are covered under their plans or who receive settlements, judgments, awards, or other payments. The purpose of this reporting is to provide CMS with the information necessary to properly coordinate benefits and avoid making payments on Medicare claims when another entity is responsible.

    The MMSEA 111 framework differs depending on whether an RRE is a non-group health plan (NGHP) or a group health plan (GHP). NGHPs include liability insurers (including self-insurers), no-fault insurers, and workers’ compensation laws or plans. GHPs include insurers and third-party administrators for GHPs, as well as plan administrators or fiduciaries of self-insured and self-administered plans.

    While reporting obligations are not changing, CMS published a final rule in 2023 that authorizes the agency to impose CMPs for noncompliance. Enforcement via random quarterly claim audits will begin on October 11, 2025, appliable to reporting failures related to events occurring on or after October 11, 2024.

    Reporting requirements for NGHPs

    NGHPs must register with CMS’s Benefits Coordination & Recovery Center (BCRC) and are expected to timely report claim information on a quarterly basis. NGHPs are required to report when they assume ongoing responsibility for medicals (ORM) or make a total payment obligation to a claimant (TPOC), such as a settlement or judgment involving a Medicare beneficiary. ORM reporting is triggered when the RRE assumes responsibility to pay, on an ongoing basis, for the injured party’s medicals associated with a claim. This often applies to no-fault and workers’ compensation claims but may occur in some circumstances with liability insurance. TPOC reporting is required when a one-time or lump-sum payment is made to resolve a claim. CMS has established a $750 threshold for TPOC reporting, although certain exceptions apply. To be considered in compliance with the timeliness requirement, NGHPs must report events within one year of the event triggering the reporting obligation, such as the date of incident for which an ORM is assumed or the date of a TPOC settlement.

    Among the entities classified as NGHPs are healthcare providers that “self-insure” for risk management purposes. Such “self-insurance” occurs when an NGHP writes off some or all of a Medicare beneficiary’s medical bill (including patient out-of-pocket costs) in order to reduce the risk of a future liability claim or provides a Medicare beneficiary (or another party) with something of value to reduce the risk of a future liability claim.

    Enforcement and penalties for NGHPs

    For NGHPs, CMS may impose inflation-adjusted penalties of $250 per day per record if a record is between one and two years late, $500 per day per record if a record is between two and three years late, and $1,000 per day per record if a record is three or more years late. There is a maximum inflation-adjusted penalty of $365,000 per record. Because of the annual inflation adjustments, these CMP amounts, including the CMP cap, are currently in excess of the base amounts and will likely continue to increase annually.

    There are two safe harbors where the CMP would not apply to NGHPs:

    • Any untimely reporting that is the result of a technical or system issue outside of the RRE’s control or that is a result of an error caused by CMS or one of its contractors
    • Any untimely reporting by an NGHP that has made a good faith effort to obtain the necessary reporting information because of a lack of cooperation by the beneficiary

    RREs must retain documentation of these good faith efforts for five years because of CMS’s right to audit.

    How this affects GHPs

    GHPs are subject to MMSEA 111 reporting requirements and, like NGHPs, will be subject to CMPs for noncompliance. GHPs must also register with the BCRC and quarterly report coverage information for Medicare beneficiaries enrolled in their plans. GHP reporting must reflect any changes in coverage, including new enrollees, terminations, and corrections to previously submitted records. GHPs may choose between a basic reporting option, which includes hospital, medical, and primary prescription drug coverage, and an expanded reporting option, which also includes supplemental or secondary prescription drug coverage.

    CMS will begin imposing CMPs for GHPs in the same timeframe as NGHPs, with penalties assessed for untimely reporting of coverage records. A GHP record is considered timely if the record is reported within one year of the latter of the coverage effective date or the date the individual became a Medicare beneficiary.

    GHPs are subject to inflation-adjusted CMPs of $1,000 per day per record of noncompliance, with a maximum inflation-adjusted CMP of $365,000 per record. As with the NGHP CMP amounts, the current amounts are already higher than these base amounts because of the inflation adjustment and will likely continue to increase on an annual basis. As with NGHPs, enforcement will be prospective only. Although there is a safe harbor for technical or system issues outside of the RRE’s control, there is no good faith safe harbor for GHPs.

    RRE audits

    CMS will begin MMSEA 111 audits in January 2026. These audits will cover new claims that were reported during the prior calendar quarter (with the initial reporting period looking back to October 15, 2025). CMS will select a random sample of 250 new Medicare secondary payer occurrences each quarter to assess compliance. Audits will include occurrences of both MMSEA 111 submissions and records from sources outside of the MMSEA 111 reporting process to ensure that CMS does not miss situations where an RRE has entirely failed to report the occurrence. RREs found to be noncompliant will receive a notice of proposed penalty and will have the opportunity to appeal through CMS’s administrative process.

    Conclusion

    With the reporting enforcement date of October 11, 2025, quickly approaching, RREs should take immediate steps to assess their compliance with MMSEA 111 reporting requirements. This includes ensuring timely and accurate submission of required records and reviewing internal compliance procedures. Any records out of compliance should be updated as soon as possible. NGHPs should also document any good faith efforts to obtain necessary information from beneficiaries, and RREs should be prepared to respond to MMSEA 111 audits beginning in 2026.

    While these audits might appear to represent a very small portion of the new claims that are likely to be reported each quarter, they nonetheless present a risk of enforcement that did not previously exist and the potential for material financial penalties. Identification of improperly reported claims through the new audits may lead to more widespread enforcement of MMSEA 111 reporting requirements under the False Claims Act in circumstances where reporting failures or deficiencies resulted in Medicare paying a claim that was the responsibility of a previously undisclosed primary payor. All RREs should use the CMP reporting deadline as an opportunity to review MMSEA 111 reporting compliance and, if necessary, take corrective actions before October 15, 2025.

    For more information on MMSEA 111 compliance, please contact Emily Cook or your regular McDermott Will & Schulte lawyer.

    Authors

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Sydney Merritt Martinez

    Associate

    Washington, DC

    More insights

  • Major ECJ decision confirms when data may be anonymous in the hands of third parties

    Major ECJ decision confirms when data may be anonymous in the hands of third parties

    ARTICLE / INTERNATIONAL NEWS

    Major ECJ decision confirms when data may be anonymous in the hands of third parties

    September 8, 2025

    Read time: 6 min

    Key takeaways
    Overview

    On 4 September, the ECJ handed down a major and eagerly awaited decision on the scope of personal data, accepting the point that pseudonymised data may be anonymised in the hands of a third party.

    The ECJ’s approach is consistent with the approach of the UK data protection authority guidance, which we summarised earlier this year in an article, ‘What ICO guidance on anonymisation means for health and life sciences companies’.

    The decision will be widely welcomed as good news and a victory for common sense, particularly in the life sciences sector.

    Background

    The background to the case was the sharing of a dataset by the Single Resolution Board (SRB) with Deloitte, which had been tasked by SRB with carrying out a valuation of the effects of a resolution procedure on shareholders and creditors.

    SRB took a series of steps to protect the dataset shared with Deloitte, including applying pseudonymisation measures to the dataset. Deloitte had no access to the original database, and SRB retained a code which allowed it to reidentify the dataset. The dataset sent to Deloitte included an alphanumeric code but not the reidentification code. SRB did not include information in its privacy notice that Deloitte was a potential recipient of the personal data.

    Following this sharing, the European Data Protection Supervisor (EDPS) received five complaints from data subjects and found that the data was personal data (pseudonymised) because SRB retained the reidentification code.

    SRB did not look at the data from Deloitte’s perspective (i.e., in Deloitte’s hands). The view of the EDPS was that it was enough for the data to be personal data because SRB had the reidentification code.

    At the heart of the dispute was whether anonymisation should be an absolute or relative test. The EDPS adopted an absolute approach, and if the court had accepted EDPS’s view, this would mean it would never be possible for data to be anonymous if any person retained the code.

    The key legal question reviewed by the ECJ was whether the data relates to identified or identifiable persons. It was accepted that the persons were not identified, so the key point is whether the persons were identifiable.

    The court rejected the EDPS position here.

    Instead, the ECJ confirmed that, contrary to the opinion of the EDPS and EDPB, pseudonymised data may, depending on the circumstances of the case, ensure that persons are no longer identifiable. More importantly, the ECJ found that the fact that SRB held the reidentification code did not necessarily mean the data was personal data.

    Instead, it was possible to put oneself in Deloitte’s position to decide whether the data was identifiable. Here, the EDPS had not properly looked (as it should have done based on the Breyer case) at whether Deloitte had legal means available to it which could, in practice, enable it to access the additional information necessary to re-identify the persons.

    As the EDPS had not looked at Deloitte’s perspective, the court held that it was not possible for EDPS to conclude that the data was personal data.

    However, it is important to note that the court did agree with EDPS in one respect – and that is that SRB, as data controller,  had breached its transparency obligations because it did not tell data subjects that the data was being transmitted to Deloitte, regardless of whether such data was personal data from Deloitte’s perspective.

    What next?

    First, this ruling confirms that pseudonymisation may be recognised as an anonymisation technique in certain cases, which has always been challenged by several EU Data Protection Authorities.

    Second, it is very helpful to have a decision that says that an absolute approach to anonymisation is not always required – the court affirms the relative approach and says that the perspective of the recipient is the one to be considered, i.e., in assessing anonymisation, a “whose hands” test is relevant.

    However, it was accepted by the parties that the data was personal data in SRB’s hands. Hence, SRB needed to tell data subjects about who it was sending their data to. This raises interesting questions about the scope and nature of transparency and would indicate to an expansive transparency notice.

    Finally, given that the decision goes against the approach that had been advocated by data protection authorities, including in recent draft guidance, it is likely that the debate to shift to how to assess the re-identification risks in the hands of the recipient, and what is meant by “reasonable means” to re-identify. Interestingly, the ECJ included a reminder in the decision that the re-identification risk must be reasonably likely, noting that the court had previously decided that this risk is insignificant where identification of a data subject would be prohibited by law or impossible in practice, because it would involve a disproportionate effort in terms of time, cost, and labour (ECJ, 7 March 2024, OC v European Commission, C 479/22). It will be interesting to review the next steps and guidance issued by authorities.

    How can we help?

    Our expert teams provide extensive support to clients in developing anonymisation and pseudonymisation strategies and work with clients in negotiating and developing agreements for the re-use of personal data.

    We are working with clients to evaluate the impact of this decision on their data processing operations and adapting their privacy risk assessments and strategies in the context of pseudonymised environments.

    In depth
    Authors

    Sharon Lamb

    Partner

    London – 22 Bishopsgate

    More insights

  • OIG continues focus on RPM services in new data-driven report

    OIG continues focus on RPM services in new data-driven report

    ARTICLE / CLIENT ALERT

    OIG continues focus on RPM services in new data-driven report

    September 8, 2025

    Read time: 8 min

    Key takeaways
    Overview

    On August 25, 2025, the US Department of Health and Human Services Office of Inspector General (OIG) issued a report analyzing Medicare billing for remote patient monitoring (RPM) services. With nearly one million Medicare beneficiaries receiving RPM services in 2024, RPM services have been the focus of recent OIG alerts, reports, and workplan items. OIG cites the increase in Medicare payments for RPM services and the potential for these services to lead to fraud, waste, and abuse as the basis for its continued attention to RPM.

    This report demonstrates OIG’s continued focus on RPM services. Stakeholders should review their current remote monitoring programs to ensure that RPM services are provided in a manner that is consistent with existing Centers for Medicare & Medicaid Services (CMS) regulations and guidance and should remain alert for additional potential changes to the requirements for RPM services.

    In depth

    Background

    In 2019, CMS began expanding payment for RPM services, which generally involve the use of digital technologies (i.e., medical devices together with software) to collect medical and other forms of health data from a patient in one location and electronically transmit the information to the patient’s healthcare provider in a different location for assessment and care management. In some cases, the technologies can either trigger direct patient engagement or facilitate patient communication. Remote physiological monitoring services (CPT codes 99091, 99453, 99454, 99457, and 99458) involve monitoring physiological measurements (e.g., weight, blood pressure, blood sugar) through medical devices that automatically transmit data obtained from patients remotely to healthcare providers for assessment and recommendations. In addition to the remote physiological monitoring CPT codes, CMS has established payment for other RPM services, including remote therapeutic monitoring services. The August 2025 OIG report focuses only on remote physiological monitoring services.

    Prior OIG alerts and reports on RPM

    OIG has increasingly scrutinized RPM services in recent years. For example, in November 2023, OIG issued a consumer alert focused on RPM, particularly direct-to-consumer RPM programs that involve advertising (i.e., through phone, television, or internet-based marketing) directed toward Medicare beneficiaries. This alert was intended to raise awareness among Medicare beneficiaries about the potential for fraud schemes involving bad actors that allegedly sign patients up for remote monitoring without an established provider-patient relationship.

    In November 2024, OIG issued a report recommending additional oversight of RPM services furnished to Medicare beneficiaries. The report recommended that CMS take several steps to improve oversight of RPM services, including:

    • Implementing additional safeguards to ensure that RPM is used and billed appropriately in Medicare
    • Requiring that RPM services be ordered and that information about the ordering provider be included on claims and in encounter data for RPM
    • Developing methods to identify what health data are being monitored
    • Conducting provider education about billing of RPM
    • Identifying and monitoring companies that bill for RPM.

    For more information on this report, please see our prior On the Subject, “OIG recommends additional oversight of remote monitoring services.”

    In December 2024, OIG announced it was adding an audit of RPM services to its work plan, citing the dramatic increase in Medicare payments for RPM services and the services’ susceptibility to fraud, waste, and abuse (e.g., unsolicited device shipments, inadequate monitoring, and inappropriate billing).

    New report findings

    Most recently, OIG, through its evaluation shop, conducted a data-driven analysis of Medicare claims and Medicare Advantage encounter data for RPM services (CPT codes 99091, 99453, 99454, 99457, and 99458) furnished between January 1, 2024 and December 31, 2024. OIG outlined its findings in response to six key questions in the August 25, 2025 report:

    • How much is Medicare paying for RPM? RPM use continued to grow in 2024, with Medicare and Medicare Advantage payments exceeding $500 million. This represents a 31% increase from 2023 and continues an upward trend that has occurred every year since Medicare began widely covering RPM services in 2019. The number of Medicare beneficiaries receiving RPM services also continued to grow, with nearly one million patients receiving RPM services in 2024.
    • How many new patients do medical practices bill for? About 4,600 medical practices routinely billed for RPM in 2024, typically billing RPM for about 70 patients during the year and adding about five new patients each month. However, OIG found that certain medical practices experienced sudden large increases in the volume of patients treated. OIG noted that while significant increases in the volume of patients treated may represent legitimate growth in a practice’s uptake of RPM, such billing spikes have been a marker of fraud for other Medicare services.
    • Do medical practices have a prior relationship with their patients? Before billing for RPM, a medical practice must establish a relationship with the Medicare beneficiary by having either an in-person or telehealth visit. OIG found that most medical practices had prior relationships with nearly all of their patients. However, OIG found 45 practices that it asserted did not have a prior relationship with 80% or more of their patients.
    • Are medical practices billing for treatment management? Treatment management services are provided when a provider or clinical auxiliary staff spend at least 20 minutes in a month using the patient’s RPM data to make decisions about the patient’s treatment and communicating with the patient about their care. OIG found that certain practices did not bill for any treatment management services in 2024 for 75% or more of their patients, warranting further scrutiny to ensure that RPM is being effectively used to treat patients’ conditions.
    • Do multiple medical practices bill for services provided to the same patient? OIG found that the vast majority of medical practices did not bill for RPM services for the same beneficiaries, although certain practices frequently billed for the same beneficiaries that two or more other practices also billed for. OIG noted that when practices frequently bill for the same patients, it raises concerns that the practices may be billing for monitoring that is either not medically necessary or not actually provided.
    • Do medical practices bill for multiple devices per patient? Medicare generally allows practices to bill for only one RPM device per month per patient. OIG found that most medical practices never billed for more than one device per month, but certain practices frequently billed Medicare for two or more devices per patient per month. OIG noted that frequent billing for multiple devices may indicate that practices are double billing for the same device or billing for devices that are either not medically necessary or not actually provided.

    OIG stated that monitoring billing can help:

    • Safeguard the Medicare program
    • Prevent fraud, waste, and abuse
    • Ensure that Medicare beneficiaries receive the benefits of RPM while also minimizing program integrity risks.

    OIG stated that the billing patterns highlighted in its report (including billing for a high proportion of patients who have no prior history with the medical practice and billing for multiple monitoring devices a month for a patient) can help OIG identify medical practices that warrant further scrutiny.

    Takeaways for stakeholders

    Providers that furnish RPM services and digital health companies that help providers furnish these services should continue to monitor OIG and CMS publications on RPM services. Companies should ensure that their remote monitoring programs (including their policies, procedures, and general practices) are consistent with existing CMS regulations and structured to address the concerns highlighted by OIG, as appropriate. In light of increasing scrutiny of remote monitoring services, companies should ensure that their compliance programs fully address the unique risks and considerations these services present.

    The American Medical Association’s CPT Editorial Panel finalized new and updated RPM codes that will be effective January 1, 2026. As part of the regular review process for new and updated CPT codes, CMS proposed new and updated payment rates for the revised CPT codes in the CY 2026 Medicare Physician Fee Schedule Proposed Rule. While CMS could have used this opportunity to provide guidance or implement additional requirements for RPM services to respond to the November 2024 OIG report, CMS did not propose any changes or guidance clarifications to address the concerns raised by OIG. In response, in its August 2025 report, OIG reiterated the importance of CMS implementing the OIG’s 2024 recommendations to strengthen CMS’s oversight of RPM services. RPM also remains on the OIG workplan.

    OIG’s August 2025 report is based on a claims data analysis. Providers should expect that CMS contractors, such as Medicare Administrative Contractors, Recovery Audit Contractors, and Unified Program Integrity Contractors, will rely on similar claims data analyses to target providers for audits and other potential program integrity reviews.

    Stakeholders also should be aware that OIG continues to focus on RPM services as a fraud and abuse concern. This concern may prompt discussions with CMS regarding additional measures to ensure that remote monitoring services are furnished consistent with existing requirements and guidance, or it could prompt CMS to impose additional limitations or requirements on RPM services.

    We will continue to monitor updates to RPM services. Please contact the authors of this article or your regular McDermott Will & Schulte lawyer with any questions.

    Authors

    Caroline Reignley

    Partner

    Washington, DC

    Grayson I. Dimick

    Associate

    Washington, DC

    James A. Cannatti III

    Partner

    Washington, DC

    Marshall E. Jackson , Jr.

    Partner

    Washington, DC

    More insights

  • HHS announces information blocking enforcement “crackdown”

    HHS announces information blocking enforcement “crackdown”

    CLIENT ALERT / INFORMATION BLOCKING

    HHS announces information blocking enforcement “crackdown”

    September 5, 2025

    Read time: 6 min

    Key takeaways
    Overview

    The US Department of Health and Human Services (HHS) announced its intent to begin actively enforcing the information blocking regulations adopted under the 21st Century Cures Act, in a press release on September 3, 2025, and an enforcement alert issued jointly by the HHS Office of Inspector General (OIG) and Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) on September 4, 2025. Actors subject to the information blocking regulations should review their current information sharing practices to ensure compliance.

    For more information on information blocking, visit McDermott Will & Schulte’s Information Blocking & Interoperability in Healthcare resources page. For more information about how to prepare for HHS enforcement of the information blocking regulations, view our webinar “Information Blocking: Defense of Cures Act Investigations and Enforcement.”

    In depth

    The Cures Act prohibits information blocking by health care providers, certified health information technology (IT) developers, and health information networks and exchanges (HIN/HIEs). Information blocking refers to practices that are likely to interfere with the access, exchange, or use of electronic health information (EHI), except as required by law or specified in an information blocking exception, and that:

    • If conducted by a certified health IT developer or HIN/HIE, the developer or HIN/HIE knows, or should know, are likely to interfere with access, exchange, or use of EHI.
    • If conducted by a health care provider, the provider knows are unreasonable and likely to interfere with access, exchange, or use of EHI.

    On July 3, 2023, OIG issued its final rule to implement OIG’s authority under the Cures Act to investigate claims of information blocking and assess civil monetary penalties of up to $1 million (subject to inflation adjustments) for information blocking violations by a certified health IT developer or an HIN/HIE. The effective date of the OIG final rule was September 1, 2023. For a discussion of the OIG final rule, see our Special Report. To date, OIG has not publicly released information about any investigation or enforcement action under the OIG final rule.

    On July 1, 2024, HHS issued a final rule to implement the Cures Act provision establishing penalties (called “appropriate disincentives”) for certain health care providers determined by OIG to have committed information blocking. The disincentives for certain Medicare-participating hospitals and clinicians became effective July 31, 2024, while disincentives associated with the Medicare Shared Savings Program became effective January 1, 2025. For a discussion of the appropriate disincentives final rule, see our On the Subject. To date, there have been no public reports of any OIG investigation of health care providers or impositions of appropriate disincentives by HHS under this final rule.

    In addition to these penalties, ASTP can terminate a certified health IT developer’s certifications under the Health IT Certification Program for information blocking in violation of ASTP’s health IT certification requirements.

    HHS described the September 3, 2025, press release as “a warning to actors still engaging in information blocking to come into compliance with the rules governing the flow of patient information” and encouraged stakeholders to report alleged information blocking.

    In the enforcement alert, ASTP and OIG committed “to using all available authorities to hold information blockers accountable,” and HHS stated that it will provide additional resources to enforce the information blocking prohibition. In conjunction with these public statements, ASTP held an in-person boot camp on September 4, 2025, for actors that interact with certified health IT, highlighting current capabilities to access, exchange, and use EHI as well as the complaint system process for allegations of information blocking. ASTP is planning additional outreach and engagement activities in the future.

    Next steps

    All regulated actors should consider the following next steps:

    • Review policies, procedures, and practices affecting access, exchange, or use of EHI to confirm that they are consistent with the information blocking regulations and related laws, such as HIPAA and, for developers, ASTP’s Health IT Certification Program requirements.
    • Review, update, or create documentation describing the organization’s commitment to health information sharing consistent with the information blocking regulations.
    • Train personnel responsible for negotiating and implementing collaborations, partnerships, and other arrangements with third parties (e.g., digital health companies and consumer-facing app developers) seeking access, exchange, or use of EHI, to avoid conduct that may lead to information blocking claims.
    • Refine processes to create and retain records and other documents demonstrating the organization’s compliance with the information blocking regulations, including relevant exceptions.
    • Interview and identify defense counsel to help navigate a potential OIG investigation so the organization is prepared in the event of an actual investigation.

    Because ASTP has emphasized information sharing practices through certified application programming interface (API) technology in multiple guidance documents during the past 12 months, certified health IT developers should consider the following next steps:

    • Review deployments of certified API technology to confirm compliance with the Health IT Certification Program’s conditions and maintenance of certification requirements specific to certified APIs.
    • Review certified API practices, informed by the practices ASTP highlighted in its API guidance, to confirm compliance and identify potential information blocking exceptions that may apply to related practices.
    • Promptly evaluate and, if appropriate, address any complaints from certified API users alleging noncompliance with any certification requirements.

    Health care providers should consider the following steps with respect to their certified API technology deployments:

    • Review the provider’s certified API practices, informed by the practices ASTP highlighted in its guidance, to confirm compliance and identify potential information blocking exceptions that may apply to related practices.
    • Promptly evaluate and, if appropriate, address any complaints from certified API users alleging noncompliance with any certification requirements.

    For more information about ASTP’s API guidance, see our On the Subject about the ASTP fact sheet released October 29, 2024.

    Please contact your regular McDermott Will & Schulte lawyer or any of the authors of this article if you have questions about compliance with the information blocking regulations or responding to OIG inquiries.

    Authors

    James A. Cannatti III

    Partner

    Washington, DC

    Daniel F. Gottlieb

    Partner

    Chicago

    Nathan Gray

    Associate

    Washington, DC

    More insights