ARTICLE / CLIENT ALERT
New York Assembly Passes Restrictive Health Information Privacy Act
January 24, 2025
Read time: 10 min
For more information related to state privacy laws, please visit McDermott’s Global Privacy & Cybersecurity Resource Center, a one-stop shop for timely webinars, thought leadership, and insights covering critical developments that impact data privacy and compliance worldwide.
On January 22, 2025, the New York Assembly passed Senate Bill S929, titled the New York Health Information Privacy Act (New York HIPA). The act is now on its way to Governor Kathy Hochul for her signature.
If signed into law, New York HIPA will impose strict requirements on entities that handle health or wellness-related consumer data and shares a number of similarities with Washington state’s My Health My Data Act (MHMDA), another far-reaching consumer health data privacy law. Both New York HIPA and the Washington MHMDA have significant implications for entities operating in various sectors, including advertisers, mobile app providers, wearable device providers, wellness and nutrition companies, and processors handling health information. While New York HIPA exempts Health Insurance Portability and Accountability Act (HIPAA)-covered entities, this exemption only applies to the extent that covered entities are processing HIPAA-protected health information (PHI). Therefore, while patient medical records for example may be excluded from the law’s application, other personal information medical providers and their business associates collect that has historically not been treated as PHI is likely to be subject to its provisions.
New York HIPA prohibits companies and nonprofits from selling an individual’s regulated health information without their consent. More significantly, the act prohibits entities from processing regulated health information unless such processing is “strictly necessary” for providing or maintaining a requested service or product, or if that collection and processing otherwise fits within a very narrow set of exemptions. For all other collection and processing, entities must obtain prior authorization via a lengthy form that must be delivered to consumers separately from any other transaction. This authorization is revocable and must expire after one year.
We discuss the key features and requirements of New York HIPA below, alongside notable comparisons to the MHMDA.
Key Features and Requirements
New York HIPA contains several key features that, if signed into law, will make it one of, if not the, broadest state consumer health privacy laws:
I. A Uniquely Broad Definition of Regulated Health Information
New York HIPA’s definition of regulated health information encompasses an extremely broad range of non-HIPAA-regulated data, from an individual’s personal wellness habits to their purchase histories. It also includes location and payment information that “relates to an individual’s physical or mental health” as well as “any inference drawn or derived about an individual’s physical or mental health that is reasonably linkable to an individual.” While the Washington MHMDA uses a similarly broad definition for “consumer health information,” the MHMDA specifically carves out public data, research data, and information regulated under the Gramm-Leach-Bliley Act. Significantly, New York does not exempt these types of data, nor does it exempt HIPAA-covered entities or business associates in their entirety, or financial entities, such as banks, credit card companies, credit unions, and other institutions involved in handling payment information.
II. An Equally Broad Definition of Regulated Entities
New York HIPA’s scope is quite broad, in that it will regulate any for-profit or not-for-profit entity, regardless of size, that (a) controls the processing of regulated health information of an individual who is a New York resident, (b) controls the processing of regulated health information of an individual who is physically present in New York while that individual is in New York , or (c) is located in New York and controls the processing of regulated health information. Under this definition, any company that collects non-HIPAA-regulated health, wellness, or nutritional information pertaining to a New York resident, or even such information pertaining to a visitor while they are in the state, is considered a regulated entity. New York HIPA can be interpreted so broadly as to cover non-New York entities processing non-New York-related data of non-New York residents, simply because those individuals happen to be located in New York at the time of processing.
III. Narrow Restrictions on What Constitutes “Strict Necessity” for Purposes of Collection and/or Processing
New York HIPA requires regulated entities to obtain “valid authorization” to collect or process regulated health information, with a limited set of exemptions for processing activities that are “strictly necessary.” Under New York HIPA, processing is only strictly necessary when used to:
- Provide products or services requested by a customer
- Conduct certain limited internal business operations
- Protect against or detect security incidents or threats
- Protect the vital interests of the individual
- Investigate or defend against legal claims
- Comply with legal obligations
Notably, strict necessity expressly excludes “any activities related to marketing, advertising, research and development, or providing products or services to third parties.” New York HIPA intends to limit marketing and advertising without consumer authorization. However, the law is so broad that it is also likely to hamper the efforts of regulated entities to conduct general outreach that is helpful and, in many cases, necessary for consumers to become aware of new medications, research, and clinical trials.
IV. Onerous Authorization Requirements for Purposes of Collection and/or Processing
Because several routine collection and processing activities fall outside of what is “strictly necessary” under New York HIPA, many entities will need to obtain “valid authorization” from consumers. This authorization differs significantly from typical opt-in requirements in other state consumer privacy laws. A regulated entity’s request for a consumer to fill out this form must be obtained independently from any other transaction and cannot be made within the first 24 hours of a customer’s initial use of a requested product or service. This requirement effectively precludes regulated entities from offering products or services to customers during the initial account registration process, to the extent those products or services process any regulated health information.
Furthermore, if the authorization form pertains to multiple categories of processing activities, it must allow individuals to provide or withhold authorization for each activity and the form must not include any request for authorization for a processing activity for which an individual has previously withheld or revoked authorization within the past calendar year. This level of complexity significantly exceeds the scope of a typical opt-in function. In particular, the requirement to provide tailored forms that track when authorization was given and revoke such authorization after one year is likely to create numerous costly compliance issues for regulated entities and present significant challenges for their information technology teams.
According to New York HIPA, authorization may not be obtained by deceptive pattern or design (authorization may not be obtained via any mechanism “with the purpose or substantial effect of obscuring, subverting, or impairing an individual’s decision-making”), and the form itself must include a host of information, such as:
- The types of regulated health information to be processed
- The nature of the processing activity
- The purpose of processing
- The names or categories of service providers or third parties with which customer information may be shared
- A general disclaimer stating that failure to provide authorization will not interfere with a consumer’s experience of using the regulated entity’s products or services
- Any monetary or other valuable consideration a regulated entity may receive in connection with such processing
- An expiration date of the authorization
- The mechanism by which a consumer may revoke authorization
- The mechanism by which the individual may request access to and deletion of their regulated health information
- Any other information material to an individual’s decision-making regarding authorization for processing
- The signature (including an electronic signature) of the individual, or their parent or guardian if authorized by law
While this authorization form is meant to “clearly” disclose processing to individuals, it will likely be both onerous for regulated entities to create and manage and burdensome for customers to read and use.
V. Onerous Revocation and Notice Requirements
If a regulated entity is still able to collect or process regulated health information after navigating these various restrictions, it must also provide consumers with an effective, efficient, and easy-to-use mechanism to revoke authorization. Entities that provide consumers with online accounts must give them the ability to easily access, within their account settings, a list of all processing activities for which the consumer has provided authorization and allow the consumer to revoke authorization in the same place with one motion or action. While granting authorization is a weighty and complex process, revoking authorization must be as simple as a swipe of the finger. Upon receipt of such revocation, the regulated entity must “immediately” cease processing activities, subject to limited exemptions.
Significantly, regulated entities intending to offer new or materially altered processing activities must obtain new authorization for each activity. In essence, this requires regulated entities to assess whether updated products or services include “material changes” and, if so, to roll out new and updated authorization forms for each consumer of those updates. Moreover, because valid authorization cannot be granted within 24 hours of a consumer requesting a product or service, regulated entities will not, for example, be able to launch material app updates alongside a new authorization form. Instead, apps may be forced to request that consumers install the update, and then (at least a day later), provide notice of material processing changes alongside a request for authorization.
VI. Broad and Largely Unworkable Security Requirements
While New York HIPA would require regulated entities to develop, implement, and maintain reasonable administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of regulated health information, it lacks specific guidance on how regulated entities should verify consumer requests to access or delete their data. Without a defined verification process, regulated entities may be compelled to comply with all such requests (within 30 days) without sufficient grounds to decline a faulty or fraudulent request.
Furthermore, New York HIPA would permit third-party agents to act on a consumer’s behalf in making such requests, but it fails to provide a mechanism for a regulated entity to verify that third-party agent’s identity or that they are authorized to act on behalf of a specific consumer. This vulnerability could enable malicious actors to easily access an individual consumer’s health, wellness, and nutritional information for unauthorized and potentially harmful purposes.
VII. Wide-Ranging Investigatory Powers and Harsh Penalties
New York HIPA would grant the New York attorney general the authority to investigate suspected violations and bring enforcement actions. Such actions can result in civil penalties of up to $15,000 per violation or 20% of revenue obtained from New York consumers within the past fiscal year, whichever is greater, as well as other forms of relief. Although the New York HIPA does not offer a private right of action like the Washington MHMDA, this penalty structure is notably strong in comparison because the MHMDA authorizes the Washington attorney general to levy penalties of up to $7,500 per violation. This severe penalty structure, in conjunction with the confusing and occasionally conflicting requirements outlined above, could deter entities from offering services in New York and increase their compliance costs.
What’s Next?
New York HIPA will take effect one year after it is signed by the governor. Assuming it is signed into law, prior to its effective date, the New York attorney general may promulgate rules and regulations necessary to effectuate and enforce its provisions. McDermott will continue to keep you apprised of future developments, so stay tuned.
If you have questions or need assistance preparing for the new state consumer laws, please contact your regular McDermott lawyer or one of the authors.

