VANTRO Webster · Discussion edition · 17 October 2026
VANTRO·
Webster operations
Design proposal · Version 1
From calendar to accountable workflow

Every pack.
Every handover.
A clear next step.

A separate Webster workspace that gives the manager advance visibility, gives staff focused queues, and preserves a clear record for every patient.

The operating promise

Know what is due, who owns it, what is blocking it, and whether the patient received the correct checked pack.

Executive overview

Plan this week and next week, distribute packing and checking tasks, and act before a supply deadline is missed.

Patient continuity

Keep pack coverage, medication-list versions, communications, holds and collection evidence together.

Separate demo first. A standalone Cloudflare-ready theme uses fictional patients. It does not connect to the current VANTRO patient database or change the live dispensing workflow.

This is a proposed product design, not a clinically ready service or a guarantee against error. Pharmacist judgment, pharmacy procedures and validated operational controls remain essential. All example names, workload values and dates in the demo are fictional.

VANTRO· WEBSTER
Interface system
01 · Screens and responsibilities

One shared record.
Focused views for each role.

The proposed visual direction combines a navy navigation rail, calm mint accents, generous spacing and clear status chips. Persistent patient identity and pack coverage stay visible during every task.

ScreenWhat the user sees and does
Manager overviewThis-week / next-week forecast; unassigned, packing, checking, ready and overdue counts; blockers; daily pack counts and current stages. Assign or reassign both packer and checker.
Calendar & workloadDay/week view with separate preparation, check and collection deadlines. Move work within a permitted window; see the affected packs and assignments before confirming.
Packing queue“My work” ordered by deadline and priority. Open a pack, review approved instructions, record completion or a blocker. Show the medication-list version used.
Pharmacist checkingWaiting, urgent and returned-for-rework queues. Approve a specific pack version or return it with a reason. Changed content invalidates earlier approval.
Collection deskSearch patient, confirm identity, select exact checked packs, record collector and handover evidence. Unchecked, superseded or held packs cannot be released.
Patient workspaceOverview; pack history; communication timeline; medication lists; holds; collection history. Pin current risks and outstanding actions above routine history.
Reports & settingsWorkload, exceptions, collection follow-up and list reviews. Configure staff, review interval, alert owners and notification recipients.

Manager

Allocates work and monitors completion. Manager access alone does not grant clinical approval or hold-release authority.

Packer / student

Works within training and pharmacy supervision arrangements. Can record packing progress and escalate uncertainty; cannot approve a clinical change.

Checking pharmacist

Owns medication reconciliation, pack approval, clinical hold release and documented exceptions.

Collection staff

Records handover of eligible packs and exceptions. Cannot convert an unchecked pack into a ready pack.

Actor identity comes from the signed-in account, not a free-text staff name. Assignment and actual completion are recorded separately.

VANTRO· WEBSTER
Pack lifecycle
02 · State and release controls

Completion means an
attributable action.

Every physical pack has a unique identifier, coverage dates, content version and lifecycle. A patient can have several packs in different states; one patient-level checkbox cannot represent them all.

TransitionAction / ownerRequired result
Planned → AssignedManager assigns staffPacker, checking pharmacist and deadlines are visible.
Assigned → PackingPacker starts workCurrent approved instructions acknowledged; blockers checked.
Packing → Awaiting checkPacker completesSigned-in actor, server time, pack version and completion evidence saved.
Awaiting check → ReworkPharmacist returnsReason and responsible packer recorded; release remains blocked.
Rework → Awaiting checkPacker correctsCorrection history retained; complete new check required.
Awaiting check → ReadyPharmacist approvesApproval bound to exact pack and medication-list versions. Checker differs from packer under the proposed policy.
Ready → CollectedHandover staff confirmsExact packs, collector, signature/evidence, date, time and staff actor recorded.
Active → HeldAuthorised staff records holdWork/release blocked; reason, source, affected packs and review owner visible.
Held → Review requiredReview date arrivesAlert created; no automatic packing restart or release.
Approved content changesPharmacist assesses impactAffected packs become blocked, superseded or rework-required. Previous check cannot authorise changed contents.
Hold is a control, not just a label. Record the previous stage and hold scope. A pharmacist explicitly resolves the hold and decides the appropriate stage after reviewing current instructions.

