System Overview

Platform shape

The platform consists of three major systems with intentionally different responsibilities.

LoveMyLife

Consumer-facing channel for:

• browsing products and services
• booking appointments
• completing consultation forms
• uploading prescriptions
• providing payment and delivery information
• viewing order and consultation status

Phensys

Clinical and orchestration core for:

• patient clinical record
• doctor and prescriber workflow
• consultation outcomes
• prescription creation and status
• routing requests to pharmacy or fulfilment providers
• managing high-level operational state across systems

Pharmetra

Pharmacy operations platform for:

• dispensing workflow
• stock management
• wholesaler ordering
• packing and labelling
• postage and dispatch
• fulfilment audit trail

Design objective

The architecture should support:

• multi-tenant provider routing
• white-label patient journeys
• multiple pharmacy and supplier backends
• clean certification and audit narratives
• future replacement of any single channel or provider

Canonical flow

LoveMyLife or another channel
            ↓
          Phensys
            ↓
   Provider selection and routing
            ↓
     Pharmetra or another backend

Key rule

No patient-facing channel should become the source of truth for clinical or pharmacy operations.

That means:

• LoveMyLife captures intent and displays status.
• Phensys owns orchestration truth.
• Pharmetra owns pharmacy execution truth.