The short answer
"Support" in a health IT contract can mean a ticket queue, a named implementation team that disappears at go-live, an advisory retainer billed separately, or an ongoing relationship included in the subscription. These cost very different amounts and the difference is rarely visible on a feature comparison page.
The reliable test is not what the marketing page says. It is what the order form itemizes, and what happens in month seven.
Four support models, and how to recognize them
Reactive ticket support. You submit an issue, it is triaged against a severity table, and a response target applies. This is the baseline and it is almost always included. It answers "the system is broken." It does not answer "is our configuration defensible."
Implementation-only expertise. A specialist team is assigned for onboarding, data migration, and training, then rolls off at a defined milestone. Recognize it by a statement of work with an end date, or by phrase like "through go-live."
Advisory purchased separately. Ongoing expert guidance exists as a distinct named service with its own line item. Virtual CISO and similar retainer offerings sit here. This is a legitimate model and often a good one. It is simply not included, and a comparison that reads it as included understates the cost.
Included ongoing advisory. Access to a person with subject expertise, available through the term, at no additional charge. Recognize it by its absence from the price schedule as a separate line.
None of these is inherently better. The failure is buying one while budgeting for another.
What "included" usually means
Three phrases carry most of the ambiguity.
"Dedicated support" frequently means a named account manager for commercial matters rather than a subject matter expert. Ask what that person's role is and what questions they are qualified to answer.
"Unlimited support" almost always scopes to the ticket queue, not to advisory hours.
"Onboarding included" is a project, not a relationship. Ask for the end condition in writing.
Questions that expose the model
Put these in the evaluation, in this order.
- After go-live, who do we call with a question that is not a system defect, and what is that person's role?
- Is there a cap on hours, interactions, or scope for that access?
- Which of the services in your proposal appear as separate line items on the order form?
- If we need expert time in month seven and again in month eleven, what does each cost?
- Does the assigned team change at renewal?
- What happens to advisory access if we do not buy the optional services?
Question three is the one that settles it. Marketing pages describe a relationship. Order forms price it.
The renewal cliff
A common pattern: heavy expert involvement through implementation, a quiet middle period, then a scramble before the annual assessment or survey when the organization discovers that the people who set the system up are no longer engaged and the knowledge left with them.
This is not vendor bad faith. It is what an implementation-only model produces by design. The cost surfaces as either an urgent professional services purchase or as internal staff time nobody budgeted.
Two things reduce the risk. Ask during evaluation what a typical month eight looks like for a customer of your size. Ask for a reference from an organization that is at least two years in, rather than one that recently went live.
Reading the order form
The order form is the honest document. Work through it this way.
| What you see | What to ask |
|---|---|
| A line item with a term shorter than the subscription | What happens when it ends |
| "Professional services" as a pooled hours block | What the rate is once the block is used |
| Support tiers named in an exhibit rather than the body | Which tier the quoted price includes |
| An optional service that appears in the proposal narrative but not the pricing table | Whether it is included or was quoted separately |
| Travel or onsite fees under expenses | What triggers an onsite visit and who decides |
FAQ
Is included advisory always better than a separate retainer?
No. A separate retainer often buys deeper and more senior time. The problem is only when a buyer compares an included model against a retainer model on subscription price alone, which understates the retainer total.
How do I compare two vendors when one bundles and one itemizes?
Build a three-year total that adds the bundled subscription on one side and the subscription plus the expected services spend on the other. Ask each vendor what a customer of your size typically spends on services annually.
What is a reasonable response target for a health IT system?
It varies by severity tier, and the tier definitions matter more than the hours. Read how the contract defines a severity one incident. A definition that requires complete unavailability of the entire system will rarely be met by a real outage affecting one department.
Should support commitments be in the contract or an SLA exhibit?
Either can be binding. What matters is that the exhibit is incorporated by reference and cannot be changed unilaterally during the term.