TriPoint Healthcare Solutions

Advising, Educating, and Operationalizing Privacy and Security in Healthcare

  • About TriPoint Healthcare Solutions
    • Meet Danika
    • Client Tesimonials
  • Services
  • Blog
  • HIPAA Resources
  • Contact Us
  • Past Presentations

Archives for February 2015

You Are a Business Associate – Sign This: The Tangled Web Created with Business Associates

February 20, 2015 by Danika Brinda Leave a Comment

Image of business partners handshaking over business objects onThe new complicated world of understanding Business Associate, Subcontractors, and Agents.

Scenario: A financial planner contacted me concerned as he just received an e-mail that a business associate agreement needs to be signed in order to work with the company that processes applications for life insurance.  The financial planner didn’t know what a business associate under HIPAA regulations meant and was getting ready to just sign the document and return it.  Thankfully, the financial planner reached out for clarification, I quickly advised against just signing the agreement and pushing back against the company to determine why they thought he was a business associate.  While dialogue between the insurance company and financial planner is still occurring, through evaluation of the work between the financial planner and insurance company (and client), it is clear that the financial planner WOULD NOT be a business associate under the HIPAA regulations. 

Since the final Omnibus Rule was effective in 2013, a new wave of confusion and challenge on who is considered a business associate and who is not considered a business associate has come to light.  To protect themselves, organizations (Covered Entities and Business Associates) have been requiring that all third parties that they work with in any business aspect sign a business associate agreement.  Even if the third party doesn’t meet the definition of a business associates or physically have interaction with protected health information, a blanket coverall approach to get signed business associate agreement is being applied.  To create more confusion, many third party organizations are just signing business associate agreements not truly knowing or understanding what it actually means and the implications of becoming a business associate.  Is this the best approach or taking the business associate agreement process to the EXTREME?

MY OPINION (Not Advice): Not everyone is a business associate and should sign a business associate agreement.  Proper review and governance over the management of business associates within covered entities and business associate organizations needs to be completed.  Additionally, the third party organizations who are just signing business associate agreements should stop and evaluate what it is they are signing.  Agreeing to terms in a business associate agreement and declaring that you are a business associate or subcontractor or a business associate does have major implications.

Covered entities and business associates need to spend time really understanding who may or may not be a business associate.  It should not be a blanket process where everyone that works with a specific company automatically has to sign an agreement.  Additionally, if information is being shared to support the spectrum of patient care (provider to provider), the business associate definition may not apply.  Dedicated individuals who are knowledgeable and understand the regulations should be working with organizations to help them navigate the business associate process.    

Per the 2013 Omnibus Rule, a business associate is  “a person or entity, other than a member of the workforce of a covered entity, who performs functions or activities on behalf of, or provides certain services to, a covered entity that involve access by the business associate to protected health information.  Per the Omnibus Rule of 2013, a “business associate” may also be considered a subcontractor that creates, receives, maintains, or transmits protected health information on behalf of another business associate.”  Those are key words to use to evaluate if an organization is a business associate – do they create, receive, maintain, or transmit data on behalf of a covered entity or business associate? 

What should an organization do?

The best process for an organization is to have an established person or group of people in charge of the evaluation of business associate agreement.  Here are some recommended steps for overall governance of Business Associates within an organization.

  • Create a team or individual responsible for the management of business associates
  • Generate a list of the account payable reports for the past 3 months and review all third party vendors and/or individuals for your organization
  • Determine the scope of work that the third party has been doing on behalf of the organization
  • Evaluate if the third party scope of work being done qualifies the third party as a business associate
  • If it is determined that they are a business associate establish and execute a business associate agreement
  • Keep up a log of all business associates – some recommended fields are Business Associate Name, Contact Individual, Contact Information, Tasks that qualify as a business associate, Business Associate Agreement signed, Date agreement signed
  • Create a process for a proactive review of any NEW third parties and that organizations is going to establish a business relationship with

It is now time to effectively oversee and manage the business associate process within an organization – the covered entity should be aware that while business associate and subcontractors are liable for HIPAA compliance, the ultimate liability falls onto the covered entity. 

Note to third parties (contractors, subcontractors) – make sure you know and understand the implications of becoming a business associate or an organization.  If you truly don’t meet the definition of a business associate or subcontractor, don’t just sign the contract – seek out advice or guidance on the proper steps!

Danika

