Framework brief · US law
HIPAA is a duty. Not a badge.
If your product touches protected health information for a covered entity, the customer will ask you to sign for that duty. There is no official certificate that ends the question.
Current as of November 2026. Operator brief, not legal advice.
All six frameworksWhat it is
A statute, three rules, one enforcement office.
HIPAA is US federal law. The Department of Health and Human Services, through the Office for Civil Rights, enforces it. The three rules operators actually feel are the Privacy Rule, the Security Rule, and the Breach Notification Rule.
The Privacy Rule governs protected health information broadly: who may see it, for what purpose, and what the individual can ask. The Security Rule governs electronic PHI — administrative, physical, and technical safeguards, beginning with a risk analysis. The Breach Notification Rule is the clock and the audience when unsecured PHI is compromised.
If a vendor sold you a HIPAA certificate, you bought a costume.
Who it binds
Covered entities, and you if you are in the chain.
Covered entities are health plans, healthcare clearinghouses, and healthcare providers who transmit health information electronically in standard transactions. Most software companies are not those. They become business associates when they create, receive, maintain, or transmit PHI for a covered entity — or for another business associate.
That is the commercial moment. The customer will not debate your architecture until the business associate agreement is on the table. No BAA, no PHI. HardStack does not advertise a BAA. Carbon installs in your environment so the documentation work does not require sending PHI to us.
A product sold to patients in Europe can owe GDPR as well. A BAA does not answer that. A US health-data duty and a European personal-data duty can sit on the same build.
What done looks like
It does not look like a date on a certificate. It looks like the ability to show, when a customer, an acquirer, or OCR asks:
- A risk analysis of electronic PHI, and safeguards chosen because of it — not a template with the company name swapped in.
- The BAA chain: who touches PHI, under what contract.
- Access that matches the job, and a minimum-necessary practice someone can describe without a slide.
- A breach procedure. Notice to individuals goes without unreasonable delay and no later than 60 days after discovery. HHS, and in larger breaches the media, are part of that procedure. The outside limit is not a target.
What a SOC 2 does not cover
Security controls rhyme. Encryption, access reviews, and logging show up in both. That is where a crosswalk earns its keep.
It stops there. A SOC 2 opinion does not cover minimum necessary, patient access rights, the content of a BAA, or breach notification to individuals and to HHS. A hospital that accepts “we have SOC 2” in place of those is taking a risk OCR will not share.
HITRUST is a separate certifiable framework some healthcare buyers ask for. It is not HIPAA, and it is not a substitute for the statute. If a deal names both, treat them as two workstreams that can share evidence.
What the company has to be able to show
Where PHI lives. Who is a business associate. Which safeguards are administrative, which are technical, which are physical. How a workforce member gets access, and how it is removed. How you would know a breach had happened, and who calls whom. How subcontractors are bound.
The failure mode is a risk analysis written to satisfy a checkbox, disconnected from the system that actually shipped. OCR has asked for the risk analysis first for years. If it does not describe this product, it does not describe your duty.
Where Carbon stops
We do not certify HIPAA. Nobody official does.
If HIPAA is a cue on the build, Carbon shapes the documentation package to that duty — requirements, risk, evidence, traceability — in your environment, on your LLM. It does not sign a BAA, and it does not replace counsel or a risk analysis of the system you actually operate.
Request a trialRelated briefs