November 5, 2026

Dragon Broke in Citrix? A 30-Day Pilot Plan for IT Leaders

A physician holding a handheld dictation microphone beside a monitor showing a remote desktop session with a blinking cursor

A dictation upgrade goes in on a Tuesday. By Friday, the radiation oncology team is typing notes by hand again. Dragon works on the doctors who run it on a local PC. It does not work well for the doctors who reach the chart through a Citrix session. A temporary workaround keeps things limping along, but it expires when the old Dragon version is retired at the end of the year.

That is the situation we heard from an oncology group we spoke with, and it is more common than vendors admit. This post is for the IT director or CIO who owns the problem. It explains why dictation breaks inside a remote session, what a deadline like this really forces you to decide, and how to run a 30-day pilot on just the affected group, without ripping out anything else.

Why Dragon breaks inside Citrix

Dictation looks simple from the doctor's chair. You talk, words appear. Behind that, three separate things have to work at once, and a remote session puts a wall between each of them.

  • The microphone. Audio has to travel from the doctor's desk to wherever the speech engine runs. Remote sessions pass audio through a redirected channel, and that channel can add delay or drop out.
  • The software on each side. Many Dragon setups need helper components on the local device and inside the hosted session. When an upgrade changes one side and not the other, versions stop matching and things quietly fail.
  • The text box. Words must land in the field where the cursor is. Clinical apps like Varian ARIA run inside the session, and the dictation tool sits outside it. If the tool cannot see which field is active, text goes nowhere, goes to the wrong place, or only works when you click in a specific way.

The first two are IT problems. The third is the one physicians feel. They say things like "it stopped typing in the note" or "I have to click twice before it listens." If you hear that, you are probably looking at the text box problem.

We cannot tell you which of these is the cause in your environment. Only logs and a test on one affected machine can. But the pattern fits: local installs fine, hosted sessions broken, trouble starting right after an upgrade.

What the year-end deadline really means

A workaround that expires on a known date is not a plan. It is a countdown. If your current Dragon version is retired in December, you have three honest paths:

  • Fix the Dragon-in-Citrix setup. Work with your Microsoft or Nuance contacts and reseller to get the new version and the Citrix components lined up. This keeps one vendor, but you depend on their timeline.
  • Move the affected users to another tool. Keep Dragon where it works. Replace it only for the hosted-session group.
  • Move everyone. Rarely the right first step, and not something to decide under a deadline.

The second path is the low-risk one, and it fits when you have a contract in place. You are not breaking the agreement. You are testing a tool on the small group that is already blocked. If it works, you have a fallback before January. If it does not, you lost a month and nothing else.

How DictaFlow Medical approaches the problem

DictaFlow Medical is hold-to-talk dictation. The doctor holds a key, talks, and lets go. The text is typed into whatever field has the cursor, the way a keyboard would type it. It does not rely on pasting from the clipboard, which many Citrix policies block. That is why we describe it as built for Citrix and other virtual desktop setups. There is no EHR integration project, because the EHR never needs to know it is there.

A few other facts an IT lead will ask about:

  • It is tuned for medical vocabulary. You can add custom terms, and it learns from corrections over time.
  • Cloud mode gives the best accuracy and cleans up the text. Local Offline mode runs on the device with no internet.
  • It is HIPAA compliant, and a BAA is standard. The Medical product runs on its own BAA-covered backend, and customer data is not used to train models.
  • Live mode shows words as you speak. Toggle mode is there for people who do not like holding a key.
  • It runs on Windows, Mac, iPhone and Android.

We are not claiming nobody else can type into a hosted session. We are saying this is the problem the product was built around, so it is a fair thing to test first.

A 30-day pilot plan for the affected group

Keep the pilot small. Ten providers is plenty. Here is a checklist you can hand to your team.

Week 0: set it up

  • Pick the group that is broken today, such as radiation oncology on the hosted EHR. Leave everyone else alone.
  • Name one physician champion and one IT owner.
  • Write down the three or four screens where they dictate most. Note which fields are free text.
  • Check that your security team is comfortable with the BAA and the data flow. Ask us for the details you need.
  • Install from the downloads page on one test PC first, then the pilot group. Start on the free plan, which includes 2,000 words a month with no card, so the first tests cost nothing.