Collected packs remain historical records. A later medication change creates an urgent patient-contact and pack-reconciliation task; the system must not silently rewrite what was supplied.

Cancellation, disposal and replacement are separate recorded outcomes with reasons and linked pack IDs. Historical events are never erased to make the dashboard look complete.

VANTRO· WEBSTER
Scheduling model
03 · Supply dates before calendar convenience

Plan from pack coverage,
not collection time.

Collection is evidence of handover. The next cycle is anchored to the intended period covered by the medicine pack, then confirmed against current clinical instructions and any changes.

Date / fieldMeaning
Coverage start and endFirst and last intended medication dates; include dose-session boundaries where partial days matter.
Preparation targetPlanned packing date, derived from coverage and configurable lead time.
Checking deadlineTime available for independent checking and corrections before handover.
Expected collectionAgreed pickup/delivery deadline; distinguish it from actual collection.
Actual completion / collectionImmutable event times for work performed and packs physically handed over.
Hold review / change effectiveWhen to review a hold; when approved medication instructions begin to apply.

Fictional weekly example

A pack covers 19–25 October and is collected on 17 October. The next intended coverage starts 26 October. If collection is delayed until 20 October, the next cycle does not automatically shift to 27 October.

Travel / early packing

An early-pickup communication selects a specific pack and requested collection date. If uncompleted preparation was planned later, the demo advances it to that date and flags the assignment for manager review. Existing earlier preparation and completed records stay in place. Medication coverage and clinical holds remain unchanged.

Partial / multiple packs

Show separate pack IDs and coverage. Collecting two of three packs leaves one outstanding. Overlap, gaps or a partial-day replacement require explicit review.

Plan the work around patient needs

Plan by pack counts, patient supply dates, current stages, holds and assigned responsibilities. Interruptions from dispensing, counselling and other duties mean elapsed time is not a staff-efficiency measure. Do not show estimated task minutes, speed rankings or productivity scores. Completion timestamps are retained only as care and audit evidence.

Moving work changes task dates, not medication coverage. Non-working days, public holidays, staff absence and medicine/pack suitability constrain how early work may be scheduled. No automatic “optimisation” overrides pharmacist decisions.

VANTRO· WEBSTER
Patient continuity
04 · Communications and medication lists

A quick note becomes a
visible, owned action.

1Capture the communicationOpen the patient and select doctor, hospital, patient, carer or other source. Record caller identity, contact details, received time, channel, original note and attachments.
2Structure without changing the sourceSuggested fields include admission/discharge, medication change, travel, collection request, hold reason, effective date and follow-up. Retain the original wording alongside any structured summary.
3Review and assignThe author confirms the summary. A medication change remains pending until a pharmacist verifies the source and reconciles it. Assign an owner, due time and affected packs.
4Close the loopRecord clarification, approved action, patient contact and outcome. Keep unresolved items pinned; keep previous notes and later corrections visible.
AI is optional assistance. A summary or extracted medication list must not silently alter an approved regimen, release a hold, approve a pack or invent missing instructions.

Medication-list panel

Show source, document date, received date, uploader, version, effective date, pharmacist verification, last approved change and next review due. Uploading a document does not automatically make it the active packing instruction.

A configurable three- or six-month review interval reflects the pharmacy’s chosen policy. It is not presented as a universal legal interval. Changes and transitions of care can trigger review earlier. Show “requested”, “received—awaiting verification”, “current” and “overdue” distinctly.

Hospital holds

