On November 30, 2016, the House overwhelmingly passed (392-26) the 21st Century Cures Act (“Bill”). The Bill moves on to the Senate next week and it is projected to pass in the Senate as well. Notably, the Bill seeks to improve upon the federal regulatory structure regarding Federal Drug Administration (FDA) approval and expediting the development of new drugs. Under the Bill, FDA funding would increase by $500 million. The Bill also provides for the authorization of new National Institutes of Health research grant funding, in the billions, including funding for Vice President Biden’s “moonshot” to cure cancer. Importantly, a proposed provision regarding reporting under the Sunshine Act was removed from the Bill. Specifically, the proposed provision would have exempted from the reporting requirements of the Physician Payment Sunshine Act payments from drug and device manufacturers to physicians for speaking at continuing medical education events and for contributing to medical textbooks, or medical journals.
In a final rule published today in the federal register (“Final Rule”), CMS announced numerous changes to the consolidated Medicare and Medicaid requirements for participation for long term care (LTC) facilities (42 CFR part 483, subpart B), which take effect on November 28, 2016 (see the March 7, 2016 blog for information about the July 16, 2015 proposed rule (“Proposed Rule”)). Much to the satisfaction of elder care advocates, the Final Rule provides that nursing homes may no longer require prospective nursing home residents to agree to binding arbitration. This strikes a blow at LTC facilities, which generally used arbitration as a tool to avoid incurring the onerous costs associated with litigation.
CMS’ position in the final rule isn’t shocking as it had expressed concern about the use of arbitration agreements in nursing homes in its Proposed Rule. Although no longer permissible for LTC facilities to use as a condition of admission, according to Andy Slavitt, CMS’ Acting Administrator, and Kate Goodrich, Director of the Center for Clinical Standards & Quality, “facilities and residents will still be able to use arbitration on a voluntary basis at the time a dispute arises.” However, such agreements will still need to be “clearly explained” to residents.
Nursing homes that have traditionally asked residents to sign binding arbitration agreements should revisit their admissions processes and implement revised policies and procedures to ensure compliance with the Final Rule, so that, beginning November 28, 2016, residents at such LTC facilities are no longer required to agree to binding arbitration. LTC facilities may also consider revising their policies and procedures to incorporate recommending the use of arbitration to residents following disputes that may arise, and to ensure that any such recommendations are clearly explained to their residents.
For more information regarding the voluntary use of arbitration agreements in the nursing home context, contact J. Nicole Martin, Dana Petrillo or any member of Cozen O’Connor’s health care law team.
Last week, the Third Circuit Court of Appeals held that the merger between Penn State Hershey Medical Center and PinnacleHealth System, the two largest hospitals in Harrisburg, Pennsylvania, may not move forward at this time. The Court of Appeals overturned the District Court’s (Middle District of PA) denial of the FTC’s and the Commonwealth of Pennsylvania’s request for a preliminary injunction, directing the District Court to enter a preliminary injunction blocking the merger “pending the outcome of the FTC’s administrative adjudication.”
In reaching its decision, the Court of Appeals held that the critical determination of the relevant market for a proper antitrust analysis should be defined primarily “through the lens of the insurers” and that it “was error for the District court to completely disregard the role insurers play in the healthcare market.” The Court of Appeals ruled that the relevant market was the four- county Harrisburg area. It found that the market was highly concentrated and that the combined hospitals would control 76% percent of the market. As a result the plaintiffs were found to have established a prima facie case that the merger “is presumptively anticompetitive.”
In rebuttal, the hospitals alleged, among other things, that, the merger would result in efficiencies leading to capital savings and enhance the hospitals’ efforts to engage in risk-based contracting, but the Court of Appeals found that these arguments failed to demonstrate tangible, verifiable benefits to consumers, and only constituted “speculative assurances.” It remains to be seen whether the hospitals will continue their pursuit of merger through the FTC’s administrative review process or abandon it.
This decision, like others involving hospitals that have preceded it, underscores the unique nature of the markets in which hospitals and other healthcare providers operate. These markets are not primarily defined by the direct impact of market consolidation upon the behavior of the ultimate consumers, the patients. Instead, the markets are defined by the patients’ purchasing surrogates, their health insurers.
For more information about this decision, contact Chris Raphaely, Nicole Martin or a member of Cozen O’Connor’s Health Law team
Federal Trade Commission, HIPAA, OCR / No Comments
On July 29, 2016, the Federal Trade Commission (“FTC” or “Commission”) reversed an FTC administrative law judge’s (“ALJ”) opinion which had ruled against the FTC, finding that the Commission had failed to show that LabMD’s conduct caused harm to consumers to satisfy requirements under Section 5 of the FTC Act. In reversing the ALJ, the FTC issued a unanimous opinion and final order that concluded, in part, that public exposure of sensitive health information was, in itself, a substantial injury.
The FTC initially filed a complaint against LabMD in 2013 under Section 5 of the FTC Act, alleging that the laboratory company failed to “provide reasonable and appropriate security for personal information on its computer networks,” which the FTC claimed lead to the data of thousands of consumers being leaked. The complaint resulted from two security incidents that occurred several years prior, which the FTC claimed were caused by insufficient data security practices.
In its opinion, the FTC concluded that the ALJ had applied the wrong legal standard for unfairness and went on to find that LabMD’s data security practices constituted an unfair act or practice under Section 5 of the FTC Act. Specifically, the Commission found LabMD’s security practices to be unreasonable – “lacking even basic precautions to protect the sensitive consumer information on its computer system.” The Commission stated that “[a]mong other things, [LabMD] failed to use an intrusion detection system or file integrity monitoring; neglected to monitor traffic coming across its firewalls; provided essentially no data security training to its employees; and never deleted any of the consumer data it had protected.” As a result of these alleged shortcomings in data security, medical and other sensitive information for approximately 9,300 individuals was disclosed without authorization.
Further, and perhaps more importantly, the Commission concluded that “the privacy harm resulting from the unauthorized disclosure of sensitive health or medical information is in and of itself a substantial injury under Section 5(n), and thus that LabMD’s disclosure of the [ ] file itself caused substantial injury.” Thus, contrary to the findings of the ALJ, the Commission essentially held that the mere exposure of sensitive personal and health information into the public domain may be enough to constitute a substantial injury for purposes of Section 5, without any proof that the information was ever misused.
As a result, the FTC ordered LabMD to establish a comprehensive information security program, obtain independent third party assessments of the implementation of the information security program for 20 years, and to notify the individuals who were affected by the unauthorized disclosure of their personal information and inform them about how they can protect themselves from identity theft or related harms.
Takeaway: While LabMD has announced its intention to appeal, the FTC’s decision reinforces its role as an enforcer of data security, even in the health care arena, where OCR has been the traditional enforcer of HIPAA and health care data breaches. Thus, in addition to OCR, health care entities must continue to monitor FTC enforcement actions to see if there are any additional or conflicting data security standards mandated by both agencies. Any companies handling PHI should, therefore, continue to ensure that their data security policies and procedures are being implemented and followed in accordance with industry standards. Inadequate security safeguards may contribute to data breaches resulting in government investigations and enforcement actions – not just by OCR, but the FTC as well.
For more information about the FTC’s opinion, contact Gregory M. Fliszar or a member of Cozen O’Connor’s Health Law team.
On August 18, 2016, the Secretary of Pennsylvania’s Department of Health (“DOH”), Dr. Karen Murphy, announced that the DOH has posted draft temporary regulations (“Regulations”) focusing on the 25 medical marijuana grower/processor permits that will become available under Pennsylvania’s Medical Marijuana Act (“Act”) that was passed last April.
The Regulations state the general application requirements for medical marijuana organizations, which requirements include detailed information about principals and financial backers of such organizations. Medical marijuana organizations include not just grower/processors, but also clinical registrants and dispensaries. The application requirements also contain a clear commitment to foster diversity. The Regulations establish procedures for promoting and ensuring that medical organizations foster diversity through participation of diverse groups in all aspects of the medical organization’s operations. This includes but is not limited to requiring each organization to have a diversity plan. Diverse groups are defined under the Regulations as “disadvantaged business[es], minority-owned business[es], women-owned business[es], service-disabled veteran-owned small business[es] or veteran-owned small business[es] that ha[ve] been certified by a third-party certifying organization.”
The Regulations also contain specific requirements for grower/processor permits. Application forms for permits will be posted on the DOH website in the future. Among the requirements is that a grower/processor notify DOH within six months of being issued an initial permit that it is ready, willing and able to begin production.
The Regulations prohibit executive level employees of the Commonwealth and their immediate family members from being employed by or holding an interest in medical marijuana organizations while employed by the Commonwealth and for one year thereafter.
The Regulations are not final and are open for public comment until August 26, 2016.
Although Pennsylvania joins 23 other states and the District of Columbia to legalize medical marijuana, marijuana is still classified as a Schedule I controlled substance by the U.S. Drug Enforcement Agency, and as such it remains a crime under federal law to grow, sell and/or use marijuana. Any content contained herein is not intended to provide legal advice in connection with the violation of any state or federal law. Although the Act provides for the legalization of medical marijuana in the Commonwealth of Pennsylvania, one should obtain legal advice with respect to any such compliance issues.
Stay tuned for details regarding an upcoming Cozen O’Connor webinar on these Regulations.
For more information about the Regulations or the Act, contact Chris Raphaely, J. Nicole Martin or another member of Cozen O’Connor’s Cannabis Industry Team.
In response to the increasing prevalence of ransomware cyber-attacks by hackers on electronic health information systems in hospitals and medical practices, the Department of Health and Human Services (HHS) Office for Civil Rights (OCR) announced on Monday July 11, 2016 its publication of new HIPAA guidance on ransomware (“Ransomware Guidance”). According to OCR:
Ransomware is a type of malware (or malicious software) that encrypts data with a key known only to the hacker and makes the data inaccessible to authorized users. After the data is encrypted, the hacker demands that authorized users pay a ransom (usually in a cryptocurrency such as Bitcoin to maintain anonymity) in order to obtain a key to decrypt the data.
Notably, the HIPAA Security Rule already requires implementation of security measures to help covered entities and business associates prevent the introduction of malware (e.g., ransomware) into their systems, and to implement policies and procedures to assist in responding to ransomware attacks. The Ransomware Guidance addresses, among other areas, how to implement security measures in order to prevent, mitigate the chances of, or even recover from ransomware attacks. Not surprisingly, conducting a risk analysis (or risk assessment) is at the core of covered entities and business associates implementing security management processes as required by the HIPAA Security Rule. The Ransomware Guidance further notes that maintaining an overall contingency plan, as required by the Security Rule, that includes disaster recovery planning, emergency operations planning and frequent backups of data can also help covered entities and business associates respond to and recover from malware infections, including ransomware attacks.
In addition, the Ransomware Guidance states that ransomware attacks against a covered entity or business associate can be considered a breach under the HIPAA Rules. Specifically, the Ransomware Guidance provides, “[w]hen electronic protected health information (ePHI) is encrypted as the result of a ransomware attack, a breach has occurred because the ePHI encrypted by the ransomware was acquired (i.e. unauthorized individuals have taken possession or control of the information), and thus is a ‘disclosure’ not permitted under the HIPAA Privacy Rule.” Therefore, unless it can be shown that there is a low probability that the PHI involved in the ransomware attack has been compromised based on the factors in the Breach Notification Rule, a breach is presumed to have occurred, which would trigger the applicable breach notification provisions.
Even before OCR’s publication of the Ransomware Guidance, in late June the Secretary of HHS sent a letter (“Letter”) to the attention of chief executive officers at health care entities addressing the threat of ransomware. The Secretary attached interagency guidance to the Letter containing best practices and mitigation strategies integral to combatting ransomware incidents.
Ransomware is immediately disruptive to the day-to-day operation of businesses, as seen by its impact earlier this year on health care systems like MedStar in Washington, D.C. and Hollywood Presbyterian Medical Center in Los Angeles (“HPMC”), resulting for example, in HPMC paying 40 Bitcoins (approximately $17,000) to regain control of its computer system. Although the Ransomware Guidance does not address whether payment or ransom should be paid to regain access to computer systems, the interagency guidance attached to the Letter advises against paying hackers because, among other reasons, paying a ransom doesn’t necessarily guarantee that an entity will regain access to its system. The Ransomware Guidance does recommend that an entity victimized by a ransomware attack contact its local FBI or United States Secret Service field office.
For more information about the Ransomware Guidance contact Gregory M. Fliszar, Ryan Blaney, J. Nicole Martin or a member of Cozen O’Connor’s Health Law team.
The White House recently released a guidance document for those in the precision medicine community to help ensure that participants’ data and resources remain secure. The document, titled “Precision Medicine Initiative: Data Security Policy Principles and Framework,” is meant to offer “security policy principles and a framework to guide decision-making by organizations conducting or participating in precision medicine activities” and is the result of a collaborative, interagency process featuring roundtable discussions with various security experts as well as a review of existing data security resources. Federal PMI agencies already have committed to integrating the framework into all PMI activities.
But the document is meant only to be a guideline – not a one-size-fits-all solution. It notes that those in the PMI community must constantly strive to use current best practices and should conduct their own “comprehensive risk assessment to identify specific security requirements and establish processes to continuously review and make improvements.”
The guidance emphasizes some overarching principles that anyone dealing with sensitive data should bear in mind when developing and implementing a data security plan:
- Keep pace with changing technology and new security threats.
- Tailor your data security plan to your unique circumstances.
- Be specific – think about your risks and put in writing how you will neutralize them.
- Have an independent third party review your plan.
- Without compromising security, be transparent about your plan to build trust among participants.
The document also offers specific suggestions with respect to identity proofing, user credentials and authentication, encryption and physical security, audits to detect anomalous activity, and incident response, among other topics. The White House also emphasizes the importance of ongoing participant education, as well as role-specific training for those who use PMI data.
On balance, the White House’s message to the PMI community is clear: Think hard about data security, think often about data security, and act vigilantly.
The guidance is available here: www.whitehouse.gov/sites/whitehouse.gov/files/documents/PMI_Security_Principles_Framework_v2.pdf.
For more information you can contact Ryan P. Blaney or another member of Cozen O’Connor’s Health Law team.
E-Cigarettes, Food and Drug Law, HHS, Regulations / No Comments
Days after the publication of the Food and Drug Administration’s controversial final rule regarding e-cigarettes (and other nicotine-delivering products), a company called Nicopure Labs LLC filed a lawsuit challenging it in the U.S. District Court for the District of Columbia. Nicopure seeks to have the rule vacated and declared unlawful, and has requested a preliminary injunction barring enforcement of the rule and prohibiting the FDA from taking any action under the rule pending resolution of the lawsuit.
The final rule, which will take effect on August 8, 2016 absent an injunction, grants the FDA authority to regulate electronic cigarettes and other vaping products and imposes rules on the industry that many insiders fear will leave it decimated. These rules include banning sales to anyone younger than 18 years of age, requiring extensive warning labels on packing and — most significantly — subjecting all products (even those currently on the market) to the FDA approval process and the FDA’s reporting and recordkeeping requirements. The price tag associated with the FDA approval process alone likely will pose an insurmountable barrier for the small vape shops, device manufacturers and e-liquid producers that currently drive most of the industry.
Nicopure, a Florida company that distributes battery-powered vaping devices and manufactures and distributes e-liquid, seeks to have the Final Rule vacated on several grounds. First, Nicopure alleges that the deeming rule defines “tobacco product” so broadly that it constitutes an unreasonable construction of the authority granted under the Administrative Procedure Act (APA). Additionally, Nicopure contends that the rule should be vacated as arbitrary and capricious in violation of the APA. Finally, Nicopure brings a constitutional challenge, arguing that the rule violates the First Amendment by prohibiting manufacturers from “making truthful and nonmisleading statements regarding vaping devices, e-liquids and related products” and from “engaging in other forms of protected expression, including by distributing free samples of vaping devices or e-liquids.”
As of this writing, the FDA has not responded to Nicopure’s complaint, but the case (Nicopure Labs, LLC v. Food and Drug Administration, et al.,1:16-cv-00-878) will no doubt be closely watched by the rule’s proponents and detractors alike.
For more information you can contact Ryan Blaney or another member of Cozen O’Connor’s Health Law team.
On April 17, 2016, Governor Wolf signed Act 16 of 2016, making Pennsylvania the 24th state (plus the District of Columbia) to legalize marijuana for medical use. The full text of the act is available here.
Physicians, not surprisingly, will play a vital role in making medical marijuana available to Pennsylvanians, while ensuring patient safety in the process. This is what they should know about Act 16: Continue reading…