Frequent trips
Keep routine transport moving across departments and operating hours.
Hospital specimen transport solution
From collection point to laboratory.
Connect wards, clinics and blood collection points with laboratory receiving. Software organizes the task, robots handle transport, and staff prepare and complete each handover.
Many collection points. One receiving workflow.
Frequent trips, scattered departments and concentrated collection windows put pressure on manual transport. Start with the handover rules, then allocate the robots.
Collection points
- Wards & nurse stations
- Outpatient clinics
- Blood collection points
- Emergency departments
- Surgical collection points
Indoor or cross-building transport
Laboratory receiving
Check the container and confirm receipt
Collection points, eligible specimens and transport conditions are confirmed with the hospital.
Clear handovers
Identify who loads, who receives and how confirmation is recorded.
Variable demand
Combine stationed robots at busy points with shared capacity off peak.
One service. Clear responsibilities.
From a department’s request to laboratory receipt, follow the people, software and robots that carry the task forward.
Prepare and dispatch
The department seals the specimens and transport container, then calls a robot and selects laboratory receiving. When the robot arrives, staff verify access, load the assigned compartment and confirm dispatch.
Specimen delivery
- Sending point
- Ward nurse station
- Receiving point
- Laboratory receiving
Sealed specimen container
Ready for handover
Travel through the hospital
KAGO takes indoor routes; TRANGO links buildings. Containers travel in closed compartments, with lift and door integration where the route requires it. Staff carry out any planned transfer between robots.
Within one building
Ward → laboratory
KAGO
Between buildings
Collection building → central laboratory
TRANGO
Receive and confirm
Laboratory staff receive the arrival notice, verify access and retrieve the container. They check the handover, confirm receipt and report any exception. The task retains the outcome.
Laboratory handover
- Arrival notification
- Verify access and collect
- Check and confirm receipt
Report exceptions to the agreed contact
Interfaces, permissions and handover rules are confirmed for the project.
Follow a sealed specimen box.
Explore the hospital cutaway, or follow the robot through a staff handover. The plan and 3D scene share one task clock.
Routes share one illustrative level and omit lift travel. Time is compressed. Staff load and retrieve the container. The hatch mechanism is illustrative and subject to the selected hardware. The lower floor provides building context only. No device or hospital system is connected.
Routes share one illustrative level and omit lift travel. Time is compressed. Staff load and retrieve the container. The hatch mechanism is illustrative and subject to the selected hardware. The lower floor provides building context only. No device or hospital system is connected.
Match the service to the collection rhythm.
Combine the three modes around the central laboratory. Keep robots at dense collection points during peaks and share them between departments during quieter periods.
Stationed service
For busy collection points
Keep a robot near a specimen-intensive department or blood collection point for repeated loading and short trips.
Scheduled loops
For regular collection rounds
Visit agreed stops at configured times to collect or deliver routine specimens. Confirm the timetable and collection responsibilities.
On-demand calls
For routine, variable requests
A department calls a robot; dispatch allocates a suitable unit to the requested destination.
Two roles, selected for the route.
A layered fleet does not require every specimen to change robots. Use KAGO for a direct indoor trip or TRANGO for a route between buildings. Confirm any transfer points and responsible staff during planning.
Within one building
KAGO
Short, frequent trips from a ward or department to the laboratory, with lift and door integration where required.
Explore KAGO
Between buildings
TRANGO
Campus trunk transport linking buildings and the central laboratory, with space for hospital-provided transport containers.
Explore TRANGOA task connects people, robots and the building.
The plan combines task intake, dispatch, status monitoring, exception records and reporting. Hospital system integration is optional; the service can operate independently.
People
Departments, collection teams and laboratory staff create tasks and complete handovers.
Tasks & dispatch
Allocate robots, monitor task and robot status, and retain transport and receipt records.
Building connections
Connect compatible lifts and automatic doors on authorized routes. Plan charging points.
Exceptions & recovery
Record alerts, identify the issue, arrange handling, confirm the state and retain the outcome. Recovery rules are agreed during commissioning.
Movement follows the space available.
- Crowds
- Slow down or stop; pass only when there is safe clearance.
- Beds & wheelchairs
- Use obstacle avoidance and give space. The plan does not claim priority recognition for emergency beds.
- Blocked routes
- Reroute within permitted space or wait for access to recover.
- Lifts & doors
- Use integrated lifts and doors. If a lift is too full, exit or wait for the next car.
Start with one laboratory and 2–3 busy departments.
Confirm collection and receiving points, routes, permissions and handover rules before expanding. The stages below are indicative; site changes and integration scope determine the actual schedule.
- 01
Site survey
3–5 days
Points, routes, departments and handover rules.
- 02
IoT integration
1–2 weeks
Connect the required lifts and automatic doors.
- 03
System deployment
1 week
Map the site, deploy robots and configure tasks and permissions.
- 04
Joint testing
1–2 weeks
Test robots, access equipment and complete delivery scenarios.
- 05
Pilot operation
1–2 weeks
Run a limited service, review issues and adjust the workflow.
Hospital preparation
- Confirm departments, collection times and named handover staff.
- Authorize site work and provide access to lifts and automatic doors.
- Agree packaging, storage, infection-control and exception procedures.
- Prepare transport boxes and, when needed, insulated containers for chilled or temperature-sensitive items.
YOGO implementation
- Solution design, mapping and task configuration.
- Robot and dispatch deployment, plus agreed IoT integration.
- Operator training, pilot support and operational feedback.
- Maintenance and after-sales support under the project agreement.
For temperature-sensitive specimens, the hospital supplies suitable insulated containers. Confirm and validate container suitability, transport conditions and journey limits for the specimens and route.
Accept the complete journey.
Acceptance covers a usable workflow, clear handovers, stable operation and accessible records. Agree measurable pilot criteria with the hospital rather than treating illustration data as a service guarantee.
Tasks
A task can be created, assigned and completed.
Handovers
Loading and receiving responsibilities are clear; receipt records can be checked.
Access
Required lifts and automatic doors work on the agreed route.
Operation
Robots operate in the intended corridors and routine pedestrian conditions.
Exceptions
Alerts and task histories are available to the team.
Training
Departments can follow the agreed operating SOP.
Deliverables
- Survey findings and point list
- Maps and route configuration
- Robot and compartment configuration
- IoT integration list
- Operating SOP and training materials
- Pilot and acceptance documentation
Questions before the first route.
Does the service require hospital system integration?
No. It can run independently. Optional standard interfaces can be scoped if the hospital needs system integration.
How is access to the specimens controlled?
The plan includes card authorization, compartment locking, arrival notices and receipt records. Confirm the selected robot variant, credential method and permissions during design and commissioning.
Does a robot automatically transfer boxes to another robot?
Staff handle transfers between robots; automatic box transfer is outside this solution’s scope. Any relay process needs defined transfer points, staff and confirmation rules.
Are refrigeration and delivery times guaranteed?
The plan provides for hospital-supplied insulated containers when needed. It does not specify active refrigeration or a guaranteed journey time. Confirm transport conditions and acceptance criteria for the specimens and route.
What support accompanies rollout?
On-site training, pilot follow-up, exception handling, remote support and routine inspection support rollout. Service hours and response commitments belong in the project agreement.
Begin with a route the team can verify.
Bring the collection points, laboratory location, demand by time of day, building plans and handover requirements. Run the full journey first, then extend it.
Plan a hospital pilot