Corporate Transparency Act Update: Nationwide Injunction Continues
ARTICLE / CLIENT ALERT
Corporate Transparency Act Update: Nationwide Injunction Continues
January 24, 2025
Read time: 3 min
What Happened?
On January 23, 2025, the Supreme Court of the United States issued a stay of the nationwide preliminary injunction against enforcement of the Corporate Transparency Act (CTA) (31 U.S.C. § 5336) and the Beneficial Ownership Information Reporting Requirements final rule promulgated thereunder (31 C.F.R. 1010.380), which had been originally entered by the US District Court for the Eastern District of Texas on December 3, 2024, in Texas Top Cop Shop, Inc. v. McHenry, No. 4:24-cv-00478 (E.D. Tex.) (formerly, Texas Top Cop Shop, Inc. v. Garland). As a result, the nationwide preliminary injunction against enforcement of the CTA and the final rule imposed in Texas Top Cop Shop was lifted pending disposition of the appeal in that case before the US Court of Appeals for the Fifth Circuit (and disposition of any petition for writ of certiorari in the Supreme Court).
However, on January 7, 2025, a separate nationwide injunction against enforcement of the final rule was issued by another District Court for the Eastern District of Texas in Smith v. US Department of the Treasury, No. 6:24-cv-336-JDK (E.D. Tex.). As of the time of writing this On the Subject, the order in Smith had not been appealed.
On January 24, 2025, following the Supreme Court’s ruling in Texas Top Cop Shop, the Financial Crimes Enforcement Network (FinCEN) issued an alert that, in light of the order in Smith, reporting companies are still not required to file beneficial ownership information with FinCEN and are not subject to liability if they fail to do so while the order remains in force. However, FinCEN explained that reporting companies may continue to voluntarily submit beneficial ownership information reports (BOIRs).
What Now?
Following FinCEN’s alert, we recommend that reporting companies continue to be prepared to comply with the CTA and submit BOIRs to FinCEN in the event the order in Smith ceases to apply as a result of a stay of the injunction pending appeal (which happened to the order in Texas Top Cop Shop). Even if the order in Smith ceases to apply, we expect FinCEN to grant a limited extension of any CTA reporting deadlines, as was done when the injunction in Texas Top Cop Shop was initially stayed by the Fifth Circuit on December 23, 2024.
McDermott will continue to monitor for relevant developments. If you have any questions or need advice on the CTA or its application to your business, please contact your primary McDermott lawyer or one of the authors of this article.

Data Privacy and Cybersecurity in 2025 Q&A Series
ARTICLE
Data Privacy and Cybersecurity in 2025 Q&A Series
February 2025
Read time: 2 min
Following our recent client alert, learn more about the topics that we are watching most closely as 2025 unfolds. Our global privacy and cybersecurity lawyers share further insights from working with clients on these key issues.
- Website Tracking: Elliot Golding and David Saunders share the common mistakes companies make when implementing cookie management practices (and how to avoid them) and how they help clients address concerns regarding website tracking technologies.
- PCI DSS 4.0: Mark Schreiber and Brian Long break down PCI DSS 4.0, the common misconceptions companies have about compliance with the security requirements, and how it impacts third-party vendors and service providers.
- EU Data Act and Cybersecurity Frameworks: Rosa Barcelo, Romain Perray, Julie Favreau, and Matúš Huba explain the nuances of the EU Data Act and the three EU cybersecurity frameworks (NIS2, DORA, and the Cyber Resilience Act), the common challenges they see their clients face, and how companies can prepare for compliance.

Corporate Transparency Act update: Supreme Court stays nationwide injunction but reporting still voluntary
ARTICLE / CLIENT ALERT
Corporate Transparency Act update: Supreme Court stays nationwide injunction but reporting still voluntary
January 24, 2025
Read time: 3 min
On Jan. 23, 2025, the US Supreme Court granted the request by the government for a stay of the injunction issued by the US District Court for the Eastern District of Texas in Texas Top Cop Shop, Inc. v. McHenry that enjoined enforcement of the Corporate Transparency Act and its implementing regulation (“Reporting Rule”).[1] However, on Jan. 7, 2025, a different federal judge in the same district court but in a different lawsuit brought by different plaintiffs issued an order staying the effective date of the Reporting Rule in Smith v. US Department of the Treasury.[2]
On Jan. 24, 2025, the US Department of the Treasury’s Financial Crimes Enforcement Network (“FinCEN”) clarified on its beneficial ownership information webpage that beneficial ownership information report (“BOI Report”) filings are still voluntary despite the US Supreme Court’s recent action. FinCEN also clarified that reporting companies are not subject to liability if they fail to file BOI Reports while the Smith order remains in force.
Accordingly, at this time, BOI Report filings for both existing entities and newly formed/registered entities are voluntary. Clients who defer filing BOI Reports should nonetheless continue to prepare for anticipated BOI Report filings in the event the nationwide stay issued in the Smith case is reversed, vacated or otherwise modified.
We will continue to monitor for developments related to the Reporting Rule, including developments related to these cases, and whether the Justice Department, the Treasury Department or FinCEN issues any additional guidance to assist clients in navigating any BOI Report filing obligations.
Authored by Melissa G.R. Goldstein, Betty Santangelo, Michael S. Didiuk, Jessica Romano, Kyle B. Hendrix, and Bryson Kern.
For assistance in navigating the CTA’s reporting requirements, please contact one of the authors or your attorney at McDermott Will & Schulte.

