HITECH Act Breach Notification StandardsFebruary 2010 By: David M. Hyman, Daniel A. Schwartz, Nicole DiMaria, and Nicole Martin Wolff & Samson Health Law Alert This is the third in a series of three HITECH alerts. This Wolff & Samson Health Law Alert is the third in a three-part series regarding the Health Information Technology for Economic and Clinical Health Act (the “HITECH Act” or “HITECH”), which significantly broadens the scope of existing health information privacy and security requirements. The first HITECH alert addressed certain provisions of HITECH that create new and revise or expand existing privacy requirements with respect to protected health information (“PHI”) under the regulations implementing the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”). The second HITECH alert reviewed sections of HITECH that affect business associates of HIPAA covered entities and business associate agreements. This latest alert summarizes the HITECH Breach Notification Standards, which impose certain additional obligations on covered entities and business associates in the event unsecured PHI is breached. Enforcement Will Begin February 22, 2010 – Necessary and/or Suggested Steps for ComplianceAs a result of rules promulgated on August 24, 2009, the United States Department of Health and Human Services (“HHS”) will begin imposing penalties for noncompliance with the Breach Notification Standards on February 22, 2010. If they have not done so already, covered entities must incorporate the Breach Notification Standards into their existing HIPAA compliance infrastructure. For instance, covered entities are required to implement the same type of policies and procedures, training programs and other administrative elements relating to the Breach Notification Standards that are mandated under the HIPAA privacy rules. While business associates do not appear to be legally mandated to implement such administrative requirements, in light of their direct compliance obligations under the Breach Notification Standards (as further discussed below), we recommend business associates also implement policies, procedures and training programs to ensure their compliance. In addition, as discussed in the second Alert of this series, we recommend that covered entities and business associates amend their business associate agreements to delineate their respective legal obligations under the Breach Notification Standards and agree to certain communication terms to ensure their obligations will be satisfied in the event of a breach. Basic Elements of the Breach Notification StandardsThe Breach Notification Standards require the provision of notice to affected individuals, HHS and in some cases the media, in the event of a “breach” of “unsecured” PHI. As further detailed below, the Breach Notification Standards prescribe rules with respect to the methods, content and time period for providing such notice. Definition of “Breach”The term “breach” generally means “the acquisition, access, use or disclosure of protected health information in a manner not permitted under [the HIPAA privacy rules] which compromises the security or privacy of the protected health information.” There are scenarios that are specifically excluded from the breach definition, such as in the case of an unintentional acquisition of PHI by the employee of a covered entity or business associate.
Definition of “Unsecured Protected Health Information”The Breach Notification Standards only apply to breaches of “unsecured protected health information,” which is defined as PHI “that is not rendered unusable, unreadable, or indecipherable to unauthorized individuals through the use of a technology or methodology specified by the Secretary [of HHS].” HHS issued guidance in April 2009 regarding the technologies and methodologies, such as encryption, that can be used to secure PHI and avoid the occurrence of a “breach” of such PHI; this guidance is available at: http://www.hhs.gov/ocr/privacy/hipaa/administrative/breachnotificationrule/index.html. The Notice Requirements – Who Must Provide It, When It Must Be Provided, and What It Must Include
When a Breach Is Considered “Discovered”A breach is generally considered “discovered” by a covered entity or business associate as of the first day the breach is known, or by exercising reasonable diligence would have been known, to the entity. A breach is generally “known” by an entity when a member of its workforce or an agent (other than the person committing the breach) has or should have knowledge of the breach. The “discovery” provisions can have a substantial affect on the nature of the relationship between a business associate and covered entity, particularly when a business associate is an “agent” of the covered entity. In such a case, the business associate’s discovery of a breach of unsecured PHI will be imputed to the covered entity and the timeframe within which the covered entity must make its required notification(s) will begin on the day the business associate discovered the breach. Whether or not a business associate is an “agent” of a covered entity will depend on the circumstances surrounding the engagement and the nature of the business associate relationship. Covered entities and business associates should consider this aspect of the Breach Notification Standards and whether a business associate is properly categorized as an “agent” when entering into and amending business associate agreements. Burden on Covered Entities and Business Associates to Demonstrate Compliance - Documentation of Risk Assessments and/or Provision of Required Notifications Should be MaintainedCovered entities and business associates have the burden of demonstrating that an impermissible use or disclosure of PHI did not constitute a breach or that all required notifications were made. Therefore, the provision of any required notifications or the risk assessment resulting in the determination that such notifications are not required should be documented in writing. ■ ■ ■ Related Practices |
© 2012 Wolff & Samson PC All Rights Reserved.