PhytoMedic Platform

Technical & Commercial Proposal

Fabbi Software · March 2026

PhytoMedic Platform — Fabbi Software

We answer your 5 questions.

  1. Platform vision — What is PhytoMedic? What does V1 cover?
  2. V1 scope — Line-by-line what's in, what's out, what's future
  3. Architecture extensibility — Does V1 block future phases?
  4. Cannametrics data model — Data foundation built into V1
  5. Platform scope map — PhytoMedic ecosystem (not just DoctorHub)
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q1 + Q5

Platform Vision & Scope Map

Both questions address the same thing: what is PhytoMedic and how big is it?

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

PhytoMedic — One Ecosystem, 5 Versions

PhytoMedic is not a doctor app. It is a fully integrated medical cannabis platform connecting all stakeholders.

PhytoMedic 5-Layer Architecture

Fabbi's V1 scope = Layers 0–1 + Doctor Portal + Admin Portal

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Platform Scope Map — V1 Highlighted

Platform Scope Map — V1 Highlighted

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q2

V1 Scope — In / Out / Future

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

V1 Scope — What Fabbi Builds

Feature ✅ V1 (Fabbi builds) Future
Auth & Multi-tenant Passkeys, WebAuthn, biometric, JWT RS256 SSO/OAuth2 (V1.5)
KYC & QES Manual KYC + D-Trust registration & signing AI KYC (V1.5), SwissSign (V1.5)
Presence Check Geofence GPS + rotating QR + liveness selfie —
Patients & Appointments Search, create, consent, booking, calendar Full history (V1.5)
Prescriptions ICD-10, product select, dosage, QES-sign Templates (V1.5)
Pharmacy Routing Cannaleo + HiGreen auto-routing Fallback rules (V1.5)
Cannametrics Collect + store: catalog, prices, availability, outcomes Analytics UI (V3)
Doctor & Admin Portals Web + Mobile (iOS/Android via React Native) —
Audit Trail Hash-chained, tamper-evident, 10-year retention Regulatory export (V1.5)
Notifications Push (iOS/Android) + Web Push + Email SMS (V1.5)
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

V1 Scope — Explicitly Out

What's out Phase How it extends V1
Patient Portal V1.5 New patient role + new UI on existing V1 APIs
Pharmacy Portal V2 Pharmacy org type + inventory APIs
Cannametrics Dashboards V3 Analytics on V1 foundation data — no migration
Manufacturer Portal V4 Manufacturer org type on same model
Public Growth Layer V5 Separate marketing site, no DB coupling
E-Rezept / Gematik TI V2+ FHIR-ready architecture prepared in V1

Key principle: Adding a future phase = adding a role + a portal. No schema migration. No breaking changes.

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q3 + Q4

Architecture Extensibility & Data Foundation

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Architecture Extensibility — V1 Does Not Block V1.5 → V5

Extensibility Axis V1 Design Impact on Future
Multi-tenant org_id Every entity carries org_id from day 1 New portal = new role + new UI. No schema change.
RBAC role model DOCTOR, ADMIN, COMPLIANCE, SUPER_ADMIN Adding PATIENT, PHARMACIST = role additions only
API-first design All features exposed as REST APIs Patient Portal (V1.5) = new frontend on existing APIs
Modular Monolith Domain modules, not microservices Extractable to microservices if scale demands
Cannametrics tables V1 writes structured data from day 1 V3 = read-only analytics on existing tables
i18n scaffolded EN/DE from V1 Multi-language = content additions only
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Cannametrics — Why Data Collection Starts in V1

The problem: V3 Analytics needs historical data — prices, availability trends, routing patterns — that can only be collected over time.

The solution: V1 collects and stores Cannametrics data from Day 1. V3 reads and analyzes it. Clean separation.

Cannametrics Data Collection Pipeline

By the time V3 launches: months of historical data already collected.

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

V1 does not block any future phase.

Patient Portal (V1.5) — patient role + new UI on existing APIs ✅

Pharmacy Portal (V2) — pharmacy org type + inventory APIs ✅

