{"id":36041,"date":"2019-02-21T09:16:19","date_gmt":"2019-02-21T14:16:19","guid":{"rendered":"https:\/\/sciencebusiness.technewslit.com\/?p=36041"},"modified":"2019-02-21T09:16:19","modified_gmt":"2019-02-21T14:16:19","slug":"how-your-health-care-facility-can-survive-a-security-breach","status":"publish","type":"post","link":"https:\/\/technewslit.com\/sciencebusiness\/?p=36041","title":{"rendered":"How Your Health Care Facility Can Survive a Security Breach"},"content":{"rendered":"

– Contributed content –<\/em><\/p>\n

\"Medical
(Darko Stojanovic, Pixabay)<\/figcaption><\/figure>\n

21 Feb. 2019. Information leaks are bad news in any business<\/a>. They\u2019re a sure way to lose customer trust and throw your reputation into disrepute. And, that\u2019s when the worst information you\u2019re leaking is customer emails. When it comes to health care, many patients say that info leaks like these are unforgivable. When your private medical history gets into the wrong hands, it can be more than a little unsettling. It can feel like the worst violation. And, it all happened in the hands of your company.<\/p>\n

But, we\u2019re here to tell you that a breach doesn\u2019t need to spell the end of your health care facility altogether. In an ideal world, of course, an incident like this would never happen. The fact that it has actually leaves you on the wrong side of the law. But, once you\u2019ve paid your fines<\/a> and done your due, there\u2019s no reason you can\u2019t build yourself back up. All you need to do to make it happen is take care of the following.<\/p>\n

Make it up to the people involved<\/b><\/p>\n

First, remember that paying your legal fine doesn\u2019t make up for what happened. You still need to make an effort to address the people affected. It was their details you let loose, after all, and it\u2019s them you need to work hardest on. Of course, accountability<\/a> is always tricky in instances like these. The temptation is not to apologize to keep your hands clean. But, that\u2019s never going to help you get going again. Remember, too, that you\u2019ve already paid your dues. There\u2019s nothing to lose by saying sorry or offering compensation to the injured parties. There is, however, a whole load to lose by ignoring them.<\/p>\n

Provide proof that things have changed<\/b><\/p>\n

Of course, no one\u2019s going to rely on your services now unless you can prove that things have changed. As always in business, your best way of doing this is to provide certification in your favor. Being able to prove things like your SOC 2 compliance<\/a> can make a huge difference to the way customers approach you. Displaying reports like these clearly at your front desk and on your website can work in your favor. That way, future clients can rest easy that you\u2019re doing what you can. Speaking of which, you also need to\u2026<\/p>\n

Make sure it never happens again<\/b><\/p>\n

Once bitten, twice shy. While it\u2019s possible to crawl back from one security breach, you won\u2019t be able to do the same again. In many ways, you could say that this is your last chance. Far from just getting the certification, you also need to make 100% sure you\u2019re doing everything to avoid repeat breaches. That means going beyond just your legal requirements. You may find, for instance, that online booking<\/a> reduces the risk of leaked information. You may also want to send your reception team on confidentiality courses. These steps are above and beyond the call of duty, and they\u2019re sure to see you back at the top in no time.<\/p>\n

Editor’s note: The opinions in this post are the contributor’s and not those of Science & Enterprise.<\/em><\/p>\n

*\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0 *<\/p>\n","protected":false},"excerpt":{"rendered":"

When your private medical history gets into the wrong hands, it can be more than a little unsettling.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[132,78],"class_list":["post-36041","post","type-post","status-publish","format-standard","hentry","category-regulations","tag-contributed","tag-software"],"_links":{"self":[{"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/posts\/36041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=36041"}],"version-history":[{"count":1,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/posts\/36041\/revisions"}],"predecessor-version":[{"id":36042,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=\/wp\/v2\/posts\/36041\/revisions\/36042"}],"wp:attachment":[{"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=36041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=36041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/technewslit.com\/sciencebusiness\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=36041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}