HIPAA Privacy Rule Explained: What Covered Entities Must Do to Comply

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 Privacy Rule Explained: What Covered Entities Must Do to Comply

Kevin Henry

HIPAA

January 30, 2025

7 minutes read
Share this article
HIPAA Privacy Rule Explained: What Covered Entities Must Do to Comply

If you handle patient information, the HIPAA Privacy Rule explained here shows exactly what covered entities must do to comply. This guide translates legal requirements into actionable steps so you can protect Protected Health Information and meet regulators’ expectations.

This overview is for general information and does not constitute legal advice.

Covered Entities Overview

The Privacy Rule applies to three types of covered entities: health plans, health care clearinghouses, and health care providers that transmit health information electronically in connection with standard transactions. If you fall into one of these categories, the rule governs how you use, disclose, and safeguard PHI.

  • Health plans: insurers, HMOs, Medicare, Medicaid, employer group health plans.
  • Health care providers: hospitals, physicians, dentists, pharmacies, laboratories, and others that conduct electronic standard transactions.
  • Health care clearinghouses: entities that translate data between billing/claims formats.

Business associates are not covered entities, but when they handle PHI for you, they must comply through business associate agreements. Hybrid entities (such as universities with clinics) must designate their health care components and apply Privacy Policies accordingly.

Understanding Protected Health Information

Protected Health Information (PHI) is individually identifiable health information that relates to a person’s past, present, or future health, the provision of care, or payment for care, and that identifies the person or could reasonably identify them. PHI can exist in any medium—paper, oral, or electronic (ePHI).

  • Common examples: names, addresses, full-face photos, device serial numbers, medical record numbers, claim details, diagnoses, lab results, and billing data.
  • Not PHI: truly de-identified data, education records covered by FERPA, and employment records held by you in your role as employer.

You can de-identify data by expert determination or by removing specific identifiers and ensuring no actual knowledge of re-identification risk. Limited data sets may be used for research, public health, or operations with a data use agreement.

Applying the Minimum Necessary Standard

The Minimum Necessary Standard requires you to limit uses, disclosures, and requests for PHI to the least amount needed to accomplish the purpose. It is a practical, role-based control that reduces risk and improves privacy.

When the standard applies

  • Internal uses for operations: limit access to workforce members who need it.
  • External disclosures: provide only the portion of PHI required by the requester’s stated purpose.
  • Requests for PHI: ask only for what you truly need.

Key exceptions

  • Disclosures to the individual.
  • Uses or disclosures for treatment.
  • Uses/disclosures made pursuant to a valid authorization.
  • Disclosures required by law or to the Department of Health and Human Services.

Operational tips

  • Create role-based access matrices and standard protocols for routine disclosures.
  • Use de-identified or limited data sets wherever feasible.
  • Embed the Minimum Necessary Standard into request forms, workflows, and Workforce Training.
  • Audit queries and reports to ensure they pull only the needed fields.

Developing Privacy Policies and Procedures

Privacy Policies and procedures are the backbone of compliance. They document how you use and disclose PHI, honor individual rights, and manage third parties. Keep them current, practical, and consistently enforced.

Core policy elements

  • Notice of Privacy Practices (NPP): explain your uses/disclosures, rights, and how to complain.
  • Authorizations: when required, content standards, tracking, and revocation handling.
  • Individual rights: access, amendments, accounting of disclosures, restrictions, and confidential communications.
  • Minimum necessary: role-based rules, routine protocols, and approval pathways for non-routine disclosures.
  • Business associate management: due diligence, agreements, and oversight.
  • Sanctions and mitigation: disciplinary actions and steps to lessen harmful effects of improper disclosures.
  • Documentation and retention: keep policies, forms, and decisions for required retention periods.

Operationalize policies with clear procedures, checklists, and templated forms. Align Privacy Rule requirements with your security, records management, and incident response programs to prevent gaps.

Ready to simplify HIPAA compliance?

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