Hospital Provider-Based Compliance: Top 10 Myths and Truths
ARTICLE / CLIENT ALERT
Hospital Provider-Based Compliance: Top 10 Myths and Truths
January 23, 2025
Read time: 13 min
Medicare reimbursement for hospital outpatient services has come under attack in recent years, with a focus on “site neutral” payment policies that would pay hospitals for outpatient services furnished in off-campus locations at the same rates paid for similar services furnished in physician offices or other non-hospital settings. The December 18, 2024, bipartisan health package that was almost approved by Congress included a provision that would have required hospitals to submit “provider-based attestations” (PBAs) for all off-campus outpatient hospital locations in order to be paid as a hospital location. Many stakeholders consider this a “near miss,” and hospitals should expect that Congress will pass this provision and implement it in the near future. Now is the time to prepare for that eventuality. This On the Subject highlights PBA-related considerations and revisits 10 key myths and compliance challenges hospitals face in relation to provider-based status.
Hospitals are required to comply with the provider-based rules at 42 C.F.R. § 413.65 as a condition of receiving payment from Medicare. However, most hospitals are not currently required to obtain affirmative approval from the government prior to furnishing and billing for services at provider-based locations. PBAs are documents used by hospitals to evidence compliance with all elements of the Medicare provider-based rules. Preparing and submitting PBAs is an enormous undertaking and is currently voluntary for most hospitals, resulting in few hospitals submitting PBAs. Successful PBAs result in a letter from the Centers for Medicare & Medicaid Services (CMS) confirming that the location qualifies as provider-based (as long as the circumstances described in the PBA do not change). The provider-based rules are complex, which often leads to confusion as to the actual requirements under the rules. Further, the regulations have not been regularly amended and are rarely enforced, resulting in hospital compliance resources being directed to other compliance concerns that may appear higher risk. As a result, many locations that currently operate as off-campus hospital outpatient locations could lose provider-based status, and therefore hospital reimbursement rates, if required to submit compliant attestations.
Provider-Based Compliance Myths
Below are 10 myths about provider-based compliance that arise frequently in evaluations of such compliance for both new and established hospital outpatient locations. In light of increasing government focus on provider-based locations, hospitals and health systems should review these myths, along with the corresponding truths, to identify and proactively correct noncompliance before any implementation of requirements to submit PBAs and prove compliance with all provider-based requirements to the satisfaction of the government.

Myth #1: Compliance with the provider-based rules “doesn’t matter” because the government does not enforce them, and Medicare routinely pays claims for services at locations that do not meet the provider-based rules.

Truth: Compliance with the provider-based rules is a condition of receiving payment from Medicare. While it is true that public enforcement of the provider-based rules has been limited, that does not diminish the obligation to comply with the provider-based rules. When a hospital submits a claim for services at a provider-based location, and when it files its Medicare cost report, it attests to compliance with the provider-based rules. Submission of a claim for services at hospital location that is known to not comply with the provider-based rules is a false claim, subject to civil and criminal penalties, including per-claim penalties of more than $25,000 and prison sentences. Receiving payment for hospital services that do not meet the provider-based rules is also an overpayment. Such overpayments may require a full refund of claims billed from the location or a refund that constitutes the difference between the hospital payment and the payment that would have been received had the service been furnished at a non-hospital location.
Lack of historical enforcement does not change these difficult truths. Hospitals and health systems that have not carefully tracked ongoing compliance with the provider-based rule are well advised to make this part of their compliance workplans in 2025 to understand their compliance risks in this area. If PBAs become a requirement for all off-campus locations, as expected, hospitals will be required to attest to compliance up front and to maintain compliance over time, which carries additional monitoring and oversight challenges.

Myth #2: Compliance with the provider-based rules is easy and can be accomplished in a matter of days or weeks.

Truth: For strategic reasons, hospitals often acquire, create, or convert locations to provide off-campus hospital services. In some instances, there may be significant pressure to establish a location as a hospital off-campus department and, in turn, to come into compliance with the provider-based rules. However, because of certain requirements under the provider-based rules, it typically takes months, if not a year or more, to establish provider-based compliance for a new hospital location. For example, compliance with signage and public awareness rules requires permanent signage, which must be designed, ordered, and installed. Ensuring that the medical records for a provider-based location are integrated with the hospital’s electronic health records (EHRs) may require reconfiguring EHRs and other software systems to incorporate the new location. Compliance with employment and clinical and administrative oversight requirements may require renegotiation of employment contracts and compensation, particularly when unions are involved. Finally, provider-based locations often must be licensed as part of the hospital, which can take many months in some states. These are just a few examples. Establishing compliance with the provider-based rules entails many time-consuming tasks that cannot be expedited no matter how strong the perceived need.
In almost all cases, there will be operational matters related to compliance with the provider-based rules that require input from compliance and legal counsel, even when relying on competent consultant support in the development of the provider-based location.

Myth #3: Hospitals can temporarily create a provider-based location or operate a “part-time” provider-based location.

Truth: Provider-based locations are required to be operationally, administratively, and financially integrated with the hospital. Because of the close integration with the hospital required for provider-based compliance, it is not possible to “temporarily” convert a location to provider-based status. As noted, many of the requirements for provider-based compliance are time consuming to implement appropriately. Hospital conditions of participation also typically do not accommodate arrangements that allow a provider-based location to be operated as a hospital location on some days and as a different provider type on others. Where such arrangements may currently exist, it is unlikely that they satisfy the provider-based requirements, and they may also fail to meet the requirements to bill for services as another provider type – resulting in such a location being unable to compliantly bill Medicare at all. If a plan to “temporarily” convert or “time share” a provider-based location as a quick fix to achieve a specific operational goal sounds too good to be true, it probably is.

Myth #4: A provider-based hospital outpatient location on the main hospital campus can operate as a joint venture.

Truth: The reference to on-campus joint venture provider-based locations in the provider-based rules requires compliance with all other provider-based rules and, for hospital outpatient departments, a joint venture location cannot practically meet all other provider-based rules. Licensure, financial integration, clinical integration, operational integration, and compliance with the hospital’s Medicare provider agreement, among other applicable requirements, present significant barriers to on-campus hospital outpatient department joint ventures. A joint venture outpatient department also cannot be enrolled in Medicare as part of a hospital, cannot be certified by Medicare as part of a hospital, and cannot comply with Medicare cost reporting rules. Other transaction structures, such as co-management arrangements, may provide alternatives to achieve some of the business and clinical goals otherwise driving a proposed “provider-based joint venture.”

