HIPAA compliance is meeting the Privacy, Security and Breach Notification Rules of the US Health Insurance Portability and Accountability Act, which apply to covered entities and to the business associates that handle protected health information for them.
Built to save your team time and money: every control is tied to its evidence, so internal reviews can run shorter and your evidence is in order when a customer, insurer or regulator asks.
Here is the part people get wrong
HIPAA does not come with a certificate, and it does not hand you a fixed checklist either. The Security Rule, 45 CFR Part 164 Subpart C, requires administrative, physical and technical safeguards for electronic protected health information, and it starts with a risk analysis: you identify where the information lives, what threatens it, and which safeguards are reasonable and appropriate for your size and systems (source: eCFR, 45 CFR Part 164 Subpart C). The HHS Office for Civil Rights enforces the rules, and in an investigation the first request is that risk analysis and the records behind it (source: HHS, the Security Rule).
So the gap is rarely legal. It is evidence: a risk analysis nobody has updated, training nobody can prove, access reviews that live in someone's inbox. The Breach Notification Rule adds a clock, since affected individuals must be notified without unreasonable delay and no later than 60 days after a breach is discovered (source: HHS, Breach Notification Rule), which is a hard thing to meet from a shared drive.
What the platform does
- Security Rule safeguards pre-loaded as controls, each with an owner and a due date
- Risk register for the risk analysis, with treatment plans and review dates
- Readiness check that shows the gap, with tasks created from the result
- Policies with acknowledgement tracking, so workforce training and sign off are on record
- One evidence repository for access reviews, logs, agreements and screenshots, tagged to the control
- Read only auditor portal for a customer's assessor or your own counsel
- The same evidence carries SOC 2, which many health care buyers ask for alongside HIPAA
Where your data sits
SecuritComply runs on dedicated cloud infrastructure in Toronto, Canada, with the application, the database and file storage together in one region. A client instance can be hosted in a United States region on request. Every plan includes unlimited users, multi factor authentication, tenant isolation and encryption at rest, with the price published on the pricing page. Selling to Canadian health care as well? The Canadian edition of this page covers PHIPA and PIPEDA next to HIPAA.
How long it takes
There is no honest single number, and you should be careful with anyone who gives you one before they have seen your environment.
Three things decide your timeline. The first is how much you have to protect: the number of systems, sites and assets in scope. The second is how many people touch them, because every user needs access rules, training and a record. The third is where you start. A team with written policies and working controls moves fast. A team starting from a blank page does not.
The readiness check is how you find out. It shows what is already in place and what is missing, and that gap is your real timeline.
Get your free accountHIPAA compliance FAQ
Who has to comply with HIPAA?▾
Covered entities (health plans, health care clearinghouses and providers that transmit health information electronically) and their business associates, the vendors that create, receive, maintain or transmit protected health information on their behalf. A software company serving US hospitals or clinics is usually a business associate.
Is there a HIPAA certificate?▾
There is no official HIPAA certification program. Compliance is shown through documented safeguards, a current risk analysis and the records that prove the safeguards operate, and the HHS Office for Civil Rights enforces the rules. SecuritComply holds those records in one place.
What does the Security Rule require?▾
Administrative, physical and technical safeguards for electronic protected health information, including a risk analysis, workforce training, access controls, audit controls and transmission security, set out in 45 CFR Part 164 Subpart C.
How long does HIPAA compliance take?▾
There is no honest single number. Three things decide it: how many systems and assets touch protected health information, how many people use them, and how much you already have in place. The readiness check shows your real gap, and that gap sets your timeline.
Where is our data hosted?▾
In Toronto, Canada by default, on dedicated infrastructure. A client instance can be set up in a United States region on request; tell us when you create your account.
