In our series on the HIPAA Administrative Simplification Security Rule, this is the third implementation specification for the Administrative Safeguard Standard (Security Management Process). This implementation specification is required.What to DoApply appropriate sanctions against workforce members who fail to comply with the security policies and procedures of the covered entity.How to Do ItThe covered entity must determine appropriate internal sanctions or penalties for violation of its security policies and procedures by workforce members. Sanctions should:
» Deter noncompliant behavior, such as posting passwords on computer hardware or under a desk pad.
» Serve as an incentive for compliance with security policies and procedures.
The appropriate sanctions will be suggested by the results of the covered entity’s risk analysis. Sanctions should be in proportion to the covered entity’s estimate of harm that would be anticipated from specific security incidents. For example, posting or sharing a password may appear innocuous, but consider potential harms if an unauthorized user of the password gained access to electronic protected health information and disclosed it publicly. The covered entity should clearly articulate sanction policies, so that workforce members easily understand consequences of violations of security policies and procedures. Sanctions should apply equally to all workforce members. Workforce members should understand that consequences may include not only disciplinary action within the covered entity, but also civil and possibly criminal enforcement.The HIPAA Administrative Simplification Privacy Rule also includes an administrative, technical, and physical safeguard standard. The covered entity should make sure that the sanctions pertaining to each Rule are consistent.
HIPAA.com cofounder Ed Jones is a consultant and author of books on healthcare privacy, security, and electronic health records. He was an SVP at an NYSE-traded health plan insurer and held senior roles at the US Department of Justice and the CIA.
When a HIPAA breach hits, delay costs money. Build your response team before you need it: a data privacy attorney first (to help protect the investigation under privilege), then forensic and IT consultants, media relations, and HR.
I am asked that question almost weekly. While the answer has traditionally been “no,” the legal landscape is shifting and the risk of being sued continues to increase.
Let’s
A party’s responsibilities under HIPAA generally come from two sources - the law itself and the business associate agreement entered into between the covered entity (the health care provider or
June 7, 2013. Today, HHS published in the Federal Register "Technical Corrections to the HIPAA Privacy, Security, and Enforcement Rules" that were published on January 25, 2013, as
June 7, 2013. Today, HHS published in the Federal Register "Technical Corrections to the HIPAA Privacy, Security, and Enforcement Rules" that were published on January 25, 2013, as
The Final Rule took effect March 26, 2013, with 180 days to comply. How the 180-day rule works for future HIPAA changes, which deadlines didn’t move, and the longer transition for existing business associate agreements.
How the 2013 Final Rule changed delivery of the Notice of Privacy Practices: when health plans must post or mail a revised notice after a material change, what stays the same for providers, and how to keep notices accessible.
March 22, 2013. Today, we continue going through the HIPAA Privacy Rule, section by section, as modified in the Final Rule: Modifications to the HIPAA Privacy, Security, Enforcement, and Breach