United States: HHS Releases Guidance On Privacy And Security Audits And Ransomware

If your organization operates in the healthcare industry, particularly if it qualifies as a covered entity or business associate under the Health Insurance Portability and Accountability Act (HIPAA), you may have noticed the recent flurry of activity from the US Department of Health and Human Services (HHS) Office for Civil Rights (OCR). First, HHS has recently launched phase two of its three-part audit of compliance with HIPAA privacy, security and breach notification rules. Second, HHS has provided guidance on ransomware which states that the presence of ransomware is a "security incident," which triggers breach disclosure obligations. Organizations subject to HIPAA should review its security incident procedures in light of the upcoming audits and the ransomware guidance and even entities outside the healthcare industry may also benefit from reviewing these guidance documents since other agencies and governmental authorities may follow HHS's lead in these interpretations.

HHS OCR Phase Two Audits Focus on Privacy, Security and Breach Notification Rules 

Last month, the HHS Office of Civil Rights officially launched phase two of its HIPAA audit program, sending out notification letters to 167 selected covered entities. In an effort to provide the selected covered entities with greater understanding of the audit process, HHS recently posted guidance on its website in the form of a FAQ. According to the FAQ, the purpose of these audits is to provide HHS "an opportunity to examine mechanisms for compliance, identify best practices, discover risks and vulnerabilities that may not have come to light through OCR's ongoing complaint investigations and compliance reviews, and enable us to get out in front of problems before they result in breaches."

The desk audit program has already begun. Those covered entities selected to participate in desk audits received letters from HHS on July 11th via email. HHS advises covered entities to check their spam and junk mail filter to ensure that communications from HHS are not inadvertently deleted. Although every covered entity is eligible for selection to participate in the desk audits, OCR is endeavoring to select entities that represent a wide range of health care providers, health plans, health care clearinghouses and (for the desk audits commencing in the fall) business associates. The current set of desk audits will examine compliance with specific requirements of HIPAA Privacy, Security and/or Breach Notification Rules. Those selected for audit will receive document request letters from HHS, outlining the specific subject of the audit.

How the desk audit program works. Per HHS's FAQ, the audit process for phase two will employ common audit techniques. HHS will send request to those entities selected for audit to provide certain specified documents and other data. Those audited entities will then be required to submit the requested documents and data through a new secure audit portal on HHS's website within 10 business days of the date of HHS's request. HHS auditors will review the submitted documentation and then share their draft findings with the audited entity. The audited entity will then have 10 business days to respond in writing to the HHS auditor's draft findings. The auditor will have 30 business days to complete the final audit report following the audited entity's response. The final audit report will describe how HHS conducted the audit, discuss any findings, and include the audited entity's responses to the draft findings. HHS will share a copy of the final report with the audited entity.

Onsite audits. Following the conclusion of all desk audits at the end of this calendar year, HHS will commence a third set of audits which will be onsite and examine a broader scope of requirements from the HIPAA rules than the desk audits. HHS has stated that entities selected for desk audits may be subject to these subsequent onsite audits. Entities selected for onsite audits will be notified via email of their selection and each onsite audit will be conducted over 3 to 5 days onsite, depending on the size of the entity. As with the desk audits, audited entities will have 10 business days to review and provide written comments to the draft findings of the HHS auditor, the auditor will complete a final audit report within 30 business days of the audited entity's response, and HHS will share a copy of the final report with the audited entity.

What happens after the audit. If an audit report indicates a serious compliance issue for an audited entity, HHS may initiate a compliance review. Although HHS will not post a listing of audited entities or the findings of an individual audit which clearly identifies the audited entity, HHS may be required to release audit notification letters and other information about these audits pursuant to a Freedom of Information Act request. HHS will aggregate data from all final reports and will use that information to determine what types of technical assistance should be developed and what types of corrective action would be most helpful. HHS will also develop tools and issue guidance to assist the industry in compliance with HIPAA requirements.

How to Prepare for an Audit

All covered entities and business associates should be prepared for an audit by HHS. Covered entities and business associates should review their privacy, security and breach notification policies and practices. In particular, they should confirm their compliance with the following HIPAA requirements:

  • Notice of Privacy Practices. Organizations must provide printed copies of the organization's current privacy  notice to patients and make this notice available on the organization's website. These notices must include their effective date as well as: (a) how the organization may use and disclose protected health information (PHI); (b) the patient's rights with respect to PHI and how the patient may exercise these rights, including how the patient may complain to the organization; (c) the organization's legal duties with respect to PHI, including a statement that the covered entity is required by law to maintain the privacy of PHI; and (d) a contact for further information about the organization's privacy policies.
  • Written HIPAA policies and procedures. An organization's HIPAA policies and procedures should conform with the administrative, technical and physical safeguards promulgated by HHS and should identify any risks or vulnerabilities in the organization's collection, storage or use of PHI. The organization should implement safeguards for all paper, electronic and verbal PHI, including PHI on mobile devices and storage media.
  • Risk assessment. Organizations should both conduct risk assessments and promptly implement appropriate security measures to address any identified risks. These assessments should include, at a minimum, an evaluation of the likelihood and impact of potential risks to PHI, documentation of the organization's security measures and, where required, the rationale for adopting such measures. Organizations must also conduct periodic follow-up security risk assessments to identify, address and document any deficiencies so as to maintain continuous, reasonable and appropriate security protections. And in light of HHS's new guidance on ransomware (discussed below), organizations should include the threat posed by ransomware attacks in their security assessments.
  • Breach Procedures. Organizations must implement notification policies and procedures that conform to HIPAA requirements for breaches of unprotected PHI (including HHS guidelines for breaches affecting 500 or more individuals). Organizations should conduct training for new employees and ongoing training for all staff on how to appropriately respond to a security breach.

