Epic EHR Virtual Assistant Guide: Hyperspace, In Basket, and SmartTools

Epic is the most powerful EHR in the U.S. market and also the most opinionated. A virtual medical assistant who knows Epic thoroughly can save a practice five to ten hours of in-office staff time per week. A virtual medical assistant who has only used other EHRs will spend their first two weeks asking confused questions. The difference is mostly in five Epic-specific concepts.

Hyperspace access and Citrix delivery

Most Epic deployments are delivered through Citrix, which means a virtual medical assistant needs both an Epic user account and a Citrix entitlement. The single most common Epic onboarding mistake is provisioning Epic but forgetting Citrix, which leaves the virtual medical assistant unable to actually log in. Confirm both before day one.

In Basket pools and message routing

Epic's In Basket is the single most important workflow surface for any virtual medical assistant. The right setup is a shared In Basket pool that the virtual medical assistant and the in-office team both access, with clear routing rules for patient messages, refill requests, results, and staff messages. Without pool access, the virtual medical assistant is locked out of half their job.

SmartTools: SmartPhrases, SmartTexts, and SmartLinks

Epic's productivity gains come from SmartTools. SmartPhrases (.dot phrases) expand to pre-written text. SmartLinks pull live data from the chart. SmartTexts wrap whole note templates. A virtual medical assistant should be able to read, use, and edit existing SmartPhrases on day one, and should be building practice-specific SmartPhrases by week two. This is the single biggest productivity lever inside Epic.

Patient Cases versus Telephone Encounters

Epic distinguishes between Telephone Encounters (a charge-eligible documented patient interaction) and informal staff messages. A trained virtual medical assistant uses Telephone Encounters for any clinically significant phone interaction and routes informal messages through the In Basket. Mixing these up is the second-most-common Epic onboarding mistake.

Workqueues for charge capture and denials

On the revenue cycle side, Epic uses Workqueues for charge review, denial follow-up, and AR aging. A virtual medical assistant working in revenue cycle needs Workqueue access scoped to their role: charge review for charge entry, denials for AR follow-up, account-level for patient billing questions. Each Workqueue has a different security configuration that the practice's Epic analyst needs to set up before day one.

Common Epic onboarding mistakes

The five recurring mistakes: provisioning Epic without Citrix, forgetting to add the virtual medical assistant to the In Basket pool, granting blanket security access instead of role-scoped access, skipping SmartPhrase training in week one, and conflating Telephone Encounters with informal messages. Address all five during onboarding and the virtual medical assistant is productive on day three instead of day fifteen.