A trusted local service
Patients are told to allow up to five days. They may phone, visit to check or collect, or wait for delivery. These are Jon’s reported observations.
Review edition · 9 October 2026Your prescription.
Your prescription.
Your pharmacy.
A clearer connection.
A Mossley-branded patient app that brings prescription progress, collection and delivery together—building on the service patients already value.
Independent proposal prepared with Jon. For discussion with pharmacy staff and owners; not a final specification or an implemented service.
Make progress visible
One Mossley experience for current status, repeats, history, authorised family access, collection and delivery updates.
Keep existing work familiar
Agree data sources and staff actions first. Minimise disruption to pharmacy software. Prescription details remain in authorised systems.
Explore the proposed experience
A patient app, made tangible.
Click through the concepts. Every name, medicine, address, reference, time and count below is fictional. No request reaches a pharmacy.
Information boundaries
Patient medicine details are not shown in the driver concept. Same-address grouping does not give one person access to another’s prescription.
9:41Fictional app concept
+ Mossley PharmacyClickable review mockup · no live patient data or connected services
From preparation to handover
Useful choices at the right moment.
Delivery responses
Choices become available after the driver scans the prescription. Earlier availability is a question for PharmDel and pharmacy staff.
- Suggested windows or custom availability.
- Request available items now or wait for the remainder, where partial-supply information is available.
- Request a combined household delivery with the relevant authorisations.
A round that can adapt
Late replies are assessed against remaining stops, staff priorities and time windows. Driver Assist proposes a revised order for voice confirmation.
Approved changes update the patient’s estimated arrival window. Normal progress continues to refine the estimate. Conflicting requests must be surfaced rather than promised silently.
Collection made simpler
Staff mark the prescription ready. The patient then gives an expected collection time and identifies themselves or an authorised nominee.
A collection code or QR concept supports a quicker handover. Staff can scan or confirm with a button, under an agreed pharmacy process.
For patients without the app
Opted-in, one-way text updates remain available. Availability and hold requests can be made by phoning the pharmacy. Staff use the existing phone call to the driver in the initial pilot. Two-way SMS is deferred unless straightforward and affordable.
Round assistant, not a replacement
PharmDel remains the main record.
Jon’s preferred pilot uses his own dash-mounted iPhone or Android as a second device. Driver Assist organises the round and proposes changes; PharmDel tracks delivery outcomes.
Driver Assist · fictional round
Next three stops
45 stops loaded · example progress 18 / 45
Next · Stop 19 · Demo address A
12:30–12:50 · 3 bags · 2 recipients
Confirmed household group · allow 4 minutes at stop
Then · Stop 20 · Demo address B
6 minutes’ travel · 2 minutes at stop
Then · Surgery A
Staff priority · before 13:00 · outgoing paperwork
Patient response: please hold delivery
Proposed: skip Stop 20; add its package to the pharmacy-return checklist. Preserve the surgery deadline.
Voice is simulated by buttons here. No microphone, navigation, tracking or PharmDel connection is active.
Pharmacy return checklist
No additional returns in this example yet.
Realistic round estimates
Allow for travel and delivery time. Measure arrival-to-completion time automatically where a reliable signal can be agreed.
- Use average stop time to refine duration and ETAs.
- Voice explanation for extra interaction, without confidential conversation details.
- Remember editable extra-time allowances by address.
- Report round duration, stop times and estimate accuracy if required.
Local knowledge matters
Jon reports that PharmDel optimisation is useful; experienced drivers adjust for school closing times, nearby outstanding stops and local knowledge.
A future guide could help new and covering drivers with round tips and approved location instructions.
Jon’s first priority
Get the prescription to the patient; if that cannot be done appropriately, return it to the pharmacy. Do not leave it in a potentially unsafe place. Pharmacy staff must approve the operational instructions.
Before the round
One regular surgery today; support two or three. Staff set urgency and any deadline. Other surgery stops fit the round conveniently.
At the end of the round
The pharmacy receives the completed checklist. The future fleet company is not a dependency.
Connection needs agreement
The companion cannot simply assume route access. The separate PharmDel collaboration proposal asks how to connect a round-refining layer and offers a native enhancement as the alternative.
A small staff convenience layer to explore
Collections due today.
Fictional staff concept
Prepared collections
| Reference | Arrival | Collector | Action |
|---|---|---|---|
| DEMO-C01 | 14:00 | Patient | |
| DEMO-C02 | 15:15 | Authorised nominee |
Fit the staff workflow first
A proposed screen alongside existing systems could show ready prescriptions, planned arrivals and authorised collectors.
Jon understands prescriptions are processed and stored before collection; the current collection recording system is unconfirmed. This layer’s necessity and any PharmDel connection must be reviewed with staff.
- Who supplies status and partial-supply information?
- What identity and nominee checks are sufficient?
- Where is the authoritative collection outcome recorded?
- How should repeat requests reach the existing process?
A familiar front door
The website, centred on patients.
Keep Mossley’s services and local identity. Make prescription access and next steps clearer, with the proposed Mossley app as the destination.
Services & support
Clear access to existing pharmacy services, approved advice and help without a smartphone.
Community health board
Local health notices and community updates. Owners decide contributors, approval and rollout timing.
Commerce
Product range is an owner decision, potentially informed by a patient survey. Explore nopCommerce with its built-in rewards, subject to validating the intended setup.
Delivery credits
Retained as a deferred proposal. No reward-to-delivery redemption is proposed for the initial stage. Payment and charging rules require owner review.
Future accessibility
Voice access across general patient-app functions, with confirmation before changes. Accessible text, controls and phone support belong in the initial design.
Reference reviewed: current Mossley website, 9 October 2026. It already presents services, contact and BeWell access. This concept explores a Mossley-specific app; it does not claim an existing replacement or migration.
Review before implementation01 · REVIEW 02 · PILOT PROPOSAL 03 · AGREED INTERFACE 04 · LATER STUDY
A practical path forward.
Patient & staff input
Review status, collection, repeats and permissions. Identify data sources and agree pharmacy processes.
Patient journeys
Validate a bounded patient experience with fictional scenarios before selecting a live pilot.
Driver Assist
Explore the second-device pilot with PharmDel, including voice approval and both checklists.
Delivery company
Test whether separate shifts and external work can cover fleet costs and reduce pharmacy charges.
Open viability workspaceThis review edition is not the final stakeholder proposal. Live capability, patient data, agreements, pricing and profitability remain to be validated.
Build on what already works
Share an idea.
What would make deliveries, collections or patient communication even easier?
We want input from Mossley staff, owners, patients and drivers. Tell us what happens today, what you would add and how it would help.
No confidential details: use fictional examples and leave out patient names, addresses and medicines.
This page prepares a feedback summary for you to copy or download and send to Jon through your usual channel. It does not send or store feedback centrally.