← Back to blog

HIPAA Explained: The Law, the Rules and What Vendors Face

November 14, 2026
HIPAA Explained: The Law, the Rules and What Vendors Face

HIPAA is the Health Insurance Portability and Accountability Act of 1996, a U.S. federal law that began as a way to help people keep their health insurance coverage and grew into the country's core framework for protecting health information. If you sell software or services to healthcare organizations, HIPAA reaches you through your customers' contracts and through the security questionnaires they send before they buy. Skypher automates the answering of those questionnaires, so this guide covers the law in the depth a vendor needs and then shows where the daily work lands.

Skypher
Answer HIPAA Questionnaires Faster
Skypher uses AI-driven automation to help teams answer security questionnaires, with support for multiple formats and real-time collaboration.
Visit

TL;DR

  • HIPAA is a 1996 U.S. law with five titles. Title II, Administrative Simplification, produced the Privacy, Security, Enforcement and Breach Notification Rules that security and compliance teams work with.
  • It applies to covered entities (health plans, clearinghouses, and providers that transmit health data electronically) and to their business associates, which includes many software vendors.
  • Business associates are directly liable for certain HIPAA provisions, on top of what their contracts say.
  • For vendors, HIPAA shows up as long due diligence questionnaires from healthcare buyers. Speed and consistent answers decide how fast deals move.
  • Some HIPAA rules are still in flux, so check HHS for the status of any proposed change before you answer a customer.

Table of Contents

What HIPAA is and why it exists

Congress passed HIPAA in 1996. According to the Texas Department of State Health Services, its main purpose was to help consumers maintain their insurance coverage. It also contains Administrative Simplification provisions, which aim to make the health care system more efficient through standardized electronic transactions, unique health identifiers, and privacy and security standards for individually identifiable health information.

Those provisions are where most of the modern compliance work comes from. Sections 261 through 264 of the Act require the Secretary of HHS to publish standards for the electronic exchange, privacy and security of health information. HHS is the U.S. Department of Health and Human Services, and its Office for Civil Rights enforces the rules.

The five titles

The law is organized into five titles, as the Wikipedia article on HIPAA lays out:

  1. Title I protects health insurance coverage for workers and their families when they change or lose their jobs.
  2. Title II, Administrative Simplification, requires national standards for electronic health care transactions and national identifiers.
  3. Title III sets guidelines for pre-tax medical spending accounts.
  4. Title IV sets guidelines for group health plans.
  5. Title V governs company-owned life insurance policies.

When a customer says "HIPAA compliance," they almost always mean Title II and the regulations built on it. Titles I, III, IV and V rarely come up in a vendor's security review.

The HIPAA rules in one table

You will see "the three rules" and "the five rules" in different guides. They are summaries of the same regulatory package, not different laws. HHS says the full set of Administrative Simplification regulations sits at 45 CFR Parts 160, 162 and 164 and includes the Transactions and Code Set Standards, Identifier Standards, Privacy Rule, Security Rule, Enforcement Rule and Breach Notification Rule.

RuleWhat it governsWhy a vendor cares
Privacy RuleHow protected health information may be used and disclosed, and patient rightsDefines what your customer may share with you and under what agreement
Security RuleSafeguards for electronic protected health information (ePHI): administrative, physical and technicalSource of most questions in security questionnaires
Breach Notification RuleNotice to patients, HHS and sometimes the media after a breachDrives incident response and reporting clauses in contracts
Enforcement RuleHow investigations and penalties workSets the stakes of a failure
Transactions, Code Sets and IdentifiersStandard electronic formats and identifiersMatters mainly if you handle claims or billing data

A few dates help place them. HHS published the Privacy Rule as a final regulation on December 28, 2000, after receiving more than 52,000 public comments, and published modifications in final form on August 14, 2002. Privacy regulations were implemented on April 14, 2003. The Security Rule final rule was issued on February 20, 2003 and covers three kinds of safeguards for ePHI, according to Wikipedia. For a business-focused walkthrough of that rule, see our guide to the HIPAA Security Rule for businesses.

What HITECH and the Omnibus Rule changed

The HITECH Act, enacted on February 17, 2009 as part of the American Recovery and Reinvestment Act, extended direct liability to business associates and established the Breach Notification Rule. HHS then announced a final rule on January 25, 2013 implementing HITECH provisions. That Omnibus Rule became binding on September 23, 2013 and, per a 2026 explainer, widened the business associate definition to capture cloud and storage vendors.

