Skip to main content

Practice Operations

Have You Done My Specialty? How to Get a Real Answer

What a vendor should be able to tell you about your specialty before you sign, which differences actually change the build, and the answers that mean nothing.

9 min read

It is the question every practice asks on the first call, and the one that produces the least useful answer in the entire evaluation: have you worked with a practice like mine?

The answer is almost always yes. It is usually even true. And it tells you nothing, because the question as asked can be satisfied by a logo on a slide, and what the practice actually wants to know is whether the vendor understands the handful of rules that make its own front office difficult.

The better question is narrower and harder to deflect. It is not whether a vendor has seen your specialty. It is whether the vendor can name what is different about your specialty’s front office before you explain it.

Why the specialty label is the wrong unit

Specialty is a useful word for a directory and a poor one for scoping work. Two orthopedic groups in the same city can run front offices that share almost nothing: one is heavy workers’ compensation with an in-house surgery center, the other is sports medicine with same-day access and no procedural scheduling at all. The specialty name is identical. The build is not.

What actually drives the work is a small set of structural facts, and they cut across specialty lines:

  • How many appointment types the practice really uses, and how many of those have rules attached that a scheduler has to know.
  • Whether a visit requires something before it can be booked at all, such as a referral on file, an authorization, imaging, a records request or a prepayment.
  • Whether providers have individual rules rather than a shared template, and how often those change.
  • Where coverage sits in the sequence, which differs sharply between a practice billing medical benefits only and one juggling medical against vision or dental benefits.
  • What share of volume is procedural, because procedural scheduling carries windows and prerequisites that routine visits do not.
  • Who holds the exceptions today. In most practices one or two people carry the rules in their heads, and that is the knowledge a vendor has to capture.

A vendor fluent in those six things will do good work in a specialty it has never named. A vendor that can only offer the specialty label will rebuild your rules by trial and error, on your schedule, in front of your patients.

What a real answer sounds like

Ask the question in a form that cannot be answered with a logo. Three versions that work:

“Name three things about my specialty’s front office you would expect to be different, before I tell you.” A vendor that has genuinely done the work will get most of it right and will be specific. For a pain practice it should reach authorization windows and procedural scheduling quickly. For optometry it should raise the vision-versus-medical benefit split unprompted. For behavioral health it should raise consent and records handling before anything else.

“Walk me through how you would schedule one visit type I will pick.” Then pick the awkward one, not the routine one. The answer should include what gets checked before booking, what happens when a prerequisite is missing, and who gets told. Watch for whether the vendor asks you clarifying questions. Scoping questions are the sign of someone who has done this; a confident answer with no questions is the sign of someone who has not.

“What did you get wrong the first time at a practice like mine, and what changed?” This is the most informative of the three and the one most vendors handle badly. Every real deployment has a correction in it. A vendor with no answer has either not deployed or is not being straight with you.

The answers that mean nothing

Four responses that sound like substance and are not:

A customer count in your specialty. Deployment at a practice that shares your specialty label says nothing about whether it shares your rules. Ask what that practice’s appointment type structure looked like, and you will quickly learn whether it resembles yours.

A specialty listed on a marketplace profile. A specialty tag is a category selection, not evidence of a build. It is worth exactly what any self-reported field is worth.

An outcome metric with no workflow attached. A percentage improvement is uninterpretable without the workflow it was measured on, the period, and the denominator. This applies to every vendor, including us. Ask for all three or discount the number.

“We’re configurable.” Everything is configurable. The useful questions are who does the configuring, how long a change takes, and whether you can make one without waiting for a release.

What we can tell you, and what we will not

The Pretty Good AI platform is listed across 20 specialties on the athenahealth Marketplace, and we work with practices of varying sizes and complexity. Customer-reported results. Your numbers will vary by workflow, staffing, seasonality and call mix.

That is a Marketplace listing scope, not a count of specialties with live deployments. It does not establish that your practice’s rules already exist in a template somewhere, and we would rather say so than let the specialty count do work it cannot do. Our actual claim is narrower and more useful: we build to the workflow a practice already runs, so an unusual rule is a scoping conversation rather than a feature request. We only build on athenaOne, which is what makes that possible. Depth across the platform is the reason an odd requirement is buildable at all, and most vendors on the marketplace pick a narrower wedge and build deeply inside it.

Clinical decisions stay with your clinicians in every specialty, without exception. Everything described here is front-office logistics: booking a visit, checking coverage, chasing paperwork, routing a task to the right queue. What care a patient needs, and the urgency of it, is your care team’s and is never the agent’s.

A multi-site group, and the rule nobody had written down

A multi-specialty group ran a scoping session on a single appointment type: a procedural visit that required an authorization and imaging on file before it could be booked. The group’s staff had described the rule confidently in the first conversation. In the walkthrough, the scheduler who actually did the work added a seventh condition nobody in the room had mentioned, about a specific payer that needed the imaging read rather than just the imaging.

That condition was not in any document. It lived with one person. Finding it during scoping cost an hour. Finding it after go-live would have meant visits moving, and the practice concluding the automation did not understand its specialty, when in fact nobody had ever told anyone the rule.

The lesson is for both sides. The vendor’s job is to ask the question that surfaces the undocumented rule. The practice’s job is to put the person who actually runs the workflow in the room, not only the person who manages it.

Bring one workflow to the scoping call

The fastest way to get a real answer to the specialty question is to stop asking it and run a walkthrough instead. Pick your most annoying appointment type. Have the person who schedules it on the call. Ask the vendor to walk it backwards from the booked visit: what gets checked, what blocks a booking, what happens when something is missing, who hears about it.

An hour of that tells you more than any customer list. It also produces something useful regardless of which vendor you pick, which is a written version of a rule your practice has been carrying in one person’s head.

For the structural side of the same conversation, the athenahealth surfaces a vendor actually touches covers what to ask about the integration itself, and proving an integration claim covers how to verify what a vendor says it reads and writes. The specialty question and the integration question are usually asked separately and are really the same question asked from two ends.

Ready to See It in Action?

Tell us how your front office runs today and we will walk one real workflow from your specialty

Schedule a Demo →

Written by Kevin Henrikson