PhytoMedic Platform

Fabbi's Response to Your Platform Vision

Fabbi Software · March 22, 2026 · v6 Proposal

PhytoMedic Platform — Fabbi Software

We answer your 5 questions.

  1. Platform vision — What is PhytoMedic? What does V1 cover?
  2. In / Out / Future — Line-by-line V1 vs V1.5 vs V2+
  3. Architecture extensibility — Does V1 block future phases?
  4. Cannametrics data model — Schema/ERD for data foundation in V1
  5. Platform organigram — PhytoMedic scope map (not DoctorHub)
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q1 + Q5

PhytoMedic — Platform Vision & Organigram

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 software 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 Organigram — V1 Scope Map

Platform Organigram — V1 Scope Map

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q2

V1 Scope — In / Out / Future

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

V1 Scope: In / Out / Future

Feature Area ✅ V1 (Fabbi) 🕐 V1.5 🔮 V2+
Infrastructure & Auth Multi-tenant, Passkeys/WebAuthn, biometric, JWT RS256 SSO/OAuth2 —
KYC Manual upload, admin review, approve/reject AI-assisted KYC —
QES D-Trust registration + in-app signing SwissSign fallback —
Presence Check Geofence GPS + rotating QR + liveness selfie — —
Patients Search, create, consent, contraindications Full therapy history —
Appointments Web booking + doctor calendar Full scheduling engine —
Prescriptions ICD-10, product select, dosage, QES-sign, history Template library —
Pharmacy Routing Auto-route Cannaleo + HiGreen APIs Fallback rules —
Cannametrics Collect + store: catalog, availability, prices, outcomes — V3 analytics
Admin Portal User mgmt, compliance dashboard, audit viewer — —
Audit Trail Hash-chained, tamper-evident, 10-year retention Regulatory export —
Notifications Push (iOS/Android) + Web Push + Email SMS —
Doctor Portal Full web + mobile (iOS + Android) — —
Patient Portal ❌ NOT V1 ✅ V1.5 —
Pharmacy Portal ❌ NOT V1 ❌ ✅ V2
Cannametrics Dashboards ❌ NOT V1 (data only) ❌ ✅ V3
E-Rezept/Gematik TI ❌ Out of V1 — FHIR-ready arch prepared ❌ ✅ V2+
Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Q3

Architecture Extensibility — V1 Does Not Block Future Phases

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Architecture Extensibility Confirmation

Short answer: V1 does NOT block V1.5 → V5.

Here is why, technically:

Extensibility Axis V1 Design Impact on Future
Multi-tenant org_id Every entity carries org_id from day 1 Adding Patient/Pharmacy portal = new role + new UI. No schema migration.
RBAC role model DOCTOR, ADMIN, COMPLIANCE, SUPER_ADMIN Adding PATIENT, PHARMACIST, MANUFACTURER = role + permission additions only
API-first design All features = internal REST APIs Patient Portal (V1.5) = new frontend calling existing V1 APIs
Modular Monolith Domain modules (not microservices) Extractable to microservices post-V1 if scale demands
Cannametrics tables V1 writes structured data from day 1 V3 Intelligence = read-only analytics on existing tables. No migration.
i18n scaffolded EN/DE from V1 Multi-language = content additions, no architecture change

Architecture Extensibility — V1→V5 Timeline

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

Q4

Cannametrics Data Foundation — Schema in V1

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Why Cannametrics Data Must Start in V1

The problem: V3 Analytics requires 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

Cannametrics Data Model — 6 Foundation Tables (V1)

Cannametrics ERD — 6 Foundation Tables

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Cannametrics — V3 Readiness Statement

When Cannametrics Intelligence (V3) is built, it reads these V1 tables directly — zero migration required:

V1 Table V3 Analytics Use Case
price_history Price trend analysis, market pricing intelligence
pharmacy_availability_snapshots Supply analytics, pharmacy reliability
routing_outcomes Routing performance, pharmacy partner scoring
prescription_product_data Demand by product, strain popularity (anonymized)
product_catalog Product catalog completeness, coverage gaps
pharmacy_product_availability Real-time supply dashboard (V3 live feed)

