Blog

Rhapsody Health Solutions Team

5 Questions to Ask When Calling a Reference During the RFP Process

When engaging in a RFP process for a new software vendor, calling references is arguably one of the most important steps of the process. Although it can be time-consuming to coordinate calls and analyze all the feedback, the comments of peers who have recently gone through the same process can be invaluable. One of the toughest things about reference calls is narrowing down what to ask. Below are five questions which are recommended for any reference call:

1. Would you buy from the vendor again?

If the vendor gave you this customer as a reference, then the answer is likely “Yes!” But, this is a broad-based opening question to let the reference elaborate on whether there are any little things about the vendor which are bothering them.

2. Did the vendor do what they said they would do?

This is an opportunity to find out if any promises were broken during the sales cycle. Did the vendor promise a feature that never came to be, or was not quite what they had promised?


{{cta(‘aa1521cb-5277-4f92-afda-230e28538341’)}}

3. How close was the expected level of complexity to the actual level of complexity?

This question is meant to give a sense of how honest the vendor was in presenting the ease-of-use with respect to their product. Did they make things seem much easier than they are?  Did they steer the demo to a few things they were good at, while effectively glazing over some ease-of-use issues?

4. Have you ever been “boxed-in” with the software, not being able to solve a problem?

It is important that the software will have the flexibility to accomplish everything you want it to. If the reference has ever run into a situation where they could not accomplish a task with the software, it is critical to know that.

5. How easy has the software been to maintain?

Configuring and setting up the product is sometimes the main focus of a demo, but it is also vitally important to understand how the software is maintained and supported. A software that is easy to configure, but hard to maintain, will cause more headaches in the long run because maintenance issues go on forever.

The White Paper, The thirteen steps of highly successful HL7 engine selections, available on HIMSS’ website, offers more steps to help you choose the right integration engine for your needs.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
First Name*
Last Name*

Related Blogs

Shannon Matthews

Rhapsody Brings AI-Powered Payer Interoperability Suite to Connection Hub on Epic Showroom, Accelerating Integration for Epic Payer Customers

Rhapsody’s AI-powered Payer Interoperability Suite is now available in the Connection Hub on Epic Showroom, helping Epic payer customers accelerate integration, automate complex workflows, and achieve interoperability outcomes faster.

Read More >

Read more

Rhapsody Health Solutions Team

How University of Rochester Medicine Is Using AI to Reduce Integration Burden and Accelerate Development 

Learn how University of Rochester Medicine is using Rhapsody Axon’s AI-powered capabilities to accelerate integration development, reduce manual effort, and help interoperability teams scale their work without adding headcount.

Read More >

Read more

Kevin Day, Chief Technology Officer

Before You Evaluate AI, Define the Problem You’re Trying to Solve 

Before investing in AI, healthcare organizations should define the problem they want to solve. Discover how a problem-first approach drives measurable results.

Read More >

Read more