Week 1: prove the basics

  • Dictate into the real EHR inside the real Citrix session, not a demo box.
  • Test the cursor behavior: click into a field, dictate, move to another field, dictate again.
  • Test a long note, not just a sentence. Watch for dropped words.
  • Add the 50 terms each physician says most (drug names, regimens, local abbreviations).

Weeks 2 and 3: real clinic days

  • Doctors use it for live work, with Dragon still available as a fallback.
  • Ask each one a single question at the end of each day: how many notes did you finish by voice, and where did it fail?
  • Log every failure with the app, the field, and what happened. Send the list to us. We would rather fix the real problem than guess.
  • Try both Cloud and Local Offline mode if your network policy matters.

Week 4: decide

  • Count: notes finished by voice, minutes spent fixing text, number of failures.
  • Ask the physicians whether they would go back.
  • Choose: expand, extend the pilot, or stop. Because it is month-to-month, stopping costs you nothing further.

The microphone question

Many physicians use a handheld microphone with mute and record buttons, such as a Philips SpeechMike. Any standard microphone works for audio in DictaFlow. We have not tested SpeechMike button mapping, so we will not tell you the record button will start dictation. Make it part of the pilot: bring the mics you already own, see what the buttons do, and we will help you confirm the setup. DictaFlow also supports a middle mouse trigger and supported USB foot pedals, which can be simpler to roll out.

Dragon with Citrix fixes, Philips SpeechLive, or DictaFlow Medical?

Here is a fair read of the three options for this specific problem.

Stay on Dragon and fix the Citrix setup. Best if you want one vendor, have the contract, and your support team can get the versions and Citrix components working before December. The risk is timing and support quality. You are already seeing both.

Philips SpeechLive. It is a cloud dictation service from the makers of the SpeechMike, and it is worth a look if your doctors already use Philips hardware and you want a workflow built around those mics. Check two things in your own test: whether the text reaches the field inside your hosted EHR, and how much of the work goes through a separate review screen.

DictaFlow Medical. Our pick for the affected group. It is built to type straight into hosted sessions, it is quick to install, the pilot is free to start, and a failed pilot leaves no lock-in. The tradeoff is that we are a smaller vendor. We do not match a large enterprise platform on deployment tooling, and we will say so.

If you would rather not decide in advance, run Dragon and DictaFlow side by side in week 2. Doctors will tell you which one they reach for.

What it costs

DictaFlow Medical is $39 per user per month for 1 to 4 seats and $29 per user per month for 5 or more seats. It is month-to-month, and you can cancel anytime. Teams with 5 or more seats get a usage dashboard, which helps you see who is actually using it. Ten pilot providers is $290 a month at the 5+ rate.

Frequently asked questions

Will this work with Varian ARIA and other hosted EHRs?

DictaFlow types into whatever field has the cursor, so it does not need an integration with the EHR. We recommend testing in your real session during the pilot, because every Citrix build is a little different.

Is it HIPAA compliant?

Yes. A BAA is standard. DictaFlow Medical runs on its own BAA-covered backend, and customer data is not used to train models.

Can it run without internet?

Yes. Local Offline mode runs on the device. Cloud mode gives the best accuracy and cleanup but needs a connection.

Does it work with our physicians' microphones?

Any standard microphone works for audio. Button setups on handheld mics should be confirmed during the pilot.

Do we have to leave Dragon?

No. You can keep Dragon for the users it already works for and pilot DictaFlow only for the group that is blocked.

How do we start?

Download from the downloads page and use the free 2,000 words a month, or read about DictaFlow Medical first.

The short version

Dragon not working in your hosted EHR, and a workaround that ends in December, is a problem you can solve with a small, contained test. Pick the blocked group, run 30 days, count the results, and decide with data. You can start today with DictaFlow Medical.