Filed Under: BAA, Business Associates, HIPAA, HIPAA Compliance, Subcontractor

Is Windows XP Still Common in Healthcare Organizations 10 Months after Stopping Security Updates?

February 17, 2015 by Danika Brinda Leave a Comment

laptop with a hammer on the screenOn April 8, 2014, Microsoft stopped providing patches and updates to the Windows XP operating system.  While this seems like old news and a bit crazy to talk about – many healthcare organizations are still using Windows XP operating systems.  In discussing this issue with many healthcare organizations – one of the most common issues is that they are using a software that is unable to migrate to new versions of Windows and is needed for day to day patient care.  The vendors that support these software systems are aware; however, have not taken action to move the software to a newer windows platform.

So they’re not providing updates – what does that actually mean?  With no updates being provided – there will be no new security updates, non-security hot fixes, free or paid assisted support options, or online technical content updates to the operating system.  This leaves the system vulnerable to an attack from the outside.  There has been a lot of documentation and confusion on what needs to be done in order to protect information stored on computers that have not migrated off of Windows XP.  In addition, there have been many articles have been published that are stating that if organizations didn’t migrate off of the Windows XP Platform by 4/8/14, providers will not be eligible for Meaningful Use and will not be HIPAA Compliant.  Fact or Truth?

Fact: You are not technically in violation of HIPAA if you use Windows XP as HIPAA doesn’t mandate any specific software system; HOWEVER, the practice is extremely risky and you could be found of out compliance if a data breach was to occur.

The HIPAA Security Requirement 164.308(a)(5)(ii)(B) is an addressable standard that states that an organization must have “policies and procedures for guarding against, detecting, and reporting malicious software.”  Malicious software can be brought through any program usually in the form of a virus, Trojan horse, or worm.   By not having the ability to add security patches into the operating system of Windows XP, there are risks to the organization and data that the organization keeps and maintains – good documentation of other safeguards that exist to protect that computer MUST be implemented and documented if choosing to run on the Windows XP operating system.

It is also important to note nowhere in the meaningful use requirements or the HIPAA requirements does it specify having to be on a specific software platform or operating system.  Here is an example FAQ from HHS for clarification regarding operating systems requirements under HIPAA – no specific operating system must be used!  http://www.hhs.gov/ocr/privacy/hipaa/faq/securityrule/2014.html

Still Using XP – What you should be doing now:

  • Evaluate and determine how to migrate from Windows XP to an updated operating system as soon as possible.
  • If vendor is only running on XP – work with them and continue to push them to update the software due to risks of the old system and lack of security patches.
  • Conduct your HIPAA risk assessment to determine if your organization’s systems are still operating on Windows XP and what risks exist.
  • Come up with a detailed risk management process if your organization is still running on Windows XP, including information on how to reduce risk until you migrate from the Windows XP system.
  • Evaluate everything – There is not ‘formal’ documentation from HHS, ONC, or the OCR regarding this measure and how to interpret from a meaningful use and HIPAA aspect.
  • Assure that you document Windows XP as a risk to your organization within the risk assessment/mitigation as well as potential impacts from malware, viruses, & hackers.
  • If questions come up, ask for clarification or assistance.

As of July 14, 2015, Microsoft will stop providing updates and support to any versions of Windows Server 2003 – leaving organizations with a challenge of upgrading and/or migrating to a new server software.  If you are still running on Microsoft 2003, it is time to take steps now to execute a proper migration strategy and protect your patient information.

Final note: Running any type of organization where protected health information is involved and there are not adequate and regular security patches being implemented is a risky practice and could expose an organization to a data breach.  From the eyes of a security professional – the risk isn’t worth a large scale breach of information.  It is time to take action now and get rid of old software platforms that are no longer being updated and supported.

Danika

Filed Under: HIPAA, HIPAA Compliance, Security, Windows XP

Friday the 13th HIPAA-Stitions: Demystifying the Myths

February 13, 2015 by Danika Brinda Leave a Comment

Sheet with the inscription Friday 13 and red spotsFriday the 13th comes around on average 2-3 times per year.  In 2015, Friday the 13th will visit us 3 different times.  Friday the 13th is thought to be one of the most unlucky days of the year – plaguing us with many different superstitions that cause fear among people.  From the masked Jason chasing people down an empty, dark street to the crazy doll, Chucky, that comes to life and attacks, the dread of the 13th of the month has created angst and fear to society! 

