With everything else that has been going on - the holidays, health care reform, etc. - you may have forgotten that the HIPAA Security Breach Notification Rule deadline is February 22, 2010. With less than a month before the deadline, many providers may not have started their compliance efforts yet. If you don't recall what the Security Breach Notification Rule says or requires, you can take a look here and here.
If you haven't started working on this yet, you still have close to a month, so don't panic. You should begin looking at this issue and putting together a timeline for compliance by February 22. You may have already addressed breach notification, due to state law requirements. If so, you can start by reviewing what notification policies and procedures you have in place and comparing them to the notification rules requirements.
If you do not have any notification procedures in place, I would recommend reconsidering the reasonableness of encryption as your first step. As part of your original Security Rule compliance efforts you should have assessed the reasonableness of encryption. At that time, you may have determined it was not reasonable to implement. If you go back and revisit this consideration, the advances in technology, combined with the incentive of avoiding the notification issues, may change your assessment.
If you implement encryption, you eliminate the notification provisions, because you do not have any unsecured protected health information. Don't forget that the encryption guidance from HHS includes guidance on destroying PHI. If you are not properly destroying old files, you still have a source of unsecured PHI and would still need notification procedures.
If you do not implement encryption, you need to implement notification policies and procedures. There are a few things you should consider when implementing notification. For example, you are required to provide a way for the individuals who are affected to contact you for more information. Who will be responding to these calls. You need to be sure that whoever is fielding contacts about the breach is comfortable dealing with the public (and potentially the press), understands what they can and cannot say and will stick to that. You do not want your point of contact to create any more problems for you by giving bad answers.
Another thing to consider now - if you use the toll-free number contact option, how do you want to set up the call-in number? If you already have a toll-free number, you may not want to just use it as the contact number in the event of a reportable incident. Depending upon the number of individuals involved, this may make it difficult to take normal business calls and may result in someone fielding questions that you would rather not have fielding questions.
You will want to be sure to get everybody who would be involved in detecting and reporting a breach involved in training. Everyone should know that on February 22, you have new policies and procedures going into effect and what this means. There is no point to having these new policies and procedures if no one is aware of them or understands them.
Remember - even if you have not started working on this yet, there is still time. You just need to be sure that you use this last month wisely - develop a plan, set deadlines and stick to them. This is not at all like implementing HIPAA compliance from scratch, so try not to let this ruin your weekend - just don't forget about it come Monday. (Another resource you might consider is this template my partner put together. I apologize for the shameless plug, but if you haven't started yet, you could probably use the assistance.)