If you host, process or even store health data for a customer, this is the change that matters most to you.

Who must comply: covered entities, business associates and PHI

Two definitions decide whether HIPAA applies to a company.

Protected health information (PHI) is, according to HHS, individually identifiable health information held or transmitted by a covered entity or its business associate, in any form: electronic, paper or oral. It covers information about someone's past, present or future health or condition, their care, or payment for care, when it identifies the person or could reasonably be used to do so. Employment records a covered entity keeps as an employer, and education records under FERPA, are excluded.

Covered entities are health plans, health care clearinghouses, and health care providers that transmit health information electronically in connection with standard transactions. Business associates are people or organizations outside a covered entity's workforce that perform functions or services involving PHI on its behalf.

That second group is where B2B software companies sit. HHS states that, in addition to contractual obligations under a business associate agreement, business associates are directly liable for compliance with certain provisions of the HIPAA Rules. A signed agreement does not close the question: the law applies to you as well.

Patient rights and permitted uses, in brief

Vendors do not manage patient requests day to day, but you should understand what your customers are allowed to do, because your product often supports it. According to CMS, patients may examine and get a copy of their records, including an electronic copy, request corrections, and restrict their health plan's access to information about treatment they paid for in cash. Providers may share information for treatment, payment and health care operations without a signed consent form.

HIPAA also sets a floor, not a ceiling. The ONC guide notes that more protective state laws may require written authorization where HIPAA would permit disclosure without it, and HIPAA does not override them. A customer in a state with stricter rules may therefore ask for controls that go beyond federal minimums.

Violations, breaches and penalties

The Breach Notification Rule requires covered entities and business associates to notify affected patients, HHS, and in some cases the media when a breach involves PHI. A breach usually means PHI was used or shared in a way the Privacy Rule does not allow, putting its privacy or security at risk. Our article on HIPAA breaches, deadlines and response goes through the reporting steps.

Penalty figures are published on a schedule and adjusted over time. The schedule published on January 28, 2026 ranged from $145 per violation up to $2,190,294, with a 2019 notice of enforcement discretion applying lower annual caps to the first three tiers. Check the current HHS notice before quoting a number to a customer.

Two real cases show how enforcement plays out:

  • In 2024 the HHS Departmental Appeals Board affirmed a $70,000 civil money penalty against Gums Dental Care for willful neglect of the patient access requirement.
  • HHS imposed a $4,348,000 penalty on M.D. Anderson after lost unencrypted devices holding ePHI. The Fifth Circuit vacated that penalty, finding the decision arbitrary and capricious because the organization had implemented a mechanism to encrypt ePHI.

The second case carries a practical lesson: documented, implemented safeguards matter in enforcement. For more on how investigations unfold, read HIPAA enforcement for compliance officers.

Why HIPAA is controversial

People searching for HIPAA often land on the "controversy" question, and the evidence points to two themes.

Research friction. In a 2007 national survey, 67.8% of respondents (875 people) rated HIPAA as making research more difficult at level 4 or 5 on a five-point scale, and only about a quarter perceived better participant privacy.

Misunderstanding. A study of information-release practices identified 70 HIPAA-related barriers, including inconsistent institutional interpretation and too few staff confident in release decisions. The AMA Journal of Ethics reports that providers have wrongly believed HIPAA requires authorization for treatment-related sharing or forbids talking with families, which causes delays and extra paperwork.

There is also a privacy debate over de-identified data. Stanford HAI reports that de-identified data are no longer protected by HIPAA, may be shared or sold, and can potentially be re-identified when combined with other datasets.

For a vendor, the takeaway is practical: customers interpret the rules differently, so questionnaires vary widely in what they ask and how strictly.

Why HIPAA is controversial

What has changed recently

HIPAA is not static. HHS's regulatory initiatives page says a federal court vacated most of the 2024 reproductive-health Privacy Rule on June 18, 2025, and that compliance with the remaining Notice of Privacy Practices changes was required by February 16, 2026. It describes the December 27, 2024 Security Rule cybersecurity changes as a proposed rule.

As of February 16, 2026, covered entities must also include information about Part 2 substance-use-disorder records in their Notices of Privacy Practices. Separately, HHS has proposed changes to strengthen patient access and support care coordination, estimating savings of $3.2 billion over five years.

