Vendor Risk Review for a Small Medical Practice

A practice with twelve staff doesn’t need a procurement department. It does need to know which vendor can see patient data, which service can stop tomorrow’s clinic, and who owns the unanswered questions after the contract is signed.

Takeaways

  • Tier vendors by real data, access, downtime, and exit exposure.
  • Ask for evidence that fits the tier.
  • Keep contract duties and technical proof in separate columns.
  • Recheck on material change, not only at renewal.

This review is a practice-owned decision record. It is not a HIPAA certification, vendor endorsement, or substitute for legal and security advice.

Start with the service map

HHS says risk analysis should cover all electronic protected health information the organisation creates, receives, maintains, or transmits. Its risk-analysis guidance makes scope a discovery problem. Apply that logic to the proposed service before sending a questionnaire.

VENDOR SERVICE MAP

Service and business owner: ______________________________
Patient/practice data involved: __________________________
Data created, received, stored, or transmitted: __________
User and support access: _________________________________
Connected systems: _______________________________________
Critical clinic workflow: ________________________________
Subcontractor path: ______________________________________
Downtime workaround: _____________________________________
Export, deletion, and contract-exit path: _______________

If staff can’t complete the map, the review isn’t ready for a risk score.

Three tiers beat one giant form

TierExample exposureEvidence depth
limitedno patient data, no system access, easy replacementowner, scope, access confirmation, exit note
materialrestricted practice data or workflow dependencecore controls, incident route, recovery, contract, deletion evidence
criticalePHI at scale, privileged access, or clinic-stopping dependencydeeper security evidence, subcontractors, recovery test, exit drill, approved residual-risk decision

The labels are yours. The point is to direct scarce review time at the services that can do the most damage.

For a relationship covered by HIPAA’s business-associate provisions, HHS publishes the official contract guidance. A BAA belongs in the evidence set. It doesn’t answer whether a restore has been tested or whether a support engineer can export an entire tenant.

NIST’s Cybersecurity Framework 2.0 gives organisations a risk-governance framework, including supply-chain considerations. Use it as a reference for your review method, not as a badge a vendor can award itself.

Ask for a claim, proof, and owner

Review pointVendor claimEvidence examinedGap owner and decision
identity and access
support access
event records
incident notice
backup and recovery
subcontractors
retention and deletion
export and exit

Run one tabletop before launch. Disable a user, request an export, report a suspected incident, or simulate an unavailable service with invented data. A polished questionnaire response is useful. Watching the support path work is better.

The HIPAA risk-assessment template helps place vendor findings in the practice register. The EHR downtime plan helps test operational dependence.

Patient Square is an AI clinical platform. Practice Copilot can use Patient Square EHR as the record system or work alongside an existing EHR. Review our current security page and agreement evidence, then apply the same review method you use for any vendor. We think that’s the honest standard.

FAQ

Common questions

Which medical-practice vendors need a risk review?

Review any vendor that handles practice or patient data, connects to a system, supports a critical workflow, or can materially interrupt operations. Depth should follow risk. A supplier with no sensitive data or system access needs less evidence than an EHR, billing vendor, cloud host, or AI service.

Is a signed BAA enough to approve a vendor?

No. A business associate agreement addresses required contractual duties when the relationship falls within HIPAA's business-associate rules. It does not by itself prove access control, recovery, subcontractor management, deletion, support boundaries, or operational fit. Review the actual service and evidence as well as the contract.

Should every vendor receive the same security questionnaire?

No. Start with data, access, workflow dependence, and exit difficulty, then tier the review. Reusing a short common core can help, but high-risk services need deeper evidence and a tested scenario. Low-risk office suppliers should not consume the same review effort as systems handling ePHI.

What happens when a vendor cannot answer a risk question?

Record the gap, affected workflow, interim control, owner, decision, due date, and contract consequence. The practice may reject the service, narrow its scope, add a compensating control, accept residual risk through its approved process, or require evidence before launch. Do not turn silence into a yes.

Sources

  1. HHS OCR: Business Associate Contracts and Other Arrangements.
  2. HHS OCR: Guidance on Risk Analysis under the HIPAA Security Rule.
  3. NIST Cybersecurity Framework 2.0.