A software demonstration is a useful introduction to a product. Choosing a system also means understanding how it will work for your team, how it will connect to existing tools and what the agreement will require after the sale.
Bring a short, written set of questions to each supplier. It gives clinical, operational, technical and purchasing colleagues a common way to discuss the options, even when the products take different approaches.
1. Which task should the software improve?
Choose a specific workflow and describe it from the user’s point of view. Who starts the task, what information do they need and what happens next? Ask the supplier to demonstrate that sequence, including an exception or an incomplete record.
Write down the points that need further investigation. A clear account of the work gives the team something concrete to evaluate during a trial or reference call.
2. What will implementation involve?
Ask for the proposed timetable, responsibilities and training arrangements. Identify the data that needs to move, the systems that need to connect and the people who will maintain those connections. Request written details of any interface work included in the quote.
The federal guide EHR Contracts Untangled covers requirements planning, integration and system performance as contracting considerations. Use the applicable sections as prompts for your technical and legal teams when assessing the proposed agreement.
3. How will information be handled?
Map the information the product receives, where it is processed and who can access it. Ask about user permissions, backups, incident communication and the responsibilities of any subcontractors.
For HIPAA-regulated organizations evaluating cloud services that handle electronic protected health information, HHS guidance addresses business associate agreements and risk analysis. Bring the proposed service and its data flows to your privacy and security reviewers so they can assess the arrangement in context.
4. What does the AI feature actually do?
If AI is part of the offer, identify its task and where a person reviews the output. Ask what evidence supports the proposed use, which situations it has been evaluated in and how users report an error. For any claimed improvement, ask how it was measured and what it was compared with.
NIST’s voluntary AI Risk Management Framework provides a reference for discussing the evaluation and management of AI-related risks. Product-specific questions still need product-specific answers. Record which version was demonstrated and ask how changes are communicated to customers.
5. What is included in the price?
Request an itemized proposal. Separate subscription or license fees from implementation, migration, integration, training and ongoing support. Ask which activities attract additional charges and what happens at renewal.
Use the same assumptions when comparing proposals: users, locations, included modules and expected activity. Where a supplier cannot yet price an integration or migration task, mark it as an open item for the purchasing team.
6. What happens if you change suppliers?
Ask how the organization can obtain its information, which export formats are available and what transition assistance costs. Review the support commitment and responsibilities during a move. EHR Contracts Untangled includes dedicated sections on data rights and switching systems that can inform this discussion.
Before the decision meeting, turn the answers into a concise comparison of demonstrated functions, written commitments and unresolved questions. The organization’s clinical, technical, privacy and legal reviewers can then assess the proposal against their respective requirements.
Sources & references
- EHR Contracts Untangled · Office of the National Coordinator for Health Information Technology
- Guidance on HIPAA & Cloud Computing · U.S. Department of Health and Human Services
- AI Risk Management Framework · National Institute of Standards and Technology