Thats an infrastructure? That sounds more to me like some horrible spasm than an infrastructure.
After my stint at the bank, I worked in health care - 3 stints to be exact. Here's what I learned:
1) While the bank was excruciatingly bureaucratic, our systems were pretty good. We had a homogenous Windows environment, I was part of a team that maintained a single app (a big one). We did it right; we had a single environment and kept things homogenous.
2) If we had to talk to another system, we spent a LOT of time building a system that could interface with both our systems. For example, we had data sitting in an old COBOL mainframe, so we batched it into text files, created a parser and parsed the data. We formed a team of SME's whose job is to know and train others in that.
3) While we had too many check points, we made sure that we can trace bad code to the programmer. Trust me, we had 80+ developers working on a 1GB source code, we apportioned defects/features/projects so that we could trace who was doing what and blame them if it fails.
We had NONE of this in health care. I remember after the bank, went to go for a health care company. Their architecture was so bad that we spent close to a year just rebuilding the environment - that's on top of code changes and releases, too.