The model layer

Six models. One clinical record.

IASORA runs a named, versioned model layer rather than a single prompt behind a chat box. Each model does one job well on its own. Together they are what the agents are made of.

The six

Each one does a job you can name.

Speech becomes a note. The note becomes code. The code becomes a score, an answer, and a proposed action. Six models on one record, each doing one thing well enough to be measured on its own.

01 — Language to code

IASORA Lex

A note only becomes clinical data when something can name the code and defend it.

Codes to

SNOMED CT · ICD-10 · LOINC · RxNorm · CPT

Extracts

Conditions, medications, allergies, procedures, observations

Resolves

Abbreviations, negation, disambiguation, specialty context, confidence thresholds

Reads

Scribe notes, referral letters, uploaded documents

The agent workforce

Each agent works next to a person.

An agent is a chain of these models pointed at one job. It prepares the work; the person it sits beside decides. Any model can also be licensed on its own.

Clinician

Documentation agent

Writes up the consultation and files it coded.

ScribeLexReason

Patient

Inbound voice agent

Answers the call and books against live availability.

VoiceReason

Practice manager

Outbound voice agent

Calls out for recall, reminders and results follow-up.

VoiceReason

Care coordinator

Care-gap agent

Finds who is overdue, and reaches out to them.

QLRiskVoice

Clinical director

Population health agent

Stratifies the panel and measures the outcome.

RiskReasonQL

Whichever agent runs, the run is the same six steps

01CaptureA consultation, a call, a documentScribe · Voice
02CodeLanguage becomes coded, structured dataLex
03ScoreThe patient is re-scored, every point traceableRisk
04ProposeThe agent drafts the action, with its evidenceReason
05 · GateA person approvesNothing reaches the chart unapprovedHuman decision
06MeasureCounted in English, over the live recordQL

Every step above is one authorised, metered and logged call against your workspace: which model, which user, what it was asked, what it returned.

How they run

Every call is authorised, metered and logged.

The model layer sits behind one gateway. That is what makes it reviewable: there is a single place where access, cost, residency and the audit trail are decided.

On or off, per workspace

Each model is switched on for a workspace at a tier, or left off entirely. A clinic that wants the scribe and nothing else gets exactly that.

Metered to the action

Every call is priced and counted where it happened, so the cost of an AI action is a number you can put next to the work it did.

Logged, every request

Which model, which workspace, which user, what it was asked and what it returned. The audit trail is written whether or not anyone is looking.

Inference stays in region

Kept inside your jurisdiction, on private cloud or on-premise including air-gapped, for health systems that cannot send data out.

Bring your own keys

Run the layer on your own model credentials where policy requires it, without giving up the routing, metering and audit around them.

Versioned, and reversible

Models carry versions. Weights, thresholds and rules change under an audit diff, and a change that does not hold up is rolled back in one step.

Where the models show up in the product

Scribe and Voice in the consultation and at the front desk, Lex on every document, Risk across the panel, QL in Analytics Studio, and Reason inside every agent.

See the platform

Get started

Run one model, or the whole layer.

Use the scribe on your own consultations, or talk to us about the model layer inside your own estate.