Phensys Platform Documentation¶
This documentation site is the canonical internal reference for the platform boundaries between:
- Phensys — clinical records, consultations, prescribing workflow, and orchestration
- Pharmetra — dispensing, stock control, fulfilment, labelling, wholesaler ordering, and dispatch
- LoveMyLife — patient-facing product browsing, booking, checkout, status display, and communications
Core principle¶
The platform should preserve a clear separation of concerns:
- LoveMyLife is the channel and customer experience layer.
- Phensys is the clinical and workflow orchestration layer.
- Pharmetra is the pharmacy operations layer.
Recommended orchestration model¶
Patient / LoveMyLife
↓
Phensys
↓
Provider abstraction layer
↓
Pharmetra / other pharmacy SaaS / manual workflow / supplier
What belongs where¶
| Area | Primary owner |
|---|---|
| Product browsing and UX | LoveMyLife |
| Consultation workflow | Phensys |
| Prescription record and status | Phensys |
| Dispensing and stock | Pharmetra |
| Delivery and dispatch statuses | Pharmetra |
| Patient communications | LoveMyLife, triggered by authoritative status changes |
| Tenant-level provider routing | Phensys |
Documentation structure¶
- Architecture covers boundaries, integration patterns, and events.
- Systems documents each product's responsibility.
- Workflows describes end-to-end operational flows.
- Compliance captures audit and traceability expectations.
- Decisions stores architecture decision records.
Audience¶
This site is intended for:
- founders and product owners
- engineers and architects
- compliance and operations staff
- auditors reviewing workflow ownership and traceability