ARTICLE / CLIENT ALERT
Section 1557 patient care decision support tools, anti-discrimination compliance: 12 things to consider
January 16, 2025
Read time: 8 min
In April 2024, the US Department of Health and Human Services (HHS) issued a final rule reinterpreting Section 1557 of the Affordable Care Act, which prohibits discrimination on the basis of race, color, national origin, sex, age, or disability, or any combination thereof, in a health program or activity, any part of which receives federal financial assistance. This includes a general prohibition on discrimination through the use of patient care decision support tools, which becomes effective May 1, 2025 (i.e., 300 days from the rule’s effective date).
As Section 1557 covered entities (i.e., health programs or activities that receive HHS funding, health programs or activities administered by HHS, and the federal Health Insurance Marketplace) work to evaluate their patient care decision support tools in preparation for the new requirements, below we highlight 12 things covered entities should keep in mind.
1. “Patient care decision support tool” is broadly defined.
The HHS Office for Civil Rights (OCR) defines “patient care decision support tool” to mean any automated or non-automated tool, mechanism, method, technology, or combination thereof used by a covered entity to support clinical decision-making in its health programs or activities. The definition is intentionally broad and includes tools used to assess health status, recommend care, provide disease management guidance, determine eligibility, and more. The definition does not include tools that are unrelated to clinical decision-making, such as tools used for patient scheduling, supply chain management, automated medical coding, or staffing-related activities.
2. Covered entities must make “reasonable efforts” to identify tools that use input variables that measure race, color, national origin, sex, age, or disability.
OCR does not describe how often entities must assess a tool for potential bias or discrimination. Rather, entities have an ongoing duty to “make reasonable efforts” to mitigate the risk of discrimination resulting from use of a tool in their health programs or activities.
3. Whether an entity engages in “reasonable efforts” will depend on the facts and circumstances.
In evaluating whether a covered entity complies with the “reasonable efforts” standard, OCR may consider, among other factors:
- The entity’s size and resources
- Whether the entity used the tool in the manner intended by the developer and approved by regulators
- Whether the entity customized the tool
- Whether the developer advised the entity regarding potential for discrimination
- Whether the entity has a process in place for evaluating the tool (e.g., governance).
OCR will consider compliance on a case-by-case basis. Some tools may warrant more frequent evaluation than others. For example, artificial intelligence (AI) models that learn and evolve after being deployed may require more frequent evaluation compared to static tools such as flowcharts.
4. When assessing tools for potential bias or discrimination, covered entities should consult reliable, publicly available resources.
If a covered entity does not know whether a tool uses variables that measure race, color, national origin, sex, age, or disability, the entity should consult publicly available sources or request information from the developer. Entities may gain knowledge about a tool’s potentially discriminatory risks through media outlets, peer-reviewed studies, the tool developer, professional and hospital associations, health-insurance-related associations, subregulatory governmental guidance, and subsequent regulatory guidance and rulemaking. Entities should evaluate the tools and public resources as they would evaluate medical literature – by considering the underlying evidence and whether the resource has been peer reviewed, for example.
5. Document compliance with Section 1557.
Entities should develop policies and procedures now for compliance with Section 1557. These policies and procedures should include a process for documenting the reasonable efforts planned and ultimately taken to mitigate discrimination. Options to consider include:
- Developing checklists or forms to be completed each time a tool is assessed
- Implementing policies to detect discriminatory impacts
- Establishing procedures governing how an algorithm may be used
- Training staff on the proper use of such systems and tools.
The rule requires general Section 1557 staff training following a covered entity’s implementation of policies and procedures, and no later than May 1, 2025.
6. A covered entity’s liability under Section 1557 is not related to a developer’s liability.
Covered entities’ use of patient care decision support tools must independently comply with Section 1557 irrespective of whether a tool’s developer is also subject to Section 1557. Although some stakeholders requested that covered entities share liability with algorithm creators, or that OCR impose strict liability on the manufacturers of algorithms rather than end users, HHS declined to adopt such recommendations. Instead, each covered entity must ensure that its use of a tool does not result in discrimination.
7. ASTP/ONC predictive decision support intervention is also live.
As part of the Health Data, Technology, and Interoperability (HTI-1) final rule, the Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP/ONC) established a new regulatory framework for certain AI and machine learning technologies that support decision-making in healthcare, including some patient care decision support tools. Compliance requirements took effect on December 31, 2024. Section 1557 covered entities that are also certified health IT developers should review the use of AI in their Health IT Modules (as defined by ASTP/ONC) to verify that they meet the HTI-1 certification requirements. Covered entities also should evaluate whether patient care decision support tools received from health IT developers (that may not be subject to Section 1557) comply with Section 1557 before deploying the tools for live use with patients.
8. Additional ASTP/ONC patient care decision support tool regulations are likely coming.
In September 2024, ASTP/ONC published its 2024 – 2030 Federal Health IT Strategic Plan. ASTP/ONC emphasized the key role that AI will play in future health IT regulations. The strategic plan points to the “rapid evolution” of machine-based systems that can influence decisions for a given set of human objectives. As AI-based patient care decision support tools are increasingly incorporated into health IT across the industry, ASTP/ONC will likely look to expand on the regulation of the HTI-1 final rule, and it may do so more expeditiously than inevitable revisions to Section 1557’s regulations. Section 1557 covered entities should monitor ASTP/ONC rules for potential foreshadowing of the Trump administration’s plans for patient care decision support tools under Section 1557.
9. Covered entities should continue to keep an eye on state law developments.
While OCR and ASTP/ONC have begun to regulate patient care decision support tools, US Congress has yet to definitively act. As a result, several state legislatures have enacted or proposed legislation to independently regulate developers and deployers of patient care decision support tools. While enacted and proposed legislation in states such as Illinois, Colorado, and California aim to curb algorithmic discrimination, the approaches are sometimes vastly different. In the absence of a uniform approach, covered entities should ask certain questions to inform compliance with state laws:
- Does your tool contain safeguards against algorithmic discrimination?
- Could the data used to train the tool lead to inadvertent algorithmic discrimination?
- Is there a process in place to evaluate whether algorithmic discrimination is taking place?
- Is there appropriate documentation in place to show efforts to evaluate each of the foregoing?
10. Experience implementing the regulations may influence future rulemaking.
In the Section 1557 final rule, OCR requested comments on whether it should engage in additional rulemaking to expand the scope of its prohibition on algorithmic discrimination, including other decision support tools that might not directly impact patient care and clinical decision-making but may nevertheless result in unlawful discrimination. As entities comply with the new requirements and gain experience in evaluating their use of decision support tools and documenting compliance efforts, entities should be mindful that any comments related to their experiences may shape future regulations.
11. “Ensuring nondiscrimination in the use of AI is Good Medicine.”
In a blog post accompanying a January 10, 2025, “Dear Colleague” letter explaining how covered entities can safely introduce and use AI tools in their operations, HHS OCR Director Melanie Fontes Rainer observed that “discrimination in AI-driven health care tools – whether intentional or unintentional – can lead to uneven care, diminished trust, and financial risks, such as lawsuits and regulatory interventions.” OCR’s enforcement posture has been increasing in recent years, with penalties ranging from resolution agreements and compliance reviews to compensatory and punitive damages. Plaintiffs have also successfully brought private claims against Section 1557 covered entities for discriminatory actions.
12. AI oversight has been a bipartisan effort.
The AI genie seems to be out of the bottle. However, in December 2024, the Bipartisan House Task Force on AI released a 253-page report that articulated many potential harms that may arise through algorithmic decision-making, including bias, discrimination, and worker dislocation. Although the Trump administration is likely to revise or repeal Section 1557 regulations in their entirety, efforts that covered entities take toward meeting the May 1, 2025, patient care decision support tool compliance date will lay strong groundwork for meeting state and federal government expectations for use of AI as part of patient care.

