No vendor badge or product label proves that a patient survey tool complies with HIPAA. The HHS Office for Civil Rights does not endorse or certify products, so the answer comes from checking your own workflow. Map the data, settle each party's regulated role, and review any required business associate agreement. Then run your own risk analysis, check the vendor's safeguards and contract, and test the setup before any electronic protected health information (ePHI) goes in.
This checklist is an evaluation framework, not a legal opinion or security certification. Privacy and security counsel can help determine which federal, state, professional, and contractual requirements apply to a specific organization and data flow.
Is the vendor a business associate?
Under HHS guidance, a vendor is a business associate when it performs functions or services for a covered entity involving access to protected health information. HIPAA duties depend on the entity and relationship, not the product category. The HHS overview of covered entities and business associates explains which groups and functions fall within the rules. Document your own role, whether the vendor performs a business-associate function, and what data it handles on your behalf.
The HHS cloud computing guidance says a cloud service provider that maintains ePHI for a regulated entity is generally a business associate. That remains true when the data is encrypted and the provider holds no decryption key. The same guidance says encryption alone cannot provide the confidentiality, integrity, and availability that the Security Rule requires.
Map the data before you decide. List every field collected, including names, contact details, patient identifiers, questionnaire answers, scores, free text, and appointment context. Add device data, support messages, logs, and backups, and trace where each field is created, sent, stored, viewed, exported, kept, and deleted. Include subprocessors and support access. A patient-linked PHQ-9 response is the obvious item, but less visible metadata and backups belong on the map too.
What should the business associate agreement cover?
When the vendor is a business associate, the organization needs the right contract before the vendor handles ePHI. The HHS sample business associate agreement provisions cover the core terms. These include allowed uses and disclosures, safeguards, reports, help with individual rights, subcontractors, return or destruction of data when feasible, and termination. Do not stop at the signature page: compare the agreement with the actual service, data flow, support model, and subprocessors.
Then check the service agreement and its schedules for these terms:
- Permitted data uses, disclosures, and any secondary-use restrictions
- Subcontractor obligations and change notification
- Security-incident and breach-notification responsibilities
- Data access, export, correction, return, deletion, and termination
- Availability, backup, recovery, support, and downtime commitments
- Responsibility for configuration, identity, devices, and integrations
- Conflicts between sales claims, technical documentation, and signed terms
A business associate agreement is necessary when the relationship requires one, but it does not establish that the configuration or workflow is safe. That evidence comes from your risk analysis and your own tests.
Does your risk analysis cover the tool?
The HHS Security Rule summary organizes safeguards into administrative, physical, and technical categories. The HHS risk analysis guidance says organizations must consider all the ePHI they create, receive, maintain, or transmit. It also says no single method guarantees compliance, and HHS does not prescribe one. Examine how the system protects the privacy, integrity, and availability of data across its life. Include key management, identity, endpoints, backups, exports, support access, and recovery.
Evaluate the proposed workflow in your own environment. A vendor questionnaire can inform the review, but it cannot replace it. Record threats, gaps, current controls, likelihood, impact, remaining risk, assigned actions, and approval. Revisit the analysis when the content, user roles, integration, subprocessor, setup, or data flow changes.
What evidence should you ask the vendor for?
Match each important claim to a document, configuration screen, log, contract clause, or representative test. Until you see that evidence, a security page or questionnaire answer is only a claim.
| Review area | Evidence to request or verify |
|---|---|
| Identity and access | Unique accounts, role design, authentication options, provisioning, removal, privileged access, and periodic review |
| Audit controls | Which events are recorded, who can view or change logs, timestamps, exports, alerting, and the organization's review process |
| Integrity | Validation, version history, corrections, duplicate handling, scoring provenance, and detection of failed transfers |
| Transmission and storage | Protected connections and storage, key responsibility, backups, exports, and documented exceptions |
| Availability | Service monitoring, backup scope, recovery procedures, downtime behavior, recovery tests, and customer responsibilities |
| Data lifecycle | Retention configuration, legal holds, export, deletion, backup aging, account closure, and evidence of completion |
| Incident response | Reporting channels, triage, cooperation, evidence preservation, notification roles, and tested contacts |
Use non-patient data for tests. Create accounts with different roles and attempt blocked access. Remove a user and inspect the audit events. Export and correct a record, simulate a failed link, and confirm what happens at account closure. Do not put real patient data into a trial until the relationship, agreement, setup, and approval are in place.
The EHR integration guide describes technical reconciliation tests for questionnaire records. The staff training guide covers role competency and downtime drills.
How will the vendor handle a breach?
Ask how the vendor identifies, contains, investigates, documents, and reports events. Confirm current contacts, escalation coverage, forensic cooperation, subprocessor coordination, and responsibility for required notices. Test the communication path with a tabletop exercise rather than discovering it during an incident.
The HHS breach-notification guidance sets different duties for covered entities and business associates. A business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery. Treat 60 days as an outer limit, not a service target. HHS's sample agreement notes that the parties may set a stricter timeframe for the business associate to report a potential breach. A shorter contract term gives the covered entity time to investigate and meet its own duties.
Do not assume that encryption resolves every incident. The facts, safeguards, access, key exposure, and legal analysis all matter. Preserve evidence and use the organization's incident and breach review process.
How do you approve the tool?
Record the decision, the approving roles, the evidence reviewed, the setup baseline, remaining risks, required contract changes, and conditions for use. List which data and workflows are allowed. Set review triggers for major product, integration, subprocessor, security, or legal changes.
The approval should show that the organization chose, set up, contracted for, and manages the service to meet its duties for this use. Re-run the representative tests at each review trigger. For remote care, apply the same discipline to the teletherapy assessment workflow.
