Open source
Built in the open,
on open standards
Hospital infrastructure should be transparent, inspectable and owned by the institutions that run it. medOS is open from day one — read it, contribute, self-host. You are never locked in.
$ docker compose -f docker-compose-onpremise.yml up -d
✓ 16 services · NATS · Postgres · IPFS · Besu
✓ https://medos.local — air-gapped, your hardware
The commitment
Open from day one — apply first
medOS is built in the open because the systems that run a hospital should be auditable by the people who depend on them. Sovereign storage runs on EVFS (IPFS) and audit-grade ledgers on Hyperledger Besu, with the same stylization across the stack.
The public GitHub release is being staged. Until then, access is application-based — and free-use foundation licenses are open now for aid-model deployments across Africa and low-resource health systems.
DICOM · CT chest
bafybeigd…7a3
Discharge.pdf
bafybeih2…9c1
Lab report
bafkreif…f0
IPFS-backed · node-local custody
rx.dispensed
consent.granted
ledger.posted
permissioned EVM · tamper-evident
Self-hostable
All-in-one compose: 16 services + infra + nginx on your hardware. Air-gapped supported.
EVFS — sovereign files
IPFS-backed clinical file store with content addressing and node-local custody.
Besu audit ledger
Tamper-evident, permissioned EVM chain for cross-org audit trails.
Foundation / aid model
Zero-license deployments for qualifying public-health programs — apply by email.
Open standards
Speaks every open dialect of healthcare
medOS is built on the open standards trusted across healthcare — so your data is coded, portable and never trapped in a proprietary schema.
Coded, portable, computable — fired the hyperkalemia CDS rule on write.
One write, computable everywhere
Because every value is bound to an open code system, a single observation is portable across systems, queryable for trends, and able to fire decision support — with no bespoke schema to reverse-engineer.
Portable
Export an IPS FHIR bundle for handoff — QR, file or IPFS.
Computable
Coded values feed CDS, biomarker graphs and the twin.
Exchangeable
Subscriptions push HMAC-signed bundles to partners.
No lock-in
Standards in, standards out — your data stays yours.
HL7 FHIR R4
The modern interoperability standard. medOS ships FHIR R4 read/write with SMART on FHIR, subscription delivery and a CapabilityStatement at GET /fhir/metadata.
HL7 version 2
The workhorse messaging standard for lab instruments, ADT feeds and pharmacy. medOS parses ADT/ORM/ORU over MLLP with a full ACK/NAK builder.
DICOM
The imaging standard for radiology and nuclear medicine. medOS supports MWL/MPPS for PET/CT, SPECT/CT and gamma-camera scanners, with dose-registry push.
SNOMED CT
The most comprehensive clinical terminology in the world. medOS maps isotopes, diagnoses and procedures to SNOMED CT for coded, computable records.
LOINC
The universal standard for lab and clinical observations. Every observation in the biomarker cache binds to canonical LOINC codes for trend graphs and CDS.
openEHR
Open archetypes and templates for structured clinical content. medOS bundles an openEHR preset library powering ICU monitoring and dynamic flowsheets.
What we open
The pieces we build in the open
Beyond the standards we implement, these are the parts of medOS designed to be read, forked and extended by the institutions and partners who run it.
Market packs
Per-country seed data, insurance rate tables and locale configs. Same application code, different region — add a country by dropping in seed files, zero TypeScript.
Country-agnostic modules
Capability packs with a module.json contract and a dependency-resolving installer. Entitlement is data, not branches — any country, no hardcoded list.
medical-kit
Shared front-end engines — treatment-series, perioperative status, biomarker graphs, dose patterns. Reused across 92+ miniapps.
E-Form builder
A standalone designer for clinical forms — plus the blood-bank suite and a shared data dictionary. Author once, render anywhere.
Rules as data
CDS rules, policy gates and facility-billing rules live as editable rows, not code — author NEWS2, payment gates or country billing without a redeploy.
One geography, many lenses
The decision-twin and intelligence map — Atlas, Capacity, Queue, Disease, FP&A and Twin lenses over the same bridge data model. A rendering of your data, never a separate model.
Explore HORUS →The stack
Built on these open-source technologies
medOS stands on the shoulders of the open-source community. Every layer runs on tools you already know and can inspect — grouped here by where they live in the stack.
Frontend
Data & realtime
AI · on-box
Sovereign
Ready to get started?
Explore the platform hands-on, or apply for source access and the free-use foundation program.