Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals
Protected
health information (PHI) is rendered unusable, unreadable, or
indecipherable to unauthorized individuals if one or more of the
following applies:
- Electronic PHI has been encrypted as specified in the HIPAA
Security Rule by “the use of an algorithmic process to transform data
into a form in which there is a low probability of assigning meaning
without use of a confidential process or key” (45 CFR 164.304 definition
of encryption) and such confidential process or key that might enable
decryption has not been breached. To avoid a breach of the confidential
process or key, these decryption tools should be stored on a device or
at a location separate from the data they are used to encrypt or
decrypt. The encryption processes identified below have been tested by
the National Institute of Standards and Technology (NIST) and judged to
meet this standard.
- Valid encryption processes for data at rest are consistent with NIST Special Publication 800-111, Guide to Storage Encryption Technologies for End User Devices.1
- Valid encryption processes for data in motion are those which comply, as appropriate, with NIST Special Publications 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations; 800-77, Guide to IPsec VPNs; or 800-113, Guide to SSL VPNs, or others which are Federal Information Processing Standards (FIPS) 140-2 validated.
- The media on which the PHI is stored or recorded has been destroyed in one of the following ways:
- Paper, film, or other hard copy media have been shredded or
destroyed such that the PHI cannot be read or otherwise cannot be
reconstructed. Redaction is specifically excluded as a means of data
destruction.
- Electronic media have been cleared, purged, or destroyed consistent with NIST Special Publication 800-88, Guidelines for Media Sanitization such that the PHI cannot be retrieved.
| Covered entities and business associates must only provide the required notifications if the breach involved unsecured protected health information. Unsecured protected health information is protected health information that has not been rendered unusable, unreadable, or indecipherable to unauthorized persons through the use of a technology or methodology specified by the Secretary in guidance. This guidance was first issued in April 2009 with a request for public comment. The guidance was reissued after consideration of public comment received and specifies encryption and destruction as the technologies and methodologies for rendering protected health information unusable, unreadable, or indecipherable to unauthorized individuals. Additionally, the guidance also applies to unsecured personal health record identifiable health information under the FTC regulations. Covered entities and business associates, as well as entities regulated by the FTC regulations, that secure information as specified by the guidance are relieved from providing notifications following the breach of such information. ...read more |
| In today's digital landscape, data breaches are an unfortunate reality that businesses of all sizes must contend with. A single security lapse can lead to significant financial losses, reputational damage, and legal headaches. While prevention is paramount, having a clear and well-defined data breach reporting procedure is crucial for minimizing the fallout when the inevitable happens. This article will guide you through the essential steps your business needs to take. Why a Solid Breach Reporting Procedure is Non-Negotiable Data breaches are not just a concern for large corporations; they affect small and medium-sized businesses (SMBs) just as much, if not more so. A robust reporting procedure serves multiple critical purposes: Compliance with Regulations: Various data privacy regulations, like GDPR, CCPA, and others, mandate specific reporting timelines and requirements. Failure to comply can result in hefty fines and legal action.Minimizing Damage: Swift and decisive action can significantly limit the scope ...read more |
| Following a breach of unsecured protected health information, covered entities must provide notification of the breach to affected individuals, the Secretary, and, in certain circumstances, to the media. In addition, business associates must notify covered entities if a breach occurs at or by the business associate. Individual Notice Covered entities must notify affected individuals following the discovery of a breach of unsecured protected health information. Covered entities must provide this individual notice in written form by first-class mail, or alternatively, by e-mail if the affected individual has agreed to receive such notices electronically. If the covered entity has insufficient or out-of-date contact information for 10 or more individuals, the covered entity must provide substitute individual notice by either posting the notice on the home page of its web site for at least 90 days or by providing the notice in major print or broadcast media where the affected individuals ...read more |
|
December 2025
| Su | Mo | Tu | We | Th | Fr | Sa |
| 1 | 2 | 3 | 4 | 5 | 6 |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
|
Blog Home
Newest Blog Entries
1/21/25 Healthcare Data Breaches and Their Devastating Impact
1/21/25 Your Essential Guide to Data Breach Reporting Procedures
1/21/25 Understanding Your Obligations in Data Breach Reporting
11/16/22 Administrative Requirements and Burden of Proof
11/16/22 Notification by a Business Associat
11/16/22 Breach Notification Requirements
11/16/22 Unsecured Protected Health Information and Guidance
11/16/22 Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals
11/16/22 Definition of Breach
11/16/22 Breach Notification Rule
11/16/22 Notify Individuals
Blog Archives
January 2025 (3)
November 2022 (11)
Blog Labels
ePHI Data (1)
Health Care Data (1)
Data Breach Notification (6)
Data Breach Reporting (6)
|
