Every optometry practice's workflow is shaped, more than owners like to admit, by the software it runs on. So when you're evaluating remote support — a scribe for documentation, a VA for scheduling and billing — one question matters more than any line on a résumé: does this person know your system, or will they be learning it on your clock?
Here's how remote support maps onto the platforms most optometry practices actually use, and what to ask depending on which one is yours.
Why platform fluency is the whole ballgame
A remote scribe or assistant works entirely inside your software. There's no walking over to show them where something lives. A scribe fluent in your EHR documents a slit-lamp exam at conversation speed; one who's hunting for the right field turns your exam into a dictation session. A VA who knows your PM system's scheduling logic books correctly on day three; one who doesn't generates the kind of template errors that take weeks to surface and longer to untangle.
The difference between those two hires looks identical on paper. It only shows up in the demo — which is why we recommend making candidates perform real tasks in your system (or its trial sandbox) before you commit. Any provider confident in their training will welcome it.
Cloud platforms: the natural fit
Cloud-based systems — RevolutionEHR being the prominent optometry example, along with other browser-based PM/EHR platforms — are the easy case for remote staffing. A remote team member logs in through their own credentialed account exactly as an in-office employee would, with access scoped to their role, multi-factor authentication enabled, and every action attributable in the audit log. There's nothing to install and no network gymnastics; the platform was built for distributed access.
If you're on a cloud system, your setup conversation with a staffing provider should be short: role-scoped account, MFA, and confirmation that the provider's workstation controls (no local downloads, monitored sessions) are in place.
Server-based platforms: solvable, with one extra step
Practices running locally hosted systems — Crystal PM installations, older Eyefinity/OfficeMate configurations, and other on-premise setups — add one technical layer: the remote worker reaches your server through a secured connection, typically a VPN paired with a remote desktop session, or a hosted virtual desktop your IT vendor maintains. Done properly, this is routine; thousands of practices run it daily. The keys are that the connection is encrypted, credentials are individual rather than shared, session access is logged, and nothing patient-related is stored on the remote machine.
Your staffing provider should be able to describe this handshake fluently and coordinate directly with your IT support to stand it up. A provider who waves vaguely at "we'll figure out access" hasn't done it often enough.
Platform-specific hiring questions
- RevolutionEHR practices: Has the candidate documented exams in Rev specifically? Can they navigate its exam module and order flow without guidance?
- Crystal PM practices: Ask about experience with your specific configuration — Crystal installations vary widely — and confirm the remote-access plan with your IT vendor before the start date.
- Eyefinity/OfficeMate practices: Clarify which product and version you run, since workflows differ meaningfully across them, and ask the candidate the same.
- Everyone: Request a supervised trial task in your system during the interview. Ten minutes of watching someone navigate tells you more than any certification list.
One quiet benefit of the exercise
Practices that go through this process — documenting access paths, scoping credentials, writing down their own workflows for a remote hire — routinely discover their internal documentation was thinner than they thought and their user-account hygiene worse. Tightening both is worth doing even before anyone remote logs in. The remote hire just supplies the deadline.
If you want to talk through what remote support looks like on your specific platform and configuration, that's a conversation we have weekly — bring your IT person and we'll keep it concrete.
.png)
.png)
.png)
