Content Type: Article

  • Private Markets Update | Summer 2024

    Private Markets Update | Summer 2024

    ARTICLE / REPORT

    Private Markets Update | Summer 2024

    Summer 2024

    Read time: 2 min

    Overview

    The Private Markets Update highlights key developments emerging from private markets across Europe, the UK and the United States, exploring the cross-border issues that matter to investors and sponsors in alternative assets.

    In this edition, we examine developments in the markets over the first half of 2024, and highlight some of the key issues facing investors as we move into the second half of the year.

    In depth
    Tabs

    Stéphane Dionnet

    Partner

    Brussels

    Aymen Mahmoud

    Partner

    London – 22 Bishopsgate

    Fatema Orjela

    Partner

    London – 22 Bishopsgate

    Riley T. Orloff

    Partner

    New York – One Vanderbilt Avenue

    Ettore Scandale

    Partner

    Milan

    Ian M. Schwartz

    Partner

    New York – One Vanderbilt Avenue

    Jack Thorne

    Partner

    London – 22 Bishopsgate

    Pilar Arzuaga

    Partner

    London – 22 Bishopsgate

    Harry Denlegh-Maxwell

    Senior Associate

    London – 22 Bishopsgate

    More insights
    Endnotes

  • Real-World Data Back in the Spotlight at FDA

    Real-World Data Back in the Spotlight at FDA

    ARTICLE / CLIENT ALERT

    Real-World Data Back in the Spotlight at FDA

    August 12, 2024

    Read time: 6 min

    Key takeaways
    Overview

    On July 25, 2024, the US Food and Drug Administration (FDA) announced the release of a final version of its Real-World Data: Assessing Electronic Health Records and Medical Claims Data to Support Regulatory Decision-Making for Drug and Biological Products Guidance. This guidance outlines important considerations for the use of real-world evidence (RWE) in the form of electronic health records (EHRs) and medical claims data in clinical studies, including interventional clinical investigations and observational studies. The guidance finalizes the prior draft guidance issued by FDA in September 2021 with minimal changes, such as clarifications related to use of data sources and discussion of artificial intelligence (AI) technologies.

    Stakeholders potentially affected by this guidance include sponsors; sources of EHR or claims data such as EHR vendors, payors and data aggregators; and other interested parties such as developers of AI tools used to curate or analyze such data. These stakeholders should review the guidance and be familiar with its recommendations for leveraging data sources for FDA regulatory decision making.

    In depth

    Background

    The 21st Century Cures Act, enacted December 13, 2016, required FDA to issue guidance regarding the use of RWE in regulatory decision making. This requirement led to FDA’s September 30, 2021, draft guidance outlining considerations for the use of real-world data (RWD) and RWE in regulatory decision making.

    Although FDA received significant feedback from industry on the draft guidance that requested greater flexibility, the final guidance largely adopts the draft guidance with the following key changes:

    • Clarifies that the selection of study variables for validation and the extent of effort required for validation depends on the necessary level of certainty and the implication of potential misclassification on study inference.
    • Notes that choice of a reference standard for validation may vary based on study design and question, the variable of interest and the necessary level of certainty.
    • Recommends the use of quantitative approaches to demonstrate whether and how misclassification, if present, might impact study findings.
    • Removes generally understood defined terms.

    Analysis

    The guidance discusses the selection of data sources; development and validation of definitions for study design elements; and data traceability and quality during data accrual, curation and incorporation. Notably, the guidance does not provide recommendations on study design or statistical analysis, nor does it endorse any type of data source or study methodology.

    The guidance employs the following definitions for key terms:

    • RWD means “data relating to patient health status or the delivery of health care routinely collected from a variety of sources.”
    • RWE means the “clinical evidence regarding the usage and potential benefits or risks of a medical product derived from analysis of RWD.”
    • Medical claims data means “information submitted to insurers to receive payment for treatments and other interventions.”
    • Clinical studies mean “all study designs, including, but not limited to, interventional studies where the treatment is assigned by a protocol and non-interventional studies where treatment is determined in the course of routine clinical care.”

    Data Sources

    Under the guidance, FDA recommends that protocols submitted to FDA identify all data sources proposed for the study, and that all such data sources be assessed to determine whether they are appropriate for addressing specific study questions. In particular, FDA recommends that the protocol specify the relevance and reasoning for selecting the applicable data sources. Such reasoning should address the likelihood of a data source containing the sought after information. For example, given that EHRs are captured in the course of health services and not under the protocol, a protocol proposing to use EHRs should identify the type of information being sought and relevant background detailing how the EHR captures that information.

    The guidance also discusses considerations for data linking to create broader longitudinal datasets. FDA notes that protocols should describe the accuracy and completeness of data linkages, linkage methods and any potential issues with linkage quality through the use of probabilistic and deterministic approaches. Sponsors and stakeholders that support such data linking should be mindful of the expectations that FDA outlines in the guidance regarding linking accuracy.

    Recognizing the proliferation of AI and its potential applications in curating unstructured data, FDA recommends that protocols proposing to use AI or other derivation methods specify the assumptions and parameters of the algorithms, the data set used to train and build the algorithms, and information regarding supervision of the algorithm along with any metrics regarding validation of the methods. FDA makes clear that it does not endorse any type of AI technologies. It’s unclear whether any information regarding adverse events discovered during an AI scrape of the EHR would impose reporting or other obligations on the manufacturer.

    Study Design Elements

    FDA clarifies that the study should not be designed to fit a specific data source, but rather the data sources should be selected to best fit the questions of interest. FDA discusses design elements and parameters such as time, study population, exposure ascertainment and outcome ascertainment. In this discussion, FDA encourages the use of quantitative approaches, such as quantitative bias analyses, to demonstrate how key covariates might impact study findings.

    Data Quality

    The guidance provides recommendations for examining the quality of EHR and medical claims data during the data lifecycle. FDA recommends:

    • Characterizing data according to completeness, conformance and plausibility of data values.
    • Documenting the quality assurance and quality control (QA/QC) plan that includes transformation processes.
    • Outlining procedures for ensuring data integrity.

    These activities, including preparing the QA/QC plan for addressing data quality issues, may as a practical matter require careful coordination between the sponsor and the RWD sources, including EHR vendors and other stakeholders such as data extraction and migration vendors, data tokenization vendors, de-identification vendors, and AI and other developers that provide data curation solutions. Stakeholders should carefully evaluate the various characteristics and issues that the guidance highlights with respect to evaluating data quality.

    The guidance represents the latest step in FDA’s ongoing efforts to address the appropriate role of RWD and RWE in the regulatory process.

    For more information on the RWE guidance, please contact one of the authors or any other member of McDermott’s Food, Drug & Medical Device Regulatory Practice Group.

    Authors

    James R. Ravitz

    Partner

    Washington, DC

    Jiayan Chen

    Partner

    Washington, DC

    Paul S. Gadiock

    Partner

    San Francisco

    Jennifer S. Geetter

    Partner

    Washington, DC

    Jeff Weinstein

    Counsel

    Washington, DC

    Sam Siegfried

    Partner

    Chicago

    Marissa Hill Daley

    Law Clerk

    Washington, DC

    Jae Hyun Lee

    Associate

    New York – One Vanderbilt Avenue

    More insights

  • Missed Appropriation: Massive Trade Secret Verdict Vacated

    Missed Appropriation: Massive Trade Secret Verdict Vacated

    ARTICLE

    Missed Appropriation: Massive Trade Secret Verdict Vacated

    Aug 8, 2024

    Read time: 4 min

    Key takeaways
    Overview

    The Court of Appeals of Virginia vacated a $2 billion award in a trade secret misappropriation case based on a series of evidential errors and improper jury instructions. Pegasystems Inc. v. Appian Corporation, Case No. 1399-22-4 (Va. Ct. App. 2024) (Beales, Friedman, Callins, JJ.)

    Pegasystems and Appian are both companies in the business process management (BMP) industry and offer platforms that allow third parties to build software applications. Appian accused Pega of trade secret misappropriation, presenting evidence that Pega used the employee of a licensee of Appian’s technology to pass trade secrets to Pega, thereby enabling Pega to better market its own technology and exploit Appian’s weaknesses. Pega’s “spy,” Youyong Zou, recorded almost 100 videos of Appian’s platform and used them to demonstrate the strengths and weaknesses of Appian’s system in tutorials sent to Pega. Appian brough an action against Pega and Zou under the Virginia Uniform Trade Secrets Act (VUTSA) and the Virginia Computer Crimes Act. At trial, the jury returned a verdict in favor of Appian, finding that Pega and Zou misappropriated Appian’s trade secrets in violation of VUTSA. The jury awarded Appian damages in excess of $2 billion, which was the largest damages verdict in Virginia’s history. Pega appealed.

    The Appellate Court found that although Appian did not fail as a matter of law to prove evidence of trade secret misappropriation, the trial court erred in instructing the jury by failing to place the burden of proximate causation on Appian, as required by both VUTSA and Virginia precedent. The Appellate Court found that this error resulted in a potentially excessive award that assumed all of Pega’s sales were tainted by the misappropriation. The Appellate Court instructed that on remand, Appian bears the burden of proving that the misappropriation caused the alleged damages and proving the amount of damages attributable to the trade secret with reasonable certainty. The Appellate Court also found that the trial court erroneously excluded key evidence that could have established that much of Pega’s revenue had nothing to do with the alleged misappropriation.

    The Appellate Court further found that the trial court erred in excluding evidence that Pega argued would establish that many of the allegedly stolen features actually predated Pega’s contact with Zou. The trial court had excluded the evidence because the original laptop with this evidence had become inoperable. The trial court had refused to allow Pega the opportunity to authenticate the evidence and introduce the software on a new laptop. The Appellate Court found that this refusal was an abuse of discretion. The Appellate Court concluded that Pega was entitled to introduce a copy of this software under the rules of evidence, even if it was not on the original laptop.

    Finally, the Appellate Court determined that the trial court erred in instructing the jury that the number of people with access to Appian’s trade secrets was “not relevant” to “any issue in this case.” The Appellate Court found that Pega’s evidence that “thousands” of people potentially had access to Appian’s trade secrets was relevant to (although not dispositive regarding) Appian’s reasonable efforts in protecting its secrets and whether such secrets were generally known or readily ascertainable.

    The Appellate Court therefore reversed the judgment and remanded for a new trial.

    Authors

    Anisa Noorassa

    Associate

    San Francisco

    More insights
    Endnotes

  • States Want in on the Merger Review Fun

    States Want in on the Merger Review Fun

    ARTICLE

    States Want in on the Merger Review Fun

    Aug 8, 2024

    Read time: 5 min

    Key takeaways
    Overview
    In depth

    WHAT HAPPENED

    While they have long taken a back seat to federal merger reviews, US states are becoming increasingly involved in merger reviews, including potentially requiring premerger notifications on a broad scale. On July 24, 2024, the Uniform Law Commission adopted its Uniform Antitrust Pre-Merger Notification Act (Model Act) as model legislation for states to use to implement premerger filing regimes.

    • The Act functions as a template for states to adopt their own premerger notification legislation and provides uniform suggested guidance to states that are considering their own premerger notification regimes.
    • The Model Act requires parallel filing of the Hart-Scott-Rodino (HSR) form in a state when:
      • The filing person has its principal place of business in the state; or
      • The person “directly or indirectly had annual net sales in [the] state . . . of at least 20 percent” of the threshold mandated under the HSR Act. §3(a)(1)-(2). Under the current HSR thresholds, that means sales of approximately $24 million in a state would satisfy the state-level filing requirement.
    • The Model Act also provides for automatic confidential treatment of materials submitted to the state.
      • Additionally, the attorneys general may communicate with the federal agencies about filing materials.
      • This can avoid the current practice of having to negotiate individual confidentiality agreements with any state interested in reviewing a transaction.
    • The Model Act does not impose any waiting or suspension period for notified transactions.
    • This continues a trend of government agencies obtaining more notice of M&A transactions. At the end of last year, Congress inserted Section 857 into the National Defense Authorization Act, which requires parties to provide their HSR materials to the US Department of Defense (DoD) for any proposed merger or acquisition that will require DoD review.

    BACKGROUND

    State attorneys general have broad investigatory and enforcement powers with respect to transactions implicating local competition concerns. States generally have the authority to issue investigative subpoenas, compelling production of documents and information to parties who merely sell products in a state without any further physical connection to the state.

    • Typically, states focus their efforts on transactions that have a particular impact on the state’s consumers or an industry important to the state’s economy.
      • For example, transactions involving hospitals or retail locations are traditionally more likely to draw the attention of a state’s attorney general than transactions involving national markets or consumer goods.
    • However, state enforcers have increasingly initiated their own efforts to challenge transactions.
      • This trend is illustrated by the Colorado attorney general’s lawsuit that seeks to block the Kroger-Albertsons merger.
        • Colorado is seeking a nationwide injunction and not merely an injunction on the acquisition in the state, raising a novel question with potentially significant impact on antitrust enforcement by the states.
        • Colorado is proceeding independently of the Federal Trade Commission’s (FTC) challenge to the transaction.
    • In the past few years, several states have enacted legislation to require notice and reporting of some transactions and imposing waiting periods to allow for the state’s review.
      • Many states have enacted statutes requiring filing for healthcare transactions, which often have a very localized nexus.
        • McDermott tracks these health-specific statutes here.
      • Other states have been moving to broader filing obligations:
        • For instance, New York’s proposed Senate Bill S6748B is very broad. It would require any person conducting business in the state to provide a copy of its HSR filing to the attorney general at the same time the filing is submitted to the FTC and the US Department of Justice.
        • This January, California began reviewing mergers and acquisitions by healthcare entities in the state pursuant to its 2022 Healthcare Care Quality and Affordability Act. Healthcare entities must file state-level merger notification forms in parallel with any required HSR filings, and transactions involving an out-of-state entity may also be captured. Similar requirements have been imposed for retail grocery and pharmacy transactions.

    WHAT THIS MEANS FOR COMPANIES

    • Even though only few states have enacted or proposed to enact their state-specific merger notification regimes, many others may seek to adopt the Uniform Antitrust Pre-Merger Notification Act.
    • If states adopt the legislation, companies contemplating transactions will need to track their sales generated in each state to properly assess whether notification to the state attorneys general will be required.
      • Many companies collect information annually to have their HSR materials “on the shelf,” and this could add yet another item to that process.
    • Companies should seek counsel to evaluate any relevant competitive impacts that implicate local markets. In particular, identifying the relevant local markets is an essential preliminary assessment, as state enforcers typically have particular concerns regarding localized geographic markets and their competitive landscapes.
    Authors

    Jon B. Dubrow

    Partner

    Washington, DC

    Betty (Yajing) Zhang

    Associate

    Los Angeles

    More insights
    Endnotes

  • The Case for the Welfare Plan Fiduciary Committee

    The Case for the Welfare Plan Fiduciary Committee

    ARTICLE / CLIENT ALERT

    The Case for the Welfare Plan Fiduciary Committee

    August 8, 2024

    Read time: 9 min

    Key takeaways
    Overview

    Recent lawsuits filed against the group health plans of two large US employers underscore the importance of implementing formal welfare benefit plan governance structures that include fiduciary committees comparable to the governance structures employer sponsors of retirement plans routinely adopt.

    The origins of this trend for retirement plans are not hard to trace: In the fall of 2003, a federal district court in Texas denied motions to dismiss the Employee Retirement Income Security Act (ERISA) claims in Tittle v. Enron. The 300-page opinion caught plan sponsors by surprise. The lawsuit included claims against Enron’s board and senior management, as well as its retirement plan committee. Had Tittle v. Enron been an isolated incident, plan sponsors may have forgotten about it. But in 2006, 13 lawsuits were filed against major companies claiming that these employers violated their fiduciary obligations under ERISA by selecting funds for their 401(k) plans that charged allegedly excessive fees. These lawsuits were just the beginning of a burgeoning cottage industry among plaintiffs’ law firms against 401(k) – and later 403(b) – plans that continues to this day. Fiduciary plan committees have become a first line of defense as plan sponsors and fiduciaries seek to insulate themselves from liability.

    The ERISA fiduciary standards that are at the heart of 401(k) plan litigation apply equally to all welfare benefit plans, but until recently, employer sponsors of welfare benefit plans seemed unfazed by the trends for 401(k) and 403(b) plans. The filing and initial skirmishes in Lewandowski v. Johnson and Johnson may change that complacency. Filed earlier this year, Lewandowski alleged a series of fiduciary violations involving Johnson and Johnson’s group health plan(s). The case is currently a proposed class action for breach of fiduciary duties. The putative plaintiff class alleges that the defendants failed to effectively manage the company’s prescription drug benefit program by failing to pay only reasonable amounts for prescription drugs, supervise and monitor conflicted third parties, and monitor the plan’s prescription drug formulary. While we are still a long way from any final adjudication of the matter, employers should nevertheless take note: Lewandowski signals a turning point in our view. It is time to establish a welfare plan fiduciary committee to reduce litigation risk.

    In depth

    The Devolution of Fiduciary Authority

    The devolution of fiduciary authority under ERISA highlights the complexity and responsibility inherent in managing employee benefit plans. Fiduciaries – whether named, functional or appointed – must navigate a landscape defined by stringent duties of loyalty, prudence and adherence to plan documents. The requirement to monitor delegated duties ensures ongoing accountability and underscores the importance of prudent oversight. These obligations are no less relevant to welfare plans than they are to retirement plans. As legal standards and regulatory expectations evolve, fiduciaries must stay vigilant and informed to fulfill their obligations effectively, ultimately safeguarding the interests of plan participants and beneficiaries – including taking any actions necessary to ensure that fiduciary obligations are met for welfare plans.

    ERISA fiduciaries must, among other things, discharge their duties solely in the interest of plan participants and beneficiaries and for the exclusive purpose of providing benefits and defraying reasonable administrative expenses. In addition, ERISA fiduciaries are held to the duties of loyalty and prudence, and they must follow plan documents, among other requirements. A person can become a fiduciary to an ERISA plan by being named in the plan (a “named fiduciary”), by position (the plan’s trustee, plan administrator and investment manager are always considered fiduciaries), by exercising discretionary authority or discretionary control over a plan’s management, assets, or administration (a “functional fiduciary”), or by being appointed to perform a fiduciary function by another person. By default, the plan sponsor (typically the employer of the plan’s participants) is the ERISA “plan administrator,” and thus a fiduciary, unless some other person or entity is appointed to the role.

    Named fiduciaries can be either named in, or appointed pursuant to a procedure established by, the plan document. The named fiduciary may further delegate aspects of his or her fiduciary duty to other fiduciaries. The US Department of Labor is of the view, supported by case law, that named fiduciaries cannot fully off-load their fiduciary duties by delegating these duties to others (e.g., to a plan retirement committee or third-party administrator). Rather, the delegating fiduciary must ensure that the delegation was prudent and remains so thereafter. This requirement is the source of the “duty to monitor.” And while the contours of the duty to monitor are not perfectly defined, there is general agreement that some sort of periodic reporting backup to the appointing fiduciary is a minimum requirement.

    The Fiduciary Committee

    The establishment of a fiduciary committee through formal action and proper documentation is crucial for mitigating fiduciary responsibilities for a company’s board of directors and senior management. By designating a committee as the ERISA plan administrator and ensuring regular reporting to the board, organizations can limit the fiduciary exposure of individuals who lack substantive knowledge of the inner workings of the company’s employee benefit plans. This structured approach not only protects board members and senior managers from detailed scrutiny during litigation but also upholds the integrity and proper oversight of the plan’s management.

    While it is possible to avoid even residual fiduciary responsibility on the part of a board of directors – a plan could, for example, designate a fiduciary committee as the named fiduciary by its terms – few plans attempt this. A more common approach is for a plan to designate (say, in a basic plan document) the plan sponsor as the named fiduciary unless otherwise specified in the corresponding adoption agreement. Under the default rule, the board of directors (of a corporation) or the managers (of a limited liability company) or the partners (in a partnership) are the named fiduciaries.

    However, with proper planning and documentation, it is possible to ensure that an organization’s board of directors or managers, as applicable, retain only residual “duty-to-monitor” obligations by having the board or members formally vote and pass resolutions to establish one or more fiduciary committees (e.g., one retirement plan and one welfare plan committee). The fiduciary committee would not ordinarily include board members for reasons explained below. It is also possible to ensure that a company’s senior managers have no fiduciary duties by excluding them from committee participation and otherwise ensuring that they keep their distance from plan maintenance and operation.

    To understand the stakes, consider a company has a group health plan but no formal fiduciary committee. In this example, by default, the board is the plan administrator, and members of management have likely exercised discretion over plan management, thereby making them fiduciaries as well. The plan is sued. The plaintiff’s lawyers will depose the board members and senior managers, asking them detailed questions about plan maintenance and operation. It takes little imagination to understand that these depositions will not go well. Now consider the alternative: Assume that the board has formally voted and passed resolutions to establish a welfare plan fiduciary committee, which is designated as the ERISA plan administrator. The vote also adopts a committee charter (or delegates that task to the committee) and might also include guidelines for the committee’s operations. The committee is required to report at least annually to the board on its operations, thereby facilitating the board’s oversight. Now again assume that the plan is sued. While the board members will likely be deposed, the plaintiff’s inquiry will be limited to their oversight of the committee’s actions.

    The above examples illustrate two important principles:

    1. Individuals without substantive knowledge of an employee benefits plan should not be given substantive fiduciary responsibilities.
    2. In the event of litigation, it’s easy to impeach or at least embarrass such an individual by exposing their lack of substantive knowledge.

    This is one lesson of Tittle v. Enron. It is for this reason that, in the absence of special knowledge or expertise, board members or organization managers should not participate on fiduciary committees. It is one thing to ask a board member about the substance of their day-to-day actions as a fiduciary; it is quite another thing to ask about their proper oversight of others.

    There is another, equally compelling lesson in the above examples. The grant of authority and the establishment of the committee requires formal action. The appointment of a welfare plan fiduciary committee without a vote designating the committee as the plan administrator is insufficient. Failure to observe the formalities leaves the board or members with full-blown fiduciary status, which is usually unintended and does not reduce litigation risk exposure.

    Appointing the Fiduciary Committee the Right Way

    Plan sponsors should begin with a clear intention concerning the purpose and role of their fiduciary committee. In most cases, the committee is designated as the ERISA-named fiduciary and is responsible for ongoing plan administration. The stakes are high, as fiduciary liability is personal liability. Remedies for breaches of fiduciary duties can include restoration of losses, disgorgement of profits or other equitable relief, such as removal of the fiduciary. Therefore, participation in a fiduciary committee should not be taken lightly. Comprehensive, periodic and well-documented fiduciary training for committee members is essential.

    Action Items

    Plan sponsors should consider the following measures relative to their employee benefit plan fiduciary governance, particularly as they begin to consider the next steps for their health and welfare plans:

    • Formalize Committee Establishment: Conduct a formal vote to establish the fiduciary committee(s).
    • Ensure Proper Delegation: Formalize the delegation of fiduciary duties through board resolutions and committee charters, clearly establishing the purpose and role of the fiduciary committee(s), including the types of plans they will oversee.
    • Implement Duty to Monitor: Maintain oversight by requiring periodic reports from fiduciary committees to the board for any delegated responsibilities.
    • Provide Comprehensive Training: Conduct comprehensive, periodic and well-documented fiduciary training for all committee members to ensure they are well-informed and capable of fulfilling their duties.
    • Obtain ERISA Fiduciary Insurance: Secure ERISA fiduciary insurance in addition to an ERISA fidelity bond to provide comprehensive coverage for fiduciary responsibilities.
    • Avoid Conflicts of Interest: Ensure that individuals without substantive knowledge of employee benefit plans do not have significant fiduciary responsibilities, particularly senior managers and board members.
    • Document Fiduciary Actions: Maintain thorough documentation, such as meeting minutes, of all fiduciary actions, decisions and training to provide a clear record of compliance and diligence.
    • Evaluate Fiduciary Processes Regularly: Periodically review and evaluate fiduciary governance processes to ensure they remain effective, compliant and aligned with best practices.
    Authors

    Jacob M. Mattinson

    Partner

    Chicago

    Sarah G. Raaii

    Partner

    Chicago

    More insights

  • ASTP Proposes Certification Criteria for Patient, Payer and Provider APIs

    ASTP Proposes Certification Criteria for Patient, Payer and Provider APIs

    CLIENT ALERT / INTEROPERABILITY

    ASTP Proposes Certification Criteria for Patient, Payer and Provider APIs

    August 8, 2024

    Read time: 11 min

    Key takeaways
    Overview

    On August 5, 2024, the US Department of Health and Human Services (HHS) Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) published the Health Data, Technology, and Interoperability: Patient Engagement, Information Sharing, and Public Health Interoperability (HTI-2) Proposed Rule in the Federal Register as part of its continued focus on improving information sharing among health care stakeholders through the Health IT Certification Program.

    This On the Subject discusses the proposals related to payer, provider and patient application programming interfaces (APIs). For information on the proposed rule’s information blocking provisions, see our separate On the Subject. We will also release a publication summarizing the rule’s Trusted Exchange Framework and Common Agreement proposals.

    The deadline for submitting comments to ASTP regarding the proposed rule is October 4, 2024, at 5:00 pm EDT.

    In depth

    Key Proposed Changes to the Certified API Requirements

    • The proposed rule outlines a new set of certification criteria focused on facilitating the exchange of clinical and coverage information, drug formulary information and prior authorization information among patients, providers and payers.
    • Health information technology (IT) certified to these criteria includes requirements for specific Implementation Guides (IGs) that were not previously outlined in related rulemaking by the Centers for Medicare & Medicaid Services (CMS).

    Intersection With CMS Rulemaking

    CMS previously issued two separate final rules that leverage APIs to improve interoperability and data exchange across certain payers, providers and patients. The 2020 CMS Interoperability and Patient Access Final Rule required impacted payers to implement and maintain a patient access API to facilitate patient access to claims, encounter, clinical and other data. That same rule required impacted payers to implement payer-to-payer data exchange, but CMS subsequently subjected that requirement to enforcement discretion. The rule also required payers to adopt a provider directory API. The 2024 CMS Interoperability and Prior Authorization Final Rule then expanded on the 2020 rule and required implementation of three additional APIs: a provider access API, a payer-to-payer API and a prior authorization API.

    These CMS rules apply to a subset of payers, specifically Medicare Advantage organizations, Medicaid fee-for-service (FFS) programs, Medicaid managed care plans, Children’s Health Insurance Program (CHIP) FFS programs, CHIP managed care entities and qualified health plan issuers on the federally facilitated exchanges. Although compliance dates vary based on payer type, impacted payers must generally implement the API provisions beginning on January 1, 2027.

    While CMS required payers to comply with certain technical standards in the two final rules, the agency merely recommended compliance with relevant IGs that provide more specificity. CMS decided to provide more flexibility, initially, and to allow the IGs to be voluntarily updated as future improvements are made. However, CMS also reserved the right to make compliance with the more detailed IGs mandatory in future rulemaking.

    More information on the CMS rules is available here, and the CMS-recommended IGs for each API type are detailed in the chart below.

    API Name CMS Recommended Supporting IGs
    Patient Access API
    Provider Access API
    • See IGs for patient access API
    Payer-to-Payer API
    • See IGs for patient access API
    Provider Directory API
    Documentation Requirements Lookup Service API
    Prior Authorization Support (PAS) API
    Bulk Data

    API Certification Proposals

    ASTP’s proposed rule outlines a set of health IT certification criteria for the patient, provider, payer and other APIs. ASTP notes in the proposed rule that although CMS only recommended use of certain IGs, ASTP would require certain IGs as part of its health IT certification criteria. While ASTP would require these IGs for health IT certification purposes, it cannot mandate that developers obtain certification for their API technology or that impacted payers covered under the CMS rules use certified technology. Certification is voluntary, but those seeking to be certified would need to comply with the HT1-2 proposals, if finalized, including the required IGs. It is also possible that CMS, in future rulemaking, could require impacted payers to use certified technology to meet the API requirements. The new API certification criteria would be included in the condition and maintenance of certification requirements.

    The proposed rule outlines the proposed certification criteria for each API as follows:

    • Patient Access API: The certification criteria specify requirements to enable patients to access health and administrative information using an application of their choice. The proposal would require certified health IT modules to enable patient access to payer drug formulary information and to patient clinical, coverage and claims information, including provider remittances and enrollee cost-sharing.
    • Provider Access API: The proposed rule outlines “client” and “server” certification criteria to support provider access to payer information. This information would facilitate access to patient clinical, coverage and claims information, including information about patient encounters; dates of service; diagnoses; laboratory results; information from admit, discharge and transfer messages; information received from immunization registries; and information related to medications from pharmacy networks.
    • Payer-to-Payer API: The proposed rule would support the electronic exchange of data when a patient switches insurance plans. The criteria would facilitate sharing of payer claims and encounter data (excluding provider remittances and patient cost-sharing information).
    • Prior Authorization API: The proposed rule outlines certification criteria for payers and providers to conduct electronic prior authorization. Technology certified to these criteria would support the ability to request and populate prior authorization templates and to submit and respond to prior authorization requests.
    • Provider Directory API: The proposed rule specifies requirements for health IT that payers can use to publish information regarding the providers that participate in their networks. Technology certified under these criteria would help patients understand which providers, facilities and pharmacies are covered by their current (or future) health plan.

    Action Items and Next Steps

    Impacted payers generally have until January 1, 2027, to adopt the previously finalized CMS API requirements. While not mandatory, the additional certification criteria included in the ASTP proposed rule provide more detail on how to implement and operationalize those requirements for certain health IT modules seeking certification. Based on prior experience, payers likely will have to invest significant time and effort in developing the technology, policies and practices required to meet CMS’s standards and to achieve certification under ASTP’s complementary criteria (including implementation of the IGs), if finalized. While other commercial payers are not covered under the CMS rules, they may also choose to implement these APIs and seek specific certifications to improve electronic data sharing.

    The McDermott Difference


    If you have questions about how the ASTP’s proposals would affect your organization if finalized, or if you would like assistance preparing comments to submit to ASTP, please contact any of the authors of this On the Subject or your McDermott lawyer.

    Authors

    James A. Cannatti III

    Partner

    Washington, DC

    Daniel F. Gottlieb

    Partner

    Chicago

    Jennifer S. Geetter

    Partner

    Washington, DC

    More insights

  • ASTP’s HTI-2 Proposed Rule Would Add and Expand Information Blocking Exceptions

    ASTP’s HTI-2 Proposed Rule Would Add and Expand Information Blocking Exceptions

    CLIENT ALERT / INFORMATION BLOCKING

    ASTP’s HTI-2 Proposed Rule Would Add and Expand Information Blocking Exceptions

    August 7, 2024

    Read time: 26 min

    Key takeaways
    Overview

    On August 5, 2024, the US Department of Health and Human Services (HHS) Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology (ASTP) published the Health Data, Technology, and Interoperability: Patient Engagement, Information Sharing, and Public Health Interoperability (HTI-2) Proposed Rule in the Federal Register to update its Health IT Certification Program (Certification Program) requirements and amend the information blocking regulations that ASTP issued under the 21st Century Cures Act.

    This On the Subject discusses the proposed changes to the information blocking regulations, which include new exceptions intended to offer regulated actors certainty that they can restrict information sharing in certain circumstances where the restrictions would protect patients’ access to care or honor an information sharing partner’s preferences for how much electronic health information (EHI) is made available to the partner, when and under what circumstances. ASTP also proposed adoption of certain certification criteria and standards for payer-focused application programing interfaces (APIs). For a discussion of those proposals, see our separate On the Subject.

    The deadline for submitting comments to ASTP regarding the proposed rule is October 4, 2024, at 5:00 pm EDT.

    For more background on these issues, see our previous articles:

    • A Special Report on ASTP’s final information blocking regulations adopted in 2020.
    • An On the Subject about ASTP’s amendments to those regulations as part of the Health Data, Technology, and Interoperability: Certification Program Updates, Algorithm Transparency, and Information Sharing (HTI-1) final rule.
    In depth

    Key Proposed Changes to the Information Blocking Regulations

    • The proposed rule would codify examples of certain practices that ASTP believes constitute an interference with EHI and may need to meet an exception to the information blocking prohibition.
    • The proposed new protecting care access exception would allow actors meeting certain conditions to limit EHI sharing to reduce a risk of exposing patients, providers or persons who facilitate reproductive health care to legal action based on the mere fact that they sought, obtained, provided or facilitated lawful reproductive health care.
    • The proposed new requestor preferences exception would permit an actor to tailor access, exchange or use of EHI to a requestor’s preference if the practice meets certain conditions.

    Information Blocking Prohibition

    Under the current regulations, information blocking means a practice by a health IT developer of certified health IT (certified health IT developer), health information network or health information exchange (HIN/HIE), or health care provider (collectively, actors) that, except as required by law or covered by an exception adopted by ASTP, is likely to interfere with access, exchange or use of EHI, and:

    • If conducted by a certified health IT developer or HIN/HIE, is a practice that such certified health IT developer or HIN/HIE knows, or should know, is likely tointerfere with, prevent or materially discourage access, exchange or use of EHI.
    • If conducted by a health care provider, is a practice that the provider knows is unreasonable and is likely to interfere with, prevent or materially discourage access, exchange or use of EHI.

    Interference

    The current information blocking regulations define “interfere with” or “interference” to mean “to prevent, materially discourage, or otherwise inhibit.” The proposed rule would add a new section to codify a nonexclusive list of specific practices that ASTP believes constitute interference for purposes of the information blocking prohibition. ASTP has previously identified practices that it believes may interfere with access, exchange or use of EHI in the form of Frequently Asked Questions.

    ASTP proposes to codify the following practices as interference:

    • Delay on new access. Delaying patient access to new EHI, such as diagnostic test results, so the actor’s clinicians or other representatives can review the EHI.
    • Portal access. Delaying patient access to EHI in a portal when the actor has the EHI and the actor’s system has the technical capability to support automated access, exchange or use of the EHI via the portal.
    • API access. Delaying the access, exchange or use of EHI to or by a third-party app designated and authorized by the patient, when there is a deployed API able to support the access, exchange or use of the EHI.
    • Non-standard implementation. Implementing health information technology in ways that are likely to restrict access, exchange or use of EHI with respect to exporting EHI, including exports for transitioning between health IT systems.
    • Contract provisions. Negotiating or enforcing a contract provision that restricts or limits otherwise lawful access, exchange or use of EHI.
    • Noncompete provisions in agreements. Negotiating or enforcing a clause in any agreement that prevents or restricts an employee (other than the actor’s employees), a contractor or a contractor’s employee who accesses, exchanges or uses the EHI in the actor’s health IT from accessing, exchanging or using EHI in other health IT in order to design, develop or upgrade such other health IT. This proposal is intended to address conditions on access to EHI in an actor’s health IT that are unrelated to security or privacy laws and are anticompetitive.
    • Manner or content requested. Improperly encouraging or inducing requestors to limit the scope, manner or timing of EHI requested for access, exchange or use.
    • Medical images. Requiring that access, exchange or use of any medical images (e.g., x-rays) occur by exchanging physical copies or copies on physical media (e.g., thumb drive) when the actor and the requestor possess the technical capability to access, exchange or use the images through fully electronic means.
    • Omissions:
      • Not exchanging EHI under circumstances in which such exchange is lawful.
      • Not making EHI available for lawful use.
      • Not complying with another valid law enforceable against the actor that requires access, exchange or use of EHI.
      • A certified API developer (as defined in the certification program regulations) failing to publish API discovery details as required by the maintenance of certification requirements.
      • A health care provider or other API information source (as defined in the certification program regulations) failing to disclose to the certified API developer the information necessary for the certified API developer to publish the API discovery details required by the certification program regulations.

    ASTP also identifies practices that it believes are unlikely to interfere with the access, exchange and use of EHI in the proposed rule preamble, but not in its proposed amendments to the information blocking regulations. For example, ASTP states that it would unlikely be an interference for qualified health information networks, participants or sub-participants to comply with required provisions of the common agreement and the incorporated terms of participation and standard operating procedures, respectively.

    Amended Information Blocking Exceptions

    ASTP proposes to revise certain existing information blocking exceptions.

    Privacy Exception

    The privacy exception under the current information blocking regulations provides that an actor’s denial of a request to access, exchange or use EHI to protect an individual’s privacy is not information blocking when the denial satisfies at least one of the privacy exception’s sub-exceptions. ASTP proposes to amend certain of the sub-exceptions:

    • Unreviewable Grounds Sub-Exception. One sub-exception allows denial of an individual’s request for EHI consistent with the “unreviewable grounds” for denial of access under the HIPAA Privacy Rule’s right to access protected health information in a designated record set. The unreviewable grounds are intended to address certain public policy objectives separate from privacy, such as when a health care provider provides treatment in the course of clinical research. ASTP proposes to broaden the applicability of the sub-exception so that it is available to any actor responding to a request for EHI where the circumstances for unreviewable grounds apply, and not just to actors that are also HIPAA covered entities or business associates.
    • Individual’s Request Not to Share EHI Sub-Exception. Another sub-exception permits an actor to deny a request for access, exchange or use of EHI to respect an individual’s request not to share EHI if certain requirements are met. ASTP proposes to amend the existing sub-exception so that any practice that meets the requirements of the sub-exception would not be considered information blocking even if no law requires the actor to disclose EHI against the individual’s expressed wishes.

    Infeasibility Exception

    The current information blocking regulations’ infeasibility exception provides that a denial of a request to access, exchange or use EHI due to the infeasibility of the request is not information blocking when the denial meets one of the exception’s infeasibility conditions. The denial also must meet the timeframe of the exception’s responding to requests condition, which requires the actor to respond to the requestor in writing with the reasons why the request is infeasible within 10 business days of receipt of the request.

    ASTP proposes to revise certain infeasibility conditions and to make the responding to requests condition more flexible:

    • Segmentation Condition. The segmentation condition of the infeasibility exception allows an actor to deny a request to access, exchange or use EHI because the actor cannot unambiguously segment the requested EHI from other EHI that cannot be made available because of an individual’s preference, because the EHI cannot be made available by law or because the EHI may be withheld under the preventing harm exception to the information blocking prohibition. ASTP proposes to expand the segmentation condition to allow for denial of access when EHI cannot be segmented from EHI that may be withheld under the privacy exception or the proposed protecting care access exception discussed below.
    • Third Party Seeking Modification Use Condition. One of the current infeasibility exception conditions allows an actor to deny a request if the request is to enable use of EHI to modify EHI, provided that the request is not from a health care provider requesting such use from an actor that is its business associate. ASTP proposes to revise the condition so that it is unavailable to requests by any HIPAA covered entity (and not only HIPAA-covered health care providers) requesting a modification use from an actor that is its business associate. ASTP also proposes to extend the exclusion so that the third party seeking modification use condition would not apply where a health care provider that is not a HIPAA covered entity requests modification use from an actor that would be the provider’s business associate if the provider were a HIPAA covered entity.
    • Responding to Requests Condition. ASTP proposes to revise the responding to requests condition to offer actors a more flexible response timeframe where the reasons for infeasibility are consistent with the infeasibility exception’s manner exception exhausted or infeasible under the circumstances conditions. Under the proposal, the actor could satisfy the responding to requests condition by:
      • Determining, without unnecessary delay and based on a reasonable assessment of the facts, that the requested access, exchange or use cannot be provided in accordance with the manner exception or is infeasible under the circumstances; and
      • Informing the requestor with a written response indicating the reason for infeasibility within 10 business days of the actor’s determination.

    According to ASTP, the revised condition would allow the actor, within 10 days of receiving a request, to initiate good-faith collaborative engagement with the requestor to discuss the potential infeasibility of the request as received and potentially feasible alternative ways to achieve EHI sharing. When discussions and negotiations reach a result other than successful fulfillment of access, exchange or use of EHI for the requestor, the revised condition would require the actor to provide the requestor with a written response indicating the reason for infeasibility within 10 business days of the actor’s determination of infeasibility or the discontinuation of discussions.

    Proposed New Information Blocking Exceptions

    The proposed rule includes two new information blocking exceptions.

    Protecting Care Access

    The proposed protecting care access exception would, under specified conditions, allow actors to limit EHI sharing to reduce a risk of potentially exposing patients, providers or persons who facilitate care to legal action based on the mere fact that they sought, obtained, provided or facilitated lawful reproductive health care. The proposed exception is intended to address the changed legal landscape for patients seeking, and for health care providers providing, reproductive health care, resulting from the US Supreme Court’s decision in Dobbs v. Jackson Women’s Health Organization.

    Under the proposed exception, an actor’s practice to reduce potential exposure to legal action would not be information blocking when the practice satisfies the exception’s threshold condition and also satisfies either the exception’s patient protection condition or the care access condition.

    • Threshold Condition. To meet the threshold condition, a practice must meet the following requirements:
      • Good Faith Belief. The practice is undertaken based on the actor’s good faith belief that persons seeking, obtaining, providing or facilitating reproductive health care are at risk of being potentially exposed to legal action that could arise as a consequence of particular access, exchange or use of specific EHI, and that specific practices likely to interfere with such access, exchange or use of such EHI could reduce that risk.
      • Tailoring. The practice is no broader than necessary to reduce the risk of potential exposure to legal action that the actor in good faith believes could arise from the particular access, exchange or use of the specific EHI.
      • Implementation. The practice is implemented either consistent with an organizational policy or pursuant to a case-by-case determination meeting certain requirements.
    • Patient Protection Condition. When an actor implements a practice to reduce the patient’s risk of potential exposure to legal action, the practice must:
      • Affect only the access, exchange or use of specific EHI the actor in good faith believes could expose the patient to legal action because the EHI shows, or would carry a substantial risk of supporting a reasonable inference, that the patient obtained reproductive health care; inquired about or expressed an interest in seeking reproductive health care; or has any health conditions or history for which reproductive health care is often sought, obtained or medically indicated.
      • Be subject to nullification by an explicit request or directive from the patient that the access, exchange or use of the specific EHI occur despite the risks to the patient that the actor has identified.
    • Care Access Condition. When implemented to reduce the risk of potential exposure to legal action for one or more licensed health care professionals, other health care providers, or other persons involved in providing or facilitating reproductive health care that is lawful under the circumstances in which such health care is provided, the practice must affect only access, exchange or use of specific EHI that the actor believes could expose care providers and facilitators to legal action because the information shows, or would carry a substantial risk of supporting a reasonable inference, that they provide or facilitate, or have provided or facilitated, reproductive health care.

    Requestor Preferences Exception

    The proposed requestor preferences exception permits an actor to tailor access, exchange or use of EHI to a requestor’s preference if the practice meets the following conditions:

    • Request. A requestor, without any improper encouragement or inducement by the actor, requests in writing that the actor:
      • Limit the scope of EHI made available for access, exchange or use by the requestor;
      • Delay provision of access, exchange or use by the requestor of particular EHI health information until a condition specified by the requestor (such as passage of a particular event or completion of an action) has been met; or
      • Delay provision of access, exchange or use by the requestor of particular EHI for a specified period of time.
    • Implementation. The actor’s practice must be tailored to the specific request and implemented in a consistent and nondiscriminatory manner.
    • Transparency. The actor must explain to the requestor in plain language, verbally or in writing, what tailoring the actor will implement. The actor also must notify, verbally or in writing, any requestors of changes in the actor’s ability to maintain tailoring. To satisfy this condition, the actor must, at a minimum:
      • Explain to the requestor what tailoring the actor will implement and how that will impact what EHI will be available to the requestor and when, or under what conditions EHI will be available to the requestor;
      • Upon experiencing any change in operational status, technical capabilities or other circumstances affecting the actor’s ability or willingness to maintain particular tailoring of EHI, make reasonable efforts to promptly notify each requestor for which the actor had implemented the affected tailoring; and
      • Contemporaneously document in writing any verbal explanation or notice to the requestor.
    • Reduction or Removal. An actor must act on any subsequent request from the requestor who previously requested scope, condition or timing tailoring of the requestor’s EHI access, exchange or use to reduce or remove restrictions as promptly as feasible.

    The McDermott Difference


    If you have questions about how the ASTP’s proposals would affect your organization if finalized, or if you would like assistance preparing comments to submit to ASTP, please contact any of the authors of this On the Subject or your regular McDermott lawyer.

    Authors

    Daniel F. Gottlieb

    Partner

    Chicago

    James A. Cannatti III

    Partner

    Washington, DC

    More insights

  • Anticipating the MHPAEA final regulations: A word about network composition

    Anticipating the MHPAEA final regulations: A word about network composition

    ARTICLE

    Anticipating the MHPAEA final regulations: A word about network composition

    August 6, 2024

    Read time: 6 min

    If our trade and industry sources have it right, we could see final regulations implementing the Mental Health Parity and Addiction Equity Act (MHPAEA), as most recently amended by the Consolidated Appropriations Act, 2021 (CAA), any day now. Last week, we offered a wish list of things we would like to see modified or addressed once the rules become final.

    An August 1, 2024, letter from Viginia Foxx, chairwoman of the US House of Representatives Committee on Education and the Workforce, to the secretaries of the US Department of Health and Human Services (HHS) and the US Department of the Treasury (Treasury) and the acting secretary of the US Department of Labor (DOL) leads us to add one more item to our wish list. It relates to a subject that has been a major item of contention and the cause of considerable frustration in MHPAEA audits: network composition and adequacy.

    The CAA added a requirement that plans and issuers perform and document comparative analyses of the design and application of nonquantitative treatment limitations (NQTLs) on mental health and substance use disorder (MH/SUD) benefits and medical and surgical (M/S) benefits. Nothing in the CAA modifies prior law relating to network composition or adequacy, however. MHPAEA generally requires that the application of NQTLs on MH/SUD benefits “in operation” be comparable and no more stringent than on M/S benefits. In the case of an audit, the DOL has analyzed diverse types of outcomes data, such as denial or reimbursement rates.

    But – and this is critical – nothing in existing law requires comparability of outcomes. Indeed, the DOL’s self-compliance tool makes clear that disparate outcomes are not determinative of noncompliance, recognizing that the law requires only that the processes and standards used in applying the NQTL be comparable across MH/SUD and M/S benefits. Different outcomes can still be MHPAEA-compliant. An intervening FAQ (No. 7) suggests otherwise, saying that disparate outcomes raise a “red flag.” FAQs lack the force of law, however.

    The proposed rules upend current law by making differences in outcomes a strong indicator of noncompliance or, in the case of network composition, a conclusive determination of noncompliance. Chairwoman Foxx criticizes this approach, saying that “This [ ] suggests that approval or denial rates in either a MH/SUD or M/S context are indicative of appropriateness.” This is in her view a flawed assumption. She also claims that the DOL, HHS and Treasury (the Departments) have exceeded their statutory authority in the matter. The DOL is in our experience applying this rule on audit as though the proposed rule is the law.

    We express no opinion on whether the proposed rule comports with the statue. This is for the courts to decide. It’s no secret, however, that the Departments now face a higher bar in the wake of the US Supreme Court’s decision in Loper Bright Enterprises v. Raimondo (wherein the Court overruled the Chevron deference doctrine). We would prefer that, at a minimum, the final regulations not impose an automatic finding of noncompliance in the case of network composition. The better approach, in our view, is to allow plans the opportunity to explain any differences in relevant data between MH/SUD and M/S services.

    More insights

  • On the Stand With Peg Warner

    On the Stand With Peg Warner

    ARTICLE

    On the Stand With Peg Warner

    August 6, 2024

    Read time: 5 min

    Key takeaways
    Overview

    Peg Warner has tried over 50 cases spanning jury trials (including one that lasted nearly five months), bench trials and arbitration hearings. She has served as first-chair counsel in state and federal courts in over 30 jurisdictions.

    In this Q&A, Peg shares how English history influenced her career as a trial lawyer, why going to trial is like running a marathon and which of her many jury verdicts is one of her proudest moments.

    In depth

    Why did you become a trial lawyer?

    I thought that was the “real lawyer” approach. But in general, I became a lawyer because I was a double major in English history and English literature in college. I asked one of my professors, my mentor, if he thought I should pursue a PhD in English history or go to law school. He said, “I think your personality is more suited to be a lawyer.”

    And he was right from both an intellectual and personal standpoint. What I enjoy most about trial law is that it fits with the linear perspective I gained from studying history and writing.

    How do you prepare for each day when you’re at trial?

    I look at trials as marathons, not sprints, and I must listen to my body. I train and consider how I’m going to maintain my stamina, especially for a long trial. For example, I know how much sleep I need during a trial and when I need it.

    Preparation also depends on if I’m representing the plaintiff or the defendant. If I’m representing the plaintiff, it’s a very front-end exercise in that I need to do a lot of the work before the trial starts. If I’m representing the defendant, my work tends to focus on the cross-examination side, so I approach preparation differently.

    It is true what they say in law school – that trial work is 90% preparation and 10% presentation.

    What is one thing every trial lawyer should know about being in the courtroom?

    There are three things every lawyer should know.

    One, you’re always on. Whether you’re being observed by the jury, judge, the opposing side or your client, you are on. You and your witnesses must always be aware of that. And that scrutiny extends to how you present your workspace at counsel table, which you always want to keep organized so there’s nothing between you and the jury.

    Two, you need to painstakingly prepare for the first five minutes of cross-examination. The whole point of the process is to take control of the witness from the start.

    Three, I totally believe that you can win cases in your opening statement. So, my teams spend a lot of time on the opening’s graphics, substance and presentation.

    These are the things that I stress to any lawyer I work with on a trial, including the many from the Firm whom I’ve worked with since their younger days. As I reflect on my career, one of the most rewarding elements has been watching young lawyers become great trial lawyers in the well of a courtroom.

    What is the proudest moment of your career to date?

    It’s hard to pick just one!

    Six years ago, I tried a case that we ultimately won. Our client and lead witness was at the center of a commercial dispute. The work that our team did on the trial, coupled with our client’s testimony, helped her regain her self-respect, and the jury gave her back self-esteem. She had been told for many years that she didn’t know what she was doing, even though she was right.

    Winning that trial was a profound moment for her and certainly for me as her trial lawyer.

    What is one thing about being a trial lawyer that everyone may not know?

    Every decision that a client makes to try a case, let alone undertaking the actual trial, ultimately strengthens their relationship with their trial lawyer. Choosing to go to trial is a profoundly personal decision for the client, even if the client is the general counsel of a large corporation. To decide to face the crucible of trial – and then navigating it with a client – is what’s special about being a trial lawyer. The relationship between lawyer and client is unique.

    I am acutely cognizant of the fact that each client’s fate is in my hands. As lawyers, it is essential for us to be their zealous advocates in the courtroom.

    Authors

    Margaret H. Warner

    Partner

    Washington, DC

    More insights

  • Pay To Play Implications of VP Candidacy of Minnesota Governor Tim Walz

    Pay To Play Implications of VP Candidacy of Minnesota Governor Tim Walz

    ARTICLE / CLIENT ALERT

    Pay To Play Implications of VP Candidacy of Minnesota Governor Tim Walz

    August 6, 2024

    Read time: 2 min

    Key takeaways
    Overview

    Earlier today, Vice President Kamala Harris selected Minnesota Governor Tim Walz as her running mate. As governor, Walz serves as the Chair of the Minnesota State Board of Investment (SBI), which has authority with respect to investments by various Minnesota pension plans. Thus, any contribution to, or fundraising or solicitation on behalf of, the Harris/Walz campaign should be evaluated for implications under Rule 206(4)-5 of the Advisers Act (the “Pay to Play Rule”).

    For more information, see Schulte’s Pay to Play Rule refresher.

    In depth
    Authors
    More insights