Evidence Hub – Technical, Product & Ministry Readiness

B1 — Technical Evidence Pack (Backend)

The Technical Evidence Pack shows what is actually built inside Elisence: engines, files, safety gates and tests, phase by phase.

• Phase-by-phase technical status across 17 phases (what is built, which files and artefacts exist).
• Safety layers including WORM audit logs, provenance exports and health / integrity checks.
• Screenshots and extracts from:
  • Real UI in running backends,
  • WORM JSONL logs,
  • pytest results (passed / skipped focus),
  • FastAPI /docs and /openapi.json views.
• For QDB, QFC, QSTP or ministries, these items can be bundled into a PDF Technical Evidence Pack for internal/legal review.

On the website, the live technical status is summarised on a dedicated page. Deeper logs and screenshots stay private and are shared only on request.

B2 — Product Evidence Pack

The Product Evidence Pack focuses on how Elisence looks and behaves for real people: citizens, clinicians, ministries and families – especially in the key phases already built.

• Links to YouTube product videos for major phases (including Diabetes – Phase 9, Women+ – Phase 7, Family – Phase 15, Global Nutrition – Phase 16, and others) via the public Videos page.
• Web pages as live evidence: Home, Phases overview, Governments & Qatar, Story, Founder and Articles – all part of the working product surface, not just design mockups.
• UI mockups for ministry dashboards, clinician panels and family / citizen apps, prepared for review sessions (kept private or under NDA).
• Storyboards for key phases (for example Phases 9, 7, 15, 16) showing scene-by-scene flows of how a citizen, a clinician and a ministry actually interact with Elisence.

Only the live website and videos are public. Full product packs (screenshots, UI mockups, storyboard PDFs) are shared privately with ministries and investors as part of the Evidence Pack.

Downloads — PDFs & Whitepapers

Some parts of the Evidence Pack must be available as downloadable PDFs: short summaries for Qatar, technical overviews and executive briefs that can be attached to applications or shared internally.

• Qatar Summary / 1-pager and related Qatar PDFs.
• High-level technical and product overviews for Elisence.
• Selected extracts from technical and product evidence for internal archives.

These documents are maintained on a dedicated downloads page and can be extended as more phases reach fully documented status.

B3 — Ministry Compatibility Evidence (Qatar & GCC Ready)

Elisence is designed from day one as a national-grade digital health platform, not just a consumer app. This section summarises how the platform fits the expectations of ministries of health, public hospitals, QDB/QFC/QSTP evaluators and GCC regulators.

• Non-diagnostic, non-prescriptive posture: Elisence does not give diagnoses, does not replace doctors, and does not issue prescriptions. It structures data, highlights risk, explains patterns and routes citizens to appropriate care.
• Built for ministries, hospitals and schools: The platform is designed so that a Ministry of Health, public hospital network, school system or national programme can safely deploy it as part of their own digital health ecosystem — not as a standalone foreign app.
• Data-sovereignty & hosting: Architecture is compatible with Qatar and wider GCC data-sovereignty expectations: data can be hosted inside the country or approved GCC regions, with clear separation between citizen data, analytics and research exports.
• Zero-Trust, consent-first, privacy-by-design: All sensitive actions use strict headers, passports and role-based access. Every module follows Zero-Trust principles, with explicit consent, least-privilege access and full audit trails (including WORM logs).
• Global regulatory alignment (design level): The governance model and evidence pack are aligned with the logic of NHS DCB0129/0160, EU MDR/MDCG, US FDA CDS and GCC data-protection / PDPL frameworks — always within a non-diagnostic decision-support boundary.
• Automatic country-aware behaviour: Elisence can recognise the user’s country/region and route them to the correct safety rules, disclaimers and policy mappings for that jurisdiction (for example, Qatar vs. UK vs. EU), while keeping one shared technical core.
• Five-language backbone: Core content and engines are designed around a 5-language baseline — English, Farsi, Arabic, Turkish, Romanian — suitable for GCC, diaspora communities and European partners, with RTL support for Arabic and Farsi.
• BBVP standard (Build-Back-Verify-Prove): Every phase follows an internal governance standard: engines are built, then verified with tests and WORM logs, and finally proven with manifests and SHA-256 evidence packs before being declared “Done”.

For QDB, QFC, QSTP and ministries, this means Elisence is already operating as a national digital health infrastructure layer, not just a prototype.

Official sector positioning for Qatar & GCC:

• HealthTech
• Digital Health
• AI & Data Intelligence
• Education / Behaviour Change (EdTech)
• National Digital Platforms

A dedicated Ministry Compatibility Pack (B3) can be shared privately with Qatar or GCC authorities on request, including policy mappings, data-flow diagrams, safety boundaries and governance documentation.

Qatar Export Kit – How This Evidence Is Used

In the A→Z roadmap for Qatar, this Evidence Hub feeds directly into the Final Qatar Preparation Pack (Export Kit) that can be submitted to QDB, QFC, QSTP or similar programmes.

• Qatar 1-pager and “Why Qatar?” page.
• Qatar company registration summary (QFC / QDB / QSTP path).
• Full Evidence Pack (B1 technical + B2 product + B3 ministry compatibility).
• Live website links and YouTube product videos.
• Contact details and executive summary PDF.
• Two Qatar Pitch Decks (ministry version + investor version) prepared from the same evidence base.

Once sections A–E of the roadmap are complete, this export kit can be assembled quickly from the verified website, engines and PDFs described on this page.