Not Every Function Needs A Login
■ A visitor asks for directions and the robot stays locked An elderly visitor stops in the corridor, lost, looking for room 304. No staff are nearby. He asks the delivery robot passing by, and it answers that staff authentication is required. He is left standing there, still lost.
■ People outside the assumed user group still meet the robot Service robots are designed around staff. But corridors are shared with patients, families and visitors, none of whom carry credentials. When a single login guards every function, harmless ones like giving directions get locked away with the sensitive data.
■ Conclusion: Set the unit of authentication at the function level Releasing medication records demands strict authentication. Telling someone where a room is does not. Split permissions function by function and the guard stays firm while the open counter stays open. Decide, per function, who deserves an answer. Protecting something is not the same as closing it.
