Skip to content

Hospital medication delivery solution

From pharmacy to nurse station.Authenticate both ends and verify with staff.

Robots transport medication from pharmacies to nurse stations; clinical staff prepare/check drugs, authorize receipt and administer them.

Illustrative robot service scene
  1. Request

    Users

    Select items, destination and required time.

  2. Deliver

    Robot

    Follow configured routes and access rules.

  3. Handover

    Recipients

    Receive the arrival alert, use configured access and verify receipt.

Pilot the documented workflow with responsible staff verifying key handovers.

The service

Service flow and ownership

Robots execute configured tasks; responsible staff retain verification and on-site response.

  1. Users

    Request

    Select items, destination and required time.

  2. Dispatch staff

    Prepare and load

    Check items, packaging and compartments; load manually and confirm.

  3. Robot

    Deliver

    Follow configured routes and access rules.

  4. Recipients

    Handover

    Receive the arrival alert, use configured access and verify receipt.

  5. Managers

    Retain records

    Review completion, exceptions and handover records.

Confirm execution separately from human handover/review; assigned staff take over exceptions.

Roles

  • Dispatch and receiving staff

    Request, prepare, load, verify and acknowledge receipt.

  • Robot

    Transport, notify and return status within the configured scope.

  • Management and support

    Maintain points, schedules, equipment, exception handling and records.

Service modes

Select modes for the workflow; agree extensions separately.

Direct indoor delivery

KAGO carries frequent small pharmacy-to-station loads.

Configure and validate against site conditions.

  1. RequestSelect items, destination and required time.
  2. DeliverFollow configured routes and access rules.
  3. HandoverReceive the arrival alert, use configured access and verify receipt.

Cross-building

TRANGO handles batches on validated campus routes.

Configure and validate against site conditions.

  1. RequestSelect items, destination and required time.
  2. DeliverFollow configured routes and access rules.
  3. HandoverReceive the arrival alert, use configured access and verify receipt.

Standalone / integrated

Start independently; assess optional HIS, LIS, pharmacy or nursing interfaces.

Configure and validate against site conditions.

  1. RequestSelect items, destination and required time.
  2. DeliverFollow configured routes and access rules.
  3. HandoverReceive the arrival alert, use configured access and verify receipt.

Do not replace medication review, administration or clinical judgment. Active cooling, UV disinfection, antibacterial materials and unattended transfers are not established.

Terminals and configuration

Document-based scope; confirm supplied model, options and site fit.

Illustration of items and staff handover
Illustrative scene; confirm packaging, compartments and collection against supplied configuration.
  • Terminal

    Select for medication packaging, compartments and access control.

  • Task platform

    Manage tasks, devices, collection permissions, records and exceptions.

Suitability

Scenario fit

Robots transport medication from pharmacies to nurse stations; clinical staff prepare/check drugs, authorize receipt and administer them.

  • Direct indoor delivery

    KAGO carries frequent small pharmacy-to-station loads.

  • Cross-building

    TRANGO handles batches on validated campus routes.

  • Standalone / integrated

    Start independently; assess optional HIS, LIS, pharmacy or nursing interfaces.

Where the service helps

Reduce repeated trips around these tasks and define on-site handovers.

Clinical pain pointDirect operational impact
Direct indoor deliveryKAGO carries frequent small pharmacy-to-station loads.
Cross-buildingTRANGO handles batches on validated campus routes.
Standalone / integratedStart independently; assess optional HIS, LIS, pharmacy or nursing interfaces.
Coordination priorities
  • Reduce repeated trips

    Assign suitable repeated routes to robots and compare results in the pilot.

  • Clear handovers

    Verify outcomes against task, destination and responsible role.

  • Operational review

    Use task states and exception records to adjust routes, schedules and configuration.

Building route

Routes and service points

Configure routes for the actual site; diagrams explain the workflow.

  1. Pharmacy

    Prepare, recheck, load and confirm.

  2. Nurse station

    Authorize collection and verify handover.

  3. Doors / lifts / charging

    Commission access and define safe waiting and contacts.

Illustrative route; confirm points and access on site.

Locations

  • Pharmacy
  • Nurse station
  • Doors / lifts / charging

Validate a complete loop

Pharmacy → Nurse station → Doors / lifts / charging

Diagrams explain the flow; survey actual passages, thresholds, access and stops.

Site readiness and operations

Confirm site, equipment and staffing; verify interfaces per project.

  • Identity / receipt

    Verify both ends under hospital rules; escalate refusal, missing recipients and abnormal openings.

  • Manual transfers

    Robots execute separate tasks; staff verify any required transfer.

  • Cold-chain packaging / connectivity

    The hospital provides insulated transport boxes. The source specifies robot 4G connectivity without separately installing hospital Wi-Fi.

Commission configured interfaces, notifications and access; assign site contacts and staff fallback.

Suggested readiness checks

Swipe horizontally to see all columns.

ItemScopeConfirmation
Scope and pointsPharmacy, Nurse station, Doors / lifts / chargingConfirm accessible scope and responsible staff on site.
Routes and accessMaps, passages, doors/lifts, network and charging.Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptionsDispatch and receiving staff, Robot, Management and supportAgree notifications, staff takeover, records and review rules.

