ScriptPath journey overview banner ScriptPath journey overview banner

The ScriptPath platform

A persistent coordination state from patient intent to pharmacy fulfilment.

ScriptPath connects otherwise separate prescription, patient, and pharmacy workflows.

It coordinates decision and status transitions while keeping dispensing authority inside the pharmacy.

Orchestration lifecycle

1

Intent received

A patient or authorised access surface initiates a fulfilment journey using a supported prescription pathway.

2

Options matched

ScriptPath identifies suitable participating pharmacy options using configured constraints and minimum-necessary pharmacy signals.

3

Patient chooses

The patient retains control of pharmacy selection and whether to continue.

Reservation and response lifecycle

4

Reservation requested

ScriptPath creates a time-bound coordination state and sends the request through an appropriate pharmacy workflow.

5

Pharmacy responds

The pharmacy accepts, declines, or provides an appropriate fulfilment response. Acceptance is not a dispense decision.

6

Status continues

Relevant progress is communicated without moving the authoritative dispensing record out of the pharmacy system.

Completion and recovery

The coordination state records completion, and supports expiry, decline, and patient-controlled recovery without discarding the whole journey.

Built around trust

ScriptPath keeps communication clear while pharmacists remain in control of dispensing and clinical decisions. Regulatory-aware matching helps reduce unsupported request pathways.

ScriptPath compliance and trust framework in light modeScriptPath compliance and trust framework in dark mode

Explore the participant pathways