Because status changes, keep a single approved answer for each regulatory question and update it when HHS updates its page, rather than rewriting answers deal by deal.

Where HIPAA lands on a vendor's desk

Most vendors meet HIPAA as a document. A healthcare customer sends a security questionnaire or due diligence questionnaire (DDQ) before signing, asking how you encrypt ePHI, who has access, how you handle incidents, whether you will sign a business associate agreement, and which audits you have passed. It may arrive as a spreadsheet, a web form or a portal task.

The pattern is familiar to CISOs, GRC leads and solution engineers:

  1. Sales needs the answers to move the deal.
  2. Security owns the truth behind the answers.
  3. Each new questionnaire repeats 70 to 90 percent of the last one in slightly different words.
  4. Answers drift between questionnaires, and a mismatch becomes its own risk.

The fix is a maintained knowledge base of approved answers, tied to your policies, that feeds every response. That is how our platform works: you keep your security content in one place with document versioning, and the retrieval AI draws on it to answer any format. Each answer carries a confidence score from our own models, so your team reviews the uncertain ones and moves quickly through the rest. We built it so a questionnaire of 200 questions can be answered in under a minute.

It also fits the tools your team already uses: we integrate with Slack and MS Teams, with Confluence, Notion, Google Drive, OneDrive and SharePoint as content sources, and with more than 40 third-party risk management platforms and portals, including OneTrust and ServiceNow, so portal-based HIPAA questionnaires do not need copy and paste.

If you want the surrounding compliance work, these guides help: HIPAA assessments show how to find gaps, and the 30 to 90 day PCI DSS and HIPAA crosswalk helps teams that handle both card and health data.

Turn HIPAA questionnaires into a fast, consistent process

Our Questionnaire Automation Tool takes the questionnaire in whatever format the healthcare buyer sends, answers it from your approved content, and lets security, sales and engineering collaborate in real time with unlimited users. For buyers who want answers before they ask, our Trust Center lets you publish your security and compliance posture on a customizable, customer-facing page. If your deals involve investor or fiduciary diligence, see DDQ automation. Pricing is quote-based, and you can see how plans are structured on the pricing page.

Skypher

Support is available around the clock for enterprise teams through our premium support package.

Our perspective

HIPAA is often taught as a list of rules, but vendors experience it as a stream of questions. The law does not change much from one hospital to the next. The wording of the questionnaire does.

We think the right response is to treat your security answers as a product: written once, reviewed by the people who own the controls, versioned, and reused with care. A team that answers from memory in a spreadsheet will eventually contradict itself. A team that answers from a single approved source will not.

That is why we built retrieval AI with confidence scoring rather than a generic chatbot. Your reviewers should see where an answer is strong and where it needs a human, and a Trust Center should let a healthcare buyer find the basics without opening a ticket.

Compliance leaders get time back for the work only they can do, and sales leaders get shorter cycles. That combination is what we are building for.

Gaspard

FAQ

What are the five HIPAA rules?

The usual five are the Privacy Rule, Security Rule, Breach Notification Rule, Enforcement Rule, and the Transactions and Code Set and Identifier standards. HHS lists all of them within 45 CFR Parts 160, 162 and 164. The shorter "three rules" summary usually names only Privacy, Security and Breach Notification.

Does HIPAA apply to a software company?

It does when you create, receive, maintain or transmit PHI on behalf of a covered entity, which makes you a business associate. HHS notes that business associates are directly liable for certain provisions in addition to their contract duties. The Omnibus Rule widened the definition to cover cloud and storage vendors.

Is there a HIPAA certification?

The regulations HHS publishes set requirements, and compliance is measured against them. Customers still ask how you meet the Security Rule, so keep documented answers and evidence ready. A HIPAA logo guide is not needed here, but our note on displaying HIPAA claims on websites covers how to describe your status accurately.

Why is HIPAA controversial?

Critics point to the friction it adds to research, with a 2007 survey showing most researchers found it made studies harder, and to confusion among providers about what it allows. A second debate concerns whether de-identified data is protected well enough, as Stanford HAI discusses.

What should I do first when a healthcare buyer sends a HIPAA questionnaire?

Confirm whether you will handle PHI and need a business associate agreement, then answer from your approved security content rather than from scratch. Route technical questions to the control owner. Our guide to cybersecurity compliance tips for tech and finance teams adds more on building that routine.

Sources