Shamar is the governance-native operating system for clinical care. It starts with Guardian — the safety layer that audits every AI-generated note — and grows into the OS that orchestrates specialized agents across the entire care continuum.
Scribes reduced typing. They did not reduce thinking, checking, coordinating, or liability. That layer was never built — until now.
Mr. Johnson, 65 — heart failure and diabetes. Press run. The left pane is the room. The right pane is the OS: agents activating, evidence surfacing, every step logged. You hold the veto at the end — exactly as the clinician does.
Notice what Shamar never does: it never tells the clinician what to prescribe. It surfaces the patient's own data, the label, and the guideline — with the full basis one tap away — and the clinician reasons independently. Transparency isn't a feature. It's the architecture.
Shamar enters where the pain is sharpest — an unaudited AI is writing your legal medical records — and expands, tier by tier, into the operating system care runs on.
Stage 1 · The Wedge
$99 /provider/mo
Stage 2 · Expand
$299 /provider/mo
Stage 3 · The OS
Custom + revenue-integrity share
Every competitor is retrofitting agents onto a documentation product. Shamar was built in the opposite order — the governance kernel came first.
A sandboxed kernel that constrains what every agent is permitted to do. Permission boundaries per agent, human veto gates on consequential actions, and a tamper-evident log of everything. A hallucinating agent cannot act outside its cage.
Agents collaborate through one shared, live clinical document — not chaotic message-passing. Every edit is attributed. The clinician sees one source of truth and the reasoning behind every change in it.
Fourteen years of chart is not a vector-search problem. Manifest-guided retrieval navigates records by episode of care — benchmarked at 2.2× the precision of metadata-filtered RAG on longitudinal queries.
Discrete, validated, versioned clinical actions — generate_soap_note, check_drug_interaction, schedule_follow_up, flag_denial_risk — that agents call and institutions can extend. This is where the OS becomes a platform.
Twelve specialized agents, orchestrated. Each with a narrow mandate, explicit permissions, and a name for what it actually does.
chief resident
Activates specialists by context, integrates their output into one coherent note, routes only frontier-model reasoning where it's needed.
clinical reasoning
Extracts and validates clinical facts in real time — timestamped, confidence-scored, linked to the dialogue that produced them.
evidence
Surfaces guidelines, labels, and local de-identified cohort evidence — always with the full basis inspectable, never as a command.
documentation
Structured, specialty-tuned notes in under three seconds, grounded in the verified transcript — never in imagination.
coding & revenue
ICD-10, CPT, HCC and E/M codes attached with confidence scores; denial risk flagged before the claim leaves the building.
care coordination
Books follow-ups, tasks nursing, drafts plain-language patient summaries in the patient's own language and reading level.
safety & governance
Validates every recommendation against guidelines, flags contraindications, and maintains the medicolegal audit trail.
red team · NEW
Runs continuous adversarial simulation against the other agents — failure modes are found in the sandbox, never in the clinic.
prior auth · NEW
Drafts prior-authorization packets from note evidence and predicts denials before submission — EHR-independently.
panel watch · NEW
Between visits, watches labs, messages, and device data against each care plan — and escalates only on deviation.
intake · NEW
Interviews the patient conversationally before the visit — voice or WhatsApp — and hands the Orchestrator a structured brief.
feedback loop · NEW
Every clinician veto is a labeled training signal. Shamar gets better every day it runs — per clinician, per specialty, per site.
| Dimension | Ambient AI Scribes | Shamar — Clinical Agentic OS |
|---|---|---|
| Primary function | Transcribe | Orchestrate, audit, and act |
| Timing | Post-visit | Pre-visit → in-room → between visits |
| Error catching | None — the note is signed as generated | Guardian audits every note before signature |
| Reasoning transparency | Opaque | Full evidentiary basis, one tap away |
| Action execution | None | Autonomous within veto gates you set |
| Memory | Session-only | Longitudinal, episode-indexed |
| Accountability | Undefined | Cryptographic ledger of every action & veto |
| Who it serves | Enterprise health systems only | Independents, FQHCs, rural, and emerging markets too |
Integration friction is where clinical software goes to die. Shamar is architected so value starts at zero integration — and deepens on your timeline, not ours.
Guardian audits notes before signature from a side panel beside any EHR and any scribe. No APIs, no vendor approval, no IT committee. Live in days, not quarters.
Shamar reads the chart through the standard FHIR APIs certified EHRs already expose — medications, labs, problems, encounters. This powers the pre-visit brief across Epic, Oracle Health, athenahealth, eClinicalWorks and more.
Notes filed, orders drafted, follow-ups proposed — into your EHR, always behind the veto gates you configure. Delivered through each vendor's app program as your organization approves.
In settings without incumbent EHR infrastructure, Shamar doesn't integrate — it is the system of record. The care continuum runs on it from the first encounter.
Every recommendation, its basis, the model version, and the clinician's accept / modify / veto decision — cryptographically timestamped. Documentary proof of independent clinical judgment.
We publish veto rates. A healthy override rate is proof the clinician is in command; a falling error rate over time is the outcomes story. Both are yours to inspect.
Customer PHI never trains foundation models — contractually. Zero-retention inference, BAAs at every layer, SOC 2 program underway, de-identification by expert determination.
Regulatory posture: Shamar is architected to FDA's 2026 Non-Device CDS criteria — every clinical suggestion displays its complete evidentiary basis for independent professional review, and the clinician's judgment is never replaced or time-forced. Autonomous functions ship only behind explicit veto gates. Higher-risk capabilities follow the device pathway, in the open, when they're ready.
Front one · United States
Enterprise agentic AI requires an Epic contract and a health-system minimum. Guardian serves everyone they structurally can't: independent practices, FQHCs, rural hospitals, DPC clinics — starting as the safety layer on the scribe they already bought.
Front two · Nigeria & emerging markets
Where EHR penetration is minimal, Shamar isn't an add-on — it is the clinical operating system, the way mobile money leapfrogged banks. Deployed through an existing telemedicine network, payer channels, and voice-first intake built for how care actually happens.
We're onboarding a small cohort of pilot sites for Guardian. Pilot partners get founding pricing, direct access to the clinical team, and co-authorship consideration on published outcomes.
CLINICIAN VETO ON EVERY ACTION · FULL AUDIT TRAIL · NO PHI REQUIRED TO APPLY