A policy assistant for nurses
- Before
- Searching a shared drive and finding an old version.
- With Dev Studio
- Answers from the current policy, with the page cited.
Design agents visually, connect approved data and put them into production, on one compliant core in your own cloud.
Forhealth-system IT, informatics and data teams
Policies, protocols and documents, with their access rules.
Drag stages onto a canvas: redaction, chunking, retrieval.
Test several models on the same questions.
Staged, versioned, logged, and easy to roll back.
Representative examples, not customer case studies.
01Drag the flow together: ingestion, redaction, chunking, retrieval.
02Choose the embedding model and build the vector store behind it.
Scroll to explore
See the whole agent flow, not code.
Every model and tool connection in one place.
Cost per user, team and agent.
Swap the model without rebuilding the agent.
Design, test, stage, ship, roll back.
PHI boundary and audit log on every agent, in your cloud.
Dev Studio is the back end of the InferAgents Suite: where a health system's own engineering team builds, tests and ships AI agents, with API, token and quota management built in.
No. It is part of the InferAgents Suite, runs on the same HIPAA-compliant core, and shares the suite's domain at inferagents.ai.
Health-system IT, informatics and engineering teams. At University of Chicago Medicine, the health system's own IT organisation builds agents in it directly.
Not for the common cases: agents are assembled visually from ready-made stages. Connecting new source systems and approving production releases remain engineering work.
Usage and cost are visible per user, team and agent across every model provider, with quotas that throttle or reroute work at a threshold.