How it works
One journey, six responsible parties, no ambiguity about who does what
Clinical approval always precedes payment. Prescription authorisation is separate from payment. Operations staff explicitly send every order to fulfilment — nothing dispatches automatically.
End-to-end journey
From branded sign-in to repeat care
Eight steps, in the order the product enforces them.
- Approval before paymentNo checkout until a prescriber records a decision.
- Signing is its own stepA prescription is authorised separately, by a verified prescriber.
- A person sends every orderNothing reaches the pharmacy without an explicit staff send.
- Clinic
Brand
The patient sees their clinic’s own brand on a Pathlyn tenant host — never a generic Pathlyn-branded page.
- Patient
Patient
The patient signs in or registers for the programme their clinic invited them to.
- Patient
Assessment
They complete the clinic’s configured assessment; routing flags are stored separately from clinical approval.
- Prescriber
Clinical review
Credentialled staff review the case in a role-scoped queue and record an immutable clinical decision.
- Patient
Payment
Checkout runs only after clinical approval — payment does not precede clinical review. Approval alone creates no order or prescription.
- Prescriber
Prescription
The prescription is created from the paid, approved order and waits for the prescriber’s authorisation — a separate, audited step from approval.
- Operations & pharmacy
Fulfilment
Authorised operations staff send the order once; the fulfilment partner dispatches it and tracking appears when available.
- Patient & prescriber
Repeat care
Repeat assessments and subscriptions follow the same clinical gates as the first request, when configured.
Fulfilment dispatch is manual: authorised operations staff send once. Pathlyn does not describe partner dispatch as automatic.
Who does what
Six parties, each with one clear responsibility
The same journey, read by role — useful when a clinic or pharmacy group is mapping Pathlyn onto its own operating model.
Patient
Completes the assessment, pays after approval, and receives their order and follow-up requests.
Clinic / operations
Owns clinical policy and prescriber credentialing, and explicitly authorises each send to fulfilment.
Prescriber
Reviews the case, records the clinical decision, and signs the prescription.
Pathlyn platform
Runs the software: portals, queues, payments, records, and the audit trail behind every step.
Payment provider
Processes checkout after clinical approval, through the organisation’s own connected account.
Fulfilment provider
Dispatches the order once operations staff send it, and reports status back.
See this journey running on your own service
Book a demo and we will walk through assessment, review, prescribing and fulfilment together.