April 12, 2005
Checklist for HIPAA Security Rule
As we all have learned over the past few years, there's more to HIPAA than pre-existing conditions and privacy. Now, on April 21, all but small health plans must comply with the HIPAA security rule. HealthLeaders Daily News has a helpful piece on the rule, "April 20 is Coming: A 16-Point Checklist for HIPAA Security," by Michael Doscher and Chris Davenport. Here is their checklist (minus the explanatory text for each point):
- Does the application create, receive, maintain or transmit electronic Protected Health Information (ePHI)? (For all applications that process ePHI in some way, the entity must pursue responses to the next 15 questions.)
- Is there a procedure for authorizing, establishing and modifying user access?
- Does the application possess unique user identification capabilities?
- Have unique user identification capabilities been activated?
- Are there generic IDs in use?
- Does an Emergency Access Procedure exist?
- Does the application facilitate automatic logoff capability?
- Is automatic logoff capability enabled?
- Is there an encryption feature for data "at rest" in databases?
- Is the application capable of performing audit logging?
- Is the audit logging function enabled?
- Are audit logs reviewed on a routine basis?
- Does the application possess person or entity authentication capabilities?
- Are person or entity authentication capabilities activated?
- Is there a method to ensure transmission integrity?
- Is there a capability to encrypt the transmission?
If the checklist (and accompanying explanation) still leaves you in the dark, check out the final security rule. [tm]
April 12, 2005 | Permalink