> Also just HIPAA being in the mix adds non trivial complexities
Yep, and WUSTL - like most Universities - is a major medical network in it's region. Ime, the bulk of the costs that arose from Higher Ed contracts I dealt with were due to the fact that most Higher Ed institutions were also medical networks.
But the issue is, medical PHI is important, and outages can lead to liability and potentially patient risk.
> At the time the industry wisdom was that basically 80% of CRM projects fail to return value. And the customers knew that plainly, but the alternative was trying to keep some COBOL era system limping along. So even though they knew they were likely going to burn a huge pile of money, it felt like a necessity
Pretty much, because the TCO for a Cobol system limping along would eventually become unsustainable - especially if you had dozens of BUs with their own internal data practices.
What the hell PHI / EHR work is Workday doing?
The answer should be "none".
Yeah, I had an unexpected insight into all this as growing up, my best friend's dad was a COBOL programmer for Metlife insurance.
The upside of those old mainframe centric systems is they do have impressive reliability. But you increasingly become dependent on just a handful of old souls like my friend's dad that are the only people who understand it in sufficient detail to try to update it.
My friend's dad had good job security but it seemed pretty demoralizing otherwise.