If you don't respond to notifications of a leak, the problem doesn't go away – it gets worse
First Noted: 3 September 2014
Total Records: 5000+
Status: Not Monitoring for Follow Up (Not a client)
SLC Security Services LLC has noted that this medical establishment has failed to secure patient records. Observed were patient name and date of birth as well as specific medical information. SLC Security Services LLC has confirmed the information in this report.
Company Location and Contact Information:
Various Locations – Central NC
Additional Follow up: IT staff contacted us. We provided what information was known. The entity is not a client of SLC Security Services LLC. We are unable to verify if the company has resolved the issue at this time.
Update: As of 25 Sept 2014 this vulnerability still exist. We are seeing multiple PHI and PII from this source. The issue may be attributed to an outside source.
On October 31, SLC updated their report:
SLC Security Services LLC will begin notifying patients of Cape Fear Valley Health System (Fayetteville, NC) and WakeMed (Various Locations) after formal notification has been made to the entities formally.
We have previously contacted both entities and neither entity responded to our notification letters.
Well, it appears that WakeMed IT personnel did originally respond to the notification, but what happened after that? Perhaps SLC meant to say that WakeMed didn’t respond effectively as the information is still allegedly leaking?
As I commented previously in response to their report about Cape Fear Valley Health System (also in North Carolina, and also now having their patients notified by SLC): entities need to respond to notifications or things will get worse. Certainly, this is no way for patients to find out about a security problem.
Not only did Cape Fear Valley Health System allegedly not follow up on SLC’s report to them, they did not respond to an inquiry sent to them in September by PHIprivacy.net.
Neither Cape Fear Valley Health System nor WakeMed are listed on HHS’s public breach tool as having reported breaches to HHS.
Today, PHIprivacy.net asked SLC Security via Twitter if they have reported their findings to HHS. PHIprivacy.net also tweeted inquiries to WakeMed and Cape Fear Valley Health System to inquire whether they were aware of leaks and whether they were aware that their patients were being directly notified by SLC Security.
If I get responses, I will update this post.