MedOS Lite — Open-Source Health Oracle
MedOS Lite is the open-source edition of Ever's healthcare operating system. It serves two roles in the EDH ecosystem:
Health Oracle — A standards-compliant gateway that connects hospital systems (HIS, EMR, LIS, PACS) to the EDH patient-centric network, transforming institutional data into patient-owned, encrypted records.
Storage Node — An encrypted data host that stores and serves EDH patient data, earning revenue by contributing storage capacity to the network.
Any hospital, clinic, lab, or individual can run a MedOS Lite instance. The software is MIT-licensed and runs on commodity hardware.
The Virtuous Cycle
MedOS Lite creates a self-reinforcing economic loop:
1. A hospital installs MedOS Lite to serve its own patients. The hospital connects its existing HIS/EMR system. Patient data flows through MedOS Lite, is encrypted client-side, and stored on the EDH network. The hospital's patients gain sovereign access to their records. The hospital reduces data liability — it no longer holds plaintext patient data.
2. The hospital becomes a storage node. The same MedOS Lite instance that serves the hospital's patients also contributes encrypted storage capacity to the broader EDH network. Other patients — from other hospitals, other countries — can use this node for redundant, geographically distributed storage.
3. The hospital earns revenue from hosting. Every byte of encrypted data hosted for external patients generates income for the node operator. The hospital that installed MedOS Lite to improve patient care now has a revenue stream from its idle infrastructure. Storage fees are micro-payments settled on-chain.
4. Revenue incentivizes more nodes. As hosting becomes profitable, more hospitals, clinics, and independent operators deploy MedOS Lite nodes. More nodes mean more redundancy, lower latency, better geographic coverage, and higher fault tolerance for the entire network.
5. A better network attracts more patients and institutions. Patients choose EDH because their data is available everywhere, stored redundantly across dozens of nodes, and controlled entirely by them. Institutions join because the patient demand is there and the economics work.
This is the flywheel. Every new node makes the network more valuable. Every patient that joins makes operating a node more profitable.
What MedOS Lite Does
As a Health Oracle
| Capability | Description |
|---|---|
| HIS/EMR Bridge | Connects to hospital information systems via HL7 FHIR, HL7 v2, or custom adapters |
| Data Transformation | Converts institutional formats into FHIR R4 resources |
| Client-Side Encryption | All patient data is encrypted before it touches any storage layer |
| Patient Onboarding | Automatically creates EDH accounts for new patients, issues sovereign wallets |
| Consent Management | Enforces patient consent rules — which data, to whom, for how long |
| Audit Trail | Merkle-anchored access logs for tamper-proof compliance |
As a Storage Node
| Capability | Description |
|---|---|
| Encrypted Hosting | Stores encrypted patient data blobs — the node cannot read what it stores |
| CID-Addressed Retrieval | Serves data by content address (IPFS CID), independent of location |
| Redundancy | Replicates data across peer nodes for fault tolerance |
| Micro-Payments | Earns per-byte hosting fees settled on-chain |
| SLA Enforcement | Smart contract enforces uptime and availability commitments |
| Geographic Compliance | Nodes declare their jurisdiction — patients can choose where data is stored (PDPA, GDPR compliance) |
Node Economics
Revenue Sources
| Source | Description | Settlement |
|---|---|---|
| Storage fees | Per-GB-month fee for hosting encrypted patient data | On-chain micro-payment |
| Retrieval fees | Per-request fee when external parties access hosted data | On-chain micro-payment |
| Onboarding incentives | Bonus for each new patient onboarded through the node | Protocol reward |
| Uptime rewards | Bonus for maintaining high availability (99.9%+) | Protocol reward |
Cost Structure
MedOS Lite runs on commodity hardware. Minimum requirements:
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4+ cores |
| RAM | 4 GB | 8+ GB |
| Storage | 100 GB SSD | 1+ TB SSD |
| Network | 10 Mbps | 100+ Mbps |
| OS | Linux, macOS, Windows | Linux (Ubuntu 22.04+) |
A hospital with existing server infrastructure can run MedOS Lite on spare capacity at near-zero marginal cost.
Economic Model
Revenue per node = (storage_hosted_GB × fee_per_GB_month)
+ (retrievals × fee_per_retrieval)
+ uptime_bonus
+ onboarding_bonus
Break-even: ~50 GB hosted data at current fee rates
Profitable: Most hospital nodes with 500+ patients
The exact fee rates are governed by the protocol and adjust based on network supply and demand.
Architecture
Oracle Mode (Hospital → EDH)
Node Mode (Storage Provider)
Getting Started
1. Install
# Clone the repository
git clone https://github.com/ever-network/medos-lite.git
cd medos-lite
# Install dependencies
npm install
# Run the setup wizard
npm run setup
2. Configure
The setup wizard will ask:
- Mode: Oracle (hospital connector), Node (storage provider), or Both
- Hospital connection (if Oracle): HIS endpoint, FHIR server URL, credentials
- Storage allocation (if Node): How much disk space to contribute
- Jurisdiction: Where the node is physically located (for data residency compliance)
- Wallet: EVM wallet address for receiving payments
3. Start
# Start MedOS Lite
npm run start
# Or with Docker
docker-compose up -d
4. Register as a Node
Once running, register your node with the EDH network:
npm run register-node
This announces your node to the network, stakes a small deposit (for SLA enforcement), and begins accepting storage requests.
Open Source
MedOS Lite is MIT-licensed. The full source code is available at:
github.com/ever-network/medos-lite
We welcome contributions from:
- Hospital IT teams building custom HIS/EMR adapters
- Infrastructure operators optimizing storage and replication
- Protocol developers improving the economic model and SLA enforcement
- Security researchers auditing the encryption and access control layers
See Also
- System Overview — EDH platform architecture
- Ever Services — Ever's service layer
- Architecture — Three-layer architecture
- Trust Model — Security and verification