A breach that reaches 500 people or more goes onto a public list with your name on it.
That list is maintained by the Office for Civil Rights, the part of the Department of Health and Human Services that enforces health privacy. Anyone can read it. That includes your customers, the people selling against you, and whoever is writing about them.
HIPAA, in three sentences
Most of what makes HIPAA feel unanswerable is that it is usually explained by somebody selling a service. The structure is small.
It is three rules. Keep the information private. Keep it secure. Say something when it gets out.
Those are the Privacy Rule, the Security Rule and the Breach Notification Rule, in the order you would guess. Everything else is detail hanging off one of the three.
It follows the data, not your org chart
Here is the part that surprises people. Anyone who handles that information on your behalf is inside the rules with you.
Your billing company. The service that sends appointment reminders. The contractor who took a copy of the database onto a laptop for a migration and still has it. Each of those is a business associate, and that relationship requires a written agreement.
The agreement is not paperwork for its own sake. It is what establishes that the other party knows they are inside the rules too. A vendor touching this data without one is a finding waiting to be made by somebody who is looking.
You cannot notify about what you cannot see
The uncomfortable version of this is a scope question you cannot answer.
If nothing in the system records who read what, then “how many people were affected” and “which records” have no answer. “We don’t know” is not a more comfortable position than a large number — it is usually treated as the larger number.
That is why audit logging, the record of who did what and when, tends to get looked at seriously after a scare rather than before one. It is cheap to add in advance and impossible to add retroactively, because the events you needed have already happened.
The question worth answering first
Not “are we compliant”. That is a legal conclusion, we are not your counsel, and anybody who gives you one over email is telling you something about themselves.
The question is whether anyone owns this. Whether one named person knows which vendors touch the data, whether there is a signed agreement with each of them, and whether the system could answer a scope question if it had to.
If somebody in your company already owns that, you do not need us. If nobody does, that is the gap. The questionnaire version of this problem is here, and you can tell us what you are dealing with first. The reply is free and a person writes it.