ZuFinG II – The Next Step Towards Strengthening Germany as a Financial Hub?
ARTICLE
ZuFinG II – The Next Step Towards Strengthening Germany as a Financial Hub?
October 8, 2024
Read time: 2 min
Following the initial steps with the Future Financing Act (“ZuFinG I“), the Federal Ministry of Finance presented the draft of the Second Future Financing Act (“ZuFinG II-E” and “Draft Bill“) on August 27, 2024. The Draft Bill aims to further develop the German financial market and revise some of the existing regulations. The primary focus is on facilitating access to the capital markets and relieving financial actors from excessive bureaucracy.
Find out more about the draft of the Second Future Financing Act in the latest article, “ZuFinG II – The Next Step Towards Strengthening Germany as a Financial Hub?,” by Annabelle Rau on our FinRegNewsBlog.
Sign up now for regular FinRegNews updates.

CFPB Issues Request for Information Regarding the Collection, Use and Monetization of Consumer Payment and Personal Financial Data
ARTICLE / CLIENT ALERT
CFPB Issues Request for Information Regarding the Collection, Use and Monetization of Consumer Payment and Personal Financial Data
January 16, 2025
Read time: 10 min
On Jan. 10, 2025, the Consumer Financial Protection Bureau (“CFPB”) issued a notice and request for information (“RFI”) regarding the collection, use, sharing and protection of consumer financial data by companies offering or providing consumer financial products or services, such as data obtained from payments.[1] The CFPB is requesting public input on the nature and impact of these data collection practices in relation to existing privacy laws, specifically the Gramm-Leach-Bliley Act (“GLBA”) and its implementing Regulation P.[2]
Background
Enacted in 1999, the GLBA includes several privacy provisions designed to protect consumers’ nonpublic personal information, including provisions that restrict the disclosure of such information to nonaffiliated third parties and limit its further use and disclosure by downstream recipients of such data.[3] These privacy provisions apply to “financial institutions”, which is broadly defined to include most companies engaged in financial activities including banks, credit card issuers, credit bureaus, money transmitters, mortgage originators and servicers, student loan servicers, debt collectors, and payday lenders.[4] In 2010, rulemaking authority for the privacy provisions of the GLBA (which was originally with other federal agencies) was granted to the CFPB, and since restating the prior agencies’ regulations as Regulation P in 2011, the CFPB has only modified Regulation P twice and has not revised the model privacy form developed in 2009.[5]
Recently, the CFPB conducted research into the changing consumer payments landscape and found that companies’ actual business practices may be a significant deviation from consumers’ expectations with respect to the collection, use and monetization of their data obtained from payment transactions.[6] For example, in 2021 and 2023, the CFPB conducted an inquiry to seek information on the business practices of six technology firms that offer consumer payment products, including the type of data such firms collected and how such data was maintained and used.[7] As part of such inquiry, the CFPB preliminarily identified potential risks to consumers, including the collection and use of data in excess of what is needed for a payment transaction.[8] Further, a 2020 Government Accountability Office study identified consumers’ concerns over the privacy of their data, and the potential need for reassessment of Regulation P, including updating the model privacy form.[9]
Information Requested
Given the recent changes in the consumer data landscape, the CFPB issued its RFI with an aim to collect comments on companies’ practices in collecting, using, processing, sharing and managing consumer financial data and to gather proposals for amending Regulation P.[10] The CFPB’s primary focus includes understanding:
- Incentives Behind Excessive Data Collection. The RFI seeks evidence regarding incentives for companies to collect more consumer data than is necessary for providing a consumer financial product or service.[11]
- Effectiveness of and Reforms for Regulation P. The RFI seeks evidence concerning the effectiveness of Regulation P, including the effectiveness of the model privacy form and opt-out notices.[12]
- Consumer Engagement and Barriers to Opt-Out Options. The RFI seeks evidence concerning the proportion of consumers exercising their opt-out rights, factors influencing their decisions and recommendations for simplifying the opt-out process.[13] The RFI also seeks insights identifying obstacles impeding this right, including acts or practices that discourage opting out.[14]
- Opportunities for Enhanced Data Protections. The RFI seeks insights on strengthening protections around consumer data, including protecting data subject to secondary use or held by downstream recipients, and achieving consistent protections across different types of consumer financial service providers.[15]
- Market Entry Barriers Due to Existing Data Practices. The RFI seeks evidence on whether data collections by large entities create barriers for new entrants in the consumer financial products and services space.[16]
- Harms and Benefits to Consumers under Existing Data Practices. The RFI seeks information on the harms and benefits to consumers as a result of current business practices that leverage consumer data.[17]
Implications and Next Steps
The RFI indicates the CFPB’s interest in potentially expanding existing privacy protections to encompass new payment technologies. By seeking public input on these data collection activities and their implications, the CFPB demonstrates its willingness to either amend current regulations or use its existing authority to address consumer harm caused by such practices. Whether such initiatives will carry over to the Trump administration, however, is to be seen.
The CFPB is accepting public comments through April 11, 2025.[18] While the RFI includes a list of 15 specific questions, the CFPB also indicated that they are interested in receiving any comments relating to the consumer data financial institutions collect.[19] Industry stakeholders at all levels, including companies subject to the GLBA and Regulation P, are encouraged to submit comments, data and information about how companies that offer or provide consumer financial products or services collect, use and share consumer data.[20]
Schulte Roth & Zabel’s lawyers are available to assist you in 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)
[2] See RFI at 12.
[3] 15 U.S.C. §§ 6801-6809; 12 C.F.R. Part 1016.
[4] 15 U.S.C. § 6809(3).
[5] RFI at 5.
[6] See RFI at 3.
[7] RFI at 9.
[8] RFI at 9.
[9] RFI at 6-7.
[10] RFI at 12.
[11] RFI at 12.
[12] RFI at 12-13.
[13] RFI at 13-14.
[14] RFI at 14.
[15] RFI at 15-16.
[16] RFI at 16.
[17] RFI at 16.
[18] RFI at 1.
[19] RFI at 12.
[20] RFI at 12.
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.

