Content Type: Article

  • Transatlantic Restructuring Trends: Challenges and Opportunities in 2023

    Transatlantic Restructuring Trends: Challenges and Opportunities in 2023

    ARTICLE

    Transatlantic Restructuring Trends: Challenges and Opportunities in 2023

    January 2023

    Read time: 2 min

    Key takeaways
    Overview

    In this article published in Global Restructuring Review, partners Aymen Mahmoud and Mark Fennessy in London, Felicia Perlman in Chicago and Jon Levine in New York examine how struggling companies fared in 2022 with reduced access to liquidity, and predict an increase in distressed M&A activity and out-of-court transactions as debtors look to deal with those liquidity issues in the year ahead.

    In depth
    Authors
    More insights

  • European Competition Review 2022

    European Competition Review 2022

    ARTICLE / REPORT

    European Competition Review 2022

    January 2023

    Read time: 3 min

    Overview

    In our super-connected age, we are inundated with information. It can be difficult to select what is really relevant to one’s business.

    The purpose of this Review is to provide legal counsel and their teams easy reference guidance on essential EU competition law developments covering key areas of law and policy, to help keep you up to date on the latest requirements.

    Inside you’ll find:

    Cartels & Restrictive Agreements
    Cartels were firmly in the authorities’ crosshairs in 2022. Excess pricing in the automotive industry, the exchange of sensitive information in the computing industry and coordinated pricing in aviation were all major focus points and led to some interesting decisions.

    Abuse of Dominant Position
    Questions before the courts included the scope of B2B customer rebate schemes and how close incentives come to having anti-competitive effect.

    Merger Control
    Gun-jumping remains a real focus for the European courts. Companies should also be acutely aware of developments surrounding notification thresholds.

    State Aid
    Article 107 (1) TFEU contains a general prohibition on State aid. But there are exceptions. Over the course of 2022 a number of judgments helped to shed some light on when State aid is permissible.

    Legislative and Policy Developments
    The European Commission found itself under scrutiny, both in terms of the procedure for payment of fines and in terms of decisions on anticompetitive practices. Companies should carefully consider how upcoming developments on the digital market, and the new Foreign Subsidies Regulation may affect their business. Vertical agreements, and the entry into force of the new VBER, are also hot topics.

    In depth
    Tabs

    Stéphane Dionnet

    Partner

    Brussels

    Max Küttner

    Associate

    Düsseldorf

    More insights
    Endnotes

  • NYDFS Releases Guidance for BitLicensees and Limited Purpose Trust Companies on Asset Custody in the Wake of Cryptocurrency Insolvencies

    NYDFS Releases Guidance for BitLicensees and Limited Purpose Trust Companies on Asset Custody in the Wake of Cryptocurrency Insolvencies

    ARTICLE / CLIENT ALERT

    NYDFS Releases Guidance for BitLicensees and Limited Purpose Trust Companies on Asset Custody in the Wake of Cryptocurrency Insolvencies

    January 31, 2023

    Read time: 7 min

    Key takeaways
    Overview

    On Jan. 23, 2023, the New York State Department of Financial Services (“NYDFS”) issued guidance to entities licensed under 23 NYCRR Part 200 (“BitLicensees”) and entities chartered as New York limited purpose trust companies (together with BitLicensees, “Virtual Currency Entities” or “VCEs”), on custody and disclosure practices to protect customers in the event of an insolvency or similar proceeding (“Guidance”).[1] The Guidance applies to VCEs that act as custodians (“VCE Custodians”) and discusses the standards the NYDFS expects VCE Custodians to adhere to with respect to asset custody.[2] The Guidance focuses on four areas of customer protection, each of which is further discussed below: (i) segregation of and separate accounting for customer virtual currency; (ii) VCE Custodian’s limited interest in and use of customer virtual currency; (iii) sub-custody arrangements; and (iv) customer disclosure.

    Segregation of and Separate Accounting for Customer Virtual Currency 

    NYDFS expects VCE Custodians to separately account for and segregate customer virtual currency from their own assets, including from assets of their affiliates, both on-chain and on the VCE Custodian’s internal ledger accounts. Customer virtual currency must not be commingled with the VCE Custodian’s own virtual currency. Such segregation and accounting should also be fully disclosed to the customer as further discussed below.

    Specifically, customer virtual currency[3] should be maintained in either (i) separate on-chain wallets and internal ledger accounts for each customer under that customer’s name; or (ii) in one or more omnibus on-chain wallets and internal ledger accounts that contain only virtual currency of customers held under the VCE Custodian’s name as agent or trustee for the benefit of its customers. If customer virtual currency is held in one or more omnibus accounts, the VCE Custodian must maintain appropriate records and a clear internal audit trail to identify customer virtual currency. VCE Custodians should have clearly documented policies and procedures to evidence that these safeguards are in place. VCE Custodians should also be prepared to reconcile their books and records and on-chain activity upon the NYDFS’ request.

    VCE Custodian’s Limited Interest in and Use of Customer Virtual Currency

    When customers transfer virtual currency to a VCE Custodian for custody services, the NYDFS expects that the VCE Custodian will only take possession for the limited purpose of carrying out custody and safekeeping services. Particularly, the VCE Custodian should not establish a debtor-creditor relationship with the customer and use customer virtual currency for its own use, including using customer virtual currency to secure or guarantee an obligation of, or extend credit to, the VCE Custodian or any other person. VCE Custodians are also expected to act upon the instructions of their customers (or authorized representatives) and not acquire general discretion over custodied assets beyond those terms clearly expressed in the VCE Custodian’s agreement with its customer.

    Sub-Custody Arrangements

    To the extent the VCE Custodian engages a sub-custodian for the custody of its customers’ virtual currency, it may do so only after appropriate due diligence and obtaining prior approval from the NYDFS.[4] As part of the request for approval, the NYDFS expects the VCE Custodian to provide (i) the risk assessment performed by the VCE Custodian with respect to the new relationship; (ii) the proposed agreement(s) between the parties; and (iii) the VCE Custodian’s updated policies and procedures reflecting processes and controls to be implemented for the proposed arrangement.

    Customer Disclosure

    VCE Custodians should clearly disclose to their customers in writing the general terms and conditions associated with their products, services and activities, as well as obtain acknowledgment of receipt of such disclosures prior to entering into an initial transaction with the customer. The customer agreement should also clearly disclose (i) how the VCE Custodian segregates and accounts for customer virtual currency; (ii) the property interest the customer retains in custodied assets; (iii) how the VCE Custodian may use virtual currency while in its possession; and (iv) what limitations on the use of custodied virtual currency by the VCE Custodian apply. If the VCE Custodian uses a sub-custody arrangement, the customer agreement should clearly disclose the terms of that arrangement and the material risks presented by such arrangement. Further, the customer agreement and disclosures must be readily accessible to customers on the VCE Custodian’s website.

    Conclusion

    Given the current virtual currency market, including the recent bankruptcies of cryptocurrency exchanges and platforms, the Guidance indicates that the NYDFS is taking a strong stance to ensure the protection of customer assets, particularly in the event of an insolvency of a VCE Custodian. Currently regulated VCEs, or those seeking to apply to become a VCE, should carefully review the Guidance to ensure compliance.

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

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

    Betty Santangelo – New York (+1 212.756.2587, betty.santangelo@srz.com)

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

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

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

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

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

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

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

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

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


    [1]Guidance on Custodial Structures for Customer Protection in the Event of Insolvency, N.Y. Dep’t Fin. Servs. (Jan. 2023), available at https://www.dfs.ny.gov/industry_guidance/industry_letters/il20230123_guidance_custodial_structures 

    [2] Under 23 NYCRR Part 200, BitLicensees are required to, among other things, hold virtual currency in a manner that protects customer assets; maintain comprehensive books and records; properly disclose the material terms and conditions associated with their products and services, including custody services; and refrain from making any false, misleading or deceptive representations or omissions in their marketing materials. Analogous requirements on New York State limited purpose trust companies that engage in virtual currency business activity have been imposed by the NYDFS pursuant to supervisory agreements or through its authority to order the trust company to discontinue unsafe and unsound practices. See, e.g., NY Banking Law §§ 10, 39.

    [3] The Guidance notes that to the extent a VCE funds transaction costs (e.g., gas fees) on behalf of its customers, the VCE should consider these funds as customer funds subject to the Guidance.

    [4] The NYDFS notes in the Guidance that it views the establishment of a new sub-custody arrangement as a material change to the VCE Custodian’s business, which requires prior approval. Applicants can seek the required approval during the de novo license / charter application process, while currently regulated VCE Custodians can submit requests as a material change in business.


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

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

    In depth
    Authors

    Donald J. Mosher

    Partner

    New York – 919 Third Avenue

    Betty Santangelo

    Counsel

    New York – 919 Third Avenue

    Melissa G.R. Goldstein

    Partner

    New York – 919 Third Avenue

    Adam J. Barazani

    Partner

    New York – 919 Third Avenue

    More insights

  • California DxF Policies and Procedures Released for Public Comment

    California DxF Policies and Procedures Released for Public Comment

    CLIENT ALERT / INTEROPERABILITY

    California DxF Policies and Procedures Released for Public Comment

    January 27, 2023

    Read time: 11 min

    Key takeaways
    Overview

    On January 17, 2023, the California Health and Human Services Agency (CalHHS) released updated drafts of four policies and procedures (P&Ps) under the California Data Exchange Framework (DxF) to support the implementation of the Data Sharing Agreement (DSA) among DxF participants for public comment:

    In light of the upcoming January 31, 2023, deadline for certain California health care organizations subject to the DxF to execute the DSA, and January 31, 2024, deadline to begin sharing health and social services information (HSSI), which is defined broadly n the DSA, affected health care organizations should consider whether to submit comments to the draft P&Ps and evaluate their compliance obligations if the P&Ps are finalized as proposed.

    This On the Subject discusses key requirements and implications of the draft P&Ps and potential areas for comment. For more information on the DxF, please see our On the Subject concerning 10 things providers should know about the DxF.

    In depth

    CalHHS Requests Public Comments by February 14, 2023

    CalHHS has requested comments regarding the four draft P&Ps and an amendment to the Privacy Standards and Security Safeguards P&P (that addresses the destruction of information about an individual that a participant receives in error) by February 14, 2023. Stakeholders are encouraged to suggest revisions and express any concerns related to the P&Ps. Additionally, CalHHS has developed a list of questions for public input related to the requirements and content of the P&Ps. For example, CalHHS asks whether participants that engage in the early exchange of HSSI before January 31, 2024 should be required to comply with the P&Ps (which do not take effect until January 31, 2024). The answer to this question and others posed by CalHHS will have material impacts on how organizations participate in and comply with the DxF. If you would like help developing comments on the draft P&Ps or responding to the questions posed by CalHHS, please contact Daniel Gottlieb or your regular McDermott contact.

    California Information Blocking Prohibitions Borrow from Federal Guidelines, but Differ in Key Regards

    Like prior drafts of the California Information Blocking Prohibitions P&P, the latest draft broadly prohibits participants from undertaking any practice that is likely to interfere with access, exchange or use of HSSI for the required purposes listed in CalHHS’s Permitted, Required and Prohibited Purposes P&P. The draft P&P incorporates by reference the information blocking exceptions under the final rule (ONC Final Rule) adopted by the US Department of Health and Human Services Office of the National Coordinator for Health Information Technology (ONC) under the information blocking provisions of the 21st Century Cures Act subject to certain differences discussed below. For more information about the ONC Final Rule, see our Special Report.

    As of the prior Information Blocking Prohibitions P&P draft, CalHHS created two categories of participants:

    1. Participants that are already subject to the ONC Final Rule
    2. Participants that are not subject to the ONC Final Rule.

    Participants That Are Subject to the ONC Final Rule

    Under the Information Blocking Prohibitions P&P, a participant that is subject to the ONC Final Rule is deemed in compliance with the P&P if the participant meets an information blocking exception to the ONC Final Rule with respect to HSSI, except that the P&P specifically excludes its Fees and Licensing Exceptions.

    As a result, participants may not rely on the Fees Exception to charge fees for the exchange or use of electronic health information (EHI), as defined in the ONC Final Rule, or other HSSI. In addition, it appears that CalHHS intends to prohibit participants from relying on the Licensing Exception to charge royalties or other fees for licenses to application programming interfaces (APIs) and other interoperability elements to exchange or use HSSI. In its list of questions for public input, CalHHS notes that the draft P&P does not permit participants to use the Licensing or Fees Exceptions to withhold HSSI requested for required purposes, and asks if there are any circumstances under which a participant should be able to charge fees to license technology needed for the exchange of HSSI that is required under the DSA or charge fees to another participant in connection with required HSSI exchange.

    We expect this question to elicit a wide range of contradictory comments from stakeholders, including stakeholders that are not participants but may be contractually required by participants to comply with DxF requirements, such as electronic health record (EHR) vendors or interoperability software developers. If a participant does not execute an agreement with a qualified health information organization (QHIO), as defined in the DSA, and instead elects to execute an agreement with an EHR vendor, interoperability software developer or other entity that facilitates health information exchange to meet the participant’s obligations under the DxF, the DSA requires the participant to obtain reasonable assurances from the entity that the entity will enable the participant to comply with the minimum requirements for data exchange in the P&Ps.

    EHR vendors typically charge license fees for APIs and other technology used to access and share HSSI and may object to the DxF’s fee restrictions. On the other hand, health plans, mobile health app developers, and other software and service companies that seek HSSI to provide data-enabled services to health care providers will likely support the fee restrictions to avoid obligations to pay revenue shares and other fees to access and use HSSI.

    Participants That Are Not Subject to the ONC Final Rule

    Participants that are not covered actors under the ONC Final Rule are deemed to be in compliance with the P&P if they meet one of the ONC Final Rule exceptions to the information blocking prohibition, other than the Fees and Licensing Exceptions, and subject to some minor definitional changes to the Preventing Harm Exception and a requirement that any denial of access under the Privacy Exception be consistent with applicable law and/or the Individual Access P&P.

    Availability of the ONC Final Rule’s Content and Manner Exception

    While the Information Blocking Prohibitions P&P does not allow either category of participant to rely on the Fees or Licensing Exceptions, the P&P does allow all participants to rely upon the ONC Final Rule’s Content and Manner Exception. The Content and Manner Exception requires covered actors that fulfill a request for EHI in a manner other than the manner requested by the party seeking EHI to ensure that their fees for fulfilling the request satisfy the Fees Exception and that any license of interoperability elements in relation to the request satisfies the Licensing Exception. This inconsistency may indicate that CalHHS will permit participants and requestors an opportunity to mutually agree on the terms and associated fees for access to HSSI in the manner sought by the requestor. Participants should consider seeking guidance from CalHHS to understand its intent with respect to the Content and Manner Exception either as part of a general comment or in response to CalHHS’s specific question discussed above.

    Technical Requirements for Exchange P&P May Be Burdensome for Participants

    CalHHS intends for its draft Technical Requirements for Exchange P&P to define recommended and required exchanges of HSSI among participants and the technical standards to be used in those exchanges.

    Required Exchange

    Under the draft P&P, participants must exchange data with other participants in the following scenarios using nationally and federally adopted standards:

    • In response to a request for HSSI from a participant
    • When HSSI is created and becomes available electronically in connection with an order or request for services and delivery of those services by a participant
    • When a participant requests admit, discharge or transfer (ADT) event notifications from a participant that is a hospital.

    In addition, participant hospitals must notify at least one QHIO of an ADT event using HL7 Version 2.5 ADT messages or a later, compatible version. Participants may be able to meet this requirement through their EHRs.

    Person Matching

    A participant must use a standardized set of attributes and identifiers to determine whether electronic HSSI is appropriately linked to the correct patient (Person Matching) when it sends HSSI to or requests HSSI from another participant. Participants must use the following data attributes when requesting HSSI or responding to such requests: name; date of birth; home and/or mailing address, including previous addresses if known; phone numbers; and email addresses. Data attributes for Person Matching must also follow the guidelines established by the United States Core Data for Interoperability (USCDI) Version 2.

    A participant that makes electronic requests for electronic HSSI from a participant using a health information network or health information exchange framework with a nationwide scope, including California, must make the requests using the Integrating the Healthcare Enterprise (IHE) Cross-Community Patient Discovery (XCPD) exchange profile for Person Matching and the IHE CrossCommunity Access (XCA) exchange profile to retrieve HSSI.

    Interoperability Technical Standards

    The draft Technical Requirements for Exchange P&P requires or encourages participants to use specific interoperability standards to exchange HSSI. For example, the draft P&P encourages participants to support electronic requests and electronic responses to requests for electronic HSSI using HL7 FHIR Release 4 and the US Core implementation guide. As highlighted in a recent letter from the HIMSS EHR Association to CalHHS Secretary Mark Ghaly, the associated compliance costs, short timeframes to comply with technical standards, and addressing gaps in the standards could prove burdensome.

    Real-Time Exchange P&P Timeliness Requirements May Be Unrealistic

    The draft Real-Time Exchange P&P requires participants to send HSSI to other participants in a “timely manner.” CalHHS has explained that the meaning of the phrase “timely manner” varies based on the DxF transaction pattern and its associated clinical context. Generally, the draft P&P expects participants to respond to HSSI requests associated with diagnostic, health or social services without delay. Practically, it is unclear what timeframes CalHHS would consider timely for HSSI exchange. The draft P&P does not acknowledge that response times will vary depending on the size or complexity of an HSSI data set or the technical capabilities of a requestor.

    Stakeholders should consider commenting on the variables that might affect the timeliness of data exchange and recommending to CalHHS that it may be more practical to apply the real-time exchange requirements to a more focused scope of data or subset of HSSI, such as the data classes and elements in USCDI Version 2.

    Compliance With the Early Exchange P&P Would Be Difficult

    The Early Exchange P&P is the fourth draft P&P released by CalHHS for public comment. It allows participants to choose to engage in early exchange under the DSA by executing the DSA, verifying that their exchange partners have also executed the DSA, and complying with all published P&Ps. Under the draft P&P, early exchange participants must comply with new or updated P&Ps within 10 days of their publication date, regardless of the effective date written in the P&P. The short timeframe that early exchange participants would have to comply with new or updated P&Ps could be challenging, especially for more technical P&Ps that require participants to alter transaction patterns or adopt different technical or data standards or technology for data exchange. Stakeholders might consider requesting CalHHS to allow early exchange participants more time and flexibility to comply with new or updated P&Ps, especially given the uncertainty around the timing for finalization of the P&Ps.

    The Penalties for Failure to Execute the DSA Remain Unclear

    Neither California Health & Safety Code § 130290, the authorizing statute for the DxF, nor existing CalHHS guidance specify a penalty or consequence if a “mandatory” signatory refuses or fails to sign the DSA. While some observers expected Governor Newsom’s proposed budget to address penalties for failure to execute the DSA, the proposed budget released on January 10, 2023, was silent on the DxF. Governor Newsom may include a penalty for failure to execute the DSA in the May 2023 revision to the proposed budget, which will come after the deadline to sign the DSA on January 31, 2023.

    Action Items

    As CalHHS continues to develop the DxF, hospitals and other health care organizations required to participate in the DxF should consider the following steps:

    • Review the draft P&Ps and the list of questions from CalHHS to determine whether to submit comments directly or through their representatives.
    • Raise concerns with CalHHS about how the DxF Information Blocking Prohibitions P&P may complicate their ability to rely on certain exceptions in the ONC Final Rule and create compliance challenges.
    • Contact trade associations, such as the California Hospital Association and California Medical Association, to share their concerns about the DxF and coordinate coalitions for more effective engagement with CalHHS.
    • Evaluate interoperability solutions and other tools available through EHR and digital health vendors and nationwide networks or frameworks to identify options for exchanging HSSI in compliance with the P&Ps.
    • Attend public webinars on the DxF to stay informed on P&P updates and new P&Ps.
    Authors

    Daniel F. Gottlieb

    Partner

    Chicago

    Reuben Bank

    Associate

    Los Angeles

    More insights

  • IRS Releases Memorandum on Deducting Cryptocurrency Losses

    IRS Releases Memorandum on Deducting Cryptocurrency Losses

    ARTICLE / CLIENT ALERT

    IRS Releases Memorandum on Deducting Cryptocurrency Losses

    January 26, 2023

    Read time: 10 min

    Key takeaways
    Overview

    On January 13, 2023, the Internal Revenue Service (IRS) released a Chief Counsel Advice Memorandum (CCA 202302011) concluding that taxpayers cannot claim a deduction for cryptocurrency losses that have, absent a sale or other taxable disposition, substantially declined in value if such cryptocurrency continues to trade on at least one cryptocurrency exchange and has a value that is greater than zero.

    Additionally, for individual taxpayers that purchased cryptocurrency for personal investment purposes, even if they could claim a deduction for cryptocurrency losses because of worthlessness or abandonment, the memorandum concludes that such deductions are generally disallowed due to the limitations on miscellaneous itemized deductions for tax years 2018 through 2025.

    Throughout this article, we look at the key considerations taxpayers should keep in mind if they wish to claim deductions for cryptocurrency losses.

    In depth

    DEDUCTING LOSSES GENERALLY

    Generally, any loss sustained during a tax year in connection with a trade or business or in a transaction entered into for profit is deductible under Internal Revenue Code (Code) Section 165 unless it is compensated for by insurance or otherwise. A loss is treated as sustained during the tax year in which the loss occurs if it is evidenced by closed and completed transactions, fixed by identifiable events, and, with certain limited exceptions, is actually sustained during the tax year. A loss is not sustained to the extent there exists a claim for reimbursement—if there is a reasonable prospect of recovery—until the tax year during which it can be ascertained with reasonable certainty that the claimed reimbursement will not be received. No deduction is permitted if the loss arises solely as a result of a decline in the value of property owned by the taxpayer due to market fluctuations or other similar causes. However, a loss arising from theft in connection with a trade or business or in a transaction entered into for profit is permitted and is treated as sustained during the tax year in which the taxpayer discovers the loss (provided that no claim for reimbursement exists). Theft includes embezzlement, robbery and larceny, among other items.

    If any “security” that is a capital asset becomes worthless during the tax year, the resulting loss is treated as a loss from the sale or exchange of a capital asset on the last day of the tax year. A security for this purpose means a share of stock in a corporation; a right to subscribe for or to receive a share of stock in a corporation; or a bond, debenture, note, certificate or other evidence of indebtedness issued with interest coupons in registered form by a corporation, a government or a governmental political subdivision.

    Abandonment losses incurred in a trade or business or in a transaction entered into for profit and arising from the sudden termination of the usefulness in the trade or business or the transaction of any non-depreciable property can also give rise to a deduction if such business or transaction is discontinued or where such property is permanently discarded from use therein. To prove permanent abandonment, a taxpayer must show evidence of an intention to abandon the property and an affirmative act of abandonment.

    For individual investors that purchased cryptocurrency for personal investment purposes, losses from worthlessness or abandonment are classified as miscellaneous itemized deductions. However, under current law, losses characterized as miscellaneous itemized deductions are disallowed for tax years beginning after December 31, 2017, and before January 1, 2026. Accordingly, even if a taxpayer can establish losses for worthlessness or abandonment before 2026, the deduction would be disallowed. In contrast, losses relating to theft (in connection with a trade or business or in a transaction entered into for profit) and wagering are not classified as miscellaneous deductions and would not be disallowed.

    IRS GUIDANCE ON CRYPTOCURRENCY AND LOSS DEDUCTIONS

    Facts

    The memorandum considers a fact pattern where a taxpayer purchased cryptocurrency in 2022 for personal investment purposes. After the taxpayer acquired the cryptocurrency, its value decreased significantly to the point where its value was less than one cent at the end of 2022, though the cryptocurrency continued to be traded on at least one cryptocurrency exchange. The taxpayer maintained dominion and control over the cryptocurrency, including having the ability to sell, exchange or transfer it. The taxpayer claimed a deduction on his or her 2022 tax return and took the position that the cryptocurrency was either worthless or abandoned.

    Worthless Cryptocurrency

    The IRS stated that while the cryptocurrency had substantially decreased in value, there was no deductible loss because its value was greater than zero, it continued to be traded on at least one cryptocurrency exchange and the taxpayer did not sell, exchange or otherwise dispose of the cryptocurrency. The IRS relied on existing case law that states that the “mere diminution in value of property does not create a deductible loss. An economic loss in value of property must be determined by the permanent closing of a transaction with respect to the property. A decrease in value must be accompanied by some affirmative step that fixes the amount of the loss, such as abandonment, sale, or exchange.” Additional case law states that there must be an identifiable event that supports the fact that there is no current liquidating value and no value to be acquired in the future. Because the cryptocurrency still had a liquidating value (even if it was valued at less than one cent) and because it was still possible for the value to increase in the future given that it was traded on at least one cryptocurrency exchange, the cryptocurrency in question was not wholly worthless during 2022 as a result of its decline in value and the taxpayer did not sustain a bona fide loss under Code Section 165(a) because of worthlessness.

    Abandoned Cryptocurrency

    To claim a loss under Code Section 165 for abandoned property, (1) the loss must be incurred in a trade or business or in a transaction entered into for profit, (2) the loss must arise from the sudden termination of usefulness in the trade, business or transaction and (3) the property must be permanently discarded from use or from a transaction that is discontinued. The IRS determined that the taxpayer did not abandon the cryptocurrency in 2022 for Code Section 165(a) purposes because the taxpayer did not take any action to abandon and permanently discard the cryptocurrency. The taxpayer also did not demonstrate an intent to abandon the property nor did the taxpayer demonstrate any affirmative act of abandonment.

    Instead, the taxpayer maintained ownership of the cryptocurrency through the end of 2022 and retained the ability to sell, exchange or otherwise dispose of the cryptocurrency. Furthermore, the taxpayer continued to exert dominion and control over the cryptocurrency and, regardless of intent, did not take any affirmative steps to abandon the property during 2022.

    LIMITATIONS ON THE SCOPE OF IRS GUIDANCE

    This guidance takes the form of a Chief Counsel Advice Memorandum, which is generally issued to lawyers and revenue agents within the IRS. The memorandum has no precedential value and cannot be relied on by taxpayers (or cited as precedent). Nonetheless, many taxpayers take such guidance into account as it is useful for understanding the IRS’s current position on a certain issue, particularly when there is no other guidance available. The IRS could adopt a different position on the same or a similar issue and such a position would not require the withdrawal of the memorandum.

    PATHWAY TO A DEDUCTION

    Since miscellaneous itemized deductions may be available again in the future, taxpayers may still wish to know how these deductions can be claimed. The memorandum provides that, in order for a taxpayer to take a deduction on a tax return for a loss under Code Section 165, the taxpayer must show evidence of either (1) an identifiable event that supports the fact that there is no current liquidating value of the applicable cryptocurrency or any possibility for future appreciation or (2) intent to abandon the cryptocurrency, coupled with an affirmative act of abandonment.

    In the last 12 months, many cryptocurrency protocols have been subject to exploits and hacks that have left taxpayers with losses due to theft exceeding $2 billion (e.g., the Ronin bridge hack and the Wormhole bridge exploit). During the same period, several cryptocurrency exchanges filed for Chapter 11 bankruptcy protection in the United States. With respect to theft losses (in connection with a trade or business or in a transaction entered into for profit), provided that such taxpayers can show evidence of the theft and the amount of loss and are not entitled to receive any reimbursement through insurance or otherwise, such taxpayers may be able to deduct such losses on their tax returns. However, with respect to the cryptocurrency exchanges that are currently going through the Chapter 11 bankruptcy process, the answer is less clear given the uncertainty as to whether such taxpayers are entitled to reimbursement (e.g., as a creditor).

    The most common way to abandon cryptocurrency is to send it to a null address (also known as a burn address), which takes the cryptocurrency out of circulation so it cannot be used by any person going forward. Such action should be treated as evidence supporting forfeiting of dominion and control over the cryptocurrency. Other methods of abandonment could involve transferring a taxpayer’s right (or claim) to receive any currency to another party.

    CONCLUSION

    While the memorandum is helpful in providing insight into how the IRS is considering guidance related to cryptocurrency, given the limited facts, questions remain with respect to whether a taxpayer can claim a loss deduction for cryptocurrency losses. For example, the memorandum does not provide any discussion regarding the tax consequences of a taxpayer that does not have the ability to abandon (or take other action with respect to) the cryptocurrency since it is either frozen on a cryptocurrency exchange (e.g., in the case of a cryptocurrency exchange undergoing the Chapter 11 bankruptcy process that has suspended withdrawals and/or other actions) or is traded on a decentralized exchange without any available liquidity.

    While existing guidance provides that Bitcoin and Ethereum are likely to be treated as commodities because futures on these cryptocurrencies are traded on a commodities exchange, other cryptocurrencies may be treated as securities. On March 28, 2022, the US Department of the Treasury (Treasury) released the Fiscal Year 2023 Revenue Proposals and Green Book, which extended the definition of security to include actively traded digital assets that are recorded on cryptographically secured distributed ledgers in other areas of the Code (e.g., loans of securities under Code Section 1058). Given the recent events of the overall cryptocurrency industry, the Treasury may consider extending the expansion of the definition of security to Code Section 165, however, no indication has been made.

    The IRS has recently issued several memoranda on topics related to cryptocurrency and representatives of the IRS have indicated that further guidance is forthcoming.

    Anthony Teng, a law clerk in the New York office, also contributed to this article.

    Authors

    John T. Lutz

    Partner

    New York – One Vanderbilt Avenue

    Andrew M. Granek

    Partner

    New York – One Vanderbilt Avenue

    More insights

  • Remote Monitoring Services Under Review: Medicare Coverage Policies May Be Coming

    Remote Monitoring Services Under Review: Medicare Coverage Policies May Be Coming

    ARTICLE / CLIENT ALERT

    Remote Monitoring Services Under Review: Medicare Coverage Policies May Be Coming

    January 26, 2023

    Read time: 10 min

    Key takeaways
    Overview

    Six of the seven Medicare Administrative Contractors (MACs) are scheduled to jointly host a multijurisdictional contractor advisory committee (CAC) meeting on February 28, 2023. This CAC panel meeting will allow the MACs to obtain feedback from a panel of experts on the strength of currently published evidence on remote physiologic monitoring (RPM) and remote therapeutic monitoring (RTM) for non-implantable medical devices.

    CAC meetings often, but not always, are held in advance of the publication of a draft local coverage determination (LCD), specifying the circumstances or criteria under which items and services may be covered by Medicare in a particular geographic region. Given the increasing utilization of remote monitoring services, interested stakeholders should consider attending the upcoming CAC meeting and begin gathering data to support the clinical efficacy of non-implantable medical devices for RPM and RTM services.

    In depth

    Remote Monitoring Background

    In recent years, the Centers for Medicare & Medicaid Services (CMS) has expanded its payment for remote monitoring services, which generally use digital technologies (medical devices, together with software) to collect medical and other forms of health data from patients in one location and electronically transmit the information to the patient’s healthcare provider in a different location for assessment and care management. Monitoring devices and software can collect a wide range of health data from the point of care, including both self-reported and device-measured health information. This data is electronically transmitted to health professionals who review the data, engage in interactive communications with the patients (in some cases), and may make treatment management decisions in part based on this information.

    RPM services involve monitoring physiological conditions (e.g., weight, blood pressure, blood sugar) through medical devices, which transmit data obtained from patients automatically to healthcare providers for assessment and recommendations. In 2017, the American Medical Association modified an existing code for RPM services and created additional RPM codes as the initial primary category of remote patient monitoring services. The RPM codes became effective in 2019, and CMS clarified several issues in fall 2020 as part of the annual Medicare Physician Fee Schedule rulemaking cycle. The five codes for RPM services are CPT® codes 99091, 99453, 99454, 99457 and 99458. These include two practice-expense-only codes (99453 and 99454) and three codes for treatment management and ongoing monitoring services (99091, 99457 and 99458).

    In contrast to RPM services, RTM services involve the use of medical devices to monitor a patient’s health or response to treatment using nonphysiological data. RTM can be used to monitor medication adherence, response to therapy, musculoskeletal activity and respiratory activity. This means that RTM can be used, for example, to monitor treatment specific to pain, functional status, and adherence and response to therapy. Effective January 1, 2022, the American Medical Association created five new codes for RTM services (98975, 98976, 98977, 98980 and 98981) as a separate category of remote patient monitoring services. Similar to RPM, these include three practice-expense-only codes (98975, 98976 and 98977) and two codes for treatment management (98980 and 98981).

    Beginning in 2019, CMS established payment rates and provided guidance on certain requirements and appropriate utilization for remote monitoring services, specifically for RPM services. In response to the COVID-19 public health emergency, CMS also issued several waivers and flexibilities that expanded providers’ ability to furnish remote monitoring services to patients, including flexibilities regarding who can furnish the services, the types of technology that can be used and how many days of monitoring must be obtained in order to bill.

    Not surprisingly, the availability of Medicare reimbursement for remote monitoring services has led to a substantial level of interest in furnishing remote monitoring services, since Medicare is a major payor for healthcare items and services in the United States. Between 2019 and 2021, the utilization of the RPM codes reimbursed by Medicare for services furnished in a physician office setting grew by more than 1,500% for CPT codes 99454 and 99457. The remaining RPM codes similarly had a significant increase in utilization. Due to the growth of these services, it is perhaps unsurprising that the MACs would, at a minimum, consider the clinical evidence supporting the use of RPM and RTM services. Depending on the clinical evidence supporting the use of RPM and RTM services, this could lead to proposed coverage policies that, if finalized, could restrict utilization of remote monitoring services to conditions and devices that are supported by the most robust clinical evidence. While remote monitoring services have the potential to significantly improve patient care and reduce overall utilization of health care services through early intervention, the relatively recent advent of remote monitoring services means that research on clinical use cases is, in some cases, still developing.

    Medicare Coverage Policies

    In general, Medicare covers and provides payment only for healthcare items and services that are “reasonable and necessary” for the diagnosis or treatment of an illness or injury and within the scope of a Medicare benefit category. CMS makes national coverage determinations (NCDs) through an evidence-based process with opportunities for public participation. NCDs are coverage policies that apply nationwide to all Medicare beneficiaries and can grant, limit or exclude Medicare coverage for specific medical items or services. In the absence of a national coverage policy, MACs are permitted to publish LCDs. LCDs provide guidance to the public within a specified geographic area regarding whether a particular item or service is covered by Medicare for that geography or region and, if so, under what circumstances. LCDs may not conflict with NCDs, but an LCD may supplement an established NCD.

    Representatives of all MACs except for National Government Services, Inc., (NGS) will host the CAC meeting on February 28, 2023. Collectively, the MACs participating in the CAC meeting represent the majority of the United States, with the exception of Illinois, Minnesota, Wisconsin, Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island and Vermont.

    The purpose of the CAC meeting is to obtain advice from a select panel regarding the strength of published evidence on RPM and RTM for non-implantable devices and any compelling clinical data to assist in defining meaningful and measurable patient outcomes (e.g., decreases in emergency room visits and hospitalizations) for Medicare beneficiaries. Specific questions will be published approximately two weeks prior to this meeting. The public does not have an opportunity to participate in this meeting but will be able to register for the meeting and observe the discussion.

    MACs are required to establish CACs to provide an opportunity for healthcare providers to be informed of evidence that will be used in developing an LCD and are intended to improve communications between MACs and the healthcare industry more broadly. CACs are advisory only, however, and the final decision on whether to publish a draft LCD remains with each MAC.

    The forthcoming CAC meeting is just one step in a process that could lead to the development of an LCD. Should a MAC decide to develop an LCD following the CAC meeting, the proposed LCD will be published on the Medicare Coverage Database and on the MAC’s website. After the proposed LCD is made public, there will be open meetings concerning the proposed policy and an opportunity for the public to comment in writing before the LCD is finalized. The public must have at least 45 days to comment on the draft LCD. After a proposed LCD is published, final action must be taken on the LCD within 365 days of when the draft LCD is published. Proposed LCDs may be finalized as proposed, finalized with revisions or withdrawn. A final LCD must be published at least 45 days before the policy becomes effective.

    ANALYSIS

    In line with CMS’s gradual expansion of payment for remote monitoring services, CMS has established limited payment policies for RPM and RTM services, enabling providers to furnish and bill for remote monitoring services. To date, however, there have been no established coverage policies for remote monitoring services. At this point, CMS has not given any indication that an NCD for remote monitoring services is likely to be implemented.

    Often, but not always, CAC meetings precede the issuance of a proposed coverage policy. Given the explosion of interest in remote monitoring services, it is very likely that the forthcoming CAC meeting presages the publication of a proposed LCD. The CAC meeting will also provide insight into how the MACs view the clinical evidence and utility of remote monitoring services.

    Collectively, the MACs hosting the CAC meeting represent every Medicare contractor jurisdiction in the United States, with the exception of NGS. A restrictive coverage policy implemented by these MACs could impact a substantial majority of Medicare beneficiaries. However, the individual MACs participating in the CAC meeting remain free to implement separate LCDs, and it is not outside the realm of possibility that each of the MACs may approach coverage for RPM and RTM services differently.

    Practical Implications

    Interest in remote monitoring services (both RTM and RPM) services has burgeoned over the past several years. Medicare has seen a significant increase in the utilization of remote monitoring services, and it is unsurprising that the MACs have initiated a process that may lead to an implementation of an LCD that might place controls on the utilization of these services. A multijurisdictional CAC meeting strongly suggests that the MACs have seen the astronomical growth in utilization for RPM and RTM services and are seriously considering implementing at least one LCD to control and manage such utilization.

    As noted above, CAC meetings merely represent the beginning of the LCD development process. If MACs publish a draft LCD, stakeholders with an interest in Medicare coverage for remote monitoring services will have the opportunity to participate in open meetings and submit written comments summarizing clinical evidence supporting the utility and effectiveness of remote monitoring technologies in advance of any restrictive policy becoming effective. The CAC meeting is a valuable opportunity, however, to understand what evidence the MACs are currently considering and understand what input the invited healthcare professionals provide to the MACs in advance of the LCD development.

    A proposed LCD could implement Medicare coverage limits on, for example, the types of devices and patient conditions for which remote monitoring services are considered reasonable and necessary. Similarly, an LCD could implement limits on the duration of monitoring that will be covered.

    Any digital health company that is involved in furnishing devices, software or clinical support services that rely on the RPM or RTM codes should consider registering for the CAC meeting to gain insight into the feedback the MACs receive. Digital health companies also should begin gathering and compiling an evidentiary base on how the use of their technology impacts the patient and measurably improves patient care. This effort should include evidence on what specific medical devices and patients are supported by clinical data, and how the use of RPM or RTM services impacts patient management and improves patient outcomes (for example, lowers the likelihood of side effects post-surgery, reduces the incidence of chronic condition exacerbation, or reduces recurrent hospitalizations or office visits). Healthcare providers with evidence to support the clinical utility of RPM and RTM services should similarly focus on compiling such evidence. This evidence will be crucial for establishing that the use of particular devices for certain diagnoses provides clinical benefit to the patient.

    There is no opportunity for public comment at CAC meetings, but the meeting will be open to the public to observe virtually. Interested stakeholders may wish to consider listening in to the meeting. Additional information on the meeting is available here.

    Authors

    Caroline Reignley

    Partner

    Washington, DC

    Michael W. Ryan

    Partner

    Washington, DC

    Marshall E. Jackson , Jr.

    Partner

    Washington, DC

    More insights

  • Inter-Pacific Bar Association Journal | December 2022

    Inter-Pacific Bar Association Journal | December 2022

    ARTICLE

    Inter-Pacific Bar Association Journal | December 2022

    December, 2022

    Read time: 2 min

    Key takeaways
    Overview

    Jacques Buhart and Michinari Matsumoto authored the article “Sustainability Due Diligence in the EU: From Soft Law to Hard Law”, featured in the December 2022 issue of the Inter-Pacific Bar Association Journal.

    Read the full article here (p.28 – 34).

    In depth
    Authors
    More insights

  • FTC Increases 2023 Thresholds for HSR Filings and Interlocking Directorates

    FTC Increases 2023 Thresholds for HSR Filings and Interlocking Directorates

    ARTICLE / CLIENT ALERT

    FTC Increases 2023 Thresholds for HSR Filings and Interlocking Directorates

    January 25, 2023

    Read time: 10 min

    Key takeaways
    Overview

    On Jan. 23, 2023, the Federal Trade Commission (“FTC”) announced increased reporting thresholds under the Hart-Scott-Rodino Antitrust Improvements Act of 1976 (“HSR Act”); the revised HSR thresholds apply to all transactions closing on or after Feb. 27, 2023. The minimum size-of-transaction threshold was increased from $101 million to $111.4 million. Acquisitions below this threshold will not be reportable.

    The FTC also raised the thresholds for interlocking directorates under Section 8 of the Clayton Act, effective as of Jan. 20, 2023, and the maximum civil penalty amounts for HSR violations were increased to $50,120 per day of noncompliance, effective Jan. 11, 2023.

    Revised HSR Act Thresholds

    Generally, the HSR Act requires parties to acquisitions of voting securities, assets or non-corporate interests meeting certain thresholds to make a premerger notification to the FTC and the Antitrust Division of the Department of Justice unless an exemption applies. The HSR Act thresholds are adjusted annually in accordance with changes in U.S. gross national product. The parties to a reportable transaction must observe a waiting period (generally 30 days) before closing.

    Under the revised thresholds, transactions valued up to and including $111.4 million are not reportable under the HSR Act. Transactions valued at more than $111.4 million may be reportable if they meet the following criteria and no exemption applies:

    Size-of-transaction test

    The acquiring person will hold voting securities, non-corporate interests or assets of the acquired person valued at more than $445.5 million;

         or

    The acquiring person will hold voting securities, non-corporate interests or assets of the acquired person valued more than $111.4 million but less than $445.5 million, and the size-of-person test is met.

    Size-of-person test*

    One party has at least $222.7 million in total assets or annual sales, and the other has at least $22.3 million in total assets or annual sales. If the acquired party is “not engaged in manufacturing,” then the test applied to the acquired person specifies annual sales of $222.7 million or total assets of $22.3 million.

    *For the size-of-person test, a “party” includes its ultimate parent entity (“UPE”) and the UPE’s controlled subsidiaries.

    HSR Notification Thresholds for Acquisitions of Voting Securities. After an HSR filing has been made, and the applicable waiting period has expired or been terminated, any additional acquisitions by the same acquiring person of the same issuer’s voting securities will be exempt from notification, so long as:

    • The acquiring person’s holdings crossed the notification threshold with respect to which the premerger notification was made within one year of the expiration or early termination of the HSR Act waiting period; and
    • The subsequent acquisition is consummated within five years following the expiration or early termination of the HSR Act waiting period;

    unless a higher notification level is met or exceeded. The various notification levels are set forth below:

    HSR Act Original Threshold

    2023 Adjusted Threshold

    $50 million

    $111.4 million

    $100 million

    $222.7 million

    $500 million

    $1.1137 billion

    25 percent if value of voting securities to be held
    is greater than $1 billion

    25 percent if value of voting securities to be held is greater than $2.2274 billion

    50 percent if value of voting securities to be held
    is greater than $50 million

    50 percent if value of voting securities to be held is greater than $111.4 million

    Any subsequent acquisition would be subject to the adjusted thresholds in effect when such subsequent acquisition is consummated.

    HSR Filing Fees. The HSR filing fee structure recently was overhauled, with a six-tier framework replacing the three-tiered one in place for over two decades. The transaction value ranges for each tier have been adjusted as follows for filings beginning Feb. 27, 2023:

    Filing Fee

    Size-of-Transaction (as adjusted for 2023)

    $30,000

    Greater than $111.4 million but less than $161.5 million

    $100,000

    $161.5 million or more but less than $500 million

    $250,000

    $500 million or more but less than $1 billion

    $400,000

    $1 billion or more but less than $2 billion

    $800,000

    $2 billion or more but less than $5 billion

    $2,250,000

    $5 billion or more

    The filing fees will be adjusted annually based on the Consumer Price Index as determined by the Department of Labor.

    HSR Penalties. Any person (including the company and any of its officers, directors or partners) failing to comply with the HSR Act may be subject to a civil penalty for each day during which such person is in violation of the Act. The maximum civil penalty was increased from $46,517 per day to $50,120 per day of noncompliance, effective as of Jan. 11, 2023. The civil penalty amounts are adjusted by the FTC annually based on the percentage change in the Consumer Price Index.

    Revised Thresholds for Interlocking Directorates

    Under certain circumstances, Section 8 of the Clayton Act prohibits one person from simultaneously serving as a director or officer of two competing corporations if each corporation has capital, surplus and undivided profits aggregating more than $45,257,000 (up from $41,034,000).

    The Clayton Act does not prohibit the interlock if: (1) the competitive sales of either corporation are less than $4,525,700 (up from $4,103,400); (2) the competitive sales of either corporation are less than two percent of that corporation’s total sales; or (3) the competitive sales of each corporation are less than four percent of that corporation’s total sales.

    Authored by Peter Jonathan Halasz and Ngoc Pham Hulbig.

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


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

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

    In depth
    Authors

    Peter Jonathan Halasz

    Of Counsel

    New York – 919 Third Avenue

    More insights

  • No Surprises Act and Three Takeaways on Surprise Billing from the Initial Report on the Independent Dispute Resolution (IDR) Process April 15 – September 30, 2022

    No Surprises Act and Three Takeaways on Surprise Billing from the Initial Report on the Independent Dispute Resolution (IDR) Process April 15 – September 30, 2022

    ARTICLE / CLIENT ALERT

    No Surprises Act and Three Takeaways on Surprise Billing from the Initial Report on the Independent Dispute Resolution (IDR) Process April 15 – September 30, 2022

    January 24, 2023

    Read time: 6 min

    Key takeaways
    Overview

    Enacted as Division BB of the Consolidated Appropriations Act, 2021, the No Surprises Act (NSA) provides federal protections against surprise billing with respect to:

    • Emergency services (including post-stabilization services);
    • Non-emergency items or services furnished by out-of-network providers at certain in-network healthcare facilities; and
    • Air ambulance services furnished by out-of-network providers of air ambulance services.

    Under these new rules, covered individuals are required to pay no more than in-network cost-sharing amounts for these services. Health plans, issuers and Federal Employees Health Benefits (FEHB) Carriers must pay the out-of-network provider, facility or provider of air ambulance services an amount referred to as the “Qualifying Payment Amount” (or “QPA”) unless a state consumer protection law or All-Payer Model Agreement applies. (All-Payer Model Agreements are used by Medicare among other payers for making hospital payments based on per capita amounts.) The NSA establishes a Federal IDR process to allow disputing parties to resolve disagreements about payment for qualified items and services in cases in which good faith negotiations between an out-of-network provider, facility, or provider of air ambulance services and a health plan, issuer, or FEHB Carrier are unsuccessful.

    The NSA directs the US Departments of Health and Human Services (HHS), Labor and the Treasury (collectively, the Departments) to publish certain information quarterly about the Federal IDR process. Access the first such report, Initial Report on the Independent Dispute Resolution (IDR) Process April 15 – September 30, 2022 (the Report).

    In depth

    DISPUTE VOLUME

    Perhaps the most stunning feature of the Report is the sheer number of disputes. According to the Report, from April 15 to September 30, 2022, 90,078 disputes were submitted to the Federal IDR portal. The Departments originally estimated that 17,333 claims would be submitted as part of the Federal IDR process each year. As the Report concedes, this is “significantly more than the number of disputes the Departments initially estimated would be submitted for a full year.”

    The overwhelming majority of disputes covered in the Report involved emergency services. Some 71,513 disputes involved emergency services, which accounts for 82% of all disputes initiated for emergency or non-emergency services in this period. And over half of these disputes (70,071 disputes) involved services provided in a hospital emergency room.

    INTERACTION OF FEDERAL IDR PROCESS WITH THE CLAIMS PROCEDURE RULES

    Part I of the interim final rule provides detailed rules on the Federal IDR process, but it says nothing about the way the Federal IDR rules interact with the prior rules mandating claims procedures. A group health plan may deny payment because the item or service is not covered by the plan. For example, an individual covered by a preventive-services-only plan (a/k/a MEC plan) might be erroneously billed for an emergency procedure. If a covered individual seeks to have these covered, the claim should ultimately be denied. The claim in this instance would be a post-service claim, and the proper venue for the claim’s adjudication is the plan’s claims procedure, not the Federal IDR process. The Departments acknowledge the issue in the preamble to Part I of the interim final rule (86 Fed. Reg., p. 36,901), saying:

    The Departments are aware that the timeframes for deciding post-service claims under the claims and appeals rules issued under section 2719 of the PHS Act and the timeframes for sending an initial payment or notice of denial of payment under these final rules may not always align. The Departments seek to minimize confusion about which types of disputes should be resolved through a plan or issuer’s internal claims and appeals process instead of the IDR process established by the No Surprises Act.

    The Employee Retirement Income Security Act of 1974 (ERISA) claims procedure regulation applies to coverage determinations that are part of a claim for benefits and requires group health plans to notify a claimant of a benefit determination for post-service claims not later than 30 days after receipt of the claim. This can be extended, such that the plan may have at least 45 days to provide additional information. After that, the plan has 15 days to decide.

    PROBLEMS WITH “BATCHED CLAIMS”

    The NSA allows for multiple qualified IDR items or services to be submitted as a batched dispute when certain conditions are met. Batched items and services means multiple qualified IDR items or services that are considered jointly as part of a single payment determination. To qualify as such, a batched item or service must be (i) billed by the same provider or group of providers; (ii) paid by the same payer; (iii) of the same service code or a similar service code under a different procedural coding system; and (iv) furnished within the same 30-business-day period (or had open negotiation periods ending within a 90-calendar-day cooling off period).

    According to the Report, many disputes were incorrectly batched. Many submissions included multiple service codes from the same patient encounter as one dispute, rather than separating these different service codes into separate disputes in the manner the regulations describe. The reference to “the same or similar items or services” is defined with reference to Current Procedural Terminology (CPT), Healthcare Common Procedure Coding System (HCPCS) or Diagnosis-Related Group (DRG) codes. If a dispute is incorrectly batched, the certified IDR is directed to select one service code to continue through the Federal IDR process and asks the moving party to resubmit the other service codes as separate disputes.

    The Federal IDR process is central to the operation of the NSA. The new curbs on surprise billing insulate plan participants by strictly controlling cost-sharing and requiring the group health plan or carrier to pay the difference. Self-funded group health plans often designate a third-party administrator as the claims fiduciary. Thus, the third-party administrator will generally respond to demands by healthcare providers who resort to the Federal IDR process in the event of a disputed reimbursement. But plan sponsors should monitor their delegation of fiduciary responsibility, as they are ultimately responsible for compliance with the NSA.

    For more information on these tax and employment benefit issues, please contact your regular McDermott lawyer or one of the authors listed below.

    Authors

    Sarah G. Raaii

    Partner

    Chicago

    More insights

  • PPMs, Take Note: FTC Proposed Rule Banning Noncompetes May Have Significant Industry Impact

    PPMs, Take Note: FTC Proposed Rule Banning Noncompetes May Have Significant Industry Impact

    ARTICLE / CLIENT ALERT

    PPMs, Take Note: FTC Proposed Rule Banning Noncompetes May Have Significant Industry Impact

    January 24, 2023

    Read time: 5 min

    Key takeaways
    Overview

    On January 5, 2023, the Federal Trade Commission (FTC) issued a proposed rule that would prohibit employers from using noncompete agreements with their employees or independent contractors. Noncompete agreements are prevalent in the physician practice industry, as stakeholders have long recognized the importance of noncompetes as a tool for physician alignment. Physician employers, such as physician practices and physician practice management companies, may be significantly impacted if the proposed rule is adopted, and should consider submitting comments to the FTC on this important issue.

    In depth

    On January 5, 2023, the Federal Trade Commission (FTC) issued a proposed rule that would prohibit employers from using noncompete agreements with their employees or independent contractors.

    If adopted, this rule would make it illegal for an employer to enter into a noncompete agreement with a worker (employee or independent contractor), maintain a noncompete with a worker or represent to a worker that the worker is subject to a noncompete. Employers would also be required to rescind existing noncompetes and inform workers that they are no longer enforceable. Other restrictive covenants such as nondisclosure agreements would not be affected by the FTC’s proposed rule unless they are so broad in scope that they essentially function as a noncompete agreement.

    Noncompete agreements are prevalent in the physician practice industry, as stakeholders have long recognized the importance of noncompetes as a tool for physician alignment. These agreements are executed by physicians in connection with their practice employment, practice sales and similar transactions, and ownership of medical practices. While the proposed rule is directed at restrictive covenants in the employment context, all physician noncompete agreements may be impacted as (a) the proposed rule applies to any contractual term that prevents an employee from seeking or accepting employment post-termination, with no carve-out for noncompetes in LLC agreements or related corporate entity restrictions and (b) the exception for noncompete clauses entered into in connection with sale transactions are limited to “substantial owners” holding at least 25% of the ownership interest in a business entity, a threshold too high to apply in the context of larger physician practice sales.

    The proposed rule falls under Section 5 of the FTC Act, which does not apply to nonprofit entities, including nonprofit health systems and universities. As a result, the proposed rule states that it would not apply to an entity that is not “organized to carry on business for its own profit or that of its members.”

    Physician employers, such as physician practices and physician practice management companies, may be significantly impacted if the proposed rule is adopted. As such, employers should closely review their confidentiality and trade secret covenants to ensure maximum protection and they should consider and discuss other tools for physician alignment.

    The FTC is also inviting public comment on its proposed rule. The full text of the proposed rule and information on the public comment period is available here. In particular, the FTC seeks comment on whether senior executives or franchisees should be covered by the rule, as well as whether low- and high-wage workers should be treated differently under the rule. Comments are due 60 days after the Federal Register publishes this proposed rule, after which the FTC is likely to issue a final rule. Should the rule become final, companies should be prepared for it to go into effect 180 days after the date of publication.

    The proposed rule arrives with the FTC’s concurrent announcement of settlements in complaints it issued against three employers’ use of noncompetes. These settlements ban those employers from enforcing, threatening to enforce or imposing noncompetes against specified groups of employees and require that the companies notify all affected employees.

    Whether the FTC will succeed remains an open question. Republican Commissioner Christine S. Wilson, in a dissenting statement, cautioned that the proposed rule is open to meritorious challenges that (a) the commission lacks authority to engage in “unfair methods of competition” rulemaking and (b) the Supreme Court of the United States’ “major questions” doctrine suggests that the federal courts may preclude the FTC from venturing into this novel area of regulation absent legislative amendments to its enabling statute. Plus, interested parties may persuade the FTC to scale back its proposed regulation.

    Interested parties, including physician practice management companies interested in submitting such comments, can obtain further guidance and drafting assistance from any of the authors of this On the Subject or their McDermott Health lawyer.

    Authors

    Dana Dombey

    Partner

    Miami

    Larry C. Guess

    Partner

    Chicago

    Paul W. Hughes

    Partner

    Washington, DC

    Amanda Jester

    Partner

    Austin

    Brian Mead

    Partner

    Chicago

    Joseph M. Parise

    Partner

    Boston

    Joel C. Rush

    Partner

    Washington, DC

    Jerry J. Sokol

    Partner

    Miami

    Kristian A. Werling

    Partner

    Chicago

    More insights