Cannametrics catalog sync runs every 15 minutes (configurable via CATALOG_SYNC_INTERVAL_MINUTES). Fine-tuning based on Cannaleo/HiGreen API rate limits — Sprint 1 discovery.

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Fabbi's V1 Commitment

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

What Fabbi Commits to Build in V1

✅ Fabbi builds in V1

  • 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 data foundation: all 6 tables, catalog sync service, snapshot jobs, price history, routing outcomes, V3 read API
  • Doctor Portal: iOS + Android (React Native) + Web (responsive)
  • Admin Portal: user management, compliance dashboard, audit viewer
  • Shared Services: notifications (push + email), encrypted doc storage
  • Architecture extensibility docs: formal V1→V5 extensibility statement

❌ Explicitly out of V1

  • Patient Portal (V1.5 — separate engagement)
  • Pharmacy Portal (V2)
  • Cannametrics dashboards / analytics (V3)
  • Manufacturer Portal (V4)
  • Public Growth Layer / website (V5)
  • E-Rezept / Gematik TI (client obtains Zulassung independently)
  • AI/ML KYC (FHIR-ready data model prepared, AI decision 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 SwissSign sandbox agreement Cannabis Ärzte (Alexander) Before kickoff
2 D-Trust sandbox credentials Cannabis Ärzte (Alexander) Before kickoff
3 Cannaleo API documentation + sandbox Cannabis Ärzte / Cannaleo Week 1
4 HiGreen API documentation + sandbox Cannabis Ärzte / HiGreen Week 1
5 AWS account (Frankfurt region) setup Fabbi (with client access) Sprint 0
6 Contract signing + 5% kickoff payment Cannabis Ärzte Before kickoff

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

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Quotation v6

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Quotation Summary — v6.0

Component v5.1 (baseline) Delta (CR-002) v6.0
Total SOW items 88 items +10 items 98 items
Total hours 2,684h +170h ~2,854h
Timeline 3 months — 3 months
Team 8 devs + PM + BA + QA — 8 devs + PM + BA + QA
Subtotal $39,940 +$2,524 $42,464
Discount (10%) -$3,994 -$252 -$4,246
Total $35,946 +$2,272 $38,218

CR-002 delta (+$2,272) covers:

  • Cannametrics data foundation: +120h (7 SOW items)
  • Architecture extensibility documentation: +20h
  • PhytoMedic platform diagram + v6 proposal: +30h

Payment terms: 5% signing · 35% arch+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

Team composition (8 developers, senior-level — no juniors per Jan 2026 requirement):

  • 1 PM · 1 BA · 2 Frontend devs · 3 Backend devs · 1 QA

Cannametrics data foundation (+120h) built by 1 backend dev in Sprints 1–3 as a parallel track. No timeline impact on the critical path.

Sprint Gantt — V1 3-Month Delivery

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Next Steps

Confidential | March 2026
PhytoMedic Platform — Fabbi Software

Next Steps

For Cannabis Ärzte

  • [ ] Review this v6 proposal
  • [ ] Confirm V1 scope and Cannametrics requirement
  • [ ] Initiate SwissSign sandbox agreement (pre-kickoff dependency)
  • [ ] Align on Cannaleo + HiGreen API access (Week 1)
  • [ ] Review updated quotation ($38,218 — delta +$2,272 for CR-002)
  • [ ] Sign software development contract
  • [ ] 5% kickoff payment

For Fabbi

  • [ ] Incorporate feedback from Alexander
  • [ ] Finalize SOW v6 (98-item list)
  • [ ] Update acceptance criteria (Cannametrics items)
  • [ ] Sign contract + issue invoice
  • [ ] Sprint 0 kickoff
Confidential | March 2026

Let's build PhytoMedic.

Questions? Let's talk.

PhytoMedic Platform — Fabbi Software

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

Fabbi Software · fabbi.com.vn
Confidential — March 22, 2026

Confidential | March 2026