Country packs — templates and worked examples
A country pack is a set of 17 answers to regulatory questions specific to a country: which clinical coding systems are used, how long records must be kept, what consent text is required, and other legal and technical facts about how healthcare data is handled locally. This page lists the template for building a new pack and worked examples showing what a filled-in pack looks like. This is the free, source-available edition. See the international section for MOBLUEHQ's planned commercial markets.
Country pack template
A structured guide for answering the 17 core questions about your country's regulatory requirements. Covers coding systems, privacy regime, FHIR profiles, and more.
17 fieldsNo code needed
Read the template →Each worked example is one contributor's attempt to fill the template using publicly available sources. They are starting points for correction, not finished products. Every answer is tagged for confidence — [L] for lay knowledge, [SAFE] for standardized facts, or marked as needing local input.
Philippines (ph)
English is the working language of Philippine healthcare. This example was chosen as the first worked example because the language question is nearly free; regulatory details are the challenge.
5 fields confident12 fields open
Read the Philippines example →Mexico (mx)
Spanish-language healthcare system with two binding technical instruments in Spanish. The regulatory picture requires translation and multi-payer navigation.
Spanish primaryMulti-payer
Read the Mexico example →India (in)
A federated health system with dynamic consent architecture. This example corrects field numbering and includes field 13 (secondary use) which prior examples omitted.
Federated consentCorrected numbering
Read the India example →China (cn)
A starting point for deciding whether to proceed. Data residency law creates structural constraints. The on-premise, no-telemetry architecture is likely the only viable shape.
Residency constraintArchitectural note
Read the China example →Jamaica (jm)
A small-country example where regulatory material is less published. Demonstrates how absence of sources is itself a finding, not a gap to paper over.
Limited sourcesHonest absence
Read the Jamaica example →Kenya (ke)
English is the working language of Kenyan health IT. This example shows what maximal honesty looks like when most regulatory fields require local expertise.
5 fields confident12 fields open
Read the Kenya example →A worked example is not a validated pack ready to deploy. It is a proof that the template is usable end-to-end, and a demonstration of how many fields honestly remain open on a first pass (typically more than half). Each example shows which fields have confident answers, which have a lean or general-knowledge guess, and which are genuinely unknown and need local expertise to answer.
Read the summary section at the end of each example for an explicit count of what is ready and what is not.
Two different things get called a "pack" here, and they answer different questions. A country pack, like the worked examples above, is the set of local rules, codes, and forms the software needs — which clinical coding systems apply, how records must be retained, what consent language is required, and similar regulatory and technical facts. A language pack is narrower: it covers only the screen text a clinician or patient reads in the interface. Clinical content — codes, terminology, drug names, anything that could affect care — is never machine-translated; a language pack changes labels and prompts, not medical meaning.
Drafts are underway for five free-eligible priority countries: Pakistan, Nigeria, Bangladesh, Ethiopia, and Egypt. The interface-language drafts accompanying them are Urdu and English for Pakistan, English and Hausa for Nigeria, Bengali for Bangladesh, Amharic for Ethiopia, and Arabic for Egypt. Separate interface-language drafts are also underway for French (serving francophone countries such as the Democratic Republic of the Congo), Spanish, Filipino, Hindi, and Chinese.
All of this is draft material, not a finished or reviewed pack. As with the worked examples above, every country pack needs a local clinical and regulatory reviewer before any clinic relies on it, and every language pack needs a native-speaking reviewer before it reaches a real screen. If you are a clinician, health-IT engineer, or translator who can help review a pack for your own country or language, get in touch.