Prescribing model
Prescribers stay with the clinic
Each organisation’s services are delivered by its own prescribers. Pathlyn does not supply prescribers to a clinic, and does not market a supplied prescriber network before that capability exists.
For pharmacy groups
Built for pharmacy groups: structured requests, with the context your pharmacists need
Clinics on Pathlyn send orders only after clinical approval, verified payment and prescription authorisation — to whichever fulfilment integration your organisation configures.
- Approved
- Paid
- Authorised
- Sent by a person
Structured handoff
Nothing dispatches until a person sends it
Pathlyn prepares an order only after clinical approval, verified payment and prescription authorisation are all recorded. Authorised operations staff send it once — dispatch is never described as automatic.
- Gate 1
Clinical approval
Recorded once by a credentialled prescriber.
- Gate 2
Verified payment
Taken only after approval, creating one paid order.
- Gate 3
Prescription authorised
A separate, audited step by a verified prescriber.
- Gate 4
Explicit staff send
Authorised operations staff send the order once.
- Handoff
Your fulfilment integration
Configured per organisation.
Operating model
Clear about what Pathlyn provides
Locations
No branch network required to get started
A pharmacy group is not blocked by a missing branch model. Organisation locations remain a later-phase concern — Pathlyn does not promise branch management, in-pharmacy appointments, or a supplied prescriber network today.
Governance
Built for multi-organisation operations
Multiple organisation workspaces
Every organisation on Pathlyn is isolated — staff, patients, and data never cross a tenant boundary.
Controlled service templates
Services are configured through Service Studio, not built one-off per clinic.
Prescriber credentials, verified
A prescriber must hold a currently-verified credential before they can review or sign a case.
Operations exception visibility
Payment, prescription, and fulfilment issues appear in one operations view per organisation.
Talk through your fulfilment integration
Fulfilment connects through a configurable integration layer. We name a fulfilment partner only after we have verified and approved that relationship publicly.