Cannametrics Intelligence (V3) — analytics on V1 foundation tables ✅

Manufacturer Portal (V4) — manufacturer org type on same model ✅

Public Growth Layer (V5) — separate marketing site, no DB coupling ✅

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

What Fabbi Commits to Build in V1

✅ Fabbi builds

  • Clinical Core: multi-tenant, KYC, QES D-Trust, presence check, patient records, prescriptions, BtMG compliance, audit trail
  • Pharmacy routing: Cannaleo + HiGreen APIs, product catalog, auto-routing
  • Cannametrics foundation: 6 tables, catalog sync, snapshot jobs, price history, routing outcomes
  • Doctor Portal: iOS + Android (React Native) + Web
  • Admin Portal: user management, compliance dashboard, audit viewer
  • Shared Services: push + email notifications, encrypted doc storage

❌ Explicitly out of V1

  • Patient Portal (V1.5)
  • Pharmacy Portal (V2)
  • Cannametrics dashboards (V3)
  • Manufacturer Portal (V4)
  • Public Growth Layer (V5)
  • E-Rezept / Gematik TI (client obtains Zulassung)
  • AI/ML KYC (data model prepared, AI deferred)
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Pre-Kickoff Requirements (Client)

Before Fabbi can start, the following must be in place:

# Item Owner Deadline
1 D-Trust sandbox credentials Cannabis Ärzte (Alexander) Before kickoff
2 Cannaleo API documentation + sandbox Cannabis Ärzte / Cannaleo Week 1
3 HiGreen API documentation + sandbox Cannabis Ärzte / HiGreen Week 1
4 AWS account (Frankfurt region) setup Fabbi (with client access) Sprint 0
5 Contract signing + kickoff payment (5%) Cannabis Ärzte Before kickoff

⚠️ E-Rezept / Gematik Zulassung is a German federal certification that Cannabis Ärzte must obtain independently. Fabbi prepares FHIR-compatible architecture — integration is a V2+ engagement.

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Investment & Delivery

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Investment Summary
Scope 98 SOW items
Effort ~2,249 hours
Timeline 3 months (13 weeks, 6 sprints)
Team 1 PM · 1 BA · 2 FE · 3 BE · 1 QA (senior-level)
Subtotal $32,548
Discount (10%) −$3,255
Total $29,293

Includes CR-002 (+$2,278): Cannametrics data foundation (+120h), architecture extensibility docs (+20h), platform diagrams (+30h)

Payment terms: 5% signing · 35% architecture + base · 30% beta · 30% final acceptance

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Timeline & Team — V1 (3 months)

Sprint Duration Key Deliverables
Sprint 0 Week 0–1 Kickoff, env setup, QES sandbox integration, API access
Sprint 1 Weeks 1–3 Auth + KYC + multi-tenant + Cannametrics schema + catalog sync
Sprint 2 Weeks 3–6 Presence check + Patient mgmt + Appointments + QES signing
Sprint 3 Weeks 6–9 Prescriptions + routing + Cannametrics snapshot jobs
Sprint 4 Weeks 9–11 Admin portal + audit trail + notifications + Doctor web portal
Sprint 5 Weeks 11–13 QA, bug fixes, UAT, deployment, documentation

Sprint Gantt — V1 3-Month Delivery

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Next Steps

Cannabis Ärzte

  • Review this proposal and confirm V1 scope
  • Confirm Cannametrics data requirement
  • Initiate D-Trust sandbox credentials (pre-kickoff)
  • Align on Cannaleo + HiGreen API access (Week 1)
  • Review investment ($29,293)
  • Sign software development contract
  • 5% kickoff payment

Fabbi

  • Incorporate feedback from Alexander
  • Finalize SOW (98-item acceptance criteria)
  • Sign contract + issue invoice
  • Sprint 0 kickoff
Confidential | March 2026

Let's build PhytoMedic.

Questions? Let's talk.

Alexander · Cannabis Ärzte · Germany
Hà LTT · Fabbi Software · Vietnam

Fabbi Software · fabbi.com.vn