Myth #5: Provider-based locations can operate under separate leadership from the main campus.

Truth: Off-campus provider-based locations must be under the “direct supervision” of the main provider hospital, and the monitoring and oversight of the provider-based location must be the same as the monitoring and oversight of on-campus locations. This means that an off-campus provider-based location must act like a department of the hospital that is located on campus, including reporting up through the hospital’s organizational structure. This requirement extends to clinical as well as administrative reporting. For example, nurses providing services at an off-campus provider-based location are part of the hospital nursing staff and as such must report up through the hospital’s nursing staff structure and not through a different structure that ultimately ends at an administrator rather than the hospital’s chief nursing officer. For physicians, because the provider-based location is part of the hospital, roles such as chief medical officer, director, or other leadership titles must align with those of the hospital and reflect that they are part of the hospital’s structure, not a different medical staff or clinical enterprise.
Compliance with this requirement becomes more difficult to demonstrate when the distance between the provider-based location and the main campus is great. While the provider-based rules generally require that provider-based locations be within 35 miles of the main campus, there are several exceptions. None of the exceptions, however, change the nature of the main provider’s required oversight of the provider-based location.
“Remote locations” (additional inpatient campuses) are provider-based locations and are subject to the provider-based rules in the same manner as outpatient locations. Remote locations must be and operate under the control of the main provider. They must comply with the requirement that the remote location have the same monitoring and oversight by the main provider as any on-campus location. The remote location and the main provider hospital are, for CMS purposes, a single hospital, meaning that there is one chief executive officer, one chief nursing officer, a single medical staff, single nursing staff, single clinical departments, single medical record, etc., and administrative and clinical reporting structures must reflect this reality. This can be particularly challenging to explain to hospital leaders, or those who seek to be hospital leaders, as they may conflate separate campuses with separate hospitals and seek to create redundant structures that risk noncompliance with the provider-based rules.

Myth #6: There is flexibility in the language used for notification to Medicare beneficiaries of the provider-based status of off-campus outpatient departments.

Truth: Off-campus outpatient locations must provide Medicare beneficiaries with a notice to inform them that they are receiving services at a hospital location. The notice must include the specific content and language used in the provider-based rule.
Failure to provide such notice, or failure to include in the notice language acceptable to CMS, could result in false claims and overpayments due to noncompliance with the provider-based rule.

Myth #7: Provider-based location signage only requires the name of the health system.

Truth: With limited exceptions, provider-based locations are required to be held out to the public as part of the specific hospital to which the department is provider-based. With increased movement toward health system (as opposed to hospital) branding, this requirement is frequently overlooked. Signage and other public-facing written materials of the provider-based location must make it clear to patients that they are receiving services from the specific hospital of which the provider-based location is a part. Use of a system name is not sufficient to “hold out” the location as part of a specific enrolled hospital. Counsel should carefully review any naming conventions for provider-based locations that vary from simple use of the hospital’s name before they are rolled out.

Myth #8: If a location complies with the plain text of the provider-based rules, it can bill Medicare as a hospital.

Truth: The provider-based rules are not the only rules that apply when determining if Medicare may consider a particular location to be part of a hospital. All applicable state laws, Medicare enrollment rules, Medicare certification rules, and Medicare cost reporting rules, among other federal and state laws, must be met before a location may bill Medicare as part of a hospital. For example, if a location has met all provider-based rules, but the location has not been added to the hospital’s Medicare enrollment record, the location cannot bill Medicare as a hospital location.

Myth #9: It is only necessary to comply with the provider-based rules at the time a location first starts billing Medicare as a hospital.

Truth: Continued compliance with the provider-based rules cannot be guaranteed just because the rules were met when a location opened or when a periodic compliance review was conducted. Even submission and approval of a PBA does not establish a location as provider-based in perpetuity. Provider-based compliance must be incorporated into the hospital’s ongoing compliance program and compliance monitoring protocols. All staff of provider-based locations should be regularly trained on the requirements for provider-based status and how to identify potential risk areas or noncompliance. “Slippage” in compliance with the provider-based rules happens frequently if compliance is not effectively monitored. If at any point a location no longer meets all appliable provisions of the provider-based rules, it cannot be considered part of the hospital, and any payments made to the hospital or at hospital rates could be considered overpayments subject to quantification and return to the government. For locations with approved PBAs, any material changes from the facts submitted with the attestation could result in loss of provider-based status. CMS requires locations to report any material changes to the information in the PBA, which is difficult to accomplish if provider-based locations are not carefully and regularly monitored.

Myth #10: The provider-based attestation is a short document that is easy to prepare and have approved.

Truth: A quick internet search for provider-based attestation templates produces examples of forms that are a few pages long. This should not lull hospitals into thinking that completion of the template form is all that a PBA requires. Such examples are grossly misleading because they typically include only the cover page of a PBA and give the impression that a PBA is a rote box-checking exercise. It is not. The typical PBA, once fully compiled and completed, is generally about 500 pages and includes voluminous documentation to support the statements attested to by the hospital on the cover page. Preparing a PBA requires coordination and cooperation across many hospital departments, and determining the proper supporting documentation and locating it can often take weeks, if not months. Policy and procedure updates, organizational and reporting chart updates, and other document revisions necessary to prepare attachments to the PBA can add to the preparation time. Further, because of the highly technical nature of many of the provider-based rules and the significant consequences for noncompliance, it is prudent to have legal counsel actively involved in the attestation preparation process and for them to meaningfully review and comment on the final PBA before it is submitted.
Moreover, submission of a PBA is not the end of the process, and the final approval likely will not come quickly. Both the Medicare Administrative Contractors (MACs) and CMS routinely respond to PBAs with follow-up questions, often requiring hospitals to locate and produce additional documentation. Approval of a PBA typically takes more than six months and can involve multiple rounds of follow-up questions. At times, the MAC or CMS may require material changes to information submitted with the attestation, which can in turn require material modifications to the operations of the location at issue before it can compliantly bill for services as hospital services.
Conclusion
Congress appears to be intent on requiring PBAs for all off-campus provider-based hospital locations and will likely continue to push for this requirement until it is implemented. Hospitals and health systems should evaluate their provider-based compliance now, in anticipation of this change, or risk losing the ability to bill Medicare for off-campus hospital locations as part of the hospital. A starting point is to evaluate the operations of existing provider-based locations to ensure that they are consistent with the “truths” of provider-based status and not the “myths.”
We will also be hosting a webinar on provider-based myths and truths on March 17, 2025, from 12:30 – 1:30 pm ET. Please click here to register.

Bulletin Concurrence XIII
ARTICLE
Bulletin Concurrence XIII
January 2024
Read time: 2 min
We are delighted to share the thirteenth Bulletin Concurrence which aims to keep you up to date with the key developments in competition law between September-December 2024.
Read the full Bulletin (in French) here.