Offer 1, 2, 3 or 7 days, custom date, or until further clearance. These choices set a review date, never an automatic restart. A pending hospital change blocks affected packing/release until the pharmacist resolves it.

Missing or overdue documentation prompts an owned pharmacist decision and continuity-of-supply plan. The software must not independently decide to stop a patient’s medicines because an administrative date has passed.

VANTRO· WEBSTER
Operational visibility
05 · Reports, alerts and follow-through

See the exception.
Know who will resolve it.

Report / alertActionable information
Weekly workloadThis week and next week: unique patients and pack tasks by stage; unassigned work, upcoming supply dates, holds and checking queues.
Today’s handoverDue collections, ready packs, unchecked packs, partial collections and contact tasks. Identify threatened supply continuity, not only overdue calendar rows.
Changes and holdsUnverified instructions, affected ready/collected packs, hold review dates, pending discharge reconciliation and named clinical owners.
Medication-list reviewsLast verified list, next review date, request history, document received but unverified, overdue items and follow-up owner.
Quality and workloadRework reasons, missed deadlines, late collections, completion time trends and unresolved exceptions. Use for improvement, not simplistic staff rankings.

Alert behaviour

Each alert has severity, patient/pack link, owner, deadline and resolution state. Manager notifications update when packing or checking finishes; routine updates are grouped so urgent exceptions remain prominent.

Overdue tasks escalate to a configured backup pharmacist or manager. Acknowledgement means someone has seen the issue; it does not mark the clinical or operational issue resolved. Snoozing needs a reason and a new review time.

Collection evidence

Record patient or authorised collector, packs released, staff actor and timestamp. Support signature capture or a linked paper-sheet reference; document refusal or inability through the pharmacy’s process.

Daily email summary

Optional schedule and authorised recipients; report window and generation time shown. Record provider acceptance separately from delivery evidence. A failed email leaves the dashboard task open.

Zero results need an explanation. A report with no rows should show the active scope, source-data freshness and exclusion counts, helping staff distinguish “nothing due” from a filter or data failure.

Email content and patient identifiers require an agreed privacy model. The public demonstration uses only fictional data and simulates notifications.

VANTRO· WEBSTER
Reliability by design
06 · Required production foundations

Safe behaviour includes
failures and interruptions.

The demonstration validates interaction and workflow. Production needs a separate security, clinical and operational review before any real patient information is introduced.

Durable records

Server-backed patient, cycle, pack, assignment, document, communication, hold and collection records. Reloading or switching devices must not lose confirmed work.

Audit history

Append-only events capture actor, server time, reason, previous/new values and linked versions. Correct errors through attributed amendments rather than silent deletion.

Duplicate prevention

Unique cycle/pack identifiers and idempotent actions prevent double-clicks, retries and repeated scheduler runs from creating duplicate work or collections.

Concurrent changes

Version checks reject stale updates. A checker must see a newly entered medication change before approval; a late browser tab cannot overwrite a hold.

Access and separation

Role-based permissions and pharmacy isolation enforced on the server. Protect documents, backups and logs; public demo hosting must never serve patient files.

Recoverable outages

Show offline/unsaved state clearly. Use an approved downtime log, then reconcile manually with duplicate checks. Never display a failed save as completion.

Scheduling and service monitoring

Use Australia/Melbourne for business dates and daylight-saving transitions, with UTC event storage. Monitor scheduler heartbeat, report generation, notification failures and unresolved task counts. Alert on silence or stale data.

Restoration and data quality

Test backup restoration and access recovery. Validate patient identity, duplicate imports, missing coverage, overlapping packs and document-version links. Keep an exportable audit record for investigation.

No automatic success by assumption. A local click is not a saved event; a prepared pack is not a checked pack; an emailed report is not proof of patient collection.
VANTRO· WEBSTER
Delivery and acceptance
07 · Build, test, then introduce

A staged path to
real pharmacy use.

