blueOpenHealthcare
blueOpenHealthcare is the free, source-available edition of blueHealthcare, priced by country using the World Bank's own published income classification rather than a bespoke list: free automatically for low- and lower-middle-income countries, free case by case for upper-middle-income countries, and licensed commercially everywhere else. It exists for two reasons, not one — so that health systems that cannot pay for software can still run a signed, verifiable clinical record, and because it is a channel to developers and clinicians who already move between two health systems and can teach us what their country's coding, privacy law and language actually require. No patient data, ever — real or "anonymised" — anywhere in this community.
blueOpenHealthcare — this section
- Source-available; the licence restricts who may run it for free, so it is not "open source"
- Free for low- and lower-middle-income countries; case-by-case for upper-middle-income; a commercial licence is required everywhere else
- Running it for real patients requires sharing back changes and translations — never patient data
- Code contributions are not yet accepted — the licence is proposed and pending legal review
- All of the platform's modules, plus the eight clinical products, for eligible countries (see "What's in the free edition" below)
- blueVigil, the trial-safety product on the main site, is not part of this release
The commercial blueHealthcare platform
- Licensed commercially, sold by contract — see the healthcare overview
- Available to any organisation regardless of country, including high-income countries such as the US, Canada, the UK, Germany, Australia, and Saudi Arabia
- No share-back obligation
- The full product suite listed on the overview page
Eligibility is set by the World Bank's country income classification, published annually: low- and lower-middle-income countries are eligible automatically, upper-middle-income countries may apply and MOBLUEHQ decides case by case, and high-income countries (Canada, the US, the UK, Germany, Australia, Saudi Arabia among them) need a commercial licence. It's free to use, provided you share back what you build. Anyone, anywhere, may read the code and build with synthetic data — the location test applies only to running it for real patients.
This exists for two reasons, not one: so that health systems that cannot pay for software can still run a signed, verifiable clinical record, and because it's how the software reaches developers and clinicians who already move between two health systems — exactly the people best placed to tell us what a country's coding, privacy law and language actually require. Share-back means registering each live clinic and sending back the code of your changes and translations — never patient data. See the full eligibility and share-back terms.
All eight blueHealthcare products, for eligible countries: patient record and terminology, registration and scheduling, clinical notes, orders, results, medicines, lab, imaging, and integrations, together with the launcher, the receipt verifier (open to everyone), a developer kit (written, and inside the source package on the downloads page), and the platform's cryptographic eSource module for clinical trials.
Running blueOpenHealthcare for free comes with one obligation only: share back the code of your changes and your translations. It is never conditional on sending us patient data in any form — not identifiable, not de-identified, not aggregated. There is no version of this programme, today or planned, where continuing to use the free edition depends on what a clinic's records contain.
Start here
The first page for clinic administrators, developers, and ministry officials evaluating the platform.
What you get
A measured inventory of modules, products, tools, and system requirements for a ministry or board to judge the platform.
AI features
The language-model features in blueHealthcare: what they do, how they work, what gates them, and their status.
Why
Why there is a free edition, and what "open" does and doesn't mean.
Architecture
The core/app split, the pack model, receipts, and the verifier.
Specs
The jurisdiction pack, coding system, privacy regime and FHIR profile interfaces, quoted from the real code.
Receipt specification
A draft standard any system can adopt to prove what it ran and recorded, independent of this platform.
Eligibility and share-back
Who can use it for free, and what sharing back means.
Downloads
The planned clinic-server installer and developer kit — not yet available.
Roadmap
What's built, what's measured, what isn't — in plain words.
Country packs
The pack template, and worked examples for the Philippines, Mexico, India, China and Jamaica — including every question still open.
API
Working examples of common API operations, executed by automated tests in the repository.
Contribute
What's possible now versus later, and the rule that never bends.
Fixtures
Synthetic fixture sets: what they are, and the no-real-data rule.
Governance
Roles, moderation, and how a contribution is credited.
Security
How to report a vulnerability.
Hire a local developer
What the work actually is, how to scope it, and how to check it — plus using an AI coding agent instead.
Community
Where the discussion lives.