Evaluate healthcare software using documented controls, contractual responsibilities and the exact proposed workflow. A marketing statement about security is not enough to determine whether a system and its use meet your organization’s obligations.
Start with the proposed data flow
Write down what information the system will receive, where it will be stored, who will use it and which other services may process it. Include support access, backups, exports and optional AI features in the discussion.
Use that map to ask specific questions. “Where does a document go when uploaded?” is more useful than “Is everything secure?” Have the people responsible for privacy and security review the answers before introducing patient data.
What should a practice ask about a BAA?
A business associate agreement, or BAA, addresses responsibilities for protected health information in an applicable business-associate relationship. HHS guidance discusses these arrangements for cloud services handling electronic PHI, alongside risk analysis and safeguards. A contract does not replace implementation of those safeguards. See HHS cloud-computing guidance.
Ask which legal entity signs the agreement, which services and data it covers, and how vendor responsibilities align with your actual use. Review subprocessors, support arrangements and relevant terms with qualified advisers.
Ask for evidence of the access model
- Show how clinical, front-office, billing and supervisor access differs.
- Demonstrate how an account is removed when a team member leaves.
- Explain what activity is recorded and who can inspect that history.
- Describe how support personnel receive and lose access.
- Show how exports, backups and restoration are controlled.
These are evaluation requests, not claims that Carelumio has passed a particular assessment. Confirm each required control in the proposed product configuration.
Treat record types deliberately
HHS describes psychotherapy notes maintained separately from the medical record as a specially protected category. Do not assume that every therapy progress note belongs in that category, or that the same sharing workflow is appropriate for both. See the HHS explanation.
Other requirements may apply to your setting and records. Identify them with your clinical and privacy leads, then test the resulting requirements against the vendor’s actual storage, access and exchange design.
Use a written review record
| Ask about | Evidence to request |
|---|---|
| Hosting and data processing | Documented locations, data flow and relevant third-party services. |
| Access and activity history | A demonstration of role configuration and recorded activity. |
| Incident response | Applicable notification commitments and operational responsibilities. |
| Continuity and exit | Backup, recovery, export, return and deletion arrangements. |
| AI functionality, if used | Data use, retention, review workflow and contractual terms. |
Keep open questions visible and assign an owner to resolve them. Do not substitute a badge or broad assurance for the evidence your organization needs. This guide supports vendor evaluation; it is not legal advice or a certification of a product.