More than that, you need to figure out how administrators view your offering, i.e. How much money does it make them. Some things doctors like cause the hospital to lose money -- like actually spending time getting to know patients and understand their condition, or keeping them out of the hospital. Doctors aren't always the people running things

Ive also noticed that even though the industry has done things X way for a long time, sometimes those are done because "well We've always done it that way". It's cargo culting, and nobody has a good reason why its done.

Being an outside can sometimes mean that you call attention to that, and show better ways. And with the internet and publications, can be an effective way to do that.

Most of the times however, there are reasons and you should at least understand why. But for those cases where "why" isn't defined, poke at them.... You're likely to find something interesting.

Agreed. It is very easy to try to disrutpt a process without understanding the reasons behind the current process. A lot more difficult to understand the current process then propose changes that address that processes shortfall.

There is always a reason why things are done a particular way "It's always been done that way" is shorthand for "I don't know why it's done that way". Like history, you need to understand the reasons behind a process before you can effectively change it, otherwise you are doomed to make the same mistakes and very soon your shiny new process will start to look as cobbled together as the previous one.

You mean... make software for the people who use it, not the people who make it?

Following doctors will only provide you with better tools for doctors. You need to shadow the admin side and understand the painpoints they experience because ultimately they pay bill.

The way the system works in whatever country you live in has shortcomings. Finding ways to fix those issues higher up the chain will provide the most value.