Why “SRA” and “risk analysis” — are they the same thing?
Mostly, yes, in everyday use. “Risk analysis” is the term the HIPAA Security Rule itself uses. “SRA” is the shorthand most practices use day to day. The deliverable is the same: a formal, evidence-backed analysis of risk to your ePHI.
Is this the same as the free HHS SRA Tool?
No. The HHS SRA Tool is a self-guided questionnaire — useful as a starting point, but it records what you tell it. Our assessment independently validates your answers against technical evidence from your systems. If you've outgrown the tool, this is the next step.
We had an SRA done last year. Why do it again?
Because staff change, systems change, and vendors change. The Security Rule expects the analysis to be current. An existing-SRA review can also tell you whether last year's assessment meaningfully reflected your technical environment before you commission a full one again.
Is this a “HIPAA audit”?
Not in the regulatory sense — only OCR conducts HIPAA audits. What most people mean by a “HIPAA audit” is an independent third-party assessment of their HIPAA security posture. That's what this is: an independent assessment conducted with the rigor an auditor would expect to see.
Will this make us “HIPAA certified”?
There is no such thing as HIPAA certification — no government body issues one. An evidence-backed risk analysis gives you something real: documented proof that you performed a serious, thorough analysis and are addressing what it found.
Does this guarantee we'll pass an OCR audit?
No honest assessor can promise that. What it does is put you in a defensible position: an accurate, thorough risk analysis, grounded in evidence, with documented follow-through on findings.
Do you work with our MSP?
Yes. We coordinate evidence collection with your IT team or MSP, and the remediation roadmap is built for them to execute. The difference is that the assessment itself is independent — your MSP doesn't grade its own homework.