Unpacking the Biden Administration’s Last-Minute Antitrust Worker Protections
CLIENT ALERT / US POLICY
Unpacking the Biden Administration’s Last-Minute Antitrust Worker Protections
January 22, 2025
Read time: 6 min
In the final week of the Biden administration, the antitrust enforcement agencies – the Federal Trade Commission (FTC) and the US Department of Justice (DOJ) – released two policies potentially impacting labor markets. The first, released by the FTC on January 14, 2025, is a Policy Statement on the Exemption of Protected Labor Activity for Independent Contractors. The second, released concurrently by the FTC and DOJ on January 16, 2025, is the Antitrust Guidelines on Business Practices that Impact Workers. The policies address antitrust law as applied to workers in different ways.
One policy contemplates new antitrust liability protections for independent contractors (especially “gig workers”) similar to the existing antitrust exemption for collective action by employees. The other provides a broad list of types of conduct by employers related to workers that “could” violate the antitrust laws. We expect the new Trump administration will revisit these last-minute policy releases. In the meantime, these policy statements and guidelines reflect agency positions and do not themselves change applicable law. The National Labor Relations Act continues to statutorily exclude independent contractors from unionization rights and processes.
Policy Statement on Labor Exemption for Independent Contractors
In a 3-2 vote along partisan lines, the FTC released a policy statement that clarifies the antitrust liability for independent contractors involved in labor organizing. This policy statement extends the exemption from antitrust liability for labor organizing and bargaining to independent contractors and gig workers. The FTC clarifies their position is that the formal classification of a worker as an “employee” or as an “independent contractor” does not affect their potential protection from antitrust liability if they are engaged in protected labor activities such as organizing and collective bargaining activity.
In the FTC’s open commission meeting on January 14, 2025, Commissioner Bedoya emphasized that labor organizing protections are rooted in the First Amendment and should not be dependent on whether somebody is paid on a 1099 or a W-2. Commissioner Slaughter referenced recent merger enforcement wins that proposed unionized labor as a plausible market for antitrust purposes as evidence that courts agree with such an interpretation. Commissioner Slaughter also expressed concern that the US Department of Labor, during President Trump’s first term, conducted rulemaking that ran counter to treating independent contractors similarly to employees. This may foreshadow how the FTC under the new Trump administration may view this policy statement.
Commissioners Ferguson and Holyoak, the former having been selected as the next chair of the FTC, issued a short dissent in which they did not address the substance of the policy statement. However, they raised strong reservations about the FTC making such a statement so close to the Biden-Trump changeover, lending uncertainty to the statement’s future. Although the FTC, under the new Trump administration, likely cannot succeed in taking formal action to repeal the statement, which was issued by a majority of the commissioners, until a third Republican commissioner is confirmed, this categorical dissent likely means that such a repeal may be in the future. Mark Meador has been nominated by President Trump as the third Republican commissioner, but he will need to proceed through the Senate confirmation process before taking office and creating a Republican majority.
Guidelines on Business Practices That Impact Workers
In another final act, the Biden FTC and DOJ replaced the 2016 Antitrust Guidance for Human Resource Professionals with new Guidelines on Business Practices that Impact Workers. The new guidelines lay out a list of agreements that “may” violate the law, including:
- Agreements between employers not to recruit, solicit, or hire workers, or to fix wages or terms of employment.
- Agreements between franchisors and franchisees not to poach, hire, or solicit workers.
- Exchanging competitively sensitive employment information among companies that compete for workers.
- Employment restrictions that restrict workers’ freedom to leave their jobs.
- Various potentially restrictive, exclusionary, or predatory employment conditions that harm competition, including overbroad nondisclosure agreements that effectively prevent a person from working in the same industry.
The guidelines generally do not provide clarity around the circumstances under which various conduct will be viewed as violating the law. Instead, they provide a list of things that “may” violate the law and “general principles” for analyzing such cases. As such, although they purport to be “guidelines,” they are not particularly useful in providing clarity around the government’s approach to analyzing the conduct at issue but are more a shot across the bow, listing the conduct that could be problematic. Their practical usefulness seems limited, and companies will need to look to case law to try to assess their exposure rather than taking guidance from them.
These guidelines were also released on a 3-2 vote along partisan lines. Commissioner Ferguson, again joined by Commissioner Holyoak, issued another scathing dissent. Although agreeing that the FTC has the responsibility to review and update its guidance, the dissent takes no position on the substance of the guidelines. Instead, the dissent, like that in the policy statement above, vehemently disagrees with the decision to take such an action in the waning days of the Biden administration, noting that it is inappropriate to release new guidance when “[t]he Biden-Harris FTC has no future.”
Therefore, the only certainty is that the 2016 Guidance for Human Resource Professionals is no longer in effect.
Recently, the Commission brought several cases aimed at protecting labor, including challenges to mergers of competing employers and cases involving other agreements among employers related to their labor practices, such as nonsolicit agreements. The Republican commissioners have supported some of those actions, so we expect that the Trump FTC will continue to pay attention to labor competition issues, but they will not be as progressive as the previous Democratic majority. Former FTC Chair Lina Khan announced she will leave the FTC in the coming weeks. Following that, the Commission will be split 2-2 on partisan lines until the fifth commissioner is confirmed, and it is unlikely the FTC will bring any novel enforcement actions under the new Guidelines on Business Practices that Impact Workers, but more mainstream labor theories will continue to be in play.
A majority is also needed to repeal the new guidelines, so repeal is unlikely in the near term. However, once the third Republican commissioner is seated, it appears highly likely that the FTC will review and potentially repeal or significantly alter these new guidelines, particularly given the Republican commissioners’ dissent.