How Employers Can Aid Employees Impacted by the Los Angeles Wildfires
ARTICLE / CLIENT ALERT
How Employers Can Aid Employees Impacted by the Los Angeles Wildfires
January 15, 2025
Read time: 5 min
Over the past two weeks, wildfires have caused substantial loss and damage to homes and communities in Los Angeles, California, and the surrounding areas. In the wake of such devastation, employers may seek opportunities to provide financial assistance to impacted employees. Fortunately, the Internal Revenue Service (IRS) has outlined various ways for employers to provide much-needed assistance to employees impacted by natural disasters like the wildfires, including tax-free qualified disaster relief payments, leave donation programs, and other tax-efficient options.
Qualified Disaster Relief Payments
Generally, payments made by an employer to, or for the benefit of, an employee must be included in the employee’s taxable gross income unless excluded under another provision. One such exclusion is “qualified disaster relief payments” under Section 139 of the Internal Revenue Code. Employers can make “qualified disaster relief payments” to employees who are victims of many disasters, including the Los Angeles wildfires, on a tax-free basis.
Qualified disaster relief payments include both reimbursements and cash advances and are not treated as taxable income/wages subject to payroll taxes (e.g., Federal Insurance Contributions Act and Federal Unemployment Tax Act) for employees. In addition, employers can deduct these payments as ordinary and necessary business expenses.
A payment qualifies as a “qualified disaster relief payment” if the following requirements are satisfied:
- There has been a “qualified disaster” (e.g., a federally declared disaster issued by the president of the United States).
- The payment is intended to cover reasonable and necessary personal, family, living, or funeral expenses, or reasonable and necessary expenses incurred for repairing or replacing a personal residence or its contents, provided the expenses were incurred as a result of the qualified disaster and are not covered by insurance or other resources.
- The payment is not income replacement (i.e., a payment for lost wages, lost business income, or unemployment benefits).
Qualified disaster relief payments do not need to be paid pursuant to a plan document. In fact, a formal written plan document is not required or recommended. Nevertheless, given the benefits of tax-free status for qualified disaster relief payments, employers that choose to provide such payments should consider adopting an administrative process to validate such payments meet the necessary legal requirements. Such a process can include a short application form for assistance that validates the disaster for which relief is sought, contains an affirmative statement from the employee that the requested funds are necessary for expenses associated with the Los Angeles wildfires, and confirms that such expenses are not reimbursable by insurance.
In addition, employees are not required to account for actual expenses in order to qualify for the exclusion, provided that the amount of the payments can be reasonably expected to be commensurate with the expenses incurred. Although substantiation is not required, a simple application/attestation statement from the employee is recommended to provide the employer with assurance regarding its compliance with the legal requirements for offering these payments on a tax-free basis.
Leave Donation Programs
Since the wildfires have been federally declared a natural disaster, an employer may establish “leave banks” for employees to donate accrued but unused leave to other employees who may be affected by the wildfires. Employees who donate their accrued leave are exempt from taxes on those amounts, but those who receive the leave will incur payroll and income taxes for the time given. Employer-sponsored leave banks programs must be written and must meet certain requirements under IRS Notice 2006-59 to receive favorable tax treatment for both the donor and recipient employee.
Retirement Plan Options
An employer-sponsored defined contribution retirement plan can provide additional relief to “qualified individuals” impacted by a qualified disaster. A “qualified individual” is an individual whose principal residence during the incident period of any qualified disaster is in the qualified disaster area and the individual has sustained an economic loss by reason of that qualified disaster. Employer-provided retirement plans can provide the following options:
- Distributions up to $22,000 per federally declared disaster, with no early withdrawal penalty. Such distributions must be taken within 180 days of the date the disaster was declared.
- Increased maximum loan amounts equal to 100% of a participant’s account balance, up to $100,000.
- Extended repayment period of one year for current outstanding loans (as of date such natural disaster was declared). In this case, employers can extend repayment of loans to January 8, 2026.
Employers will need to amend their retirement plans if their plans do not already have such disaster-related provisions. Such amendments must be made by the end of this year for employees to take advantage of these provisions.
Summary
Employers seeking to provide financial assistance to employees should consider the various tax-advantaged programs made available by the IRS. Since the requirements of each program vary, it is important that employers properly structure these programs to comply with the necessary legal requirements.

