KShop

KShop - Patient ordering and pharmacy follow-through

Keep orders coming, even when the doors are closed.

In the intended pilot workflow, appropriately verified patients can revisit available repeats, submit or update a request outside opening hours and follow its order status without taking review responsibility away from the pharmacy.

KShop keeps the patient request and order context together while pharmacy staff retain every professional and clinical decision.

The pharmacy problem

Patients cannot always call during opening hours.

A patient can need to check a repeat, request pickup or delivery, update an order or ask for cancellation after opening hours, while staff still need the right context before deciding what happens next.

What KShop covers

What patients and staff can do.

KShop describes a patient portal connected to configured pharmacy-system information and the staff order work that follows.

Illustrative pilot workflow

From patient request to pharmacy review.

This static sequence explains the intended path from verified access to status communication; it does not simulate a patient portal, order record or pharmacy system.

  1. Verify access and show available repeats

    Configured pharmacy-system connections can support appropriately verified patient access to available repeats while staff retain patient-specific access decisions.

  2. Build or update the request

    The patient can create or update a request with supported pickup, delivery, collection or cancellation information, including outside opening hours.

  3. Complete staff checks with KSafe evidence

    Pharmacy staff review the request in KShop with relevant KSafe stock evidence; KSafe remains the owner of its inventory record.

  4. Decide whether to fulfil or update the request

    Staff retain the decision to supply, fulfil, update or cancel the request after their professional and clinical review.

  5. KMail

    Communicate the order status

    Configured status information can be shared with the patient while KMail retains the communications decision.

This workflow describes intended pilot behaviour, not an immediate service or product demonstration.

Staff control

Your team reviews every request.

KShop supports the request and order context; it does not replace pharmacy judgement or clinical responsibility.

Buyer value

Make ordering easier for everyone.

The value is a clearer patient request path and a staff view that keeps the order history and required checks together, not a promise of sales, revenue or fulfilment.

KSuite connections

How KShop connects the work.

KShop can connect patient and staff follow-through to the relevant operational module without moving responsibility for its record.

Illustrative example

A repeat request after hours.

The patient can revisit an available repeat and send a request. When the pharmacy next reviews it, staff use the order context and KSafe evidence to decide the appropriate supply, fulfilment or follow-up before a status update is communicated.

Pilot scope

Set up the patient journey together.

The described KShop workflow is intended pilot behaviour; it does not assert immediate or general production availability.

Buyer questions

Questions about KShop.

These answers distinguish patient access and status visibility from the staff decisions that remain necessary before an order progresses.

Can a patient submit a request outside opening hours?
Appropriately verified patients can submit an intended pilot request outside opening hours. The request may be accepted, but it is not immediately reviewed, reserved, approved for dispensing, paid or fulfilled.
Does KShop decide whether a request can be supplied?
No. Pharmacy staff retain every professional and clinical decision, including review, supply, dispensing approval, fulfilment, cancellation and final follow-through.
How does KShop work with KSafe, KMail, KDash and Kat?
KShop can use KSafe stock evidence for staff checks, share configured status communications through KMail, make follow-through visible in KDash and provide configured status information for Kat phone enquiries while each module retains its own record and decision boundary.