New York Governor Proposes Cost Market Impact Review, Expanded Disclosures for Material Transactions With Healthcare Entities
ARTICLE / CLIENT ALERT
New York Governor Proposes Cost Market Impact Review, Expanded Disclosures for Material Transactions With Healthcare Entities
January 22, 2025
Read time: 6 min
On January 21, 2025, New York Governor Kathy Hochul released the FY 2026 New York State Executive Budget, which proposed to impose a “cost market impact review” (CMIR) for certain “material transactions” involving “health care entities” in New York. The New York State Assembly and Senate must now review the proposed legislation and may propose revisions to, or removal of, the proposal before approving the final FY 2026 state budget.
If enacted as proposed, the governor’s proposed legislation would delay timeframes for closing certain large material transactions involving healthcare entities in New York and would subject the parties to these transactions and the transactions themselves to heightened regulatory scrutiny. The proposed legislation does not clarify the central definitions that establish the scope of the notice requirement.
Current Law
New York law currently requires “health care entities” to submit to the New York State Department of Health (DOH) a written notice at least 30 days prior to closing a “material transaction” with a healthcare entity. The notice must provide basic information regarding the transaction, including the names of the parties to the material transaction, any plans to eliminate services and/or participation in specific plan networks, and the transaction’s anticipated impact on cost, quality, access, health equity, and competition in the affected markets.
The law defines a “health care entity” as including, with certain exceptions:
- A physician practice, group, or management services organization or similar entity providing all or substantially all of the administrative or management services under contract with one or more physician practices
- A provider-sponsored organization
- A health insurance plan
- Any other kind of healthcare facility, organization, or plan providing healthcare services in this state.
“De minimis” material transactions with healthcare entities are not considered material transactions subject to the notice requirement. A de minimis transaction is a transaction that results in a healthcare entity increasing its total gross in-state revenues by less than $25 million. The law does not explain how “in-state revenues” are to be counted.
Although the law authorized DOH to add, amend, or repeal any rule or regulation necessary to implement the requirement as of its effective date (August 1, 2023), to date DOH has not taken any such regulatory action, nor has DOH issued subregulatory guidance explaining its interpretation of the law and its requirements.
The Proposed Legislation
The governor’s proposal would extend the pre-closing notice timeframe to 60 days and allow DOH to require parties to the transaction, as well as their parents and subsidiaries, to submit additional documents and information. Such additional data requests may be made by DOH to the extent necessary to:
- Conduct DOH’s preliminary review of the transaction
- Assess the impacts of the transaction on cost, quality, and access to healthcare, health equity, and competition
- To verify or clarify information previously submitted by the parties.
Upon submission of the notice, DOH would conduct a “preliminary review” of the transaction to determine whether a full CMIR was required. If DOH requires a CMIR, the parties may be required to delay the closing of the proposed transaction for up to 180 days from the date of the preliminary review so that DOH can complete the CMIR. During the CMIR, DOH may again require any party or its subsidiaries and parent entities to submit additional documentation and information to the extent such additional information is necessary for DOH to conduct the CMIR.
The proposed legislation would also require parties to a material transaction to annually notify DOH of factors and metrics to assess the impacts of the transaction on cost, quality, access, health equity, and competition. DOH may require parties to submit additional documents and information in connection with the annual report, to the extent such additional information is necessary to assess the impacts of the transaction on cost, quality, access, health equity, and competition, or to verify or clarify information submitted in support or as part of the annual report.
The proposed legislation would protect documentation, data, and information submitted by the parties from New York’s Freedom of Information Law disclosure, but data submitted in annual reports, information submitted in conjunction with a CMIR, and CMIR findings may be used as evidence in investigations, reviews, and other actions by DOH or the New York State Attorney General, including evaluating certificate of need applications.
DOH may assess the parties to material transactions all costs (without cap) incurred by DOH in reviewing and evaluating the notice and performing the CMIR.
Analysis and Takeaways
If enacted, the proposed legislation would expand the authority given to DOH to review material transactions involving healthcare entities in New York state. Although the proposed legislation would not grant DOH express authority to approve or disapprove proposed material transactions, DOH could significantly delay these transactions by declining to recognize a notice as complete without the production of the information and documents it requests.
The proposal does not shed additional light on key aspects of the existing law that remain subject to interpretation, including questions regarding the definition of a “health care entity,” “material transaction,” and the de minimis exception. DOH has not yet published regulations or subregulatory guidance on these topics, which has created ambiguity and differing interpretations that this proposal does not appear to address. Accordingly, these key aspects of the material transactions law will remain subject to interpretation by parties to such transactions unless and until DOH promulgates regulations and provides additional guidance.
The proposed legislation will be subject to refinement in the coming legislative budget process, during which the New York State Senate and Assembly may revise or remove portions of the governor’s executive budget. The state budget, reflecting the revisions to the governor’s executive budget approved by the State Senate and Assembly, is required to be signed into law by April 1, 2025, although in recent years the budget has not been finalized until several weeks later.