Key Takeaways

  • Audit guidance is important for all covered entities and business associates. HHS has stressed that its guidance for phase two audits "should be helpful to audited entities as well as other covered entities and business associates seeking assistance with improving their compliance with these important requirements of the HIPAA Rules."
  • Your organization may still be selected for an audit. Phase two audits, including both desk audits and onsite audits, will continue throughout this year. Even if your organization is not selected to participate in a phase two audit, phase three audits are just around the corner.
  • Organizations should be prepared for an audit. All covered entities and business associates should carefully review their policies and procedures for compliance with HIPAA rules. Particular attention should be paid to compliance with the Security Rule.

Guidance on Ransomware

In addition to the FAQ on the phase two desk audits, HHS Office of Civil Rights released important new guidance on how to protect against and respond to ransomware attacks. Citing cyber-attacks on electronic health information systems as "one of the biggest current threats to health information privacy," the new guidance issued by HHS in July 2016 reinforces activities required by HIPAA to help organizations prevent, detect, contain and respond to ransomware.

And while only organizations subject to the HIPAA Security Rule are obligated to comply with this guidance, other entities which may be targeted by ransomware can also benefit from reviewing these requirements since it is likely that other agencies and governmental authorities will follow HHS's lead.

What is ransomware? Ransomware is a type of malicious software that prevents or limits users from accessing their own system, either by locking the system's screen or by encrypting the user's files. Users are then forced to pay a ransom (hence the term "ransomware") in order to regain access to their system. Though ransomware is a serious threat to any organization, for healthcare entities who deal with medical emergencies on a daily basis, even a few hours of system downtime can be potentially life-threatening. These healthcare entities are then often forced to pay the ransom, thereby encouraging future attacks on similar organizations. And there has indeed been a sharp increase in the number of ransomware attacks on hospitals and other covered entities over the past few years. The HHS Guidance cites to a recent US Government interagency report which indicates that there have been 4,000 daily ransomware attacks since early 2016, compared to 1,000 daily ransomware attacks reported in 2015. With the threat of ransomware growing, OCR has issued new guidance to better protect patients.

Ransomware attacks are security incidents. The key takeaway from OCR's guidance is that ransomware attacks will generally be considered a security incident under the HIPAA Security Rule. A breach is presumed to have occurred unless the covered entity or business associate can demonstrate a low probability that protected health information has been compromised. Thus, organizations subject to the HIPAA Security Rule that suffer from a ransomware attack must comply with the Security Rule breach notification requirements, including the requirement to notify the affected individuals, the Secretary of HHS and in certain cases the media if it affects more than 500 individuals.

Breach notification requirements may be avoided in certain cases. As noted above, HHS's guidance does allow for organizations to demonstrate that there is a low probability of protected health information having been compromised, thereby avoiding the breach notification obligations. To do this, these organizations must conduct a risk assessment by considering four factors: (a) the nature and extent of the protected health information involved; (b) the unauthorized person who used the PHI or to whom the disclosure was made; (c) whether PHI was actually acquired or viewed; and (d) the extent to which the risk to PHI has been mitigated. Furthermore, HHS's guidance encourages organizations "to consider additional factors, as needed, to appropriately evaluate the risk that the PHI has been compromised." This risk assessment must be thorough, completed in good faith and reach conclusions that are reasonable given the circumstances. Additionally, organizations must maintain sufficient documentation supporting their conclusions.

Organizations must prepare for attacks. In addition, HHS's guidance also requires organizations to proactively implement policies and procedures that will help it respond to and recover from a ransomware attack. These policies and procedures include: (a) implementing a security management process, which includes conducting a risk analysis to identify threats and vulnerabilities to ePHI and implementing security measures to mitigate or remediate those identified risks; (b) implementing procedures to guard against and detect malicious software; (c) training users on malicious software protection so they can assist in detecting malicious software and know how to report such detections; and (d) implementing access controls to limit access to ePHI to only those persons or software programs requiring access.

OCR further reminds organizations that "the Security Rule includes requirements for all covered entities and business associates to conduct an accurate and thorough risk analysis of the potential risks and vulnerabilities to the confidentiality, integrity and availability of all of the ePHI the entities create, receive, maintain or transmit and to implement security measures sufficient to reduce those identified risks and vulnerabilities to a reasonable and appropriate level." It is therefore incumbent on organizations to address the threat posed by ransomware in their risk assessments. It is not enough to simply respond to ransomware and report them as security incidents; organizations must be prepared to prevent, detect and contain them as security threats.

Key Takeaways

  • Ransomware attacks pose a serious threat, and they are increasing. Ransomware attacks are often successful and they are increasingly targeting hospitals and other entities in the healthcare industry. For many covered entities and business associates, the question is "when" and not "if" they will be attacked with ransomware.
  • Ransomware attacks are considered a security incident under the HIPAA Security Rule. When a covered entity or business associate suffers a ransomware attack, a breach is presumed to have occurred unless that organization can demonstrate a low probability that protected health information has been compromised. This will trigger a requirement for the victim entities to notify individuals whose information is involved in the breach "without unreasonable delay" and in no case later than 60 days following the discovery of the breach. Breach notification rules may also require notice to the HHS Secretary and the media.
  • Organizations must prepare for attacks. HHS's new guidance requires all covered entities and business associates to implement policies and procedures addressing ransomware attacks. All such organizations should carefully review their policies and procedures to ensure compliance with this new guidance.
  • Organizations in all sectors can benefit from reviewing the HHS requirements. Once a major agency like HHS defines an obligation to detect, prevent, combat and report ransomware attacks, other regulatory agencies may also follow suit in issuing similar guidance.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.