Content Type: Article

  • District Court Vacates 340B Cuts, But Don’t Expect Immediate Payment Rate Restoration

    District Court Vacates 340B Cuts, But Don’t Expect Immediate Payment Rate Restoration

    ARTICLE / CLIENT ALERT

    District Court Vacates 340B Cuts, But Don’t Expect Immediate Payment Rate Restoration

    October 3, 2022

    Read time: 6 min

    Key takeaways
    Overview

    On September 28, 2022, the US District Court for the District of Columbia vacated the 2022 rule under which the US Department of Health and Human Services (HHS) reduced Medicare Part B payments on 340B drugs paid under the Outpatient Prospective Payment System (OPPS), restoring payments to the full OPPS rate. This ruling is consistent with the Supreme Court of the United States’ June 2022 decision, which held that identical predecessor rules implemented by HHS in 2018 and 2019 were contrary to law. While this decision represents another win for 340B hospitals in their long battle against reductions in 340B drug rates, hospitals subject to the 340B payment reductions should not expect to see more money any time soon—and when they do receive the amounts owed by HHS, those amounts may be less than expected.

    In depth

    Background

    We previously analyzed the 340B payment reductions and litigation in a series of articles:

    The issues began in 2018, when HHS implemented a 28.5% reduction to payments for most 340B drugs paid under OPPS, lowering the reimbursement amounts from average sales price (ASP) plus 6% to ASP minus 22.5%. (PPS-exempt cancer hospitals, PPS-exempt children’s hospitals and rural sole community hospitals that participate in the 340B Program and are paid under OPPS were not subject to the payment cuts. Critical access hospitals are not paid under OPPS and therefore were not subject to the payment cuts.) The payment reduction was implemented in a “budget neutral” manner, such that the estimated dollars of the payment reduction for 340B drugs were used to increase payments on other items and services paid under OPPS. Hospitals subject to the reductions immediately sued HHS in federal district court, alleging that HHS did not have the authority to reduce 340B reimbursement rates in this manner. The district court agreed with the hospitals, but the US Court of Appeals for the District of Columbia Circuit reversed the district court. The Supreme Court then reversed the DC Circuit in June 2022 and vacated the 2018 rule. The Supreme Court remanded the case to the district court to determine any remedies following the vacatur.

    On remand, the hospitals filed motions for both prospective and retrospective relief. They asked the district court to vacate the 2022 rule to restore payments to the full OPPS rate for the balance of the year, and to order HHS to pay the hospitals the amount of the payment reductions from the prior years.

    Summary of the Decision

    The district court’s September 28, 2022, decision addresses only the hospitals’ request for prospective relief. HHS had argued that hospitals’ motion would require the district court to not only vacate the 2022 rule but also issue an injunction to return to the full OPPS payment rate. The district court disagreed and simply vacated the part of the 2022 rule that effectuates the 340B payment reductions. The district court reasoned that an injunction was unnecessary because vacating the rule automatically returned the payment rate for 340B drugs to the rate applicable to all other (non-340B) hospitals. The district court also rejected HHS’s argument that vacating the rule for the remainder of 2022 would violate budget neutrality requirements, reasoning that any remedy would necessarily implicate budget neutrality principles, and the budgetary impact of a vacatur effective September 28 would not be significant.

    Immediate Effect of the Decision

    The district court’s decision vacates the 340B payment cuts for the remainder of 2022 and does so without requiring budget neutrality (i.e., a corresponding decrease in payments to other items and services paid under OPPS). But 340B hospitals should not expect to see an immediate restoration of 340B claims payment to the full OPPS amount because HHS must reprogram its payment systems, which will take some time. It could be weeks or months before the payments are restored. Further, although the district court’s order does not require budget neutrality, HHS could attempt to maintain budget neutrality by implementing a downward adjustment on payments to all hospitals for other items and services for the remainder of 2022. The result of such a downward reduction would be a payment reduction for non-340B hospitals and possibly a net reduction in reimbursement for 340B hospitals the remainder of 2022. HHS may also appeal the district court’s order, which could delay any restoration of the payment rates while the matter is pending before the appeals court.

    Issues the Decision Does Not Address

    The district court did not address the issue of remedies for payment reductions made from January 1, 2018, to September 28, 2022, and stated that it would address that issue in a future order. While the district court was unsympathetic to HHS’s budget concerns as to the remainder of 2022, it acknowledged that the amount of money at issue for the remaining months of 2022 is much smaller than the amount involved from 2018 through 2022. In fact, based on the 2023 OPPS proposed rule, the amount at issue from 2018 through 2022 could be more than $10 billion. Given those considerations, 340B hospitals should not assume that the district court will order HHS to make retrospective payments for the period of 2018 through 2022. Nor should 340B hospitals assume that any such retrospective remedy order from the district court will extend to 340B hospitals that are not members of the American Hospital Association or otherwise named plaintiffs in the case. HHS has argued that any relief ordered by the court in this case (as opposed to retrospective relief developed and implemented by HHS through notice and comment rulemaking) should be limited to named plaintiffs.

    340B hospitals should also proceed with caution when applying claim modifiers to identify 340B drugs. The district court’s decision to vacate part of the 2022 OPPS rule relates only to the 2022 payment rule and is silent regarding the requirements to apply modifiers to claims for 340B drugs. In the 2023 OPPS proposed rule, HHS proposed to discontinue the 340B payment cuts but retain the modifier requirement, indicating that HHS views the payment portion of the rule and the modifier requirements to be separate and distinct requirements.

    STAY CURRENT ON THE 340B LITIGATION THAT MAY IMPACT YOUR BUSINESS

    McDermott+Consulting has launched a 340B Litigation Tracking Tool, a real-time resource following the 40+ state and federal 340B program legal challenges. No more searching online or sorting through your newsfeed for important case developments. This tracker, available 24/7 and regularly monitored by our team, delivers concise updates to help you make informed risk analyses on what’s next for your business in the evolving 340B landscape. Learn more here. 

    Authors

    Emily Jane Cook

    Partner

    Los Angeles, Washington, DC

    Cathy Ren

    Partner

    Los Angeles

    More insights

  • Colorado Attorney General’s Office Issues Draft Colorado Privacy Act Regulations

    Colorado Attorney General’s Office Issues Draft Colorado Privacy Act Regulations

    ARTICLE / CLIENT ALERT

    Colorado Attorney General’s Office Issues Draft Colorado Privacy Act Regulations

    October 3, 2022

    Read time: 8 min

    Key takeaways
    Overview

    On September 30, 2022, the Colorado Attorney General’s Office (the AG’s Office) released draft regulations to the Colorado Privacy Act (the CPA). Before these proposed regulations take effect, however, there will be a lengthy public comment period, which will run from October 10, 2022, through February 1, 2023. On February 1, 2023, the AG’s Office will hold a public hearing on the proposed regulations and then take the public comments under advisement. In short, we are still several months away from having finalized regulations under the CPA, which goes into effect on July 1, 2023.

    The good news for businesses is that the draft regulations (1) are mostly consistent with the proposed California Consumer Privacy Act (the CCPA) regulations and (2) do not contain too many new obligations beyond the plain language of the CPA itself. This will hopefully ease the compliance burden for companies that are plotting out a multistate approach.

    In depth

    KEY DIFFERENCES FROM THE CCPA DRAFT REGULATIONS

    Many of the differences between the CCPA regulations and the proposed CPA regulations are technical in nature. However, what most businesses are likely to focus on is what are the new or different things that the CPA regulations would require above and beyond what companies are already preparing for in their CCPA privacy notices. Discussed in more detail below, some of the key differences include:

    • The CPA regulations require the disclosure of the new consumer right to appeal a data subject request decision of a company, a right not found in the CCPA.
    • There is significantly more detail regarding how companies will be expected to acknowledge and honor opt-out signal technology (as of 2024) as compared to the proposed CCPA regulations.
    • Colorado also appears to have taken a more practical approach to loyalty programs than the CCPA. For example, there is an express recognition in the CPA regulations that if a consumer’s privacy preferences make the delivery of a loyalty program benefit impossible, then companies are under no obligation to provide the benefit.
    • The CPA regulations dedicate significant space and detail to the requirements for obtaining consent from a Colorado resident.

    NOTABLE REQUIREMENTS IN THE CPA PROPOSED REGULATIONS

    • Instructions on Appeals Process: Rule 6.03 would require companies to provide in their privacy notice instructions to consumers on how they may appeal a company’s decision in response to a data rights request. The existence of the consumer appeal right is one of the key differences between California and the laws of Colorado, Connecticut and Virginia.
    • Authenticating Data Rights Requests: Rule 4.08 would require companies to establish “reasonable methods” to authenticate a consumer submitting a data rights request. To determine if a method is reasonable, companies must consider the right exercised, the type, sensitivity, value and volume of personal data involved, and the level of harm that improper access or use could cause the consumer. Practically speaking, these proposed regulations allow businesses to make the CCPA’s authentication requirements the floor rather than inventing a new, or worse, conflicting, process whole cloth.
    • System for Recognizing Universal Opt-Out Mechanisms: The proposed CPA regulations provide significantly more guidance and direction to companies about honoring universal opt-out mechanisms than the draft CCPA regulations. The CPA regulations provide, for example, that the Colorado Department of Law will maintain a public list of mechanisms that have been recognized by the AG’s Office as meeting the required standards for opt-out signal technology. The proposed CPA regulations also provide far greater detail than the CCPA regulations with respect to the deployment and effect of the signals. While there is room to improve still on these proposed rules, they are more detailed and pose less compliance burden than the proposed CCPA regulations.
    • Identification of Rights: The proposed regulations largely mirror the CCPA regulations in terms of the requirements for the delivery and content of privacy notices. However, there are some specifics in the CPA-proposed regulations that will require companies’ attention. For example, a privacy policy must “clearly indicate[]” which data subject rights are available to Colorado residents. The proposed regulations also require that a company’s privacy policy use the word “privacy” in the static link available on web pages. This will require a move away from the “Legal Notices” or “Terms” links that some companies use.
    • Biometrics Definitions: Rule 2.02 would introduce new defined terms and definitions, including “Biometric Data” and “Biometric Identifiers.” What is noteworthy about the definition of “Biometric Identifiers” is that it applies not just to commonly conceived concepts of biometrics but also to “behavioral characteristics.” It is unclear what “behavioral characteristics” ultimately would comprise “Biometric Data” (i.e., a biometric identifier used for identification purposes), but it introduces a new concept of biometrics that is less than clear.
    • Introduction of Duty Regarding Sensitive Data: The CPA-proposed regulations would codify something that many privacy professionals had been anticipating: Sensitive data inferences would be treated the same way as the sensitive data itself. The classic example is that if someone tells a company that they keep a certain religious diet, the company can infer from that information a sensitive data category (e.g., religious beliefs). Rule 6.10 would provide duties regarding a company’s processing of this type of inference data. In addition to obtaining consent to process these inferences, there are limits on the period of time in which they can be stored by a company.
    • Disclosures for a Request for Consent: The proposed regulations, beginning in Rule 7.03, set forth a robust set of rules around both the method and content for obtaining consumer consent under the CPA. Some of these requirements are proscriptive, such as the requirements that consents must be combined with other consents and must contain certain disclosures. Any company that has to obtain consent under the CPA should pay close attention to these proposed regulations.
    • Refreshing Consent: Rule 7.08 would introduce a new requirement of “refreshing consent.” Under the proposed regulation, a company must refresh consent “at regular intervals.” The draft regulations do not provide much clarity on how often consent should be “refreshed,” simply stating that it should be based on the context and scope of the original consent, sensitivity of the personal data collected and the consumer’s reasonable expectations. Rule 7.03 does require that consent must be “refreshed” annually for sensitive data.
    • Data Protection Assessments: Rule 8.04 describes what would become of the content requirements for data protection assessments. The draft rule provides a lengthy list of 18 elements to be addressed in each assessment, including, for example, the specific purpose of the processing, procedural safeguards and the dates the assessment was reviewed and approved. In addition, the new regulations would require that these assessments be revisited and updated on at least an annual basis.
    • Profiling: The draft regulations give particular focus to profiling. The rules distinguish between profiling based on: (i) solely automated processing; (ii) human reviewed automated processing; and (iii) human involved automated processing. Controllers that engage in profiling must provide additional disclosures in their privacy notice about this type of activity including, but not limited to:
      • What decision is subject to profiling;
      • The categories of personal data that were or will be processed as part of the profiling in “Furtherance of Decisions that Produce Legal or Other Similarly Significant Effects”;
      • A plain language explanation of the logic used in the profiling process; and
      • Why profiling is relevant to the ultimate decision.
    • Bona Fide Loyalty Programs: Rule 6.05 would clarify how data right requests impact loyalty programs and the disclosures that are required for those programs. If a consumer exercises their right to delete, and such a deletion would make it impossible for the company to provide program benefits to the consumer, the company would not be obligated to provide the benefit to the consumer. Similarly, if a consumer refuses to consent to the processing of sensitive data necessary for a personalized program benefit, the company would not have to provide that personalized benefit, though it must provide, if available, a non-personalized benefit. Rule 6.05E also requires controllers to disclose certain information with respect to the loyalty program in their privacy notice. These disclosures include the value of the loyalty program benefits.

    The above highlights scratch the surface of the proposed regulations. The good news is that these are draft regulations, and the AG’s Office has invited public comment on not only the proposed regulations themselves but nearly five pages worth of specific questions regarding the scope and language of the proposed regulations, signaling a demonstrated interest by the AG’s Office to invite and consider public comment.

    Although the proposed Colorado regulations will not take effect until July 2023, many companies are working now to update their existing programs for CCPA compliance and may want to consider incorporating some of the key Colorado components as they do.

    McDermott’s Global Privacy & Cybersecurity team can help you integrate the Colorado requirements into your program, notices and processes. We can also help businesses submit comments to the new proposed regulations. For assistance, please contact your regular McDermott Will & Emery lawyer.

    Authors

    Elliot R. Golding

    Partner

    Washington, DC

    Amy C. Pimentel

    Partner

    Boston

    David P. Saunders

    Partner

    Chicago

    More insights

  • FDA Issues Long-Awaited Final Clinical Decision Support Software Guidance

    FDA Issues Long-Awaited Final Clinical Decision Support Software Guidance

    ARTICLE / CLIENT ALERT

    FDA Issues Long-Awaited Final Clinical Decision Support Software Guidance

    September 30, 2022

    Read time: 12 min

    Key takeaways
    Overview

    On September 28, 2022, the US Food and Drug Administration (FDA) issued its final Clinical Decision Support Software Guidance three years after the issuance of its 2019 revised draft guidance. The final guidance refines and clarifies several key concepts for determining whether clinical decision support (CDS) software is a medical device. It also includes updated examples of device CDS and non-device CDS based on FDA’s review of proposed software solutions over the past three years. The final guidance signals that a greater number of CDS products, and many products that were previously classified as non-device CDS, will be subject to FDA’s regulatory oversight. FDA has stated that it will continue to update and revise its digital health guidance documents as it learns and evolves its regulatory approach. For industry, this may offer more opportunities to engage with FDA and inform the agency’s thinking on CDS and digital health regulation.

    In depth

    On September 28, 2022, the US Food and Drug Administration (FDA) issued its final Clinical Decision Support Software Guidance three years after the issuance of its 2019 revised draft guidance. The final guidance refines and clarifies several key concepts for determining whether clinical decision support (CDS) software is a medical device. It also includes updated examples of device CDS and non-device CDS based on FDA’s review of proposed software solutions over the past three years.

    The 21st Century Cures Act amended the Federal Food, Drug, and Cosmetic Act (FDCA) by exempting five categories of software [1], including CDS, from the definition of medical device in section 201(h). While the software exemptions provided clarity and freedom from FDA regulation for certain segments of the digital health industry, such as electronic health record vendors, the CDS provisions in section 520(o)(1)(E) introduced regulatory concepts that created interpretative challenges. Section 520(o)(1)(E) states:

    The term device, as defined in section 201(h), shall not include a software function . . .

    (E) unless the function is intended to acquire, process, or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system, for the purpose of—
    (i) displaying, analyzing, or printing medical information about a patient or other medical information (such as peer-reviewed clinical studies and clinical practice guidelines);
    (ii) supporting or providing recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition; and
    (iii) enabling such health care professional to independently review the basis for such recommendations that such software presents so that it is not the intent that such health care professional rely primarily on any of such recommendations to make a clinical diagnosis or treatment decision regarding an individual patient.

    Many of the differences in interpretation seemed to focus on the concepts of “signal” acquisition and processing and the healthcare provider’s reliance on the software output.

    FDA attempted to clarify section 520(o)(1)(E) in its 2019 draft guidance by describing a four-factor test for non-device CDS. However, many developers struggled to reconcile the four-factor test with the agency’s traditional risk-based approach for evaluating medical devices and the other software guidance documents with overlapping and sometimes contradictory interpretations of CDS functions that might exist in mobile applications or clinical software. The large volume of CDS tools on market that have similar intended uses but different regulatory classifications illustrate not only the complexity of the regulatory framework, but also that the statutory provisions and guidance are susceptible to significant differences in interpretation and application.

    In the final guidance, FDA seeks to clarify and explain the criteria for device versus non-device CDS by elaborating on important elements of its original four-factor test described below.

    • Criterion 1: not intended to acquire, process or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system
    • Criterion 2: intended for the purpose of displaying, analyzing or printing medical information about a patient or other medical information (such as peer-reviewed clinical studies and clinical practice guidelines)
    • Criterion 3: intended for the purpose of supporting or providing recommendations to a healthcare professional about prevention, diagnosis or treatment of a disease or condition
    • Criterion 4: intended for the purpose of enabling such healthcare professional to independently review the basis for such recommendations that such software presents so that it is not the intent that such healthcare professional rely primarily on any of such recommendations to make a clinical diagnosis or treatment decision regarding an individual patient.

    Notable takeaways from the guidance include the following:

    Criterion 1

    • Medical images – The term “medical images” may include images that were not originally acquired for a medical purpose. This suggests that images acquired or created on a mobile phone (e.g., a personal photo of a spot or lesion taken on a smartphone) can be considered a “medical image” if the software processes or analyzes that image for a “medical purpose.”
    • Patterns and signals – The guidance clarifies that a pattern refers to “multiple, sequential, or repeated measurements” from a signal or signal acquisition system. Further software functions that “interpret the clinical implications or clinical relevance” of medical images, signals or patterns do not satisfy criteria 1 for non-device CDS. However, “activity monitors” or other software that measure physiological parameters for non-medical or non-device purposes are exempt (e.g., retinal image analysis for security purposes).

    Criterion 2

    • Medical information about a patient and other medical information – FDA defines patient information as “the type of information that normally is, and generally can be, communicated between HCPs [healthcare professionals] in a clinical conversation or between HCPs and patients in the context of a clinical decision . . . .” The agency also states that to satisfy criterion 2, the relevance of the information for clinical decision making must be “well understood and accepted.” Other medical information encompasses peer-review clinical studies, clinical guidelines and other information that is verified and validated for accuracy. Collectively these concepts suggest that the CDS output must be the type of information that is routinely discussed with patients, readily understood by both the patient and the HCP, and based on reliable, known or validated sources.
    • Sample frequency – FDA introduces the concept of sample frequency as a key distinction between signals and patterns under criterion 1 and medical information under criterion 2. The guidance states that a single measurement (e.g., blood glucose lab test result) about a patient is “medical information” that an HCP might communicate to a patient in a clinical conversation. This would be “medical information” that satisfies criterion 2. However, software that analyzes continuous glucose monitor readings would constitute signal or pattern analysis and would not be exempt under criterion 1. While FDA acknowledges there is a continuum, the latter is more likely to fail criterion 1 because it is acquiring, processing or analyzing a medical image or signal.

    Criterion 3

    • Recommendations to enhance, inform or influence – FDA states that to satisfy criterion 3, the software must not be designed or deployed in a way that “replaces” or “directs” the HCP’s judgment. The terms “enhance” and “influence” appear to be new and perhaps are intended to emphasize the fact that non-device CDS is intended to supplement the HCP’s own knowledge and judgment.
    • Level of software automation – The guidance describes automation bias as the “propensity of humans to over-rely on a suggestion from an automated system.” Automation bias can take the form of errors of commission (following incorrect advice) or omission (failing to act because there is no prompt to do so). The guidance suggests a direct correlation between the level of automation in the software and the increased risk of automation bias. FDA states that the risk of automation bias increases when software provides or has a single, specific, selected recommendation or output rather than a list of options or complete information to consider.
    • Disease risk scores and disease risk probability outputs – Related to the issue of software automation is FDA’s concern that risk scores increase automation bias and tend to be more diagnostic and directive than lists that present a range of options. FDA expressly states that software that provides a risk probability or risk score for a specific disease or condition—or that is used to predict or detect symptoms or clinical outcomes associated with certain diseases or conditions (see examples 24 and 25 in the guidance)—or software meant to identify patients who “may exhibit signs” of a disease or condition does not satisfy criterion 3. Similarly, in situations that require urgent action, there may be insufficient time for the user to adequately consider other information. FDA’s examples in the guidance underscore the agency’s view that, to satisfy criterion 3, the output should be in the form of lists or prioritized lists of preventive, diagnostic or treatment options (e.g., FDA-cleared or approved therapies) or lists of possible next steps (e.g., additional diagnostic screenings) for the HCP to consider.
    • Time-critical outputs – FDA states that a critical factor in determining the device status of CDS is whether the outputs of the software “require urgent action” or “direct” the HCP to take a specific action.” FDA is concerned that software outputs such as alarms or alerts that require or direct the HCP to act in critical situations increase the risk of so-called “automation bias.”

    Criterion 4

    • Labeling – FDA states that labeling and disclosures about and within the software outputs are critical to demonstrating that HCPs are not meant to rely primarily on the output of the CDS to make or inform clinical decisions. FDA seems to suggest that appropriate disclosure of the basis for the CDS output and recommendations is important for HCPs to make their own judgments. Software should clearly describe the intended use of the product, including the intended HCP and patient populations.
    • Disclosures (including limitations) – Regardless of software’s complexity or whether it is proprietary, FDA states that the tool should disclose the following:

    1. The input medical information (including how obtained, relevance, how data compares to relevant subsets of subjects, and data quality requirements)

    2. A plain language description of underlying algorithm development and validation, including the following:

    • A summary of the logic or methods
    • Data (to allow the HCP to assess whether the data is representative of their patient population and if best practices were followed)
    • A description of results from clinical studies conducted to validate the software (e.g., full reports of studies identified, summaries of the strength of studies, studies most closely matching patient-specific diagnosis or demographics, and key elements of the diagnosis or demographics searched for in the medical record noted)

    3. Relevant patient-specific information, limitations or other information that may be relevant, such as missing, corrupted or unexpected input data values or significant variability.

    FDA’s example 33 in the guidance (a software function that analyzes patient-specific medical information to provide a list of follow-up options for the HCP to consider) does not satisfy criterion 4 primarily because “input medical information is not adequately disclosed . . . from the patient’s medical record or . . . the radiologist report” and because “specific details on the independence of the development and validation datasets, such as the distribution of cases from different sites, breast density, ethnicity, or other important factors, are not available,” and therefore “the HCP will not be able to assess if the results are generalizable.”

    Patient CDS – FDA appears to have removed the concept that all CDS intended for patient and caregiver use are automatically considered device CDS. The term “patient CDS” first appeared in the draft guidance, but the Cures Act CDS provision only refers to HCPs and does not specifically address patients or caregivers. FDA signals that certain patient or caregiver CDS may be regulated as medical devices based on their functions, and it clarifies that manufactures and developers should review FDA’s other digital health and software policies to assess whether patient or caregiver CDS might be regulated as medical devices.

    The final guidance signals that a greater number of CDS products, including many products that were previously classified as non-device CDS, will be subject to FDA’s regulatory oversight. The emphasis on automation bias and disclosures reflects the agency’s learning, surveillance and evaluation of hundreds of CDS tools since it released the draft guidance. The removal of the automatic device CDS designation for patient or caregiver CDS is more consistent with the plain language of the Cures Act and FDA’s risk-based approach to device evaluation.

    For some, the final guidance may resolve lingering questions of interpretation and may contribute to more efficient decision-making regarding design, development and commercialization strategies. For others, the guidance may introduce practical challenges and new complexities. The guidance may present a particular challenge for developers and manufacturers that must now revisit prior determinations regarding the device status of their CDS tools. This is particularly true for CDS that predict risk or triage or rank order patients for additional potential diagnosis or treatment, for products used in time-sensitive diagnosis or treatment, and for developers of complex software algorithms.

    Manufacturers and developers may also wrestle with how to disclose the aspects of the underlying algorithm architecture and validation that FDA deems critical for HCP independence and safety without disclosing proprietary or commercially sensitive information. FDA has stated that it will continue to update and revise its digital health guidance documents as it learns and evolves its regulatory approach. For industry, this may offer more opportunities to engage with FDA and inform the agency’s thinking on CDS and digital health regulation.

    ——————————
    [1] (1) For administrative support of a healthcare facility; (2) for maintaining or encouraging a healthy lifestyle; (3) to serve as electronic patient records; (4) for transferring, storing, converting formats or displaying data; or (5) providing certain types of clinical decision support to a healthcare provider unless interpreting or analyzing a clinical test or other device data.

    Authors
    More insights

  • What’s the Pay Range? Practical Considerations for Employers in the Advent of California’s Pay Transparency Law

    What’s the Pay Range? Practical Considerations for Employers in the Advent of California’s Pay Transparency Law

    ARTICLE / CLIENT ALERT

    What’s the Pay Range? Practical Considerations for Employers in the Advent of California’s Pay Transparency Law

    September 30, 2022

    Read time: 7 min

    Key takeaways
    Overview

    Effective January 1, 2023, California employers must comply with the requirements of Senate Bill 1162 ( SB 1162)—California’s pay transparency law signed by Governor Gavin Newsom on Tuesday, September 27, 2022. Among other things, SB 1162 amends Labor Code Section 432.3 to require employers with 15 or more employees to include pay scales in job postings; the law also requires employers to provide current employees with the pay range for their job upon request. Furthermore, the law imposes a records retention requirement for job titles and wage rate histories, and it includes penalties for noncompliance. This On the Subject outlines the details of the new law and explores strategic considerations for employers as they prepare for compliance with SB 1162’s pay transparency requirements.

    In depth

    THE LAW

    Under California’s current law, Labor Code Section 432.3 requires employers to provide candidates for employment with the pay scale applicable to the position they are applying for only upon reasonable request, meaning only after an initial interview has been completed. Employers are prohibited from asking about the candidate’s historical pay data or relying on such information for purposes of determining whether to make an offer of employment or what the offered salary should be.

    Effective January 1, 2023, SB 1162 expands California employer pay transparency requirements in the following ways:

    • Pay scales in job postings: Employers with 15 or more employees must provide the pay scale in any job posting. If the employer utilizes a third-party vendor to upload job postings, the employer must convey pay scale information to that vendor and the vendor shall include the pay scale in its posting. “Pay scale” refers to the salary or hourly wage range that the employer “reasonably expects” to pay for the position.
    • Pay scale for current employees: Employers of any size must also provide current employees with the pay scale for the employee’s current position at that employee’s request.
    • Retention of records: Employers must retain records of job titles and wage rate history for employees during the course of their employment and for at least three years after that employee’s separation from employment. The California Labor Commissioner is given authority to inspect these records.

    PENALTIES FOR VIOLATING SB 1162

    SB 1162 provides for an individual cause of action brought within one year after a person who claims to be aggrieved by a violation of the law learns of a violation, with remedies including injunctive relief and any other relief a court deems appropriate. The Labor Commissioner may also issue civil penalties for noncompliance with either the pay scale disclosure or record retention requirements ranging from $100 to $10,000 “per violation.” The actual citation amount will depend on several factors, including whether the employer has previously violated the law.

    With respect to the pay disclosure requirement, the law provides for a “safe harbor” for first-time violations where the employer can demonstrate that all job postings for open positions have been updated to include the pay scale as required. However, failure to comply with the records retention requirement creates a rebuttable presumption in favor of any employee bringing a claim under the law.

    BIG PICTURE: THE TREND TOWARD GREATER PAY TRANSPARENCY

    With SB 1162, California joins the burgeoning trend as just the latest jurisdiction to require more pay transparency in job postings and to employees. In a departure from tradition, California is not the first in this space; several laws have already been enacted across the country in the last three years that require varying levels of pay range disclosures, including in the City of Ithaca, New York City, Westchester County, Jersey City, Colorado, Nevada and Washington.

    SB 1162’S UNSETTLED QUESTIONS

    As has been the case for many state and local pay transparency laws, SB 1162 leaves several open questions as to its interpretation. Until the California Department of Industrial Relations may publish additional guidance on its interpretation of the new law, the following questions remain unanswered:

    • Remote Workers: Notably, SB 1162 does not restrict its application to businesses based in California. Thus, it remains unclear whether the new law would apply to businesses that operate outside of California but that have employees, including remote employees, in California, or that post open roles that can be performed remotely including from California.
    • Pay Scale: While SB 1162 defines “pay scale” as the salary or hourly wage range that an employer “reasonably expects to pay” for a particular job position, the law does not further define “reasonably expects to pay.” It is yet to be seen how specific or precise a reported pay scale must be relative to the employer’s wage and salary records as applicable to its present workforce.
    • Violations: The new law imposes potential penalties up to $10,000 per “violation;” however, it is unclear how the state will count a “violation” and whether each noncompliant job posting constitutes a separate violation, whether the same job posting may constitute multiple “violations” if posted on multiple job boards or whether one “violation” is each instance the state notifies an employer of its group of noncompliant job postings.
    • Aggrieved Person: Although the statute generally utilizes the terms “applicant,” “applicant for employment” and “employee,” Section 432.3(d)—which establishes the private right of action for violations of this section—provides that a “person” who claims to be aggrieved may file a complaint with the Labor Commissioner or otherwise bring a civil action. Thus, the law leaves the open question of whether anyone browsing for jobs online can bring a claim over noncompliant job postings, or whether, at minimum, that person must have applied for a job to have standing to bring a claim.
    • Statute of Limitations: SB 1162 provides that an aggrieved person may file a complaint with the state within one year of learning of the violation, but it does not expressly place an upper limit on when the violation must be discovered.
    • Unionized Workforces: The National Labor Relations Act already provides for protection of discussions involving compensation as concerted activity. It remains to be seen how pay disclosure laws such as SB 1162 will interface with the National Labor Relations Board’s current direction and goals.

    PREPARING FOR COMPLIANCE UNDER SB 1162

    California is just one of many states and municipalities joining the recent trend toward pay transparency laws nationally. Accordingly, employers with operations (or with the potential for remote workers) in California may consider the following:

    • Review all current job descriptions, job postings, promotion prospects and prospective transfers to determine the pay range to be reasonably set for an applicant or employee in those scenarios. Consider the pay range for those currently in such roles as part of this process.
    • Conduct a privileged pay equity audit with counsel and implement any appropriate adjustments in advance of the January 1, 2023, effective date.
    • Review applicable collective bargaining agreements or proposals in the process of negotiations.

    Please reach out to your McDermott lawyer if you have any questions.

    Note: SB 1162 also updated California’s current pay data reporting law, Section 12999 of the Government Code, to require that employers that have retained 100 or more workers through labor contractors to report median and mean hourly pay rates by job category and “each combination of race, ethnicity, and sex” for that group of workers. This requirement goes into effect May 10, 2023, and is not the subject of this alert.

    Authors
    More insights

  • French Foreign Investment: Guidelines Published by the Ministry of Economy

    French Foreign Investment: Guidelines Published by the Ministry of Economy

    ARTICLE / CLIENT ALERT

    French Foreign Investment: Guidelines Published by the Ministry of Economy

    September 27, 2022

    Read time: 6 min

    Key takeaways
    Overview

    On 9 September 2022, the Foreign Direct Investment Office of the Ministry of Economy (the FDI Office) issued guidelines on foreign investment control.

    In depth

    Among the clarifications provided by those guidelines, the most important are:

    Regarding the investor:

    • A recall of the now well-known rule that it is sufficient that only one entity in the investor’s chain of control is a foreign one for the transaction to fall within the scope of control;
    • Any person who is not French or, even if French, is domiciled abroad for tax purposes (with the exception of tax residents in Monaco), as well as any entity established abroad (including in Monaco) is a foreign investor;
    • When several foreign investors jointly establish a French investment vehicle without any of them having control of this vehicle, this vehicle is not regarded as a foreign investor. This hypothesis remains delicate to address since the FDI Office may rely alternatively on Article 430-1-III of the French Commercial Code on merger control, which provides that it is sufficient to demonstrate the existence of a “decisive influence” on the composition, organs or decisions of an undertaking, even by a non-member, to establish the existence of control
    • In the presence of investment funds, it is not necessary to specify the identity of all investors, but only of their manager or the persons exercising control over the funds.

    Regarding the concepts of joint control and concerted action:

    • Joint control is assessed within the meaning of Article L. 233-3-III of the Commercial Code. It therefore presupposes the existence of a concerted action – assessed independently of Article L. 233-10 – whose purpose is to implement a common policy with regard to the controlled company by means of a legally binding agreement (articles of association, pact, etc.) that enables the concerted parties to determine together, in fact, the company’s decisions. Joint control is assessed using a range of indicators including veto rights on strategic decisions, on the appointment or dismissal of managers, on the conclusion of an investment or a contract, on the approval of the budget or business plan granted to each of the concert parties
    • The shift from joint or concerted control to sole control of the foreign investor, and vice versa, does not require a new authorisation from the FDI Office; and
    • The crossing of the threshold of 25% of the voting rights of the target entity, which alone constitutes an investment, may be characterized by the crossing of the threshold in concert within the meaning of Article L. 233-10 of the Commercial Code between several shareholders with respect to a given company. Two investors are considered to be acting in concert when they have entered into an agreement with a view to acquiring, disposing of or exercising voting rights, to implementing a common policy with respect to the company or to obtaining control of that company. The presumptions of concert under Article L. 233-10 may be applied; and
    • For listed companies, the crossing of the 25% voting rights threshold by a foreign investor already authorised to acquire 10% of the voting rights does not require the granting of a new authorisation (provided that there is no change in circumstances that would prevent this exemption).

    Regarding the concept of “branch of activity”:

    • The FDI Office defined it as “a whole capable of functioning by its own means under normal conditions”; the assignment of a part of a branch of activity is therefore likely to be considered as the assignment of a single element of this whole, such as a portfolio of sensitive contracts, a contract, a licence or any equipment essential for the performance of a sensitive activity.

    Regarding the notion of sensitive activity:

    • The FDI Office has a broad approach regarding R&D activities, the sensitivity of which is assessed in the light of all the theoretical potential fields of application, and not just the applications considered by the company. This position should lead to a more systematic submission of applications to the FDI Office;
    • The absence of a materiality threshold for triggering the control: the turnover of the target company or the amount of the transaction is not in itself a criteria for determining the criticality of a company’s activity, but may be taken into account; and
    • The identity of clients plays a decisive role in the conduct of the review. The presence of sensitive customers may lead to a company falling within the scope of the review even though the activity is not in itself particularly critical.

    Regarding the application procedure:

    • It is not recommended to submit a joint application for authorisation in cases involving two foreign investors, who are independent of one another;
    • Business secrecy does not apply to requests for information from the FDI Office in the context of the review, which may go beyond the list of information set out in the law. The FDI Office may also request information directly from the target company that will not be disclosed to the investor. In practice, it is also possible for the target company to communicate separately to the Bureau the most sensitive information (list of clients, details of technologies and know-how, etc.) required for the filing of the application; and
    • Contrary to the 30 working daytime limit of phase 1 which is suspended at each request for information from the Bureau, the 45-day time limit of phase 2 is a firm time limit which cannot be interrupted.

    In the event of non-compliance with the authorisation application procedure or the commitments:

    • Sanctions are not subject to a specific limitation period; and
    • When a transaction falling within the scope of control has not been subject to prior authorisation, the operation is null and void and the investor may be subject to criminal sanctions. If the investor finds out that a transaction has been carried out without authorisation, the FDI Office should be informed as soon as possible to regularise the transaction and avoid the risk of nullity.
    Authors

    Sabine Naugès

    Partner

    Paris

    More insights

  • NYC to End Private-Sector Vaccine Mandate on November 1, 2022

    NYC to End Private-Sector Vaccine Mandate on November 1, 2022

    ARTICLE / CLIENT ALERT

    NYC to End Private-Sector Vaccine Mandate on November 1, 2022

    September 22, 2022

    Read time: 3 min

    Key takeaways
    Overview

    On September 20, 2022, New York City Mayor Eric Adams announced that New York City’s COVID-19 vaccine mandate for private employers will end on November 1, 2022. The vaccine mandate for public employees will remain in effect until further notice.

    In depth

    Since December 27, 2021, New York City has required all private employers within the five boroughs to collect proof of vaccination from their employees. With just a handful of exceptions (such as remote workers, or those requiring medical or religious accommodations), unvaccinated employees have been prohibited from in-person work within the five boroughs. The vaccine mandate required employers to convince their employees to get vaccinated. For those employees who refused to be vaccinated and did not otherwise qualify for an exception, employers were often compelled to lay off employees.

    The Mayor’s September 20 announcement also included a strong encouragement for employers to implement their own policies that encourage or mandate COVID-19 vaccination, even in the absence of a government mandate, confirming that employers may still choose to require vaccination as a condition of in-person and remote employment, subject to exemptions for employees requiring medical or religious accommodations.

    NEXT STEPS

    Private employers in New York City should plan to revise their vaccination policies to remove references to the City’s mandate. Employers should also consider updating other health and safety policies in light of the approaching cold and flu season to provide additional protections in the event of another COVID-19 surge.

    Authors

    Abigail M. Kagan

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • Commerce Issues Final Rule Implementing Pause on Possible Circumvention Duties on Solar Panels

    Commerce Issues Final Rule Implementing Pause on Possible Circumvention Duties on Solar Panels

    ARTICLE / CLIENT ALERT

    Commerce Issues Final Rule Implementing Pause on Possible Circumvention Duties on Solar Panels

    September 22, 2022

    Read time: 7 min

    Key takeaways
    Overview

    The US Department of Commerce (Commerce) has finalized its proposed regulations (Final Rule) implementing Presidential Proclamation 10414.[1] In Proclamation 10414, US President Joe Biden temporarily waived the application of any antidumping (AD) or countervailing (CVD) duties on entries of silicon photovoltaic cells and modules (CSPVs) that are completed in Cambodia, Malaysia, Thailand or Vietnam and using parts and components manufactured in the People’s Republic of China (PRC) that are subject to the ongoing circumvention inquiry on CSPVs from the PRC (SA-Completed CSPVs).[2]

    In general, the Final Rule retains the structure of the proposed regulations and pauses the possible imposition of AD or CVD circumvention duties or estimated duties on CSPVs that are subject to the current circumvention proceedings.[3] However, the Final Rule introduces an important qualification: That these SA-Completed CSPVs “must be utilized in the United States” by the “Utilization Expiration Date,” which is 180 days after the end of the presidential waiver of any AD/CVD duties.[4] This qualification may be difficult to implement and adds some degree of uncertainty as to the application of this temporary waiver on the duties. The Final Rule also authorizes potentially troubling certifications to accompany SA-Completed CSPVs in the event of an affirmative preliminary or final circumvention determination. The Final Rule does not take effect until November 15, 2022.

    In depth

    TERMINATION OF WAIVER

    Commerce’s waiver of the imposition of any AD/CVD duties or cash deposits is in effect until the “Date of Termination.”[5] Consistent with Proclamation 10414, the “Date of Termination” means June 6, 2024, or the date the emergency described in Proclamation 10414 has been terminated—whichever occurs first.[6]

    Thus, consistent with Proclamation 10414, the Final Rule provides that there is some possibility that the AD/CVD waiver of duties could cease prior to June 6, 2024. Section 362.103(b)(2) of the Final Rule addresses the steps Commerce will take in the event that the emergency is terminated prior to June 6, 2024, but following an affirmative preliminary or final determination of circumvention.[7] Notably, Commerce would be able to order the suspension of liquidation and the collection of cash deposits on merchandise that entered on an alternative later date following the Date of Termination. Commerce does not provide what that alternative date might be but simply states that it would be “an appropriate date that is on or after the Date of Termination.”[8]

    This provision was added in response to requests to include a grace period in the event of an early termination.[9] While Commerce declined to add a grace period (declaring that such a request was “premature”), it did note that, in the one instance where similar presidential authority to waive duties had been exercised (duty-free importation of lumber in 1947), President Biden granted the industry six weeks to prepare for the end of duty-free importation.[10] Thus, should President Biden decide that the emergency has ceased prior to June 6, 2024, it appears likely that there would be at least some notice of such termination before the reimposition of cash deposit requirements.

    DEADLINE FOR UTILIZATION OF SA-COMPLETED CSPVs

    The Final Rule introduces a new condition that, in order to qualify for this waiver, the SA-Completed CSPVs “must be utilized in the United States by the Utilization Expiration Date,” which is 180 days following the Date of Termination.[11] That is, assuming the waiver terminates on June 6, 2024, the SA-Completed CSPVs must be utilized by December 3, 2024. The Final Rule provides that “utilization and utilized” means the SA-Completed CSPVs will be used or installed in the United States.[12] The Final Rule further provides that “[m]erchandise which remains in inventory or a warehouse in the United States, is resold to another party, is subsequently exported, or is destroyed after importation is not considered utilized.”[13]

    Commerce explained that it introduced the utilization condition in response to concerns about “stockpiling” CSPV imports. Specifically, Commerce stated: “It is not Commerce’s goal to have merchandise that enters before the Date of Termination be used in projects long into the future, as the emergency declared by the President exists at this very moment.”[14] This new condition only applies to CSPV entries after November 15, 2022 (the effective date of the Final Rule). Thus, entries prior to that date will not be subject to this condition.

    It is not entirely clear how Commerce will implement this utilization condition. Presumably, Commerce will require some type of certification as to when or how a company expects to utilize the CSPVs. The fact that this provision does not go into effect until November 15, 2022, and will only be necessary should Commerce issue a preliminary affirmative circumvention determination (Commerce’s preliminary circumvention determinations are not currently due until November 28, 2022) may provide Commerce time to implement a certification requirement. However, any certification will be with respect to activities that happen after the CSPVs have been entered into the United States, which will be difficult to implement—that is, it is not clear how, or whether, Commerce or the US Customs and Border Protection (CBP) would try to verify that such utilization will or did occur by the Utilization Expiration Date.

    CERTIFICATION REQUIREMENT

    The Final Rule also provides Commerce the authority to require certifications to accompany SA-Completed CSPVs. Specifically, 19 C.F.R. § 362.104 provides that “[n]othing in this section shall preclude the Secretary from requiring certifications . . . in the event of an affirmative preliminary or final determination in the Solar Circumvention inquiries.” While Commerce’s Final Rule explains that it will continue to use the certification requirements in place as an enforcement tool to monitor imports of CSPVs that are “either Chinese or Taiwanese in origin and covered by the current AD/CVD duty orders,”[15] its Final Rule could be interpreted as allowing certifications for purposes other than monitoring existing orders. The Final Rule does not provide any clarification as to why such certifications might be required for other purposes or what the consequences are for failing to provide such certifications.

    SUMMARY OF POSSIBLE LIABILITY FOR AD/CVD DUTIES

    Under the Final Rule, even if there have been affirmative circumvention determinations, no resulting AD/CVD estimated duties will be applied to SA-Completed CSPVs that have been entered into the United States or withdrawn from the warehouse for consumption before the Date of Termination and for use by the Utilization Date. Thus, assuming no change to the June 6, 2024, termination date outlined in Proclamation 10414, companies should be able to import SA-Completed CSPVs up to June 6, 2024, without the risk of paying AD/CVD duties, provided that they (1) are able to utilize those CSPVs in the United States by the December 3, 2024, utilization date and (2) are able to provide whatever certification of this utilization that Commerce and CBP may require.

    There is some risk that President Biden could decide that the emergency that formed the basis for Proclamation 10414 has ended before this June 6, 2024, date and could therefore lift the waiver of any AD/CVD circumvention duties prior to this date. Should that be the case, as noted above, the Final Rule leaves open the possibility of some grace period after an announcement of the termination of the emergency before duty liability could begin; however, they do not provide for any specific grace period.

    Authors

    Carl J. Fleming

    Partner

    Washington, DC

    More insights

  • New York Bill Would Expand Fashion, Entertainment Industry Labor Protections

    New York Bill Would Expand Fashion, Entertainment Industry Labor Protections

    ARTICLE / CLIENT ALERT

    New York Bill Would Expand Fashion, Entertainment Industry Labor Protections

    September 21, 2022

    Read time: 3 min

    Key takeaways
    Overview

    In response to growing demands to overhaul the fashion industry’s labor practices, the New York State Legislature recently considered the New York Fashion Workers Act—an amendment to the state’s labor law—that would significantly expand labor protections for those in the fashion and entertainment industry.

    The bill (SB8638/A09762) advanced out of the Senate Labor Committee, but it ultimately failed to receive a final floor vote in the final days of the latest legislative session. Below are some of the more significant amendments to the labor law the bill proposed:

    1. Management companies would have a formal fiduciary duty to any model or creative that the management company manages, procures or attempts to manage.
    2. Commissions made by model and creative management companies would be capped at 20% of a model’s or creative’s pay.
    3. Models, photographers and other creative talent would have to be paid no more than 45 days after completion of a job. In addition, funds would have to be deposited in a client trust account for safekeeping.
    4. Management companies would have to notify former talent in writing should the management company collect royalties from talent they no longer represent.
    5. Management companies would have to register with the New York State Department of Labor (the Department) and deposit a $50,000 surety bond with the Department.
    6. In the case of a dispute with a client regarding late or non-payment of services rendered, the management company would pay the talent and keep payment from the client when the dispute is resolved.

    While the bill was not signed into law during the 2022 session, it is unlikely that these proposed changes are going away entirely. Employers in the entertainment and fashion industry should be prepared for a revival of this bill next year. McDermott Will & Emery will continue to monitor these proposals and is available to advise clients who are interested in preparing for these changes.

    In depth
    Authors

    Melis Solaksubasi

    Associate

    Chicago

    More insights

  • International News: Spotlight on Competition Law

    International News: Spotlight on Competition Law

    INTERNATIONAL NEWS / REPORT

    International News: Spotlight on Competition Law

    September 2022

    Read time: 4 min

    Key takeaways
    Overview

    In line with the evolution of the economy and the ongoing growth of online business and global trade, we’re seeing a corresponding increase in competition regulation and a rise in enforcement across all authorities.

    The growth of the online economy has triggered the US Federal Trade Commission’s (FTC) update of its 20 year old .com Disclosures: How to Make Effective Disclosures in Digital Advertising guide, and the development of an analytical framework for all digital distribution across the European Union. In just one seismic shift under the new EU Vertical Block Exemption Regulation 2022/720, dual-pricing, i.e., setting different wholesale prices for online/offline sales by the same distributor, is no longer considered a hardcore restriction unless its purpose is to prevent the effective use of the internet to sell the goods or services.

    In the United States, there is an increased focus on anticompetitive mergers and acquisitions (M&A). The Biden Administration, the Department of Justice Antitrust Division, and the FTC have all stated that the regulatory landscape needs to be reshaped to better reflect dynamic markets, and their priority is the aggressive pursuit of litigation against offending parties rather than the granting of consent decrees. The tendency to “sin first and beg forgiveness later” will emphatically no longer work, as a recent French gun-jumping case demonstrates.

    Both the United States and the European Union have also turned their attention to investigating wage fixing and no-poach labour market violations that are not connected with M&A or business collaborations. It’s clear that competition/antitrust authorities are determined to expand their remit.

    Please contact the authors directly if you have any comments on our articles, or would like to discuss any of the issues raised.

    In depth
    Authors

    Gregory E. Heltzer

    Partner

    Washington, DC

    Graham J. Hyman

    Associate

    New York – One Vanderbilt Avenue

    Lisa P. Rumin

    Partner

    Washington, DC

    More insights

  • SEC Pay-to-Play Rule Update: Recent SEC Enforcement Activity and What It Means for the November Midterms

    SEC Pay-to-Play Rule Update: Recent SEC Enforcement Activity and What It Means for the November Midterms

    ARTICLE / CLIENT ALERT / US POLICY

    SEC Pay-to-Play Rule Update: Recent SEC Enforcement Activity and What It Means for the November Midterms

    September 21, 2022

    Read time: 4 min

    Key takeaways
    Overview

    On Sept. 15, 2022, the U.S. Securities and Exchange Commission (“SEC”) settled enforcement actions against four investment advisers for violating Rule 206(4)-5 under the Investment Advisers Act of 1940, as amended (the “Pay-to-Play Rule”).[1]

    The Pay-to-Play Rule. Among other things, the Pay-to-Play Rule prohibits advisers from providing investment advisory services for compensation to a government entity within two years after the adviser or one of its “covered associates” makes a contribution to an official of the government entity that is directly or indirectly responsible for, or can influence the outcome of, the hiring of an investment adviser by the government entity or has authority to appoint any person who is directly or indirectly responsible for, or can influence the outcome of, the hiring of an investment adviser by the government entity.[2] Compliance with the Pay-to-Play Rule requires a high degree of care because the technical requirements of the rule are very specific and intent is irrelevant. In light of the upcoming elections, it is particularly important for investment advisers, including exempt reporting advisers[3], to focus on compliance with the Rule.  

    The Recent Enforcement Cases. In all four cases, political contributions of $1,000 or less by personnel of investment advisers mandated a two-year “time-out” from receiving fees from the pension plans invested in funds managed by the advisers because the recipient of the contribution was an “official” of the pension plan due to the recipient’s role with respect to the pension plan. Notably, in all of the cases, the investment advisers had established advisory relationships with the pension plans prior to the contributions. None of the cases involved allegations of any intent to actually influence the allocation of pension investments – the very type of quid pro quo arrangement the Pay-to-Play Rule is designed to address. In fact, in three of the cases, the investments by the pension plans were made years before the political contributions were made and the funds were closed-end funds with no redemption rights.

    These settlements demonstrate the SEC’s continued aggressive enforcement of the Pay-to-Play Rule[4] and other prophylactic rules.[5] Moreover, violations of the Pay-to-Play Rule are easily detected by the Staff due to the increasing public availability of information about many political contributions. Coupled with the strict liability nature of the statute, political contributions by personnel of investment advisers make for “low hanging fruit.”

    What Should Investment Advisers Be Doing? This aggressive enforcement – and strict liability – make it critically important for investment advisers to maintain robust policies and procedures designed to prevent improper contributions from being made in the first place. While the Pay-to-Play Rule provides for an exception to the two-year “time out” for returned contributions, this exception is only available when the contribution has been discovered within four months of being made, is less than $350 and is returned within 60 calendar days from the date of discovery. Pre-clearance of all political contributions – irrespective of the recipient or the amount – helps to prevent improper contributions, as does periodic training. Electronic records searches can help identify contributions that may not have been cleared, as can reviews of publicly available information about contributions. Advisers also should keep in mind that contributions to candidates for federal office may be covered by the Pay-to-Play Rule if the candidate is currently a state officeholder at the time of the contribution. Additionally, contributions to PACs, political parties and other committees require heightened diligence with respect to the ultimate recipient of the funds.[6] In light of the upcoming midterms, now is a good time to remind your personnel of your policy with respect to political contributions, including, if applicable, the need to pre-clear all contributions.

    Authored by Allison Scher Bernbach, Marc E. Elovitz, Peter D. Greene, and Kelly Koscuiszka.

    If you have any questions concerning this 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

    Peter D. Greene

    Partner

    New York – 919 Third Avenue

    Kelly Koscuiszka

    Partner

    New York – 919 Third Avenue

    More insights