ARTICLE / CLIENT ALERT
IRS Announces 2026 Limits for Health Savings Accounts, High-Deductible Health Plans, and Excepted Benefit HRAs
May 1, 2025
Read time: 2 min
The Internal Revenue Service (IRS) recently announced (see Revenue Procedure 2025-19) cost-of-living adjustments to the applicable dollar limits for health savings accounts (HSAs), high-deductible health plans (HDHPs), and excepted benefit health reimbursement arrangements (HRAs) for 2026. All of the dollar limits currently in effect for 2025 will change for 2026, with the exception of one limit. The HSA catch-up contribution for individuals ages 55 and older will not change as it is not subject to cost-of-living adjustments.
The table below compares the applicable dollar limits for HSAs, HDHPs, and excepted benefit HRAs for 2025 and 2026.
| HEALTH AND WELFARE PLAN LIMITS | 2025 | Δ | 2026 |
|---|---|---|---|
| HDHP – Maximum annual out-of-pocket limit (excluding premiums) | |||
| Self-only coverage | $8,300 | ↑ | $8,500 |
| Family coverage | $16,600 | ↑ | $17,000 |
| HDHP – Minimum annual deductible | |||
| Self-only coverage | $1,650 | ↑ | $1,700 |
| Family coverage | $3,300 | ↑ | $3,400 |
| HSA – Annual contribution limit | |||
| Self-only coverage | $4,300 | ↑ | $4,400 |
| Family coverage | $8,550 | ↑ | $8,750 |
| Catch-up contributions (ages 55 and older) | $1,000 | = | $1,000 |
| Excepted Benefit HRA | |||
| Annual contribution limit | $2,150 | ↑ | $2,200 |
Next Steps
Plan sponsors should update payroll and plan administration systems for the 2026 cost-of-living adjustments and incorporate the new limits in relevant participant communications, such as open enrollment and communication materials, plan documents, and summary plan descriptions.
For further information about applying the new HSA, HDHP, and excepted benefit HRA plan limits for 2026, please contact your regular McDermott lawyer or one of the authors below.

