• 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

Case study: Breach of PHI by a Business Associate

July 12, 2014 Posted by Art Gross HIPAA, Risk Assessment No Comments

Crime Scene

One of our medical practice clients contacted us regarding a breach of Protected Health Information (PHI) by their billing company. The client received a letter from the billing company’s attorney stating that 60 of the client’s patients had their information breached when the billing company’s file server was compromised. The PHI included treatment reports, name, address and social security numbers.

This situation offers some valuable lessons for both covered entities and business associates.

Responsibility

While it was the billing company that suffered the breach, ultimately it is the medical practice’s patients who had their information compromised. This brings up a huge point that the actions or inactions of a business associate can have a major impact and liability to a covered entity (medical practice). Signing a HIPAA business associate agreement is a requirement but does not guarantee that a covered entity is protected from business associate related breaches. It is very important to ensure that business associates are protecting PHI. While it is impossible to police the actions of all business associates, a good starting point would be to ask all business associates a few basic questions:

  • Have you performed a security risk assessment and implemented additional security to protect PHI?
  • Do you have policies and procedures on how to protect PHI?
  • Have you trained your employees on protecting PHI?

The above questions won’t necessarily stop a breach but if the business associate answers no to any of the questions you should be concerned that there is a higher chance that the business associate might cause a breach of PHI.

It is important that any business associate agreement (BAA) provide protections in the event of a breach. The BAA should define responsibilities including financial responsibilities, reporting responsibilities, etc.

Notification to Patients

The letter that the client received regarding the breach stated that the breach was discovered 52 days ago. This information is very important and very troubling. The HIPAA Breach Notification Rule states that individuals affected by a breach must be notified within 60 days of discovery of the breach. This only provided the client with 8 days to notify the patients. This is not a lot of time to react, plan and respond to the breach notification requirements.

The Office of Civil Rights (OCR) gives guidance into the reporting responsibilities after the discovery of a breach of PHI.

Emphasis added

Notifying Individuals
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 likely reside. The covered entity must include a toll-free phone number that remains active for at least 90 days where individuals can learn if their information was involved in the breach. If the covered entity has insufficient or out-of-date contact information for fewer than 10 individuals, the covered entity may provide substitute notice by an alternative form of written notice, by telephone, or other means.

These individual notifications must be provided without unreasonable delay and in no case later than 60 days following the discovery of a breach and must include, to the extent possible, a brief description of the breach, a description of the types of information that were involved in the breach, the steps affected individuals should take to protect themselves from potential harm, a brief description of what the covered entity is doing to investigate the breach, mitigate the harm, and prevent further breaches, as well as contact information for the covered entity (or business associate, as applicable).

With respect to a breach at or by a business associate, while the covered entity is ultimately responsible for ensuring individuals are notified, the covered entity may delegate the responsibility of providing individual notices to the business associate. Covered entities and business associates should consider which entity is in the best position to provide notice to the individual, which may depend on various circumstances, such as the functions the business associate performs on behalf of the covered entity and which entity has the relationship with the individual.

It should be noted that the business associate did offer to notify the affected patients for the client. The question that you should ask yourself is this:

If you are delivering bad news (breach of their PHI) to a patient or customer do you want a 3rd party to tell them or should you tell them yourself?

Notification to OCR

Not only does a covered entity need to ensure that the affected patients are notified but they must also notify OCR of the breach.

Emphasis added

Notice to the Secretary
In addition to notifying affected individuals and the media (where appropriate), covered entities must notify the Secretary of breaches of unsecured protected health information. Covered entities will notify the Secretary by visiting the HHS web site (http://www.hhs.gov/ocr/privacy/hipaa/administrative/breachnotificationrule/brinstruction.html) and filling out and electronically submitting a breach report form. If a breach affects 500 or more individuals, covered entities must notify the Secretary without unreasonable delay and in no case later than 60 days following a breach. If, however, a breach affects fewer than 500 individuals, the covered entity may notify the Secretary of such breaches on an annual basis. Reports of breaches affecting fewer than 500 individuals are due to the Secretary no later than 60 days after the end of the calendar year in which the breaches are discovered.

In this case there were only 60 patient records breached so the client would need to report to OCR within 60 days after the calendar year.

Stressful Times

It goes without saying that both the client and the business associate are dealing with a very stressful event. Some of the potential outcomes of this breach include:

  • Patients’ information being used for illegal activity that causes harm to the patient
  • Patients being upset and leaving the practice (which results in lost revenue)
  • Clients of the billing company leaving due to the breach (which results in lost revenue)
  • The medical practice and or billing company having their reputation damaged because of the breach
  • OCR investigating the breach and handing out HIPAA related fines that be financially damaging (keep in mind the 60 patients are only for this one client. This breach could be much larger and affect a lot more patients)

HIPAA/Cyber Insurance

This case is a text book example of why all organizations need to have some sort of insurance to protect against breaches. In this case the covered entity did nothing to cause the breach yet they will have to deal with breach related expenses (legal, postage, toll-free number, answering patient questions/concerns, credit monitoring services, etc.). Depending on the total amount of patient records breached, the business associate is looking at very large breach related expenses including possible HIPAA related fines.  Without insurance to pay or offset these expenses, the breach could be financially damaging to both organizations.

Ask yourself these questions:

  • If you or one of your business associates caused a breach and the overall expense was $150,000 or $450,000 and you did not have insurance to cover the expenses, how would you pay for it?
  • Could the breach related expenses put you out of business?

This example shows why it is critical to have enough insurance to cover or offset breach related expenses. Don’t assume your malpractice or general liability insurance will cover these expenses. Most policies do not cover breach related expenses. It is important to evaluate your insurance and make sure that you have the appropriate coverage to protect your organization. The good news is that HIPAA/Cyber insurance policies are generally very affordable.

Hopefully this example gives you more insight into what happens when PHI is breached. It should show you that PHI can be breached by both covered entities and business associates. It is critical to ensure that your organization and your business associates are properly protecting PHI.

HSN MU Risk Assessment
 
  

Tags: BreachBusiness AssociateHIPAA FineHIPAA Insurance
No Comments
Share
0

You also might be interested in

Huge security breach fines coming in 2011

Feb 21, 2011

According the Health Data Management magazine, The HHS Office for[...]

Deeper look at the $4.3 million HIPAA fine

Feb 23, 2011

The Health and Human Services’ (HHS) Office of Civil Rights[...]

OCR shows its serious about HIPAA enforcement

Mar 11, 2011

The Office for Civil Rights (OCR) showed once again that[...]

Leave a Reply Cancel Reply

Recent Posts

  • How to Use Microsoft 365 Securely in a Shared Office Environment
  • Why Your HIPAA Policies Shouldn’t Live in a Drawer
  • Is Your Staff Prompting AI Safely? What You Need to Know Now
  • One Click, $600K Lost: The HIPAA Lesson You Can’t Ignore
  • HIPAA Enforcement: What Every Healthcare Practice Needs to Know

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

  • June 2025
  • 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