I think this is a great topic that persists a feeling in IT in general. Probably someday there will be a degree or course in Engineering Psychology or the Psychology of Design as it pertains to building consensus with COMPLETELY disparate groups. 1) A good salary is a great thing, but that $ doesn't reduce frustration. If your any good at your job you're passionate, then salary is a ends to a means, ie we normally want to build something and look back on that and say, "I did that". 2) Although he is an MD, and therefore Omnipotent, he has had to have a peer review from time-to-time. See if you can find an instance where he was doing something one way and had to reconsider. Especially in medicine where there aren't "do-overs". This will help bring to him the idea that even though this is software and your time is infinite :-) it would be best to have a "plan" going into it like a treatment plan or surgery plan. 3) Detachment from outcome is a wonderful thing but hard to obtain. If you would rather do then redo, it might be time to move on. If you can look at this is a challenge that you're obviously taken on, consciously or subconsciously, then it would behoove you to stay the course. Build the system the way you think it should work and then show it to him. But remember if you make someone feel like a dipshit, even if they deserve it, then you'll probably fail and loose the game. Even then you can say you played a good game but we all would rather win then say we played hard. Happy Hunting :)
We all sit around and suppose while the secret sits in the center and knows - Robert Frost