Food as Medicine: A Deep Dive Into Reimbursement
ARTICLE / CLIENT ALERT
Food as Medicine: A Deep Dive Into Reimbursement
May 1, 2025
Read time: 13 min
The topic of “food as medicine” has gained increased attention recently, driven by a growing recognition of the role nutrition plays in preventing and managing chronic diseases. This article provides a high-level overview of the evolving food as medicine landscape and highlights key players, incentives, and regulatory challenges. It delves into how both governmental and private sources fund and reimburse these initiatives with a goal of integrating nutrition into healthcare for improved health outcomes.
Defining Food as Medicine
While there is no single definition of food as medicine, the concept generally refers to prioritizing food and diet in an individual’s health regimen with the goal of either preventing, reducing symptoms of, or reversing disease. In its Food Is Medicine Landscape Summary, the US Department of Health and Human Services defines the concept as “encompass[ing] a broad range of approaches that promote optimal health and healing and reduce disease burden by providing nutritious food – with human services, education, and policy change – through collaboration at the nexus of health care and community.” The American Society for Nutrition notes that food as medicine sits at the crossroads of nutrition and healthcare and may take many forms, including medically tailored meals (MTM), medically tailored groceries, and produce prescription programs. As illustrated by the varying definitions and potential service offerings, food as medicine represents a broad array of disciplines, interests, and actors and may include services, whether standalone or in conjunction with one another, in furtherance of a person’s overall health and well-being.
The chart below summarizes various key actors within the food as medicine industry. These actors often must engage with one another via a patchwork of contractual and other relationships to successfully implement and execute effective food as medicine programs.
The Food as Medicine Landscape
| Actor | Role | Examples of Participation/Activities | Key Legal Issues | Incentives to Participate |
|---|---|---|---|---|
| Healthcare Providers | Integrate nutrition-based interventions into care plans | Offer MTM and nutrition counseling | Compliance with healthcare regulations; liability for dietary recommendations | Reduced healthcare costs; improved patient outcomes |
| Food and Meal Delivery Services | Supply and deliver nutritious meals tailored to medical needs | Partner with healthcare providers to deliver MTM and specialized meal plans | Food safety and labeling regulations; liability for meal delivery and dietary accuracy | Increased demand; revenue growth |
| Retailers and Grocery Chains | Facilitate access to healthy foods | Implement produce prescriptions and offer discounts on healthy foods | Product safety and labeling; compliance with health and nutrition claims requirements | Customer loyalty; increased sales |
| Health Insurers/Payers | May cover and reimburse for food as medicine services | May provide coverage for nutrition programs, MTM, and produce prescriptions, or allow food as medicine activities to be accounted for under value-based care models | Coverage and reimbursement policies; regulatory compliance with state and federal laws | Cost savings; enhanced member health |
| Nonprofit Organizations | Address food insecurity and promote nutrition education | Run community programs providing access to healthy foods and nutrition education | Funding and grant compliance; accountability for nutrition advice and program outcomes | Funding opportunities; community impact; mission fulfillment |
| Research Institutions | Conduct studies on the impact of nutrition on health | Generate evidence to support food as medicine interventions and inform policy | Ethical considerations in research; compliance with research funding and reporting standards | Grant funding; policy influence |
| Technology Companies | Develop platforms and apps for delivery of personalized nutrition services, data analytics, and other technology services | Create digital health tools for dietary recommendations and tracking and integration with electronic medical records; support data sharing among partners and various actors | Data privacy and security; compliance with healthcare technology standards | Market expansion; data monetization |
Funding and Reimbursement for Food as Medicine Initiatives
As with any innovative initiatives, funding sources are of pivotal importance for food as medicine programs. Food as medicine initiatives may be funded and reimbursed via both governmental and private sources. However, not all actors are able to participate in each potential reimbursement stream, further necessitating strategic partnerships between payors and providers of both food and patient services to develop effective programs. Actors may also face specific regulatory issues and related hurdles.
Food as medicine initiatives are not currently reimbursed by Medicare or Medicaid on a fee-for-service basis under the traditional programs. However, both Medicare Advantage (MA) and Medicaid waiver programs have provided certain avenues for food as medicine reimbursement. While the Biden administration advanced initiatives in this arena, the new Trump administration has already narrowed some of these flexibilities (see Medicaid Managed Care section below).It will be important to closely monitor federal rulemakings to stay abreast of potentially changing rules in this arena.
Medicare Advantage
Many MA organizations (MAOs) offer food as medicine interventions under a range of authorities. These benefits may be attractive to MAOs as a way to reduce costs and improve member health, and offer an enhanced, competitive benefits package. Despite these incentives, MAOs do not have the authority to offer any food as medicine benefits that they wish and instead must fit all benefits into an authorized benefits category. The most common pathways for MAOs to offer food as medicine include supplemental benefits, special supplemental benefits for the chronically ill (SSBCIs), and the Value-Based Insurance Design (VBID) Model.
Supplemental Benefits
A supplemental benefit is an item or service not covered by original Medicare that is primarily health related and for which the MA plan must incur a non-zero direct medical cost.[1] Guidance from the Centers for Medicare & Medicaid Services (CMS) regarding supplemental benefits specifically lists several food as medicine items that qualify as supplemental benefits:
- Meals for a temporary duration immediately following surgery or an inpatient hospital stay.
- General nutritional education through classes and/or individual counseling.
- Enhanced disease management programs that include educational activities related to dietary restrictions and nutritional counseling.
- Weight management programs that include a plan to keep the weight off over time; guidance on healthier eating; and ongoing feedback, monitoring, and support.
- One-on-one medical nutrition therapy counseling provided by a registered dietician or other nutrition professional.[2]
Offering these food as medicine items as supplemental benefits is popular in the MA program. For CY 2025, nearly two-thirds of MA plans offer some kind of temporary meal service benefit, and more than 99% of Medicare beneficiaries have access to a plan that offers one.[3]
Special Supplemental Benefits for the Chronically Ill
In addition to traditional supplemental benefits, MAOs can offer an even broader range of supplemental benefits to chronically ill enrollees. Per the Social Security Act, these benefits, known as SSBCIs, need not fall within the definition of “primarily health related” but must be limited to items or services that have a “reasonable expectation of improving or maintaining the health or overall function of the chronically ill enrollee.”[4] This gives MAOs more leeway in the types of items and services they can offer. However, only members who qualify as chronically ill enrollees[5] are eligible to receive SSBCIs.[6] Common SSBCIs include meals and allowances for healthy food and produce.[7] The meals can go beyond those provided as a traditional supplemental benefit and do not need to be tied to a member’s surgery or an inpatient hospital stay. Healthy food allowances typically are offered in the form of a debit card that can be used at a grocery store. CMS has recently clarified that nonhealthy foods are not allowable as SSBCIs because they do not have a reasonable expectation of improving or maintaining the health or overall function of a chronically ill enrollee.[8] For CY 2025, the vast majority (84%) of special needs plans, which typically enroll higher proportions of chronically ill members, offer food and produce as an SSBCI while only 15% of non-special-needs plans do.[9]
Value-Based Insurance Design Model
The VBID Model has permitted participating MAOs the flexibility to use certain varied supplemental benefit designs.[10] Under the model, MAOs have offered certain enrollees non-primarily health-related supplemental benefits and may offer them on a non-uniform, tailored basis to certain enrollees.[11] MAOs may target the benefits based on chronic health conditions, socioeconomic status, residence in most underserved area deprivation index areas, or a combination of the foregoing. Food as medicine benefits under the model include meals (beyond otherwise allowable limits) and individual food items, including produce.[12] While the model has been a popular avenue to offer these benefits, CMS has announced that it will terminate the VBID Model at the end of 2025.[13]
Medicaid Managed Care and Sections 1115 and 1915 Waivers
To receive federal matching funds for their Medicaid programs, states generally must agree to meet federal requirements.[14] However, states can choose to provide optional benefits under state plan authority and through waiver authority under Section 1915 of the Social Security Act. They can also offer non-mandatory benefits under demonstration project waiver or expenditure authorities under Section 1115 of the Act. States also use managed care delivery systems to provide Medicaid covered benefits through contracted arrangements with managed care organizations (MCOs).[15]
With limited exceptions, federal law does not explicitly permit states to cover the direct provision of food as an established Medicaid benefit.[16] However, states and MCOs can address nutritional needs in a variety of ways. For example, states could add home-delivered meals as a service under Section 1915(b)(3) authority and have managed care plans provide this service to individuals with chronic conditions, as long as the meals do not constitute a full dietary regimen and the individuals receiving the service have an assessed need for home-delivered meals documented in their person-centered service plan.[17] At least 10 states, including California, New York, Massachusetts, and Illinois, have obtained CMS-approved Section 1115 waivers to implement food as medicine demonstration projects.[18]
While states have had great flexibility to tailor their food as medicine projects in the past, CMS recently rescinded guidance on covering services and supports for health-related social needs, which had given states a framework for providing food.[19] CMS has previously articulated that it considers the following nutrition services allowable under Section 1115 authority:
- Case management services.
- Nutrition counseling and instruction.
- Home-delivered meals (including MTM) or pantry stocking, up to three meals per day.
- Nutrition prescriptions, up to three meals per day.
- Grocery provisions, up to three meals per day.[20], [21]
States were also granted leeway to propose clinically focused, needs-based criteria to target interventions at certain populations.[22] Common target populations include pregnant and postpartum individuals, individuals with chronic diet-sensitive conditions, and individuals with substance use disorder or serious mental illness.[23]
Recently, CMS sent a state Medicaid director letter indicating that the agency would review Section 1115 waivers that provided federal matching funds for programs that would not have otherwise qualified for federal Medicaid funding.[24] The letter did not directly mention food and nutritional supports, but six of the eight states mentioned as having approved Section 1115 waivers that would be reviewed are states that currently implement food as medicine programs.[25] The extent to which the Trump administration will approve federal funds being used for food as medicine programs is uncertain at this time.
Additional Authorities
In addition to waivers, Medicaid MCOs may leverage the following authorities to implement food as medicine interventions:
- In lieu of services and settings is a payment pathway that enables states to authorize Medicaid MCOs to provide medically appropriate, cost-effective substitutes for covered services.[26] Allowable substitutes include grocery provisions, nutrition prescriptions, home delivered meals or tailored pantry stocking, and nutrition counseling.[27]
- Value-added services are services in addition to those covered under the state plan, although the cost of these services may not be included in the capitation rate.[28]
- Federal regulations include requirements for how states may direct plans to implement specific delivery systems and provider payment initiatives under Medicaid managed care. These types of payment arrangements permit states to direct specific payments made by managed care plans to providers under certain circumstances and can assist states in furthering the goals and priorities of their Medicaid programs, including to reinforce a state’s commitment to addressing social determinants of health (SDOH).[29]
- States may use incentive payments to reward managed care plans that make investments or improvements in SDOH in line with performance targets specified in the managed care plan contract, including implementation of a mandatory performance improvement project that focuses on factors associated with SDOH.[30]
- States may develop and implement specific managed care plan procurement and contracting strategies to incentivize care coordination across medical and nonmedical contexts, including to address SDOH.[31]
Private Sources of Funding and Reimbursement
Covering food as medicine under an employer-sponsored health plan currently may pose administrative challenges, but the Internal Revenue Service (IRS) may adopt more flexible guidance to expand such coverage.[32]
Currently, whether an employer health plan may cover or reimburse an expense on a tax-advantaged basis generally depends on whether it meets the definition of a qualified medical expense. Section 213(d) of the Internal Revenue Code and related regulations define medical expenses as amounts paid “for the diagnosis, cure, mitigation, treatment or prevention of disease, or for the purpose of affecting any structure or function of the body” that are “incurred primarily for the prevention or alleviation of a physical or mental defect or illness.” Expenses that are merely “beneficial” to an individual’s general health are not medical care under Code Section 213(d). Such expenses generally are not qualified medical expenses unless a physician determines that they are necessary to treat or alleviate a certain physical or mental illness.
As a result, food as medicine generally must meet the definition of a qualified medical expense to be covered or reimbursed under an employer-sponsored health plan. Food as medicine, such as special foods or supplements, may be considered a dual-purpose expense, which can be a qualified medical expense or a personal expense depending on the facts and circumstances. To substantiate that a particular expense, such as food as medicine, is in fact a qualified medical expense, IRS guidance generally requires that claims for expense reimbursements be substantiated with independent third-party information. This is usually accomplished through an invoice or other documentation of the expense and a letter of medical necessity, in which a healthcare provider documents that an individual has a certain condition for which the provider recommends a specific food as medicine. The IRS does not consider an individual’s self-substantiation or certification to be adequate. Even when an individual obtains a letter of medical necessity, the employer-sponsored health plan administrator (often a third-party administrator) may take a conservative position and not cover or reimburse potential dual-purpose items such as food as medicine.
In addition to potential government reimbursement opportunities and coverage under employer-sponsored health plans, food as medicine programs may be paid for on a cash basis or otherwise funded by private investment. These partnerships and funding sources can potentially alleviate some regulatory complexities associated with government reimbursement but may also present other considerations when building a successful food as medicine program.
Key Takeaways
The concept of food as medicine is broad and constantly evolving. Marketplace participants continue to face various hurdles such as funding and reimbursement to get initiatives off the ground and to show their value proposition and beneficial impact on global health and well-being. As these programs evolve and seek to expand, market participants in this space should implement strategies for regulatory compliance and stay abreast of current reimbursement opportunities.
In addition to tracking and complying with reimbursement requirements, it is important to remember that actors in this space do not act alone and often must partner and contract with each other to implement effective programs. As food as medicine opportunities continue to evolve, actors in the food as medicine space should continue to look for new ways to partner with one another to implement and deliver food as medicine programs.

