Roles, moderation, and credit
Nothing below describes infrastructure that exists yet — no public repository, forum, or issue tracker is live today. This page states the intended shape, so it can be checked against what actually ships.
- Maintainer — the company, and only once a maintainer is funded. A community edition is a commitment to build, not a release date.
- Country pack steward — one named, in-country person per jurisdiction pack.
- Reviewer — clinical, privacy, or terminology, labelled by what they review.
- Contributor — anyone filing a field report, a glossary entry, or, later, a pack.
Manead Khin, Head of blueHealthcare, holds standing authority over clinical-content and jurisdiction-pack decisions in this programme. No pack, translation, or clinical wording change — from a country steward, a reviewer, or the company itself — ships against her guidance. This is a governance fact stated for anyone deciding whether to invest time in a proposal, not a claim about her credentials; see leadership for her role and background.
A short code of conduct plus the PHI rule (see fixtures), a named moderator, and a takedown path for anything that looks like real patient data: remove it, purge it from history, notify the person who posted it, and record that it happened — without the data itself — in a public digest.
Credit is the name on the pack, and a contributors list once there's a repository to hold one. No swag programme; no leaderboard.
The intent is that pack and interface changes go through a written proposal the company answers in public — the same thread doubling as the "what we learned" record described on the roadmap page.
There is no vote and no steering committee — we are not inventing either to sound more open than the programme actually is. A disagreement over an interface or a pack detail is argued in public on the proposal thread; if it isn't resolved there, the company decides and states its reasoning in the same thread, in writing, so the disagreement and the decision are both on the record. On clinical content specifically, the standing rule above governs: Manead Khin's guidance is what a disagreement resolves against.
A proposal can be closed for scope alone, regardless of quality — that applies before the first outside contribution is ever accepted, not after one goes wrong.
All eight blueHealthcare products are in scope for the free edition in eligible countries — this isn't a subset. Two modules, AI governance and structured intake, are not included in this release; that's a scope decision made now, not a promise about when either ships.
Free use of blueOpenHealthcare is never conditional on a clinic, developer, or ministry sending us patient data in any form. The only obligation is sharing back code, configuration, and translations. See the open edition home for the fuller statement of this rule.