Content Type: Article

  • First Circuit Affirms Dismissal of Fraudulent Transfer and Fiduciary Duty Claims

    First Circuit Affirms Dismissal of Fraudulent Transfer and Fiduciary Duty Claims

    ARTICLE / CLIENT ALERT

    First Circuit Affirms Dismissal of Fraudulent Transfer and Fiduciary Duty Claims

    December 12, 2017

    Read time: 9 min

    Key takeaways
    Overview

    “[T]he largely debt-financed purchase of a family-owned [business] was not a fraudulent [transfer] and did not amount to a violation of the fiduciary duty of the company’s directors,” held the U.S. Court of Appeals for the First Circuit on Dec. 4, 2017. In re Irving Tanning Co., 2017 W.L. 5988834, *1 (1st Cir. Dec. 4, 2017). According to the court, “the bankruptcy court’s factual determinations [after a five-day trial were] not clearly erroneous,” and were supported by “sufficient facts to support its conclusions” despite a lack of specific findings relating to two debtor subsidiaries. Id.

    Relevance

    Courts have recently rejected fraudulent transfer and fiduciary duty attacks on transactions undermined by unforeseen events and the “global financial crisis” of 2009-10. Id., at *2. See, e.g., In re ATP Oil & Gas Corp., 2017 U.S. App. LEXIS 21337 (5th Cir. Oct. 27, 2017) (affirmed dismissal of trustee’s fiduciary duty and fraudulent transfer claims based on payment on stock dividends and payment of cash bonuses to officers during the two years preceding bankruptcy after a major oil spill in 2010 and moratoria on further drilling); and In re Lyondell Chem. Co., 2017 Bankr. LEXIS 1097, *6 (Bankr. S.D.N.Y. April 21, 2017) (after a lengthy trial, trustee failed to prove insolvency, actual fraud or fault to support breach of fiduciary duty claims; debtor had been “buffeted by unplanned and . . . unforeseeable events . . . and the effect of the Great Recession at the end of 2008.”).

    Facts

    The holding company debtor (“Holdco”) and its two operating subsidiaries (“Sub 1” and “Sub 2”) were part of an administratively consolidated Chapter 11 case. A private equity firm (“P”) had created Holdco after acquiring the stock of another leather manufacturer (“Irving”) in the same business as Sub 1. P believed that “consolidating [Sub 1] and Irving could lower the cost of leather production and allow the surviving entity’s products to reach new markets.” 2017 WL 5988834, at *1. Eventually, P created Holdco and transferred its “stake in Irving to it.” Id. Holdco was the sole shareholder of Sub 1, which was in turn the sole shareholder of Sub 2. Holdco had acquired Sub 1 from a family group of shareholders, who had owned it for over 100 years and who sold it to Holdco in late 2007 for cash, a note, Holdco stock, the assumption of some of Sub 1’s liabilities and the granting of employment contracts for two shareholders. Id., at *1, *6.

    The directors of Sub 1 carefully “considered the transaction” with Holdco before approving it. Id. at *2. They received “financial advice from . . . a management consulting firm; accounting advice from an outside public accountant; and legal advice from” Sub 1’s counsel. Id., at *2. Evidence showed “that the transaction would create a stronger entity long-term. Financial projections [showed] that the transaction was likely to succeed, though [Sub 1] recognized that the transaction involved risk.” Id.

    Holdco financed the transaction with a loan from its primary lender, secured by the assets of Holdco and its four subsidiaries. Holdco was “able to pay its bills” immediately after the transaction, but encountered financial problems in early 2008 when “the global financial crisis” started. Id. By 2010, Holdco was insolvent, causing it and the other debtors to file Chapter 11 petitions in late 2010. A litigation trust acquired the debtors’ claims after the bankruptcy court confirmed a Chapter 11 plan on Oct. 18, 2012.

    The Lower Courts

    The litigation trustee sued the shareholders and the directors of Sub 1. It sought to void the transactions as a fraudulent transfer and hold the directors liable for breach of their “fiduciary duties by approving” the transaction with Holdco. Id., at *3.

    The bankruptcy court, after a five-day trial with a voluminous record, ruled for the defendants “on every count.” Id. Despite the court’s failure to make “specific findings with respect to” Sub 1 and Sub 2 when finding that the sale of Sub 1 was not a fraudulent transfer and that its directors had not breached their duties, the trustee never asked for additional findings. Id.

    The trustee appealed to the district court, arguing that “the bankruptcy court’s decision was insufficiently supported by findings of fact and was clearly erroneous.” Id. Affirming, the district court disagreed, holding that any mistakes made by the bankruptcy court “were harmless and that [the trustee] had not shown any breach” of fiduciary duty. Id.

    The Court of Appeals

    The court overlooked the bankruptcy court’s lack of detailed findings because the factual findings in the record were sufficient and because the trustee failed to ask the bankruptcy court for more findings. Id., at *4. Still, the First Circuit conceded that the bankruptcy court ordinarily should have analyzed whether the “transaction was fraudulent with respect to the individual debtors,” Sub 1 and Sub 2, not just Holdco. Id., at *4. Under the Uniform Fraudulent Transfer Act (“UFTA”), which the trustee relied on here, “each entity needs to be evaluated separately.” Id. “[W]hether the transaction was fraudulent with respect to a separate entity [i.e., Holdco] does not adequately protect [the] interest” of the creditors of Sub 1 and Sub 2. Id.

    1. Holdco — No Fraudulent Transfer. According to the First Circuit, “the bankruptcy court clearly stated the evidence on which it [relied, and] it found the necessary facts,” none of which was “clearly erroneous.” Id., at *5. First, Holdco “received reasonable value”— it paid cash to shareholders, made life insurance payments and non-competition agreement payments “in exchange for [Sub 1].” Id. More important, “the value of [Sub 1] stock . . . exceeded the total transferred to the shareholders.” Id., at n. 6. Sub 1 “had $44.2 million in total equity at the time of closing, and Holdco paid $27.4 million for it,” giving the bankruptcy court “a reasonable basis for its determination,” which the First Circuit refused to “second guess.” Id., at *5.

    Nor had the trustee shown that Holdco was “undercapitalized” or that it “would be unable to pay its debts as they came due following the transaction.” Id. A lender’s credit report, available cash and assets, plus credible testimony as to the witnesses’ belief regarding Holdco’s ability to pay its bills, supported the bankruptcy court’s fact findings.

    1. Subs 1 and 2 — No Fraudulent Transfers. The trustee also failed to prove either undercapitalization or belief by those debtor subsidiaries that they would be unable to pay their debts as they became due. Id., at *6. Because Holdco “was a holding company with no business operations of its own,” nothing in the record would support the trustee’s allegations “if in fact their corporate parent/grandparent [Holdco] was not subject to either of those taints . . . . ” Id. Despite the theoretical possibility that the subsidiaries were insolvent or undercapitalized, the trustee “provided no evidence that this theoretical possibility was true.” Id. at n.9.
    2. No Actual Fraudulent Intent. The bankruptcy court “found that the defendants – who controlled [Sub 1 and Sub 2] did not act with intent to defraud.” Id., at *7. Because actual fraud had to be proved “by clear and convincing evidence,” a “largely factual [finding] based on credibility,” the First Circuit declined to review the bankruptcy court’s finding, particularly when the trustee produced “no direct evidence of actual fraud” and when the “circumstantial evidence [showed] that [Sub 1 and Sub 2] received reasonably equivalent value” in the transactions. Id. at *7, n.10. Substantial testimony and “documents in the record” showed “that the merger had the potential to create efficiencies, expand markets, lessen costs and allow the [insider] family to continue its connection with the [Sub 1] brand into another generation.” Id. at *7. Only “two [purported] badges of fraud were present: the sale was made to [Sub 1’s] insiders and the transfer involved the sale of substantially all of [Sub 1’s] assets.” Id., at n. 11. Unless Sub 1 were successful, though, both debtor subsidiaries could not create efficiencies, expand markets and allow the insider family defendants to continue their connection with the Sub 1 brand. Id.
    3. No Breach of Fiduciary Duty. In the view of the First Circuit, “the findings of fact supporting [the bankruptcy court’s] fraudulent [transfer] analysis . . . foreclose the possibility of fiduciary duty liability.” Id., at *8. The trustee alleged that the directors “breached their duty of care by failing to properly investigate the transaction and violated their duty of loyalty by self-dealing and approving prohibited distributions,” but Holdco’s “insolvency is the only specific harm alleged to have resulted from these breaches.” Id. Still, the bankruptcy court properly found that the trustee failed to prove that “the purported breach proximately caused the harm suffered.” Id. In fact, the trustee failed “to convincingly link” Holdco’s “inability to pay its bills as they came due in 2009” with the “2007 payments to the Shareholder Defendants.” Id. Testimony and “an expert report” showed that “unforeseeable increases in chemical and energy prices, along with the financial crisis, significantly contributed to [Holdco’s] insolvency,” confirmed by “board meeting minutes.” Id. Because “the transaction did not cause the insolvency of [Holdco],” the same result followed for Sub 1, because Holdco “was a holding company without any operations of its own.” Id.

    Comment

    Irving Tanning shows the advantages of a fair trial. The defendants made a strong factual record of care, diligence and thoughtful consideration by business people who were later confronted by unforeseeable events. Insolvency here did not follow from either mismanagement or self-dealing.

    Authored by Michael L. Cook.

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


     

    This information has been prepared by Schulte Roth & Zabel LLP (“SRZ”) for general informational purposes only. It does not constitute legal advice, and is presented without any representation or warranty as to its accuracy, completeness or timeliness. Transmission or receipt of this information does not create an attorney-client relationship with SRZ. Electronic mail or other communications with SRZ cannot be guaranteed to be confidential and will not (without SRZ agreement) create an attorney-client relationship with SRZ. Parties seeking advice should consult with legal counsel familiar with their particular circumstances. The contents of these materials may constitute attorney advertising under the regulations of various jurisdictions.

    In depth
    Authors
    More insights

  • FDA Menu Labeling Guidance: Latest Step on a Long Road

    ARTICLE

    FDA Menu Labeling Guidance: Latest Step on a Long Road

    December 12, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Arthur DeCelle wrote this bylined article on FDA draft guidance regarding federally mandated calorie and nutrient disclosure on chain restaurant menus and vending machines. Because the guidance “could lead to nuisance complaints from regulators” if implemented, Mr. DeCelle wrote, “a conservative approach is advisable to mandatory disclosures. All aspects of calorie and nutrient disclosure for standard menu items and vending machine offerings should be reviewed by counsel or a knowledgeable compliance professional.”

    In depth
    Authors
    More insights

  • FDA Issues Fourth and Final Software as a Medical Device Clinical Evaluation Guidance

    FDA Issues Fourth and Final Software as a Medical Device Clinical Evaluation Guidance

    ARTICLE / CLIENT ALERT

    FDA Issues Fourth and Final Software as a Medical Device Clinical Evaluation Guidance

    December 12, 2017

    Read time: 7 min

    Key takeaways
    Overview

    The FDA recently released “Software as a Medical Device (SaMD): Clinical Evaluation,” a final guidance document that aims to establish a common understanding of clinical evaluation and principles for demonstrating the safety, effectiveness and performance of Software as a Medical Device. Rather than replace or conflict with existing regulatory requirements or provide recommendations for application to specific situations, the guidance provides an evidentiary and technical framework to evaluate safety and performance of SaMDs throughout the product’s lifecycle.

    In depth

    On December 7, 2017, the US Food and Drug Administration (FDA) released a final “Software as a Medical Device (SAMD): Clinical Evaluation” guidance document (Guidance). The goal of the final Guidance is to establish a common understanding of clinical evaluation and principles for demonstrating the safety, effectiveness and performance of SaMD. As with previously issued SaMD guidance documents, the Guidance is not intended to replace or conflict with existing premarket or postmarket regulatory requirements related to the regulatory classification of medical devices, and it does not provide recommendations for application to specific regulatory situations. Rather, the Guidance provides an evidentiary and technical framework to evaluate safety and performance of SaMDs throughout the product’s lifecycle. It incorporates established quality management principles that developers should consider in the development and design of medical software. FDA intends to consider the principles set forth in the Guidance in the development of its regulatory approaches for digital health technologies through public processes. SaMD software uses an algorithm that operates on data input to produce an output intended for medical purposes, such as to treat, diagnose, drive clinical management, or inform clinical management. Mobile applications that meet this definition are considered SaMD. These products include many functions that are regulated by FDA as medical devices.

    The Guidance is intended to build on the previous three SaMD guidance documents: “Software as a Medical Device (SaMD): Key Definitions,” “Software as a Medical Device: Possible Framework for Risk Categorization and Corresponding Considerations” and “Software as a Medical Device (SaMD): Application of Quality Management System,” all issued by the International Medical Device Regulators Forum (IMDRF). The IMDRF is a voluntary group of medical device regulators from Australia, Brazil, Canada, China, Japan, Russia, Singapore, the United States and European countries. The group provides harmonized principles for individual jurisdictions to adopt based on their own regulatory framework. Collectively, the previous IMDRF SaMD guidance documents and the clinical evaluation Guidance provide a framework for defining which functions are considered SaMD, identifying and characterizing risks associated with SaMD functions, developing quality management systems (QMS) and controls for SaMDs, and validating the clinical effectiveness and safety of SaMDs.

    As we summarized in our FDA 2016 Year in Review report, FDA released a draft of the Guidance in October 2016. The final Guidance provides further detailed instruction to manufacturers but does not represent a departure from the October 2016 draft.

    SaMDs are categorized on the basis of the state of the health care situation or condition in which it is used (critical, serious or non-serious) and the intended medical purpose of the information provided by the SaMD (treat or diagnose, drive clinical management or inform clinical management). The four categories (I, II, III and IV) are based on the levels of impact the SaMD has on patient or public health. The categories are in relative significance to each other. Category IV has the highest level of impact, Category I the lowest. SaMD output used to treat or diagnose a critical health care situation or condition is the highest categorization (IV). Below is the risk categorization framework in the IMDRF SaMD “Possible Framework for Risk Categorization and Corresponding Considerations” guidance. This framework is not intended to supersede FDA’s framework for medical device classifications but, rather it is intended to provide a framework for determining what type and how much data will be required to validate the performance of the device.

    State of Health care Situation or Condition

    Significance of information provided by SaMD to the healthcare decision

    Treat or Diagnose

    Drive Clinical

    Management

    Inform Clinical

    Management

    Critical

    IV

    III

    II

    Serious

    III

    II

    I

    Non-Serious

    II

    I

    I

    The Guidance emphasizes the importance of independent review, i.e., review conducted by outside experts such as formal consultation with regulators, third parties on behalf of regulators, the editorial board of a peer-reviewed journal or “non-conflicted” internal expert reviewers without significant involvement in the development of the SaMD, particularly for SaMDs categorized as III or IV.

    The Guidance describes clinical evaluation as an ongoing lifecycle process that involves a set of activities conducted in the assessment and analysis of a SaMD’s clinical safety, effectiveness and performance as intended by the manufacturer. Monitoring real world performance data can help SaMD functionality and intended use evolve after initial introduction into the market. The reference to the use of real world data for performance validation reflects the growing importance of real world evidence (RWE) and real world data (RWD) for product development. See Use of Real-World Evidence to Support Regulatory Decision-Making for Medical Devices (Aug. 31, 2017). The Guidance focuses on three key principles for clinical evaluation:

    • Valid Clinical Association: whether there is a valid clinical association (i.e., scientific validity) between the SaMD output and its targeted clinical condition in the real world through existing evidence (e.g., literature searches, clinical research, professional society guidelines) or by generating new evidence (e.g., secondary data analysis, clinical trials). In other words, Clinical Association demonstrates the level of clinical acceptance and how much meaning and confidence can be assigned to the clinical significance of the SaMD’s output in the intended health care situation and the clinical condition or psychological state (i.e., well-established or novel).
    • Analytical Validation: whether the SaMD correctly processes input data to generate accurate, reliable and precise output data (i.e., confirms and provides objective evidence that the software was correctly constructed through display of accuracy, repeatability and reproducibility and demonstrates the software meets its specifications that conform to user needs and intended uses) through verification and validation activities as part of quality management system (QMS) or by generating new evidence (e.g., curated databases, previously collected patient data). In other words, Analytical Validation is intended to confirm whether the software was correctly constructed.
    • Clinical Validation: whether use of SaMD’s accurate, reliable and precise output data achieves its intended purpose in the target population in the context of clinical care, i.e., yields a clinically meaningful output. Clinically meaningful means a positive impact on the health of an individual or population, to be specified as meaningful, measurable, patient-relevant clinical outcome(s), including outcome(s) related to the function of the SaMD (e.g., diagnosis, treatment, prediction of risk, prediction of treatment response), or a positive impact on individual or public health. In other words, Clinical Validation shows the relationship between the verification and validation results of the SaMD algorithm and clinical conditions of interest as part of QMS or good software engineering practices or by generating new evidence (e.g., clinical data).

    If the foregoing cannot be established, the manufacturer must modify the SaMD’s intended use such that it can be supported by available evidence, modify the target clinical association and/or make changes to the software.

    On the same day that this Guidance was issued, FDA published draft guidance on clinical decision support software and made technical corrections to existing medical software policies. We describe both guidance documents in detail here. Taken together, the guidance statements clarify how developers should approach the development and classification of software-based medical device products in preparation for pre and postmarket decision-making. In the absence of specific guidance on the implementation of FDA’s Medical Device Quality System Regulation (QSR) for digital health products and software-based medical devices, this guidance and the previously issued IMDRF Guidance documents provide a useful framework for designing, testing and validating medical software.

    Authors

    Michael W. Ryan

    Partner

    Washington, DC

    More insights

  • The Pitfalls of Deploying Employees Abroad

    ARTICLE

    The Pitfalls of Deploying Employees Abroad

    December 2017

    Read time: 2 min

    Key takeaways
    Overview

    The temporary deployment of employees abroad no longer concerns only large corporations. Many mid-sized businesses have established branches and companies abroad in order to distribute their products and services there. Dr. Sandra Urban-Crell and Dr. Gudrun Germakowski go into aspects to be taken into account.

    In depth
    Authors
    More insights

  • FDA Publishes Draft Guidance on CDS Software and Revises Medical Software Policies

    FDA Publishes Draft Guidance on CDS Software and Revises Medical Software Policies

    ARTICLE / CLIENT ALERT

    FDA Publishes Draft Guidance on CDS Software and Revises Medical Software Policies

    December 11, 2017

    Read time: 10 min

    Key takeaways
    Overview

    On December 7, 2017, the US Food and Drug Administration (FDA) published a highly anticipated draft guidance document that describes how the agency intends to exercise oversight over clinical decision support (CDS) software. Simultaneously, FDA also issued a draft guidance document that describes how the agency intends to revise four previously issued digital health final guidance documents for consistency with the 21st Century Cures Act, which amended the Federal Food, Drug, and Cosmetic Act’s definition of “device” to exclude software with several types of functions (including certain CDS functionalities). The key provisions and implications of these guidance documents are briefly summarized in this On the Subject.

    In depth

    FDA has long expressed an interest in digital health products. The extent to which FDA should assert jurisdiction over digital health products, however, has been the subject of considerable debate. The debate has been particularly intense with respect to FDA’s oversight of clinical decision support (CDS) software.

    In early December 2016, Congress weighed in by enacting section 3060 as part of the 21st Century Cures Act. Section 3060 expressly excludes several types of software from the Federal Food, Drug, and Cosmetic Act’s (FDCA) definition of a “device”—excluding such products from FDA’s regulatory jurisdiction—including products that meet all four of the following criteria:

    • 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;
    • 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);
    • Intended for the purpose of supporting or providing recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition; and
    • Intended for the purpose of 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.

    Almost one year later, on December 7, 2017, FDA issued (1) a draft guidance entitled Clinical and Patient Decision Support Software (the CDS Guidance) that outlines the agency’s interpretation of the four above-referenced criteria, and (2) a draft guidance entitled Changes to Existing Medical Software Policies Resulting from Section 3060 of the 21st Century Cures Act (the Technical Changes Guidance) that outlines how the agency intends to revise four final guidance documents for consistency with the 21st Century Cures Act provision, noted above, that excludes software specific functions from the FDCA’s definition of a device.

    The CDS Draft Guidance

    The CDS Guidance outlines FDA’s position with respect to the agency’s oversight of (1) CDS software intended for health care professionals and (2) patient decision support (PDS) software intended for patients and caregivers who are not health care professionals. The CDS Guidance is intended to identify the types of decision support software functionalities that (1) do not meet the definition of a device as amended by the 21st Century Cures Act, (2) may meet the definition of a device but for which FDA intends to exercise enforcement discretion, and (3) meet the definition of a device and are the focus of FDA’s regulatory oversight.

    As an initial step, FDA provides its definition of CDS software—i.e., software with functions that meet the first three of the four above-listed criteria. FDA reiterates, however, that CDS software only falls outside the definition of a “device” if it meets the fourth of the above-referenced criteria, which requires the software to enable independent review of the basis for any recommendations (or outputs) by a health care provider.

    Next, FDA provides guidance on its interpretation of each of the four above-referenced criteria. Specifically:

    Criteria

    Guidance

    The software is 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.

    Leaving these functionalities within the definition of a device is consistent with agency policy and prior guidance—products with these functionalities have long been regulated as medical devices by FDA.

    The software is intended to display, analyze or print medical information about a patient or other medical information (such as peer-reviewed clinical studies and clinical practice guidelines).

    Includes software that displays, analyzes, and/or prints the type(s) of information that health care professionals use in patient management—i.e., demographic information, symptoms, and test results, and/or medical information (e.g., clinical practice guidelines, peer-reviewed clinical studies, textbooks, approved drug labeling and government agency recommendations).

    The software is intended to support or provide recommendations to a health care professional about the prevention, diagnosis, or treatment of a disease or condition.

    The statutory exception is limited to software that supports or provides recommendations to health care professionals; software that exclusively assists patients would not meet this criterion. That being said, FDA does not intend to enforce compliance with applicable regulatory requirements with respect to analogous devices that provide similar recommendations for patients or caregivers who are not health care professionals.

    The software enables a 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.

    • To meet this criterion, software functions will need to explain the purpose or intended use of the software function; the intended user; the inputs used to generate the recommendation; and the rationale or support for the recommendation. To the extent developers have not provided this targeted information to health care providers, this requirement may impact product advertising, promotions, and disclaimers.
    • The user should be able to reach the same recommendation on his or her own without relying primarily on the software function.
    • The sources supporting the recommendation or underlying the rationale for the recommendation should be identified and easily accessible to the intended user, understandable by the intended user and publicly available (e.g., clinical practice guidelines, published literature). This requirement is consistent with the agency’s past guidance.
    • Software that makes recommendations on the basis of non-public information or provides recommendations whose meaning could not be expected to be independently understood by the intended health care professional user would not meet this requirement.

    Based on the above, the CDS Guidance lists several examples of software that is not a device. In almost all of the examples, the agency includes the caveat that the recommendations provided by the software must be consistent with current clinical guidelines and consistent with FDA-approved drug labeling. For example, software that suggests a test based on a physician’s order is a CDS function that is not a device, provided the software’s suggestions are consistent with clinical guidelines. As another example, software that contains calculators for ordering total parenteral nutrition (TPN), such as software that recommends increased protein TPN for patients with active infections consistent with clinical practice, is not a device. Notably, software that provides health care professionals with recommendations on the use of a prescription drug that are consistent with FDA-required labeling are also not a device. However, software distributed by or on behalf of a sponsor for use with one or more of its drugs or biologics is not addressed in the CDS Guidance, and FDA noted that labeling and combination product requirements may be applicable. This statement is particularly relevant for many drug and biologics manufacturers who provide enhanced labeling, instructions for use or patient metrics through software or mobile applications. FDA appears to confirm without further explanation that certain types of software distributed with drugs or biologics may be subject to labeling and/or advertising regulations.

    The agency further indicates that it intends to focus its oversight on CDS and other software functions that remain devices, including several types of software based on computed tomography (CT) or magnetic resonance (MR) images. For example, FDA will regulate software that analyzes CT images to compute and/or approximate fractional flow reserve because the software performs an image analysis that the user could not independently derive. For similar reasons, FDA will continue to regulate software that manipulates data from a CT scan, including software that provides 3D reconstruction to aid in the placement of catheters in lung tissue and markers in lung tissue to guide radiosurgery and thoracic surgery.

    Enforcement Discretion for Certain PDS Software

    Lastly, as noted above, the CDS Guidance describes a new subcategory of decision support software called PDS software that is subject to enforcement discretion. This category encompasses several types of general health and wellness functions that allow the intended user to obtain health recommendations and other information. To fall within enforcement discretion, FDA encourages developers to identify and present the supporting basis and rationale for any software recommendations in an understandable format. As is true for labeling, developers should take note that explanations for health care providers will likely be different than those issued to patients. Similar to CDS software, enforcement discretion does not apply to all PDS software. The CDS Guidance offers examples to assist stakeholders in appropriately classifying PDS software.

    The Technical Changes Guidance to Implement the Cures Act

    In the Technical Changes Guidance, FDA details the changes it intends to make to four existing guidance documents—General Wellness: Policy for Low Risk Devices, Mobile Medical Applications, Off-the-Shelf Software Use in Medical Devices, and Medical Device Data Systems, Medical Image Storage Devices, and Medical Image Communications Devices—to conform such documents to the requirements of section 3060 of the 21st Century Cures Act. FDA also announced its intent to withdraw its Guidance for the Submission of Premarket Notifications for Medical Image Management Devices.

    The changes proposed to the above-referenced guidance documents primarily involve the movement of certain device functionalities from lists of products over which FDA intends to exercise enforcement discretion to lists of products that do not meet the definition of a device after the enactment of section 3060.

    The guidance offers insights regarding FDA’s proposed approach to certain functions that were not explicitly addressed in prior guidance. For example, FDA affirms that electronic health records (EHRs) and personal health records (PHRs) are generally excluded from the definition of medical device, but notes that certain components or functions within EHRs and PHRs may be regulated as devices. FDA plans to address multifunction software in a separate guidance.

    Implications

    With the notable exception of the proposal to exercise enforcement discretion with respect to certain PDS software, the positions set forth in the CDS Guidance—and the examples provided therein—mirror previous FDA guidance and examples that pre-dated the 21st Century Cures Act. While the CDS Guidance confirms that the agency intends to take a similar approach to CDS as it has taken to mobile medical apps (MMAs), certain important questions remain unanswered, most notably:

    • How will FDA regulate CDS software that relies on complex machine learning functionality?
    • Will FDA acknowledge that enforcement discretion may be appropriate with respect to certain low risk CDS software?
    • How does FDA plan to regulate multifunction software products that provide multiple intended uses and both regulated and potentially unregulated functions?

    Stakeholders should consider submitting comments on these and other issues of interest to inform FDA’s consideration of the final guidance documents. The draft guidance documents are open for comment until February 6, 2018.

    Authors

    Michael W. Ryan

    Partner

    Washington, DC

    More insights

  • Tax Court Addresses §956 Issues Concerning CFC Loans and Guarantees

    ARTICLE

    Tax Court Addresses §956 Issues Concerning CFC Loans and Guarantees

    December 8, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Lowell Yoder wrote this bylined article on a recent US Tax Court case, Crestek v. Commissioner, which addressed several issues concerning the application of §956 to CFC (controlled foreign corporation) loans and guarantees. The court “applied a plain reading of the Code in determining the treatment of investments in US property held by CFCs,” Mr. Yoder wrote.

    In depth
    Authors

    Lowell D. Yoder

    Partner

    Chicago

    More insights

  • Congressional Tax Reform Efforts May Impact Retirement Plan Sponsors

    Congressional Tax Reform Efforts May Impact Retirement Plan Sponsors

    ARTICLE / CLIENT ALERT

    Congressional Tax Reform Efforts May Impact Retirement Plan Sponsors

    December 7, 2017

    Read time: 8 min

    Key takeaways
    Overview

    On Saturday, the Senate passed its version of the Tax Cuts and Jobs Act. The process of reconciling the House and Senate versions of the bill has already begun in earnest. Currently, the retirement-plan-related changes included in each version of the bill still differ in many respects, and it is unclear which (if any) changes will be included in the final bill. As a result, with only a few weeks left until the holiday recess, a clear picture of the potential impact of tax reform on retirement plan sponsors has yet to emerge.

    In depth

    Early Saturday morning, following an all-night voting session, the Senate passed its version of the Tax Cuts and Jobs Act (Act), bringing Congressional Republicans one step closer to securing the most sweeping overhaul of the tax code in decades. Changes to the nearly 500-page bill, including handwritten revisions to the document, were still being made only hours before the final vote concluded just before 2 am on Saturday. Now that both the House and Senate have approved their own versions of the Act, they will begin the process of reconciling those versions to create a final bill, which must then be passed by both chambers.

    Both the House and Senate versions of the Act include proposed changes that would affect all tax-qualified retirement plans, including both pension and savings plans. Despite early speculation, neither version of the Act includes the most controversial potential change, a proposal to significantly reduce the limit on pre-tax contributions to employer-sponsored 401(k) plans ($18,500 for 2018). In addition, the version of the Act passed by the Senate on Saturday does not include some of the more significant changes that would have applied to section 403(b) and governmental section 457(b) plans under the summary of the bill released by the Senate last month. However, both the House and Senate versions of the Act include a number of smaller changes that could impact retirement plan administration.

    In Depth

    Of the retirement-plan-related changes currently under consideration, very few have been approved by both the House and Senate. Instead, many of the proposed changes appear in only one version of the Act.

    Proposed Changes Approved by Both the House and the Senate

    Rollovers of Loan Repayments

    Both the Senate and House versions of the Act include relief that would extend the period for rolling over a loan offset. Retirement plan loans generally become immediately due and payable when a plan participant terminates employment. If the loan is not repaid, the plan offsets the loan against the value of the participant’s account. Currently, this type of loan offset may be rolled over by a participant tax-free if he or she makes an equivalent contribution to another tax-qualified plan or individual retirement account (IRA) within 60 days of the date of the offset. Both versions of the Act would extend this period, from the current 60 days to the due date (including extensions) for the affected participant’s tax return for the year in which the offset occurred.

    Recharacterization of Contributions to Traditional and Roth IRAs

    In addition, both the Senate and House versions of the Act would eliminate the ability to recharacterize a traditional IRA contribution as a Roth IRA contribution, as well as the ability to recharacterize a Roth IRA contribution as a traditional IRA contribution.

    Proposed Changes Approved by Only the House

    Expanded In-Service Distributions for Defined Benefit Plans

    When the House version of the Act was passed last month, it included a rule that would lower the minimum age for receiving an in-service distribution from a defined benefit plan. Currently, defined benefit plan sponsors may allow active employees to request in-service distributions of their plan benefits beginning as early as age 62. The House version of the Act lowers the age for receiving this type of distribution to age 59½. The House version would also lower the age at which in-service distributions would be permitted from governmental section 457(b) plans from 70½ to 59½. Both changes would provide plan sponsors greater flexibility in plan administration; however, the Senate version of the Act does not currently include similar provisions.

    Non-Discrimination Testing Relief for Closed Defined Benefit Plans

    The House version of the Act also permanently extends the temporary nondiscrimination testing relief currently available to certain employers sponsoring closed defined benefit plans. Many employers have closed their defined benefit plans to new participants, but permit existing participants (or groups of participants) to continue to earn benefits under the plan. Because new employees can no longer enter the plan, closed plans can become discriminatory if the attrition rate of non-highly compensated employees outpaces the attrition rate of highly compensated employees.

    Therefore, the House version of the Act provides permanent nondiscrimination testing relief that mirrors relief previously established by Notice 2014-5 and extended earlier this year. Like the existing relief, the permanent relief provided under the House version of the Act would make it easier for closed pension plans to satisfy certain nondiscrimination testing requirements by expanding the availability of cross-testing between defined benefit and defined contribution plans. However, the Senate version of the Act does not include this relief, meaning its inclusion in any final bill will need to be addressed in the reconciliation process.

    Hardship Withdrawals

    The House version of the Act includes several provisions that would relax certain rules that apply to participants requesting hardship withdrawals from employer-sponsored 401(k) plans.

    Specifically, the House version of the Act would eliminate the requirement that employers suspend employee contributions under 401(k) plans for the six month period following a hardship withdrawal. The House version of the Act would also eliminate the requirement that participants take all available retirement plan loans before receiving a hardship distribution and would expand the sources of 401(k) accounts currently available for hardship withdrawals (to include not only elective deferrals, but qualified non-elective contributions (QNECs), qualified matching contributions (QMACs) and earnings on those amounts), together with earnings on elective deferrals. The Senate version of the Act does not include any similar provisions designed to facilitate or expand the availability of hardship distributions. However, the summary comparison of the House and Senate versions of the Act, published on December 7, 2017, by the Joint Committee on Taxation, suggests that both versions of the Act include the same proposed changes to current hardship withdrawal rules.

    Proposed Changes Approved by Only the Senate

    Contribution Limits under Section 403(b) and Section 457(b) Plans

    When the Chairman’s Mark of the “Tax Cuts and Jobs Act” (Chairman’s Mark) was released last month, it included a number of provisions that, if adopted, would have had significant implications for governmental section 457(b) plan sponsors who also maintain a 403(b) plan. However, the version of the Act passed by the Senate on Saturday does not include some of those more significant changes.

    The Chairman’s Mark suggested that the Senate would adopt rules that would harmonize the contribution limits that apply to 401(k), 403(b) and 457(b) plans beginning next year, meaning that all 401(k), 403(b) and 457(b) plans (rather than just 401(k) and 403(b) plans) would have a combined deferral limit ($18,500 for 2018). The Chairman’s Mark also indicated that the Senate would (i) set a single aggregate limit on contributions to all 401(k), 403(b) and 457(b) plans maintained by the same employer; (ii) modify the special catch-up contributions available to certain 403(b) plan participants and the special contribution limitations for governmental section 457(b) plans; and (iii) eliminate a special rule under which employers may continue to make contributions to 403(b) plans for up to five years after an employee terminates from employment.

    However, the Senate version of the Act passed on Saturday only includes one of the changes original proposed in the Chairman’s Mark, a rule that would increase the special contribution limitations for governmental 457(b) plans from $3,000 to $6,000 (as adjusted each year), to mirror the 401(k) plan catch-up contribution limit.

    Conclusion

    Given the substantial differences between the House and the Senate versions of the Act, it is unclear what changes, if any, retirement plan sponsors will be required to make to their plans. However, because these bills may affect retirement plan administration as early as 2018, employers should keep a close eye on the developing legislation. As the House and Senate continue the reconciliation process, a clearer picture of the potential impact of tax reform on retirement plan sponsors should begin to emerge over the next couple of weeks.

    Authors

    Alan D. Nesburg

    Counsel

    Chicago

    More insights

  • Executive Compensation in Germany – Taxation as a Proposed Way of Regulation

    ARTICLE

    Executive Compensation in Germany – Taxation as a Proposed Way of Regulation

    December 7, 2017

    Read time: 2 min

    Key takeaways
    Overview

    In the run-up to the last two federal elections the limitation of executive compensation was discussed between the political parties in Germany. The topic is obviously a reliable source for media attention. And every time the proposals lack structural solutions that could have the potential for effective change in favor of more populist terms. This time the Social Democrats (SPD) published a draft bill proposing a tax non-deductibility of management remuneration (including pension schemes) above EUR 500,000. Dr. Nils Wighardt and Dr. Andreas Berger explain in their article that this is not only insufficient, but also a one-sided approach at the expense of shareholders while explaining that a simplification could enable the supervisory board to avoid the risk of unjustified payments and media critic independent of the current regulation.

    In depth
    Authors
    More insights

  • ISS and Glass Lewis 2018 Proxy Guidelines Continue to Expand Shareholder Influence

    ISS and Glass Lewis 2018 Proxy Guidelines Continue to Expand Shareholder Influence

    ARTICLE / CLIENT ALERT

    ISS and Glass Lewis 2018 Proxy Guidelines Continue to Expand Shareholder Influence

    December 6, 2017

    Read time: 8 min

    Key takeaways
    Overview

    Proxy advisory firms Institutional Shareholder Services (ISS) and Glass Lewis recently published their proxy voting policy updates for 2018. ISS’s updated guidelines will apply to stockholder meetings held on or after Feb. 1, 2018, while Glass Lewis’s policy will generally apply to meetings held on or after Jan. 1, 2018. The changes reflect an increased focus on governance issues raised by shareholder activists over the past year. The major updates to the voting guidelines are summarized below.

    ISS 2018 Proxy Voting Guidelines

    Staggered Boards: ISS will now recommend a vote against or withhold from the entire board of directors (except new nominees, who are considered on a case-by-case basis) of companies that have opted into, or failed to opt out of, state laws requiring a classified board. Under certain state statutes, such as the Maryland Unsolicited Takeover Act, boards may be able to opt into requirements that would stagger the board without a stockholder vote, while other state statutes require public companies to have staggered boards unless such companies affirmatively opt out of the statute. Companies subject to these statutes have a powerful and preclusive defensive tactic that can be used to entrench boards without stockholder input, and the new ISS policy may serve as a disincentive to companies seeking to use such tactics.

    Shareholder Rights Plans (Poison Pills): ISS will now recommend a vote against or withhold from all nominees of a company with a poison pill with a term longer than one year that was not approved by shareholders. Under the previous ISS policy, ISS drew a distinction between classified and annually elected boards with poison pills, and would only recommend votes against or withhold votes at least once every three years for annually elected boards. In addition, a commitment to put a long-term poison pill to a binding shareholder vote no longer will offset an adverse vote recommendation. Regarding short-term rights plans (one-year or less) nominees will be considered on a case-by-case basis, with ISS focusing on the rationale for adopting the pill and other relevant factors.

    Restrictions on Binding Shareholder Proposals: In the past, ISS has generally recommended against or withheld from members of a company’s governance committee if the company’s charter included excessive restrictions on stockholders’ ability to amend the charter. The 2018 guidelines expand that general rule to include undue restrictions in all of the company’s governing documents, including the bylaws.

    Pledging of Company Stock: ISS will recommend a vote against the committee overseeing risks related to pledging or the full board where a significant level of pledged stock by executives or directors raises concerns. This update codifies a practice that ISS implemented in 2013.

    Excessive Non-Employee Director Compensation: Non-employee director (NED) compensation has risen every year since 2012. This issue is consistently in the spotlight, and some activists have gone so far as to challenge director pay in proxy fights. Accordingly, ISS is implementing a new policy of providing an adverse vote recommendation for board or committee members responsible for setting NED pay where there is a pattern (i.e., two or more consecutive years) of excessive pay without providing a compelling rationale or other mitigating factors. This policy will not have an effect on 2018 vote recommendations.

    Say-on-Pay: ISS has consistently provided that it will recommend a vote against, on a case-by-case basis, compensation committee members or the full board where the company’s previous say-on-pay proposal received less than 70 percent shareholder support. While ISS previously considered several factors in this decision, the 2018 guidelines state that ISS will also consider the breadth of company disclosure regarding engagement efforts by institutional investors, specific concerns of dissenting shareholders and specific actions that the company has taken to address shareholders’ concerns. When companies comply with these disclosure requirements, it will shine additional light on concerns with executive pay.

    Pay-for-Performance Evaluation: In connection with its past pay-for-performance evaluation, ISS will now analyze rankings of CEO total pay and company financial performance over the previous three years as compared to peer group companies. Additionally, ISS will report the multiple of a CEO’s total pay relative to its peers over the last fiscal year.

    Boardroom Diversity: ISS has made it a fundamental principal that boards should be “sufficiently diverse to ensure consideration of a wide range of perspectives.” Accordingly, ISS will identify in its reports where a board lacks gender diversity. However, ISS will not issue any adverse voting recommendations due to a lack of gender diversity. Nonetheless, the gender of directors should be considered when formulating director slates.

    Glass Lewis 2018 U.S. Policy Guidelines

    Dual-Class Share Structures: Glass Lewis continues to believe that dual-class voting structures are not in the best interest of shareholders and that companies should implement a one vote per share system. Therefore, Glass Lewis will typically recommend that shareholders vote in favor of recapitalization proposals that eliminate dual-class stock structures. Further, Glass Lewis will recommend against proposals to adopt new classes of common stock. Importantly, following an IPO or spin-off, the presence of dual-class shares will be a sign to Glass Lewis that shareholder rights are severely restricted. Finally, in examining the results from shareholder meetings at companies with dual-class stock structures with disparate voting and economic rights, where the vote results indicate that a majority of unaffiliated shareholders supported a shareholder proposal or opposed management’s proposal, Glass Lewis believes that the board should demonstrate an appropriate level of responsiveness.

    Board Responsiveness: Glass Lewis has long encouraged a board response where 25 percent or more of shareholders vote against management’s recommendation. However, in response to increased investor sentiment, spurred by shareholder activism, beginning in 2018, where 20 percent or more of shareholders vote against management, the board should demonstrate some level of responsiveness to shareholder concerns. The 20 percent figure includes when shareholders withhold votes or vote against a director nominee, vote against a management-sponsored proposal or vote for a shareholder proposal. The 20 percent threshold does not automatically lead to a negative recommendation, but will be a contributing factor if Glass Lewis determines that the board was not responsive. This policy change demonstrates that Glass Lewis is raising board response standards in light of increased shareholder engagement.

    Virtual Shareholder Meetings: While Glass Lewis believes that virtual meeting technology can be a useful complement to a traditional shareholder meeting, it recognizes the potential that virtual-only shareholder meetings may reduce board accountability and stifle shareholder discourse. In 2018, Glass Lewis will not make voting recommendations based only on a company holding virtual-only meetings. However, beginning in 2019, Glass Lewis will recommend voting against members of the governance committee of a board that plans a virtual-only meeting without robust disclosure that ensures shareholders have the same rights and opportunities as in-person meetings.

    Director Commitments: Due to historically high levels of time directors devote to their positions, Glass Lewis will begin generally recommending against directors who serve as an executive officer of a public company while serving on more than two public company boards. However, Glass Lewis will not recommend voting against overcommitted directors at companies where they also are an executive. Similarly, Glass Lewis will typically recommend votes against directors who serve on more than five public company boards. In determining whether to recommend against potentially overcommitted directors, Glass Lewis will consider the size and location of companies where the director serves on the board, director position on those boards, director’s tenure on the boards and director’s attendance record at board meetings. Conversely, Glass Lewis indicates that it will generally not recommend voting against an overcommitted director who serves on company boards within a consolidated group of companies or whose firm’s sole purpose is to manage a portfolio of investments which include the company.

    Board Gender Diversity: As in previous years, Glass Lewis will consider board composition and may note instances where it believes a board lacks diverse director candidates. In 2018, Glass Lewis will not make any voting recommendations solely on the basis of board diversity. However, in 2019, Glass Lewis will generally recommend voting against the nominating committee chair of boards that do not have any female directors. Glass Lewis may extend this recommendation to other nominating committee members depending on the size, industry and governance profile of the company.

    Glass Lewis’s 2018 U.S. Policy Guidelines are available here.


    Authored by Eleazer Klein and Brandon S. Gold.

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

    In depth
    Authors

    Ele Klein

    Partner

    New York – 919 Third Avenue

    Brandon S. Gold

    Partner

    New York – 919 Third Avenue

    More insights

  • Trebled Damages Mean No Injunction for Knock-Off Software

    ARTICLE

    Trebled Damages Mean No Injunction for Knock-Off Software

    December 6, 2017

    Read time: 2 min

    Key takeaways
    Overview

    Jodi Benassi wrote this bylined article on the Fourth Circuit’s SAS Institute, Inc. v. World Programming Ltd. ruling, which affirmed in part, reversed in part and remanded a district court finding that a defendant was liable for breach of a software license agreement and therefore infringed the plaintiff’s copyright in the subject software.

    In depth
    Authors
    More insights