Washington’s Digital Ad Tax: A Lawsuit Waiting To Happen?
ARTICLE
Washington’s Digital Ad Tax: A Lawsuit Waiting To Happen?
May 1, 2025
Read time: 5 min
On April 27, 2025, the Washington Legislature delivered to Governor Bob Ferguson’s desk Senate Bill (SB) 5814, a sweeping tax bill that, among other changes, would expand the state’s retail sales and use tax to sales of digital advertising services and a range of high-tech and IT services. The bill now awaits the governor’s signature, with a decision due by May 20, 2025.
If enacted, the changes would take effect October 1, 2025, marking a significant expansion of Washington’s tax base into areas that have long been exempt, particularly intermediate business services such as digital marketing, data processing, and custom software support.
WHAT THE BILL DOES
SB 5814 amends RCW 82.04.050 by redefining “sale at retail” to include a broad range of services previously excluded from the sales tax. Specifically, it adds “advertising services,” defined as:
All digital and nondigital services related to the creation, preparation, production, or dissemination of advertisements including, but not limited to: layout, art direction, graphic design, mechanical preparation, production supervision, placement, referrals, acquisition of advertising space, and rendering advice…
The definition also expressly includes:
- Online referrals
- Search engine marketing
- Lead generation optimization
- Web campaign planning
- The acquisition of advertising space in the internet media
- Website traffic analysis for determining the effectiveness of an advertising campaign.
However, the bill expressly excludes advertising services rendered in connection with newspapers (as defined in RCW 82.04.214); printing or publishing (RCW 82.04.280); radio and television broadcasting; and out-of-home advertising such as billboards, transit displays, and signage at events.
With that list of exclusions, it’s hard to imagine what advertising services other than internet advertising services are left to tax. This focus on internet advertising creates a prima facie discriminatory tax on electronic commerce barred by the federal Internet Tax Freedom Act (ITFA).
ITFA AND THE CERTAINTY OF A LEGAL CHALLENGE
ITFA prohibits states from imposing “discriminatory taxes on electronic commerce.” A tax is discriminatory if it applies to digital services but not similar offline equivalents.
While SB 5814 expressly includes both digital and non-digital advertising services, the carve-outs for traditional formats such as print, TV, and radio effectively leave out non-digital advertising. As the bill itself states, services connected to newspapers, publishing, and broadcast media are not taxable. This distinction creates a classic ITFA problem:
- A digital banner ad campaign will be taxed.
- A newspaper ad or radio spot promoting the same product will not.
This kind of structural bias has been challenged before. Maryland’s Digital Advertising Gross Revenues Tax (the first of its kind in the United States) was enacted in 2021 and quickly faced multiple lawsuits on ITFA and other grounds. In 2022, a Maryland trial court struck down the law as unconstitutional, citing ITFA violations and federal preemption (although the decision was later reversed on procedural grounds). That litigation continues while the stack of taxpayer refund claims on the Maryland Comptroller’s desk grows taller.
Washington faces a similar outcome. SB 5814’s facial discrimination against digital advertising is precisely the kind of unequal treatment ITFA was designed to prohibit.
HIGH-TECH AND IT SERVICES ARE NOW TAXABLE
High technology is a bread-and-butter industry for Washington. Remarkably, SB 5814 also extends the sales tax base to a host of high-tech services that are the core of its economy. Newly taxable categories include:
- Custom website development
- IT technical support (e.g., help desk and network operations)
- In-person or live virtual IT training
- Data processing and data entry.
These services are often purchased by businesses (not end consumers), which raises concerns about tax pyramiding (i.e., the compounding of sales tax on intermediate services before the final product reaches consumers). This hidden cost is typically passed on to customers, increasing prices and embedding inflationary pressure in the state’s economy.
Local advertisers and businesses that rely on digital marketing and high-tech services will see these costs rise, which will lead to higher prices for consumers and make it more difficult to operate competitively in Washington.
OUTLOOK
If enacted, SB 5814 will face legal challenges, particularly under ITFA, in due course. The bill’s structure – taxing digital ad services while exempting traditional media – invites litigation that will tie up the state’s Revenue Department in court for years and expose Washington to refund liability with interest and make future tax revenue illusory.
At the same time, the bill’s economic impact is highly uncertain. While projected to raise new revenue, it may instead undermine Washington’s own digital economy, pushing business out of state, inflating the cost of advertising and IT services, and burdening consumers with hidden costs.
The state is gambling with legal exposure and economic disruption to chase speculative revenue. Like Maryland, Washington may find that taxing digital advertising is far easier to legislate than to defend or enforce. If SB 5814 becomes law, the real verdict may come not from Olympia, but from the courts.

IRS Roundup April 1 – April 17, 2025
ARTICLE
IRS Roundup April 1 – April 17, 2025
May 1, 2025
Read time: 4 min
Check out our summary of significant Internal Revenue Service (IRS) guidance and relevant tax matters for April 1, 2025 – April 17, 2025.
April 4, 2025:
The IRS issued Notice 2025-19, inviting the public to submit recommendations for items to include in the IRS’s 2025-2026 Priority Guidance Plan. The IRS uses the Priority Guidance Plan to identify and prioritize the tax issues that should be addressed via regulations, revenue rulings, revenue procedures, notices, and other published administrative guidance. A list of factors the IRS considers when selecting projects for inclusion is outlined in the notice.
April 9, 2025: The US Department of the Treasury (Treasury), along with the IRS and the Financial Crimes Enforcement Network, eliminated 15 rules and guidance materials, in addition to two rules already rescinded by the Office of the Comptroller of the Currency. The stated purpose of these actions was to remove rules that the government says are now obsolete and hamper the growth of US small businesses. These actions were some of the many that the Treasury says it will take over the next several months to eliminate unnecessary IRS rules and to “unleash the regulated banking sector.”
April 10, 2025: US President Donald Trump signed legislation blocking an IRS reporting rule that would have required decentralized digital asset platforms to report statistics showing customers’ gross sales on their platforms.
April 11, 2025: The IRS issued Notice 2025-24, providing penalty relief under Section 6707A(a) of the Internal Revenue Code to participants in micro-captive reportable transactions that fail to timely file (i.e., by April 14, 2025) certain disclosure statements as required under Section 6011; Treas. Reg. §§ 1.6011-10(h)(2) or 1.6011-11(h)(2); Section 6111; and Treas. Reg. §§ 1.6011-10(h)(3) or 1.6011-11(h)(3)). Participants will only qualify for relief if they file the required disclosure statement with the Office of Tax Shelter Analysis by July 31, 2025.
April 14, 2025: The IRS issued Notice 2025-22, providing for the elimination of extraneous and unnecessary Internal Revenue Bulletin guidance. This notice was prompted by the issuance of Executive Order 14219 on February 19, 2025. The purpose of Executive Order 14219 is to focus the IRS’s limited enforcement resources on regulations “squarely authorized by constitutional Federal statutes” while eliminating “overbearing and burdensome” regulations and “ending Federal overreach.” In Notice 2025-22, the IRS eliminated several current sources of guidance and stated that it anticipates revoking or obsoleting hundreds of similar guidance documents in the near future.
April 15, 2025: The IRS issued Notice 2025-21, providing updates on the corporate bond monthly yield curve, spot segment rates used under § 417(e)(3), and the 24-month average segment rates under § 430(h)(2) of the Code. This notice also provides guidance on the interest rates for 30-year Treasury securities and the 30-year Treasury weighted average for plan years beginning before 2008.
April 17, 2025: The IRS issued Notice 2025-23, announcing its intent to publish a notice of proposed rulemaking, proposing the removal of Treas. Reg. § 1.6011-18 (Basis Shifting TOI Regulations) from the Income Tax Regulations. As of January 14, 2025, the Basis Shifting TOI Regulations identified certain partnership-related-party basis adjustment transactions as transactions of interest. Since becoming effective in January, taxpayers have criticized the Basis Shifting TOI Regulations as imposing complex, burdensome, and retroactive disclosure obligations on ordinary activities, rendering compliance costly and creating uncertainty for business activities. Thus, pursuant to Executive Order 14219, directing agencies to remove certain regulations through the Department of Government Efficiency initiative, the Treasury identified this as a burdensome regulation that should be removed. Moreover, given the Treasury’s intent to remove the Basis Shifting TOI Regulations, Notice 2025-23 states that the IRS will waive penalties under § 6707A(a) for any failure to file a Form 8886, § 6707(a) for any failure to file a Form 8918, and § 6708 for any failure to maintain a list under § 6112.
The IRS also released its weekly list of written determinations (e.g., Private Letter Rulings, Technical Advice Memorandums, and Chief Counsel Advice).

