HIPAA Compliance Quiz Privacy and Security Rules
True / False
True / False
True / False
Disclaimer
This quiz is for educational purposes only. It does not constitute professional advice. Consult a qualified professional for specific guidance.
HIPAA Privacy and Security Rule Mistakes That Trigger Audit Findings
Most HIPAA misses are not about memorizing acronyms. They come from mixing up what the Privacy Rule permits, what the Security Rule requires for ePHI, and what your organization must be able to prove through documentation.
Frequent Privacy Rule errors
- Over-sharing for “convenience”: staff disclose PHI beyond the minimum necessary for payment or operations. Fix: build role-based workflows and default to limited datasets for routine tasks.
- Using the wrong legal basis: teams treat patient authorization, consent, and “allowed without authorization” as interchangeable. Fix: map common disclosures to TPO (treatment, payment, health care operations) versus situations that need a signed authorization, such as many marketing disclosures.
- Weak patient-rights handling: access requests are delayed, routed informally, or fulfilled with incomplete records. Fix: standardize intake, identity verification, and response time tracking.
Frequent Security Rule errors
- Risk analysis that is outdated or superficial: inventories miss cloud apps, endpoints, or remote access paths. Fix: keep an ePHI data flow map and tie risks to specific safeguards and remediation dates.
- Misunderstanding “addressable” safeguards: teams assume addressable means optional. Fix: document the decision to implement, implement an equivalent alternative, or not implement with a defensible rationale.
- Access control gaps: shared accounts, missing MFA on remote access, or poor termination procedures. Fix: unique user IDs, least privilege, and automated deprovisioning.
Breach and vendor pitfalls
- No Business Associate Agreement before a vendor touches PHI. Fix: require BAAs in procurement and re-check subcontractor chains.
- Assuming “no harm” means no breach: breach decisions are made without a documented risk assessment. Fix: use a consistent breach triage checklist and retain evidence.
Authoritative HIPAA Privacy, Security, and Breach Notification References
Use these primary sources to confirm rule text, official interpretations, and security implementation expectations.
- HIPAA Guidance Materials (Privacy): OCR guidance and professional FAQs on permitted uses and disclosures, patient rights, and common scenarios.
- The Security Rule (HHS): Security Rule overview, guidance links, and tools related to administrative, physical, and technical safeguards.
- Guidance on Risk Analysis: OCR expectations for risk analysis scope, documentation, and common mistakes.
- Breach Notification Rule (HHS): requirements for notifying individuals, HHS, and media after a breach of unsecured PHI.
- NIST SP 800-66 (HIPAA Security Rule Implementation Guide): a detailed framework for translating Security Rule standards into practical security controls.
HIPAA Privacy and Security Rules FAQ for Compliance Professionals
What is the practical difference between the HIPAA Privacy Rule and the Security Rule?
The Privacy Rule sets rules for how PHI may be used or disclosed and what rights individuals have over their information. The Security Rule applies to ePHI and requires administrative, physical, and technical safeguards, such as access controls, audit controls, and risk management.
When does the “minimum necessary” standard apply, and when does it not?
Minimum necessary generally applies to uses and disclosures for payment and health care operations, and to many internal uses. It typically does not apply to disclosures for treatment, disclosures to the individual, disclosures required by law, or disclosures made pursuant to a valid HIPAA authorization. Your policies should spell out role-based limits.
Is encryption required under HIPAA?
Encryption is an addressable implementation specification under the Security Rule for data at rest and in transit. Addressable does not mean optional. You must implement encryption, implement an equivalent alternative, or document why neither is reasonable in your environment, based on your risk analysis.
What makes someone a Business Associate, and what is the common BAA mistake?
A Business Associate is a person or entity that performs functions or services for a covered entity that involve creating, receiving, maintaining, or transmitting PHI. The common mistake is signing the vendor contract first and handling the BAA later. If the vendor handles PHI, the BAA should be executed before any PHI is shared.
What is “unsecured PHI,” and why does it matter for breach notification?
Unsecured PHI is PHI that is not rendered unusable, unreadable, or indecipherable to unauthorized persons using approved methods, such as certain encryption approaches. If PHI is properly secured, an incident may not trigger breach notification duties. If it is unsecured, you generally need a documented breach risk assessment and timely notifications when required.
How fast must an organization respond to a patient’s request for access to records?
HIPAA sets a general expectation of responding within 30 days for access requests, with a possible one-time extension of up to 30 additional days if the individual is given a written explanation for the delay. Many compliance failures come from lost requests, unclear identity verification steps, or partial production of the designated record set.
Looking for more? Browse more Compliance & Safety quizzes on QuizWiz or explore the full QuizWiz workplace quiz library.