Content Type: Article

  • IRS Issues Critical Wage and Apprenticeship Guidance under Inflation Reduction Act of 2022

    IRS Issues Critical Wage and Apprenticeship Guidance under Inflation Reduction Act of 2022

    ARTICLE / CLIENT ALERT

    IRS Issues Critical Wage and Apprenticeship Guidance under Inflation Reduction Act of 2022

    November 30, 2022

    Read time: 5 min

    Key takeaways
    Overview

    The US Department of the Treasury just released its guidance on the labor requirements that must be fulfilled in order to maintain the credit for the full amount for clean energy and infrastructure projects under the Inflation Reduction Act of 2022 (Act). This includes renewable energy, energy storage, hydrogen, biogas, carbon capture and electric vehicle charging infrastructure. The guidance covers the Act’s two fundamental critical labor requirements— providing prevailing wages and employing a certain amount of registered apprentices—that project developers must meet for clean energy projects to maintain the credit for the full amount of 30% for the investment tax credit (ITC) or the full amount of the production tax credit (PTC).

    As detailed further below, depending upon a project’s development status, such guidance either triggers a mad dash to begin construction by January 28, 2023, in order to be exempted from such requirements or continues to leave developers a bit in the dark on operational and administrative requirements for projects beginning construction after January 28, 2023 (as actual wages are not yet published), each assuming formal guidance is published in the Federal Register on November 30.

    In depth

    Key Takeaways

    • The guidance is scheduled to be published Wednesday, November 30, 2022.
    • The guidance starts the clock on a 60-day period for the labor provisions to take effect and impacts renewable energy, storage, hydrogen, biogas and carbon capture projects and electric vehicle charging infrastructure.
    • The net result is twofold and depends upon where a project is on its development timeline.
    • For those projects further along in the development lifecycle and that seek both (i) an exemption from the requirements as well as (ii) qualification for such tax benefits, such projects must be under construction by January 28, 2023, to be exempted from the new requirements (assuming formal guidance is published in the Federal Register on November 30).
    • For such projects, the guidance triggers a sprint to start construction of such projects before the new wage and apprentice requirements take effect.
    • The guidance clarifies that the two existing, long-standing methods to determine the start date of construction on a project still apply: (i) physical work and (ii) 5% safe harbor tests.
    • For those projects not seeking to “beat the clock” and that will start construction after January 28, 2023, there is currently little information about how to actually confirm you are paying appropriate wages.
    • The required wages vary by job type and location.
    • The guidance instructs project developers to access the wages published on the US Department of Labor website at sam.gov.
    • However, there are currently no postings for many job types or locations.
    • The guidance also includes instructions on how to request a wage determination from the department if the information is not available online.
    • Developers should send emails requesting wage determinations to IRAprevailingwage@dol.gov with the “facility, facility location, proposed labor classifications, proposed prevailing wage rates, job descriptions and duties, and any rationale for the proposed classifications.”
    • The guidance reiterates certain information on qualified apprentices under the Act.
    • It states qualified apprentices must be used for 10% to 15% of total labor hours.
    • The percentage is 10% for projects on which construction starts in 2022 or earlier, 12.5% for projects starting construction in 2023 and 15% thereafter.
    • At least one qualified apprentice must be used on any project that at least four individuals will participate.
    • The guidance further directs owners to employ general record-keeping requirements, such as accounting for contractors and subcontractors, to prove to the federal government that they are hiring qualified apprentices or made a good faith effort to find them and that required wages were paid.
    • Such records must identify the wage determinations, the mechanics and laborers who performed the work, the classifications of work they performed, their hours worked in each classification and the wage rates paid for the work.

    Conclusion

    The newly released guidance is important to those developers and investors who may benefit from “beating the clock” in order to gain an exemption from the new requirements. And while the guidance is informative on certain other aspects of project development post the 60-day clock, there are still some gaps that remain for developers to fill in before they can be certain these projects will meet the guidance on wages and pencil out.

    For counseling on your project on how to “beat the clock” or continue to develop and implement further IRS guidance, please contact a McDermott IRA team member. Additionally, we will be hosting a webinar to unpack this topic on Friday, December 2, 2022. Click here to register.

    Authors

    Carl J. Fleming

    Partner

    Washington, DC

    Heather Cooper

    Partner

    Miami

    More insights

  • Clarity for Rural Emergency Hospitals and Changes for Critical Access Hospitals: CMS Finalizes Conditions of Participation and Payment and Enrollment Policies But Pauses Stark Law Flexibilities

    Clarity for Rural Emergency Hospitals and Changes for Critical Access Hospitals: CMS Finalizes Conditions of Participation and Payment and Enrollment Policies But Pauses Stark Law Flexibilities

    ARTICLE / CLIENT ALERT

    Clarity for Rural Emergency Hospitals and Changes for Critical Access Hospitals: CMS Finalizes Conditions of Participation and Payment and Enrollment Policies But Pauses Stark Law Flexibilities

    November 29, 2022

    Read time: 14 min

    Key takeaways
    Overview

    Rural emergency hospitals (REHs) are a new provider type that will allow Medicare to pay for emergency department and other outpatient hospital services in rural areas beginning on January 1, 2023, without requiring the facility to meet the current Medicare definition of a “hospital.”

    Effective January 1, 2023, a REH is eligible for increased reimbursement under Medicare. On November 1, 2022, the Centers for Medicare & Medicaid Services (CMS) finalized the REH conditions of participation (CoPs) and payment rates that will apply to emergency department and outpatient hospital services furnished by REHs in connection with the 2023 Hospital Outpatient Prospective Payment System (OPPS) final rule.

    In depth

    Background

    Under current Medicare program rules, Medicare does not recognize “freestanding emergency departments” or other non-hospital providers of emergency department services. Medicare will only pay for these services at facilities that meet the Medicare definition of a “hospital,” which requires the provision of inpatient services, among other requirements that are often difficult for low-volume facilities to meet. This limitation has presented particular challenges for rural communities, where there may be insufficient patient volume or resources to support inpatient services, but where access to emergency services and higher-level outpatient services is still necessary and may otherwise require travel to distant communities.

    General acute care hospitals with no more than 50 beds located in a rural area and critical access hospitals (CAHs) that meet statutory and regulatory criteria are eligible to convert to REHs.

    REH Services Eligible for Increased Reimbursement

    “Rural emergency hospital services” (REH Services) are now a category of services eligible for reimbursement by Medicare. By statute, REH Services include emergency services and other medical and health services. REH Services must be paid by Medicare at the OPPS rate plus 5%.

    The statute provides considerable flexibility for CMS to define the “other medical and health services” that may be reimbursed as REH Services. CMS finalized its proposal to broadly define REH Services to include all services that are eligible for reimbursement under the OPPS. This provides REHs with considerable flexibility to tailor the services they will offer (provided the REH CoPs are met). The definition will in effect provide a higher reimbursement level for any outpatient service that is eligible for reimbursement under the OPPS.

    Facilities that enroll as REHs are not eligible for reimbursement for acute care inpatient services. As a result, the regulatory definition proposed by CMS will exclude acute inpatient services from the definition of “REH Services.”

    The final CoPs for REHs require REHs to provide basic laboratory services and certain diagnostic services. In addition, REHs may (but are not required to) provide other outpatient services, including radiology, outpatient rehabilitation, surgical, maternal health and behavioral health services. CMS has finalized its proposal that any outpatient service that does not meet the definition of an REH service will be paid at the same rate as if the service was furnished in a hospital outpatient department and paid under a fee schedule other than the OPPS. In effect, a laboratory service furnished by an REH will be paid under the clinical laboratory fee schedule, and other non-REH Services furnished by an REH will be paid under the otherwise applicable fee schedule.

    Following statutory changes implemented in 2017, most off-campus hospital departments are subject to a site-neutral payment methodology that reduced payments to hospitals for services at off-campus locations that began billing Medicare after November 1, 2015. CMS finalized its interpretation of the site-neutral provisions such that REH Services are not subject to this payment reduction. CMS will pay for REH Services at 105% of the OPPS rate, regardless of the location or original date of Medicare billing. CMS also clarified that a provider-based rural health clinic (RHC) that is currently excepted (and entitled to a payment limit per visit based on their all-inclusive rate rather than a national statutory payment limit) may maintain excepted status if the hospital to which the RHC is provider-based converts to an REH.

    Proposed REH Reimbursement Methodology

    Medicare payments for REHs will be made at the OPPS rate for services provided, plus a 5% add-on to the OPPS rate and a fixed monthly payment. By statute, this must be calculated by reference to the 2019 reimbursement for CAHs. CMS maintained its proposed payment reimbursement methodology largely as proposed, despite commentary from the Medicare Payment Advisory Commission (MedPAC) noting that CMS should exclude beneficiary copayments from the payment calculation.

    In the final rule, CMS calculates the monthly facility payment, which is based on reimbursement to CAH through claims paid for dates of service in calendar year 2019, by including both amounts paid by the Medicare program and from beneficiary copayments. In addition to relying on the CAH claims data, CMS finalized adjustments for certain supplemental payments Medicare makes to CAHs, including new technology payments, outlier claims payments, indirect medical education payments, disproportionate share hospital (DSH) payments, uncompensated care payments and low-volume hospital payments. CMS modified the calculation of the REH add-on payment slightly to exclude the low-volume payment adjustment for CAHs that do not meet the 15 road miles distance requirement.

    As finalized, the monthly REH add-on payment for 2023 will be $272,866. The monthly payment amount for REHs in future years will be based on the 2023 payment, increased by the hospital market basket percentage increase.

    REH Conditions of Participation

    The final CoPs for REHs are taken largely from the CAH CoPs and are largely consistent with the proposed rule. CMS recognized that REHs will not provide inpatient services and therefore will not require the same level of staffing and oversight as general acute care hospitals. However, the CoPs require an REH to maintain a staffed emergency department 24 hours a day, seven days a week, with a physician, nurse practitioner, clinical nurse specialist or physician assistant immediately available to provide emergency services in the facility. REHs also are required to have a transfer agreement in place with a Level I or Level II trauma center. REHs with distinct part skilled nursing units are required to comply with the skilled nursing facility CoPs.

    REHs are required to maintain licensure and operate under applicable state or local licensure laws, which may impose more stringent requirements than CMS, in order to operate as an REH. As required by statute, REHs are limited to an annual average length of stay of 24 hours. CMS emphasizes that REHs could keep patients for more than 24 hours if necessary, but the agency does not anticipate that the frequency with which this might be required would result in an REH exceeding the 24-hour average annual length of stay requirement.

    The final CoPs for REHs also include the following provisions:

    • REHs must be staffed at all times by an individual who is competent in the skills needed to address emergency medical care. There must be adequate medical and nursing personnel qualified in emergency care to meet the needs of the facility. An REH must have a physician or other practitioner on call at all times and available onsite within 30 or 60 minutes (depending on if the facility is located in a frontier area).
    • REHs must develop, implement and maintain a data-driven quality assessment and performance improvement program (QAPI), consisting of the following five parts: (1) program and scope, (2) program data collection and analysis, (3) program activities, (4) executive responsibilities, and (5) a unified and integrated QAPI program for an REH in a multi-hospital system. (REHs that are part of a multi-facility system consisting of multiple separately certified hospitals, CAHs and/or REHs may elect to have a unified and integrated QAPI program in accordance with state and local laws.) Finally, the REH must specifically measure, analyze and track staffing as a quality indicator.
    • Emergency, laboratory, radiologic and pharmaceutical services must be provided to meet the needs of an REH’s patients in a manner consistent with the CoPs for CAHs.
    • REHs must have discharge planning that focuses on returning the patient to a home or community-based setting and aligns with CoPs for hospitals and CAHs. This requirement is notable because the discharge planning CoPs for hospitals and CAHs do not generally apply to outpatients. However, CMS expects that some REH patients may be discharged from the REH to a post-acute setting, and discharge planning would allow for a smooth transition and continuity of care for the patient across the continuum of treatment facilities.
    • REHs are permitted to serve as telehealth originating sites and apply medical staff credentialing rules for telehealth providers similar to those for telehealth services provided in hospitals and CAHs.
    • REHs are allowed to provide any outpatient services consistent with the needs of the community (based on a community needs assessment) that meet certain additional requirements. For example, outpatient services must be provided in a manner based on nationally recognized guidelines or standards of practice, and the REH must have a system for referral of patients receiving outpatient services to different levels of care, as appropriate.

    REH Enrollment Provisions

    To facilitate enrollment of REHs, CMS finalized its proposal to permit REHs to enroll in Medicare through the “change of information” process by submitting a Form CMS-855A, rather than having to terminate the current CAH or hospital enrollment and then submit a new enrollment as an REH. In response to commenters asking about CAHs or rural hospitals that closed after December 27, 2020, but which would otherwise be eligible to convert to an REH, CMS clarified that a CAH or rural hospital that closed may submit a CMS-855A change of information to enroll as an REH. The facility must meet all CoPs for REHs in order to reopen as an REH.

    Stark Law Regulatory Modifications to Accommodate REHs

    Under the final conditions of participation, REHs are required to provide radiology and certain imaging services, clinical laboratory services and outpatient prescription drugs. Each of these services are considered to be “designated health services” within the meaning of the federal self-referral law (the Stark Law). With respect to services furnished to Medicare beneficiaries, an REH would be an entity that furnishes designated health services (a DHS entity).

    There are several regulatory Stark Law exceptions that apply to physician-owned entities and that may currently be relied on by small rural hospitals and CAHs for purposes of Stark Law compliance, such as the rural provider exception and the whole hospital exception. However, once a CAH or a small rural hospital converts to an REH, the entity will no longer qualify as a “hospital” for purposes of the physician self-referral law and will not be able to qualify for the whole hospital exception. The rural provider exception, in contrast, will remain available.

    In the proposed rule, CMS expressed concerned that the Stark Law could serve as an impediment to the enrollment of entities that are owned by or invested in by physicians but are otherwise eligible to become REHs. Accordingly, CMS proposed to create a relatively broad new REH Exception (the REH Exception) that would have permitted physicians to own and invest in REHs. In the proposed exception, CMS did not propose to incorporate many of the limitations imposed by Congress through the Affordable Care Act (ACA) to physician-owned hospitals, including strict limits on expansion of size and additional physician ownership or investment interests. CMS sought comment in the proposed rule as to whether CMS should incorporate requirements for public disclosures of physician ownership and investment or an annual report to CMS in the REH Exception. Due to concerns raised by commenters regarding the risk of program or patient abuse based on the REH Exception as proposed, CMS declined to finalize the proposed exception.

    CMS finalized its definition of “rural emergency hospital,” for purposes of the Stark Law regulations, as proposed. In addition, CMS clarified that REHs located in rural areas will be eligible to rely on the rural provider exception and will not be obligated to comply with the additional requirements applicable to “hospitals” under this exception. Specifically, an REH may qualify for this exception if the entity furnishes substantially all (not less than 75%) of the DHS it furnishes to residents of rural areas.

    CMS finalized its revisions to certain exceptions applicable to compensation arrangements between certain types of DHS entities and physicians to clarify that such exceptions may be used for compensation relationships between REHs and physicians. Because REHs are not “hospitals” within the meaning of the Stark Law or its implementing regulation, these changes are necessary to ensure REHs can qualify for certain regulatory compensation exceptions. Specifically, CMS modified the exceptions for the following types of arrangements to incorporate REHs as entities eligible to rely on the exception, when all elements of the exception are met:

    • Physician recruitment
    • Obstetrical malpractice insurance subsidies
    • Retention payments in rural and underserved areas
    • Electronic prescribing items and services
    • Assistance to compensate a non-physician practitioner
    • Timeshare arrangements.

    CMS is seeking comment on whether revisions to the exception for medical staff incidental benefits are necessary to explicitly clarify that REHs are eligible to utilize the exception, although CMS notes that an REH could use the existing exception even absent modification. CMS is also seeking comment on the need for REHs to recruit physicians to establish or join medical practices in the geographic area served by the REH and how CMS should define an REH’s geographic service area for purposes of physician and non-physician practitioner recruitment.

    Final Definition of “Primary Road” for CAH Designation

    In addition to finalizing the CoPs for REHs, CMS also proposed a definition of “primary roads” in connection with modifications to the CoPs for CAHs. CMS received numerous comments from existing CAHs and hospitals interested in applying for CAH designation expressing concern that the proposed definition of primary roads, which included federal highways with only one lane in each direction, could jeopardize their eligibility to operate as CAHs.

    In line with CMS’ effort to reduce the burden for providers to meet the distance criteria and codify the definition of primary road in a way that would provide greater flexibility, consistency and clarity to providers regarding the distance requirement for CAH eligibility, CMS agreed with the feedback it received through comments that the proposed definition may have had unintended consequences for existing CAHs and/or hospitals interested in applying for CAH designation.

    After review of the comments and consideration of potential unintended implications, CMS took an alternative approach as it related to federal highways and finalized the definition of primary road to include numbered federal highways with two or more lanes each way, similar to the description of numbered state highways. Excluding federal highways with only one lane in each direction is a deviation from the status quo regarding how to measure distance between a CAH and another hospital or CAH and may open opportunities for new CAHs.

    The complete definition is codified at §485.610(c)(2) to include a numbered federal highway, including interstates, intrastates, expressways or any other numbered federal highway with two or more lanes each way; or a numbered state highway with two or more lanes each way.

    Notably, CMS further clarified that an REH established within less than a 35-mile drive (or less than a 15-mile drive in areas with only secondary roads available or in mountainous terrain) will not impact CAH designation. Because an REH cannot provide inpatient services, CMS noted that the services provided and the distinct community purpose served by CAHs and REHs would not duplicate or overlap.

    PRACTICAL IMPLICATIONS

    CMS finalized its proposed expansive definitions that will enable REHs to provide a wide variety of services eligible for payment as REH Services and finalized an REH-favorable approach to calculating the fixed monthly payment amount. Similarly, CMS opted for an enrollment process for REHs that is less burdensome than the standard enrollment process for new providers and clarified that entities that would otherwise have been eligible to enroll as REHs but have closed since December 27, 2020, may nonetheless enroll in Medicare as an REH.

    However, due to strong objections from several commenters, CMS declined to finalize the relatively broad regulatory exception that would have permitted physicians to own and invest in REHs, without many of the restrictions that are generally applicable to physician-owned hospitals. Commenters expressed concerns about the potential for overutilization, misutilization and patient steering due to physician ownership in REHs if the exception was finalized as proposed. CMS noted that commenters did not provide alternative program integrity criteria (outside of those applicable to the whole hospital exception) and, as such, CMS decided not to finalize the proposed REH Exception. It remains to be seen whether the absence of the REH Exception will limit the conversion of physician-owned rural hospitals to REHs.

    Authors

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Caroline Reignley

    Partner

    Washington, DC

    Sandra M. DiVarco

    Partner

    Chicago

    More insights

  • A Healthy Dose of Seeds: Unique Combination Trade Secrets Entitled to Protection

    A Healthy Dose of Seeds: Unique Combination Trade Secrets Entitled to Protection

    ARTICLE

    A Healthy Dose of Seeds: Unique Combination Trade Secrets Entitled to Protection

    Nov 29, 2022

    Read time: 4 min

    Key takeaways
    Overview

    The US Court of Appeals for the Sixth Circuit upheld a jury verdict finding a dietary supplement company liable for misappropriating another company’s research and development (R&D) related to broccoli-seed extract. Caudill Seed & Warehouse Co., Inc. v. Jarrow Formulas, Inc., Case No. 21-5354 (6th Cir. Nov. 10, 2022) (per curiam) (Moore, J., concurring in part and dissenting in part). The decision addressed several issues relating to so-called “combination” trade secrets.

    Caudill manufactures and sells various nutritional supplements, including a supplement made using broccoli-seed extract. Caudill sued Jarrow Formulas for trade secret misappropriation after its Director of Research Ken Ashurst left Caudill and joined Jarrow. Ashurst had led Caudill’s R&D efforts for nine years, including extensively researching the development of broccoli-seed derivatives and assembling a large body of research related to broccoli seeds. After he joined Jarrow, Ashurst delivered a curated collection of broccoli product research to Jarrow and helped it bring its own competing broccoli-seed extract supplement to the market in just four months.

    The case proceeded to trial. The jury found that Caudill had a protectable trade secret; Jarrow misappropriated said trade secret; and Caudill was entitled to more than $2 million in actual losses, more than $400,000 in unjust enrichment damages, and exemplary damages. Jarrow moved for judgment as a matter of law and for a new trial. After the district court denied the motions, Jarrow appealed.

    Jarrow argued that Caudill improperly asserted a “kitchen-sink theory” of trade secrets by broadly defining all its research activities as a single trade secret. Jarrow also argued that Caudill failed to show that it had acquired the alleged trade secret. Finally, Jarrow challenged the damages awards on legal grounds. The Sixth Circuit rejected each of Jarrow’s arguments on appeal.

    The Sixth Circuit first found that Caudill properly defined its alleged trade secret as its “research and development on supplements, broccoli, and chemical compounds.” The Court treated Caudill’s alleged trade secret as a “combination” trade secret (i.e., a collection of elements that individually are generally known but are unique in combination.) The Court concluded that Caudill demonstrated it had assembled a unique collection of processes and information relating to its R&D process, and therefore, Caudill properly defined its entire R&D process as a trade secret. The Court rejected Jarrow’s argument that Caudill’s alleged trade secret mostly consisted of public domain materials on the basis that the materials were unique in combination.

    The Sixth Circuit also rejected Jarrow’s argument that Caudill failed to show that Jarrow acquired and used the entire combination trade secret. The Court noted differing authority on whether a plaintiff alleging a combination trade secret must show acquisition and use of the entire combination but concluded that trade secret law does not require proving acquisition of “each atom” of the combination trade secret. The Court reasoned that when a trade secret consists of a “mass of public information” that has been collected, the defendant will always be able to identify some minute detail of the combination that it did not use. Here, the evidence demonstrated that Jarrow acquired “vast quantities of information” concerning Caudill’s R&D process, and the Court held that this evidence supported a finding of misappropriation.

    Finally, the Sixth Circuit upheld all the damages awarded to Caudill, rejecting Jarrow’s argument that Caudill could not recover the full value of its R&D efforts—more than $2 million—as compensatory damages because that trade secret was not destroyed via public disclosure. The Court rejected this argument, reasoning that the jury could find that the $2 million represented the value of the trade secret to Jarrow. Judge Moore dissented on this point, concluding that if the jury conceived of $2 million as the value of the trade secret conferred to Jarrow, then it should have been included in the jury’s unjust enrichment (as opposed to compensatory damage) award.

    Authors

    Anthony S. Ferrara

    Partner

    Washington, DC

    More insights
    Endnotes

  • Employers Seek Clarity on Reproductive Healthcare Benefits Litigation Following EEOC Commissioner Filing

    Employers Seek Clarity on Reproductive Healthcare Benefits Litigation Following EEOC Commissioner Filing

    ARTICLE / CLIENT ALERT

    Employers Seek Clarity on Reproductive Healthcare Benefits Litigation Following EEOC Commissioner Filing

    November 28, 2022

    Read time: 4 min

    Key takeaways
    Overview

    Following the US Supreme Court’s decision in Dobbs v. Jackson Women’s Health Organization, many employers extended travel benefits to women residing in states where abortion or reproductive health procedures may now be unlawful. Recently, US Equal Employment Opportunity Commission (EEOC) Commissioner Andrea Lucas filed a Commissioner’s Charge against at least three companies alleging that doing so violates Title VII of the Civil Rights Act of 1964 (Title VII) and the Americans with Disabilities Act of 1990 (ADA). Although these charges are not public, it’s believed they mirror a letter that Sharon Fast Gustafson, the former EEOC General Counsel, recently sent en masse to employers around the country also alleging such travel programs violate federal anti-discrimination laws. The EEOC has since issued a statement that Gustafson’s views are her own and do not necessarily reflect those of the EEOC.

    In depth

    When Title VII was amended in 1978 by the Pregnancy Act amendments, language was added requiring pregnancy, childbirth and related medical conditions be treated equally with other medical conductions under an employer’s “fringe benefit programs.” Lucas asserts that providing travel benefits for those seeking abortions provides preferential treatment to women, thus constituting gender discrimination. Her contention is also that travel benefits further implicate religious discrimination by favoring those who terminate pregnancies over those who, for religious reasons, carry a child to term. Her final contention is that the provision of travel benefits violates the ADA, which she claims requires parity of benefits for those with physical disabilities.

    Employers are now asking whether Lucas’ and Gustafson’s position may be the beginning of litigation by the EEOC or private plaintiffs and whether they can take measures to address the legal arguments being raised.

    First, it is doubtful the EEOC will be suing. While Title VII and the ADA authorize a single commissioner to file a Commissioner’s Charge, that Charge will be investigated like any other Charge of Discrimination. If cause is found, EEOC procedure requires in cases garnering public attention (which this most certainly is) that litigation may only be commenced if a majority of the Commissioners (minus the Commissioner who brought the Charge) vote in favor of doing so. In the absence of a quorum, then only the General Counsel of the EEOC may initiate suit. At this time, Lucas would not appear to have such votes.

    Second, employers can and should draft around these contentions to prepare for private suits. Specifically, such travel benefits should cover not only abortion and/or reproductive health, but also all covered services or procedures that are unavailable within a covered individual’s state of residence or area, regardless of the individual’s gender, pregnancy or childbirth status, or disability status. This would make the benefits “available” to everyone.

    Finally, there is a suggestion that, even with such drafting, this travel benefit will still be utilized primarily by non-Christian women, thus supporting a disparate impact claim based on religious discrimination. This is an overreach. Title VII claims require an adverse employment action such as an employee who requests but is denied a travel benefit due to her religion; here, that would be a null set.

    For more information and resources, please view the McDermott interdisciplinary post-Roe working group site or contact the authors below.

    Authors

    Sarah G. Raaii

    Partner

    Chicago

    More insights

  • NYDFS Continues Effort to Amend Cybersecurity Regulation (“Part 500”) and Publishes Revised Proposed Amendments

    NYDFS Continues Effort to Amend Cybersecurity Regulation (“Part 500”) and Publishes Revised Proposed Amendments

    ARTICLE / CLIENT ALERT

    NYDFS Continues Effort to Amend Cybersecurity Regulation (“Part 500”) and Publishes Revised Proposed Amendments

    November 23, 2022

    Read time: 10 min

    Key takeaways
    Overview

    On Nov. 9, 2022, the New York Department of Financial Services (“NYDFS”) published a proposed amendment (“Proposed Amendment”)[1] to its 2017 cybersecurity regulation (“Part 500”), which requires certain NYDFS-regulated financial services companies to, among other things, safeguard consumer data and adopt and implement a cybersecurity program. The Proposed Amendment is subject to a 60-day notice and comment period, which will be open until Jan. 9, 2023. Based on NYDFS’ review of any comments received, NYDFS will either propose further revisions to the Proposed Amendment or adopt the final regulation.

    The Proposed Amendment is the NYDFS’ second rulemaking in its effort to amend Part 500, and follows NYDFS’ Pre-Proposed Amendment, which was published on July 29, 2022 (the “Pre-Proposed Amendment”).[2] The Proposed Amendment generally maintains most of the material changes reflected in the Pre-Proposed Amendment, as well as imposing certain additional regulatory burdens. Key changes in the Proposed Amendment include: (1) a revised definition of “Class A companies” that is narrower than the definition included in the Pre-Proposed Amendment, so that only entities with large New York operations are subject to the heightened requirements applicable to such companies;[3] (2) requiring increased accountability for cybersecurity governance at the board of directors and C-suite levels; (3) allowing more risk-based controls to prevent initial unauthorized systems access and the spread of a cyberattack than those included in the Pre-Proposed Amendment, such as allowing the Chief Information Security Officer (“CISO”) to authorize reasonable alternatives to NYDFS-prescribed multi-factor authentication requirements; (4) putting in place additional requirements to those included in the Pre-Proposed Amendment for incident response, business continuity and disaster recovery testing and training; (5) adding further NYDFS reporting requirements to those included in the Pre-Proposed Amendment; and (6) proposing different implementation periods for certain requirements as compared with the Pre-Proposed Amendment. Each of these key changes is discussed in turn below.

    1. Class A Companies

    • Definition. The Proposed Amendment narrows the definition of “Class A companies” so that only larger entities are subject to the heightened requirements applicable to such companies. A “Class A company” is defined in the Proposed Amendment to only include a covered entity with at least $20 million in gross annual revenue in each of the last two fiscal years from the New York operations of the covered entity and its affiliates; and either (1) over 2,000 employees averaged over the last two fiscal years, including both those of the covered entity and all of its affiliates regardless of location; or (2) over $1 billion in gross annual revenue in each of the last two fiscal years from all business operations of the covered entity and all of its affiliates. The Pre-Proposed Amendment previously defined “Class A companies” to include firms with either (1) over 2,000 employees or (2) over $1 billion in gross annual revenue averaged over the previous three years from all business operations of the covered entity and its affiliates, which would have covered a broader range of entities.
    • Privileged Access and Password Management. Additionally, whereas the Pre-Proposed Amendment required Class A companies to implement a password vaulting solution for privileged accounts, the Proposed Amendment replaces this solution with requirements that Class A companies implement (1) a privileged access management solution, and (2) an automated method for blocking commonly used passwords for all accounts. If it is not feasible to implement an automated password blocking solution, a Class A company’s CISO would be required to approve in writing reasonably equivalent controls on an annual basis.

    2. Increased Accountability for Cybersecurity at the Leadership Level

    • Senior Governing Body. The Proposed Amendment adds a new governance requirement, not previously included in the Pre-Proposed Amendment, mandating that a covered entity’s senior governing body must have sufficient cybersecurity expertise or be advised by persons that have such expertise. It also includes a new requirement that covered entities have in place written cybersecurity policies and procedures subject to approval at least annually by the firm’s senior governing body.

    3. Risk-Based Controls to Prevent Unauthorized Systems Access and the Spread of a Cyberattack

    • CISO. Currently, each covered entity must designate a CISO pursuant to Part 500. The Pre-Proposed Amendment introduced a requirement that the CISO have “adequate independence and authority” to ensure cybersecurity risks are appropriately managed. The Proposed Amendment, however, removes the term “independent” and adds a requirement that the CISO must be able to direct sufficient resources to implement and maintain a cybersecurity program. Additionally, like the Pre-Proposed Amendment, the Proposed Amendment includes a new requirement that the CISO report in writing on the cybersecurity program to the covered entity’s “senior governing body”[4] at least annually. The Proposed Amendment also includes a new requirement and specifies that the report must include plans for remediating material inadequacies in the covered entity’s cybersecurity program.
    • Multi-Factor Authentication. Part 500 currently provides for the CISO’s ability to approve in writing reasonably equivalent or more secure compensating controls in lieu of NYDFS-prescribed multi-factor authentication requirements subject to the CISO’s annual review. The Pre-Proposed Amendment[5] eliminated this ability, but the Proposed Amendment adds it back in.
    • Access Privileges. The Proposed Amendment adds a new requirement (not included in the Pre-Proposed Amendment) that covered entities review access privileges at least annually and that such entities ensure that unnecessary accounts and access privileges are terminated.
    • Password Policy. The Proposed Amendment requires covered entities that utilize passwords as a method of authentication to implement a written password policy that meets industry standards — a new requirement not included in the Pre-Proposed Amendment.

    4. Enhanced Requirements for Vulnerability Management, Penetration Testing and Incident Response, Business Continuity, and Disaster Recovery Testing and Training

    • Vulnerability Management and Penetration Testing. Part 500 currently requires covered entities that do not continuously monitor their information systems to conduct annual penetration testing of such systems. The Pre-Proposed Amendment added a requirement that penetration testing be conducted by a qualified independent party. The Proposed Amendment, in turn, specifies that such a qualified independent party could be either internal (e.g., a firm employee) or external (e.g., a third-party provider or outside expert), and that testing specifically address unauthorized access through social engineering, and adds a new requirement, not previously included in the Pre-Proposed Amendment, that covered entities develop and implement written policies and procedures for vulnerability management. Further, the Proposed Amendment requires penetration testing to be conducted at least annually in addition to the automated scanning of information systems and a manual review of systems not covered by the scans, whereas the Pre-Proposed Amendment required that covered entities either perform penetration testing or conduct continuous scans. Additional requirements introduced in the Proposed Amendment include: (1) putting in place monitoring systems to promptly alert the covered entity to cybersecurity vulnerabilities; (2) timely remediating such vulnerabilities; (3) documenting material issues during testing; and (4) reporting the same to the firm’s senior management and senior governing body.
    • Incident Response, Business Continuity and Disaster Recovery Testing and Training. The Proposed Amendment adds new requirements, not previously included in the Pre-Proposed Amendment, that covered entities (1) test their incident response and business continuity and disaster recovery plans, at least annually, with the participation of all applicable staff (including senior management); and (2) provide relevant training to all employees responsible for implementing such plan.

    5. Additional Reporting Requirements[6]

    Part 500 currently only requires reporting to NYDFS cybersecurity events that have a material likelihood of harming the covered entity’s operations. The Pre-Proposed Amendment added additional requirements for covered entities to notify NYDFS within 72 hours of any cybersecurity event in which an unauthorized user has gained access to a privileged account or any cybersecurity event in which ransomware was deployed within a material part of such covered entity’s systems, as well as within 24 hours of any extortion payment made in connection with a cybersecurity event. Documentation regarding the covered entity’s investigation of a reportable cybersecurity event must be provided to the NYDFS electronically within 90 days of such covered entity’s initial report of the event to the NYDFS. The Proposed Amendment, in turn, preserves these requirements and adds to them a new requirement that covered entities notify NYDFS within 72 hours of becoming aware of a cybersecurity event at a third-party service provider if it affects the covered entity.

    6. Revised Transitional Implementation Periods for Certain Technical Requirements[7]

    Although the NYDFS rulemaking would generally become effective 180 days from the date of publication of the Notice of Adoption in the State Register (“Effective Date”), the Proposed Amendment establishes different timelines for compliance with certain requirements proposed therein. For example, covered entities would have (i) 30 days from the Effective Date to comply with the new NYDFS notice requirements; (ii) one year from the Effective Date to comply with the Proposed Amendment’s data backup requirements; (iii) 18 months from the Effective Date to comply with the new requirement to conduct automated or manual scans of information systems as set forth in the Proposed Amendment; and (iv) two years from the Effective Date to comply with the requirement that covered entities implement written policies and procedures designed to ensure a complete, accurate and documented asset inventory.[8]

    Conclusion

    If adopted as a final rule, coming into compliance with the Proposed Amendment is likely to require substantial time, effort and resources for covered entities, especially in light of the NYDFS’ 180-day implementation period.

    Firms that are subject to Part 500 may wish to comment on aspects of the Proposed Amendment that they believe, for example, would be unduly burdensome or do not sufficiently reflect the operational considerations faced by industry members. They should also consider instances where they believe exemptions or exceptions should apply. Firms may also wish to seek clarification on how the Proposed Amendment would impact other areas of compliance. Comments on the Proposed Amendment must be submitted to the NYDFS before Jan. 9, 2023.

     

    Schulte Roth & Zabel’s lawyers are available to assist you in preparing a public comment or addressing any questions you may have regarding these developments. Please contact the Schulte Roth & Zabel lawyer with whom you usually work, or any of the following attorneys:

    Donald J. Mosher – New York (+1 212.756.2187, donald.mosher@srz.com)

    Alexander M. Kim – New York (+1 212.756.2075, alex.kim@srz.com)

    Melissa G.R. Goldstein – Washington, DC (+1 202.729.7471, melissa.goldstein@srz.com)

    Kara A. Kuchar – New York (+1 212.756.2734, kara.kuchar@srz.com)

    Adam J. Barazani – New York (+1 212.756.2519, adam.barazani@srz.com)

    Jessica Romano – New York (+1 212.756.2205, jessica.romano@srz.com)

    Jessica Sklute – New York (+1 212.756.2180, jessica.sklute@srz.com)

    Noah N. Gillespie – Washington, DC (+1 202.729.7483, noah.gillespie@srz.com)

    Hadas A. Jacobi – New York (+1 212.756.2055, hadas.jacobi@srz.com)

    Rebecca A. Raskind – New York (+1 212.756.2396, rebecca.raskind@srz.com)

    Jesse Weissman – New York (+1 212.756.2460, jesse.weissman@srz.com)


    [1] See Proposed Amendment, available here. Part 500, which originally went into effect on March 1, 2017, establishes cybersecurity requirements for any person or entity “operating under or required to operate under a license, registration, charter, certificate, permit, accreditation or similar authorization under the [New York] Banking Law, the [New York] Insurance Law or the [New York] Financial Services Law.” 23 NYCRR § 500.1(c). Additional information on Part 500 is available on the NYDFS website.

    [2] The Pre-Proposed Amendment was subject to a short pre-proposal comment period, which ended Aug. 18, 2022. For additional information regarding the Pre-Proposed Amendment, please see our prior Alert “NYDFS Publishes Pre-Proposed Amendment to Cybersecurity Regulations (‘Part 500’).”

    [3] Part 500 does not currently include the term “Class A companies.”

    [4] “Senior governing body” is defined to mean “the covered entity’s board of directors (or an appropriate committee thereof) or equivalent governing body or, if neither of those exist, the senior officer of the covered entity responsible for the covered entity’s cybersecurity program.” Proposed § 500.1(p).

    [5] Proposed § 500.12(b).

    [6] See Proposed § 500.17.

    [7] Proposed § 500.22(d).

    [8] See Proposed §§ 500.22(d)(4), 500.13(a).


    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. ©2022 Schulte Roth & Zabel LLP.

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

    In depth
    Authors

    Donald J. Mosher

    Partner

    New York – 919 Third Avenue

    Melissa G.R. Goldstein

    Partner

    New York – 919 Third Avenue

    Adam J. Barazani

    Partner

    New York – 919 Third Avenue

    More insights

  • “It’s So Hard to Say Goodbye…”: Judge Drain Bids Farewell to Bench By Urging Congress to Curtail Section 546(e) Safe Harbor

    “It’s So Hard to Say Goodbye…”: Judge Drain Bids Farewell to Bench By Urging Congress to Curtail Section 546(e) Safe Harbor

    ARTICLE / CLIENT ALERT

    “It’s So Hard to Say Goodbye…”: Judge Drain Bids Farewell to Bench By Urging Congress to Curtail Section 546(e) Safe Harbor

    November 21, 2022

    Read time: 8 min

    Key takeaways
    Overview

    Four years after New York grocery chain Tops’ exit from Chapter 11, U.S. Bankruptcy Judge Robert Drain ruled that the Tops’ Chapter 11 trustee may proceed with litigation against certain private equity investors. The trustee alleged that the investors drove the company into bankruptcy by paying themselves more than $375 million in dividends while neglecting to address Tops’ unfunded pension liabilities. The ruling pushes back against what Judge Drain denounced as improper use of Section 546(e) of the Bankruptcy Code — an exemption that protects certain transactions from being unwound in Chapter 11 if they involve securities or commodities contracts — to defend against lawsuits over leveraged buyouts and private dividends.

    Importantly, Judge Drain suggested directly to Congress a significant tightening of the Section 546(e) safe harbor in the last opinion of his two-decade career on the bench. Judge Drain argued that the safe harbor should apply only to public transactions so that private investors cannot use it to protect themselves, to the detriment of other creditors, if their transactions have no obvious connection to the public securities and commodities markets.

    The investors have moved for leave to appeal Judge Drain’s decision to the U.S. District Court for the Southern District of New York. Halperin v. Morgan Stanley Inv. Mgmt., Inc. (In re Tops Holding II Corp.), No. Chapter 11, 2022 BL 364663, 2022 Bankr. Lexis 2899 (Bankr. S.D.N.Y. Oct. 12, 2022).

    I.  Factual Background

    In late 2007, a Morgan Stanley-led group of private equity investors purchased Tops for $300 million through a leveraged buyout. At the time of purchase, Tops was the largest participating employer in a multiemployer pension plan that was “significantly underfunded.”

    From 2007 to 2013, Tops paid $375 million in dividends to the investors that acquired it in the LBO. Secured debt and cutbacks in capital expenditure funded almost all of these payments.

    Tops filed for bankruptcy in February 2018. Two years later, the Tops post-bankruptcy litigation trustee filed a complaint seeking to claw back the dividend payments made to Tops’ private equity investors between 2007 to 2013 as constructive fraudulent transfers because they rendered the company insolvent. The investors who received the dividends claimed that the Section 546(e) safe harbor protected those dividends from clawback.

    II.  Fraudulent Transfer Law

    The Bankruptcy Code allows bankruptcy trustees to avoid certain transfers made by debtors as fraudulent to facilitate preservation of estate assets. Congress intended these safe harbor provisions to level the playing field among creditors in the event improper prepetition transactions have drained a debtor of its valuable assets.

    A bankruptcy trustee can avoid constructive fraudulent transfers if: (1) the debtor received less than reasonably equivalent value in exchange for the transfer; and (2) the debtor was insolvent at the time that the transfer was made or became insolvent as a result of the transfer, the transfer left the debtor with unreasonably small capital or the debtor intended to incur debts beyond its ability to pay. 11 U.S.C.

    • 548(a)(1)(B). A trustee can also avoid fraudulent transfers under applicable state law.

    Section 546(e) of the Bankruptcy Code affords a complete defense to constructive fraud claims if the requirements of the so-called “safe harbor” are satisfied. The Bankruptcy Code safe harbors transactions that are (1) “a transfer . . . in connection with a securities contract” that (2) is “made by or to (or for the benefit of)” a “financial institution.” 11 U.S.C. § 546(e).

    III.  Legal Analysis

    Tops’ investors argued that Congress protected the dividend payments from avoidance under the Section 546(e) safe harbor — even though the dividends were not themselves safe harbored transfers — because they were partly funded by proceeds from a safe harbored offering of notes “securities contracts.” Further, the investors argued that the payments were transfers made by a qualifying “financial institution” because they were made by Tops’ bank to the investors’ banks, which banks were acting as Tops’ and the investors’ respective agents or custodians.

     A. Qualifying Transaction

    First, Judge Drain found that the dividends were not qualifying transactions under Section 546(e). Judge Drain relied on the Supreme Court’s ruling in Merit Mgmt. Grp., LP v. FTI Consulting, Inc. where it stated, “the only relevant transfer for purposes of the safe harbor is the transfer that the trustee seeks to avoid” and not any intermediary transfers. Merit Mgmt. Grp., LP v. FTI Consulting, Inc., 138 S. Ct. 883, 888 (2018). Judge Drain stated:

    “What clearly is not a ‘settlement payment’ in respect of a securities contract for purposes of section 546(e), however, is a dividend, and because it is the 2009, 2012, and 2013 dividends that the Complaint seeks to avoid . . . Merit Mgmt. requires that they not be safe-harbored under section 546(e). . . . Tops received nothing in exchange for the . . . dividends, whereas a . . . ‘settlement payment’ is an exchange of money or securities that completes a securities transaction. Thus, standing alone, the dividends would not constitute settlement payments for purposes section 546(e).”

    Judge Drain elected not to collapse a series of transaction steps the recipients asserted related to the prepetition dividends, explaining that Merit Mgmt instructs courts to focus the safe harbor analysis on the specific transfer that the trustee seeks to avoid.

    Judge Drain also questioned the practicality of determining when individual transfers in an multi- step transaction are sufficiently linked to warrant applying the safe harbor to the entire transaction. “Such line drawing,” Judge Drain explained, “could easily rise to a nearly metaphysical dimension” and creates “clear potential for abuse.”

    B. Agents and Custodians

    Second, Judge Drain found that the parties involved were not qualifying “financial institutions” under Section 546(e). Judge Drain acknowledged that the conduit banks facilitating the dividend payments might be “financial institutions.” This could satisfy Section 546(e) if the banks acted as the parties’ agents or custodians. However, the investors failed to identify any evidence of formal agency and/or custodial arrangements between the banks, on one hand, and Tops and the investors, on the other. “Without more,” Judge Drain explained, “a bank account holder’s relationship with its bank is merely a creditor-debtor relationship” and not that of agent and principal.

    IV.  Plea to Congress

    Finally, in his last ruling before retiring from the bench, Judge Drain urged Congress to narrow significantly Section 546(e) of the Bankruptcy Code by making it applicable only to public market transactions. Judge Drain stated, “[t]he avoidance of these dividends and the loans that funded them would have no effect on the public securities markets, the ostensible purpose for section 546(e).” Judge Drain condemned the “currently overly broad free pass in section 546(e) that has informed the playbook of private loan and equity participants to loot privately held companies to the detriment of their non-insider creditors with effective impunity.” Judge Drain continued, “[t]here is little doubt that the same playbook has been followed . . . and will continue to be followed unless Congress acts.”

    V.  Key Takeaways

    • Judge Drain’s plea to Congress, if adopted, would greatly expand a trustee’s avoidance powers and could have important ramifications for how parties structure leveraged buyout and restructuring transactions. This is especially true if they involve any form of dividend payments, which are, by definition, transfers without an exchange of reasonably equivalent
    • Even if Congress does not amend the Section 546(e) safe harbor, Judge Drain’s ruling scrutinizes the structure of leveraged buyout and restructuring transactions in light of Merit. Judge Drain would not necessarily protect transfers under Section 546(e) simply because one or more elements of a multi-step transaction satisfies the safe harbor criteria. This diverges from long- considered practice of “collapsing” multi-stage transactions in certain bankruptcy analyses including avoidance
    • Lastly, parties that intend to rely on the safe harbor must note the importance of properly drafted agency and custodial agreements and the role they play in a Section 546(e) analysis. Judge Drain’s ruling clarifies that the absence of formal agency and custodial arrangements could prove fatal to a safe harbor

    Authored by Douglas S. Mintz, Peter J. Amend, Christiana H. Johnson and Kelly (Bucky) Knight.

    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 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. ©2022 Schulte Roth & Zabel LLP. All rights reserved. SCHULTE ROTH & ZABEL is the registered trademark of Schulte Roth & Zabel LLP.

    In depth
    Authors
    More insights

  • New California Law Requires Open Payments Notice to Patients

    New California Law Requires Open Payments Notice to Patients

    ARTICLE / CLIENT ALERT

    New California Law Requires Open Payments Notice to Patients

    November 16, 2022

    Read time: 3 min

    Key takeaways
    Overview

    On September 29, 2022, California Governor Gavin Newsom signed Assembly Bill 1278, which requires physicians and their employers to provide patients with notices about the Open Payments database starting January 1, 2023.

    The federal Open Payments program is designed to promote transparency by requiring applicable manufacturers of drugs, devices, and biological or medical supplies to annually report to the Centers for Medicare & Medicaid Services certain payments and other transfers of value made to physicians, certain advanced practice providers (e.g., nurse practitioners) and teaching hospitals. Currently, pharmaceutical companies in California must disclose their compliance program, including information related to the annual dollar limits on gifts, promotional materials or incentives provided to medical or health professionals (California Health & Safety Code § 119402). The enactment of this new legislation will impose new disclosure requirements specifically onto physicians and their employers regarding physicians’ financial relationships with pharmaceutical and medical device manufacturers.

    Effective January 1, 2023, physicians and surgeons who are licensed pursuant to the California Medical Practice Act or the California Osteopathic Act, or their employers, must provide patients with a written or electronic notice of the Open Payments database at the initial office visit. The new law does not apply to physicians and surgeons working in a hospital emergency room.

    The written or electronic notice must include a signature from the patient or the patient’s representative, the date of signature and the following text:

    • The Open Payments database is a federal tool used to search payments made by drug and device companies to physicians and teaching hospitals. It can be found at https://openpaymentsdata.cms.gov. For informational purposes only, a link to the federal Centers for Medicare and Medicaid Services (CMS) Open Payments web page is provided here. The federal Physician Payments Sunshine Act requires that detailed information about payment and other payments of value worth over ten dollars ($10) from manufacturers of drugs, medical devices, and biologics to physicians and teaching hospitals be made available to the public.

    Physicians and surgeons must retain the notice in the patient’s medical record.

    Physicians and surgeons also are required to post an Open Payments database notice in each location where they practice, in an area where the notice is likely to be seen by all persons who enter the office. Effective January 1, 2024, physicians and surgeons also must conspicuously post the same Open Payments database notice on their practice’s website if any.

    Violation of this law will constitute unprofessional conduct, which may subject violators to disciplinary actions by their respective licensing boards.

    In depth
    Authors
    More insights

  • Recent Employment Law Updates

    Recent Employment Law Updates

    ARTICLE / CLIENT ALERT

    Recent Employment Law Updates

    November 16, 2022

    Read time: 4 min

    Key takeaways
    Overview

    EEOC Releases Updated “Know Your Rights” Poster

    The U.S. Equal Employment Opportunity Commission (EEOC) has released a “Know Your Rights” poster, which replaces the previous “EEO is the Law” poster. The new poster summarizes federal laws prohibiting job discrimination and explains that employees or applicants can file a charge if they believe that they have experienced discrimination. Covered employers are required by federal law to prominently display the poster at their work sites. The EEOC also encourages employers to post a notice digitally.

    The EEOC advises that employers should remove the old poster and display the new one within a reasonable amount of time. Covered employers are subject to fines for noncompliance, with the maximum penalty being $612 per offense.

    New York City’s Private-Sector Vaccine Mandate Has Expired

    New York City’s COVID-19 vaccine mandate for private employers, detailed in a previous Alert, expired on Nov. 1, 2022. The expiration of the private-sector mandate does not curtail an employer’s ability to create and enforce its own vaccine policies, subject to applicable local, state and federal laws. For example, employers are still permitted to require their employees to be vaccinated to enter their workplaces.

    New York City Salary Transparency in Job Advertisements Law Now in Effect

    New York City’s Salary Transparency in Job Advertisements law went into effect on Nov. 1, 2022. As previously discussed here and here, the new law makes it an unlawful discriminatory practice for covered employers to advertise a job posting for any position (including when seeking, among other roles, interns and consultants) located within New York City (including remote roles) without including a “good faith” minimum and maximum salary for the job.

    New York City Releases Proposed Rules for Upcoming Artificial Intelligence Employment Law

    The New York City Department of Consumer and Worker Protection has proposed rules to implement the legislation, previously passed effective as of Jan. 1, 2023, regulating the use of Automated Employment Decision Tools (“AEDT”) (discussed here).

    The proposed rules define key terms to supplement the law’s definition of AEDTs, as well as terms for the law’s mandated bias audit. The proposed rules also require that employers publish the results of their bias audit, that such posting be made “publicly available on the careers or job section of their website in a clear and conspicuous manner,” and include the date of the audit, the distribution date of the tool and the selection rates and impact ratios for all categories.

    The proposed rules further outline several ways by which employers may provide the law’s required advance notice of AEDT use. These methods must include instructions on how a candidate or an employee may request an alternative selection process or accommodation. Additionally, the proposed rules provide clarification with respect to the law’s requirement of notices regarding the type of data collected, the source of the data and the data retention policy.

    Authored by Mark E. Brossman, Ronald E. Richman, Martin L. Schmelkin, Scott A. Gold, Max Garfield, Donna K. Lazarus, Abdulrahman Alwattar, Laura R. Horowitz and Michelle M. Orge.

    If you have any questions concerning this Alert, please contact your lawyer or one of the authors.

    In depth
    Authors

    Mark E. Brossman

    Partner

    New York – 919 Third Avenue

    Ronald E. Richman

    Partner

    New York – 919 Third Avenue

    Martin L. Schmelkin

    Partner

    New York – 919 Third Avenue

    Max Garfield

    Partner

    New York – 919 Third Avenue

    Donna K. Lazarus

    Partner

    New York – 919 Third Avenue

    Abdulrahman Alwattar

    Associate

    New York – 919 Third Avenue

    Michelle M. Orge

    Associate

    New York – 919 Third Avenue

    More insights

  • SEC Proposes Service Provider Oversight Regime for Investment Advisers

    SEC Proposes Service Provider Oversight Regime for Investment Advisers

    ARTICLE / CLIENT ALERT / US POLICY

    SEC Proposes Service Provider Oversight Regime for Investment Advisers

    November 11, 2022

    Read time: 8 min

    Key takeaways
    Overview

    Highlights

    The Securities and Exchange Commission (the “SEC”) has proposed new rules that would dictate with great specificity the manner in which advisers oversee their service providers. While the proposed rule is described as covering “outsourcing” by investment advisers, in fact it would go far beyond delegation arrangements. The service providers covered by the rule as proposed would also include those who “assist” the adviser with certain services or functions, for example a valuation firm that assists the adviser in fair valuation determinations even though the fair valuation determinations are performed by the adviser. Advisers would not only be required to satisfy the specific ongoing oversight requirements prescribed by the proposed rule, they would also have to disclose in Form ADV the fact that they have “outsourced” such services and disclose the names and addresses of all of the outsourced service providers and the nature of the services provided. Failure to satisfy the specific oversight and documentation requirements dictated by the rule could be charged as fraud under the Advisers Act.

    The Proposed New Oversight, Recordkeeping and Reporting Regime

    On Oct. 26, 2022, the SEC proposed a new rule under the Investment Advisers Act of 1940 (the “Advisers Act”) that imposes due diligence, monitoring, recordkeeping and disclosure obligations on registered investment advisers that outsource certain functions to service providers. Although Proposed Rule 206(4)-11 (the “Proposed Rule”) is presented as “a means reasonably designed to prevent fraudulent, deceptive, or manipulative acts, practices, or courses of business within the meaning of section 206(4) of the Act”,[1] it will likely have a greater direct impact on advisers’ outsourced arrangements across a wide range of products, services and service providers.

    “Covered Functions” Provided by “Service Providers”

    The Proposed Rule does not use or define the term “outsourcing”. Rather, the types of relationships covered under the Proposed Rule are defined by new and vague standards. The Proposed Rule applies to any registered investment adviser that retains a “service provider”[2] to perform a “covered function,” which is defined as a function or service: (1) that is necessary for the adviser to provide its investment advisory services in compliance with the federal securities laws and (2) that, if not performed or if performed negligently, would be reasonably likely to cause a material negative impact on the adviser’s clients or on the adviser’s ability to provide investment advisory services.[3] To help identify the types of third parties that might provide covered functions, the Proposing Release includes some examples: “Adviser/Subadviser; Client Services; Cybersecurity; Investment Guideline/Restriction Compliance; Investment Risk; Portfolio Management (excluding Adviser/Subadviser); Portfolio Accounting; Pricing; Reconciliation; Regulatory Compliance; Trading Desk; Trade Communication and Allocation; and Valuation.”[4] The list is not exhaustive and it suggests that advisers should take a critical eye to how the Proposed Rule might impact many of its critical third party arrangements.

    The first part of the covered function test is aimed at “functions or services that are related to an adviser’s investment decision-making process and portfolio management.”[5] The Proposing Release encourages a broad interpretation of the first part of the test by including as examples services like portfolio accounting services, compliance services and valuation and pricing services. It adds, however, that “certain of these functions may be covered functions for one adviser but not for another adviser, depending on the facts and circumstances.”[6]

    The SEC provides as an example a valuation service provider. “For example, an adviser may use valuation service providers to assist in fair value determinations. Such services would be included under the proposed rule as covered functions, as opposed to, for example, common market data providers providing publicly available information.”[7] Although the valuation service provider is not delegated the authority to value the investments, the SEC indicates that by utilizing such a service provider to assist in fair valuations, the adviser has “outsourced” its valuation function.

    The second part of the covered function test is also unclear. What is a function that, if not performed or performed negligently, would be reasonably likely to cause a material negative impact on the adviser’s clients or on the adviser’s ability to provide investment advisory services? Will it be possible for advisers to rule out certain services under this formulation? The Proposing Release suggests that an “adviser should consider a variety of factors when determining what would be reasonably likely to have a material negative impact, such as the day-to-day operational reliance on the service provider, the existence of a robust internal backup process at the adviser, and whether the service provider is making or maintaining critical records, among other things.”[8]

    The Proposing Release includes a number of examples, some of which suggest that this part will be interpreted broadly, as well. The SEC advises that “if an adviser licenses a commonly available index and its stated investment strategy involves management against that index, failure to receive the index or an inaccurate delivery of the index could have a material negative impact on the adviser’s ability to manage that portfolio.”[9] In this case, the adviser’s relationship with the index provider would, presumably, be subject to the Proposed Rule.

    Due Diligence and Ongoing Monitoring Requirements

    Once an adviser determines that a service provider will perform a covered function, the Proposed Rule requires due diligence that directs advisers to confirm and document six aspects of the intended covered function services, including:

    • The nature and scope of the services;
    • Potential risks resulting from the service provider performing the covered function, including how to mitigate and manage such risks;
    • The service provider’s competence, capacity and resources necessary to perform the covered function;
    • The service provider’s subcontracting arrangements related to the covered function;
    • Coordination with the service provider for federal securities law compliance; and
    • The orderly termination of the provision of the covered function by the service provider.

    The Proposed Rule requires documentation of an adviser’s third-party due diligence assessment, including “any policies or procedures or other documentation showing how the adviser would mitigate and manage the risks it identifies, both at a covered function and a service provider level.”[10] The Proposed Rule also requires ongoing monitoring of the covered function services, assessments of the engaged service provider’s performance, and that an adviser retain books and records associated with the monitoring and assessment of the service provider.

    Additional Requirements for Outsourcing of Recordkeeping Functions

    The Proposed Rule also includes requirements specific to advisers that rely on third parties to make and/or keep any books and records required by the recordkeeping rule (“Recordkeeping Function”). In particular, the Proposed Rule requires advisers to conduct due diligence and monitoring for all third parties performing Recordkeeping Functions and obtain reasonable assurances that the recordkeepers will meet certain standards. In particular, the investment adviser must have reasonable assurance that the third party recordkeeper will:

    • Adopt and implement internal processes and/or systems for making and/or keeping records that meet the requirements of the recordkeeping rule applicable to the adviser in providing services to the adviser;
    • Make and/or keep records in a matter that meet all of the requirements of the recordkeeping rule applicable to the adviser;
    • For electronic records, provide access to electronic records by the adviser and the SEC; and
    • Ensure the continued availability of required books and records if the third party’s operations or relationship with the adviser cease.

    Recordkeeping Requirements

    The Proposed Rule’s recordkeeping requirements will obligate advisers “to make and keep a list or other record of covered functions that the adviser has outsourced to a service provider and the name of each service provider, along with a record of the factors, corresponding to each listed function, that led the adviser to list it as a covered function.”[11]

    Form ADV Disclosures

    The SEC also has proposed amendments to Form ADV under new Item 7.C in Part 1A and Section 7.C in Schedule D, which would require advisers to provide “census-type information” about the third parties that provide covered functions. Such information would include the names and addresses of the service providers and an indication as to the types of services provided. All of this would be categorized in the ADV as “outsourced” functions.

    Comment Period and Engagement with the SEC

    Comments on the proposal are due on the later of Dec. 27, 2022, or 30 days from the date of publication in the Federal Register. We are preparing comments on the Proposed Rule to provide information and perspective to the Commission and welcome dialogue with our clients on these issues.

    Authored by Allison Scher Bernbach, Marc E. Elovitz, Kelly Koscuiszka, and Philip J. Bezanson.

    If you have any questions concerning this Client Alert, please contact your attorney or one of the authors.

    In depth
    Authors

    Allison Scher Bernbach

    Partner

    New York – One Vanderbilt Avenue

    Marc E. Elovitz

    Partner

    New York – 919 Third Avenue

    Kelly Koscuiszka

    Partner

    New York – 919 Third Avenue

    More insights

  • Healthcare Regulatory Check-Up | October 2022

    Healthcare Regulatory Check-Up | October 2022

    ARTICLE / REPORT

    Healthcare Regulatory Check-Up | October 2022

    November 2022

    Read time: 2 min

    Overview

    This issue of McDermott’s Healthcare Regulatory Check-Up highlights significant activity between September 21 and October 20, 2022. We review several criminal and civil enforcement actions related to Anti-Kickback Statute (AKS) and beneficiary inducement issues, as well as allegations of false claims. This issue also examines a recent Office of Inspector General (OIG) advisory opinion related to a proposed patient assistance program for Medicare Part D cost-sharing obligations.

    In depth
    Tabs

    Tony Maida

    Partner

    New York – One Vanderbilt Avenue

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Monica Wallace

    Partner

    Chicago

    Caroline Reignley

    Partner

    Washington, DC

    Rosalyn R. Broad

    Partner

    Austin

    More insights
    Endnotes