Which of the Following Is Not a Purpose of HIPAA? What the Law Does—and Doesn’t—Cover

Check out the new compliance progress tracker


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

Which of the Following Is Not a Purpose of HIPAA? What the Law Does—and Doesn’t—Cover

Kevin Henry

HIPAA

July 17, 2025

6 minutes read
Share this article
Which of the Following Is Not a Purpose of HIPAA? What the Law Does—and Doesn’t—Cover

HIPAA's Main Purposes

When you ask “Which of the following is not a purpose of HIPAA?” the clearest answer is this: HIPAA was designed to protect Protected Health Information and streamline health data exchange—not to regulate clinical quality or force providers to use electronic records. Its core aims are portability of insurance coverage, health data confidentiality, and standardized electronic transactions.

Enacted in 1996, HIPAA improves coverage portability between jobs, combats fraud and abuse, and establishes Administrative Simplification Provisions that make routine healthcare transactions more consistent. Together with its Privacy and Security Rule Standards, the law forms a national baseline for how PHI may be created, used, shared, and safeguarded.

What HIPAA does—and does not—aim to do

  • Does: Protect PHI, set Privacy Rule Compliance expectations, and require safeguards for electronic PHI.
  • Does: Standardize electronic claims, eligibility checks, and remittances to reduce administrative burden.
  • Does not: Regulate healthcare quality, clinical practice standards, or prices.
  • Does not: Mandate adoption of electronic medical records (EMRs) for every provider.

HIPAA's Privacy Rule

The Privacy Rule sets national standards for how covered entities—health plans, most healthcare providers, and clearinghouses—and their business associates may use and disclose PHI. It balances Health Data Confidentiality with the need to share information for treatment, payment, and healthcare operations without unnecessary friction.

Under the rule, you have rights: to access and obtain copies of your records, request amendments, receive a Notice of Privacy Practices, and—subject to exceptions—get an accounting of certain disclosures. Organizations must follow the minimum necessary standard, limit uses to defined purposes, and secure appropriate authorizations for non-routine uses such as most marketing.

Privacy Rule Compliance also requires workforce training, policies and procedures, and mitigation steps if improper uses or disclosures occur. De-identified data, when stripped of specified identifiers or validated by expert determination, falls outside PHI and may be used more freely.

HIPAA's Security Rule

The Security Rule applies to electronic PHI (ePHI) and requires a risk-based program of administrative, physical, and technical safeguards. Rather than prescribing one-size-fits-all tools, it sets Security Rule Standards that scale to an organization’s size, complexity, and risk profile.

Key expectations include ongoing risk analysis and management, role-based access, authentication, audit controls, contingency planning, and workforce security. Encryption is “addressable,” meaning you must implement it when reasonable and appropriate or document an equivalent, effective alternative to protect ePHI.

Documentation, periodic evaluations, and incident response are integral. If a breach of unsecured PHI occurs, federal breach-notification requirements—added to HIPAA by later amendments—may apply.

HIPAA's Administrative Simplification

The Administrative Simplification Provisions standardize electronic transactions to lower cost and error. Common transactions—claims, eligibility inquiries, claim status, referrals, and remittance advice—use uniform formats and code sets so systems can “speak the same language.”

Code sets such as ICD and CPT/HCPCS ensure consistent clinical and billing terminology. Unique identifiers, including the National Provider Identifier for providers, reduce ambiguity. Operating rules further harmonize how payers and providers exchange information across Health Information Technology systems.

Ready to simplify HIPAA compliance?

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

HIPAA's Exclusions

HIPAA does not cover every piece of health-related information. Personal Health Data Exemptions include de-identified data and information you keep solely for yourself in consumer apps or wearables that are not offered by, or on behalf of, a covered entity. In such cases, other consumer protection laws may apply, but HIPAA typically does not.

Employment records held by an employer, education records protected by FERPA, and life insurance records are generally outside HIPAA. Law enforcement and courts can receive certain disclosures under defined exceptions, but they are not “covered entities” under the rule. Always remember: HIPAA protects PHI handled by covered entities and business associates, not all health-related data everywhere.

Healthcare Quality Regulation

Regulating clinical quality is not a purpose of HIPAA. The law does not set standards of care, dictate treatment pathways, license professionals, or score hospitals on outcomes. Other regulators and programs address those areas.

HIPAA does, however, permit data uses and disclosures that support quality improvement, patient safety activities, and public health. In short, it enables appropriate information flow while keeping PHI protections intact—but it does not grade or police the quality of care you receive.

Electronic Medical Records Mandates

HIPAA does not require providers to adopt electronic medical records. If a practice uses only paper, it can still be HIPAA-compliant. Once ePHI is created, received, maintained, or transmitted, the Security Rule applies and appropriate safeguards must be in place.

Widespread EMR adoption has been driven primarily by separate incentives and programs under broader Health Information Technology policy, not by HIPAA itself. HIPAA’s role is to protect PHI within whatever record system you use—paper or electronic—not to mandate a specific technology.

Conclusion

HIPAA’s purposes are to protect PHI, enable Privacy Rule Compliance and Security Rule Standards, and streamline data exchange through Administrative Simplification Provisions. It does not regulate healthcare quality or mandate EMRs. Knowing this boundary helps you design compliant processes, choose appropriate technologies, and avoid misconceptions that create unnecessary risk.

FAQs.

What does HIPAA protect in healthcare?

HIPAA protects the confidentiality, integrity, and availability of Protected Health Information. The Privacy Rule limits when PHI can be used or disclosed, and the Security Rule sets safeguards for ePHI. You also have rights to access and request corrections to your records as part of Privacy Rule Compliance.

What is excluded from HIPAA regulations?

HIPAA generally does not cover employment records, FERPA-protected education records, life insurance records, or data you keep in consumer apps and wearables that are not provided by a covered entity. These Personal Health Data Exemptions mean not all health-related information falls under HIPAA, though other laws may still apply.

Does HIPAA regulate healthcare quality?

No. HIPAA does not set clinical quality standards or determine the standard of care. Its focus is health data confidentiality, appropriate information sharing, and Security Rule Standards for ePHI—not grading or enforcing care quality.

Does HIPAA require electronic medical records?

No. HIPAA does not mandate EMRs. It requires safeguards when you handle ePHI and supports secure Health Information Technology, but separate programs—not HIPAA—drove the push for electronic records.

Share this article

Ready to simplify HIPAA compliance?

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

Related Articles