One operational graph underneath every healthcare answer.
Generating a healthcare agent is the easy part. Grounding it in 1,958 mapped processes — and the regulations, standards, and CMS benchmarks behind each — is the part Amandil already built. Build agents you own, run them in your stack, kept current as healthcare moves.
Two sides of one graph: the knowledge an agent reasons from, and the guardrails that govern what it's allowed to do.
Knowledge grounds reasoning. Every process linked, every metric cited.
Guardrails govern action. The graph defines the bounds; the agent enforces them.
1,958 processes in the healthcare graph — any one of them can host an agent that cites the regulation, applies the standard, and returns an audit trail. The three below illustrate the shape the substrate produces — pattern, mechanism, output. Design partners build the first production deployments.
The same three customer segments that anchor every Amandil vertical. Payers and providers run the operations. Consultancies compress discovery into branded analysis. Health-IT vendors embed the graph into their products.
Show me the processes CMS thinks we're worst at — ranked by automation feasibility and payback.
Sixteen of twenty-two domains are shared between payer and provider — the mirror_of relationship pairs both views of the same work so the seam stops being a black box. Diagnose, benchmark, simulate, automate.
Replace six weeks of discovery with a 30-minute branded analysis.
Start at the end state. The graph already contains every domain, process, standard, regulation, role, and benchmark. Walk into the first leadership meeting with a ranked list of opportunities and a defensible citation for each.
Inherit a healthcare operations context layer instead of building one.
Embed Amandil through a native Model Context Protocol server. Issue a bearer token, scope to allowed tools and L1 domains, and your product inherits 1,958 grounded processes, 50+ standards, 20+ regulatory frameworks — all citeable, all versioned.
No data sharing, no integration. We benchmark your organization against CMS public data — and hand back the processes to fix first.
Annual platform licensing. Available via app, API, or AI assistant integration. Live demo against the graph included in every roadmap request.
Yes. It's live at v1.11 — 22 domains, 1,958 processes, 10,140 typed edges, stitched to public CMS data for 9,000+ hospitals, with 2,493 regulations reverse-indexed. Every node is citeable and versioned.
No. The graph is a public reference architecture of how healthcare operates — its processes, standards, and 2,493 regulations — with peer benchmarks drawn from public sources such as CMS and HFMA. None of it is your internal systems. Benchmark against the public data, or drop in your own; no integration is required to start.
CMS Medicare data, HIPAA, NCQA, and Joint Commission, plus reference standards X12, FHIR, HL7v2, CPT, HCPCS, and ICD-10 — with 2,493 regulations reverse-indexed to the processes they govern.
Through native Model Context Protocol (MCP) for Claude, Cursor, and any MCP-compatible framework, or REST for legacy stacks. The agent calls the graph like any other tool and gets structured, token-budgeted context with a citation on every answer.