Connecting your practice system · 4 of 6
Teaching Mesio your system
You click around your own software once. What Mesio takes from that is the shape of the screen, and never what is written on it.
Mesio cannot know in advance where your particular system keeps a perio chart. So on browser-based systems you show it, once, by using your software the way you already do.
What you actually do
Open a patient, go to the places you would normally go. The chart, the notes, the insurance page. That is it. You are not configuring anything or filling in a form describing your software.
What it takes from that
The structure of the page. Where a field sits, what it sits next to, how to get back to it. The shape of the screen rather than its contents.
Patient information is not part of what is learned. What gets kept describes where things are, not what they say. That is what makes the next part acceptable.
Why your practice benefits from other practices
Practice systems look the same across the offices that use them. So when one practice's setup has been proven to work, every other practice on that same layout benefits, without anyone at those practices doing anything.
This is why the product gets better on its own between releases. Someone else's successful setup becomes your working integration.
Two limits make that safe. What is shared is page structure, never anything about a patient or a practice. And a newly learned setup is used only by the practice that produced it until it has actually been proven, so a one-off that happened to work somewhere is not pushed onto anyone else.
When it gets something wrong
A learned location can go stale when your vendor changes their screens. Mesio treats a field it is no longer confident about as a miss rather than writing into the wrong box, which means the failure mode is work not being done rather than work being done somewhere wrong.
From there it finds its way back, or falls to a route that needs a little more from you.
You are not locked into what it learned
Where Mesio has not learned your system, the other routes still work. Teaching it is how you get more automation, not how you get a working product.