OpenMed docs for builders and clinical teams.
Install the CLI once preview access is granted, move from first prompt to deterministic workflows, import consumer records, run care-coordination reviews, and wire hybrid medical service endpoints without losing the terminal-native experience.
curl -fsSL "<install.sh URL shared during preview>" | bash
Use the docs the way you adopt the product.
The builder track focuses on installation, native service wiring, MCP, configuration, profiles, and CLI behavior. The clinical track focuses on workflows, skills, consumer imports, care coordination, privacy, and the actual runtime boundary.
CLI, config, and integrations
Start with setup, profiles, native service wiring, and optional MCP.
- Install and authenticate quickly
- Configure models and profiles
- Point native services at hosted, private, or on-prem endpoints
Workflows, skills, and trust
Learn how OpenMed handles prior auth, coding, care coordination, consumer summaries, FHIR, and reviewable workflow output.
- Start from pre-built clinical skills
- Choose the right agent mode for the job
- Add your own local markdown skills
- Review privacy and approval boundaries
- Run native medical tools from natural language
Hybrid medical services are part of the product story.
OpenMed does not route every clinical task through a generic frontier model. The operator runtime stays inspectable while sensitive or high-volume extraction, de-identification, terminology, and HCC work can run on protected clinical service planes designed for speed and cost efficiency.
Private extraction and coding endpoints, separate from the operator runtime.
The extraction plane covers NER, PII detection, and de-identification. The coding plane covers terminology, LOINC, RxNorm, MedlinePlus, PubMed, HCC mapping, and RAF scoring. General agent reasoning stays on the configured model-provider path; these service planes are for the clinical workloads that should be governed separately.
Operator runtime
CLI, TUI, sessions, plans, cards, and workflow artifacts stay on the operator machine.
Clinical extraction
NER, PII, and de-identification run on a protected Hugging Face-hosted accelerated service during preview.
Terminology and HCC
ICD-10, CPT, SNOMED, LOINC, RxNorm, MedlinePlus, PubMed, HCC, and RAF can run behind a separate service boundary.
Shipped feature surface
The current release is broader than extraction and terminology alone.
Deterministic review loops
Run 13 deterministic workflows with draft preview, finalize, provenance, case-run history, and workflow diffs.
Multi-source health imports
Import Apple Health, Health Connect, C-CDA, FHIR exports, and labs files into one consumer-summary path with timeline, trends, reconciliation, optional education, and optional FHIR.
Inbox and discharge workflows
Prepare local message-thread and discharge packs, triage inbox messages, build discharge handoffs, and require reviewer metadata before care-coordination finalization.
Payer, coding, claims, and FHIR
Prior auth, appeals, coding audit, HCC / RAF, claims explanation, med-rec discrepancy review, clinical documentation, and structured extraction plus FHIR diff all ship today.
Core guides
Everything needed to get operational without digging through raw markdown.
Getting Started
Install, authenticate, choose a lane, and run the first clinical, consumer, or care-coordination workflow.
CLI Reference
Commands, options, model selection, updates, and workflow-facing behavior.
Agent TUI
Conversation flow, sessions, shortcuts, plans, cards, and slash commands.
Skills
See how built-in and user-installed skills steer the agent through specialized work.
MCP Connectors
Add your own remote MCP servers and expose them as namespaced OpenMed tools.
Native Medical Services
See the hybrid deployment model for extraction, de-identification, terminology, HCC, and RAF services.
Privacy & Security
Runtime boundaries, PHI mode meaning, token storage, and when network access happens.
Also useful: Configuration and Profiles.
Protected clinical endpoints, inspectable workflows, explicit service boundaries.
OpenMed keeps the TUI, sessions, plans, and generated artifacts inspectable while many medical capabilities call configured model, inference, terminology, or MCP services. The durable review surfaces are visible plans, tool traces, workflow previews, and explicit artifacts, with protected extraction and HCC service planes separated from the general model-provider path.
- 62 built-in native tools, 13 deterministic workflows, 13 built-in skills, 4 built-in agent modes
- Consumer imports for Apple Health, Health Connect, C-CDA, FHIR exports, and labs files
- Care-coordination workflows with reviewer metadata on finalize
- Hybrid medical services for NER, PII/de-id, ICD-10, CPT, SNOMED, LOINC, RxNorm, MedlinePlus, HCC, and RAF
- Local-only consumer and care-coordination import paths with no outbound send or writeback
- No telemetry, analytics, or background usage reporting
- Optional MCP access only when explicitly configured