Fleet planning

Pilot and expansion

Start with one pharmacy, one building and three to five nurse stations before adding cross-building routes and TRANGO.

Terminal

Select for medication packaging, compartments and access control.

Task platform

Manage tasks, devices, collection permissions, records and exceptions.

Sizing considerations
Clinical parameterImpact on capacity
Task cycleMeasure request, execution, handover, return and charging time.
Site scopePharmacy, Nurse station, Doors / lifts / charging
Staff coordinationAllow for available receiving, reviewing and exception-response staff.

Source configurations/data refer to their stated scenario; confirm final sizing through site validation.

Schedules and tasks

Schedule around demand and site routines, allowing for cleaning, charging and exceptions.

  1. Identity / receipt

    Site-defined schedule

    Verify both ends under hospital rules; escalate refusal, missing recipients and abnormal openings.

  2. Manual transfers

    Site-defined schedule

    Robots execute separate tasks; staff verify any required transfer.

  3. Cold-chain packaging / connectivity

    Site-defined schedule

    The hospital provides insulated transport boxes. The source specifies robot 4G connectivity without separately installing hospital Wi-Fi.

Start with one pharmacy, one building and three to five nurse stations before adding cross-building routes and TRANGO.Do not replace medication review, administration or clinical judgment. Active cooling, UV disinfection, antibacterial materials and unattended transfers are not established.

Systems and staff coordination

Start with the documented workflow and verify optional interfaces separately.

System layerResponsibilities
TerminalSelect for medication packaging, compartments and access control.
Task platformManage tasks, devices, collection permissions, records and exceptions.

Pilot & operation

Suggested implementation

The following are project assessment and acceptance suggestions, subject to site confirmation.

  1. Confirm scope

    Site preparation

    Start with one pharmacy, one building and three to five nurse stations before adding cross-building routes and TRANGO.

  2. Configure and commission

    When ready

    Check devices, routes, points, accounts and necessary access/system interfaces.

  3. Trial and acceptance

    By project agreement

    Validate real tasks, staff coordination, exceptions and records before expansion.

Suggested exception handling

The following are project assessment and acceptance suggestions, subject to site confirmation.

View the hospital medication exception matrix

Swipe horizontally to see all columns.

ConditionActionOwnership and records
Task cannot continuePause, wait or hand over to staff under site rules.Managers record cause, owner and recovery conditions.
Handover/review incompleteContact the assigned staff; automatic task closure does not replace their confirmation.Record the reason and follow-up.
Device/access exceptionFollow support procedures and use staff service if required.Support and site staff coordinate and validate recovery.

Suggested acceptance

The following are project assessment and acceptance suggestions, subject to site confirmation.

View acceptance measures and responsibilities

Swipe horizontally to see all columns.

CheckStatusVerification
Task executionSuggested acceptance itemComplete tasks within agreed routes/scope and record success, failure and reasons.
Staff coordinationSuggested acceptance itemVerify notification, permissions, human review/handover and exception takeover.
Operational recordsSuggested acceptance itemSample tasks, times, points and outcomes; agree metrics and targets with the project team.

Agree before delivery

  • Service scope

    Do not replace medication review, administration or clinical judgment. Active cooling, UV disinfection, antibacterial materials and unattended transfers are not established.

  • Responsibilities

    Dispatch and receiving staff, Robot, Management and support

  • Configuration and metrics

    Agree device models, options, interfaces, timing and targets in project documents.

Questions

KAGO inpatient medication delivery robot

Related equipment

Review product information and reconcile the document version with the supplied model/configuration.

View product

Document configuration and device checks

Terminal
Select for medication packaging, compartments and access control.
Task platform
Manage tasks, devices, collection permissions, records and exceptions.

Document and current product versions may differ; confirm supplied specifications and project configuration.

Common questions

Where should the pilot start?

Start with one pharmacy, one building and three to five nurse stations before adding cross-building routes and TRANGO.

How do robots and staff share work?

Dispatch and receiving staff:Request, prepare, load, verify and acknowledge receipt. Robot:Transport, notify and return status within the configured scope. Management and support:Maintain points, schedules, equipment, exception handling and records.

What needs separate confirmation?

Do not replace medication review, administration or clinical judgment. Active cooling, UV disinfection, antibacterial materials and unattended transfers are not established.

How are configuration and acceptance set?

Use source recommendations as a starting point, then confirm against site routes, supplied equipment and trial data. Suggested checks do not establish fixed performance or service guarantees.

Plan a project

Pilot preparation

Start with one pharmacy, one building and three to five nurse stations before adding cross-building routes and TRANGO.

Discuss the solution
Scope and points
Pharmacy, Nurse station, Doors / lifts / charging Confirm accessible scope and responsible staff on site.
Routes and access
Maps, passages, doors/lifts, network and charging. Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptions
Dispatch and receiving staff, Robot, Management and support Agree notifications, staff takeover, records and review rules.

Choose a dedicated solution for each workflow.