Content Type: Article

  • First-Out, Last-Out: Still trending?

    First-Out, Last-Out: Still trending?

    ARTICLE / CLIENT ALERT

    First-Out, Last-Out: Still trending?

    November 24, 2020

    Read time: 5 min

    Key takeaways
    Overview

    First-Out, Last-Out structures (FOLO), traditionally a key feature of the European mid-market space, seem to have experienced a gradual decline in some markets – whether because of an inadequate return profile or due to a reshaping of the relationships between credit funds and banks vis-à-vis their respective market shares. While market commentary has been quick to point out the decline, FOLO days may not be over yet.

    In depth

    What Is FOLO?

    Post financial crisis, the rise of private debt funds combined with reduced bank liquidity has meant that banks are no longer the key credit providers. FOLOs are a derivative of unitranche structures, allowing a single tranche of term loan to combine senior and junior debt with a blended interest component.

    Whilst the primary goal is to create one efficient streamlined process, certain features should be noted:

    • Deals which would include two main credit documents (e.g., senior/mezzanine or first-lien/second-lien) are papered using just one. FOLOs are documented under a single credit facility, but behind the scenes, in a side agreement between the lenders (AAL), the loan is split into first-out and last-out pieces, where the last-out are paid more interest (given longer skin in the game).
    • The AAL is a separate document entered into between the lenders and kept confidential from the borrowers. There has been no notable testing of AALs in the English courts.
    • Unitranche facilities are often coupled with revolving facilities for liquidity (RCFs) provided on a super senior or first-out basis and often by traditional lending banks rather than credit funds. In FOLOs, the super senior term loan and RCF (and sometimes a proportion of the hedging liabilities) will constitute the first-out piece and rank ahead of the senior term loan (last-out) as to enforcement proceeds.
    • Whilst RCFs have traditionally been provided by banks, private credit funds are increasingly willing to either underwrite these for quick execution before selling down their position, or even to provide the RCF on an ongoing basis.
    • In a typical unitranche deal, the instructing group for enforcement purposes is based on a ‘majority senior lenders’ concept, with FOLOs instead utilising (primarily) the majority of the last-out creditors and the super senior or first-out lenders are given certain step-in rights following the expiry of a standstill period after which they can, subject to certain conditions, take control of any enforcement process.
    • Pricing is typically higher than syndicated bank financings but lower than that of first-lien/second-lien.

    Advantages and Disadvantages

    From a borrower’s perspective, FOLOs represent simplified negotiation processes, reduced execution risk and certainty through an absence of flex terms (as present in syndicated financings), but market participants have raised some concerns that bring the future of FOLOs into question:

    • FOLO returns may not be sufficient in comparison to the returns the banks often need to yield to make a trading profit.
    • Banks view providing the RCF as supporting the direct lenders, which makes them significantly less attractive, the only concomitant benefit being some control over the day-to-day banking requirements of the underlying borrower.
    • Early covenant triggers for the last-out creditors keep banks out of any enforcement process, thereby reducing their participation in recovery strategies.
    • Some LPs (e.g., pension funds) are taking on the super senior or first-out piece direct to benefit from the associated return, further reducing bank involvement.
    • A layer of super senior debt can be viewed as obstructive in a restructuring, particularly in light of cross-class cramdown regimes being introduced in the United Kingdom and globally.

    Does FOLO Still Have a Part to Play?

    With the COVID-19 outbreak leading to increased and speedy utilisation of working capital lines, traditional FOLO players are reassessing their risk strategies. The increasing competition between private debt funds and banks has brought further debate into an already-troubled dynamic.

    The proliferation of funds willing to provide a one-stop shop may mean that FOLO structures lose their place in the market. Questions are being asked from both sides: on the one hand, banks are less willing to sit behind credit funds in an enforcement process, and on the other, in a market where restructurings are becoming a more popular means of debt reorganisation, direct lenders view a layer of super senior debt as potentially worsening the process for them, without the traditionally high returns associated with FOLO structures.

    It is not all doom and gloom for FOLOs across Europe, however. Certain jurisdictions, such as Germany and Belgium, have been able to continue to offer lower pricing and therefore to benefit from the advantages of FOLOs without being under-compensated for their risk. It remains to be seen if there will be some return to this lower-risk style of lending in a post-COVID-19 environment.

    Authors

    Aymen Mahmoud

    Partner

    London – 22 Bishopsgate

    Giulia Venanzoni

    Counsel

    London – 22 Bishopsgate

    More insights

  • Brexit and Marketing Notifications under AIFMD

    Brexit and Marketing Notifications under AIFMD

    ARTICLE / CLIENT ALERT

    Brexit and Marketing Notifications under AIFMD

    25 November 2020

    Read time: 3 min

    Key takeaways
    Overview

    UK managers (“UK AIFMs”) that currently market their funds in Europe under the national private placement regimes implementing Article 36 of the Alternative Investment Fund Managers Directive (“AIFMD”) should be aware that their existing marketing notifications will lapse on 1 Jan. 2021.

    Following the end of the Brexit transition period, the UK will be considered a “third-country” for the purposes of AIFMD and Article 36 will no longer apply. Instead, UK AIFMs will need to rely on the local regimes established under Article 42 of AIFMD to market their funds, as third-country AIFMs.

    Subject to the necessary cooperation agreements being in place between the FCA and the relevant EEA member state regulators (which is expected to be the case following the end of the Brexit transition period), UK AIFMs will be required to make separate notifications under Article 42 in each relevant country if they wish to continue marketing their funds. UK AIFMs should be able to market in the same jurisdictions under Article 42, as currently under Article 36.

    As third-country managers, UK AIFMs will also be required to submit Annex IV transparency reports on a country-by-country basis to the relevant member state regulators (in addition to continuing with their AIF001/002 reporting to the FCA).

    UK AIFMs that wish to continue marketing their funds after 1 Jan. 2021 should prepare and submit their Article 42 notifications in the relevant EEA countries as soon as possible. No notifications are required if the UK AIFM no longer wishes to market its funds.

    Authored by Anna Maleva-Otto, Christopher Hilditch and Olivia Cork.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.


    This communication is issued by Schulte Roth & Zabel LLP and Schulte Roth & Zabel International 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. ©2020 Schulte Roth & Zabel LLP and Schulte Roth & Zabel International LLP.

    All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.

    In depth
    Authors

    Christopher Hilditch

    Partner

    London – One Eagle Place

    More insights

  • OIG Finalizes Revisions to Safe Harbor Protection for Drug Rebates and Establishes New Safe Harbors for Point-of-Sale Price Reductions, PBM Service Fees

    ARTICLE / CLIENT ALERT

    OIG Finalizes Revisions to Safe Harbor Protection for Drug Rebates and Establishes New Safe Harbors for Point-of-Sale Price Reductions, PBM Service Fees

    November 23, 2020

    Read time: 4 min

    Key takeaways
    Overview

    On November 20, 2020, the US Department of Health and Human Services (HHS) Office of Inspector General (OIG) released a final rule as part of ongoing administration drug pricing reform efforts and in conjunction with the release of several other significant final rules (for more information about the other rules HHS released on November 20, 2020, please see Regulatory Sprint to Coordinated Care. The final rule—scheduled to be officially published in the Federal Register on November 30, 2020—largely adopted the policies proposed in OIG’s related notice of proposed rulemaking (proposed rule), which we previously discussed in this On the Subject. Once effective, the final rule will modify a regulatory provision that had previously protected certain pharmaceutical manufacturer rebates from criminal prosecution and sanctions under the federal Anti-Kickback Statute, and will instead provide an alternative pathway to protection for certain price reductions made available at the point of sale. The final rule will also provide protection for certain fees that a manufacturer might pay to a pharmacy benefit manager (PBM).

    In depth

    Specifically, the final rule will exclude rebates and other discounts on prescription pharmaceutical products offered by pharmaceutical manufacturers to Medicare Part D plan sponsors from protection under the discount safe harbor, unless the price reduction is required by law. The proposed rule had also proposed to exclude discounts to Medicaid Managed Care Organizations (MCOs), but commenters persuaded OIG to not finalize those changes. Thus, the final rule’s exclusion will apply only to pharmaceutical manufacturer discounts and rebates offered directly to Part D plan sponsors, and those negotiated by or paid through a PBM acting under contract with a Part D plan sponsor. OIG also confirmed that, despite the modification under the final rule, it intends for the discount safe harbor to continue to protect discounts on prescription pharmaceutical products offered by pharmaceutical manufacturers to other entities, including, but not limited to, wholesalers, hospitals, physicians, pharmacies and third-party payors in other Federal health care programs. The final rule makes this modification effective on January 1, 2022.

    In addition, the final rule will add two new regulatory safe harbors for:

    • Certain price reductions that are fully passed through to the dispensing pharmacy and applied to the price charged to a Medicare Part D plan or Medicaid MCO member at the point of sale; and
    • Fixed fee payments from manufacturers to PBMs for the services that PBMs provide to those manufacturers. In order to be protected, the fees would have to be for services provided to the manufacturer that relate to the PBM’s arrangements with health plans (e.g., services that rely on data collected from health plan customers).

    These new safe harbors will become effective 60 days following publication of the final rule in the Federal Register (assuming a November 30, 2020 publication date, that would make the new safe harbors available starting on January 29, 2021).

    The potential implications of the final rule extend beyond the context of federal Anti-Kickback Statute compliance to drug reimbursement in the United States more broadly. Public debate and legal scrutiny of the final rule and its policies will likely continue.

    The final rule can be found here and the HHS factsheet is available here.

    Please do not hesitate to contact your regular McDermott lawyer or any of the authors of this On the Subject if you have questions or need assistance with evaluating and structuring discount and related arrangements in light of the final rule.

    Authors

    James A. Cannatti III

    Partner

    Washington, DC

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Tony Maida

    Partner

    New York – One Vanderbilt Avenue

    Monica Wallace

    Partner

    Chicago

    More insights

  • Sticky Situation? Circumstantial Evidence Can Support Intent to Confuse in Trade Dress Claims

    ARTICLE

    Sticky Situation? Circumstantial Evidence Can Support Intent to Confuse in Trade Dress Claims

    November 23, 2020

    Read time: 1 min

    Key takeaways
    Overview
    In depth
    Authors
    More insights

  • Viewpoint: Customer Privacy Must be Considered in Bankruptcy

    ARTICLE

    Viewpoint: Customer Privacy Must be Considered in Bankruptcy

    November 23, 2020

    Read time: 1 min

    Key takeaways
    Overview
    In depth
    Authors
    More insights

  • New SEC Guidance on Compliance Responsibilities of Fund Managers and Chief Compliance Officers

    New SEC Guidance on Compliance Responsibilities of Fund Managers and Chief Compliance Officers

    ARTICLE / CLIENT ALERT

    New SEC Guidance on Compliance Responsibilities of Fund Managers and Chief Compliance Officers

    November 23, 2020

    Read time: 9 min

    Key takeaways
    Overview

    On Nov. 19, 2020, the SEC’s Office of Compliance Inspections and Examinations and its director provided unprecedented guidance with respect to the responsibilities of private fund managers and their chief compliance officers. The public guidance, which is consistent with comments we have observed from OCIE examination staff, identifies numerous strengths and weaknesses of the compliance programs of SEC-registered investment advisers. Private fund managers and their CCOs should evaluate their compliance programs in light of this guidance.

    As is customary, the Director of OCIE, Peter Driscoll, addressed the annual Investment Adviser/Investment Company Outreach program; he presented statistics for the 2020 fiscal year (e.g., conducting over 2,950 examinations, holding 300 outreach events, issuing a cybersecurity report and publishing eight risk alerts) and highlighted areas of focus during the year (including Regulation Best Interest and Form CRS compliance, LIBOR transition preparedness and asset verification).[1]

    What was less customary was a plain English direction to senior management at private fund managers and other investment managers about compliance resource and support levels. Summarized in three words as “empowerment, seniority and authority,” the Director gave a very straightforward assessment of shortcoming he sees, highlighting that:

    “We notice when a CCO holds one or more roles in a firm and is inattentive to their compliance responsibilities.

    We notice when a firm positions a CCO too low in the organization to make meaningful change and have a substantive impact, such as a mid-level officer or placed under the CFO function.

    We notice when CCOs are expected to create policies and procedures, but are not given the resources to hire personnel or engage vendors to provide systems to implement those policies and procedures.

    We notice when a CCO is replaced because they challenge questionable activities or behavior.

    We notice when a CCO is trotted out for an examination or sits silently in the corner in compliance discussions, overshadowed by firm senior officers.

    We notice when a firm puts responsibility on the CCO for a failure of an employee or an officer to follow a firm policy or procedure.”

    The direction to senior management, and its implicit warning, could not be clearer: “CCOs should not and cannot do it alone and should not and cannot be responsible for all compliance failures.”

    The Director contrasted these troubling observations with positive ones, noting that “we do also see good practices where CCOs are routinely included in business planning and strategy discussions and brought into decision-making early-on … CCO access and interaction with senior management” and “prominence in the firm,” in general “demonstrable actions, not just words, supporting the CCO and compliance[.]” Factors mentioned in the speech that could fall under the “demonstrable actions” rubric include organizational and reporting lines, budget allocations and robust levels of dedicated staffing.

    Registered advisers are required to conduct an annual review of the sufficiency of their compliance program and the efficacy of its implementation. The OCIE Director’s direction and warning should be incorporated into such reviews.

    OCIE Examination Observations and Compliance Guidance

    On the same day as the Director’s comments, OCIE released a Risk Alert entitled “OCIE Observations: Investment Adviser Compliance Programs”[2] that focuses on examination deficiencies observed by OCIE staff, especially deficiencies that relate to Rule 206(4)-7 (“Compliance Rule”).

    The Compliance Rule requires SEC-registered investment advisers to adopt and implement written policies and procedures reasonably designed to prevent violation of the Investment Advisers Act (and the rules promulgated thereunder). The Compliance Rule does not specify a list of necessary actions to satisfy this requirement and, in the Risk Alert, OCIE instructs that “[e]ach adviser should adopt policies and procedures that take into consideration the nature of that firm’s operations. The policies and procedures should be designed to prevent violations from occurring, detect violations that have occurred and correct promptly any violations that have occurred.”

    Annual and Interim Compliance Reviews. The Risk Alert notes that the annual compliance review required under the Compliance Rule should consider:

    • Compliance matters that arose during the previous year;
    • Changes in the business activities of the adviser or its affiliates; and
    • Changes in the Advisers Act or applicable regulations that might suggest a need to revise an adviser’s policies or procedures.

    In addition, the Risk Alert cites the 2003 SEC Adopting Release for the Compliance Rule in stating that “although the Compliance Rule requires only annual reviews, advisers should consider the need for interim reviews in response to significant compliance events, changes in business arrangements, and regulatory developments.”

    This intra-year review point should not be ignored or glossed over. When combined with the Director’s statements and the numerous deficiencies and concerns identified in the Risk Alert, rote reliance on a single annual compliance review may be seen as problematic by the SEC examination staff, and could be particularly problematic if an actual deficiency contributes to harm to clients or a substantive violation of the federal securities laws.

    Concerns over Inadequate Compliance Resources. The Risk Alert identifies several issues and concerns related to “inadequate compliance resources.” These concerns include situations involving:

    • “Dual hatted” CCOs who do not appear to have sufficient knowledge of the Investment Advisers Act or of their compliance responsibilities under the Act or who do not appear to devote sufficient time to fulfilling (and who may not in fact be fulfilling) their CCO responsibilities; and
    • Situations where advisers that “had significantly grown in size or complexity” have not increased their compliance headcount and have not invested in additional information technology resources, resulting in compliance-related deficiencies and failures.

    OCIE also referenced numerous examples of CCOs “who lacked sufficient authority within the adviser to develop and enforce appropriate policies and procedures for the adviser.” As support for this shortcoming, the Risk Alert cited situations where CCOs were restricted from accessing critical compliance information, where senior non-compliance personnel only had limited interaction with the CCO, where CCOs’ knowledge about their firms’ investment and business operations was unreasonably limited and where CCOs simply were not consulted on matters that potentially had compliance implications.

    Annual Review Deficiencies. Annual reviews were also expressly identified as a concern area, with the Risk Alert expressing concern over annual reviews that could not be substantiated in writing, that failed to identify key risk areas for the adviser, or that did not address areas of significant risk for the adviser and its business (with oversight and review of third-party managers, cybersecurity, fee calculations and expense allocations being identified as areas of “significant” risk).

    “Follow Through” Failures. The Risk Alert highlighted numerous areas where advisers failed to carry out actions required to be taken under their compliance policies or failed to follow through on processes that were in place. These “follow through” failures collectively included:

    • Inadequate training programs;
    • Absences of compliance checklists and similar processes;
    • Failures to implement procedures for numerous categories of policies;
    • Inadequate or absent testing programs; and
    • Outdated or inaccurate information (including the use of “off-the-shelf policies”).

    Specific Shortfall Areas. The Risk Alert also includes the following, fairly lengthy, list of specific areas where “OCIE staff observed deficiencies or weaknesses with establishing, implementing or appropriately tailoring their written policies and procedures”:

    Portfolio Management

    • Due diligence and oversight of outside managers.
    • Monitoring compliance with client investment and tax planning strategies.
    • Oversight of third-party service providers.
    • Due diligence and oversight of investments, including alternative assets.
    • Oversight of branch offices and investment advisory representatives to ensure they are complying with the adviser’s policies and procedures.
    • Compliance with regulatory and client investment restrictions.
    • Adherence with investment advisory agreements.

    Marketing

    • Oversight of solicitation arrangements.
    • Prevention of the use of misleading marketing presentations, including on websites.
    • Oversight of the use and accuracy of performance advertising.

    Trading Practices

    • Allocation of soft dollars.
    • Best execution.
    • Trade errors.
    • Restricted securities.

    Disclosures

    • Accuracy of Form ADV.
    • Accuracy of client communications.

    Advisory Fees and Valuation

    • Fee billing processes, including how fees are calculated, tested or monitored for accuracy.
    • Expense reimbursement policies and procedures.
    • Valuation of advisory client assets.

    Safeguards for Client Privacy

    • Regulation S-P.
    • Regulation S-ID.
    • Physical security of client information.
    • Electronic security of client information, including encryption policies.
    • General cybersecurity, including access rights and controls, data loss prevention, penetration testing and/or vulnerability scans, vendor management, employee training or incident response plans.

    Required Books and Records. Written policies and procedures to make and keep accurate books and records as required under Rule 204-2 under the Advisers Act.

    Safeguarding of Client Assets. Written policies and procedures regarding custody and safety of client assets.

    Business Continuity Plans. The maintenance of adequate disaster recovery plans because the business continuity plans were not tested or did not contain contact information or designate responsibility for business continuity plan actions.

    Action Items for Investment Fund Managers

    These public statements may provide important indications of OCIE’s examination approach going forward. Private fund managers of all sizes and types should carefully read both of these documents and should be reviewing the level of investment in their compliance programs and personnel. This should not be a siloed, technical effort — OCIE has clearly expressed a desire for all members of senior managements to be focused on the high bar set by the Risk Alert.

    The coming months will see significant changes with a new Presidential administration and a new SEC Chairman. Fund managers should address the specific points just identified by OCIE and its director to be prepared for scrutiny in the new year.


    Authored by Brian T. Daly and Marc E. Elovitz.

    If you have any questions concerning this Alert, please contact your attorney at Schulte Roth & Zabel or one of the authors.

    In depth
    Authors

    Marc E. Elovitz

    Partner

    New York – 919 Third Avenue

    More insights

  • European Commission White Paper on Levelling the Playing Field as Regards Foreign Subsidies

    European Commission White Paper on Levelling the Playing Field as Regards Foreign Subsidies

    ARTICLE

    European Commission White Paper on Levelling the Playing Field as Regards Foreign Subsidies

    November 19, 2020

    Read time: 2 min

    Key takeaways
    Overview

    The EU Commission plans to create new instruments to address possible distortions in the internal market caused by operators subsidised by third countries. This concerns not only, but in particular, the M&A market. The Commission summarises its considerations in a White Paper on Levelling the Playing Field as Regards Foreign Subsidies and invited the public to comment. The deadline for comments on the White Paper has now expired. Dr. Nikolaus von Jacobs and Dr. Germar Enders provide an overview of what market participants can expect.

    In depth
    Authors
    More insights

  • 8 Steps to Record Employment Decisions in Uncertain Times

    8 Steps to Record Employment Decisions in Uncertain Times

    ARTICLE

    8 Steps to Record Employment Decisions in Uncertain Times

    November 18, 2020

    Read time: 1 min

    Key takeaways
    Overview

     

     

    In depth
    Authors
    More insights

  • US Department of the Treasury Seeks Public Comments on Proposed Terrorism Risk Insurance Program Regulations

    US Department of the Treasury Seeks Public Comments on Proposed Terrorism Risk Insurance Program Regulations

    ARTICLE / CLIENT ALERT

    US Department of the Treasury Seeks Public Comments on Proposed Terrorism Risk Insurance Program Regulations

    November 18, 2020

    Read time: 4 min

    Key takeaways
    Overview

    The US Department of the Treasury (Treasury) published an official notice on November 10, 2020, seeking comments from interested parties on proposed new rules promulgated under the latest version of the Terrorism Risk Insurance Act (TRIA). TRIA was first enacted in 2002 as a temporary government program to provide a federal backstop for certain insured terrorism losses. The act has been amended and extended multiple times since then, most recently in 2019, when the Terrorism Risk Insurance Program (TRIP) was extended until December 31, 2027.

    In depth

    Treasury is seeking comments on certain aspects of the 2019 legislation, including whether any amendments are necessary to the timeframe and process by which Treasury certifies that a covered act of terrorism has occurred—for example, allowing third parties to petition for certification or imposing mandatory timeframes for Treasury to certify an event. Such changes, if implemented, would remove some of the government’s discretion in whether/when to certify that a covered terrorist event has occurred, and could have a meaningful impact on how TRIA might work in practice. Treasury also seeks comments as to whether there should be coverage under TRIA for non-US cyber-related terrorist events that cause losses within the United States, and whether it would be appropriate to change current reimbursement formulas that are thought to favor captive insurers over traditional insurers.

    It is interesting, however, to compare and contrast Treasury’s proposed changes with those recommended earlier this year by the Advisory Committee on Risk-Sharing Mechanisms. The Advisory Committee was created by the 2015 reauthorization of the TRIA legislation to provide advice and recommendations on the creation of private market terrorism risk-sharing mechanisms, and its membership constitutes industry thought leaders. In addition to the issues identified by the Treasury in its November 10 notice of proposed rulemaking, earlier this year the Advisory Committee also recommended in its Report in May 2020 that Treasury and/or the Federal Insurance Office (FIO) consider a wider range of issues, including:

    • Whether the current $100 billion cap on federal payments should be indexed, particularly in light of evolving loss models for Nuclear Biological Chemical and Radiological (NBCR) events
    • Whether industry retention levels also ought to be indexed
    • Whether mandatory recoupment levels (now at 140% of insured losses) and amounts ought to be modified to reverse or reduce the shift in financial responsibility for TRIP losses from the government to policyholders and to study the possibility that for certain terrorism events the federal government might actually make money from recoupment payments.

    It appears from the current proposed rule that Treasury/FIO will not be examining these and other issues identified by the Advisory Committee at this time.

    Should anyone need more detailed information or have an interest in submitting comments to Treasury (comments are due January 11, 2021), we would be pleased to advise further.

    Authors

    Andrea T. Best

    Partner

    London – 22 Bishopsgate

    Thomas M. Dawson

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • ONC Extends Compliance Date for Information Blocking Rule

    ONC Extends Compliance Date for Information Blocking Rule

    CLIENT ALERT / INFORMATION BLOCKING

    ONC Extends Compliance Date for Information Blocking Rule

    November 17, 2020

    Read time: 8 min

    Key takeaways
    Overview

    On November 4, 2020, the US Department of Health and Human Services Office of the National Coordinator for Health Information Technology (ONC) published an interim final rule with comment period in the Federal Register that extends certain compliance dates included in ONC’s May 1, 2020, final rule implementing the 21st Century Cures Act. Among other things, the ONC interim final rule pushed the compliance date for ONC’s information blocking provisions from November 2, 2020, to April 5, 2021. The interim final rule did not make substantive changes to the information blocking provisions or ONC’s Health IT Certification Program.

    In depth

    On November 4, 2020, the US Department of Health and Human Services Office of the National Coordinator for Health Information Technology (ONC) published an interim final rule with comment period (ONC IFR) in the Federal Register that extends certain compliance dates included in ONC’s final rule published in the Federal Register on May 1, 2020, to implement certain provisions of the 21st Century Cures Act. A key extension is the change of the information blocking prohibition applicability date (formerly, the “compliance date”) from November 2, 2020, to April 5, 2021. ONC also extended deadlines for certain health IT certification requirements included in the ONC final rule.

    The ONC IFR did not establish penalties for information blocking by health care providers or make other substantive changes to the information blocking provisions of the ONC final rule or ONC’s Health IT Certification Program. (For more information regarding the substantive requirements of the ONC final rule, see our prior Special Report.) Rather, ONC stated that it is simply providing an extension in response to the unique circumstances of the Coronavirus (COVID-19) pandemic.

    ONC recognized that the original compliance date did not allow sufficient time for covered actors, including certified health IT developers, health care providers and health information networks and health information exchanges (HIN/HIEs), to assess whether their arrangements and practices that involve the access, exchange or use of electronic health information (EHI) comply with the information blocking prohibition and, if appropriate, amend existing arrangements and implement new procedures to avoid information blocking, particularly when many covered actors are on the front lines combating COVID-19. ONC also concluded that certified health IT developers needed more time to update their software to address new requirements for application programming interfaces (APIs), EHI export and other capabilities.

    Although appreciated, the ONC IFR—which spent more than a month under Office of Management and Budget review—came at the 11th hour, with many certified health IT developers and health care providers already well along the path of implementing their information blocking compliance strategies. Balancing against the need for resources to directly and indirectly combat the COVID-19 pandemic, certified health IT developers and health care providers can use the additional few months to test and refine information blocking prohibition compliance procedures. Specifically, health care providers should consider whether the additional time allows them to test or revisit their release of information practices or any plans for the availability of EHI through their patient portals. Similarly, certified health IT developers should evaluate whether the extension to the health IT certification criteria deadlines affect their software development timelines.

    Stakeholders may submit comments to the ONC IFR through 5 pm EST on January 4, 2021.

    The following sections discuss the new compliance dates applicable to (1) certified health IT developers, HIN/HIEs and health care providers, and (2) only certified health IT developers under the ONC’s Health IT Certification Program.

    Changes to Key Compliance Dates Applicable to Certified Health IT Developers, HIN/HIEs and Health Care Providers

    April 5, 2021

    • Information Blocking Provisions

    ONC extended the applicability date for the information blocking prohibition from November 2, 2020, to April 5, 2021. The information blocking provisions prohibit practices that the actor knows are likely to interfere with access, exchange or use of EHI, unless the practices are required by law or are covered by one of the eight exceptions established by ONC. For health care providers, the provider must also know that the practice is unreasonable for it to constitute prohibited information blocking. For the first 18 months, the information blocking provisions will only apply to EHI identified by the data elements represented in the US Core Data for Interoperability (USCDI).

    October 6, 2022

    • Scope of Information Blocking Provisions Expands to the Full Electronic Designated Record Set

    ONC changed the date on which the scope of the information blocking provisions expands from the data elements represented in the USCDI to the full electronic designated record set as defined in the HIPAA regulations from May 2, 2022, to October 6, 2022.

    Changes to Key Dates Applicable Only to Certified Health IT Developers

    April 5, 2021

    The ONC IFR extended the compliance date for the following health IT certification requirements applicable to certified health IT developers from November 2, 2020, to April 5, 2021.

    • Information Blocking Condition of Certification (CoC) requirement

    The Information Blocking CoC provides that a certified health IT developer must not engage in practices that constitute information blocking. Thus, in addition to potential civil monetary penalties for information blocking under the Cures Act, a certified health IT developer may jeopardize its products’ certification status if it engages in information blocking. The April 5, 2021, compliance date for the CoC aligns it with the new applicability date for the ONC final rule’s separate information blocking provisions.

    • Assurances CoC and Maintenance of Certification (MoC) requirements

    The ONC final rule’s Assurances CoC requires certified health IT developers to provide satisfactory assurances that they will not take any action that constitutes information blocking, and will ensure that their health IT conforms to the full scope of the certification criteria. The Assurances MoC requires certified health IT developers to retain all records and information necessary to demonstrate initial and ongoing compliance for 10 years beginning from the date the developer’s health IT is first certified.

    • API CoC – compliance for current API criteria

    The ONC final rule’s API CoC requires health IT developers that offer certified APIs to allow EHI to be accessed, exchanged and used through the certified API without special effort, and to publish complete business and technical documentation via a publicly accessible hyperlink that allows any person to directly access the information without any preconditions or additional steps. The CoC also establishes specific limitations to fees, terms and conditions that certified health IT developers may apply to their certified APIs.

    • Communications CoC/MoC requirements

    The Communications CoC provides that a certified health IT developer must not prohibit or restrict communications regarding the usability, interoperability or security of its health IT; the developer’s business practices; or the manner in which someone has used the developer’s health IT. Until developers have revised their contracts with customers and other contractors in accordance with the CoC, the Communications MoC requires developers to issue an annual written notice to the customers and contractors stating that they may make communications on these topics, even if the customer has agreed to contract provisions that contradict the CoC and would otherwise prohibit such communications.

    December 15, 2021

    • Submission of initial plan for real world testing

    The ONC final rule requires certified health IT developers to submit testing plans to their certifying bodies to test a subset of certified health IT functionality in the setting(s) where the certified health IT modules are (or will be) marketed.

    April 1, 2022

    • Submission of initial attestations

    Certified health IT developers are required to attest on a semiannual basis beginning on April 1, 2022, that they are in compliance with applicable CoC and MoC requirements.

    December 31, 2022

    The ONC IFR extends the deadline for certified health IT developers to update their software to include certain new certified capabilities from May 2, 2022, to December 31, 2022:

    • New standardized API functionality

    Certified health IT developers with certified APIs are required to make available FHIR-based APIs certified to § 170.315(g)(10) by no later than December 31, 2022.

    • 2015 Edition health IT certification criteria updates in the ONC final rule (except for the updated EHI export capability, which is extended until December 31, 2023)

    Certified health IT developers must update health IT modules certified to various other 2015 edition certification criteria to address revised standards and specifications established under the ONC final rule.

    March 15, 2023

    • Submission of initial results of real-world testing

    The ONC final rule requires certified health IT developers to submit the results of real-world testing of each of their certified health IT modules to their certifying bodies each calendar year. The ONC IFR provides that the first real-world testing results report is not due until March 15, 2023.

    December 31, 2023

    • EHI export capability must be made available

    The ONC final rule requires certified health IT developers of health IT modules that are part of a product that electronically stores EHI to provide customers with the ability to export EHI from the product in accordance with a new EHI export certification criterion. This criterion includes the ability to export the EHI of both a single patient and the entire patient population.

    * * *

    In conjunction with the release of the ONC IFR, ONC also issued Frequently Asked Questions on its website. Certified health IT developers and other actors regulated under the ONC final rule should review the Frequently Asked Questions and work with counsel to evaluate whether the guidance affects stakeholders’ approaches to information blocking compliance.

    Please do not hesitate to contact your regular McDermott lawyer or any of the authors of this On the Subject if you have questions about or need assistance implementing compliance with the ONC final rule or its extended compliance dates.

    Authors

    James A. Cannatti III

    Partner

    Washington, DC

    Daniel F. Gottlieb

    Partner

    Chicago

    More insights