Just like all the superstitions and fears we face on Friday the 13th, HIPAA is full off different myths and fears created among the healthcare community.  Healthcare organizations fear HIPAA as it is going to cause issues and destruction among their organization.  Different interpretations and analysis of the HIPAA requirements has created confusions and fears among the healthcare community. 

In honor of Friday the 13th – Lets Demystify 13 of Today’s HIPAA-Stitions

  1. HIPAA prohibits me from taking care of patients and releasing information for continuity of care.

HIPAA allows the sharing of patient information for the purpose of treatment, payment, and healthcare operations (TPO).  If a provider needs to release patient information to help in the continuity of care, that is an acceptable disclosure under the HIPAA regulations.  It is smart to check with state requirements on the protection of patient information as some states do requirement a signed authorization for any use or disclosure of patient information. 

  1. The HIPAA Security Risk Analysis only needs to be completed one time.

The HIPAA regulations actually do not define what the frequency of the HIPAA risk analysis needs to be.  Built to be scalable, the HIPAA security rule allows the covered entity or business associate to define the frequency; however, do it one time and never again is not an acceptable practice and leaves the organization vulnerable to non-compliance and risks to PHI.

  1. Texting is considered a way of communicating about patients and has no concerns with HIPAA compliance.

Normal SMS texting is not a secure means of communications with protected health information.  In fact, texting using normal SMS format is quite risky to the healthcare organization.  If a healthcare organization is going to allow texting as a means of communications regarding patients (think about this before saying yes), a secure solution for texting should be implemented as well as a policy and procedure for effective management of texting with patient information.  Think about not only how to manage the data as it is in transmission from device to device, but also how you will manage the devices and the information that may be stored on the device.  

  1. HIPAA prohibits me from sending patient reminders about appointments and leaving messages on phones.

The HIPAA privacy rule allow for all providers to communicate with their patients regarding their health care, which includes reminders about appointments. This includes communicating with patients at their homes, whether through the mail or by phone. The HIPAA regulations do not prohibit a provider from leaving messages for patients on their voicemail; however, it does require that the covered entity provides adequate safeguards to the privacy of a patient, which may include getting agreement from the patient to leave a voicemail at a specific number or send information regarding care to a specific address. 

  1. Since the EHR we use is a cloud based EHR, I don’t have to worry about having a written contingency plan in place.

Using a cloud based, EHR may eliminate an organization’s need to manage the backup process for the EHR system; however, it doesn’t completely eliminate the need to create and implement a contingency plan.  The contingency plan is intended to cover so much more than how the information is backed up, such as how the organization will work in emergency mode, what systems are most vital to the day to day operations or the organization, and how recovery of data will occur.  Another aspect to think about is the EHR may only be one of the systems that stores and maintains patient information.  If you have other systems or are storing information regarding patients in other electronic locations, it is important to have a plan in place on how that information is being backed up and restored in the case of an emergency. 

  1. As long as we have passwords in place to get into our systems with patient information, the information is considered secure.

A common misunderstanding of the application of passwords is that they make a system secure when implemented – but they don’t.  Passwords do provide an appropriate safeguard and a layer of security to patient information; however, the protection is only as good as the password.  To help better manage the use of passwords, strong passwords should be implemented on any systems that provide access to patient information.  Strong passwords should be a minimum of 8 characters in length and use uppercase letter, lowercase letters, numbers and systems – 3 of the 4 is the minimum recommendation.  Remember that the only true way to make information secure is to encryption the information or destroy the information using appropriate means.

  1. My business associate states they are HIPAA compliant so there is no need to worry about the protection of the information shared with them.

No organization is out there certifying healthcare organizations as “HIPAA Compliant.”  Any third party organization that is stating that they are HIPAA complaint most likely means that they have created an internal program to meet the requirements of the HIPAA regulations as they apply to business associates.  It is best practices that covered entities as business associates about the safeguards used to protect the information they are sharing and what makes them “HIPAA Compliant.”

  1. I don’t have an electronic health record; therefore, the HIPAA security rule doesn’t apply to me.

HIPAA doesn’t distinguish between systems where information is stored on where the security rule applies and doesn’t apply.  Rather HIPAA focuses on the media type of the information – electronic, paper, and oral.  The security rule applies specifically to all electronic protected health information, which is PHI that is created, received, maintained or transmitted in electronic form.  An electronic health record is only one source of electronic protected health information. 

  1. Meaningful use changed requirements for the HIPAA risk analysis.

