HIPAA Wiki: A Plain-English Guide to Privacy, Security, and Compliance

Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Wiki: A Plain-English Guide to Privacy, Security, and Compliance

Kevin Henry

HIPAA

May 29, 2025

7 minutes read
Share this article
HIPAA Wiki: A Plain-English Guide to Privacy, Security, and Compliance

This HIPAA wiki gives you a plain-English path through the rules that protect health data in the United States. You will learn what counts as Protected Health Information, who must comply, how the Privacy and Security Rules work, what to do after a breach, and how the HITECH Act and enforcement shape day‑to‑day compliance.

HIPAA Overview

HIPAA—the Health Insurance Portability and Accountability Act—sets national standards for handling Protected Health Information (PHI). It defines who is responsible, how information can be used or disclosed, and the safeguards you must implement to protect electronic PHI (ePHI).

Key terms you should know

  • Protected Health Information: Individually identifiable health data in any form—paper, electronic, or spoken—that relates to a person’s health, care, or payment.
  • Covered Entities: Health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically in connection with certain transactions.
  • Business Associates: Vendors and service providers that create, receive, maintain, or transmit PHI on behalf of a Covered Entity (for example, billing services, cloud hosts, or analytics firms).

What HIPAA requires at a high level

  • Limit uses and disclosures of PHI to what’s allowed or authorized.
  • Honor patient rights (access, amendments, and more) under the Privacy Rule.
  • Protect ePHI with Administrative Safeguards, Technical Safeguards, and physical protections under the Security Rule.
  • Follow Breach Notification Requirements if unsecured PHI is compromised.

HIPAA Privacy Rule

The Privacy Rule governs how PHI may be used or disclosed and grants people control over their information. You must define who can access PHI, why, and under what conditions, then document and train accordingly.

Permitted uses and disclosures

  • Treatment, payment, and healthcare operations without patient authorization.
  • Disclosures required by law and certain public interest purposes (for example, public health reporting) subject to specific conditions.
  • All other uses require a valid, written authorization that specifies purpose, scope, and expiration, and can be revoked by the patient.

Patient rights

  • Right of access to inspect or obtain copies of PHI, including most electronic records.
  • Right to request amendments to PHI maintained in designated record sets.
  • Right to an accounting of certain disclosures and to request restrictions (including paying out-of-pocket to restrict disclosure to health plans in some cases).
  • Right to receive a Notice of Privacy Practices describing how you use and disclose PHI.

The minimum necessary standard

You must make reasonable efforts to limit PHI to the minimum necessary to accomplish the intended purpose. Role-based access, need-to-know policies, and routine de-identification where feasible help you meet this standard.

HIPAA Security Rule

The Security Rule applies to ePHI and requires you to ensure confidentiality, integrity, and availability. It is risk-based: you must evaluate your environment and then implement reasonable and appropriate safeguards, documenting decisions along the way.

Risk Analysis and risk management

Begin with a comprehensive Risk Analysis to identify where ePHI lives, how it flows, and what could go wrong. Then manage those risks with prioritized controls, remediation timelines, and ongoing monitoring.

Administrative Safeguards

  • Assign security responsibilities and conduct workforce training and sanctions.
  • Develop policies and procedures for access management, incident response, and contingency planning (backup, disaster recovery, emergency mode operations).
  • Manage vendors through Business Associate Agreements and periodic due diligence.
  • Perform regular evaluations and document all decisions and outcomes.

Technical Safeguards

  • Unique user IDs, strong authentication, and robust access controls.
  • Audit controls and activity logs to record access and detect anomalies.
  • Integrity controls to prevent improper alteration or destruction of ePHI.
  • Transmission security (for example, encryption in transit) and encryption at rest where your Risk Analysis shows it is reasonable and appropriate—or document an alternative with equivalent protection.

Physical protections

  • Facility access controls, workstation security, and secure device/media handling.
  • Sanitization or destruction procedures before device reuse or disposal.

HIPAA Breach Notification Rule

