Practical vendor due diligence
Healthcare AI Governance: A Vendor Approval Checklist
Evaluate one product, one plan, and one workflow before approving an AI vendor. Use this guide to assemble evidence, record unresolved questions, and assign the decision to a responsible owner.
Open the interactive evaluation checklist1. Define the proposed use before reviewing the vendor
Write down the exact product, subscription tier, integrations, users, and intended task. A policy for one enterprise product may not cover the same company’s consumer app. Draw the path from data entry to storage, model processing, human review, and deletion.
- Name an operational owner and a security or compliance reviewer.
- List the data involved, including recordings, prompts, attachments, logs, and outputs.
- Record what the tool must not do and how staff will work if it is unavailable.
2. Ask for evidence that answers specific questions
Treat a marketing statement as a claim to investigate. Save a dated link or document reference beside each finding. A working source link is not proof that a contract covers your intended use.
- Product and plan scope: which features and integrations are covered?
- Data use: are inputs, recordings, and outputs used for training, and under which terms?
- Retention: what is kept, for how long, and what happens to backups and logs after deletion?
- Access: who can view data, including vendor support and subprocessors?
- Security and operations: what access controls, incident contacts, export options, and fallback procedures are documented?
3. Resolve the BAA and risk-analysis questions
HHS explains that a cloud provider creating, receiving, maintaining, or transmitting ePHI on behalf of a covered entity or business associate is itself a business associate, including when it holds encrypted data without the key. An applicable BAA and the organization’s own risk analysis are both necessary; a vendor badge does not replace either.
- Identify the contracting entity and exact covered services.
- Distinguish “BAA available” from “our organization has executed the applicable BAA.”
- Record permitted uses, subcontractor responsibilities, incident notification, and termination provisions. Confirm applicable obligations with the responsible reviewer.
4. Make the decision conditional on the actual evidence
Use a written decision rather than averaging unresolved issues into a reassuring score. The statuses below are a suggested internal workflow, not regulatory classifications.
- Hold: a material question remains unresolved. Assign an owner and a due date.
- Pilot with conditions: specify permitted data, users, duration, human review, and stop conditions.
- Approve a defined use: record the exact product, configuration, evidence references, approver, and review trigger.
- Decline: explain the unresolved requirement and what evidence would allow reconsideration.
Worked example: evaluating an ambient documentation tool
Illustrative example only; this is not a review of a named vendor or a real customer engagement. A practice wants to turn visit audio into draft notes. The vendor advertises BAA availability, but the proposed plan’s coverage and audio-retention terms are not yet documented.
- Initial decision: hold use with patient data while those questions remain open.
- Evidence requested: applicable agreement, covered plan and features, recording retention and deletion terms, support access, and training policy.
- Proposed pilot conditions after review: limited authorized users, clinician review of every draft, a correction process, and a defined end date.
- Reopen review if the plan, model, integration, data use, or contractual terms change.
Copy this vendor approval record
Use the fields below in your own approval document. Keep confidential contracts and patient data in your organization’s approved systems, not in a public review request.
- Vendor / product / plan / proposed workflow:
- Operational owner / reviewers / decision date:
- Data types / integrations / storage and access locations:
- Evidence references / document versions / dates checked:
- BAA applicability / execution status / covered services:
- Open questions / responsible person / due date:
- Decision / allowed uses / restrictions / human oversight:
- Review date / change triggers / incident contact / exit plan:
Review when the risk changes
Set a review cadence appropriate to the use and your organization’s requirements. Also review material changes rather than waiting for a calendar date: new data types, new features, different models, contract changes, incidents, or a change in vendor ownership.
- Recheck the source documents and record what changed.
- Confirm restrictions are still enforced in the deployed configuration.
- Retire unused access and document data return or deletion when ending the service.
What VNDRIQ can and cannot establish
Use the registry to locate vendor records and organize due diligence. Source coverage varies by record. Automated source-check dates, editorial review dates, vendor claims, and internal assessments are different kinds of information. A listing or score is not certification, a signed agreement, or approval for your organization.
- Open the evidence links and confirm they cover the product you intend to use.
- Treat missing information as an open question, not a favorable finding.
- Use the interactive evaluation checklist to record the review; make the final decision through your organization’s responsible reviewers.
Source and scope
The HHS source supports the cloud-service and BAA discussion. The checklist, decision record, and example are VNDRIQ editorial guidance, not an official government template or legal determination.
HHS: Guidance on HIPAA and Cloud ComputingHave a vendor question?
Bring the vendor name, product, plan, and intended workflow. Identify what is still unknown.
Request a vendor review