Clinical training covers how to care for a patient. It almost never covers the system that determines whether that care is available, funded, staffed or permitted.
Which means a large number of people make decisions inside that system with no formal grounding in how it works.
The layer that decides what care happens
Four forces shape what a health organisation actually does, and they operate largely independently of clinical judgement.
How money flows. What gets paid for, by whom, on what basis.
What regulation requires. Licensing, accreditation, safety obligations, reporting.
What capacity exists. Staff, space, equipment, and the flow between them.
What the organisation is measured on. Targets and metrics, which shape behaviour more strongly than strategy documents do.
A clinician can be entirely right about what a patient needs and entirely unable to arrange it, and the reason is almost always in this layer.
The demand for this capability is rising because healthcare is being rebuilt around data and devices, which brings commercial, regulatory and operational questions into every clinical service.
What the direction covers
The scope: hospitals, insurance, the FDA, reimbursement, operations and the business of healthtech.
Four capabilities.
Health system structures and financing. How different systems are organised and paid for, which varies enormously between countries and determines what a product or service has to prove and to whom.
Reimbursement and coding. How services convert into payment, and the coding layer that connects to health informatics.
Regulation and accreditation. What organisations must do and demonstrate.
Operations. Capacity, flow, scheduling, workforce planning and quality improvement.
Reimbursement, which shapes everything upstream of it
The part that most changes how someone sees the system once they understand it.
Payment mechanisms create incentives, and those incentives shape behaviour regardless of intent.
Paying per activity rewards volume. More procedures, more visits, more tests.
Paying per patient per period rewards keeping people well and creates a pressure to under-provide.
Paying per episode rewards efficiency within the episode and creates edge effects at its boundaries.
Paying against outcomes sounds ideal and runs into measurement: attributing an outcome to a provider requires risk adjustment, and imperfect risk adjustment penalises those treating sicker patients.
Every mechanism has a failure mode. There is no clean design, which is why systems keep changing theirs.
Two practical consequences.
Anything new needs a payment route. A device, a service or a digital product that no mechanism pays for will not be adopted at scale however good it is. This is the single most common reason promising healthtech does not reach patients, and it is frequently discovered after the product is built.
Coding practice is not neutral. Where codes drive payment, coding carries financial incentive alongside clinical fact. Analysts treating claims data as a clinical record inherit that, which links directly to the health informatics direction.
Where this sits in the domain
Healthcare systems, regulation and operations is the tenth of ten directions in Astra Trainer's medicine and healthtech domain, and the one that connects the other nine to whether anything reaches a patient.
Partners scoping it are usually either health systems developing clinical leaders, or healthtech companies whose engineers and commercial staff need to understand the buyer. For the latter it is frequently scoped with medical devices for the regulatory layer and health informatics for the data layer. Lessons are five minutes, which suits clinical managers who have no protected time. You can see the ten directions here.
Capacity is a flow problem, not a bed count
The most useful operational idea in this direction, and the least intuitive.
Healthcare capacity problems present as shortage: not enough beds, theatre time, clinic slots. The instinct is to add resource.
Frequently the constraint is elsewhere.
The bottleneck is usually not where the queue is. A queue forms in front of a constraint, and the constraint may be several steps downstream. Emergency departments back up because wards are full; wards are full because discharge is slow; discharge is slow because social care or transport is not available. Adding emergency capacity treats the symptom.
Variation destroys capacity. A system running at high average utilisation with variable demand and variable service time will queue badly, because there is no slack to absorb variation. This is a queueing result and it is deeply counterintuitive to anyone whose instinct is to maximise utilisation. Planning a service at ninety-five percent occupancy guarantees delays.
Local optimisation harms the whole. A department that maximises its own throughput can create work downstream and reduce total output.
These are standard operations management ideas, applied in manufacturing for decades, and they are not part of most clinical or managerial training in healthcare.
Why healthtech products fail on procurement
Worth a section, because it is where commercial teams lose years.
The buyer is not the user. The clinician who wants it does not hold the budget. The budget holder has different criteria and a longer list of competing demands.
The budget may sit in the wrong place. A product that saves money in one part of a system but is paid for by another will struggle, because the payer sees only cost.
Evidence requirements differ from regulatory requirements. Clearance to market is not the same as evidence sufficient for a health technology assessment or a procurement decision, and the second is usually harder.
Integration cost is real and rarely counted in the proposal.
Procurement processes are slow by design, for accountability reasons, and treating that as an obstacle to be bypassed generally makes it slower.
Commercial teams that understand this build the payment and evidence route alongside the product. Teams that do not discover it after building something clinically excellent that nobody can buy.
The roles, named
Clinical directors and clinical leads. Clinicians with management responsibility, which is where most of this capability is needed and least often supplied.
Service and operations managers.
Health economists and HTA specialists.
Reimbursement and market access specialists in industry.
Quality improvement practitioners.
Capacity and demand planners, a small group with disproportionate influence.
Compliance and accreditation staff.
Commercial and product staff in healthtech, who need to understand the buyer rather than the user.
Who can be trained into it
Clinicians moving into management. The largest and most underserved group. They arrive with clinical credibility and without financial, operational or regulatory frameworks, and the usual approach is to let them work it out. Structured training here has an unusually direct return, because these are the people making resource decisions.
Operations professionals from other sectors. Manufacturing, logistics and aviation all bring flow and capacity thinking that healthcare needs and lacks. The gap is the clinical and regulatory context.
Finance staff in health organisations, who understand the money and frequently not the clinical activity generating it.
Commercial staff entering healthtech from other industries, where the buying process is unlike anything they have sold into.
Policy and commissioning staff.
Analysts working with operational and financial data that encodes all of the above.
Scope and jurisdiction. Health system structures, financing, regulation and reimbursement differ substantially between countries, and much of this content is jurisdiction-specific. Training builds the concepts and the analytical frameworks and must be grounded in the relevant system for the partner. Nothing here constitutes regulatory, reimbursement, legal or financial advice for a specific organisation or product, and market access strategy requires qualified professional input.
What to take from this
Money, regulation, capacity and measurement decide what care happens, and almost nobody working in healthcare is trained in them.
Every payment mechanism creates incentives and every one has a failure mode. Anything new without a payment route does not scale, however good it is.
Capacity problems are flow problems. The bottleneck is rarely where the queue is, and high average utilisation guarantees delay when demand varies.
Healthtech fails on procurement more often than on clinical performance, and the buyer is not the user.
And clinicians moving into management are the group where structured training has the most direct return, because they hold the credibility and make the decisions.
Why do clinicians need this?
Because clinical training does not cover the system that decides whether care is funded, staffed or permitted, and clinicians in management roles make resource decisions inside it without formal grounding.
Why does reimbursement matter so much to product teams?
Because a device or service that no payment mechanism covers will not be adopted at scale regardless of quality. That is the most common reason promising healthtech does not reach patients, and it is usually discovered after the product is built.
Why does adding capacity often not help?
Because the queue forms in front of a constraint that may be several steps downstream, and because high average utilisation with variable demand produces delay by construction. Both are standard operations results.
Who converts into these roles well?
Clinicians moving into management, who need the frameworks; operations professionals from manufacturing, logistics or aviation, who bring flow thinking and need the clinical context; and commercial staff entering healthtech from other industries.
Where does this fit in the domain?
Tenth of ten directions in Astra Trainer's medicine and healthtech domain, and the one connecting the other nine to whether anything reaches a patient. You can see them here.