ARTICLE
HIT Think Why Legal Questions Surround the Use of Voice Technology in Care Delivery
October 16, 2019
Read time: 1 min
ARTICLE
October 16, 2019
Read time: 1 min
ARTICLE
October 11, 2019
Read time: 1 min
ARTICLE
October 2019
Read time: 1 min

ARTICLE / CLIENT ALERT
October 11, 2019
Read time: 11 min
OFAC continues to issue sanctions and associated guidance relating to a number of targeted jurisdictions. Starting with Iran, which has been the subject of new sanctions over recent months, and continuing with Venezuela, Ukraine, Nicaragua and Cuba, the following sets forth a summary of the more recent sanctions developments.[1]
On Sept. 18, 2019, President Trump announced that he ordered Treasury Secretary Steven Mnuchin to substantially increase sanctions imposed on Iran.[2] This announcement came following a string of actions taken to increase the sanctions against Iran over the summer months.
Earlier this year, on May 8, 2019, President Trump signed Executive Order (“E.O.”) 13871, “Imposing Sanctions With Respect to the Iron, Steel, Aluminum and Copper Sectors of Iran,” designed to combat Iran’s access to weapons, counter Iran’s influence in the Middle East and deny the Iranian government revenue.[3] In addition to blocking a broad range of transactions in the iron, steel, aluminum and copper sectors of Iran, the order authorizes sanctions on correspondent and payable-through accounts at foreign financial institutions (“FFIs”) determined to have knowingly conducted or facilitated significant transactions related to these sectors, to or from Iran or for or on behalf of individuals or entities blocked pursuant to this order.[4] Specifically, among other things, the Secretary of the Treasury may prohibit the opening of, or impose strict restrictions on maintaining, correspondent or payable-through accounts in the United States by such FFIs.[5]
In connection with the issuance of this new order, OFAC issued six new Frequently Asked Questions.[6] These FAQs address the effect of the order, its effective date, the wind-down period, its applicable definitions and relationship with other sanctions and exceptions.
Additionally, on June 7, 2019, OFAC designated Persian Gulf Petrochemical Industries Company and its subsidiaries, pursuant to E.O. 13382, as amended, as Specially Designated Nationals (“SDNs”) for providing support to Khatam al-Anbiya, a person whose property and interests are blocked pursuant to E.O 13382, which authorized sanctions on weapons of mass destruction proliferators and their supporters.[7]
On June 24, 2019, OFAC designated Iran’s Supreme Leader, his Office and persons appointed to certain official or other positions by the Supreme Leader or his Office, pursuant to E.O. 13876, as SDNs.[8] On that same day, OFAC designated eight senior commanders of Navy, Aerospace and Ground Forces of the Islamic Revolutionary Corps, pursuant to E.O. 13224, as amended, as SDNs for their involvement in effectuating the Iranian regime’s destructive influence in the Middle East.[9] On July 9, 2019, further sanctions were issued pursuant to E.O. 13224 against key Hizballah political and security figures.[10]
On Aug. 28, 2019, OFAC targeted two Iranian regime-linked networks, pursuant to E.O. 13382, for engaging in procurement activities benefitting Iranian military organizations.[11] Specifically, OFAC targeted the Dehgan Network, including two Iranian nationals (Hamed Dehghan and Hadi Dehgan), that have used a network of intermediary companies to facilitate proliferation-related transactions and the Shariat Network, including Asre Sanat Eshragh Company and its owner Seyed Hossein Shariat, that procured large amounts of aluminum alloy products for multiple Iranian entities.[12]
On Sept. 4, 2019, OFAC, pursuant to E.O. 13224, identified 16 entities, 10 individuals and 11 vessels as part of a large shipping network that is directed by and financially supports the Islamic Revolutionary Guard Corps-Qods Force (IRGC-QF) and added them to the SDN List.[13]
On Sept. 20, 2019, OFAC, based on its authority under E.O. 13224, took action against the Central Bank of Iran (CBI), the National Development Fund of Iran (NDF), which is Iran’s sovereign wealth fund, and Etemad Tejarate Pars Co. by blocking all property and interests in property of these entities.[14] The Secretary of the Treasury stated this action was based on the fact that these entities provided “crucial funding” that the Iranian regime “uses to support its terrorist network, including the Qoods Force, Hizballah and other militants that spread terror and destabilize the region.”[15]
On Sept. 25, 2019, OFAC issued a new FAQ, discussing the Secretary of State’s Sept. 25, 2019 determination that COSCO Shipping Tanker (Dalian) Co. and COSCO Shipping Tanker (Dalian) Seaman & Ship Management Co. meet the criteria for the imposition of sanctions with respect to Iran under E.O. 13846 and clarifying that sanctions do not apply to the ultimate parent company, COSCO Shipping Corporation Ltd. (COSCO).[16]
Between April 17 and July 3, 2019, OFAC designated additional entities and individuals in Venezuela as SDNs pursuant to E.O. 13850, as amended, and E.O. 13692, as amended. On April 17, 2019, Banco Central de Venezuela (also known as the Central Bank of Venezuela) and the bank’s director, Iliana Josefa Ruzza Terán, were designated as SDNs for operating in the financial sector of the Venezuelan economy.[17] In addition, OFAC continues to target the political regime of President Nicolas Maduro Moros (“Maduro”). On June 27 and 28, 2019, several former officials from Maduro’s regime, including Maduro’s son, were designated as SDNs as a result of their positions as former officials of the Government of Venezuela.[18]
As a result of these designations, all property and interests in property of the above-named entities and individuals, and any entity that is owned, directly or indirectly, 50 % or more by the designated entities or individual, that are in the U.S. or in the possession or control of U.S. persons, are blocked.
In connection with the April 17, 2019 designations, OFAC added two new general licenses,[19] amended five existing general licenses[20] and issued one new FAQ. In its newly issued FAQ, OFAC clarified its position that despite the new sanctions, it is “committed to ensuring that humanitarian assistance and non-commercial, personal remittances can flow to the people of Venezuela.”[21]
On June 6 and 26, 2019, OFAC further amended four existing licenses related to activities involving entities related to Petróleos de Venezuela, S.A. (“PdVSA”), and issued one new FAQ.[22] In this FAQ, OFAC clarified that persons subject to U.S. jurisdiction cannot export or reexport diluents,[23] directly or indirectly, to Venezuela, or engage in transactions or activities related thereto.[24]
On July 3, 2019, Cubametales, a Cuban state-run oil company, was designated an SDN, pursuant to E.O. 13850, as amended, for providing support to Maduro.[25] In connection with this designation, OFAC delisted PB Tankers S.p.A. (“PB Tankers”) and its related entities, because PB Tankers terminated its charter agreement with Cubametales and took other steps to prevent future sanctionable activity.[26]
On Aug. 5, 2019 the President issued E.O. 13884, blocking all property and property interests in the Government of Venezuela and authorizing the Treasury Department to sanction additional persons who have assisted or supported the Government of Venezuela, including through the provision of goods or services.[27] While E.O. 13884 continues to allow transactions with the Venezuelan private sector, given that the government of Venezuela owns or controls such large portions of the economy, the practical scope of E.O. 13884 is quite broad.
In connection with the newly issued E.O. 13884, OFAC amended 12 preexisting general licenses[28] and issued 13 new general licenses.[29] Additionally, in response to E.O. 13884, OFAC issued three new FAQs. FAQ 679 clarifies that U.S. support for Interim President Guaidó is still permitted through the issuance of General License 31.[30] FAQ 680 affirms that under the blocking sanctions imposed by E.O. 13884, U.S. persons are generally prohibited from engaging in transactions with the Government of Venezuela or with entities owned 50 % or more by the Government and that OFAC expects financial institutions to conduct due diligence to confirm that customers are not persons whose property and interests are blocked.[31] Finally, FAQ 681 clarifies that General License 28 does not extend to the wind-down periods that have already expired regarding PdVSA, the Central Bank of Venezuela and of blocked persons.[32]
On Sept. 9, 2019, OFAC published an additional general license authorizing transactions involving certain Government of Venezuela persons.[33] Specifically, the new general license authorizes transactions with the Government of Venezuela provided that the individuals are (i) U.S. citizens, (ii) permanent resident aliens of the United States, (iii) individuals in the United States who have a valid U.S. immigrant or nonimmigrant visa and (iv) former employees and contractors of the Government of Venezuela.[34] In connection with this license, OFAC published a revised FAQ 680 to reflect the authorizations granted by the new general license and provide additional clarity on the prohibitions in E.O. 13884.[35]
On Sept. 30, 2019, OFAC amended two general licenses, including General License No. 3G, “Authorizing Transactions Related to, Provision of Financing for, and Other Dealings in Certain Bonds”[36] and General License 9F, “Authorizing Transactions Relating to Dealings in Certain Securities,”[37] extending the expiration for these licenses until March 31, 2020.
On June 26, 2019, OFAC extended the expiration date of two general licenses related to the GAZ Group (“GAZ”). General License 13L now authorizes certain transactions necessary to divest or transfer debt, equity, or other holdings in GAZ through Nov. 8, 2019 at 12:01 am EST.[38] General License 15F now authorizes certain activities necessary to maintain or wind-down operations or existing contracts with GAZ through Nov. 8, 2019 at 12:01 am EST as well.[39] In addition to this extension, General License 15F authorizes the installation of automotive safety systems consistent with applicable regulatory requirements in vehicles produced by GAZ Group or any other entity in which GAZ Group owns, for the same time period.[40]
OFAC issued regulations to implement E.O. 13851, which blocked property of certain persons contributing to the violent response by the Government of Nicaragua to protests that began on April 18, 2018 and the Ortega regime’s dismantling and undermining of democratic institutions.[41] The proposed regulations took effect on Sept. 4, 2019. OFAC intends to further supplement these regulations with a more comprehensive set of regulations and additional interpretive and definitional guidance, general licenses and statements of licensing policy.
On Sept. 9, 2019, OFAC published an amendment to the CACR,[42] to further implement the President’s foreign policy toward Cuba by “denying Cuba access to hard currency” and “curbing the Cuban government’s bad behavior while continuing to support the long-suffering people of Cuba.”[43] The Amendment became effective on Oct. 9, 2019.[44] In connection with the amendments, OFAC published updated FAQs[45] and a Fact Sheet.[46] The updated FAQs makes clear that the Sept. 9 amendments revise certain authorizations for remittances to Cuba, eliminate the authorization for donative remittances, and revise the authorization commonly known as the “U-Turn” general license. In connection with the U-Turn general license, the amendment removes the authorization for banking institutions subject to U.S. jurisdiction to process certain fund transfers originating and terminating outside the United States.[47] These banking institutions will be authorized to reject such transactions, but they may no longer process the transactions.[48]
On Sept. 9, 2019, the President issued E.O. 13886 “Modernizing Sanctions to Combat Terrorism.”[49] E.O. 13886 amends E.O.13224 which was issued by President Bush in 2001, and rescinds E.O. 12947 issued by President Clinton. E.O. 13886 is aimed at giving the government a wider array of tools to sanction terrorist groups and their funders, as well as a unified approach. The E.O. gives federal agencies the authority to target terrorist leaders and those who participate in terrorist training and permits secondary sanctions against financial institutions that aid terrorists. As a follow-up, the treasury department sanctioned a number of terrorist organizations, including al-Qaida, Hamas, the Islamic State Militant Group and Iran’s Quds Forces. The treasury department also labeled a Syrian-based al Qaida affiliate group as a specially designated global terrorist entity.
On Aug. 20, 2019, OFAC designated Dominican national Cesar Emilio Peralta and the Peralta Drug Trafficking Organization (“Peralta DTO”), pursuant to the Foreign Narcotics Kingpin Designation Act.[50] OFAC designated eight additional Dominican nationals for assisting Peralta and the Peralta DTO, as well as six entities in Santo Domingo, Dominican Republic.[51] These designations target significant foreign narcotics trafficking through the Dominican Republic and to consumer markets in the United States, Puerto Rico and Europe.[52] OFAC’s Kingpin designations were closely coordinated with the Drug Enforcement Administration and the Federal Bureau of Investigation, and further OFAC’s commitment to countering criminal networks that engage in human trafficking.[53] The following day, OFAC additionally designated several Chinese individuals, pursuant to the Kingpin Act.[54]
In addition to recent Kingpin designations, on Aug. 16, 2019, OFAC settled with Atradius Trade Credit Insurance Inc. (“Atradius”), of Hunt Valley, Maryland, accepting a payment of $345,315 for apparent violations of the Foreign Narcotics Kingpin Sanctions Regulations.[55] Atradius had agreed to accept the assignment of debt owed by Grup Wisa S.A. (“Grupo Wisa”), an SDN.[56] Atradius then filed a creditor claim in Panama and ultimately received a payment of approximately $4 million in satisfaction of that debt.[57] OFAC determined that, by accepting the assignment of Grupo Wisa’s debt and receiving payment from Grupo Wisa’s liquidation, Atradius dealt in the property or interests in property of an SDN in violation of 31 C.F.R. § 598.203(a).[58] This enforcement action highlights the importance of diligence regarding any transaction with an SDN.
Given the breadth and frequency of the recent changes across multiple sanctions programs in recent months, it is important to stay abreast of OFAC’s actions and continuing developments related to all sanctions programs.
Authored by Betty Santangelo, Gary Stein, Hannah M. Thibideau, and Jennifer M. Opheim.
If you have any questions concerning this client alert, please contact your lawyer or one of the authors.
ARTICLE / CLIENT ALERT
October 9, 2019
Read time: 7 min
The Department of Health & Human Services’ (HHS) proposed changes to the Stark Law, the Anti-Kickback Statute, and the Civil Monetary Penalty Law, released today as part of the Regulatory Sprint to Coordinated Care, would represent some of the most significant changes to these laws in the last decade. This high-level overview addresses noteworthy changes and next steps as the healthcare industry continues to navigate the transition towards a value-based healthcare delivery system. In-depth analysis on key provisions will follow on McDermott’s Regulatory Sprint Resource Center.
On October 9, 2019, the US Department of Health and Human Services (HHS) published proposed changes to the physician self-referral law (Stark Law) (Stark Proposed Rule) and the Anti-Kickback Statute (AKS) and the Beneficiary Inducement Civil Monetary Penalty Law (CMPL) (AKS Proposed Rule).
The proposed rules represent some of the most significant potential changes to these laws in the last decade. HHS Deputy Secretary Eric Hargan said that they “would be a historic reform of how healthcare is regulated in America.” This On the Subject provides a high-level overview of key provisions in the proposed rules. More in-depth analysis will follow at our Regulatory Sprint Resource Page.
The “Sprint”
The Stark Law and AKS Proposed Rules have been promulgated as part of HHS’s “Regulatory Sprint to Coordinated Care,” which was launched in 2018 with the goal of reducing regulatory burden and incentivizing coordinated care. As part of this initiative, the Centers for Medicare and Medicaid Services (CMS) and the HHS Office of Inspector General (OIG) began scrutinizing a variety of long-standing regulatory requirements and prohibitions to determine whether they unnecessarily hinder the innovative arrangements that policymakers are otherwise hoping to see develop. The agencies took the step of formally seeking public input on this topic by issuing requests for information (RFIs) in June and August 2018. More information about HHS’s Sprint and the RFIs is available on our Regulatory Sprint Resource Page.
The Proposals
The Proposed Rules reflect a coordinated effort between CMS and OIG to address various challenges to the transition to value-based care. Both agencies clearly recognize that the two laws often operate in tandem, but they also emphasize that they are distinct and separate enforcement vehicles. Thus, in some instances OIG’s proposals may be more restrictive that CMS’s, and both agencies state that the AKS may act as a “backstop” to protect against arrangements that meet a Stark Law exception but are nonetheless considered abusive. CMS also proposes to remove compliance with the AKS as a requirement from several Stark Law exceptions, further underscoring the laws’ separateness.
The Stark Law Proposed Rule includes new exceptions designed to enable value-based care arrangements and proposes a long list of additional changes to the Stark Law regulations intended to address many of the most challenging aspects of Stark Law compliance. Among the most noteworthy proposals are the following:
The AKS Proposed Rule also includes many important proposals that would modify existing AKS safe harbors, create new AKS safe harbors and create new CMPL exceptions. We have identified those proposals below along with brief descriptions of some of the changes they would involve:
Next Steps
If finalized, the changes proposed in these rules could present significant opportunities for new arrangements, but may also necessitate revisions to current arrangements involving healthcare providers, others involved in the healthcare industry, and patients.
The public now has the opportunity to provide feedback to HHS on the proposed changes to help inform any future final rules. The proposed rules state that comments for each will be due 75 days from the date of publication in the Federal Register (which is currently scheduled for October 17, 2019). All stakeholders should consider commenting, as these proposed rules have the potential to fundamentally alter the health care landscape by allowing new and different types of arrangements. Watch our Regulatory Sprint Resource Page for updates.
ARTICLE
October, 2019
Read time: 2 min
Deniz Tschammler authored the article “IT-Sicherheit im Gesundheitswesen – Schutz kritischer Infrastrukturen und Verifikation von Arzneimitteln”, featured in PharmR 10/2019, p. 509-516 in October 2019.