PointClickCare Denied En Banc Hearing to Overturn Preliminary Injunction Mandating Access to EHR Data
CLIENT ALERT / INFORMATION BLOCKING
PointClickCare Denied En Banc Hearing to Overturn Preliminary Injunction Mandating Access to EHR Data
May 1, 2025
Read time: 12 min
On April 23, 2025, the US Court of Appeals for the Fourth Circuit denied PointClickCare Technologies, Inc.’s petition for en banc review in Real Time Medical Systems, LLC v. PointClickCare. A Fourth Circuit panel previously affirmed a preliminary injunction issued by the US District Court for the District of Maryland. The injunction issued on July 29, 2024, required PointClickCare to remove certain restrictions on Real Time’s access to electronic health record (EHR) data that PointClickCare hosts for skilled nursing facility customers. Real Time sought access to the data to provide data analytics services to the skilled nursing facilities and alleged unfair competition in the form of information blocking.
The case has generated intense interest among stakeholders that maintain or request electronic health information, including EHR software developers and other actors subject to the information blocking regulations adopted by the US Department of Health and Human Services (HHS) Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) under the 21st Century Cures Act. The Fourth Circuit panel’s decision interprets ambiguities in the information blocking regulations in ways that favor access by information requestors and raises the prospect that requestors can enforce the information blocking regulations through lawsuits based on state unfair competition law claims or other state law claims, despite the lack of a federal private right of action under the Cures Act for information blocking violations. Lawsuits based on state law claims are attractive to some requestors that have grown frustrated by the absence of enforcement of the regulations to date by the HHS Office of Inspector General (OIG).
On the other side, the American Hospital Association (AHA) and Electronic Health Record Association (EHRA) have filed multiple amici curiae briefs in support of PointClickCare, including a brief filed on April 2, 2025, supporting its petition for rehearing. AHA, EHRA, and many regulated actors generally believe the information blocking regulations should be interpreted to only require the provision of access through standards-based access methods and not to require actors to develop bespoke methods unless the actor and requestor mutually agree to the bespoke methods.
For more information about enforcement of the information blocking prohibition, see our On the Subject on the information blocking disincentives final rule and our webinar titled, “Information Blocking: Defense of Cures Act Investigations and Enforcement.”
Background on Real Time V. PointClickCare
PointClickCare provides a cloud-based EHR system to skilled nursing facilities and other health care providers. PointClickCare has added clinical decision support and other analytics capabilities to its EHR system that compete with Real Time’s services. PointClickCare’s standard customer agreement prohibits customers’ use of automated users, commonly called “bots,” to extract data or access services in a way that adversely impacts performance.
Real Time provides health data analytics services under agreements with certain skilled nursing facilities and other providers that are PointClickCare’s customers by accessing and analyzing information stored in the PointClickCare system. While PointClickCare and Real Time contract with some of the same customers for their respective services, they do not contract with each other to address Real Time’s access to PointClickCare’s technology.
In Real Time’s standard business model, it downloads information needed for its analytics from PointClickCare’s system through login credentials provided by the common customer and assigned to Real Time’s bots. The bots reduce Real Time’s time and labor to download and analyze the information. Some of the downloaded information is available through standards-based application programming interfaces (APIs) required for certification under ASTP’s Health IT Certification Program while other information, such as certain customizable point-of-care data, is only available through bespoke access methods.
In November 2022, PointClickCare began presenting the access control Completely Automated Public Turing Test to Tell Computers and Humans Apart (CAPTCHA) to users that PointClickCare thought were bots based on historical usage. CAPTCHAs are designed to ensure that bots cannot log in to online platforms. The CAPTCHAs displayed text or puzzles for the user to decipher to access the EHR. PointClickCare stated that it implemented the CAPTCHAs to address security and system performance issues related to bots.
In October 2023, PointClickCare began presenting allegedly indecipherable CAPTCHA images that could not be solved by humans to certain users. Real Time’s users could generally not decipher the images and access information stored in PointClickCare’s system. When the CAPTCHAs were not solved, Real Time would lose access to accounts.
The parties began discussing an agreement for alternative access methods, including a “USCDI connector” and “Marketplace API” that would enable access to about 30% of the data that Real Time stated it needed for its analytics services. The US Core Data for Interoperability (USCDI) is a standardized data set that is available through certain APIs certified under the ASTP’s Health IT Certification Program. To address Real Time’s additional data requests, the parties also discussed data export services from PointClickCare. The parties exchanged drafts of an agreement, but negotiations ended without an executed agreement. The Fourth Circuit’s decision indicates that PointClickCare ended the negotiations.
After Real Time determined that it could not reach a negotiated business deal, Real Time sued PointClickCare on January 9, 2024, alleging unfair competition, tortious interference with Real Time’s contracts with skilled nursing facilities, and several other claims that were not at issue on appeal to the Fourth Circuit. The district court concluded that Real Time demonstrated a likelihood of success on the merits of its Maryland unfair competition claim and tortious interference claims and issued an injunction to stop PointClickCare from using indecipherable CAPTCHA images and deactivating Real Time’s EHR system accounts. The district court’s analysis of the unfair competition claim focused on whether PointClickCare’s deployment of indecipherable CAPTCHAs amounted to unfair competition in the health care analytics market through information blocking that violates the Cures Act. The district court rejected PointClickCare’s position that its use of CAPTCHA images and related practices did not violate the Cures Act because they satisfied the health IT performance, security, and manner exceptions of the information blocking regulations. PointClickCare appealed the district court decision to the Fourth Circuit.
Fourth Circuit Information Blocking Analysis
On appeal, the Fourth Circuit reviewed the Maryland unfair competition claim that was based on a finding of an information blocking violation. The Court first concluded that a federal statute (i.e., the Cures Act) without a private right of action can support a Maryland unfair competition claim and that the Cures Act does not preempt state law claims.
Like the district court, the Fourth Circuit noted that PointClickCare conceded that using indecipherable CAPTCHAs meets the Cures Act’s definition of information blocking absent an applicable exception. The Court then turned to an analysis of whether PointClickCare’s deployment of indecipherable CAPTCHAs is information blocking that does not meet the manner, security, and health IT performance exceptions. The Fourth Circuit decision is most noteworthy for its interpretation of ambiguous language under the manner exception, the impact of which could extend well beyond the dispute between Real Time and PointClickCare.
Manner Exception
To meet the manner exception, an actor (such as PointClickCare) must fulfill a request for electronic health information in any manner requested, unless the actor is technically unable to fulfill the request or cannot reach agreeable terms with the requestor to fulfill the request in the manner requested. If an actor does not fulfill the request in the manner requested because it is technically unable to fulfill the request or cannot reach agreeable terms with the requestor to fulfill the request in the manner requested, the actor must fulfill the request in an alternative manner. The exception requires the actor to fulfill the request without unnecessary delay in an alternative manner in the following order of priority, and to only proceed to the next manner if the actor is technically unable to fulfill the request in the prior manner:
- Using technology certified to standards adopted by ASTP for the Health IT Certification Program
- Using content and transport standards specified by the requestor and published by the federal government or a standards developing organization accredited by the American National Standards Institute
- Using an alternative machine-readable format, including the means to interpret the electronic health information, agreed upon with the requestor.
In the Fourth Circuit’s analysis of whether PointClickCare’s attempt to negotiate an access agreement with Real Time met the manner exception, the Court interpreted the language of the exception differently than some actors and requestors have interpreted it since its adoption. For example, the Court interpreted the phrase “cannot reach agreeable terms” in the exception’s manner requested prong to require an actor to engage in “good-faith,” “reasonable,” and “genuine” efforts to reach an agreement over any manner requested and to have “articulable reasons why the parties cannot come to an agreement.”
PointClickCare in its petition for rehearing, and AHA and EHRA in their amici brief supporting the petition, argued that the manner exception does not require actors to negotiate or make any level of efforts to reach agreeable terms. In their view, pointing to HHS preamble guidance, the manner exception is intended to allow the parties to mutually agree on a market-based information sharing solution or, if not, to permit the actor to fulfill a request through a standards-based manner such an API or export technology certified to standards of the ASTP’s Health IT Certification Program. They asserted that “HHS crafted the Manner Exception to allow requestors to receive nonstandard access only when they agree to the actor’s terms.”
The Fourth Circuit also addressed whether an alternative manner, such as use of certified technology under the first alternative manner, must provide all of the information requested by the requestor even if the standard for the certified technology does not include all of the requested information. The Fourth Circuit concluded that the standards-based API offered by PointClickCare during negotiations was insufficient because the API only provided about 30% of the information sought by Real Time. Instead, the Court concluded that PointClickCare must meet the manner exception for each category of requested information. In contrast, PointClickCare (and AHA and EHRA in their amici brief) argued that offering any alternative manner under the alternative manner prong complies with the manner exception because ASTP intended to favor standards-based solutions.
Under the current information blocking regulations, if the actor and requestor are unable to agree on an alternative manner and meet the manner exception, the actor can potentially meet another exception such as the infeasibility exception, which includes a manner exception exhausted condition for circumstances where an actor offers alternative manners but cannot reach agreement with a requestor. The district court and Fourth Circuit did not address whether PointClickCare met the infeasibility exception based on the requirements of the manner exception exhausted condition. It appears that PointClickCare did not raise the condition because the indecipherable CAPTCHAs were in place before the February 8, 2024, effective date of the final rule that added the manner exception exhausted condition to the infeasibility exception. For more information about the condition, see our On the Subject regarding ASTP’s Health Data, Technology, and Interoperability: Certification Program Updates, Algorithm Transparency, and Information Sharing (HTI-1) final rule.
Health IT Performance and Security Exceptions
After rejecting PointClickCare’s position that it met the manner exception, the Fourth Circuit turned to the health IT performance and security exceptions. The Court determined that PointClickCare did not meet these exceptions because, among other reasons, they require a practice to be “implemented in a consistent and non-discriminatory manner.” Like the district court, the Fourth Circuit concluded that PointClickCare’s bot-prevention practices were targeted at Real Time and “correspond[ed] with PointClickCare’s entrance into the field as a competitor.” The court noted that PointClickCare failed to articulate a specific security risk posed by Real Time’s bot access, stating that arguments that broadly pointed to the potential malicious use of bots were insufficient. The Fourth Circuit also noted that PointClickCare never sued a customer to enforce its customer contract provisions prohibiting bots.
Next Steps
Actors seeking to avoid state law claims similar to those made by Real Time should consider the following steps:
- Maintain a log or other documentation of attempts to negotiate an agreement with requestors, particularly requestors seeking bespoke solutions.
- Maintain documentation of the technical requirements and anticipated resources needed for any requested solution.
- Implement consistent, repeatable procedures regardless of whether a requestor is a competitor for any product or service.
- Conduct any vendor security assessments for bespoke data access solutions in accordance with a security policy that is tailored to documented security risks and consistent with the information blocking regulations’ security exception.
- Document any system performance issues caused by third-party applications to support assertions of the health IT performance exception.
Requestors seeking access to electronic health information should consider the following steps in light of the Fourth Circuit decision:
- Obtain a representation and warranty or other assurance that the customer has contractual rights from the certified health IT developer or other data source to provide the requestor with access to the health IT.
- Determine whether the developer offers APIs or other standards-based interoperability elements that meet the requestor’s needs.
- If a bespoke solution is needed, seek a nondisclosure agreement to present the use case to the developer and seek a development or access agreement under the manner exception.
- Document all steps to seek and negotiate an agreement and any corresponding steps (or non-responsiveness) by the health IT developer.
- If an actor will not agree to a commercially reasonable manner that provides the electronic health information requested, the requestor should consider available options to incentivize the actor to provide the requested information, including prelitigation remedies and potential state law claims in light of the Fourth Circuit’s decision.
For more information about compliance with the Cures Act’s information blocking prohibition and state laws with potentially similar prohibitions, contact any of the authors of this On the Subject or your regular McDermott lawyer.