Stage 1 — Separate visual demo. Demonstrate role views, patient timeline, assignment, packing, checking, hold, priority and collection using fictional records. Make reset and demo status obvious.

Stage 2 — Validated workflow. Agree pharmacy policy, roles, terminology and exception handling; implement durable records, server rules and audit history in an isolated test environment.

Stage 3 — Controlled pilot. Train a small team, rehearse downtime, run an agreed parallel verification process and reconcile every pack before expanding.

Acceptance scenarioRequired observable outcome
Weekly pack; early or late pickupCoverage stays correct; actual collection changes only the handover record.
Packer submits; checker returnsRework reason visible; release blocked until a new pharmacist check.
Change after checkingAffected pack approval invalidated; replacement/recheck linked to the new approved instructions.
Hospital hold reaches review dateReview alert appears; packing/release remain blocked until pharmacist clearance.
Travel and multiple packsReason, approved coverage and individual pack collection recorded; gaps/overlaps flagged.
Medication-list uploadOld version retained; new document stays unverified until pharmacist approval.
Two users; retry; outageStale save rejected, duplicate action prevented, failed save visible and recovery reconciled.
Staff absence / email failureUnowned or threatened work escalates; dashboard remains authoritative; no false completion.

Go-live gate: pharmacy lead approves workflow and local procedures; critical acceptance scenarios pass; permissions, restoration and downtime are demonstrated; training and support ownership are assigned; no unresolved critical release or patient-identification defect remains.

Clinical governance references — separate from product decisions

The Australian Commission’s Medication Management at Transitions of Care Stewardship Framework (2025) provides relevant governance context. The PSA dose administration aid guidance should be checked in its current accessible edition before production; the supplied PDF link was not retrievable during this review. Interface rules, review intervals and escalation timings in this document are proposed design choices, not claims of universal legal requirements.

VANTRO·
Pickup notifications · Added 17 October 2026
Automatic ready notification

Pharmacist sign-off.
Then the ready message.

The pharmacist's successful Check & release action triggers a ready notification to the patient's selected recipient: the patient or nominated carer. Completing packing alone never triggers the message.

Demo implemented. Automatic simulation is on by default. Recipient, masked mobile, message, pharmacist actor, simulated time and outcome appear in Pickup notifications. No real phone receives a message.
ConditionRequired behaviour
Current pack approvedCreate one notification for that sign-off. Repeated clicks or retries must not duplicate it.
Selected recipientUse the verified patient/carer mobile and documented SMS preference / authority. Do not message every stored contact.
Missing details or permissionPreserve successful pharmacist checking. Record a Not sent exception and assign contact follow-up.
Hospital hold / unresolved changeBlock ready notifications. If already sent, flag staff contact; an SMS cannot be recalled.
Notification contentIdentify the pharmacy and say the pack is ready. Avoid medicine names, diagnoses or unnecessary health details.
Collection completedStop outstanding pickup reminders for those packs. Retain the notification history.

Production delivery model

Save pharmacist sign-off and a unique outbox event in one database transaction. Send only after that transaction succeeds. Recheck eligibility before transmission. Track queued, provider accepted, delivered and failed separately; delivery confirmation does not establish that the recipient read it.

Use provider message IDs and idempotency protection; retry recoverable failures with limits and escalate ambiguous timeouts instead of blindly sending again. Keep credentials on the server, enforce spending limits and monitor prepaid credit. Receive status callbacks securely. Receiving replies and opt-out handling depend on the chosen sender configuration.

Cost controls

Use a short plain-text template, preview SMS segments, apply an SMS budget and avoid repeat reminders after collection. Provider setup, per-segment charges, number rental, GST and any registration charges must be confirmed before activation.

Example wording

Hello Eleanor, your pack at Demonstration Pharmacy is ready for collection. Please collect during our opening hours.

The demo uses masked fictional mobile numbers and local simulation. No messaging account has been created, funded or connected.