Before you call someone ignorant and say that the bureaucracy disagrees and so what possible standing could I have, consider a little bit of charitable reasoning would add some much needed credibility to the objection.
That you've done consulting to the healthcare sector doesn't mean much of anything to me, one way or another. Heck, the IT consultant for our CTO in my health chain can say the same, and all he does is EMR rollouts. He has about 0% understanding of healthcare policy, or how the system actually works. He understands EMR implementations. The financial analyst consulting to our COO has been in the hc sector for about a year and his knowledge of actual hc policy outstrips the EMR guy by at least an order of magnitude.
As a physician and healthcare policy expert, I don't much need any credibility, outside of that provided by the contents of my posts. I'm happy to let them speak for themselves, rather than appeal to authority - the latter of which is essentially non-existent in this pseudonymous context.
As the job of physician is being reduced to that of a health care service project manager who assembles and directs specialists using technology tools, it's becoming vulnerable to the same technology changes that sidelined project managers.
Skill is pareto distributed, and there is a long tail of medical services that could be done by apprenticed tradespeople, and the only thing preventing that is medical associations - and as you say, holding litigation risk.