Hospital logistics, explained from the human side.
junglemysteryparcel.site

Field guide 03 / People and shared space

Sharing the corridor

A safe delivery fits around patients, visitors and staff—not the other way round.

Three review points

People and access

Review visibility, mobility aids, assistance dogs, sensory needs and the space required for beds and equipment.

Loads and cleaning

Check stability, secure compartments, hygiene separation and responsibility for cleaning.

Faults and emergencies

Define escalation, safe recovery, fire-route protection and how emergency movements take priority.

Assess the service, not just the product

A manufacturer may provide extensive safety documentation, but a hospital still needs to understand the risks of its particular service. The same machine can face different conditions on a quiet stores route and a busy outpatient corridor. Assessment should include the load, the building, nearby activities and the people who may encounter it. Procurement, facilities, health and safety, infection prevention, security and frontline teams all hold different parts of that picture.

ISO 12100 describes a framework for machinery risk assessment and risk reduction. ISO 3691-4 addresses safety requirements and verification for driverless industrial trucks and their systems, where applicable. These references are not interchangeable with a site approval, and a product’s classification matters. Ask suppliers to explain the standards they claim, the scope of their evidence and the operating limitations that the hospital must maintain.

Make room for people who move differently

Hospitals are not controlled warehouse aisles. A person may stop suddenly because they are in pain, confused or looking for a department. Someone using a walking frame may need more time and space than a navigation model predicts. A bed team may have limited sight lines around the load they are moving. Safety planning should account for these ordinary conditions rather than treating them as unusual exceptions.

Consider how the robot communicates intent. Audible alerts may be inaudible to some people and distressing to others; visual signals may not be useful to a person with sight loss. Excessive warnings can become background noise. Review the combination of speed, clearance, predictability and information with accessibility representatives. Do not assume that a friendly appearance, a spoken greeting or a prominent screen makes a machine understandable to everyone.

Stopping safely is not the whole answer

Protective sensing and stopping behaviour are important, but they need to be considered within the full traffic arrangement. A stopped robot could block a narrow doorway, a clinical response route or access to equipment. Approved waiting areas should be identified before service begins. The design should also address what happens when several robots wait at once, especially near lifts, docking stations and popular receiving points.

Emergency-stop controls, protective stops and normal pauses have different purposes. Staff should understand the actions relevant to their role without being expected to diagnose machinery faults. Training must explain who can reset or move a machine and under what conditions. Nobody should be encouraged to push, tow, lift or bypass a disabled robot unless an authorised recovery procedure explicitly allows that action.

Include the risks that do not look robotic

A poorly secured cart can create a risk even when navigation works correctly. Review load restraint, stability, protruding items and pinch points at docking interfaces. Charging arrangements need suitable locations and controls, including consideration of electrical safety and the supplier’s battery guidance. Maintenance access should not obstruct clinical work or create an informal storage area in an escape route.

Cleaning is another operational responsibility, not a cosmetic extra. The cleaning method must suit the equipment and the local infection prevention policy. Staff need to know which surfaces they clean, when the task happens and how contamination or spills are reported. Using incompatible chemicals can damage components; relying on occasional wiping can leave important contact surfaces neglected. The process should be practical enough to survive a busy shift.

Test difficult conditions deliberately

Acceptance testing should cover credible interruptions in a controlled and approved manner: a blocked route, an unavailable lift, an unreceived delivery or a loss of a required connection. Tests should not expose patients or staff to avoidable hazards. Record the expected response, the observed response and who decides whether a problem prevents launch. A successful demonstration on one quiet afternoon is not evidence of reliable performance throughout the working week.

The Health and Safety Executive provides guidance on workplace equipment and risk management in Great Britain. The Provision and Use of Work Equipment Regulations 1998, usually called PUWER, are an important part of that context. Fire arrangements also need local specialist review; guidance under the Regulatory Reform (Fire Safety) Order 2005 is relevant in England and Wales. Requirements differ by jurisdiction and should be checked for the actual facility.

Keep learning after launch

Encourage staff to report near misses, confusing behaviour and practical workarounds without making the robot’s continued operation the priority. A repeated delay or an awkward receiving position can be an early signal of a safety issue. Review changes to maps, software, loads and service hours through a controlled process. A service should be paused or restricted when its agreed safe conditions no longer hold.

Useful assurance is ongoing. Named owners should review incidents, maintenance records, training needs and emerging accessibility concerns. Clinical priorities can change quickly, while equipment may remain in service for years. The purpose of a safety system is to keep those changing realities visible and actionable, not merely to produce a folder that was complete on the day of installation.

Safety needs an owner

Clear dispatch and recovery responsibilities turn a technical capability into a manageable service.

Connect the handoffs →