Plane 01
Operator runtime
Sessions, plans, tool traces, provenance, and workflow artifacts stay on the machine running OpenMed.
Inspectable workflows · consumer + coordination · terminal-native
Terminal-native AI for clinical workflows that need control.
OpenMed gives builders and clinical teams one inspectable agent for prior auth, appeals, coding, claims explanation, care coordination, consumer record imports, clinical documentation, FHIR work, literature search, and structured artifacts across an inspectable operator runtime with protected hybrid medical services.
One prompt, one plan, visible execution.
The product story should match the product: structured, terminal-native, and inspectable.
Runtime boundary
Protected clinical services, inspectable runtime, explicit review before action.
OpenMed keeps the operator review loop visible, separates medical-service endpoints from the model-provider path, and routes sensitive or high-volume clinical processing to dedicated services when those paths are invoked.
Inspectable runtime
The TUI, sessions, plans, and generated artifacts remain visible and locally controlled.
Protected clinical services
Extraction, de-identification, terminology, LOINC, RxNorm, MedlinePlus, and HCC services run on dedicated medical-service endpoints when those paths are invoked.
Performance and cost efficiency
High-volume unstructured clinical processing can stay on dedicated service planes instead of consuming frontier-model context for every page.
Preview deployment
During preview, the native medical-service tier is provisioned on private Hugging Face accelerated infrastructure.
Workflow review
Deterministic workflows support draft preview, approval tokens, provenance, visible artifacts, and reviewer metadata on care-coordination finalization.
Zero telemetry
No analytics, tracking, or background usage reporting built into the product.
Hybrid medical services, not a black-box healthcare prompt.
OpenMed separates the operator runtime, the model-provider path, and the medical service tier. That makes extraction, de-identification, terminology, LOINC, RxNorm, MedlinePlus, and HCC infrastructure visible, configurable, and better suited to sensitive or high-volume clinical processing than a single undifferentiated model path.
Deployment model
Keep the workflow inspectable. Put the medical services where you need them.
During preview, OpenMed operates these service planes on private Hugging Face accelerated infrastructure behind protected endpoints so evaluators do not need to self-host clinical services. The same service planes can later move to customer VPC, private cloud, or on-prem infrastructure without changing the CLI or TUI experience.
Plane 02
Clinical extraction and de-identification
NER, PII detection, and de-identification run through a dedicated native service endpoint.
Plane 03
Terminology, coding, and HCC
PubMed, ICD-10, CPT, SNOMED, LOINC, RxNorm, MedlinePlus, HCC mapping, and RAF scoring run through a separate protected service plane.
Designed for the people shipping it and the teams using it.
OpenMed serves infrastructure-minded adopters and clinical operators in the same workflow surface.
For builders
Ship a terminal-native medical workflow with visible control surfaces instead of a black-box assistant.
- Install with a provisioned shell command
- Configure models, profiles, native services, and optional MCP
- Inspect plans, tool traces, and workflow outputs
For clinical teams
Use one interface for prior auth, appeals, coding, documentation, care coordination, consumer-health summaries, and evidence gathering.
- Start from pre-built clinical skills
- Choose the right built-in agent mode for the job
- Review workflow previews before finalizing
- Keep outputs structured, exportable, and evidence-linked
Capabilities grounded in the current product.
Everything on this page maps to workflows, tools, skills, or documentation already present in the repo.
Clinical workflows
Prior Auth + Appeals
Review requests against CPT / ICD-10 criteria, LCD/NCD guidance, and denial evidence gaps with explicit recommendations.
Care coordination
Inbox + Discharge
Prepare local inbox or discharge exports, run reviewer-safe triage and handoff workflows, and generate follow-up tasks plus patient-facing drafts.
Consumer health
Record Imports + Summary
Import Apple Health, Health Connect, C-CDA, FHIR export, or labs files into one consumer-summary path with timeline, trends, reconciliation, questions, and narrative.
Structured output
Coding + Claims
Run ICD-10, HCC, RAF, code-audit, and claims-explainer workflows with terminology validation and model-aware context when configured.
Clinical documentation
Notes + SOAP
Turn visit transcripts into structured notes with vitals parsing, medication review flags, ICD-10 extraction, and E/M hints.
FHIR + extraction
Structured FHIR Diff
Extract structured entities, build FHIR bundles, and compare them against a baseline bundle with visible diffs.
Native medical tools
PubMed + Terminology
Use built-in PubMed, ICD-10, CPT, SNOMED, LOINC, RxNorm, MedlinePlus, HCC, RAF, and crosswalk tooling through configurable native service endpoints.
Deployment
Hybrid Medical Services
Use protected extraction, de-identification, terminology, education, and HCC services provisioned privately on Hugging Face during preview, with a portable service boundary for later customer-managed deployment.
Deterministic workflows
Draft, Finalize, Diff
Use draft preview, approval-token finalize, provenance, case-run history, and workflow diffing instead of opaque one-shot chat output.
Remote integrations
Bring Your Own MCP
Attach remote JSON-RPC MCP servers when you need organization-specific tools beyond the native OpenMed surface.
Trust
Mode Boundaries
Use `clinical`, `consumer`, `coordination`, and `plan` modes to choose the right execution lane and review boundary for the job.
Install, authenticate, ask.
Three steps from a fresh machine to a live workflow in the terminal across clinical, consumer, or care-coordination lanes.
Install
OpenMed is currently in preview. Installation is shared directly with approved evaluators.
Preview Access
Installation is shared directly during preview.Authenticate
Use Codex OAuth or provide an API key, depending on the SDK path you want.
openmed loginAsk
Describe the workflow in natural language and inspect the plan, tool traces, and outputs as they appear.
openmedDocs that behave like product onboarding.
Start at the route you need instead of scanning one long index page.
Overview
Getting Started
Install, authenticate, choose a lane, and run the first workflow.
Product
CLI Reference
Understand the commands, agent modes, flags, and workflow-facing behavior.
Product
Agent TUI
See the terminal interface, plans, sessions, and keyboard flows.
Product
Skills
Review the built-in skill library and learn how to add your own local skills.
Product
Profiles
Inspect the built-in config presets and how they affect current settings.
Integrations
MCP Connectors
Add your own remote MCP servers and expose them as namespaced tools.
Integrations
Native Medical Services
See how extraction, de-identification, terminology, RxNorm, MedlinePlus, and HCC endpoints are deployed and secured.
Trust
Privacy & Security
Understand runtime boundaries, PHI mode meaning, token storage, and network paths.
Start with the CLI and choose the lane you need.
The product boundary today is straightforward: local sessions and artifacts, four built-in agent modes, configurable model and medical-service endpoints, optional MCP, and workflow outputs you can inspect before you depend on them. Consumer-import and care-coordination lanes remain local review flows with no outbound send or external-system writeback path.