Workforce Training and Designation of Privacy Official

You must train your workforce on HIPAA privacy requirements and your internal policies. Provide training at onboarding, when job duties change, and when policies are updated, with periodic refreshers to reinforce the Minimum Necessary Standard and acceptable use.

  • Cover PHI definitions, permissible uses/disclosures, authorizations, and the complaint process.
  • Teach role-based scenarios, including how to handle requests from family, law enforcement, or media.
  • Document completion dates, content covered, and attendance; track remedial training when needed.

Designate a privacy official responsible for developing and implementing policies, and a contact person to receive complaints and provide information on your NPP. Ensure they have authority, resources, and direct access to leadership.

Implementing Data Safeguards

The Privacy Rule requires appropriate safeguards to prevent impermissible uses and disclosures. Coordinate your privacy program with Administrative Safeguards, Physical Safeguards, and Technical Safeguards commonly associated with the Security Rule for ePHI.

Administrative Safeguards

  • Risk-based access management, workforce clearance, and role-based permissions.
  • Policies for workstation use, data handling, and secure disposal of records.
  • Vendor oversight and contingency planning for downtime and emergencies.

Physical safeguards

  • Controlled facility access, clean desk protocols, and secure file storage.
  • Device and media controls, including encrypted storage and verified destruction.

Technical Safeguards

  • Unique user IDs, strong authentication, and automatic logoff.
  • Access controls and audit logging to monitor PHI activity.
  • Encryption in transit and at rest where reasonable and appropriate.
  • Data loss prevention and minimum necessary configurations in analytics tools.

Handling Complaints and Enforcement Procedures

You must maintain a clear, non-retaliatory process for receiving and investigating privacy complaints. Identify where to submit complaints internally, how investigations occur, and how outcomes are documented and communicated.

  • Apply and document sanctions for workforce violations in line with your policies.
  • Mitigate harmful effects of impermissible uses or disclosures without delay.
  • Coordinate with incident response for breach analysis and notifications required under related rules.
  • Retain documentation of decisions, training, sanctions, and complaints for required periods.

Regulatory enforcement is led by the Office for Civil Rights. Violations can trigger corrective action plans, monitoring, and significant Civil and Criminal Penalties. Civil penalties scale by culpability (from lack of knowledge to willful neglect), and criminal penalties may apply for knowing misuse of PHI. Penalty amounts are adjusted periodically and can involve substantial fines and, for criminal cases, possible imprisonment.

In practice, sustained compliance comes from culture: clear leadership, practical processes, continuous Workforce Training, and measurable safeguards that make the Minimum Necessary Standard the default.

FAQs

What types of organizations are covered entities under HIPAA?

Covered entities include health plans (such as insurers, HMOs, Medicare, Medicaid, and employer group health plans), health care clearinghouses, and health care providers who transmit health information electronically in connection with standard transactions like claims or eligibility checks.

How is Protected Health Information defined under the Privacy Rule?

PHI is individually identifiable health information related to a person’s health, care, or payment for care that identifies the person or could reasonably identify them. It covers paper, oral, and electronic forms, excludes de-identified data and certain education or employment records, and is subject to the Minimum Necessary Standard for most uses and disclosures.

What are the requirements for workforce training under HIPAA?

You must train workforce members on your Privacy Policies and procedures as appropriate to their roles. Training occurs at onboarding, when job duties or policies change, and with periodic refreshers. You must document training completion and provide targeted remedial training after incidents or audit findings.

What penalties exist for violations of the HIPAA Privacy Rule?

Enforcement by the Office for Civil Rights can result in civil monetary penalties that scale by culpability and are adjusted over time, resolution agreements with corrective action plans, and, for knowing wrongful disclosures or misuse, criminal penalties that may include fines and imprisonment. Reputational harm and required notifications can add significant operational and financial impact.

Share this article

Ready to simplify HIPAA compliance?

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

Related Articles