After years of supporting eClinicalWorks practices across Dallas-Fort Worth and Houston, the calls follow a pattern. The same ten problems come up again and again, and almost every one starts with the same question: is this an eCW problem or is it our problem? Getting that answer wrong costs practices hours on hold with the wrong party. This guide covers the ten most common eCW problems we see, what each one usually means, what your staff can check in two minutes, and when to pick up the phone.
1. eCW is running slow
Slow is the most common complaint and the least specific. For hosted practices, the usual suspects are the internet connection and the workstation, in that order. For on-premise practices, add the server and the database to the list. A quick test: if every application is slow, it is your network or workstation. If only eCW is slow, and it is slow on every workstation, the problem is upstream, either your connection to the hosting environment or the server itself. Morning slowness that clears by mid-day often points to backup jobs or updates running into business hours, which is a configuration problem, not a fact of life.
2. Printing stopped working
The classic pattern: a Windows update ships overnight and the front desk cannot print encounter forms in the morning. Printing in eCW rides on Windows print drivers, and those break routinely. Your staff can check whether the printer works outside eCW (print a test page). If it does, the problem is in the middle layer, and that layer belongs to whoever manages your IT, not to eClinicalWorks.
3. Scanning and document attachment failures
Scanner problems look like eCW problems but almost never are. TWAIN drivers, USB connections, and scanning utilities sit entirely on the local side. If documents scan but do not attach, that can be an eCW-side issue worth a vendor ticket.
4. Login problems and locked accounts
Locked accounts, expired passwords, and sessions that will not release are split territory. Account administration inside eCW belongs to your practice administrator or the vendor. But if logins fail from one workstation and work from another, the workstation is the problem, and that is local IT.
5. eBO reports timing out
Enterprise Business Optimizer reports put real load on the database. Reports that run fine on the 1st and time out at month-end are usually resource contention: too much reporting on too little server, or a database that has not had maintenance. Hosted practices should push the vendor; on-premise practices need their IT partner to look at the SQL side.
6. Lab and imaging interface failures
Interfaces fail quietly. Results stop arriving, and nobody notices until a clinician asks where a lab went. The interface has two ends: eCW's side and the lab or imaging center's side, with your network in the middle. The two-minute check: did results stop from one source or all sources? One source points to that source's feed. All sources points to your side or eCW's interface engine.
7. Fax problems
Practices still live and die by fax. Whether you run eCW's fax integration, a cloud fax service, or an analog line, failures land on the local side far more often than the application side. A fax queue that backs up silently can sit for days; someone should be watching it, and that someone is your IT partner.
8. EPCS token and PDMP problems
When a prescriber's two-factor token stops working on a Friday afternoon, controlled-substance prescribing stops with it. Token enrollment, identity proofing, and Texas PDMP connectivity each involve different parties, and the fix is usually procedural rather than technical. This is a place where an IT partner who has done it before saves hours.
9. Freezes during charting
A workstation that freezes mid-note is usually a workstation problem: memory, an aging machine, or something else fighting for resources. If every workstation freezes at the same moment, look at the network or the server. The distinction matters because the fixes have nothing in common.
10. Problems after an upgrade
Every eCW upgrade carries some risk to local integrations: printing templates, scanning profiles, interfaces, and third-party tools. The practices that sail through upgrades are the ones whose IT partner tested beforehand and was on hand the morning after. The ones that struggle are the ones who found out about the upgrade when the problems started.
Who owns what: eCW vs your IT partner
The dividing line is consistent. eClinicalWorks owns the application: bugs, templates, clinical content, their hosted data center, and upgrades to the software itself. Your IT partner owns everything the application touches: workstations, printers, scanners, the network, servers or the connection to hosting, interfaces on your side, backup, and security. The expensive failure mode is having nobody on the IT side who knows eCW, because then every local problem gets misrouted to vendor support, and vendor support correctly sends it back.
When to stop troubleshooting and call
Two minutes of checking is worth doing. Two hours of staff time on an IT problem is not. If the quick checks above do not resolve it, the practice should have one number to call where the person answering knows eCW, knows your environment, and owns the problem to resolution, whichever side it lands on. That is what we do for eCW practices across DFW and Houston, with an initial response within 15 minutes.
Frequently asked questions
eClinicalWorks support handles the application itself. For problems in the environment around it, workstations, printing, network, interfaces on your side, you need your own IT partner. Galleon supports eCW practices across DFW and Houston at (972) 776-6366.
Morning slowness usually points to overnight jobs running long, workstations overdue for a restart, or bandwidth contention as the whole office logs in. It is diagnosable and fixable; it is not something to live with.
Almost always your IT company. Printing rides on Windows drivers and local print infrastructure, which sit outside the application.
A two-minute check (is it one workstation or all, one function or everything) makes every ticket faster, whoever it goes to. Beyond that, hand it off.
No. The vendor supports their software. We support everything it runs on, and we manage the vendor ticket when the problem is on their side.