Tell Us Your Secret: Case Dismissed for Failure to Identify Trade Secrets
ARTICLE
Tell Us Your Secret: Case Dismissed for Failure to Identify Trade Secrets
May 1, 2025
Read time: 4 min
The US Court of Appeals for the Tenth Circuit affirmed a district court’s grant of summary judgment in favor of the defendants for the plaintiff’s failure to identify the trade secrets at issue with sufficient particularity. Double Eagle Alloys, Inc. v. Hooper, Case No. 24-5089 (10th Cir Apr. 22, 2025) (Bacharach, Seymour, Phillips, JJ.)
Double Eagle and Ace Alloys are direct competitors and distributors of specialty metals for companies in the oil and gas industry. After working for Double Eagle for decades, including five years as an inside sales manager, Michael Hooper left to join Ace. As he departed, Hooper took with him 2,660 digital files downloaded from his Double Eagle computer to an external storage device. After discovering the download, Double Eagle sued Hooper and Ace for trade secret misappropriation and civil conspiracy. The parties cross moved for summary judgment.
Double Eagle argued that the files Hooper downloaded contained financial, technical, and business information that qualified as trade secrets. Double Eagle categorized the files as pump-shaft-quality (PSQ) specifications, pricing, and customer drawings. Ace argued that the alleged trade secrets were not protectable since Double Eagle shared the information with customers or posted the information online. The district court granted summary judgment to the defendants on all claims, holding that “Double Eagle failed to identify its alleged trade secrets with sufficient particularity and clarity to proceed to trial,” that it failed to present evidence of the information’s secrecy to support the misappropriation claim, and accordingly that there was no underlying tort on which to base the claim for civil conspiracy. Double Eagle appealed.
Double Eagle argued that the summary judgment grant was improper because there were genuine issues of material fact on the issue of whether it identified its trade secrets with sufficient particularity and whether the business information was confidential. Double Eagle also argued that the district court erred by not allowing it an opportunity to supplement the evidence in support of its claim. The Tenth Circuit disagreed and affirmed on all counts.
The Tenth Circuit agreed with the district court that Double Eagle failed to introduce evidence that its alleged trade secrets were “known only to a limited number of people, were not readily ascertainable, or were valuable because they were not widely known.” The Court noted that Double Eagle’s PSQ specifications were readily ascertainable through proper means, its pricing was shared with customers without any protection to prevent customers from sharing those prices, and the customer drawings originated from the customers and were not owned by Double Eagle.
The Tenth Circuit similarly agreed with the district court’s dismissal of the misappropriation claim, explaining that the same lack of secrecy that defeated the trade secret claim also defeated the misappropriation claim. Finally, the Court rejected Double Eagle’s argument concerning its ability to supplement the record because the district court invited the parties to submit briefing on the issues, including an opportunity to move for leave to submit more evidence, but Double Eagle chose not to do so. Having rejected Double Eagle’s arguments on the first two claims, the Court necessarily rejected the civil conspiracy claim for lack of an underlying tort in support of the alleged conspiracy.

