Earlier quoted context omitted.
Standardize what? With a complex medical condition like that every patient is different so it's tough to apply evidence-based medicine practices. The technology for sharing patient records is gradually being standardized. But that won't help if the doctors don't actually take time for a detailed review of the patient's records.
Personally, from my observations as a software engineer married to a doctor and friendly with lots of doctors, and as an occasional participant in the American healthcare system, the general inadequacy of electronic medical systems is one of the most maddening aspects of our system. Epic is a monstrosity and none of the other systems are much better. The tech is outdated, the interfaces are awful, they're incredibly…
The regulations (often vague and open to interpretation by the customer) often play a part in creating the monstrosities that power our healthcare systems. Because of the subject to interpretation aspect customers often say, "No. This is how it has to work because our processes say this is what we do to meet the regulation." Inevitably it's implemented to be configurable because that's what's required.
Another culprit is the institutions and lack of standards surrounding process. There's a reason EPIC software is customized for every institution it is installed in. It's because every institution wants to do things differently. Even in the space which I work, it's the same. Every institution wants "some specific change" that they can't live without and won't go live until it's available. I'm saying this is neither a good nor a bad thing. It's just a reality.
And the ever present legacy, take EPIC as the example, it was founded in 1979. I'm not saying that their code is all from 1979 but there's definitely a fingerprint of what was in their modern day applications. There are layers upon layers of data from mergers and acquisitions translated into various codes and mapped to various databases for any number of uses. Any day of the week your state code may be two letters, three letters, full name, a custom internal legacy code, you name it you'll see it.
Spend a year working for a company with a regulated legacy healthcare product and significant user base. You'll have to become proficient at security, regulations, data standards (HL7, FHIR, etc), legacy data migration, and any other number of skills. If you're lucky enough to have all of those in place then you're still going to spend time coming up to speed within the specific healthcare domain you're working in and where it touches other healthcare (and non-healthcare eg financials) domains. Oh, and often you won't be allowed access to production instances to troubleshoot issues and a copy of the production instance isn't available because HIPPA and the customer is uncomfortable giving access to engineers. You get really good recreating problems purely via error logs and staring at the code where the issue "might" have occurred.