The meaningful use requirements didn’t actually change any of the requirements that HIPAA mandates – it actually points directly to the HIPAA requirements for the conducting of the HIPAA risk analysis for protecting patient information.  The only ‘change’ is that if you are participating in the meaningful use program, a HIPAA risk analysis must be conducted or updated for each year that you attest for meaningful use.

  1. Every unauthorized use and disclosure of patient information is considered a data breach.

In order to determine if a breach occurred from an unauthorized use or disclosure of information, an investigation must be completed by the covered entity or business associate to determine the risk to the patient information.  Per the Omnibus Rule of 2013, an unauthorized use or disclosure of health information is not considered a breach if there is low probability that the information has been compromised. 

  1. Since the patient won’t sign my Notice of Privacy Practices, I am not allowed to treat that patient.

A patient refusing to sign the notice of privacy practice acknowledgement doesn’t prohibit the provider to take care of the patient.  The regulations state that the covered entity should make reasonable effort to get an acknowledgement of the notice of privacy practices signed.  By signing the acknowledgement, the patient is only documenting that they have been given or offered a copy of the notice of privacy practice, which explains how the organization will use and safeguard their protected health information. 

  1. The HIPAA regulations prohibit Provider/Patient e-mail communication

The HIPAA regulations do not prohibit provider from communicating with patients through e-mail.  The regulations actually state that if the provider is going to communicate with patients through e-mail, proper safeguards should be implemented to protect the information.  Additionally, the Omnibus Rule states that e-mail can be sent to a patient without encryption as long as the patient agrees to it and is aware of the risks to the information. 

  1. Since I fully implemented a HIPAA compliance program, data breaches will not occur at my organization.

Just because an organization implements a full HIPAA compliance program and addresses all areas of potential risk to their organization, there is no guarantee that a data breach is not going to occur.  With the sophistication of recent data attacks and human interaction, there is always going to be a risk that a data breach can occur.  The best scenario is having a fully implemented HIPAA compliance program and assure adequate training to workforce members.  Reducing and managing potential risks is the best avenue to take – no organization is without some risk.  

When evaluating HIPPA and operationalizing it to ‘fit’ a specific organization, HIPAA doesn’t have to be feared!  Overcome the common HIPAA-Stitions and being successful with HIPAA compliance can be a goal reached by all organizations – large and small.  Don’t fear HIPAA as we fear Friday the 13th, instead take it on full speed and don’t look back until you met the appropriate level of compliance.

Danika

Filed Under: Other

HIPAA Makes Us Do What? Why? Understanding the Heart of HIPAA!!

February 9, 2015 by Danika Brinda Leave a Comment

Red heart vector illustrationAs we prepare for Valentine’s Day and the celebration of love with hearts and cupids, we are reminded that everything that we do is defined from purpose and intent.  Valentine’s Day dates back to the 5th Century as a dedicated day for people to show their love and respect for one another.

Just as with any holiday or dedicated day, HIPAA has a defined purpose and intent.  It wasn’t created to put challenges and burdens onto healthcare organizations and business associates.  It wasn’t created to block patient care and make it impossible to share protected health information.  HIPAA was created with a purpose and intent, to provide protections and rights to protected health information.  Understanding the heart of HIPAA can help an organization evaluate and successfully implement the regulations. 

The HIPAA Privacy Rule, which was mandated in 2003, has three distinct purposes.  Each of the purposes was created with intent of adding protections and enhancements to how healthcare organizations safeguard protected health information.  The Privacy Rule doesn’t focus on a media type of protected health information – but rather focuses on all patient information regardless of medium.  The three main goals of the HIPAA Privacy Rule are:

  1. protect and enhance the rights of consumers by providing them access to their health information and controlling the inappropriate use of that information;
  2. to improve the quality of health care in the U.S. by restoring trust in the health care system, and
  3. To improve the efficiency and effectiveness of health care delivery by creating a national framework for health privacy protection that builds on efforts by states, health systems, and individual organizations and individuals.

The HIPAA Security Rule, which was mandated in 2005, took protecting information to the next level with the focus on information that is created, stored, transmitted, and maintained in an electronic format.  With the increase in the amount of electronic protected health information, the main purpose of the HIPAA Security Rule is to

  1. Establish the minimum requirements to ensure the confidentiality, integrity, and availability (CIA) of electronic protected health information.