ARTICLE
October 7, 2019
Read time: 2 min
Reproduced with permission. Published October 4, 2019. Copyright 2019 The Bureau of National Affairs, Inc. 800- 372-1033. For further use, please visit http://www.bna.com/copyright-permission-request/

ARTICLE
October 7, 2019
Read time: 1 min
ARTICLE / CLIENT ALERT
October 3, 2019
Read time: 12 min
The FDA recently released six guidance documents as part of the agency’s continued focus on updating the regulatory stance on software as a medical device and other digital health products. The updated guidance documents reflect the need for a more flexible, risk-based approach to regulation that accommodates a rapidly evolving technological landscape. This On the Subject summarizes the key provisions and changes presented in the guidance, and discusses next steps for stakeholders impacted by FDA’s evolving approach to digital health regulation.
The 21st Century Cures Act, enacted in December 2016, amended the definition of “medical device” in section 201(h) of the Federal Food, Drug, and Cosmetic Act (FDCA) to exclude five distinct categories of software or digital health products. In response, the US Food and Drug Administration (FDA) issued new digital health guidance and revised several pre-existing medical device guidance documents. FDA also stated that it would continue to assess how to update and revise these guidance documents as its thinking evolved.
Late last week, FDA issued five final guidance documents and re-issued a draft guidance document to better reflect FDA’s current thinking on software as a medical device (SaMD) and other digital health products:
Most of the guidance documents reflect modest changes to prior draft guidance documents that describe categories of low-risk health and wellness devices that FDA does not intend to regulate. FDA’s new draft Clinical Decision Support (CDS) Software guidance, however, provides a new and more detailed analysis of risk factors that FDA will apply to determine whether a CDS tool is a medical device. FDA updated its previously issued draft CDS guidance without finalizing it. Although the new guidance does not explain why FDA is reissuing the CDS guidance in draft, the new draft guidance seems to reflect the agency’s attempt to better align its definition of non-device software with the often misunderstood and misinterpreted statutory definition of CDS in section 520(o)(1)(E) of the Cures Act. The chart below summarizes the key provisions and changes to these guidance documents.
Digital health products can present a particular challenge for developers and regulators in assessing the appropriate regulatory pathways for a new product. The updated guidance documents reflect the need for a more flexible, risk-based approach to regulation that accommodates a rapidly evolving technological landscape. These documents also reflect what appears to be the new normal for digital health regulation—the need for iterative thinking and ongoing revisions to interpretive guidance documents to keep pace with a constantly changing marketplace.
Overview
FDA finalized its draft guidance, which provides FDA’s current thinking regarding the amended definition of a “device” and the resulting impact it has on FDA guidance documents related to medical device software that predate the Cures Act. The guidance describes changes to the following four guidance documents at a high level:
FDA clarified that hardware with general wellness intended uses that relate to maintaining or encouraging a general state of health or healthy activity that otherwise meet the definition of a “device” under section 201 of the FDCA will continue to be regulated as devices.
FDA also withdrew its Guidance for the Submission of Premarket Notifications for Medical Image Management Devices, because some software functions described therein no longer meet the definition of a “device.” For the Medical Image Management Devices that continue to meet the definition of “device,” FDA acknowledged that the guidance was out-of-date and encouraged medical device manufacturers to reference the FDA-recognized versions of voluntary consensus standards instead.
Overview
FDA previously finalized its draft guidance on General Wellness Products in 2016 (previously discussed here).
FDA clarified that software functions that are intended for maintaining or encouraging a healthy lifestyle and are unrelated to the diagnosis, cure, mitigation, prevention or treatment of a disease or condition are excluded from the definition of “device.”
The title of Section V has been changed to “Examples of General Wellness Products that Are Not Medical Devices and Examples of General Wellness Products that Are Medical Devices for which FDA Does Not Intend to Enforce Requirements” to more accurately reflect the fact that some examples provided in this section do not meet the definition of a “device.”
Overview
This guidance supersedes the February 9, 2015, “Mobile Medical Applications” guidance. While FDA broadened the scope of the guidance to include device software that includes mobile applications, FDA reiterated that it intends to apply regulatory oversight to only those software functions that:
FDA intends to continue exercising enforcement discretion (i.e., based on FDA’s current understanding of risks, it does not intend to enforce compliance with applicable device requirements) over the following software functions:
FDA also moved a number of examples from Appendix B (examples of mobile apps for which FDA intends to exercise enforcement discretion) or Section V.B (examples of mobile apps for which FDA intends to exercise enforcement discretion, such as functions that enable patients or HCPs to interact with electronic health record (EHR) systems or those intended to transfer, store, convert, format and display medical device data in its original form) to Appendix A (examples of mobile apps that are NOT medical devices) because they no longer meet the definition of a “device.”
Overview
Since the Cures Act excludes software that is intended for “transferring, storing, covering formats, or displaying clinical laboratory test or other device data and results unless such function is intended to interpret or analyze clinical laboratory test or other device data, results, and findings” (emphasis added), Medical Device Data Systems (MDDS), medical image storage devices and medical image communications devices no longer meet the definition of a “device.”
The guidance defines “Non-Device-MDDS” as software functions that are solely intended to transfer, store or convert formats and display medical device data or results. However, software functions that “analyze or interpret” medical device data and results, such as medical images, waveforms, signals or other clinical information, remain devices. Additionally, software functions intended to generate alarms or alerts or prioritize patient-related information on multi-patient displays are not excluded from the definition of a “device,” because they involve analysis or interpretation of laboratory tests or other device data and results.
The guidance also defines “Device-MDDS” as hardware functions that are solely intended to transfer, store or convert formats and display medical device data or results. Hardware that is intended to transfer, store, convert formats and display medical device data and results remains a device unless it is used solely for transfer, storage or conversion of formats and to display medical device data or results.
FDA intends to provide recommendations on Non-Device-MDDS and Device-MDDS functions with respect to how they affect the safety and effectiveness of device function(s) in multiple function device products in a separate guidance.
Guidance: Off-the-Shelf Software Uses in Medical Devices
Overview
In the revised guidance, which updates the September 1999 guidance, FDA removed the section on “Exemption of Laboratory Information Management Systems,” for Laboratory Information Systems and Laboratory Information Management Systems functions, which includes calculator/data processing modules for clinical use under 21 CFR section 862.2100, intended for administrative support. FDA made this change because FDA no longer regulates software that simply transfers, stores, converts formats or displays clinical laboratory test data and results as a “device.”
Overview
FDA clarified that the term “clinical decision support” (CDS) is used broadly. CDS provides HCPs and patients with information, “intelligently filtered or presented at appropriate times” to enhance healthcare. Under section 520(o)(1)(E) of the FDCA, software that meets all of the following criteria are excluded from the definition of a “device,” (further discussed here):
The most significant element is whether the HCP can independently review the basis for information or recommendations the software presents, so that the HCP is not required to rely primarily on any of such recommendations to make a decision regarding a patient.
In the previous version of the draft guidance, FDA stated that it also intended to exercise enforcement discretion over products intended for patients or caregivers if the software generally paralleled CDS for HCPs and met all four criteria above. The revised guidance removes the concept of “patient decision support” or “PDS” software. FDA now considers all CDS software that is intended for a patient or caregiver, regardless of whether the user can independently review the basis for information or recommendations presented by the software, to be “Device CDS,” although some Device CDS software intended for patient or caregiver use remains subject to enforcement discretion. For example, software that provides information to a patient about the use of a prescription drug that is consistent with both FDA-approved labeling and the patient’s prescription, such as software that reminds a patient how or when to take a prescribed drug, remains under enforcement discretion.
If the software is intended for an HCP and the HCP can independently review the basis for information or recommendations, the software is “Non-Device CDS.” The revised guidance clarifies that “Non-Device CDS” includes software functions that meet all criteria in the basic framework and only includes software intended for HCPs.
For Device CDS, FDA has adopted the International Medical Device Regulators Forum (IMDRF) risk-based framework for categorizing products, which evaluates (1) the significance of the information provided by the product to a healthcare decision (to treat or diagnose, to drive clinical management or to inform clinical management) against (2) the state of the healthcare condition (critical, serious, non-serious). See IMDRF “‘Software as a Medical Device’: Possible Framework for Risk Categorization and Corresponding Considerations.” Based on this, FDA has established a summary of its current regulatory policy and added examples for each of the following categories:
The guidance is open to public comment until December 26, 2019. FDA intends to make conforming edits to the Policy for Device Software Functions and Mobile Medical Applications – Guidance for Industry and Food and Drug Administration Staff after finalizing this guidance.
ARTICLE
October 3, 2019
Read time: 2 min
There are myriad opportunities for hospitals and health systems (HHSs) to engage in data-focused collaborations with other stakeholders in the healthcare industry. These collaborations include, to an increasing extent, digital health and technology companies both big and small. As both users and contributors of data in these endeavors, and because they are often on the front line for patients who have questions about the use of their data, HHSs must navigate multi-dimensional compliance issues and other legal factors. In the fourth installment of our Focus on Innovation Centers series, Jiayan Chen and Ed Zacharias outline key considerations for HHSs as they contemplate potential data-focused collaborations and other relationships.