A healthcare system is not one organisation.
It is hundreds, running at once.
OpenKnowra resolves hospitals, clinics, pharmacy, provider networks, workforce, payers and regulators into one live Healthcare System Twin. Its context-native grid lets AI agents sense, reason and act across capacity, workforce, care pathways, reimbursement and compliance, and it is the engine behind the Healthcare Complexity Index.
- 1,000 free credits
- No credit card for corporate accounts
- No NDA
- No company data required
Experience the platform with sample data today. Connect your enterprise when you’re ready.
Six systems. Six partial truths.
Every system holds one slice of the organisation. None of them sees the whole. Decisions get made out of context and wait on someone to stitch the story together by hand, and the cost shows up as blocked beds, uncovered shifts, avoidable denials and compliance found late.
Complexity, not size. How hard a system is to run, not how big it is.
Healthcare has always measured scale. Revenue, beds, headcount, facilities. It has never measured difficulty. Two systems can report identical revenue and be worlds apart in how hard they are to operate, yet pay, staffing, cost benchmarks and integration plans are all set as though they are the same.
The Healthcare Complexity Index is the first rigorous, comparable measure of how complex a healthcare system is to run. It scores a system from 0 to 100 across nine dimensions of organisational complexity, always relative to a defined set of peers, and it runs on this grid.
Nine dimensions resolved from the same twin the grid runs on. Each is scored as a rank within the chosen peer set, so the answer is never an absolute verdict, only a defensible read of how demanding one system is against others of its kind.
Nine dimensions of what makes a healthcare system hard to run.
Complexity is not one thing, so the Index does not treat it as one signal. Each dimension had to clear two tests: it had to be a distinct driver of difficulty rather than a restatement of another, and it had to be countable rather than a matter of opinion. Six were conceptualised by Cornell’s Institute for Compensation Studies. Three came from Spire.AI and its Work and Workforce Engineering practice.
Structural differentiation
How many legal entities, hospitals, clinics and sites have to be governed as one, and across how many geographies. Every additional part is something to reconcile and keep aligned.
Workforce heterogeneity
How many distinct clinical and non-clinical credential types the system must roster, supervise and keep compliant. A narrow workforce and a wide one are not the same job.
Service & payer concentration
How widely activity spreads across service lines and payers. Every additional combination adds contracts, authorisation rules and documentation standards.
Span & administrative intensity
Manager to staff ratios, the administrative share of the workforce and the number of supervisory layers. The visible footprint of how much coordination is actually required.
Regulatory & jurisdictional surface
States, licensure boards, payer contracts, bargaining units and accreditation regimes in scope. Each one is a separate rulebook to satisfy and evidence.
Clinical acuity
The severity and resource intensity of the patients treated and the breadth of conditions handled. The dimension tied most directly to workforce demand.
Financial & reimbursement risk
How many reimbursement models run at once, from fee for service through to full risk, and how far exposure varies across them.
Teaching & academic intensity
The supervision and coordination load carried by graduate medical education, research activity and academic affiliation, running alongside clinical operations.
Digital & interoperability
How many clinical and administrative systems must be integrated and kept in reliable exchange. A fragmented estate makes every other dimension harder to manage.
A living twin of your healthcare system, and the system that runs on it.
Healthcare Systems combines two capabilities into one context spine. The first understands the organisation. The second acts on it, autonomously and governed.
It understands your healthcare system
EHR, rostering, HRIS, claims, supply, quality and regulatory data resolved into one living Healthcare System Twin, with provenance on every signal and your own clinical and policy rules built in. Not a copy in a lake, a live model connected to the systems you already run.
And it acts on what it finds
Healthcare Systems assemblies, digital workers and AI agents act on that twin to relieve capacity pressure, close workforce gaps, keep pathways moving, recover reimbursement and evidence compliance. Clinicians and leaders stay in command on every call that carries clinical or financial consequence.
Healthcare Systems is not an EHR, a rostering tool or a claims platform. Those each hold one slice. This is the context layer above them that resolves the whole system and lets work run across it.
One twin. Seven operating clusters.
The whole healthcare system on one twin, opened into seven clusters, all reading the same resolved system context.
Outcomes, not dashboards.
Flow pressure surfaced against admissions already in the pipeline, so escalation happens before the ward is full.
Coverage, credentials and fatigue resolved together, so gaps get filled safely rather than expensively.
The same twin that runs the work scores how demanding the system is, so cost and pay can be judged against difficulty rather than size.
Autonomy you can audit. Routine work runs itself; a person stays on every decision that carries clinical or financial consequence; and the split between the two stays visible end to end.
A grid is not one thing.
It’s the whole system, layered.
This is what separates a grid from a solution. The healthcare system opens into clusters, each cluster into running assemblies, each assembly composed of the workers, agents and APIs that do the work.
Operational clusters
Seven operating areas. Every part of the system has a home on the twin.the system, groupedAssemblies
Complete functions that run end to end, governed at every step.21 running functionsWorkers · Agents · APIs
Workers own the process, agents reason and decide, APIs feed real-time context.28 workers · 39 agents · 37 APIsThe trace is the decision.
Every capacity, rostering, pathway and reimbursement decision moves through the same ordered checkpoints, so the decision and its full trace are produced together, down to the source rule.
Causal and deterministic
Every recommendation follows your clinical and policy rules in order, not a probabilistic guess. A clinical lead, a compliance officer or an auditor can open the chain and see exactly why an action was proposed, down to the rule that produced it.
Humans on the gates
Clinicians and leaders stay in command on the high-stakes calls: clinical escalation, agency engagement, appeals, and anything that carries patient safety or regulatory exposure.
Proven beyond healthcare
The same reasoning substrate is formalized in peer-reviewed research for aerospace competency management and runs tier-one banking operations.
Built for scrutiny
Certified to SOC 2 and ISO 27001, with an independent bias audit, and built for the transparency that regimes such as the EU AI Act now require.
Walk your hardest capacity call, end to end.
On your sites, your workforce, your payers, as the use case. Not a generic demo.