Dead-on right. It's not the back-end, it's not what brand of software, it's not the brand of tablet... it's the interface.
I'll say it again... most physicians are NOT geeks, with the occasional exception (confession: I actually have a server rack in my house). People may not realize this, but plenty of physicians can't even type, particularly the older ones.
I have a colleague... I'll call him Dr. Smith. He's a GP, and he's literally been practicing for nearly 50 years. That's not a typo... he started in 1960. He's old-school, and anybody (including me) would be happy to have him take care of them... because he takes all his own calls... comes into the ER to see his patients, even in the middle of the night and on weekends. He's also a hell of a nice guy, and a good doc... a real dying breed.
He's computer-illiterate. Completely. You threaten him with "learn this crappy new system or else," and he's going to balk. He'll retire, or drop his privileges and move to the hospital across town like a bunch of his younger colleagues given the same ultimatum.
You think you can force physicians to simply eat sh*t? Who do you think you are... Medicare? You MUST have physician buy-in, and physicians balk at being told "use this crap or else" by some suit who doesn't take care of patients, ESPECIALLY when the UI slows them down, cuts into their productivity, and interferes with their care of patients. I've worked in environments where that was done as a top-down forced implementation (I'm an ex-military doc), and it sucks out loud (it was also reverted to paper in less than 24 hours after the entire facility literally ground to a halt).
How do you like it when some admin weenie comes down to your server room and says "we're implementing this brand-new system. It sucks, it's slow, it crashes, it's full of security holes... but you're going to use it or else." Somehow, I think a similar industry-wide fiat like that directed against IT, posted on Slashdot, would easily generate a 1000-comment thread... in the first 15 mintues.