California SB 923: New Trans-Inclusive Healthcare Requirements for Health Plans
ARTICLE / CLIENT ALERT
California SB 923: New Trans-Inclusive Healthcare Requirements for Health Plans
January 17, 2025
Read time: 8 min
Beginning in the first quarter of 2025, California healthcare service plans, health insurers, Medi-Cal managed care plans, and PACE organizations must ensure that staff who have direct enrollee contact receive evidence-based cultural competency training focused on transgender-inclusive healthcare. This requirement arises from Senate Bill No. 923 (SB 923), a law passed by the California legislature in 2022. Provider directories must also be updated by March 1, 2025, to identify which in-network providers have previously offered gender-affirming services.
SB 923 is part of a broader effort by the California legislature to require healthcare entities to improve access to culturally competent gender-affirming care for transgender, gender diverse, and intersex (TGI) individuals. This legislation builds on prior mandates requiring physicians and surgeons to complete continuing medical education (CME) courses addressing cultural and linguistic competency. The legislation expanded existing cultural competency training requirements to now require CME programs to address TGI-related health needs, thus laying a foundation for the broader system-wide changes that SB 923 compels.
While the statute sets “no later than March 1, 2025,” as the outer deadline for compliance, the California Department of Managed Health Care (DMHC) All Plan Letter (APL) 24-018 imposes an earlier deadline – February 14, 2025 – for all full-service (and certain specialized) healthcare service plans under DMHC jurisdiction to complete the required training.
Below we outline the key requirements, summarize the CME obligations already in effect, consider initial feedback from early implementation, and offer steps to help affected entities prepare for upcoming deadlines.
New Requirements for Health Plans, Insurers, and Medi-Cal Managed Care Entities
SB 923 requires healthcare service plans, health insurers, Medi-Cal managed care plans, and PACE organizations to engage in workforce cultural competency training. Key training elements include:
- Adopting inclusive communication techniques by using TGI-inclusive terminology and ensuring respectful, affirming interactions with TGI patients.
- Addressing health disparities by explaining how family and community acceptance influence TGI patient health outcomes and integrating this understanding into care practices.
- Conducting refresher course training whenever a complaint is filed and upheld against a staff member for failing to provide TGI-inclusive care and administering additional courses more frequently if needed.
Training must be provided to staff who directly interact with enrollees. This includes frontline personnel such as call center representatives, nurses, and other staff members who have contact with patients. Exempt from this training requirement are specialized healthcare service plans providing only dental or vision services and Medicare Advantage plans. Currently, SB 923 does not include any exemptions or opt-outs for staff or providers based on religious, moral, or rights of conscience objections grounds.
While SB 923’s statutory language sets an outer compliance deadline of no later than March 1, 2025, DMHC’s APL 24-018 specifies that all full-service healthcare service plans, regardless of size (and certain specialized plans other than dental or vision-only plans), must ensure that staff complete the required training by February 14, 2025. For health insurers regulated by the Department of Insurance or Medi-Cal managed care plans overseen by the Department of Health Care Services (DHCS), the statutory deadline remains March 1, 2025, unless their respective regulators issue further guidance.
In addition to initial training, DMHC’s APL requires that training be completed every two years thereafter, ensuring ongoing competency. Newly hired staff with direct enrollee contact must complete the training within 45 days of commencing employment. Health plans should also note that regulators may impose sanctions or penalties for noncompliance, reinforcing the importance of meeting these requirements.
Updated Provider Directories for Gender-Affirming Services
By March 1, 2025, health plans, insurers, and Medi-Cal managed care plans must update their provider directories (as well as call center information) to identify which in-network providers have affirmed and previously provided gender-affirming services. These services might include hormone therapy, gender-confirming surgeries, gender-affirming gynecological care, or voice therapy.
Already-in-Effect CME Requirements
Since 2006, curricula for CME courses in California have been required to include cultural and linguistic competency in the practice of medicine. Since 2022, CME course curricula also have been required to include the understanding of implicit bias. SB 923 amended the cultural competency portion of California’s Business and Professions Code Section 2190.1 to require that CME also include TGI health needs. The updated CME curricula should address:
- Using correct names, pronouns, and gender-neutral language.
- Avoiding assumptions about gender or sexual orientation.
- Understanding the discrimination and barriers that TGI patients face, and how implicit bias may influence clinical decisions.
- Implementing administrative changes, such as more inclusive intake forms, to create a welcoming care environment.
Cultural competency, including TGI-specific elements, and implicit bias training are not necessary for CME courses offered outside of California to California-licensed physicians and surgeons or as part of CME courses dedicated solely to research or other non-clinical issues lacking a direct patient care component.
Implementation Status of SB 923 CME Requirements
Since the TGI-focused CME requirements took effect in 2023, some larger health systems have begun integrating targeted training modules while smaller practices have struggled to find suitable specialized resources. According to the California Association of Health Plans, questions remain about how these training standards will align and be enforced across various health plans and delegated entities. Despite these uncertainties, incremental progress continues. As more healthcare organizations develop approved training resources and toolkits, accessibility and overall cultural competency likely will improve.
Practical Steps for Compliance
- For Healthcare Providers: Integrate the updated CME modules into existing physician education, revise administrative materials (intake forms, electronic medical records) to reflect inclusive language, and ensure all frontline staff are trained in respectful, TGI-inclusive communication.
- For Health Plans and Insurers: Implement TGI-focused training as specified by DMHC: for full-service healthcare service plans, by February 14, 2025, and for other regulated entities, by the statutory deadline. Update provider directories to highlight gender-affirming providers by March 1, 2025, and establish effective complaint and grievance tracking to ensure accountability. With respect to ERISA-governed self-insured group health plans, SB 923 does not provide an express exception. However, ERISA typically preempts state laws that attempt to regulate employee benefit plans, although fully insured plans are generally subject to state insurance laws and would likely need to comply with SB 923. A plan that is not fully insured or regulated by the California DMHC would generally not need to comply. As of the publication date, we are unaware of any ERISA preemption challenges to SB 923. Some group health plan sponsors may wish to proceed with compliance and continue to watch for any updates.
- For Medi-Cal Managed Care Plans and PACE Organizations: Follow guidance issued by regulators, such as the DHCS Policy Letter 24-03, to implement required training, keep provider directories current with gender-affirming providers, and report TGI-related complaints. In addition, remain alert for further instructions from regulators and prepare to incorporate the required standards.
Looking Ahead
When SB 923 was initially debated, some stakeholders opposed the legislation based on religious liberty and rights of conscience grounds, arguing that SB 923’s training mandates amount to unconstitutional compelled speech. However, a recent decision by the US District Court for the Central District of California in Khatibi v. Hawkins suggests that courts may uphold SB 923 as a form of government speech. The case involved a challenge to the implicit bias training requirement because some CME lecturers felt that their First Amendment rights were being violated. The court observed that “[s]tate-mandated curriculum requirements for CME courses necessary for state licensure constitutes government speech because when physicians . . . choose to teach CME courses for credit, they ‘speak for the state.’” (Khatibi v. Hawkins, No. 2:23-cv-06195-MRA-E, 2024 WL 3802523 (May 2, 2024)). The matter is currently under appeal to the US Court of Appeals for the Ninth Circuit.
Conclusion
SB 923 represents continued efforts by California toward ensuring that TGI patients receive respectful, informed, and affirming healthcare. With CME requirements already in effect and a range of new mandates, including system-wide training for health plans, updated provider directories, complaint tracking, and eventual quality standards, entities face a multifaceted compliance landscape. DHCS Policy Letter 24-03 and DMHC APL 24-018 provide clarity and actionable guidance, and both reflect the recommendations issued by the Transgender, Gender Diverse, or Intersex Working Group convened under SB 923’s mandate. Formal regulations under SB 923 will be adopted by July 1, 2027, but as the February and March 2025 deadlines approach, stakeholders should proactively implement training, update administrative practices, maintain transparent patient engagement, and follow the newly issued DHCS and DMHC directives.

