The gap between what EMR software does in a demo and what it does in your clinic at 4:40pm on a Thursday is where most practice frustration comes from. That gap is almost never a lie. It is usually a roadmap item described in the present tense, an integration that depends on a partner you have not signed with, or a capability that exists but only under conditions nobody mentioned.
The four questions
Ask every vendor on your shortlist the same four things, in writing, and keep the answers. Written answers behave differently from spoken ones.
1. Which of these capabilities are live today, and which are roadmap?
Then ask them to show you where their own website distinguishes the two. Most cannot, because most sites present shipped and planned functionality in one undifferentiated list of checkmarks. A vendor who has thought about this will have an answer ready. A vendor who has not will explain why the distinction is complicated.
Follow-up worth asking: “What date was that feature released, and can I talk to a practice using it?” A capability with no release date and no reference user is a roadmap item wearing a present tense.
2. For your three headline claims, what is the evidence?
Not a demo. A demo shows that the software can do the thing once, on prepared data, driven by someone who built it. Ask instead for the automated test that keeps it working, the reference customer who uses it weekly, or the audit that validated it.
This question separates vendors who measure their own claims from vendors who write them. Both exist, and the difference is invisible from the outside until you ask.
3. What does your product not do that competitors do? Name three.
This is the question that does the work. Every product has real gaps. A vendor who cannot name three either does not understand their market or is unwilling to tell you something inconvenient — and you will find out which during implementation.
Listen for whether the gaps are specific. “We are not as customizable as Epic” is a non-answer. “We have no native dermoscopy image storage, no pathology lab interface, and no EPCS” is an answer.
4. What would make you tell me not to buy your software?
A good vendor has a real answer, because a bad-fit customer is expensive for them too. If the honest answer is “nothing, we are right for everyone,” you have learned that they will say anything to close, which tells you how to read every other answer they gave.
Four traps in the demo itself
- The prepared patient. Demos run on a chart built to make the software look good. Ask them to create a new patient from scratch, mid-demo, and complete the workflow you actually care about. Time it.
- The driver effect. The person demoing has used the product for years. Ask to drive yourself for ten minutes. What you are measuring is not the software, it is how much of it is discoverable.
- The happy path. Ask what happens when something fails — a lab interface goes down, a claim rejects, a note is signed in error. The failure paths are where clinicians actually spend their frustration.
- The integration hand-wave. “We integrate with that” can mean a live production connection, a documented API nobody has used, or a partnership announcement. Ask which, and ask how many of their customers have it running today.
Words that need definitions before you sign
These terms are used loosely across the industry. Get each one defined in writing, in your contract, with the specific scope attached:
- “Integrated” — with whom, in production, for how many current customers, and who pays for the interface build?
- “Supports HIPAA” — a BAA is a document, not a security posture. Ask separately about encryption, audit logging, access controls, and breach notification terms.
- “AI-powered” — what specifically does the model do, what does the clinician review before it becomes part of the record, and who is accountable for an error?
- “Certified” — for what, by whom, and is the certification current? Certification programs are specific and checkable.
- “Included” — in which tier, for how long, and what happens to the price at renewal?
Two contract clauses worth asking for
Most practices negotiate price and nothing else. These two protect you from the specific failure this article is about:
- Roadmap contingency. If you are buying partly on a promised capability, name it in the contract with a date, and attach a remedy if it slips — a discount, a release right, or an escrow. A vendor confident in the date will negotiate. A vendor who refuses to name a date has told you something.
- Data egress, priced up front. Ask what it costs to get your complete records out in a usable format, and get the number in writing before you sign rather than during a migration you have already decided on.
Why we published this
Every technique above works on us, and some of them will produce answers we do not enjoy giving. We think that is the correct trade. We maintain a public list of what our own software does not do, generated from the internal system that blocks our marketing copy when it exceeds what we have verified — so the list cannot quietly drift out of date.
Use this guide on every vendor you are considering. If we come out badly on a dimension that matters to your practice, you should buy the other one.