ePHIJournal · Vol. 01 · The Independent Practice Issue

Your IT Company Runs Scans. Is That a HIPAA Risk Analysis?

A technical vulnerability scan and a regulatory risk analysis are useful—but different—tools.

November 2026 · Regulatory information checked November 3, 2026 · Read the full issue

A clean vulnerability report can be valuable—but it does not automatically satisfy HIPAA’s requirement for a comprehensive Security Risk Analysis (SRA). Here is why the distinction matters.

Two different questions

A technical scan asks whether particular software, devices or networks exhibit detectable weaknesses: an outdated application, an exposed service, a missing patch or a misconfiguration. Its output is usually a list of technical findings and possible fixes.

A HIPAA risk analysis asks a broader management question: what reasonably anticipated threats and vulnerabilities could affect the confidentiality, integrity or availability of all the ePHI the organization creates, receives, maintains or transmits? Its scope includes not only technical assets but also personnel, procedures, vendors, physical locations, backups and operations.

Where ePHI actually travels

Consider a two-physician office. Patient data may be stored in its cloud EHR, sent to a laboratory, viewed from a billing workstation, exported for a referral, included in patient emails or backed up by a managed services provider. The scanner used by its IT company may not see each of those processes, contractual relationships or physical safeguards.

A sound SRA records where ePHI exists and moves, what can go wrong, the safeguards already present, the likelihood and impact of plausible events, and the residual risks that remain. Its exact method can vary with practice size and complexity; OCR does not mandate a single proprietary scoring model.

The evidence behind the judgment

A useful assessment is not merely a spreadsheet marked “compliant.” It should be supported by interviews, system and vendor inventories, documented observations, policy review, available configuration evidence and decisions about risk. When a conclusion depends on the office manager’s assertion or a vendor’s representation, that limitation should be visible. The purpose is not to collect the largest possible binder. It is to enable decisions the physician and office manager can understand, defend and follow through on.

Risk analysis is not risk management

A risk analysis identifies and evaluates risks. Risk management is the distinct obligation to implement security measures sufficient to reduce those risks to a reasonable and appropriate level. Finding a risk is not the same as addressing it. A credible SRA should therefore produce a usable route into corrective action.

The questions to ask an IT vendor

  • Scope: Does the work cover every location, information system and vendor that handles ePHI—or only the local network?
  • Threats: Are human error, inappropriate access, downtime, physical loss and third-party issues evaluated alongside malware?
  • Risk method: Are likelihood and impact explained and documented, rather than replaced by a generic pass/fail score?
  • Evidence: Which findings were observed, supported by records or reported by personnel?
  • Follow-through: Does the practice receive a prioritized remediation list and a way to monitor progress?

What a usable SRA deliverable looks like

A practical report should identify scope and assumptions, describe the practice’s ePHI environment, document material threats and vulnerabilities, characterize risk, summarize existing safeguards, and identify corrective priorities. It should also make ownership and follow-up responsibilities clear without claiming that the report itself makes the practice fully compliant.

A small office can begin today by locating its most recent SRA, asking who approved it, checking whether it includes the current EHR and vendors, and comparing its findings with actual remediation records. If the practice cannot produce those materials, that is a reason to investigate—not automatically proof of a HIPAA violation.

A measured first step

An accurate, comprehensive baseline is the foundation for future updates and better spending decisions. It prevents the practice from treating every technology purchase as equally urgent and directs effort toward risks that matter most.

Takeaway: Ask whether the document in your file is a technical scan, a broader risk analysis, or both. Know which responsibility it actually fulfills.

ePHIShield’s Security Risk Analysis page describes what its assessment delivers and includes a sample report.

Scroll to Top