• Blog
  • Services
    • PHIshMD Ongoing Training
    • HIPAA Compliance
    • Discover Vulnerabilities to Patient PHI
  • Store
    • HIPAA Secure Now Service Store
  • Contact Us
    • Sales Inquiry
    • Customer Support
  • Resources
    • Free Healthcare Security Check Up Quiz
    • HIPAA Compliance Requirements | A Guide
    • Webinars & Downloadable Content
    • Use our free Breach Cost Calculator
    • HIPAA Secured Seal
    • In-Email Training & Analysis | Catch Phish

Call us at: 877-275-4545

Client or Partner? Login here
HIPAA Secure Now!HIPAA Secure Now!
  • Blog
  • Services
    • PHIshMD Ongoing Training
    • HIPAA Compliance
    • Discover Vulnerabilities to Patient PHI
  • Store
    • HIPAA Secure Now Service Store
  • Contact Us
    • Sales Inquiry
    • Customer Support
  • Resources
    • Free Healthcare Security Check Up Quiz
    • HIPAA Compliance Requirements | A Guide
    • Webinars & Downloadable Content
    • Use our free Breach Cost Calculator
    • HIPAA Secured Seal
    • In-Email Training & Analysis | Catch Phish

Guilty until proven innocent regarding HIPAA breaches

May 30, 2013 Posted by Art Gross HIPAA No Comments

The HIPAA Omnibus Final Rule brings a significant change to the HIPAA/HITECH Breach Notification Rule. Prior to the HIPAA Omnibus Rule, organizations were required to perform a risk assessment to determine if there was likely harm to a patient resulting from a privacy breach. Determining if the breach resulted in harm was referred to as the “harm threshold”.

Changes under the HIPAA Omnibus Rule

As mentioned, the HIPAA Omnibus Rule has significantly changed what is and what isn’t a reportable breach. The “harm threshold” has been replaced with a more objective risk based approach. The Omnibus Rule now defaults to a reportable breach unless the organization can prove otherwise. In other words, you are guilty unless you can prove you are innocent. You have to report a breach unless you can prove that you do not have to report the breach.

The “hard threshold” allowed for a subjective analysis of whether a breach would pose harm to a patient. This allowed organizations to determine if they should or should not report a breach of patient information. Let’s look at the factors that organizations need to look at under the Omnibus Rule.

4 Factors

  1. The nature and extent of the protected health information (PHI) involved, including the types of identifiers and the likelihood of re-identification
  2.  

  3. The unauthorized person who used the protected health information or to whom the disclosure was made
  4.  

  5. Whether the protected health information was actually acquired or viewed
  6.  

  7. The extent to which the risk to the protected health information has been mitigated

Taking a look at each of the 4 factors

  1. The first factor to consider is the nature and extent of PHI involved. What information was involved in the breach? What names, social security numbers, credit card information, etc were included? If it was internal patient codes that didn’t disclose names of patients, what is the likelihood that the other information can be used to identify a patient?
  2.  

  3. The second factor to consider is who was the information disclosed to?  Was it another physician that was accidentally sent the wrong patient’s records? Was it hackers looking to sell patient information on the black market?  
  4.  

  5. The third factor and probably the most significant is whether the information was actually acquired or viewed. This is where an organization is guilty until proven innocent. Let’s take the scenario of a laptop that is lost or stolen. The laptop contained patient information and was NOT encrypted. It is the organization’s responsibility to prove that the patient data on the lost laptop was not accessed or viewed. Unless the organization can retrieve the lost or stolen laptop AND prove forensically that the information on the computer was not accessed, they have to assume it was a breach. The chance of retrieving a lost laptop and proving that the data was not accessed is very remote. This will cause a lot more breach notifications as the result of lost or stolen laptops, smartphones, USB  drives, etc.  It should be noted that if the device is encrypted then the breach does NOT need to be reported regardless of whether the device is retrieved or not. Encryption continues to be a “safe harbor” that does not require notification. 
  6.  

  7. The fourth factor looks at how a breach was been handled and mitigated. An example is that an incorrect patient record was sent via email to another physician. The employee realized their mistake and called the physician’s office and spoke with person that the email was sent to. The person assured the employee that the email would be deleted. In that case there is a low probability that the information would actually be used or shared.

More Breach Notifications 

The changes to breach notifications as a result of the HIPAA Omnibus Rule is significant. Organizations have to take a much more objective approach to breaches and notifications. As demonstrated, organizations are now guilty until they can prove themselves innocent. This will result in a lot more breach notifications being sent to patients and reported to HHS/OCR.

Find out more about the HIPAA changes under the Omnibus Final Rule. Download our 7 Things You Must Know About HIPAA Security. It’s packed with very useful information!

Tags: Breach
No Comments
Share
0

You also might be interested in

Fear and destroy USB drives!

Fear and destroy USB drives!

Apr 8, 2011

In what appears to be a reoccurring story, another hospital[...]

Dropbox is not HIPAA compliant

Apr 29, 2011

An article over at KevinMD.com on using Dropbox to store[...]

5 easy steps to protecting patient data

May 1, 2011

Medical practices are not only tasked with protecting their patient’s[...]

Leave a Reply Cancel Reply

Recent Posts

  • One Click, $600K Lost: The HIPAA Lesson You Can’t Ignore
  • HIPAA Enforcement: What Every Healthcare Practice Needs to Know
  • Simplifying HIPAA for Small Practices
  • Staying Ahead of AI-Driven Cyber Threats: How HIPAA’s 2025 Security Rule Updates Help
  • AI in Healthcare: Opportunity or Risk? The Answer is Both

Recent Comments

  • Why Your Practice Needs an AI Acceptable Use Policy - HIPAA Secure Now! on How Gen AI is Transforming Everyday Healthcare
  • HIPAA Security Rule Changes 2025: What Your Healthcare Practice Must Know Now - The HJN Blog on 2025 HIPAA Security Rule Updates
  • Too Small for an OCR Audit? 2025 Proves Otherwise - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare
  • 2025 HIPAA Security Rule Updates - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare
  • Overcoming HIPAA Compliance Challenges for Small Healthcare Practices - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011

Categories

  • Backup & Disaster Recovery
  • Business Associates
  • Client News
  • Download
  • Healthcare Industry
  • HIPAA
  • HIPAA Audits
  • HIPAA Violations
  • HSN News
  • Legal
  • MACRA
  • Policies and Procedures
  • Press Release
  • Remote Workforce
  • Risk Assessment
  • Scams
  • Security
  • Security Reminders
  • Security Training
  • Telehealth
  • Uncategorized
  • Webinar
  • Website

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Contact Us

  • HIPAA Secure Now
  • 55 Madison Ave, Suite 400 Morristown, NJ 07960
  • (877) 275 - 4545
  • info@hipaasecurenow.com

Find us on Social Media

LEGAL

Privacy Policy

Terms of Service

Subscribe to our Newsletter

  • Hidden

© 2025 · HIPAA Secure Now!

Prev Next