Four Factors to Consider After the Building Electromobility Infrastructure Act (GEIG) Comes into Effect
ARTICLE / CLIENT ALERT
Four Factors to Consider After the Building Electromobility Infrastructure Act (GEIG) Comes into Effect
January 16, 2025
Read time: 3 min
As of January 1, 2025, the Building Electromobility Infrastructure Act (GEIG) has come into effect, bringing significant changes for property owners. Dr. Ulrich Flege summarizes the key points of the law below:
Obligation to Provide Charging Infrastructure
All non-residential buildings with more than 20 parking spaces must provide at least one charging point for electric vehicles. This applies to both new buildings and existing buildings undergoing extensive renovations. This regulation aims to increase the availability of charging infrastructure and promote the use of electric vehicles.
Requirements for Renovations
For major renovations of non-residential buildings with more than 10 parking spaces, protective conduits for electric cables must be installed – for every fifth parking space. Additionally, at least one charging point must be provided. A “major renovation” is defined as a renovation where more than 25 percent of the building envelope’s surface area is renovated (GEIG – Act on the Development of Building-Integrated Charging and Line Infrastructure for Electromobility). These requirements are intended to ensure that the infrastructure for electromobility is also improved in existing buildings.
High Penalties for Non-Compliance with GEIG
Those who do not implement the requirements of the GEIG face fines of up to 10,000 euros. These penalties are intended to ensure that the legal requirements are taken seriously and implemented.
Room for Interpretation
The legislator allows room for interpretation but also provides guidelines. For example, a “major renovation” is defined as a renovation where more than 25 percent of the building envelope’s surface area is renovated. However, there is room for interpretation as to when and to what extent measures must be taken. Therefore, it is advisable to seek legal advice in case of doubt to ensure that all legal requirements are met.
The McDermott team is happy to assist you with legal questions. Contact us.
Further information on the legal measures in the building sector can be found in this article.

