I'll play sort of a devil's advocate here as someone who's worked in this field: the feature-gaps identified aren't all that bad.
- 1k-assessment limit: It's not ridiculous; assessment-notes are usually 0-2 acronym-laden sentences, probably under 200 characters in general. Writing a 1k-long assessment note seems extremely unusual and I think in many situations would be completely loathed by co-practitioners, who need to very quickly read visit notes (the assessment is just one field out of dozens or hundreds). An inexperienced doctor could easily be reprimanded for such verbosity. However, there are many different working and documentation styles which work better for certain patient populations, specialties, institutional needs, etc. -- this doc may absolutely be justified in wanting to be thorough in this situation. A call from an experienced doc should be investigated and most probably addressed in future versions of the software.
- Reviewing past visits: The EMR probably does have some kind of history report/index view into the list of past visits, but the problem here seems to be that the index doesn't have the right data in it. The doc wants to review in detail the "thickest" or most important notes, so you need to display that into the index. It's a good feature idea, but not an obvious one.
- Dictation: It's disruptive and awkward to dictate in front of patients. So typing/writing while talking to the patient is generally more efficient, even if the doc has to wrap up after the patient has left. For work that is entirely done when patients are not present, dictation is a fine solution and in fact is used by many, many docs, integrated into EMRs, etc.
One issue, not explicit in the article but possibly relevant, is that managers often use constraints in enterprise software in order to control end-users. Field-lengths sometimes come out of these ("They're wasting time! They should move onto the next [patient/customer/widget/etc.]!"). But the problem there is poor communication & lack of agreement between management and workers, rather than an outright deficiency in the IT itself.
Doctors hate change, they want to keep things as they are. For most non complicated consults, people are much better of with a smart system rather than going to talk to a bored dr, but drs do not want to give up their control.
Assume the doctor has a working system that enables them to do their job, without being distracted by having to learn new, irrelevant procedures. Any new "better" system has to provide really tangible benefits to be worthwhile learning. If that new system has been designed by administrators, for the benefit of administrators, then it's little wonder that the doctors are resistant to change.
If one isn't able to do that, I would seriously question their ability to properly diagnose complex ailments.
From the perspective of a non-geek who works in a medium-to-large company, bad “enterprise” software is just an irritation that goes with the job, like bad coffee. You may complain about it but you don’t seriously expect it to be fixed.
For instance, talking to prospective users. The importance of this has been stressed over and over again and is no longer disputed. In fact, when an in-house team started designing changes to an accounting app my friend had to use, there was an official user expert designated to work with the developers. The user "expert" was her manager, who had never used the application that was being changed, had never used a similar application, and had never even done a job similar to the one done by the users. What's more, she forbade the developers to speak to the users because she didn't want the development effort to affect their productivity. Oh, it did affect their productivity eventually, believe me it did.
(It's an exaggeration to say it's uniformly terrible; I had a good experience with the one enterprise app I built, but it was for a network operations team, so they understood a lot about software and about the need to be generous with time and access.)
A guy in the oil business once told me a story about why Bangladesh's gas fields have not been thoroughly exploited yet. Basically it was a big tangle of political crap -- and according to him, Bangladeshis are very happy not to have the gas fields exploited, because they assume that both the current leadership and the opposition party are so corrupt that all the money would be stolen anyway, so it's better if the gas is not exploited until the far future when some of the money might go to the people. I have no idea if that's true or not, but it captures why I'm mostly glad that the use of technology in medicine is stuck in the dark ages. Until there is some stakeholder involved who gives a crap about patient rights and privacy (the doctors care about effective treatment, but not rights or privacy) it's best if nothing changes at all.
If one was reasoning about a computer in the way you have to reason about a biological system, there wouldn't be any reason to think that since you can create with a browser unlimited character field it, you can create a medical transcription system with an unlimited character field.