Every hospital has them — the consultants who survived three failed EMR rollouts and have no patience for a fourth. Here's how to bring them along without forcing them.
Why senior doctors resist
It's almost never about technology. It's about three things they've learned the hard way. One — every previous EMR slowed them down, and patients waited. Two — the EMR captured data that was later used against them in clinical audit without context. Three — IT made decisions about clinical workflow without asking. A senior consultant who has been burnt by all three is not irrational for resisting. They've earned the right to be careful.
The three concessions that matter
- Faster than paper — not 'will be faster after you learn it', but faster on day one for at least one common task (typically a follow-up prescription).
- No use of EMR data in audit without prior discussion — and definitely not in performance review.
- A doctor-side representative in every workflow decision — not a final-veto, but a documented voice that has to be addressed.
Voice as the bridge
The single most effective change-management lever we've used is starting senior consultants on voice prescription. The first time a 30-year veteran dictates a prescription, sees it appear on the screen in 4 seconds, and watches the assistant print it for the patient — the rest of the rollout becomes possible. Voice removes the typing tax that they had associated with EMR. Once they trust one thing, they trust the next thing.
One-button workflows for common cases
For the consultations a senior doctor does fifty times a week — the 5-minute follow-up, the routine BP check, the annual asthma review — give them a one-button workflow. One click pre-fills the chief complaint, the assessment, the prescription template, the next visit date. They review, edit if needed, sign. That's it. The system should adapt to their pattern, not the other way around. A workflow that took 90 seconds on paper now takes 25 seconds on the EMR. The case for the EMR is made in the doing.
A champion in every department
Find the one consultant in each department who is curious about the system. Make them the unofficial owner of feedback for their department. They become a bridge between their resistant colleagues and the implementation team. When a sceptical colleague raises a complaint, the champion either says 'I've used it, it does work this way and here's why' or 'I've used it, that's a real bug, I'll get it fixed'. Authority transfers from the IT team to the clinical team. The rollout becomes their rollout.
Six-week ramp
- Week 1-2 — Champions only. They use it daily, give feedback, decide what's a deal-breaker and what's tolerable.
- Week 3 — Champions train the next 30%. The next 30% are usually the curious-but-cautious — they'll come along if the champions vouch.
- Week 4 — Voluntary adoption period. The remaining 70% are invited but not forced. They watch. They ask questions. Some join.
- Week 5 — Mandatory for new admissions, OPD still optional.
- Week 6 — Mandatory across the board, with daily walk-rounds by the implementation team for the first two weeks.
What we've learned
Forced rollouts produce compliance, not adoption. The doctor logs in, ticks the boxes, and the data quality is poor because their heart isn't in it. A six-week voluntary-then-mandatory ramp produces both — by the time it's mandatory, most of the resistant doctors have come along because the early adopters made the case for them. Patience pays off; speed almost never does on this one.