CFPB Proposes Clarifications to the Scope of Regulation E for Digital Assets and Nonbank Payment Platforms
ARTICLE / CLIENT ALERT
CFPB Proposes Clarifications to the Scope of Regulation E for Digital Assets and Nonbank Payment Platforms
January 17, 2025
Read time: 8 min
On Jan. 10, 2025, the Consumer Financial Protection Bureau (“CFPB”) issued a proposed interpretive rule designed to clarify how the Electronic Fund Transfer Act (“EFTA”) and its implementing regulation, Regulation E, apply to modern digital payment systems (the “Proposed Rule”).[1] The Proposed Rule aims to ensure that the protective measures of Regulation E extend to consumers using digital wallets, payment apps, gaming platforms, and digital assets such as stablecoins.
EFTA and Regulation E protect consumers making electronic fund transfers (“EFTs”) using “accounts” established primarily for personal, family or household purposes. An EFT includes any transfer of funds that is initiated through an electronic terminal, telephone, computer or magnetic tape for the purpose of authorizing a financial institution to debit or credit a consumer’s account,[2] and traditionally includes, but is not limited to, point-of-sale transfers, ATM transfers, direct deposits or withdrawals, telephone transfers, and transfers initiated through a debit card transaction. EFTA and Regulation E offer protections including safeguards against unauthorized transactions, error resolution rights and disclosures.
The Proposed Rule reflects the CFPB’s intent to address perceived gaps in consumer protections as payment technologies evolve. By expanding the scope of Regulation E to align with evolving payment technologies, the CFPB seeks to provide consistent oversight and accountability across established and emerging platforms.
Key Features of the Proposed Rule
The Proposed Rule reflects the CFPB’s intent to ensure that consumers engaging with digital payment systems receive consistent protections, regardless of the technology or platform involved. By expanding its interpretation and clarifying key definitions within EFTA and the Regulation E framework, the CFPB is addressing perceived gaps that have emerged as nonbank providers and digital assets play an increasing role in the payments landscape. Below are the primary components of the Proposed Rule:
- Clarifying “Funds” Under EFTA. In the Proposed Rule, the CFPB provides critical interpretive guidance on how existing definitions under EFTA apply to nontraditional payment systems and digital assets. While “financial institution” is an explicitly defined term in EFTA and Regulation E, and it is well-established that financial institutions can include nonbank entities, the term “funds” is not defined. To address this gap, the CFPB draws on its regulatory authority and EFTA’s plain language and relevant case law to interpret “funds” broadly, to ensure that consumer protections extend to modern payment systems and emerging technologies, including digital assets, like stablecoins, when used in consumer transactions.
The Proposed Rule explains that, historically, the term “funds” has been understood to encompass more than fiat currency, including assets that act as a medium of exchange or can be readily converted into cash, such as checks, drafts, and negotiable instruments.[3] The CFPB clarifies that “funds” would include both fiat currencies and digital assets, such as stablecoins and other fungible assets, when used as a medium of exchange or means of payment.[4] Notably, an asset’s fluctuation in value does not exclude it from this definition. To support this interpretation, the CFPB cites recent court rulings, including one holding that cryptocurrency qualifies as “funds” under EFTA.[5]
This expanded definition of “funds” would extend the scope of Regulation E to industry stakeholders that store these digital assets or facilitate transfers of these digital assets. Interestingly, this Proposed Rule comes shortly after the CFPB declined to cover digital assets in its final rule defining larger participants in the market for general-use digital consumer payment applications.[6]
- Extending EFTA Coverage to Nontraditional Consumer Accounts. The Proposed Rule clarifies that the term “account” under EFTA and Regulation E applies not only to traditional financial accounts, such as checking and savings accounts, but also to other consumer asset accounts. Both EFTA and Regulation E define “account” broadly to mean: “[A] demand deposit (checking), savings, or other consumer asset account (other than an occasional or incidental credit balance in a credit plan) held directly or indirectly by a financial institution and established primarily for personal, family or household purposes.”[7]
The CFPB proposes to clarify that the clause “other consumer asset accounts” includes accounts that are not traditional deposit accounts but enable consumers to store funds and conduct electronic transactions.[8] Depending on the facts and circumstances, the Proposed Rule identifies several types of accounts that could qualify as “accounts” under EFTA, including: (i) video game accounts that allow consumers to purchase virtual items from multiple game developers or players; (ii) virtual currency wallets that can be used to buy goods and services or make person-to-person transfers; and (iii) credit card rewards points accounts that enable consumers to buy points for purchases from multiple merchants.[9] The CFPB, however, does not address whether these particular products may meet the definition of “prepaid account” under Regulation E and notes that the analysis will depend on the features of the product and is outside the scope of the Proposed Rule.[10] As a general matter, whether a product is a “prepaid account” or not impacts the disclosures and error resolution program requirements under Regulation E.
Based on its proposed interpretation of “account,” the CFPB maintains that nonbank entities, such as fintech companies, digital wallet providers and gaming platforms, are included in the definition of “financial institution” if they maintain consumer accounts that enable EFTs, and thus, EFTA’s consumer protection requirements, such as error resolution rights, safeguards against unauthorized transactions and clear disclosures about account terms, would apply to these nontraditional accounts. By bringing these types of accounts within the scope of EFTA, the CFPB aims to provide consistent consumer protections regardless of whether consumers rely on traditional or nonbank financial platforms. The CFPB believes this clarification aligns with the legislative history of the EFTA, which intended for “account” to cover any asset account offering equivalent EFT services.
- Addressing Exemptions for Certain Transactions. The Proposed Rule affirms that EFTA and Regulation E do not apply to transfers of funds primarily intended for the purchase or sale of securities or commodities regulated by the SEC or CFTC, or conducted through regulated broker-dealers or futures commission merchants. However, the CFPB clarifies that this exception is limited to investment-related transfers and does not apply when securities or commodities are used as “funds” in an “account” to purchase goods or services from a retailer. For example, while EFTA does not regulate the purchase of a stock, it does cover transactions where assets in a securities account are used to buy goods or services or obtain cash.
Implications and Next Steps
The Proposed Rule underscores the CFPB’s intent to strengthen consumer protections in the digital payments ecosystem, ensuring that evolving technologies operate with the same level of transparency and accountability as traditional financial institutions. But the Proposed Rule comes shortly before the Trump administration is set to take office, which will likely cause a shift in the regulatory and enforcement priorities of the CFPB.[11] It is unclear whether the CFPB will continue to pursue the Proposed Rule after the administration change.
As an interpretive rule, the Proposed Rule is not subject to the Administrative Procedures Act. Despite this, the CFPB is still accepting public comments on the Proposed Rule through March 31, 2025. Industry stakeholders are encouraged to submit comments to address potential operational challenges or provide feedback on how emerging technologies — such as stablecoins and payment-integrated gaming platforms — can be effectively regulated while fostering innovation and ensuring consumer protection.
Schulte Roth & Zabel’s lawyers are available to assist you in preparing a comment or addressing any questions you may have regarding these developments. Please contact the Schulte Roth & Zabel lawyer with whom you usually work, or any of the following attorneys:
Donald J. Mosher – New York (+1 212.756.2187)
Kara A. Kuchar – New York (+1 212.756.2734)
Betty Santangelo – New York (+1 212.756.2587)
Melissa G.R. Goldstein – Washington, DC (+1 202.729.7471)
Adam J. Barazani – New York (+1 212.756.2519)
Jessica Romano – New York (+1 212.756.2205)
Jesse Weissman – New York (+1 212.756.2460)
Julianna R. Pasquarello – New York (+1 212.756.2055)
Jonice Q. Jackson – Washington, DC (+1 202.729.7479)
[1] CFPB, Proposed Rule, Electronic Fund Transfers Through Accounts Established Primarily for Personal, Family or Household Purposes Using Emerging Payment Mechanisms, 90 Fed. Reg. 3723 (Jan. 15, 2025).
[2] See 15 U.S.C. § 1693a(7); 12 C.F.R. § 1005.3(b).
[3] See Proposed Rule at 3725.
[4] See id. at 3726.
[5] Rider v. Uphold HQ Inc., 657 F. Supp. 3d 491, 498 (S.D.N.Y. 2023).
[6] See 89 FR 99582 at 99612 (“The CFPB intends to continue to gather data and information regarding the nature of [digital asset] transactions and the impact of digital asset transactions on consumers, and to take further action as appropriate.”). For more information regarding the Larger Participant Rule, please see our prior Alert “CFPB Finalizes Rule for Federal Oversight of Popular Digital Payment Apps”.
[7] 12 C.F.R. § 1005.2(b)(1); see also 15 U.S.C. § 1693a(2) (emphasis added).
[8] “Other consumer asset accounts” also include prepaid accounts, which are already subject to Regulation E.
[9] See Proposed Rule at 3726.
[10] See id., n.42.
[11] For more information regarding changes to the CFPB under the Trump administration, please see our prior Alert “Navigating Regulatory Changes: What to Expect for the CFPB Under the Incoming Trump Administration”.
This communication is issued by Schulte Roth & Zabel LLP for informational purposes only and does not constitute legal advice or establish an attorney-client relationship. In some jurisdictions, this publication may be considered attorney advertising. © 2025 Schulte Roth & Zabel LLP. All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.
