Content Type: Article

  • “Gamification” Established Employment Relationship

    ARTICLE

    “Gamification” Established Employment Relationship

    December 2, 2020

    Read time: 2 min

    Key takeaways
    Overview

    The Federal Labor Court surprisingly decided that a “crowdworker” is an employee – the platform’s incentive system played a central role in this decision. A guest contribution from Dr. Philipp Schäuble and Franziska Leubner.

    In depth
    Authors
    More insights

  • Compulsory SARS-CoV-2 Vaccination for Employees in Germany?

    Compulsory SARS-CoV-2 Vaccination for Employees in Germany?

    ARTICLE / CLIENT ALERT

    Compulsory SARS-CoV-2 Vaccination for Employees in Germany?

    December 1, 2020

    Read time: 2 min

    Key takeaways
    Overview

    At least for the time being there are no plans to make vaccination compulsory in Germany – even though the legislator could in principle enact such a duty by means of the Infection Protection Act (Infektionsschutzgesetz) and has already made use of this possibility in other cas-es (e.g. measles).

    Also, employers cannot oblige employees to be vaccinated by means of their right to issue instructions. An instruction issued nevertheless would be ineffective under consideration of the constitutional protection of physical integrity and the general personal right.

    However, can the employer exercise its house right in such a way that it ties the admission to the company premises, e.g. to a vaccination certificate? This should only be possible if there are no less severe means to contain the risk of infection, such as remote work or hygiene measures. The personal rights of employees must be taken into consideration in a sufficient manner in any case.

    In addition, such a regulation would in principle affect the organizational conduct and the health protection, which is why the works council would have to participate in the decision before issuing it.

    Employers cannot introduce an obligation to vaccinate. Access restrictions will only be possible in exceptional cases and in compliance with the co-determination of the works council.

    In depth
    Authors
    More insights

  • Are Crowdworkers to Be Considered as Employees

    ARTICLE

    Are Crowdworkers to Be Considered as Employees

    November 23, 2020

    Read time: 2 min

    Key takeaways
    Overview

    Crowdworkers are people who work as freelancers for several clients. Their specialty is that they accept orders for the masses. But are they to be seen as employees at all?

    In depth
    Authors
    More insights

  • ESG Disclosure Looms Near | Requirements from March 2021

    ESG Disclosure Looms Near | Requirements from March 2021

    ARTICLE / CLIENT ALERT

    ESG Disclosure Looms Near | Requirements from March 2021

    December 1, 2020

    Read time: 2 min

    Key takeaways
    Overview

    The starting date for the EU regulation on sustainability transparency in the financial sector is approaching quickly. However, it has become clear that the very detailed level 2 provisions will not yet be in place by March 10, 2021. Following our earlier On the Subject which already explored this subject, we provide update on the to-dos for fund management companies. Read the full article in German here.

    In depth

    Das Inkrafttreten der EU-Offenlegungsverordnung zum 10. März 2021 rückt in greifbare Nähe. Mittlerweile ist klar, dass die Level 2-Entwürfe, mit denen die Verordnung EU-seitig umfangreich konkretisiert und faktisch verschärft werden soll, zu diesem Zeitpunkt noch nicht anwendbar sein werden. Nachfolgend geben wir ein Update zu unserem Newsletter vom 5. Oktoberund beleuchten die nun anstehenden Aufgaben für Kapitalverwaltungsgesellschaften

    Authors

    Frank Müller

    Partner

    Frankfurt

    More insights

  • Treasury Issues Advisories Related to Ransomware Attacks

    Treasury Issues Advisories Related to Ransomware Attacks

    ARTICLE / CLIENT ALERT

    Treasury Issues Advisories Related to Ransomware Attacks

    December 1, 2020

    Read time: 12 min

    Key takeaways
    Overview

    On Oct. 1, 2020, the U.S. Department of the Treasury’s Financial Crimes Enforcement Network (“FinCEN”) and Office of Foreign Assets Control (“OFAC”) each issued advisories on ransomware that, when taken together, make it more difficult for victims of such attacks to lawfully pay ransoms to regain access to hijacked systems and recover stolen data. The FinCEN advisory (“FinCEN Advisory”) discusses predominant trends, typologies and potential red flag indicators of ransomware and associated money laundering activities, and the related suspicious activity reporting requirements applicable to financial institutions. Importantly, it clarifies that institutions functioning as intermediaries between victims and cyber actors in the payment of ransoms, including digital forensics, incident response and cyber insurance companies, may be required to register with FinCEN as money services businesses (“MSBs”). The OFAC advisory (“OFAC Advisory,” and, together with the FinCEN Advisory, the “Advisories”) highlights the sanctions risks associated with paying, or facilitating payment of, ransoms to certain designated cybercriminals, and in so doing, leaves no doubt that ransomware payments from victims to cyber actors can violate OFAC regulations.

    Background

    The Advisories raise the familiar debate over “negotiating with terrorists.” On one hand, paying ransoms makes ransomware attacks more lucrative for cyber criminals and emboldens cyber criminals to perpetrate further attacks. On the other, paying ransoms may be the only way for victims to end the ransomware attack. On Oct. 13, 2020, the G-7 member nations warned that perpetrators of ransomware attacks might be state-sponsored or linked actors who might use the ransom funds for further illicit purposes, such as funding weapons of mass destruction.[1] Regulations that impose prohibitions, or at least cause delays, on paying ransoms inhibit what can be an economically efficient way for victims to respond to attacks and minimize the damage to their business continuity.

    According to the Advisories, the frequency of ransomware attacks has surged, as has the amount cybercriminals demand. The average ransom payment in December 2019 was $190,946, with several organizations reporting seven-figure payments.[2] Navigating a ransomware attack has become increasingly challenging and complex, as attackers deploy ever more sophisticated technologies and victims are often asked to pay ransoms in digital currency. The Advisories reinforce the importance of having plans in place to prevent and respond to ransomware attacks, in particular due to the heightened burden placed on victims, who often choose to pay ransoms to regain access to hijacked systems or recover stolen data.[3] Victims of ransomware schemes should review the Advisories closely and assess carefully whether paying ransom would violate the law.

    FinCEN Advisory Alerts to Common Trends, Typologies and Indicators of Ransomware Attacks

    Financial institutions are often involved in the processing of ransomware payments — a multi-step process that may include at least one depository institution and one or more MSBs — given that ransom demand payments are usually requested to be paid in convertible virtual currency (“CVC”), such as Bitcoin (“BTC”). The ransomware victim will often need to exchange fiat currency held at a bank for CVC through a MSB that operates as a CVC exchange by purchasing from the MSB the type and amount of CVC that the cybercriminal demands.

    Further, certain institutions, including digital forensics and incident response companies (“DFIRs”), and cyber insurance companies (“CICs”), might function as an intermediary by facilitating the conversion of payments to CVC and paying the ransom demanded by a cybercriminal. Entities engaged in such transactions might be required to register as MSBs with FinCEN, subjecting them to certain Bank Secrecy Act obligations, including the obligation to file a suspicious activity report (“SAR”).

    Additionally, FinCEN warns the public and financial institutions of the increasingly complex and sophisticated schemes of ransomware attacks. Cybercriminals often use common tactics, including phishing schemes, to infiltrate a victim’s systems. Employee training and institutional preparedness in the case of a cyber-attack is the best protection from a ransom scheme. FinCEN identifies the following types of schemes:

    • Big Game Hunting Schemes. Selective targeting of larger enterprises to demand bigger payouts.
    • Ransomware Criminals Forming Partnerships and Sharing Resources. Sharing resources to enhance the effectiveness of ransomware attacks, such as ransomware exploit kits that come with ready-made malicious codes and tools (which are offered for purchase or free) and forming partnerships to share advice, code, trends, techniques and illegally obtained information over shared platforms.
    • “Double Extortion” Schemes. Removing sensitive data from the targeted networks, encrypting the system files and demanding ransom. The criminals then threaten to publish or sell the stolen data if the victim fails to pay the ransom.
    • Use of Anonymity-Enhanced Cryptocurrencies (“AECs”). Requiring ransomware payments to be denominated in CVC such as BTC, or in AECs that reduce the transparency of CVC payment flows through anonymizing features, such as mixing and cryptographic enhancements. Some ransomware operators have even offered discounted rates to victims who pay their ransoms in AECs.[4]
    • Use of “Fileless” Ransomware. Sophisticated tool that can be challenging to detect because the malicious code is written into the computer’s memory rather than into a file on a hard drive, which allows attackers to circumvent off-the-shelf antivirus and malware defenses.[5]

    Additionally, FinCEN warns that institutions should be alert for the following “red flags” which may indicate a ransomware-related scheme:

    1. IT enterprise activity is connected to cyber indicators that have been associated with possible ransomware activity or cyber threat actors known to perpetrate ransomware schemes. Malicious cyber activity may be evident in system log files, network traffic or file information.
    2. When opening a new account or during other interactions with the financial institution, a customer provides information that a payment is in response to a ransomware incident.
    3. A customer’s CVC address, or an address with which a customer conducts transactions, appears on open sources, or commercial or government analyses have linked those addresses to ransomware strains, payments or related activity.
    4. A transaction occurs between an organization, especially an organization from a sector at high risk for targeting by ransomware (e.g., government, financial, educational, healthcare), and a DFIR or CIC, especially one known to facilitate ransomware payments.
    5. A DFIR or CIC customer receives funds from a customer company and shortly after receipt of funds sends equivalent amounts to a CVC exchange.
    6. A customer shows limited knowledge of CVC during onboarding or via other interactions with the financial institution, yet inquires about or purchases CVC (particularly if in a large amount or rush requests), which may indicate the customer is a victim of ransomware.
    7. A DFIR, CIC or other company that has no or limited history of CVC transactions sends a large CVC transaction, particularly if outside a company’s normal business practices.
    8. A customer that has not identified itself to the CVC exchanger, or registered with FinCEN as a money transmitter, appears to be using the liquidity provided by the exchange to execute large numbers of offsetting transactions between various CVCs, which may indicate that the customer is acting as an unregistered MSB.
    9. A customer uses a CVC exchanger or foreign-located MSB in a high-risk jurisdiction lacking, or known to have inadequate, AML/CFT regulations for CVC entities.
    10. A customer initiates multiple rapid trades between multiple CVCs, especially AECs, with no apparent related purpose, which may be indicative of attempts to break the chain of custody on the respective blockchains or further obfuscate the transaction.[6]

    The FinCEN Advisory reminds each financial institution that it might be required to file a SAR “when dealing with an incident of ransomware conducted by, at, or through the financial institution”[7] and that such SAR must incorporate all relevant information, which might include “relevant email addresses, Internet Protocol (IP) addresses with their respective timestamps, login information with location and timestamps, virtual currency wallet addresses, mobile device information (such as device International Mobile Equipment Identity (IMEI) numbers), malware hashes, malicious domains and descriptions and timing of suspicious electronic communications.”[8] FinCEN requests that financial institutions reference the Advisory on the SAR by including the key term “CYBER-FIN-2020-A006” in the SAR notes field and narrative section. In addition, financial institutions should select the suspicious activity type “cyber-event” in SAR field 42 and note the term “ransomware” in SAR field 42z.  

    The FinCEN Advisory also clarifies that information sharing among financial institutions pursuant to section 314(b) of the USA PATRIOT Act may be permissible for information related to ransomware, as the specified unlawful activities listed in 18 U.S.C. §§ 1956 and 1957 include an array of fraudulent and other criminal activities, including extortion and computer fraud and abuse.

    OFAC Advisory Warns of Sanctions Violations for Direct Payments and Facilitation of Payments to Cybercriminals

    OFAC has designated, and will continue to designate, malicious cyber actors under its cyber-related sanctions programs and other sanctions programs, and others “who materially assist, sponsor, or provide financial, material, or technological support for these activities.”[9] The OFAC Advisory provides several notable examples of ransomware and ransomware variants, such as Cryptolocker, SamSam and WannaCry 2.0, and points out the designated individuals and entities involved in such ransomware. OFAC warns that payments to such malicious actors can be used to “fund activities adverse to national security and foreign policy objectives.”

    The OFAC Advisory makes clear that OFAC will impose sanctions on U.S. persons who engage in transactions with individuals and entities involved in ransomware that have been designated by OFAC and appear on OFAC’s Specifically Designated Nationals and Blocked Persons List (“SDN”), and those covered by country or region sanctions. Additionally, OFAC cautions that a U.S. person need not know that the recipient of payment has been designated, stating that civil penalties may be imposed for “sanctions violations based on strict liability, meaning that a person subject to U.S. jurisdiction may be held civilly liable even if it did not know or have reason to know it was engaging in a transaction with a person that is prohibited under sanctions laws and regulations administered by OFAC.”[10] This poses a significant risk when paying a ransom, as cybercriminals often disguise their identities when demanding payment, making it nearly impossible to determine whether a recipient is prohibited.

    The OFAC Advisory reminds us that under its Economic Sanctions Enforcement Guidelines, OFAC provides information regarding the factors it considers when determining responses to violations.[11] Financial institutions should implement a risk-based compliance program that contemplates the potential for a ransomware payment to an SDN, as OFAC will consider this in its enforcement analysis. Additionally, an entity’s incident response and timely, self-initiated report of a ransomware attack to law enforcement might be considered when determining the appropriate sanctions.

    Notably, OFAC deters any questions on obtaining specific licenses by stating that: “license applications involving ransomware payments demanded as a result of malicious cyber-enabled activities will be reviewed by OFAC on a case-by-case basis with a presumption of denial.”[12]

    The OFAC Advisory also encourages victims of ransomware attacks to contact OFAC, as well as certain government agencies, in the event of an attack, and provides contact information for those government authorities, including OFAC, the U.S. Department of the Treasury’s Office of Cybersecurity and Critical Infrastructure Protection, the Federal Bureau of Investigation Cyber Task Force and the Cybersecurity and Infrastructure Security Agency. OFAC also recommends that victims of ransomware attacks consider whether they have additional regulatory obligations under FinCEN’s regulation.

    Conclusion

    The Advisories make clear that victims of ransomware attacks must reconsider making payments to cybercriminals, as doing so may mean that in some cases cyber victims may become the subject of a SAR filed with FinCEN or could be fined or prosecuted for paying ransoms. With the increased enforcement of sanctions for ransom payments, victims of ransomware attacks can no longer determine that the cost of paying a cybercriminal outweighs the risk of disruption to business without determining first whether the cybercriminal constitutes a prohibited counterparty and whether there are downstream consequences for payment of such ransom. Therefore, companies in the financial services sector must be ever more vigilant in identifying cybercrime attempts and preparing for the event of a cyberattack.

    Authored by Edward H. Sadtler, Betty Santangelo, Melissa G.R. Goldstein, Kelly Koscuiszka and Jaclyn N. Malmed.

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


    [1] “Econ Chiefs Urge Ransomware Victims To Report Payoffs,” Law360, Oct. 13, 2020, available here.

    [2] “Ransomware Attacks Grow, Crippling Cities and Businesses,” New York Times, Feb. 9, 2020, available here. (“The average payment to release files spiked to $84,116 in the last quarter of 2019, more than double what it was the previous quarter, according to data from Coveware, another security firm. In the last month of 2019, that jumped to $190,946, with several organizations facing ransom demands in the millions of dollars.”).

    [3] Our Aug. 17, 2020 Alert provides further information on the increasing risk of ransomware attacks, including steps that fund managers and financial institutions can take to increase preparedness for a cyber-attack.

    [4] The Attorney General’s Cyber Digital Task Force recently released a guide to cryptocurrency enforcement issues broadly. The guide warns that bad actors may exploit cryptocurrency to (1) engage in financial transactions associated with the commission of crimes, such as buying and selling drugs or weapons on the dark web, leasing servers to commit cybercrimes or soliciting funds to support terrorist activity; (2) engage in money laundering or shield otherwise legitimate activity from tax, reporting or other legal requirements; or (3) commit crimes directly implicating the cryptocurrency marketplace itself, such as stealing cryptocurrency from exchanges through hacking or using the promise of cryptocurrency to defraud unwitting investors. See U.S. Department of Justice, Cryptocurrency Enforcement Framework, Report of the Attorney General’s Cyber Digital Task Force (October 2020), available here.

    [5] Fin. Crimes Enf’t Network, Dept. of Treasury, Advisory on Ransomware and the Use of the Financial System to Facilitate Ransom Payments (2020), available here.  

    [6] Id.

    [7] Id.

    [8] Id.

    [9] Office of Foreign Assets Control, Dept. of Treasury, Advisory on Potential Sanctions Risk for Facilitating Ransomware Payments (2020), available here.

    [10] Id.

    [11] Our July 12, 2019 Alert provides additional information on OFAC’s guidance titled “A Framework for OFAC Compliance Commitments.”

    [12] Id.


    This communication is issued by Schulte Roth & Zabel LLP for informational purposes only and does not constitute legal advice or establish an attorney-client relationship. In some jurisdictions, this publication may be considered attorney advertising. ©2020 Schulte Roth & Zabel LLP.

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

    In depth
    Authors

    Betty Santangelo

    Counsel

    New York – 919 Third Avenue

    Melissa G.R. Goldstein

    Partner

    New York – 919 Third Avenue

    Kelly Koscuiszka

    Partner

    New York – 919 Third Avenue

    More insights

  • Top Trends for Energy Transition in 2021

    ARTICLE

    Top Trends for Energy Transition in 2021

    November 30, 2020

    Read time: 1 min

    Key takeaways
    Overview
    In depth
    Authors
    More insights

  • Art and AML Compliance: Beware of Snake Oil Merchants

    ARTICLE

    Art and AML Compliance: Beware of Snake Oil Merchants

    November 30, 2020

    Read time: 1 min

    Key takeaways
    Overview
    In depth
    Authors
    More insights

  • Digital Health as Healthcare Delivery: A Path to Transform Care Delivery Post-Pandemic

    ARTICLE

    Digital Health as Healthcare Delivery: A Path to Transform Care Delivery Post-Pandemic

    November 30, 2020

    Read time: 1 min

    Key takeaways
    Overview
    In depth
    Authors

    Jennifer S. Geetter

    Partner

    Washington, DC

    More insights

  • HHS Finalizes Sweeping Changes to Stark Law, Anti-Kickback Statute Regulations

    ARTICLE / CLIENT ALERT

    HHS Finalizes Sweeping Changes to Stark Law, Anti-Kickback Statute Regulations

    November 24, 2020

    Read time: 20 min

    Key takeaways
    Overview

    On November 20, 2020, the US Department of Health and Human Services (HHS) released final rules amending the regulations to the physician self-referral law (Stark Law) (Stark Rule) and the Anti-Kickback Statute (AKS) and Beneficiary Inducement Civil Monetary Penalty Law (CMPL) (collectively, AKS Rule). The Stark and AKS Rules finalize, with some modifications, most of the proposed changes promulgated by the Centers for Medicare and Medicaid Services (CMS) and the HHS Office of Inspector General (OIG), respectively, in October 2019.

    These final rules represent arguably the most significant changes to these regulations in the last decade. This On the Subject provides a high-level overview of key provisions in the Stark and AKS Rules. More in-depth analysis will follow at www.mwe.com/sprintready.

    In depth

    The Sprint

    HHS promulgated the Stark and AKS Rules as part of its “Regulatory Sprint to Coordinated Care,” which the Trump Administration launched in 2018 with the goal of reducing regulatory burden and incentivizing coordinated care. As part of this initiative, CMS and OIG began scrutinizing a variety of long-standing regulatory requirements and prohibitions to determine whether they unnecessarily hinder innovative arrangements that policymakers are otherwise hoping to see develop. The agencies formally sought public input on this topic by issuing requests for information in June and August 2018. Then, on October 9, 2019, CMS and OIG simultaneously proposed rules significantly modifying the Stark Law and the AKS. See (Stark Proposed Rule) and (AKS Proposed Rule). Stakeholders provided hundreds of comments to both agencies with regard to these proposals, and have eagerly awaited CMS’s and OIG’s final rules. After slightly more than a year, CMS and OIG have finalized most of their proposed revisions in substantially the same form as proposed.

    The Stark and AKS Rules reflect a coordinated effort between CMS and OIG to address various challenges to the transition to value-based care. Both agencies recognize that the two laws often operate in tandem, but their proposals also made clear that they are distinct and separate enforcement vehicles. Although commenters requested additional uniformity between the two regulatory schemes to ease compliance burden, as well as clarity with respect to value-based care arrangements, distinctions between the Stark and AKS rules remain. Thus, OIG’s new safe harbor regulations for value-based care arrangements are more restrictive than CMS’s, and both agencies state that the AKS acts as a “backstop” to protect against arrangements that meet a Stark Law exception but are nonetheless considered abusive.

    The Stark Rule

    The Stark Rule includes new exceptions designed to enable value-based care arrangements as well as changes that address some of the most challenging aspects of Stark Law compliance and issues often termed “technical non-compliance” by the industry. Among the most noteworthy changes to the Stark Law regulations are the following:

    • New Compensation Exceptions
      • Value-Based Care Exceptions. CMS finalized new exceptions for value-based care arrangements that satisfy a series of requirements, depending on the level of financial risk (full, meaningful downside and no risk) undertaken by the parties to the arrangement. The new value-based exceptions largely mirror the proposed rules, with minor changes often favorable to providers. Specifically, in the full financial risk exception, CMS extended the “pre-risk” period from six months as proposed, to 12 months, and in the meaningful downside financial risk exception, requires the physician be responsible to pay or forego no less than 10%, rather than paying 25% as proposed, of the value of the remuneration the physician receives under the value-based arrangement. The final version also builds in several additional guardrails around “no risk” arrangements, including updates to how “outcomes measures” (where applicable) are defined, selected and monitored. CMS permits both monetary and non-monetary remuneration between the parties and does not exclude any specific entities, such as laboratories or durable medical equipment, prosthetics, orthotics and supplies (DMEPOS) manufacturers, wholesalers or distributors, from participating in value-based care arrangements.
      • New Exception for Limited Remuneration to a Physician. CMS finalized a new exception to protect compensation not exceeding an aggregate of $5,000 per calendar year (increased from $3,500 as proposed), adjusted for inflation, to a physician for the provision of items and services without the need for a signed writing and compensation that is set in advance if certain conditions are met, including that the compensation does not exceed fair market value and is not determined in any manner that takes into account the volume or value of referrals or other business generated. The Stark Rule also permits the physician to provide the items or services in question through employees the physician hired for the purpose of performing the services, a wholly owned entity or locum tenens physicians. This new exception is one of the ways CMS expanded the avenues to protect otherwise potentially non-compliant space and equipment lease and timeshare arrangements, as well as a way to “gap fill” when the parties have not otherwise completed an agreement before beginning performance.
      • New Exception for Cybersecurity Technology and Related Services. CMS finalized a new exception to protect arrangements involving the donation of certain cybersecurity technology and related services, including certain cybersecurity hardware donations.
    • New Defined Terms
      • New or Modified Definitions for Key Stark Law Terms. In an effort to establish clear bright-line rules, CMS finalized new definitions of key concepts, including the “Big Three” that are elements of many Stark Law exceptions: “commercial reasonableness,” “fair market value,” and “takes into account the volume or value” of referrals or other business generated. Specific changes include:
        • With regard to fair market value, CMS generally attempted to return to the statutory definition of fair market value and better align fair market value with the “general market value” of a subject transaction, thus ostensibly allowing parties to consider more specific circumstances surrounding the particular arrangement than overly relying on the four corners of a salary survey. CMS notes that salary surveys can be a good “starting point” but that the fair market value for a particular physician may be higher or lower than the survey data. CMS confirms its policy that there is no predetermined salary percentage level that is per se acceptable or per se suspect. The new regulatory definition of “fair market value” provides for three separate definitions: a definition of general application, a definition applicable to the rental of equipment, and a definition applicable to the rental of office space.
        • CMS also endeavored to define, through the use of special rules, when a physician’s compensation takes into account the “volume or value” of the physician’s referrals or “other business generated.” CMS tackled the definition by delineating a “universe of circumstances under which compensation is considered to take into account the volume or value of referrals or other business generated between the parties.” Specifically, compensation “takes into account” the volume or value of referrals or other business generated if the compensation formula includes referrals or other business generated as a variable, resulting in an increase or decrease in compensation that positively correlates to the number or value of referrals or other business generated. If the methodology used to determine the physician’s compensation or the payment from the physician does not fall squarely within the defined circumstances, the compensation does not take into account the volume or value of the physician’s referrals or other business generated by the physician, for purposes of the Stark Law. CMS affirmed that an association between personally performed physician services and designated health services (DHS) furnished by an entity does not convert compensation tied solely to the physician’s personal productivity into compensation that takes into account the volume or value of a physician’s referrals to the entity or the volume or value of other business generated by the physician for the entity. The volume/value change arguably may have the greatest impact on physician compensation structures for many organizations, from health systems to group practices.
        • CMS defined the term “commercially reasonable” in regulatory text. Specifically, “commercially reasonable” means that the particular arrangement furthers a legitimate business purpose of the parties to the arrangement and is sensible, considering the characteristics of the parties, including their size, type, scope and specialty. The definition, among other things, appears crafted to provide ammunition for defense of qui tam suits predicated on a lack of commercial reasonableness solely because an arrangement with a physician was not profitable. CMS included a statement in the regulatory definition that an arrangement may be commercially reasonable even if it does not result in profit for one or more of the parties.
      • DHS Definitional Change. CMS modified the definition of DHS to make clear that an inpatient hospital service is only DHS if the furnishing of the service affects the amount of Medicare payment under the inpatient prospective payment systems for acute care hospitals, inpatient rehabilitation facilities, inpatient psychiatric facilities and long-term care hospitals. This change has the potential to dramatically reduce the number of hospital claims that may be tainted by a prohibited financial relationship between a hospital and a physician where the physician is not the admitting physician. Notably, however, CMS declined to expand the modified definition to outpatient hospital services.
    • Other Regulatory Modifications
      • Clarification of “Set in Advance.” CMS finalized guidance making clear that compensation may be set in advance, even if it is not set out in writing before the furnishing of items or services. To this end, CMS confirmed that the special rule at § 411.354(d)(1) is a “deeming” provision that parties can utilize to ensure compensation will be considered “set in advance.” CMS also finalized requirements for arrangements where the compensation (or formula for determining the compensation) is modified during the course of the arrangement. Specifically, the new regulation related to modifying compensation terms during the course of an arrangement requires that the modified compensation (or formula for determining compensation) is set out in writing before the furnishing of items or services for which the modified compensation is to be paid, and it specifically provides that parties do not have 90 days to reduce the modified compensation terms to writing.
      • Clarifications to “Group Practice” Requirements. CMS finalized clarifications to the regulations defining a “group practice” for purposes of the Stark Law, including revisions that make clear that group practices may not use DHS-specific pods for purposes of distributing DHS profits. While the profits from all DHS of any component of the group that consists of at least five physicians (which may include all physicians in the group) must be aggregated before distribution, CMS clarified that a group practice may utilize different distribution methodologies to distribute shares of the overall profits from all DHS of each of its components of at least five physicians, provided that the distribution to any physician is not directly related to the volume or value of the physician’s referrals and the same methodology is used for all the physicians included in their component. As noted below, CMS delayed the effective date for this portion of the rule to January 1, 2022, to give physician practices additional time to adjust their compensation methodologies.
      • Modifications to Various Compensation Exceptions. CMS finalized a series of modifications to various compensation exceptions, including the space and equipment lease exceptions (to clarify that the lessor is the only party that must be excluded from using the space or equipment for purposes of exclusive use), recruitment exception (to eliminate the requirement that the practice sign the writing if the practice receives no financial benefit under the agreement), fair market value exception (which can be used for the rental of office space) and others. Most, though not all, of these modifications will likely liberalize the applicability of these exceptions to provider compensation arrangements. Unlike its approach with other exceptions, CMS declined to finalize its proposed modification to the fair market value exception that would have removed a requirement that the arrangement otherwise comply with the AKS. CMS acknowledged that since this exception may now be available to protect lease arrangements, the AKS requirement should be retained as an additional guard rail against “sham leases.”
      • Temporary Non-Compliance. CMS finalized its proposal to expand the 90-day grace period for signature requirements to the requirement for a written agreement.
      • Period of Disallowance. CMS finalized its proposal to delete the goal posts for when an entity would know the period of disallowance has ended. CMS also finalized additional guidance surrounding a party’s ability to “cure” non-compliance in ongoing arrangements in certain circumstances, in order to avoid triggering a period of disallowance under the Stark Law. CMS also created a special rule that allows parties to “reconcile discrepancies” for compensation arrangements within 90 days of termination of the arrangement.
      • Limiting the Applicability of Isolated Financial Transaction Exception. CMS finalized changes to the Stark regulations clarifying that CMS does not consider the isolated financial transaction exception to apply to payments for multiple services provided over an extended period of time, even if there is only a single payment for all the services. However, CMS confirmed that this exception is available to cover the forgiveness of an amount owed in settlement of a bona fide dispute, if certain conditions are met, including that the amount is fair market value and not determined in a manner that takes into account the volume or value of referrals or other business generated.
      • Revitalization of Payments by a Physician Exception. Currently, the Payments by a Physician Exception is of limited utility because it cannot be used if another exception applies. The final rule removes some of the restrictions by permitting use of the exception outside those arrangements specifically addressed by one of the Stark Law’s statutory exceptions codified at 42 CFR § 411.357(a)-(h).
      • Abandonment of Proposed Changes to Exception for Remuneration Unrelated to the Provision of DHS. CMS originally proposed to expand the exception’s limited application in the Stark Proposed Rule. Specifically, CMS proposed to clarify that remuneration from a hospital to a physician does not relate to the provision of DHS if the remuneration is for items or services that are not related to patient care services. However, citing certain commenters’ concerns regarding patient or program abuse, CMS decided not to finalize the proposed expansion.
      • Recalibrating the Special Rule for Directed Patient Referrals to Align with Broader Regulatory Changes. CMS also added new “directed referral” rules in an effort to further protect patient choice, professional medical judgment and managed care organization operations. CMS finalized its proposal to restructure the special rule surrounding directed referrals to include an affirmative requirement that a compensation arrangement meet the conditions of the special rule, which now include a provision that more explicitly addresses permitted compensation if an entity were to require referrals. Specifically, CMS stated that neither the existence of the compensation arrangement nor the amount of the compensation may be contingent on the number or value of the physician’s referrals to the particular provider, practitioner or supplier, but that the requirement to make referrals to a particular provider, practitioner or supplier may require that the physician refer an established percentage or ratio of the physician’s referrals to a particular provider, practitioner or supplier. CMS also included this affirmative requirement in many exceptions, including the new Limited Remuneration to a Physician exception.
      • Clarification for Electronic Health Records Items and Services Exception. CMS finalized many proposed changes to the exception, including modifying the timing of certain required physician contributions, permitting certain donations of replacement technology and removing the sunset provision, thereby making the exception permanent. Notably, however, CMS did not finalize its proposal to modify the provision addressing the concept of information blocking and instead removed that provision from the exception entirely.

    The AKS Rule
    The AKS Rule also finalizes many of OIG’s proposals that modify existing AKS safe harbors, create new AKS safe harbors and create a new CMPL exception. We have summarized the key changes below:

    • New AKS Safe Harbors
      • Value-Based Arrangements. OIG finalized three new safe harbors to protect certain payments among individuals and entities in a value-based arrangement. The three new safe harbors vary in terms of the type of remuneration that can be provided, the level of financial risk the parties assume (full, substantial downside and no risk), and the types of safeguards required to satisfy the safe harbor. As mentioned above, the value-based safe harbors are generally narrower than the Stark exceptions. For example, OIG finalized several restrictive requirements in the care coordination, or no-risk, safe harbor, including that the remuneration exchanged can be in-kind only and that participants must contribute 15% of the offeror’s costs or fair market value of the remuneration, and that coordination and management of the care of the target patient population must be at least one of the value-based purposes of the value-based enterprise, among other requirements. OIG also prohibits the following entities from being able to rely on the value-based safe harbors:
        • Pharmaceutical manufacturers, distributors and wholesalers
        • Pharmacy benefit managers
        • Laboratory companies
        • Compounding pharmacies
        • Medical device and supply distributors and wholesalers.
      • In recognition of the value that digital technology can have in achieving better care coordination, outcomes and reduced costs, OIG created a limited pathway for certain non-physician-owned medical device or supply manufacturers and entities or individuals that sell or rent DMEPOS (other than a pharmacy or a physician, provider or other entity that primarily furnishes services) to contribute digital health technology in reliance on the care coordination arrangements safe harbor.
      • Patient Engagement and Support. OIG finalized a safe harbor to protect furnishing certain tools and support to patients in order to improve quality, health outcomes and efficiency. Importantly, this safe harbor is only available for value-based enterprise participants. The remuneration can be in-kind only and is limited to a $500 annual cap, adjusted for inflation, among several other requirements.
      • CMS-Sponsored Models. OIG finalized a safe harbor to protect certain remuneration provided in connection with certain models sponsored by CMS, thereby reducing the need for HHS to issue individualized fraud and abuse waivers for each model.
      • Cybersecurity Technology and Services. OIG finalized a standalone protection for donations of cybersecurity technology and services, including certain cybersecurity hardware donations.
    • Modifications to Existing AKS Safe Harbors
      • Personal Services and Management Contracts Safe Harbor. OIG finalized a proposed modification to add greater flexibility by removing the part-time schedule requirement and the aggregate compensation set-in-advance requirement, which resulted in this safe harbor having limited practical use. OIG also created a new outcomes-based payments safe harbor to protect payments, outside of a value-based enterprise context, for the achievement of one or more legitimate outcomes measures that were selected based on clinical evidence or credible medical support to improve quality, reduce costs (but not solely internal costs) or both. These measures must be reassessed periodically. This safe harbor has the familiar fair market value, commercial reasonableness and volume/value requirements and excludes the entities deemed ineligible to take advantage of the value-based safe harbors, including medical device manufacturers and DMEPOS companies.
      • Local Transportation. OIG finalized its proposal to expand and modify mileage limits applicable to patient transportation in rural areas (expanded from 50 to 75 miles) and patient transportation from inpatient facilities post-discharge (removed all mileage limits). OIG did not extend safe harbor protection to transportation of patients to any location of their choice or for nonmedical purposes.
      • Electronic Health Records Items and Services Safe Harbor. Like CMS, OIG finalized many proposed changes to this safe harbor, including modifying the timing of certain required recipient contributions, permitting certain donations of replacement technology and removing the sunset provision. OIG also chose not to finalize its proposal to modify the provision addressing the concept of information blocking, and, consistent with CMS’s approach, instead removed that provision from the safe harbor entirely.
      • Warranties. OIG finalized its proposal to expand the warranty safe harbor to protect warranties covering a bundle of one or more items and related services. Specifically, the warranty safe harbor protects the remedies offered and given if the bundled items and services fail to perform as warranted. The bundled items and services must be reimbursed by the same federal healthcare program and the same federal healthcare program payment. Although manufacturers are not eligible for protection of value-based arrangements under the value-based safe harbors described above, the revised warranty safe harbor provides an avenue for manufacturers to offer value-based arrangements through structuring warranties to guaranty product performance in conjunction with services intended to enhance clinical effectiveness.
      • Accountable Care Organization (ACO) Beneficiary Incentive Programs. OIG codified the Bipartisan Budget Act of 2018 statutory exception for ACO Beneficiary Incentive programs for the Medicare Shared Savings Program.
    • New CMPL Exception
      • Telehealth for In-Home Dialysis. OIG finalized its proposal to interpret and incorporate the Bipartisan Budget Act of 2018 statutory exception for furnishing telehealth technologies to certain in-home dialysis patients.

    Implications of the Final Rules

    The vast majority of the provisions finalized by CMS and OIG are welcome updates that may present significant opportunities for new arrangements as the march toward value-based care continues, and even outside of the value-based context. It may take time, however, for stakeholders to become fully comfortable with the new value-based care exceptions and safe harbors. CMS recognized commenter leeriness toward the utility of the “full financial risk” exception given the amount of financial risk physicians are willing to accept. Notably, the differences between the Stark and AKS value-based care rules mean that organizations will likely continue to find themselves in a compliance “grey zone” where an arrangement satisfies a Stark Law exception—because it must—but is unable to meet an AKS safe harbor because the safe harbor is too restrictive.

    Outside of the value-based issues, the Stark and AKS Rules contain many clarifications and burden reduction measures. Stakeholders pleaded with CMS for additional definitional clarity surrounding the Big Three for years. Compliance professionals and healthcare lawyers will find welcome relief in many of CMS’s regulatory updates regarding “technical non-compliance.” With the addition of the special rules, guidance on curing arrangements and the new limited remuneration exception, many arrangements that previously necessitated a self-disclosure to CMS will no longer be non-compliant. The expansion of the AKS personal services and management contracts safe harbor will enable many common arrangements, such as per-hour payments, to finally fully comply with the safe harbor. The warranty safe harbor expansion likewise should encompass many beneficial and non-abusive arrangements that manufacturers offer to their customers as part of warrantying their increasingly sophisticated products.

    However, not everything in the final rules can be correctly classified as “burden reducing.” Certain changes to the Stark Law, such as the modification to “overall profits” in the Stark Law’s group practice definition, may require practices to change their current compensation methodologies. The clarification of the isolated transaction exception may require finding other compensation exceptions to protect financial relationships with referring physicians to ensure compliance when the final rule becomes effective. The AKS patient engagement safe harbor is only available for value-based enterprise participants, which may chill the activities of individual organizations to address patient needs and social determinants of health, especially during the pandemic and economic downturn.

    Effective Date Note

    The Stark and AKS Rules state an effective date of January 19, 2021, for most of the provisions, with the exception of certain changes to the definition of a “group practice,” which have an effective date of January 1, 2022. However, the official scheduled publication date of these rules is listed as December 2, 2020, which creates doubt under the Congressional Review Act about whether the rules can go into effect prior to the Biden Administration’s inauguration on January 20, 2021. Under the Act, the 60-day clock begins to tick upon the date of publication in the Federal Register, not the informal public display of a final rule. Typically, new administrations institute a hold on any regulation that has not gone into effect by inauguration day or shortly thereafter in order to have time to review those regulations. Given the largely technical and bipartisan nature of many of the issues in the Stark and AKS Rules, the rules may go into effect despite the change in administration. We will continue to monitor this issue.

    * * *

    McDermott will continue to provide additional thought leadership on the various elements of these final rules in the coming days and weeks. Please do not hesitate to contact your regular McDermott lawyer or any of the authors of this On the Subject if you have questions or need assistance with evaluating the impact of the Stark and AKS Rules on your current or future business arrangements.

    Authors

    James A. Cannatti III

    Partner

    Washington, DC

    Tony Maida

    Partner

    New York – One Vanderbilt Avenue

    Monica Wallace

    Partner

    Chicago

    More insights

  • Cal/OSHA Adopts Emergency COVID-19 Workplace Standards

    ARTICLE / CLIENT ALERT

    Cal/OSHA Adopts Emergency COVID-19 Workplace Standards

    November 24, 2020

    Read time: 8 min

    Key takeaways
    Overview

    On November 19, 2020, California’s Division of Occupational Safety and Health (Cal/OSHA) adopted emergency temporary standards on Coronavirus (COVID-19) prevention in the workforce, effective November 30, 2020, if approved as expected by the Office of Administrative Law. These temporary standards will require most California employers to implement a written COVID-19 prevention program meeting certain criteria, comply with training and testing requirements, and provide paid leave to those with work-related Covid-19 exposure. While many employers have already followed guidance issued by Cal/OSHA to minimize employees’ exposure to COVID-19, Cal/OSHA’s new requirements warrant immediate review of current policies to ensure compliance.

    In depth

    On November 19, 2020, California’s Division of Occupational Safety and Health (Cal/OSHA) adopted emergency temporary standards on Coronavirus (COVID-19) prevention in the workforce, effective November 30, 2020, if approved as expected by the Office of Administrative Law. These temporary standards will require most California employers to implement a written COVID-19 prevention program meeting certain criteria. While many employers have already followed guidance issued by Cal/OSHA to minimize employees’ exposure to COVID-19, Cal/OSHA’s new requirements warrant immediate review of current policies to ensure compliance. For any companies that have not yet created a written plan, the rules require implementation of a written policy.

    Who is covered?

    The new standards are applicable to all California employers, except for:

    • Employees who work from home
    • Places of employment with only one employee if the employee has no contact with others
    • Employers covered by Cal/OSHA’s Aerosol Transmissible Diseases Standard, which applies to work at certain healthcare facilities, laboratories and a limited number of other employers

    Healthcare employers excluded from this new standard include:

    • Hospitals
    • Skilled nursing facilities
    • Clinics, medical offices and other outpatient medical facilities
    • Facilities where high hazard procedures are performed
    • Home healthcare
    • Long-term healthcare facilities and hospices
    • Medical outreach services
    • Paramedic and emergency medical services, including when provided by firefighters and other emergency responders
    • Medical transport.

    What is required?

    The central requirement of the new emergency standards is that employers must prepare, implement and maintain a written COVID-19 prevention program. The prevention program must provide for the following:

    • Establishing a system for communicating information to employees about COVID-19 prevention procedures, testing, symptoms and illnesses, including a system for employees to report exposures without fear of retaliation
    • Identifying and evaluating hazards, including screening employees for symptoms and identifying workplace conditions and practices that could result in potential exposure
    • Investigating and responding to cases in the workplace, including responding immediately to potential exposures by following steps to determine who may have been exposed, providing notice within one business day about potential exposures, and offering testing to workers who may have been exposed
    • Correcting COVID-19 hazards, including correcting unsafe conditions and work practices and providing effective training and instruction
    • Physical distancing, including implementing procedures to ensure workers stay at least six feet apart from other people if possible
    • Providing face coverings and ensuring they are worn
    • Adopting site-specific strategies such as changes to the workplace and work schedules and providing personal protective equipment to reduce exposure to the virus
    • Meeting requirements for positive COVID-19 case and illness recording and making the COVID-19 prevention plan accessible to employees and employee representatives
    • Removing COVID-19 exposed workers and COVID-19 positive workers from the workplace with measures to protect pay and benefits
    • Establishing criteria for employees to return to work after recovering from COVID-19
    • Meeting requirements for testing and notifying public health departments of workplace outbreaks (three or more cases in a workplace in a 14-day period) and major outbreaks (20 or more cases within a 30-day period)
    • Meeting specific requirements for infection prevention in employer-provided housing and transportation to and from work.

    Will employers that already have COVID-19 safety policies need to make any adjustments to existing policies?

    While many employers have already implemented protocols that are contemplated by the new emergency standards, the emergency rules impose specific and nuanced obligations on employers in the event of COVID-19 exposure or an outbreak in the workplace that existing workplace safety plans are unlikely to include. For example:

    • Employers must offer COVID-19 testing at no cost, during working hours, to all employees who had a potential COVID-19 exposure in the workplace.
    • Employers must exclude from the workplace any employees with COVID-19 cases and those who were exposed to COVID-19 until they satisfy certain return-to-work criteria.
    • Employers must exclude an employee from the workplace if:
      • The employee receives a positive COVID-19 test.
      • The employee is exposed to COVID-19, in which case the employee must be excluded for 14 days after the last known COVID-19 exposure.
    • An employee who is symptomatic and tests positive for COVID-19 may not return to work until that employee meets all of the following requirements:
      • The employee has not had a fever of 100.4 degrees or higher for at least 24 hours, and that fever resolved without the use of fever-reducing mediations;
      • COVID-19 symptoms have improved.
      • At least 10 days have passed since COVID-19 symptoms first appeared.
    • An employee who is not symptomatic but tests positive for COVID-19 may not return to work until a minimum of 10 days have passed since the date of the COVID-19 test.
    • While an employee is excluded from the workplace, the employer must continue and maintain the excluded employee’s earnings, seniority and benefits.
    • Paid leave must be provided while the employee is excluded from the workplace unless (1) the employee is unable to work for reasons other than protecting persons at the workplace from COVID-19 transmission, or (2) the employer can demonstrate that the exposure was not work-related. Additionally, there is no limit on the “leave” in the requirement, meaning that an employee could receive it multiple times. The pay requirement can be satisfied by an employer’s existing paid leave policies and other public sources where permitted by law and not covered by workers’ compensation.
    • Employers cannot require a negative COVID-19 test for an employee to return to work. This is a departure from prior general federal guidance issued by the Equal Employment Opportunity Commission regarding the permissibility of COVID-19 viral tests under the Americans with Disabilities Act.
    • If there is an outbreak (defined as when a local health department identifies a workplace as an outbreak location, or when there are three or more COVID-19 cases in an exposed workplace during a 14-day period), an employer must:
      • Provide testing immediately to all employees in the exposed workplace during the outbreak period and additional testing one week later
      • After the first two COVID-19 tests, provide COVID-19 testing of employees who remain at the workplace, at least once per week or more frequently if required by a local health department
      • Exclude from the workplace all employees who have tested positive with COVID-19 and employees with a COVID-19 exposure
      • Immediately investigate and determine the possible workplace factors that contributed to the outbreak and take appropriate corrective action
      • Document the investigation in the manner set forth in detail by the emergency standardsNotify the local health department immediately, and no longer than 48 hours after knowledge of the outbreak, and include detailed information about the scope of the outbreak.
    • Employers must take additional measures if there is a “Major COVID-19″ Outbreak”, which is defined as an outbreak of 20 or more COVID-19 cases within a 30-day period, until there are no new cases for a 14-day period. These additional measures require an employer to:
      • Conduct twice-weekly free testing during employees’ work hours
      • Evaluate and possibly correct the employer’s ventilation system
      • Determine the need for a respiratory protection program or make changes to it
      • Evaluate whether to halt some or all operations until the COVID-19 hazards have been corrected.

    While this list is not exhaustive of the new requirements under the emergency standards, it is clear that even California employers with robust written COVID-19 safety policies will likely be required to amend existing policies to achieve compliance.

    Finally, the new emergency standards place additional burdens on employers that provide employee housing and/or motor vehicle transportation to and from work. Employers that provide these services for employees should carefully review the requirements to determine what additional measures must be taken to comply with the new standards.

    How long will these new emergency standards remain in place?

    Once approved and published, the emergency standards will remain in effect for 180 days unless renewed, withdrawn or replaced.

    What about interaction with other state and local laws?

    Clearly, these new requirements are substantial and raise many questions, specifically as to how they relate to other county, state and federal rules and regulations. Cal/OSHA plans to publish FAQs in the near future. However, given the exceedingly short timeframe for compliance, employers should immediately begin to review and update their COVID-19 protocols and procedures to ensure compliance with this emergency rule.

    Authors
    More insights