> For the complete documentation index, see [llms.txt](https://docs.oomus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oomus.org/introduction.md).

# Introduction

**Sovereign digital public health infrastructure for national programs in Africa and in low-resource countries.**

> **Version** : 8.0 · **Date** : 2026-06-14 · **Status** : Production

***

## Welcome to the official documentation

Oomus CampaignID is an Enterprise GovTech SaaS platform designed for the generation, distribution, verification, and governance of secure digital health ID cards. It is built on a sovereign digital identity MPI (Master Patient Index), HL7 FHIR R4 interoperable, and designed to operate in low-connectivity environments.

***

## What Oomus CampaignID does

Oomus CampaignID enables national health programs and humanitarian organizations to:

* **Generate** secure digital health cards at scale
* **Distribute** cards via WhatsApp, SMS, and Google Wallet from a unified interface
* **Verify** the authenticity of cards offline — no Internet connection required
* **Deduplicate** identities automatically thanks to the probabilistic MPI engine
* **Synchronize** data from DHIS2 Tracker in real time
* **Govern** access, quotas, and approvals via an institutional RBAC system
* **Issue** Sovereign Wallet Passes — signed digital passes, syncable offline
* **Produce** physical PVC cards in two print qualities
* **Bill** with full traceability — every debit automatically generates a signed formal invoice
* **Access** sovereign identity from the mobile app **OOMUS Wallet** (iOS + Android) — bilingual FR/EN
* **Verify** their identity with the 5-step KYC wizard (ID card + biometric selfie) — MPI trust score updated in real time
* **View** the Sovereign Identity Register — IAL levels 0–3, unlocked features, cryptographic integrity

***

## Key capabilities

* **Card Studio** — Visual editor with 11 card templates, real-time preview, export, 300/450/600 DPI options
* **Sovereign digital identities** — 1 citizen = 1 MPI digital health identifier, cross-program, lifetime
* **DHIS2 integration** — Automatic synchronization, attribute mapping, generation from enrollments
* **Multichannel distribution** — WhatsApp (Meta Graph API), SMS (Orange API), Google Wallet
* **Offline verification** — Static portal, browser-side cryptography, multilingual (FR/EN/WO)
* **Sovereign Wallet** — Signed digital passes, offline bundle, device sync, audited revocation
* **Financial simulation** — Pro forma estimate, admin approval workflow, PDF/Excel generation
* **Physical PVC cards** — Standard and Industrial Offset, tracking timeline
* **Billing Infrastructure** — Centralized accounting ledger with signed invoices and immutable audit
* **Operational dashboard** — Real-time KPIs, advanced analytics, alerts
* **Enterprise security** — 2FA TOTP, brute-force protection, JTI token revocation, institutional RBAC
* **Bilingual mobile app** — OOMUS Wallet React Native / Expo SDK 54 — FR/EN, biometrics, offline-first
* **5-step KYC wizard** — ID card verification + selfie, MPI trust score propagated in real time via WebSocket
* **Real-time Citizen Wallet** — live activity, `ACTION_LABELS` human labels, filters, animated toasts
* **Sovereign Identity Register** — IAL levels 0–3, cryptographic fingerprint, error reporting

***

## Who it's for

| Target audience              | Typical use case                                          |
| ---------------------------- | --------------------------------------------------------- |
| National health programs     | Vaccination, malaria, nutrition, HIV/PMTCT                |
| Ministries of Health         | Universal health insurance card, national health identity |
| Humanitarian agencies & NGOs | Refugee identification, mosquito net distribution         |
| Government agencies          | National identity linked to health services               |
| Agricultural health programs | Farmer card / rural health                                |

***

## Available plans

| Plan                        | Identities/month | SMS/month | WhatsApp/month |
| --------------------------- | ---------------- | --------- | -------------- |
| **Essential**               | 10 000           | 50 000    | 10 000         |
| **Regional Command**        | 100 000          | 250 000   | 100 000        |
| **National Infrastructure** | 1 000 000        | 3 000 000 | 1 000 000      |
| **Sovereign Cloud**         | Unlimited        | Unlimited | Unlimited      |

***

## Tech stack

| Component            | Technology                                                        |
| -------------------- | ----------------------------------------------------------------- |
| Frontend             | Next.js + React + TypeScript                                      |
| Backend              | FastAPI + Python + SQLAlchemy                                     |
| Database             | PostgreSQL 16                                                     |
| Task queues          | Celery + Redis                                                    |
| File storage         | S3-compatible                                                     |
| Interoperability     | HL7 FHIR R4                                                       |
| **Mobile app**       | React Native 0.81.5 · Expo SDK 54 · TypeScript · i18next (FR/EN)  |
| **Mobile real-time** | WebSocket + Redis pubsub · SyncContext · `publish_wallet_event()` |
| **KYC Trust Bridge** | `kyc_trust_bridge.py` · `MpiTrustScore` · `MpiVerificationEvent`  |

***

## Start now

Go to [Quick start](/getting-started/quick-start.md) to create your first program and generate your first cards.

See the [Plans & Features](/getting-started/plans-and-pricing.md) to choose the plan suited to your program.

***

***

## Mobile app — OOMUS Wallet

The mobile app **OOMUS Wallet** (React Native / Expo SDK 54) allows every citizen to access their sovereign MPI identity, their health passes, and control the sharing of their data from their phone.

**Key features:**

* SMS OTP login → 6-digit PIN → biometrics (Face ID / Fingerprint)
* Sovereign identity card `SovereignCard` with HMAC-SHA256 QR
* **5-step KYC wizard** — ID card + biometric selfie, MPI score updated in real time after completion
* **Citizen Wallet** — WebSocket live activity, `ACTION_LABELS` human labels, All/Wallet/Health/Identity filters
* **Sovereign Identity Register** — IAL levels 0–3, cryptographic fingerprint, error reporting, unlocked services
* Management of health passes (vaccination, insurance, prescription…) with overlay `IAL level {n} required`
* Sharing consents with 2-step GrantModal
* Complete activity log — human labels, fallback `'System event'`
* Health insurance module — coverage, procedure verification, history
* **Bilingual FR/EN** — language selector in Settings, AsyncStorage persistence
* Offline mode (SyncContext) — passes and identity cached, auto-sync when network returns

**Getting started:**

```bash
cd mobile
npm install
npx expo start          # Expo Go QR code
npx expo run:ios        # iOS simulator
npx expo run:android    # Android emulator
```

**Environment variables:**

```bash
EXPO_PUBLIC_API_URL=https://api.oomus.org   # backend URL
```

***

> **Oomus CampaignID** — *One identity. One citizen. One sovereign health system.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.oomus.org/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