UK Serious Fraud Office Issues Significant New Guidance on Corporate Self-Reporting – What It Means for Your Business
ARTICLE / CLIENT ALERT
UK Serious Fraud Office Issues Significant New Guidance on Corporate Self-Reporting – What It Means for Your Business
April 30, 2025
Read time: 12 min
On 24 April 2025, the SFO published new guidance1 for companies in relation to self-reporting, co-operation, and when they can expect to be invited to engage in negotiations for a Deferred Prosecution Agreement (DPA) as an alternative to being prosecuted (the Guidance).
The Guidance provides a clear statement of the SFO’s key considerations in deciding whether a prosecution or a DPA is in the public interest.2 Those considerations include “whether, when and how” a company self-reports suspected offending, and the degree to which it co-operates with the SFO investigation. As summarised below, much of this reflects previous guidance and pronouncements by the SFO.
However, the Guidance goes further than before by explicitly stating that:
- if a company “self-reports promptly” and “co-operates fully”, the SFO will “invite it to negotiate a DPA rather than prosecute, unless exceptional circumstances apply”;3 and
- the SFO will “consider” inviting to DPA negotiations companies that have not self-reported where they go on to provide “exemplary co-operation” with its investigation.4
Both points represent public confirmation of what was, in substance, already happening in practice and are consistent with the DPAs concluded by the SFO to date. For the first time, the Guidance also sets out the case progression timescales that a self-reporting company can expect the SFO to follow.
Self-Reporting – Timing
The SFO views self-reporting suspected corporate criminal conduct as a “mark of a responsible organisation”5 and notes that a “prompt” self-report “always weighs heavily in favour of a DPA”.6 On the other hand, a failure to self-report suspected offending within “a reasonable time of it coming to light” will negatively impact the public interest assessment.7
What amounts to “a reasonable time” will depend on the circumstances. The Guidance accepts that a company may wish to take steps to investigate the suspected offending before self-reporting.8 However, the SFO does not expect a company to wait to complete its investigation prior to self-reporting. The length of time that it may reasonably take to investigate the matter before then will be a sliding scale which depends on the evidence that emerges:
If there is direct evidence of corporate offending, we would expect a corporate to self-report soon after learning of that evidence. If the position is less clear-cut we recognise that some further investigation may be necessary. 9
SFO Director Nick Ephgrave added some colour on this in a speech on the day the Guidance was launched:
As soon as you have reasonable suspicion – it doesn’t have to be ‘beyond reasonable doubt’, doesn’t have to be ‘on the balance of probabilities’, just reasonable suspicion you’ve got some offending going on – that’s the point at which you stop, that’s the point at which you talk to us. 10
The Guidance does not expand on what “prompt” amounts to, whether this means any earlier than within “a reasonable time”, or whether it still allows for a degree of investigation by the company. In practice, the advantages of taking initial steps to better understand the nature and extent of any offending prior to self-reporting are likely to outweigh any potential downsides, provided the initial investigation moves quickly. Companies should ensure that the necessary arrangements are in place for the board (and/or any other relevant governance forum) to approve the making of a self-report as soon as a “reasonable suspicion” (in the Director’s words) has emerged.
A company which submits a Suspicious Activity Report to the National Crime Agency (e.g. under the provisions of the UK Proceeds of Crime Act 2002 (POCA), or makes a report to another UK or overseas agency, should also report to the SFO “simultaneously or immediately thereafter”. Failure to do so means that it will not gain credit from the SFO for self-reporting. Bearing in mind the very low threshold for reporting a suspicion to the NCA under POCA, this may well give rise to challenges in practice. It should also be borne in mind that the SFO will generally only investigate and prosecute serious crime, so this requirement should not be misinterpreted as giving rise to a general expectation that all levels and types of suspected misconduct should be reported to the SFO.
Self-Reporting – Content
On the content of a self-report, the Guidance states that companies should provide information which enables the SFO to “understand the nature and extent of the suspected offending.” 12 This will include identifying all known facts and evidence, the individuals involved and the relevant jurisdictions.
The SFO also expects to receive information at the self-reporting stage on the location of key material and “any risks associated with the destruction of key evidence…” 13 If the SFO has concerns about potential document destruction, the implicit risk is that it takes intrusive steps to secure the material itself (e.g. a ‘dawn raid’).
Accordingly, companies conducting an initial investigation with a view to self-reporting should carefully document the methodology used to identify and preserve potentially relevant material and be prepared to justify this to the SFO in relatively short order.
Timelines
For the first time, the SFO has set out certain case-progression timescales following a self-report.14 The SFO will seek to:
- contact a self-reporting company within 48 business hours of a self-report;
- decide whether to open an investigation within 6 months;
- conclude its investigation “within a reasonably prompt time frame”;15 and
- conclude DPA negotiations within six months of sending an invitation.
Co-operation
A prompt self-report is not sufficient to secure a DPA invitation – the company “must go on to provide genuine co-operation to be eligible be invited to negotiate a DPA.”16
On the other hand, a company that does not self-report may still qualify for a DPA invitation if it provides “exemplary co-operation” (emphasis added). This is consistent with previous cases demonstrating that a DPA (and full 50 per cent penalty discount) could be secured, in the absence of a self-report, through an “extraordinary”17 or “exemplary”18 level of co-operation.
Paragraph 22 of the Guidance provides the following non-exhaustive list of hallmarks of co-operative conduct:
- Proactively and promptly preserving all digital and hard copy material likely to be relevant to the SFO investigation.
- Collecting and identifying documents and information likely to be relevant to the SFO investigation. Non-exhaustive examples include:
- Providing a list of relevant custodians and the location of material (whether hardcopy or digital);
- Identifying and/or producing relevant overseas documents within the company’s control;
- Identifying potentially relevant third-party material; and
- Providing translations of relevant foreign language documents.
- Presenting the facts on the suspected criminal conduct, including identifying all persons involved, both inside and outside of the company.
- If the company undertakes an internal investigation:
- Engaging early with the SFO as to the parameters of the investigation;
- Informing the SFO in advance of proposed investigation steps (such as interviews) and not taking any step which might prejudice the SFO investigation. The Guidance envisages discussing at the outset which steps the SFO would like to be consulted on and those where that is unnecessary;
- Providing timely updates including any key findings;
- Providing the facts gathered during the investigation;
- Providing non-privileged records of interviews. If the company claims that interview records are subject to privilege, a voluntary waiver “will weigh strongly in favour of co-operation”;
- Refraining from interviewing employees at the SFO’s request; and
- Notifying the SFO of the involvement or interest of any other authority.
- Informing the SFO of any previous relevant corporate criminal conduct and how it was resolved.
- Providing information on any disciplinary action and personnel changes made because of the offending.
- Providing financial information regarding the benefit and/or harm the offending has caused.
- Presenting a thorough analysis of the company’s compliance programme at the time of the offending and how it has remediated, or plans to remediate, any ongoing deficiencies.
- Assisting the SFO to access employees for the purposes of their interviews and ensuring, where appropriate, independent legal advice is made available to employees.
Interestingly, the Guidance states that a company which takes all the above steps is “likely to be assessed as providing exemplary co-operation”. If a company is assessed in this way, the SFO will “consider” inviting it to DPA negotiations, even where it has not self-reported. However, in practice, it would likely be a high-risk approach for a company to make a tactical decision not to self-report and then seek to make up for that deficit later by relying on the above as a roadmap to a DPA via exemplary co-operation. Such an approach may be looked on poorly by the SFO when making its overall public interest assessment, particularly against the backdrop of the SFO Director starkly warning companies that “If you have knowledge of wrongdoing, the gamble of keeping this to yourself has never been riskier.”20
A company will not be penalised for maintaining a valid privilege claim over relevant material, but the SFO will consider a voluntary waiver of privilege “a significant co-operative act.”21 Companies considering privilege waivers will need to carefully weigh the potential benefits in terms of co-operation credit against the wider risks of waiver on a case-by-case basis.
Non-Cooperative Conduct
The Guidance also gives examples of non-cooperative conduct, including delaying providing information or material for tactical reasons, seeking to overload the SFO investigation with unnecessarily large volumes of material, and attempting to withhold the full extent of the suspected offending.
Two further examples caution against what the SFO would appear to view as unreasonably ‘tactical’ approaches to multi-jurisdictional investigations, namely “‘forum shopping’ by unreasonably reporting offending to another jurisdiction” and “[s]eeking to exploit differences between international law enforcement agencies or legal systems.”22 As it is not immediately clear what the Guidance has in mind on the latter point, the extent to which companies (and their external counsel) will need to be mindful of this when engaging with the SFO alongside overseas authorities remains uncertain.23
What Are “Exceptional Circumstances”?
The Guidance concludes by reiterating that “it will only be in exceptional cases that the combination of a prompt self-report and full co-operation will result in prosecution rather than an invitation to discuss a DPA.”24 The Guidance is silent as to what exceptional circumstances the SFO might have in mind. While this maintains the SFO’s flexibility to address the specific circumstances of a given case, two potentially helpful reference points may be:
- The Skansen Interiors Limited (Skansen) case where the company was prosecuted by the Crown Prosecution Service despite self-reporting co-operating with the investigation. The CPS took the view that as a dormant company Skansen would be unable to pay a fine or otherwise comply with the terms of any DPA, whereas a prosecution would send a message to smaller companies about the importance of adequate anti-bribery and corruption procedures. The SFO may choose to adopt a similar approach in cases where the terms of a DPA could not be complied with by the company and where this could not be mitigated by obtaining appropriate parent company undertakings.25
- The public interest factors in favour of prosecution detailed in the DPA Code of Practice26 and Corporate Prosecutions Guidance.27 These include a history of similar conduct and pervasiveness of the conduct within the company. The Guidance28 leaves open the possibility that, in certain cases, one of, or a combination of, these factors may prove determinative.
Conclusion
A DPA in any given case ultimately remains subject to judicial approval through a declaration that it is in the interests of justice and its terms are fair, reasonable and proportionate.29 The Guidance therefore goes effectively as far as the SFO could in seeking to make the path to a DPA (or at least a DPA invitation) clear and transparent while maintaining some flexibility in recognition that each case will turn on its own facts.
It remains to be seen if this will be sufficient to move the dial and incentivise a new wave of corporate self-reporting. Deciding whether to self-report remains a highly fact-sensitive exercise where companies must carefully weigh the potential benefits of self-reporting against what are often very significant downsides. The Guidance spells out the SFO’s high expectations in terms of the speed of reporting and the requisite degree of co-operation. This is no small undertaking.
Companies may therefore wish to ensure that boards are pro-actively briefed on the principles and practical implications of self-reporting, ahead of any specific decision. This would reflect the Guidance but also broader considerations including, for example, remarks by the judge approving the DPA between the SFO and Amec Foster Wheeler Energy Limited that the board’s failure to self-report was “deplorable” and the “proper course” would have been to do so “as a matter of ethical corporate governance”.30 To this extent, it may be considered prudent to appraise board members of these issues and expectations, whether or not an incident has occurred.
Indeed, it is likely that boards may be faced with difficult dilemmas such as this ever more frequently, given a landscape featuring broad new legislation (such as the failure to prevent fraud offence),31 increased international co-operation,32 heightened scrutiny from auditors, civil society and other stakeholders, (potentially) newly-incentivised whistleblowers33 and aggressive competitors and litigation funders.
Even though the recent SFO announcement does not change matters fundamentally, senior management should familiarise themselves with the relevant principles in case matters arise which require quick decision making. In doing so, they should not ignore the fact that the enforcement landscape in the UK is changing rapidly, against a background where the SFO has recently acquired sweeping new powers to prosecute companies (including foreign companies) in ways that were not previously possible. The SFO’s announcement is therefore carefully timed and should be viewed as part of an increasingly co-ordinated and determined strategy to respond to corporate crime.

European Health & Life Sciences Symposium 2025: Key takeaways
ARTICLE
European Health & Life Sciences Symposium 2025: Key takeaways
April 2, 2025
Read time: 5 min
In April 2025, we were proud to host the annual European Health & Life Sciences Symposium at the Shangri-La hotel in Paris. Attended by some 300 delegates from across the industry, participants including investors, innovators, finance providers and advisers enjoyed a wide-ranging agenda covering everything from transaction trends and financing innovation through to navigating policy shifts and identifying investment opportunities.
In an era of intense innovation at the intersection of technology and biology, the healthcare industry is witnessing unprecedented advancements that present exciting openings for investors. “The dynamic world of companies applying innovative technology platforms to reshape drug discovery and patient care is presenting a new wave of investment opportunities,” says Anne-France Moreau, partner at McDermott.
Latest Innovation Trends
Two key segments of the health and life sciences ecosystem were identified as optimising growth and development and creating investment opportunities. First, the symposium heard about the TechBio space, where technology platforms and solutions support drug discovery and drug development. Second, the opportunities related to solutions and technologies that support healthcare and pharma services were discussed.
The primary goal of TechBio solutions is speed, with these technologies enabling for the acceleration of drug discovery, clinical trials and commercialisation. At the same time, these businesses aim to derisk the process of identifying potential drugs and assets by improving the chances of success. Ultimately, the focus is on improving the lives of patients that need these therapies, though the use of emerging tech.
The buzz around the application of AI and computer science in biology has attracted new types of investors into TechBio and pharma services, with tech-focused capital coming from venture capital into the biotech space. We have seen a surge in company creation in technology-enabled healthcare, but it covers such a wide range of innovations and business models, it can be complex for investors to navigate.
Assessing Opportunities
Considering the key metrics for assessing opportunities in TechBio, investors spoke about the need to look not only at the assets being developed but also the data that has been generated, though the specifics will vary by business model.
While there is a temptation for TechBio companies to be both services and biotech businesses, that is difficult for investors who tend to come from one side or another.
Those that actively invest in services are less likely to be willing to take on binary regulatory or clinical risk exposures, for example.
In pharma services, investors are looking at indicators that include the client base, recurring revenues, scalability, management team and the pathway to profitability. Often they will focus in on the financial metric that will be used for valuation by an acquirer, which may be earnings but might also be annual recurring revenues. And investors look for partners with realistic valuation expectations.
Investors in these types of companies often look for business moats that are idiosyncratic, whether those are technology, IP, clinical data or regulatory approvals that will give a competitive advantage.
Access to data can be a key policy issue for these businesses, which often rely on some combination of molecular, clinical and biological data. Discussions around sourcing reliable data, complying with relevant regulatory frameworks and protecting intellectual property will be important.
Challenges for Investors
While there is much excitement about the application of AI tools in drug development, the innovators present highlighted the fact that AI can only work with past data and the quality of the data set is critical, so genuine innovation is challenging. Likewise, areas like cell and gene therapy are new and complex areas so the technology and proof of concept is still to be developed, which can be challenging for investors.
There is also a risk that AI and machine learning tools may become commoditised over time, so valuations should not necessarily be based on those technologies but rather on new molecules, clinical data, growth rates and management capabilities. Any use of AI needs to pay close attention to ethics, with clear accountability, responsibility and human decision-making.
Where investors see a multiplication of risk around new technologies in drug development, biotech businesses often find it easier to turn to big pharma for funding because they are more able to get comfortable with that risk. However, some TechBio businesses have platforms that they wish to license to big pharma and seek partnerships, which can create challenges for exit models.
Monika Richter, partner with McDermott, says: “There are many opportunities for investors to leverage innovations in TechBio and pharma services that have the potential to improve drug development processes and patient outcomes. These are exciting and complex emerging areas that are attracting new investors into the healthcare space, but the legal and regulatory frameworks are co-developing in real time, creating a dynamic environment that needs to be navigated with care.”

Executive Order implications for 501(c)(3) status
ARTICLE / US POLICY
Executive Order implications for 501(c)(3) status
April 29, 2025
Read time: 3 min
Media reports about the Trump administration’s desire to revoke the tax-exempt status of prominent charitable organizations recently jolted the United States’s nonprofit community with anxiety over the impact potential changes to exemption standards could have on the financial stability and operational effectiveness of these organizations. While the Trump administration stated on April 22, 2025, that no executive orders concerning exemption standards are “being drafted or considered at this time,” many nonprofit hospitals, academic medical centers, and other charitable organizations are still analyzing the effect that existing executive orders have on the services and programs they provide.
Existing executive orders focusing on diversity, equity, and inclusion (DEI) programs; gender-affirming care humanitarian programs; and other activities each contain language that suggest organizations that fail to comply fully with the administration policies expressed by these executive orders risk heightened scrutiny from the Internal Revenue Service (IRS) or others regarding their exempt status.
This guide examines these existing executive orders and their relationship with IRS precedent governing charitable status through a series of frequently asked questions (FAQs). These FAQs accomplish the following:
- Identify existing executive orders that may affect the activities of charitable organizations
- Describe how charitable organizations might navigate the current environment
- Explore IRS precedent on how public policy influences the definition of “charitable” for tax purposes
- Consider how illegal activities may affect charitable status
- Summarize how a charitable organization can lose its tax-exempt status and the process that the IRS must follow
- Offer considerations for questions charitable organization leaders should ask as they prepare for potential scrutiny over compliance with executive orders.
FAQs Preview
Are all nonprofit organizations exempt from federal taxation?
No. Labeling an organization as “nonprofit” refers to its status under state corporate law, such as a nonprofit corporation. Not all nonprofit organizations qualify for tax-exempt status. Instead, a nonprofit organization must satisfy strict criteria set forth in the Internal Revenue Code (Code) to be exempt from federal taxation.
Plus, more frequently asked questions:
- What executive orders potentially affect the activities of charitable organizations?
- How concerned should hospitals, health systems, and other 501(c)(3) entities be about the current environment?
- How could a charitable organization lose its tax-exempt status?
- Could the Trump administration redefine the standards for charitable organizations?
For more information, or if you have additional questions, please contact Travis Jackson or Robert C. Louthian, III.

Washington State Enacts Merger Review Regime
ARTICLE / CLIENT ALERT
Washington State Enacts Merger Review Regime
April 28, 2025
Read time: 5 min
Washington is the first state to enact the Uniform Antitrust Premerger Notification Act, which requires merging parties that submit a federal filing under the Hart-Scott-Rodino (HSR) Act (15 U.S.C. Sec. 18(a)) to also submit the HSR filing to the Washington attorney general if the deal has a sufficient nexus to Washington. The requirements will go into effect on July 27, 2025, making Washington the first state to have a merger filing notification requirement applicable to parties from all industries.
Why It Matters
Many states have merger notification requirements for certain industries. For healthcare transactions, for example, 15 states (including Washington) have either existing or pending requirements. Furthermore, state attorneys general have indicated they will continue to pursue merger enforcement, both in coordination with federal enforcers and on their own in state court. However, until Washington did so this month, no state had enacted a merger reporting policy applicable to all industries.
Understanding the Act
On April 4, 2025, Washington Governor Bob Ferguson signed into law the Uniform Antitrust Premerger Notification Act (the Act). The Act is based on the model act produced by the Uniform Law Commission, an organization that drafts model laws to boost uniformity across states.
Washington continues a trend of government agencies and jurisdictions requiring notice of mergers and acquisitions. For example, in 2023, Congress added a requirement in the National Defense Authorization Act, which now requires parties to provide their HSR materials to the US Department of Defense (DoD) for any proposed merger or acquisition that will require DoD review. Furthermore, the legislatures in six other states – Colorado, Nevada, California, Utah, West Virginia, and Hawaii – and in the District of Columbia have introduced and are considering legislation consistent with the Uniform Antitrust Premerger Notification Act.
Below are the notable aspects of the Act that companies operating in or conducting transactions with business in Washington should be aware of, including:
- Scope of required submission. The Act requires the merging parties to submit only their HSR filing and attachments. It does not require that the parties produce any additional documents beyond the initial filing. Further, if the transaction was not HSR-reportable, it does not require reporting under the Act.
- Filing requirement and Washington nexus. A filing under the Act is only required if a federal HSR filing was made and at least one of the following requirements for Washington nexus is satisfied: (i) the person has its principal place of business in the state; (ii) the person or a person it controls directly or indirectly had annual net sales in Washington of the goods or services involved in the transaction of at least 20% of the HSR filing threshold (varies year to year, but is $126.4 million in 2025); or (iii) the person is a healthcare provider or provider organization (defined by state law) conducting business in Washington. Note, every party to a transaction may not be required to file under the Act. Only parties that meet one of the three requirements must file notice with Washington. However, this also means that merging parties that conduct any business related to the transaction in the state will need to track sales in Washington to determine whether they fall under requirement (ii).
- No waiting period or filing fee. The Act only requires notice. There is no waiting period and there is no filing fee. Filing parties, therefore, are not obligated to wait for any approval or decision to close the transaction after notifying the Washington attorney general.
- Penalties for noncompliance. Violations of the Act can carry a civil penalty, enforced by the Washington attorney general, of up to $10,000 per day of noncompliance. However, beyond enforcement of the Act itself, the Act contains no additional substantive enforcement powers for the Washington attorney general.
- Confidentiality and information sharing. The Act contains privacy provisions for parties submitting the HSR form and attachments pursuant to the Act, including preventing the Washington attorney general from disclosing any submissions and the fact that the form was filed or provided under the Act. The Act also exempts the submissions from public review under Washington’s Public Records Act (Chapter 42.56 RCW). However, the Act permits the Washington attorney general to share this information with the Federal Trade Commission, the US Department of Justice, and the attorney general of another state that enacts the Uniform Antitrust Premerger Notification Act, or a substantively equivalent act, so long as their confidentiality provisions are at least as protective as the Act.
For more information on the impacts of Washington state’s Uniform Antitrust Premerger Notification Act, please contact one of the authors or your regular McDermott lawyer.
