Dictating Into Epic Over Citrix: Why Your Words Vanish
The clipboard wall, the keystroke workaround, and a ten-minute test you can run for free.
November 06, 2026
This week a physician emailed me a question I get in some form every week. They use Epic. They were thinking about the paid plan. And then, in the middle of an otherwise normal message: could they paste notes into DictaFlow and send them straight into Epic, bypassing Citrix?
They added an apology. "Sorry if this doesn't make sense."
It makes complete sense. Of course it does. It might be the most sensible question in clinical software. You have a thing you want to say, you have a box where it has to go, and between the two sits a remote desktop that seems to exist to make your life harder. Of course you'd want to bypass it.
I'm Ryan, I build DictaFlow, and I'm not a clinician or an Epic analyst. What I can tell you is what I've learned about why text goes missing between a dictation tool and a field inside Citrix. It's a surprisingly short list.
The invisible wall
Most dictation tools do the following. They hear you, turn your speech into text, put the text on the clipboard, and press paste.
On your own computer, that works so smoothly you never notice the clipboard exists. In a Citrix session it can fall apart. Many organizations configure Citrix to block clipboard redirection, because the clipboard is a way for data to leave a secure environment. That's a reasonable security decision. It also means your pasted text goes nowhere.
The cruel part is how quietly it fails. You talk. The tool says it heard you. The field stays empty. Nothing tells you why, so you assume the dictation tool is broken. Frequently it isn't. The insertion is what got blocked, which is a separate thing from the transcription.
Citrix documents clipboard redirection and how administrators control it. If you're curious, ask your IT team whether it's enabled for your published app. It's a reasonable thing to ask, and they'll know right away.
Typing instead of pasting
The alternative is to stop using the clipboard. DictaFlow has a Typing Mode that sends finished text as keystrokes, character by character, the way a keyboard would. To the remote session it looks like someone typing.
That sounds like a hack. It is one. But it's the same hack a lot of accessibility software has leaned on for years, and it sidesteps the clipboard rule entirely.
I want to be careful here, because this is the sort of claim that gets vendors in trouble. Typing Mode can help in setups where pasting is blocked. It does not work in every environment. Your connection, your local security policy and the remote session's own input rules all matter, and I can't see inside your hospital's configuration. If I told you it works in Epic over Citrix no matter what, I'd be guessing.
So test it. Here's how.
What a dictation tool cannot do in Epic
Another thing I should clear up, because it comes up in nearly every Epic conversation.
DictaFlow types text. It doesn't drive Epic. It can't open a patient's chart, place an order, pick a diagnosis from a list or sign a note. If someone tells you a plain dictation tool can do those things, be skeptical, and that includes me.
A useful way to think about it: writing an assessment paragraph is a dictation task. Choosing a medication from a catalog is an EHR action. Those are different jobs, and mixing them up is how people end up disappointed in the first week.
Dragon Medical One has a deeper set of commands and a long history of integration at larger organizations. If your health system runs it and your IT team supports it, that is a real advantage, and it's the right answer for some places. DictaFlow is better matched to a clinician or a small group that mostly needs text to land in the field that's open.
The test I'd run before paying for anything
This is the part I'd tape to a monitor. It takes about ten minutes and it applies to any dictation tool, mine included, which is the reason I trust it more than any benchmark I could publish about my own product.
- Open a training environment or a test patient in Epic. If you don't have one, use an empty field that isn't attached to a real chart.
- Put the cursor in a free-text note field.
- Dictate two sentences of made-up text. Something like "Follow up in two weeks. Return sooner if symptoms worsen."
- Look at what arrived, and where.
- Try a second field type, such as a smart text area or a message box. They don't always behave the same.
- Check what happens if you click away mid-dictation.
You are testing insertion, separate from recognition. If the words show up in the right box, you've learned the hard part works. If they don't, stop. Don't put real patient information in until you know why.
That last point matters. When this goes wrong, the complaint is rarely "the app misheard me." It's usually "the app typed into the wrong place" or "the app typed into nothing." Those are different problems with different fixes, and it's worth knowing which one you have.
A bug report I think about
Back in September, an IT consultant tested DictaFlow in a remote desktop session and found something odd. When they used a middle mouse button to trigger dictation inside the RDP session, a stray 0 appeared at the front of the line. They asked why.
That's a good example of how this stuff really goes wrong. Nothing was wrong with the transcription. An extra character showed up somewhere between the local machine and the remote one, and I won't pretend I can explain every path an input event takes across that gap. The consultant ended up finding a different product that worked for them, and that's okay. Not every setup is going to fit, and I'd rather someone move on than keep fighting.
But it taught me to take remote sessions seriously as their own platform. A tool that behaves on a laptop can behave quite differently across a protocol boundary, and "it works on my machine" is the most dangerous sentence in this business.
Templates, since they asked
The same physician asked whether making templates for SOAP notes is intuitive. I don't want to oversell it, so here's the plain version.
You can set up spoken phrases that expand into longer blocks of text, and you can add medical terms to a personal dictionary so names and drugs come out right. That covers a lot of what people mean by templates. It isn't the same as Epic's own SmartPhrases and SmartLists, which live inside Epic and which you'll still want to use for structured parts of the note.
My honest advice is to keep Epic doing what Epic does. Let it handle the structured fields, the orders and the dot phrases. Use dictation for the narrative parts that you'd otherwise type.
The privacy side
Because this is a medical product, one more paragraph.
Don't use the free consumer version of any dictation app with patient information. DictaFlow Medical is a separate app with a separate backend, and your organization should complete its own vendor review and, where required, a business associate agreement before it processes anything identifiable. Keep your first tests on fake text. It costs you nothing and removes a whole category of risk.
Where I land
If you work in Epic through Citrix and you're tired of retyping, there are really only three questions. Does your remote setup allow keystroke input? Does the text land in the field you picked? Do you like reading and fixing it afterward?
You can answer all three for free in an afternoon. DictaFlow Medical has a free tier at 2,000 words a month, and the paid plan is $39 a month per user for one to four seats, $29 for five or more. It runs on Windows, Mac, iPhone, iPad and Android. Citrix sessions are usually reached from a Windows or Mac desktop, so that is where I'd run the test.
If you want to run that ten-minute test, the download is here: dictaflow.io/medical. If it fails in your environment, send me what you saw. A failed test in a real Citrix setup is worth more to me than a hundred compliments.
Try DictaFlow Medical free
2,000 free words a month. Test it on fake text in your own EHR before you decide.
See DictaFlow Medical