ASTP Final Rule Codifies Requirements for TEFCA-Qualified Health Information Networks
CLIENT ALERT / INTEROPERABILITY
ASTP Final Rule Codifies Requirements for TEFCA-Qualified Health Information Networks
January 15, 2025
Read time: 13 min
On December 16, 2024, the US Department of Health and Human Services (HHS) Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) published the Health Data, Technology, and Interoperability: Trusted Exchange Framework and Common Agreement (TEFCA) final rule in the Federal Register as part of its continued focus on improving information sharing among healthcare stakeholders.
Rather than codifying comprehensive substantive and procedural requirements for entities participating in TEFCA, the final rule provides a flexible framework establishing how such decisions will be made in current and future subregulatory documents. It formalizes the relationship between ASTP and the Recognized Coordinating Entity (RCE), establishes baseline procedures and timelines for ASTP and RCE to follow in administering TEFCA, and creates a formal process for ASTP review of certain RCE decisions. This approach is notable in that entities interested in participating in TEFCA must look at sources outside the rule, such as the Common Agreement, to identify ASTP’s purported operational and technical requirements for participation.
ASTP’s approach to the regulation appears designed to achieve the agency’s broader goal of rolling out TEFCA in a staged, flexible, deliberate, and consensus-driven manner. This approach may help TEFCA minimize challenges that previous technology-focused regulations have faced as a result of the pronounced timing differences between the regulatory process and the pace of technology development. TEFCA’s success also depends on stakeholder buy-in and public trust. A regulatory framework that empowers the RCE to remain responsive and adaptive may enable the RCE to address public and stakeholder reservations in a collaborative and constructive way. In a post-Loper Bright era, this flexibility may prove to be a vulnerability if subject to challenge, however.
Background on TEFCA
TEFCA is a set of principles, terms, and technical requirements that aim to facilitate health information exchange by creating a nationwide network of participating health information networks (HINs) that meet all the requirements to exchange data according to TEFCA standards (TEFCA exchange).
TEFCA originated in the 21st Century Cures Act of 2016, which required ASTP to convene public-private and public-public partnerships to build consensus and develop or support a trusted exchange framework, including a common agreement, among HINs nationally. The Cures Act specified that its statutory framework must not be construed to “require” an HIN to adopt or participate in TEFCA (i.e., TEFCA participation must remain voluntary unless the statute is amended to state otherwise).
HINs designated by ASTP to participate in TEFCA exchange are called qualified HINs (QHINs). Entities that contract with a QHIN to access TEFCA exchange are known as participants. Participants can also connect others, known as subparticipants, to participate in TEFCA exchange. The network of participants and subparticipants connected to a QHIN comprise the QHIN’s designated network. To maintain and implement the standards for TEFCA exchange and to oversee the resulting TEFCA network, ASTP may delegate certain authority to one or more RCEs. Currently, the only RCE selected by ASTP is The Sequoia Project.
The standards for TEFCA exchange, requirements for participation, and governance protocols for the TEFCA network are currently set forth in a suite of documents, including the Trusted Exchange Framework and the Common Agreement. The Trusted Exchange Framework describes a common set of foundation principles and practices to facilitate data sharing. The Common Agreement establishes the infrastructure and governing approach for users in different HINs to securely share information with each other. The Common Agreement is a legal contract that is signed by a QHIN and the RCE.
Additional requirements are found in the Standard Operating Procedures (SOPs) and the QHIN Technical Framework (QTF). SOPs are issued by the RCE and provide detailed information or requirements related to the exchange activities under the Common Agreement. The SOPs address governance, privacy, and security requirements; RCE directory services; and QHIN application and designation. The QTF outlines the technical specifications and other technical requirements necessary for QHINs to exchange information.
These documents include the purposes for which information may be requested or sent via TEFCA exchange. There are currently six exchange purposes: treatment, payment, healthcare operations, public health, government benefits determinations, and individual access services (i.e., services permitting individuals to access and obtain their own health data). Currently, QHINs are required to support exchange for any of these purposes, but QHINs, participants, and sub-participants are only required to respond to requests made for treatment or individual access services purposes. ASTP has been clear that it intends to eventually require responses to requests made under any exchange purpose, however.
For more information on TEFCA and for a list of QHINs and candidate QHINs, see The Sequoia Project’s website.
TEFCA Regulations in the Final Rule
With only minor changes from the proposed rule, the final rule creates a new 45 CFR Part 172 with regulations codifying:
- Qualification requirements for QHIN designation
- The processes for QHIN onboarding and designation
- A QHIN attestation process
- QHIN termination and appeals rights
- ASTP’s authority to delegate responsibility to the RCE
The final regulations related to QHIN designation, onboarding, suspension, and termination closely reflect the requirements and processes contained in the Common Agreement and the RCE’s current SOPs. The final rule creates the appeals process for ASTP and RCE decisions and the QHIN attestation process. In the final rule, ASTP added language requiring the RCE to seek and receive ASTP prior authorization before making certain decisions, including QHIN designation decisions, setting and determining QHIN compliance with onboarding requirements, deeming a QHIN designation application withdrawn for failure to respond to requests for more information, and suspending or terminating a QHIN.
Subpart A: Purpose, Definitions, and RCE Authority
Subpart A of the final rule provides the statutory basis for the regulations (Section 3001(c)(9) of the Public Health Service Act) and states that the purpose of the regulations is to promote full network-to-network exchange of health information and to create a voluntary process for QHINs to attest to the adoption of TEFCA. It also defines key terms that mirror the definitions provided in current TEFCA documents. Finally, this subpart lists the responsibilities that ASTP may delegate to the RCE, including QHIN designation and onboarding, suspension, and implementing a QHIN’s self-termination or termination by mutual agreement between the QHIN and the ASTP or the RCE.
Subpart B: Qualifications for Designation as a QHIN
Subpart B contains the required qualifications for designation as a QHIN, which are separated into three categories:
- Ownership requirements
- Exchange requirements
- Designated network services requirements
The first category, ownership, includes requirements for a QHIN:
- To be a US entity
- To not be under foreign control
- To have no director, officers, executives, or owners of 5% or more of the HIN on the US Department of the Treasury’s Specially Designated Nationals and Blocked Persons List or the HHS Office of the Inspector General’s List of Excluded Individuals/Entities
Healthcare data is a critical piece of national infrastructure. According to ASTP, these ownership requirements are intended to protect health data from high-risk actors and ensure that those who control the health information exchanged via TEFCA are subject to US law.
The second category, the exchange requirements, set a floor of technical and operational capabilities that a QHIN must meet. To be designated as a QHIN, an entity must be capable of:
- Exchanging data between two or more unaffiliated parties
- Exchanging all required information (i.e., the electronic health information held by an entity responding to a request via TEFCA exchange that is relevant to a request for a required exchange purpose)
- Exchanging data for at least one exchange purpose
- Receiving and responding to transactions from other QHINs for all exchange purposes
- Initiating transactions for the exchange purposes that the entity will permit its participants and subparticipants to use through TEFCA exchange
The third category of requirements, for designated network services, are meant to ensure that the TEFCA exchange network infrastructure performs at a high level. A QHIN is required to maintain operational and legal authority to operate and govern its designated network. This includes establishing representative and participatory groups that approve network governance processes and participate in governance. QHINs must also maintain dispute resolution procedures and written policies on network oversight and control, security, privacy, data breach response, and change management. QHINs are required to maintain the technical capacity for high volumes of transactions commensurate with the level of TEFCA participants and to maintain secure network-to-network connectivity. Finally, QHINs are required to have adequate financial resources and personnel to support their functions, including maintaining minimum financial reserves or insurance-based cybersecurity coverage.
Subpart B details additional requirements for QHINs offering individual access services to enable patients to gather their own healthcare information, including a requirement to obtain express individual consent and standards for handling individually identifiable information maintained by the QHIN.
Subpart C: The QHIN Designation and Onboarding Process
Subpart C establishes QHIN onboarding and designation processes, including application submission, review, and withdrawal processes. Onboarding is the process of a prospective QHIN becoming operational in the production environment. Designation refers to the written determination that an Applicant QHIN has satisfied all regulatory requirements.
The final regulations include details about what information must be included in a QHIN application and timelines for review of applications. Once an application has been confirmed to be complete, ASTP or the RCE has 60 calendar days to complete its review of an application unless extended by written notice to the applicant. The final rule requires applicants to respond to requests for additional information from ASTP or the RCE and to notify ASTP or the RCE if, following submission of the application, any information in the application becomes untrue or materially changes.
Once approved by ASTP (or the RCE with ASTP’s prior authorization), an Applicant QHIN must submit the signed Common Agreement. The Applicant QHIN has 12 months to complete the onboarding process with ASTP or the RCE, which possess discretion to extend the onboarding period by up to 12 months. During the onboarding process, the Applicant QHIN must regularly check in with ASTP or the RCE to report progress, coordinate technical testing, and address any issues. Once the onboarding requirements are satisfied, the Common Agreement will be countersigned and the Applicant QHIN will receive notice that it has been provisionally designated as a QHIN. The QHIN is then required to submit proof within 30 days of successful completion of a data transaction with all other in-production QHINs according to TEFCA exchange standards and procedures.
If a QHIN submits satisfactory proof, its QHIN designation becomes final 60 days after submission. If unsuccessful, a QHIN must submit an explanation for why it was unable to complete the required transactions and a plan and timeline for addressing any issues. ASTP (or the RCE with ASTP’s prior authorization) would then review the plan within five business days. If a QHIN fails to submit its plan, or if ASTP (or the RCE with ASTP’s prior authorization) rejects the plan, the QHIN’s designation will be revoked.
The final rule permits an Applicant QHIN to withdraw its application any time before designation by providing written notice to ASTP or the RCE. If an application is withdrawn for a failure to respond to a request for information, or if it is rejected, an Applicant QHIN must wait six months before submitting a new application.
Subpart D: Suspension of QHINs, Participants, and Subparticipants
Subpart D includes the circumstances under which a QHIN, participant, or subparticipant may be suspended from participating in TEFCA exchange. Under the final rule, a QHIN may be suspended if the QHIN is responsible for a threat condition. A threat condition exists in the following circumstances:
- A material breach of a Framework Agreement that has not been cured within 15 days of receiving notice of the breach
- A TEFCA security incident
- An event that the ASTP, RCE, QHIN, participant, or subparticipant has reason to believe will disrupt TEFCA exchange
- Any event that could pose a risk to national security interests
ASTP (or the RCE with ASTP’s prior authorization) may also order a QHIN to suspend participants and subparticipants for doing or failing to do something that results in a threat condition. ASTP or the RCE is required to make a reasonable effort to notify the affected parties in advance of a suspension. The final rule also specifies conditions and requirements for a QHIN to suspend sharing data with another QHIN because of reasonable concerns about the privacy or security of the information exchanged.
Subpart E: Termination of a QHIN
The final rule permits a QHIN to voluntarily terminate its designation with 90 business days prior written notice. ASTP (or the RCE with ASTP’s prior authorization) may also immediately terminate a QHIN for a material breach of any applicable regulatory requirements and failure to remedy that breach within 30 days, unless extended by another 30 days by ASTP or the RCE, or for a material breach of the Common Agreement that cannot be remedied.
Subpart F: Review and Appeal of RCE or ASTP Decisions
This subpart establishes a process for review of ASTP’s or the RCE’s decisions, including appeals rights. ASTP retains the authority to review an RCE’s decision at its sole discretion. Applicant QHINs may appeal the denial of their applications, and QHINs can appeal a decision to suspend a QHIN, participant, or subparticipant or terminate a QHIN’s Common Agreement. If ASTP provided prior authorization for a decision, no ASTP personnel involved in the prior authorization may participate in the review of the decision.
A notice of appeal must be submitted electronically to ASTP within 15 days of receiving notice of the decision being appealed. The initial notice of appeal is only required to include the information necessary to apprise ASTP of the appeal. The appealing QHIN will then have 30 calendar days from submission to provide a more fulsome description of the facts supporting its appeal and any documentation it would like considered during the appeal.
ASTP may exercise first review of the RCE’s determination, but a QHIN or Applicant QHIN may seek subsequent review by a hearing officer appointed by the HHS Secretary. An appeal will not stay a decision to suspend or terminate unless ordered by a hearing officer. Review of the RCE’s determination is de novo, and the appealing QHIN or Applicant QHIN has the burden of supporting its appeal by a preponderance of the evidence. The hearing officer is required to issue a written determination of the appeal.
Subpart G: QHIN Attestation Process
Section 4003(b) of the Cures Act requires HHS to establish a process for HINs to attest to adoption of the Trusted Exchange Framework and the Common Agreement. This subpart details the process for QHINs to submit an attestation, ASTP’s review of the attestation, and requirements for the creation and maintenance of a directory of designated QHINs.
The McDermott Difference
If you have questions about how the final rule may affect your organization, please contact any of the authors of this On the Subject or your regular McDermott lawyer.