Looking to the heart of the requirements and why the privacy and security requirements were created can help healthcare organizations overcome the frustration and concerns that are created when evaluating and implementing the regulation requirements.  Remember as we get ready to prepare for the day of love and celebration of hearts, HIPAA has a heart and looking to the basics and understanding what the intent of the heart is can be beneficial. 

Celebrate the Heart of HIPAA!

Danika

Filed Under: Other

And the Password IS….NOT so Secret. 6 Ways to Ensure Effective Use of Passwords.

February 3, 2015 by Danika Brinda Leave a Comment

Vector login interface - username and passwordMost everybody is familiar with the famous TV Show ‘Password’ and remember the famous line “And the password is…”  A fun and exciting game show of trying to guess the secret password in order to win money.  Today’s attempt in trying to guess passwords has become much easier and can allow access to information and detail that can dramatically impact organizations as well as individuals.  A recent review of the most ‘hacked’ passwords by SplashData has provided the top passwords that were hacked in 2014.  These passwords are easy to get access to the information they are protecting:

Top 10 Hacked Passwords in 2014

  • 123456 (number 1 for the past 2 years)
  • Password
  • 12345
  • 12345678
  • Qwerty
  • 123456789
  • 1234
  • Baseball
  • Dragon
  • Football

The good news – these passwords are thought to only make up about 2.2% of the total password population.

Password management is the number one line of defense when it comes to protecting patient information stored on a computer, on a server, in an electronic health record, or in any system where protected health information is stored.  Effectively putting strategies and management processes in place to manage passwords in a healthcare organization or business associate is a necessity for adequate protection of patient information.  Here are 6 simple ideas to help effectively manage passwords in a healthcare organization:

  1. Enforce the Use of Strong Password. A strong password at a minimum consists of 3 or 4 of the different elements – Uppercase Letters, Lowercase Letters, Numbers, and Symbols.
  2. Requirement of Specified Length of Password. Requiring a specific length of a password can help reduce the ability to ‘guess’ a password – 7 to 8 characters in length is a good practice to implement.
  3. Require that Passwords are Changed Regularly. Passwords needs to be changed on a regular basis.  Best practice within healthcare is to change all passwords (Operating System, EHR, Administrative, etc.) every 120 to 180 days.
  4. Ensure that Workforce Members Do No Write Passwords Down. Train workforce members to never, ever write passwords down.  While it is tempting and people might not think that a password will be found if hidden in a secret spot, it is important that passwords are never written down unless the organization creates a secure process for documenting passwords.
  5. Implement Lock Out of Systems After Specified Number of Incorrect Passwords Entered. It is important that if someone fails a login a specific number of times in a short period, that the system suspends the ability to log in or requires the user to come back at a later point in time to attempt the login process again.  This will deter unwanted guessing of passwords and provides an added safeguard in the “guessing” game.
  6. Educate Workforce Members on Password Management. Educate, educate, educate, educate.  Workforce members need to understand the importance of passwords and the intent of why they need to be protected to assure unauthorized access into the healthcare systems.  With proper education, workforce members will understand the need to protect passwords, and ultimately protect patient information.

While these are very simple processes, more detailed and secure methods of authentication exist that can remove some of the risks to healthcare organizations; however, they don’t come without time and cost to manage.  With simple steps, healthcare organizations can more effectively oversee how passwords are created, managed, and safeguarded within a healthcare organization.  Don’t get caught having someone guessing passwords, take the proper steps to manage passwords within an organization.

Danika

Source: http://blogs.wsj.com/digits/2015/01/20/123456-again-the-most-popular-passwords-arent-changing/

Filed Under: Other

Tweets by @TriPointHIPAA

Recent Posts

  • Ready, Set, HIPAA Enforcement – 2017 is Going to be a Year to Remember
  • What is your Greatest HIPAA Threat? Employee Negligence is Top Security Threat among Healthcare Providers and Business Associates!
  • 2015 Healthcare Data Breaches: Paper Tops Data Breach Location!
  • HIPAA Risk Analysis: Exposing 10 Common Myths
  • HIPAA Risk Analysis is More than a Checklist: 5 Steps to Conduct a Thorough Risk Analysis

Connect With Us

TriPoint Healthcare Solutions
dbrinda@tripointhealthcaresolutions.com
Phone: 612.325.9742
Fax: 763.322.5027

  • Facebook
  • LinkedIn
  • Twitter

Copyright © 2025 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in