Clinicians
Help define note structure, workflow priorities, and what the app must show at the point of care.
Team
Built by clinicians, engineers, and contributors.
The project is intentionally cross-disciplinary. The goal is not just software, but software that matches how care actually happens.
CD
Core Devs
Platform architecture
MD
Medical Board
Clinical workflows
SE
SecEng
Cryptography
You
Join the team
Who Fits Here
The project needs more than software engineers.
The best open-source healthcare tools are shaped by people who understand care delivery, implementation friction, and the realities of local systems.
Engineers
Build the data model, input pipelines, access control, and deployment tooling.
Writers and translators
Make the product understandable, maintainable, and useful in more than one language.
Security and policy reviewers
Check that the product respects patient privacy, access boundaries, and regulatory reality.
How We Work
Simple feedback loops, not heavy process.
The project should stay small enough to move, but structured enough that people can contribute without guessing how decisions get made.
- Start from a concrete workflow or problem, not abstract tech for its own sake.
- Prototype quickly, then test against a realistic care scenario.
- Keep the interface understandable for people who are already busy.
- Prefer changes that improve clarity, not just feature count.
Contribution path
1. Observe
Describe the workflow you want to improve.
2. Design
Sketch the data shape or interaction that solves it.
3. Review
Check the change against privacy, speed, and usability.
4. Ship
Merge only once the feature clearly helps the real user.
Roadmap
Project Roadmap
What the team has shipped and what is next on the horizon.
Shipped
Phase 1 — Core Offline Clinician Workflow
Local encrypted patient storage, FHIR R4 resource model, patient CRUD with encounter timeline, and offline-first authentication with full audit logging.
Shipped
Phase 2 — Local Sync and Mesh
Peer discovery, delta sync with vector clock merge, and automatic conflict detection for small clinics operating as a connected mesh.
Shipped
Phase 3 — Institutional Access Control
Attribute-based access control (ABAC) policy engine, department silos with emergency override workflows, and LDAP/Active Directory integration hooks.
Upcoming
Phase 4 — Local Intelligence (Highly Adaptable)
OCR pipeline for document scans, speech-to-text dictation, structured data extraction, and human-in-the-loop review queues. Highly adaptable to local languages and clinical specialties.
Upcoming
Phase 5 — Clinical Calculators, Knowledge Banks, and Drug Databases
Built-in clinical decision support calculators, integrated medical reference libraries, and periodically updated drug interaction and dosage databases.
Upcoming
Phase 6 — Releases for Distributed Deployments and Large Scale Organisations
Tiered packaging for rural hospitals, multi-department campuses, and regional health networks with centralised administration and telemetry.
Upcoming
Phase 7 — Internal Secure Communications Stack
End-to-end encrypted messaging, VoIP, and video conferencing between clinicians and departments with full audit trails and no third-party relay.
Upcoming
Phase 8 — Imaging and Lab Integration
DICOM and HL7/FHIR bridge for radiology, pathology, and lab systems enabling structured result ingestion and report linking.
Upcoming
Phase 9 — Federation and Research
Consent-driven record sharing, privacy-preserving analytic queries, ABDM/ABHA integration, and IHE profile conformance for research networks.
Upcoming
Phase 10 — Complete HIS
Billing, scheduling, inventory management, and other hospital information system modules for end-to-end clinical operations.
Upcoming
Phase 11 — Experimental Feature Sets
Cutting-edge prototypes such as ambient listening assistants, predictive triage signals, and synthetic data generators for training and testing.