ASTP Adopts New Protecting Care Access Exception
CLIENT ALERT / INFORMATION BLOCKING
ASTP Adopts New Protecting Care Access Exception
January 15, 2025
Read time: 8 min
On December 17, 2024, the US Department of Health and Human Services (HHS) Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) published the Health Data, Technology, and Interoperability: Protecting Care Access (HTI-3) final rule in the Federal Register. The final rule establishes the new protecting care access exception to the 21st Century Cures Act’s information blocking prohibition and makes minor amendments to two existing information blocking exceptions. The final rule finalizes information blocking regulatory changes that ASTP proposed in the HTI-2 Patient Engagement, Information Sharing, and Public Health Interoperability proposed rule.
ASTP adopted the protecting care access exception to address concerns that an actor subject to the information blocking prohibition may have about a patient’s, health care provider’s, or other person’s risk of potential exposure to an investigation, liability, or other legal action resulting from the access, exchange, or use of electronic health information (EHI) that indicates an abortion or other reproductive healthcare was sought, obtained, provided, or facilitated. ASTP notes that the concerns emanate from the new legal landscape in the wake of the Supreme Court of the United States’ 2022 decision in Dobbs v. Jackson Women’s Health Organization. Since that decision, some states have enforced laws or are contemplating legislation that authorizes administrative, civil, or criminal legal action against persons who engage in reproductive healthcare that is permitted by the law of the state in which the care is provided.
The HHS Office for Civil Rights (OCR) addressed the same concerns in its final rule amending the Health Insurance Portability and Accountability Act of 1996 Privacy Rule to prohibit the use and disclosure of protected health information potentially related to reproductive health care for certain legal actions. As part of the HTI-3 final rule, ASTP adopted substantially the same definition of reproductive health care.
Both the HTI-3 and OCR final rules are final agency actions; however, the incoming Trump administration has signaled that it may further act on these rules given different political views tied to reproductive health care. Specifically, the new administration has suggested further review of the new regulations that could result in delay, adjustments, or even full repeal. ASTP had, to some degree, anticipated these possible actions and divided its HTI-2 proposals into several different final rules that the new policy leads could review separately. For now, the HTI-3 final rule changes took effect on December 17, 2024.
New Protecting Care Access Exception
Under the protecting care access exception, a practice by a health care provider, health information network and health information exchange (HIN/HIE), or certified health IT developer (each, an actor) that is implemented to reduce potential exposure to legal action will not be information blocking when the practice satisfies the requirements of the exception’s threshold condition and either the exception’s patient protection or care access conditions.
Threshold Condition
To satisfy the threshold condition, an actor’s practice must meet each of the following requirements:
- Good faith belief. The practice is based on the actor’s good faith belief that persons seeking, obtaining, providing, or facilitating reproductive health care are at risk of being potentially exposed to legal action that could arise as a consequence of particular access, exchange, or use of specific EHI, and the practice could reduce that risk. According to ASTP, an actor’s belief does not need to be accurate, provided that it is held in good faith. ASTP advises that to hold a belief in good faith, an actor does not need to conduct tracking, detailed analysis, or extensive research of laws under which the actor does not furnish health care and does not provide HIN/HIE functionality or other health IT items or services to health care providers.
- Tailoring. The practice is no broader than necessary to reduce the risk of potential exposure to legal action that the actor in good faith believes could arise from the particular access, exchange, or use of the specific EHI.
- Implementation. The actor implements the practice either consistent with a written organizational policy or pursuant to a case-by-case determination, either of which must meet requirements specified in the final rule’s regulation text.
An actor who is a business associate of, or otherwise maintains EHI on behalf of, another actor may rely on the good faith belief and organizational policy or case-by-case determinations of the actor on whose behalf relevant EHI is maintained.
Patient Protection Condition
When an actor implements a practice to reduce the patient’s risk of potential exposure to legal action, the practice must:
- Affect only the access, exchange, or use of specific EHI the actor in good faith believes could expose the patient to legal action because the EHI shows, or would carry a substantial risk of supporting a reasonable inference, that the patient obtained reproductive health care; inquired about or expressed an interest in seeking reproductive health care; or has any health condition(s) or history for which reproductive health care is often sought, obtained, or medically indicated.
- Be subject to nullification by an explicit request or directive from the patient that the access, exchange, or use of the specific EHI occur despite the risks to the patient that the actor has identified.
Care Access Condition
When an actor implements a practice to reduce the risk of potential exposure to legal action for licensed health care professionals, other health care providers, or other persons involved in providing or facilitating reproductive health care that is lawful under the circumstances in which it is provided, the practice must affect only access, exchange, or use of specific EHI that the actor believes could expose care providers and facilitators to legal action because the EHI shows, or would carry a substantial risk of supporting a reasonable inference, that they provide or facilitate, or have provided or have facilitated, reproductive health care.
Presumption
For purposes of determining whether reproductive health care is lawful under the circumstances in which it is provided, care provided by someone other than the actor is presumed to have been lawful unless the actor has actual knowledge that the care was not lawful under the circumstances in which such care is it was provided.
Privacy Exception Amendment
The existing privacy exception to the information blocking prohibition includes four sub-exceptions intended to allow an actor to deny a request to access, exchange, or use EHI to protect an individual’s privacy. The fourth sub-exception allows an actor to not fulfill a request for EHI at the request of an individual. ASTP expanded the sub-exception by removing a limitation to individual-requested restrictions that was contingent on whether another law required the EHI be accessed, exchanged, or used.
Infeasibility Exception Amendment
The existing infeasibility exception includes a segmentation condition that allows an actor to deny a request for EHI if the actor cannot fulfill it because the actor cannot unambiguously segment the requested EHI from EHI that cannot be shared. The final rule expands the segmentation condition to cover all of the sub-exceptions under the privacy exception and the new protecting care access exception discussed above.
Action Items and Next Steps
Actors should consider taking the following steps in response to the final rule:
- Evaluate whether the actor wants to leverage the new protecting care access exception to protect the privacy of patients who have received or will receive reproductive health care, including in light of the laws of the states in which the actor conducts business.
- Review and revise existing information blocking and privacy policies and procedures to reflect the revisions to the information blocking exceptions included in the HTI-3 final rule.
- Educate reproductive health care providers about the special privacy and information blocking considerations related to EHI and other protected health information potentially related to reproductive health care.
- Monitor for additional updates from the new Trump administration as it reviews the implications of this final rule.
The McDermott Difference
If you have questions about how the final rule affects your organization, please contact any of the authors of this On the Subject or your regular McDermott lawyer.

