# ZenoXCare — Telemedicine, Discovery & Verified Reviews (Ghana)

> ZenoXCare connects patients to verified care: telemedicine, neutral provider discovery, pathway tracking, and visit-linked reviews—with tamper-evident records when payments and programs require audit-grade integrity. Built for Ghana (MoMo-native, low-bandwidth), including an installable Progressive Web App (service worker + offline shell).

## What ZenoXCare Does

ZenoXCare is a regulated digital health operating layer for Ghana. It provides:

- **Telemedicine**: Audio-first and adaptive video/async modes for real networks
- **Neutral discovery**: Rankings without pay-to-rank; clinical independence firewall
- **Verified reviews**: Feedback tied to completed care where the product supports it
- **Care pathways**: Evidence-based steps with completion tracking
- **Transparent money flows**: When funds move, trails are tamper-evident—exports for oversight
- **Mobile Money (MoMo)**: Collections and payouts with KYC and velocity controls where enabled
- **Progressive Web App**: Installable app shell, cached public routes, offline fallback (`/offline`), background sync hooks where supported

## Health Impact Credits (Non-Financial Participation Framework)

ZenoXCare features Health Impact Credits (HICs) — non-transferable, non-redeemable digital participation credits earned through verified health engagement. HICs are NOT equity, NOT investment vehicles, NOT securities, NOT tokens, and provide NO financial return.

- **Earning**: Credits earned through patient visits, preventative care, health education, vaccination tracking, chronic care adherence, data confirmations, and community volunteering
- **Tiers**: Basic Participant → Engaged → Advanced → Community Leader → Health Impact Ambassador
- **Governance**: Tier 2+ users can vote on non-financial platform priorities (feature requests, community programs, UX improvements)
- **Benefits**: Service-level only — subscription discounts, priority support, beta access, recognition badges

## Key Features

- Audit-first architecture with event-sourced ledger for finance and completion when required
- Multi-role platform: Gamers (patients/participants), Partners (healthcare facilities), Compliance officers
- Ed25519-signed ranking explanations for provable neutrality
- Real-time MoMo disbursements and collections where integrated
- Health Impact Credits with tamper-evident earning ledger (non-monetary)
- Non-financial governance voting for community priorities
- WCAG 2.1 AA/AAA accessibility compliance
- Multi-language: English (Ghana), Twi, Ga, Ewe, Hausa

## Structured data (JSON-LD, root layout)

Public HTML emits linked entities (same `@id` IRIs exposed in GET /api/public/intelligence-manifest as `jsonLdEntityIds`):

- `{baseUrl}/#organization` — Organization (publisher for discovery ItemList; healthcare graph root)
- `{baseUrl}/#website` — WebSite (`about` → SoftwareApplication; public WebPages use `isPartOf`)
- `{baseUrl}/#softwareapplication` — SoftwareApplication (health web app; `provider` → Organization)

Replace `{baseUrl}` with your deployment origin (e.g. `https://zenoxcare.com`).

## Intelligence layer (LLM crawlers & agents)

- GET /api/public/intelligence-manifest — Machine-readable manifest v1.0.5+ (`jsonLdEntityIds`, `discovery.publicMcpDiscovery` → GET /api/public/mcp-discovery): deterministic micro-router, PWA/offline-first policy, browser WebLLM (SmolLM2-360M MLC assist-only), optional `NEXT_PUBLIC_WEBLLM_MODEL_BASE_URL` CDN/Blob mirror (HF-compatible `resolve/main/` paths; see `browserOnDeviceAssist.weightsMirrorActive`), optional cloud inference when API keys exist
- GET /api/health/local-llm — Browser WebLLM status + optional OpenAI-compatible server bridge (server enrichment off unless LOCAL_LLM_ENRICHMENT_ENABLED=1)
- GET /api/public/local-model/manifest — On-device assist policy + optional Vercel Blob shard URLs + optional `browserWeightsBaseUrl` when the mirror env is set (assist-only; clinical/financial logic stays server-side)
- GET /api/public/mcp-discovery — Public MCP tool metadata (`get_intelligence_manifest` / `get_public_local_model_manifest`) with `restEquivalentGet` paths matching public REST (no secrets; authenticated full catalog: GET /api/mcp/tools)
- GET /.well-known/zenoxcare-local-model.json — Canonical single-model policy (SmolLM2-360M) + optional weights mirror env name for deployers
- GET /api/public/ai-routing?q=... — On-server micro-router maps short natural language to suggested public JSON endpoints (deterministic Jaccard profiles; engine micro_router_v1)
- POST /api/public/ai-routing — Same with JSON body `{ "query": "..." }` (max 500 chars)

## Public API Endpoints

- GET /api/public/pricing — Current pricing tiers and features
- GET /api/public/transparency — Platform transparency metrics
- GET /api/public/discovery/map — Verified facilities with coordinates for city-scoped discovery (optional ?city=slug)
- GET /api/public/discovery/ghana/location-graph — Ghana region→district administrative graph for offline pickers and hierarchy-first discovery (public, cacheable)
- GET /api/public/providers — Verified healthcare provider directory
- GET /api/health — Service health status
- GET /api/hic/balance — User HIC balance and tier (authenticated)
- GET /api/hic/history — HIC earning history (authenticated)
- GET /api/hic/tiers — Tier definitions and benefits
- GET /api/hic/leaderboard — Engagement leaderboard
- GET /api/hic/governance/proposals — Governance proposals

## Technology

- Next.js 16+ (App Router, Server Components)
- PostgreSQL with Prisma ORM, event-sourced ledger
- Kafka event streaming
- Redis caching
- 8 canonical AI agents (MCP, A2A, AG-UI, AGORA protocols)
- PWA: Web App Manifest (`/manifest.json` — shortcuts include Find care → `/g/providers?guided=1`, Contact → `/contact`), service worker (`/sw.js` precache + `/offline`), install prompt, theme color; Web Share Target opens `/g/providers?q=` with shared text

## Links

- Website: https://zenoxcare.com
- API Docs: https://zenoxcare.com/api/public/
- Contact: contact@zenoxcare.com
- Contact page (enquiries): https://zenoxcare.com/contact — POST /api/contact (rate-limited, same-origin; CSRF header required only when a session CSRF binding exists). Optional browser-side writing assist on the message field when NEXT_PUBLIC_LOCAL_ASSIST_ENGINE=1 (assist-only, non-clinical)