Built for medical clinics, physician groups and ambulatory networks
The new MA's first week is the same twenty questions, asked of the same one person
Ambulatory medicine runs on material nobody calls a policy library: EHR training workbooks, rooming checklists, payer-specific referral rules, front-desk scripts. It is real documentation, often excellent — and in practice the clinic runs on the memory of a lead MA and a practice manager, because asking them is faster than finding page 40.
What actually breaks
The workbook answers it — six clicks deep
The order of draw, the rooming sequence, the Secure Chat etiquette: all documented, in a training workbook the new hire saw once during orientation. Nobody reopens a seventy-page PDF mid-clinic. They ask the person who knows, and that person has patients of her own.
Payer rules are per-plan, per-service, per-location
Whether a referral needs an authorization depends on the plan, the service and sometimes which location performs it. That matrix lives partly in bulletins, partly in a scheduler's head, and every departure takes a payer's worth of exceptions out the door.
Locations drift until the drift becomes policy
The same visit type is checked in three ways at three sites, each defended as how we do it here. Nobody decided this; it accumulated. New staff learn whichever version their trainer knew, and the differences only surface when someone floats.
The upgrade moved the button
Quarterly EHR upgrades rearrange workflows, and the tip sheets are updated on education's schedule, not the upgrade's. For a few weeks the documentation describes last version's screens — exactly when questions are most frequent.
The documents this covers
- EHR training workbooks and tip sheets
- Rooming and intake workflows
- Referral and prior-authorization rules by payer
- Front-desk check-in and checkout procedures
- Patient portal activation and proxy access guides
- Immunization and standing-order protocols
- Telehealth visit workflows
- Per-location scheduling and escalation differences
Who feels it
- Practice managers
- Medical assistants
- LVNs and RNs
- Front desk leads
- Referral coordinators
- Schedulers
- Clinic educators and superusers
Why a governed corpus matters here
A clinic group answers to HIPAA and to every payer that audits it, and the operational questions that fill an MA's day — scope of task, standing orders, what this plan requires before that referral — deserve answers from the approved source rather than from whoever is nearest. Role-scoped retrieval matters here for the same reason training is role-specific, and a multi-location group needs the answer for this location, not the one that happens to rank first.
Questions we get asked
Does this replace our EHR training?
No — it makes the training you already paid for reachable after orientation ends. The workbooks and tip sheets your educators maintain become documents staff can ask questions of, with the answer citing the page it came from.
Our locations genuinely do things differently. Does that break it?
It is the reason location-aware retrieval exists. Where the difference is deliberate, each site gets its own answer; where it is drift nobody chose, the unanswered-question log tends to surface it — which is the first step to deciding what the policy actually is.
Who keeps the corpus current?
Your administrators approve what goes in, and every question the assistant cannot answer is logged as a gap for them to close. The system gets better at exactly the rate your team feeds it — we are honest that this takes an owner, usually the practice manager or clinic educator.
See it answer a question you actually have
30-minute demo. No slide deck. We show you the actual product with your kind of data — Epic tip sheets, clinical workflows, support resolutions. If it doesn't click, no hard feelings.
Or email [email protected] if you prefer to skip the form.