{"id":23533,"date":"2017-10-14T14:03:32","date_gmt":"2017-10-14T19:03:32","guid":{"rendered":"http:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/?p=23533"},"modified":"2019-02-27T12:09:19","modified_gmt":"2019-02-27T17:09:19","slug":"security","status":"publish","type":"post","link":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/2017\/10\/14\/security\/","title":{"rendered":"Website Update: New Security Features Go Live!"},"content":{"rendered":"

I get lots of excellent questions about heart valve disease from our patient community. And, I do my best to answer those questions to help educate and empower people just like you.<\/p>\n

Recently, I\u2019ve received a different type of excellent question specific to our website. That question is, \u201cIs HeartValveSurgery.com secure?\u201d<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

The simple answer to this question is \u201cYes\u201d. \u00a0This website is designed to be secure. \u00a0The long answer to this question is much more complex. \u00a0That said, I wanted to share with you several updates specific to the security that protects you, our community and the information shared at this website.<\/p>\n

<\/p>\n

First, I want you to know that I am personally committed to making every member of this community feel safe. In a world full of cyber attacks and hacking, I have spent a good amount of time learning about security. \u00a0When I realized that I did not have all the skills needed to keep up with the changes in website security, I hired consultants, programmers and security experts to ensure that HVS is taking all steps needed to protect this community.<\/p>\n

Second, in January, 2017, I hired a team to audit and evaluate the security of HVS. During the audit, I learned there were opportunities to enhance the security of HVS \u2013 specifically around HIPAA.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Over the next 3 months, we embedded several new physical and administrative controls to guard information that was shared across HVS. The results of this \u201cJourney to HIPAA Compliance\u201d were fantastic. On March 6, we received an attestation letter from a security consulting firm that our website was HIPAA compliant.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Did I stop there to ensure the security of HVS?<\/p>\n

Heck no!<\/p>\n

After we received the attestation letter for HIPAA compliance, I decided it was time to put the entire website in a secure, encrypted environment.<\/p>\n

You might think this is no big deal. You might think that putting an SSL certificate across HVS is easy to do. However, this migration from a \u201cHTTP\u201d to a \u201cHTTPS\u201d was a monster! \u00a0The reason is that HVS is 11 years old and has 10,000+ pages of information. There are many different systems that power the website you see. These systems \u201ctalk\u201d to each other. So, if there is an issue with one system, the other system might get confused. If that happens… problems occur and the website breaks. \u00a0Not good.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

For this reason, we needed to ensure that all steps were taken to ensure a smooth, effective migration. As a result, I hired another consultant to coach me and our programming team through this process. In total, we worked on this migration for over two months. We had three separate check-lists to guide this migration before, during and after the shift to a secure server system.<\/p>\n

Today, I am happy to report that the migration to a site-wide HTTPS environment is complete. To see this, simply check your browser URL address. You will notice that every single page on this website is now in a secure \u201cHTTPS\u201d mode. (If you didn\u2019t know, that extra \u201cS\u201d means secure.)<\/p>\n

Am I done enhancing the security of HVS? <\/p>\n

The answer is no.<\/p>\n

There will always be new and different strategies to make this website more secure. That said, I hope this post helps you learn about the efforts and resources I am extended to provide you a secure environment to get educated and empowered. If you have any questions, please let me know.<\/p>\n

Keep on tickin!
\nAdam<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":23540,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[63],"tags":[],"class_list":["post-23533","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-adams-updates"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/posts\/23533","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/comments?post=23533"}],"version-history":[{"count":0,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/posts\/23533\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/media\/23540"}],"wp:attachment":[{"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/media?parent=23533"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/categories?post=23533"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.heart-valve-surgery.com\/heart-surgery-blog\/wp-json\/wp\/v2\/tags?post=23533"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}