An overview of the new Consumer Credit Directive
ARTICLE
An overview of the new Consumer Credit Directive
December 6, 2024
Read time: 2 min
One year after the new EU Consumer Credit Directive (Directive 2023/2225) came into force, questions remain: When will it be implemented? What will be regulated? How is the business community reacting? The directive brings significant changes and extensions in an effort to strengthen consumer protection and meet the challenges of digitization. But does it really provide consumers with the desired added value and protection, or does it prevent innovative, successful business models – from which consumers benefit – via overregulation?
Read the full article, “An overview of the new consumer credit directive,” written by Renate Prinz, on our FinRegNews Blog.
Sign up now for regular FinRegNews updates.

EMIR 3: Active Accounts, clearing threshold and exemptions
ARTICLE
EMIR 3: Active Accounts, clearing threshold and exemptions
December 6, 2024
Read time: 2 min
On December 4, 2024, EU Regulation 2024/2987 (“EMIR 3”), amending EU Regulation 648/2012 on the European Market Infrastructure (“EMIR”), was published in the EU Official Journal. EMIR 3 will enter into force on December 24, 2024, although certain provisions will remain subject to the Regulatory Technical Standards that will be published by the European Securities and Markets Commission (“ESMA”).
Learn more about EMIR 3 in the latest article on our Financial Regulatory News blog, “EMIR 3: Active accounts, clearing threshold, and exemptions,” written by Michal Chajdukowsk.
Sign up now for regular FinRegNews updates.

MiCAR in Practice: BaFin Issues Guidance on Crypto Services
ARTICLE
MiCAR in Practice: BaFin Issues Guidance on Crypto Services
Januar 10, 2025
Read time: 2 min
Clear rules for crypto-asset service providers: BaFin’s new MiCAR information sheet creates transparency and provides important guidance for providers of crypto-asset services.
Renate Prinz and Annabelle Rau summarize the key contents of the new BaFin leaflet in the latest update on our FinRegNews Blog.
Sign up now for regular FinRegNews updates.