The Health Insurance Portability and Accountability Act of 1996 (HIPAA) was designed to improve "the efficiency and effectiveness of the health care system by encouraging the development of a health information system through the establishment of standards and requirements for the electronic transmission of certain health information" (Public Law 104-191).
The requirements of HIPAA are fairly complex and affect nearly every aspect of the health care system. It is important to take a detailed and methodical look at HIPAA to ensure that you are fully compliant with every aspect of this legislation. To that end, here are several important points to consider while developing your HIPAA plan of action:
- Make sure you, as a provider or health plan, are ready.
- Don't rely on your payers, or software vendors to make you compliant. HIPAA is much too complex for a 'HIPAA-in-a-can' solution offered by many vendors.
- Contract with uninterested parties (i.e. organizations without a conflict of interest) that are HIPAA-aware to help you through the process.
- There are many steps and many areas that need to be addressed. It is always better to have several, specialized people than one who thinks he is the 'HIPAA Kahuna'
- Be as prepared as possible for each regulation release by examining the context of the regulations to be released.
- Privacy was released first, so go through the steps that ensure you
- meet the requirements for privacy under HIPAA. Once that is done, start preparing for the security regulations. After all, having a secured network now will reduce the work required to meet the security regulations once they are distributed.
- Be realistic about what you are capable of accomplishing.
- HIPAA regulations are full of statements like 'reasonable effort' and 'as permitted'. This means depending on who you are, how big you are, and how much money your company has, determines your level of reasonable effort.
- HIPAA is about protecting PHI (protected health information, also confidential or sensitive health information), this is a given, what is taken for granted, is the number of possible conduits that PHI is capable of leaving your custody to an unauthorized entity.
- Be diligent about covering all the bases. Everything from fax machine location to who is asking for the PHI has to be accounted for.
- There also has to be a paper trail or 'chain of custody' for the information.
- As long as you know where the information is, who has access to it and you can prove it, who HAS accessed it, and who gave permission for what to be disclosed, the privacy regulations are pretty logical.
- If you use software for billing, you NEED to be in conversation with the vendor.
- You MUST allow enough time for testing the new billing forms and for any corrective actions that might need to happen.
- There are state-governed requirements for submitting billing.
- It is well worth the effort to use the services of a third party testing facility to verify your 835/837 forms are formatted correctly. www.claredi.com is a common validation site.
- Need to know dates
- April 14, 2003: Privacy regulations go into effect except for small health plans
- April 16, 2003: EDI transactions and code sets; must start testing
- October 16, 2003: EDI transactions and code sets; go into effect for all those covered entities that filed for an extension and small health plans
- April 14, 2004: Privacy regulations in effect for small health plans
- July 30, 2004: Employer Identifier Standards into effect, except small health plans
- August 1, 2005: Employer Identifier Standards into effect for small health plans
- Useful resources:
There is no way that all the points of HIPAA can be put into a small outline. HIPAA is a complex, sensitive beast, however, it CAN be tamed. It takes time, perseverance and an overall understanding that once these regulations are in place and working properly, it is very possible, if not likely, that these standards will start to expand to cover other entities that deal with sensitive information. Entities like child protection services and foster care agencies are likely candidates. Although HIPAA regulations are lengthy and sometimes confusing the way they override some state laws and yield to others, it is in the best interest of everyone to give HIPAA the proper respect it deserves. After all, what if the information that was accidentally given to the wrong people was yours?
The content for this security policy tip on HIPAA was compiled by Lewis C. Fry.
About the author
James Michael Stewart is a partner and researcher for ITinfopros, a technology-focused writing and training organization.
This was first published in March 2003