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
| Tier | Example exposure | Evidence depth |
|---|---|---|
| limited | no patient data, no system access, easy replacement | owner, scope, access confirmation, exit note |
| material | restricted practice data or workflow dependence | core controls, incident route, recovery, contract, deletion evidence |
| critical | ePHI at scale, privileged access, or clinic-stopping dependency | deeper 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 point | Vendor claim | Evidence examined | Gap 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.