This rule requires notifications when unsecured PHI is compromised. A breach is presumed unless you can show a low probability of compromise based on a documented risk assessment.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Assessing a potential breach

  • Consider the nature and sensitivity of the PHI involved.
  • Identify the unauthorized person who used or received the PHI.
  • Determine whether the PHI was actually acquired or viewed.
  • Evaluate the extent to which risks have been mitigated (for example, swift retrieval, encryption, or recipient assurances).

Breach Notification Requirements

  • Notify affected individuals without unreasonable delay and within required timeframes.
  • Notify the Department of Health and Human Services; for larger incidents, report promptly and for smaller ones, submit annually as required.
  • Notify prominent media outlets if a breach affects 500 or more residents of a state or jurisdiction.
  • Provide content that explains what happened, what information was involved, actions taken, and steps individuals can take to protect themselves.
  • If PHI is properly encrypted or otherwise rendered unreadable under recognized guidance, notification may not be required.

HITECH Act

The HITECH Act strengthened HIPAA by extending direct obligations to Business Associates, making breach notifications mandatory, and increasing penalties for noncompliance. It also accelerated electronic health record adoption and encouraged encryption through a “safe harbor” when PHI is rendered unusable to unauthorized parties.

HITECH expanded enforcement tools, allowed state attorneys general to bring actions, and supported audits—all of which raised the stakes for rigorous privacy and security programs.

HIPAA Enforcement

HIPAA is enforced primarily by the Office for Civil Rights (OCR). OCR investigates complaints, conducts compliance reviews, and can require corrective action plans, monitoring, settlements, or civil monetary penalties that scale with the level of culpability.

Serious or intentional misuse of PHI can trigger criminal enforcement by the Department of Justice. State attorneys general may also bring cases under HIPAA and related state laws, so you should track both federal and state requirements.

Practical steps to stay compliant

  • Designate privacy and security officers and define governance.
  • Maintain continuous training, audits, and documented policies and procedures.
  • Test incident response and disaster recovery plans at least annually.
  • Vet Business Associates, execute BAAs, and monitor performance.

HIPAA Compliance Resources

Build a resource library that aligns with your operations. Focus on tools that help you perform Risk Analysis, track remediation, and prove compliance through documentation.

  • Risk registers, asset inventories, and data-flow diagrams for ePHI.
  • Policy templates for Administrative Safeguards and Technical Safeguards, including access control, encryption standards, and logging.
  • Workforce training modules and attestation records.
  • Vendor management playbooks, BAAs, and security questionnaires.
  • Breach response kits with investigation checklists and notification templates.

Conclusion

HIPAA compliance comes down to knowing where PHI lives, limiting how it’s used, and protecting it with appropriate administrative, physical, and technical controls. By performing an honest Risk Analysis, training your workforce, governing vendors, and preparing for incidents, you build a defensible program that protects patients and your organization.

FAQs.

What entities are covered under HIPAA?

Covered Entities include health plans, healthcare clearinghouses, and healthcare providers who conduct certain electronic transactions. Business Associates—vendors that create, receive, maintain, or transmit PHI for a Covered Entity—are also directly accountable for safeguarding PHI and must sign Business Associate Agreements.

How does the HIPAA Privacy Rule protect patients?

The Privacy Rule limits how PHI can be used or disclosed, requires the minimum necessary use, and grants rights to access and amend records. It compels you to provide a Notice of Privacy Practices and to obtain authorizations for most non-routine uses, giving patients meaningful control over their information.

What are the penalties for HIPAA violations?

Penalties range from corrective action plans and settlements to tiered civil monetary penalties that increase with culpability and may reach into the millions per year. Intentional misuse can bring criminal charges, and state attorneys general can pursue additional enforcement.

How does the HITECH Act relate to HIPAA?

HITECH enhances HIPAA by imposing direct obligations on Business Associates, mandating breach notifications, raising penalties, and promoting secure electronic health records. It also expanded enforcement, audits, and incentives, making strong privacy and security programs essential.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles