HIPAA security risk analysis.Central Valley healthcare
The HIPAA Security Rule calls for a risk analysis: an accurate and thorough assessment of the risks and vulnerabilities to electronic protected health information. It is the foundation the rest of the Security Rule stands on — and a requirement federal enforcers keep citing. We write the analysis, with a follow-up list that is kept current, for healthcare organizations across the Central Valley: clinics, practices, and the business associates that serve them.
Every engagement starts with a first look, at no charge.
The work is reviewed and signed by Brian Olson, CMMC Registered Practitioner.
When it comes up
The organization has no risk analysis, or has one that is years old and describes an environment that no longer exists.
A new EHR, a new location, a new vendor, or a merger changed where health information lives.
Staff are already using AI tools with patient information, with no written rules.
A business associate agreement, a customer, or an insurer asks for the analysis.
The last analysis was a checklist or a tool output, with no risk ratings and no method behind it.
What you receive
A written security risk analysis
Covering the full environment: every system, device, and location where electronic protected health information is created, received, maintained, or transmitted, including personal devices, cloud services, and vendors.
Risk ratings with a stated method
Threats and vulnerabilities identified specifically, likelihood and impact assessed, and a defensible order for what gets fixed first.
A follow-up list, kept current
Which risks get fixed, in what order, by whom, by when — and which are accepted, by whom, in writing.
Clear rules for AI tools and patient information
What may go into which tools, so the AI use policy and the risk analysis tell the same story.
Review by a practitioner
Brian Olson spent fourteen years inside a healthcare organization, the last three as the IT director responsible for security and compliance. He reviews and signs what we deliver.
What a risk analysis is not
Not a checklist. Not a tool output alone. A questionnaire produces no risk ratings; a scanner produces findings, not judgment. An analysis requires both: the evidence from the environment, and a person applying judgment to what it means for this organization. If it isn’t written down — the method, the evidence, the people involved — it didn’t happen. That is how an investigator will read it.
Straight answers.
What people ask about HIPAA security risk analysis.
How often must the risk analysis be done?
At least annually, and whenever the environment changes materially — a new system, a new vendor, a new location. The follow-up list is kept current between analyses.
Does the analysis have to be done by an outside firm?
No. It must be accurate and thorough, and the person conducting it must be competent. Many small practices use an outside practitioner because the work requires both clinical-workflow knowledge and security knowledge.
We had an analysis done two years ago. Is it still good?
Only if nothing changed in two years. Systems, vendors, staff, and threats all change. The first look includes whether your current analysis still covers the full environment.
What does it cost?
It depends on the size and complexity of the environment, so we don’t list prices. The scope is in writing before any work starts. The first look costs nothing.
Start with a first look.
A short review of where your organization stands on the Security Rule’s requirements, and a short report signed by a person. No charge, no obligation. A person gets back to you within one business day.
