HIPAA privacy and security readiness
A hospital, a clinic software supplier and a billing processor all meet HIPAA the same way: a customer or a regulator asks for the risk analysis and the evidence behind it. Readiness is having both before the question.
The short version
HIPAA readiness is the work of showing, with records, that the privacy, security and breach-notification requirements for protected health information are met in the systems that hold it, before a regulator or a customer asks.
HIPAA applies to covered entities, which are health plans, health care clearinghouses and health care providers that transmit health information electronically in connection with covered transactions, and to their business associates, which are the people who perform certain functions for them that involve protected health information. The definitions are in 45 CFR 160.103. A Canadian supplier to a US customer is often a business associate; HIPAA for Canadian SaaS covers that case.
The risk analysis
The Security Rule requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of electronic protected health information, and it is the document regulators ask for first. The requirement is at 45 CFR 164.308(a)(1)(ii)(A). We build it from the actual systems: where the data sits, who can reach it, and what is and is not protected, using the same data map that privacy work uses.
The output is a document your own people can update each year, with a finding for each risk and an owner and a date for each fix.
Safeguards and the evidence for them
For each safeguard the Security Rule names, we collect the artifact that shows it is operating: the access-control export, the log configuration, the encryption setting, the backup test. A policy that says a control exists is not evidence that it does. Technical hardening itself is under security services, and the wider frameworks are on PCI, HIPAA and CPCSC readiness.
Business associates and vendors
A covered entity may let a business associate handle electronic protected health information only after obtaining satisfactory assurances, documented in a written contract or other arrangement, and a business associate needs the same assurances from a subcontractor (45 CFR 164.308(b)). We list the vendors that touch protected health information, check that each has that documentation in place, and give your counsel the gaps. The wording of an agreement is for counsel; the process is in vendor management and security and privacy terms in technology contracts.
The breach clock
After a breach of unsecured protected health information, the individual must be told without unreasonable delay and no later than 60 calendar days after discovery; the media must be told within the same limit when more than 500 residents of a state or jurisdiction are involved; and HHS is told at the same time as the individuals for breaches of 500 or more people, and within 60 days of the end of the calendar year for smaller ones.
Whether a breach has occurred, and whether notice is required, is a legal decision for your counsel; our work is the facts, the timeline and the evidence that decision rests on. The text is in the Breach Notification Rule. For the first day of an event, see incident readiness and the US notification table.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What does HIPAA readiness cover?
HIPAA readiness is the work of showing, with records, that the privacy, security and breach-notification requirements for protected health information are met in the systems that hold it, before a regulator or a customer asks.
Who does HIPAA apply to?
HIPAA applies to covered entities, which are health plans, health care clearinghouses and health care providers that transmit health information electronically in connection with covered transactions, and to their business associates, which are the people who perform certain functions for them that involve protected health information.
What is the HIPAA risk analysis?
The Security Rule requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of electronic protected health information, and it is the document regulators ask for first.
What are the breach notification deadlines?
After a breach of unsecured protected health information, the individual must be told without unreasonable delay and no later than 60 calendar days after discovery; the media must be told within the same limit when more than 500 residents of a state or jurisdiction are involved; and HHS is told at the same time as the individuals for breaches of 500 or more people, and within 60 days of the end of the calendar year for smaller ones.
Do you decide whether a breach must be reported?
Whether a breach has occurred, and whether notice is required, is a legal decision for your counsel; our work is the facts, the timeline and the evidence that decision rests on.
Tell us what holds the health data
Say whether you are a covered entity or a business associate, and which systems hold the data. The reply says what a scope would cover. Other US rules are on the United States page.