GwenOS
The healthcare operating system
GwenOS is the platform payers, providers, and health services run their administrative work on. It plugs into the systems you already have.
Talk to usWhat it is
One record per person. Healthcare-ready agents on top.
Healthcare runs on systems of record, plus a second pile of tools that do the work. The two rarely agree on who the patient is. GwenOS puts both in one operating system. It resolves every person into one record and puts healthcare-ready agents to work on top of it.
The stack
Start at the bottom.
Most of GwenOS sits below the waterline. Scroll up through it, from the Models at the base to the Solutions your teams run every day.
Models
GwenOS routes each task to the model that fits.
Frontier models for breadth. Our own LLMs, SLMs, and sovereign models for the determinations healthcare makes millions of times a day.
Agent Harness
This layer is Gwen.
Skills, endpoints, cognitive services, MCP, routing, and memory, with security and governance built in. Models are necessary but insufficient for healthcare work. The harness is the part that knows what a prior auth is.
Entities & Digital Twins
One record per person
Patient, Member, Provider, Payer, and Claim 360. One resolved record per entity, assembled from every system that holds a fragment. Most healthcare AI fails because the agent does not know who the patient is.
Entities & Digital TwinsData & Integrations
Nothing moves first.
Connectors, clearinghouses, APIs, and industry networks. GwenOS meets data where it already lives.
Snowflake Native AppsCapabilities & Knowledge
Built once, used by every workflow
OCR, match and merge, entity resolution, evidence extraction, policy management, intelligent queuing. Beside them sit payer policies, codes, clinical guidelines, and your own history, kept live. The tenth workflow deploys faster than the first because all of this is already here.
Surfaces
Where your people work
- Gwen StudioBuilds an Ai Worker from a policy document.
- Gwen CoworkerPending: One line from Product.
- Gwen CodePuts healthcare endpoints in your codebase.
- Dashboards & AnalyticsShows what every workflow did, and how long it took.
- End User InterfaceWhere reviewers, coders, and analysts work the queue.
Solutions
Five Solutions, ready to run
- Intelligent UMReads the chart before the nurse does.
- Intelligent RCMReviews the claim before it leaves and works the denial when it comes back.
- Medical CodingSuggests the code and shows the line in the chart that supports it.
- Payment IntegrityChecks the claim against the contract, the policy, and the record.
- HCC Risk AdjustmentTies every code to its evidence, before the visit and after.
GwenOS
That is GwenOS.
It is the platform payers, providers, and health services run their administrative work on. It resolves every person into one record and puts healthcare-ready agents to work on top of it. It plugs into the systems you already have and deploys in weeks.
How deep it goes
Most platforms stop at the Agent Harness.
GwenOS keeps going, down to Entities and its own Models. An agent that can read a chart is useful. An agent that knows whose chart it is can do the work.
Security & Governance
Governance runs through every layer
Policy, privacy, audit, retention, and access control live in the platform. Every workflow inherits them.
Pending: page planned at /gwenos/security-governanceTime to production
Live in 60 days
UPMC went live on utilization management in 60 days. GwenOS plugs into the claims system, the EHR, and the clearinghouse you already run. Nothing gets torn out first.
Pending: confirm go-live wording with Fawad before publishingWho runs on it
One platform across payers, providers, and health services
The same layers sit under every segment. What changes is the Solutions on top.
- Payers
- Providers
- Home health
- Health services