The problem
A patient arrives for an MRI on the fourth floor and ends up in radiology on the second. A family member circles the ICU wing looking for room 412. An outpatient turns up twenty minutes late because the entrance on the appointment letter is one building over from the one they used.
Each of these costs a few minutes. Together they cost the morning, and they cost it twice: once for the patient, and once for the staff member who stops what they are doing to point the way. Then there is the part nobody measures, which is the waiting. A token number with no estimate attached keeps a person in a chair for two hours when they could have come back in twenty minutes.
What the pilot does
We build live guidance inside one area of your facility: the outpatient block, the imaging wing, the emergency entrance, wherever the friction is worst. Patients and visitors scan a code or open a link and get directions on their own phone, with no app to install.
Then we add the waiting layer. What each step is, how long it typically takes, where to sit, and when to start walking towards the next counter. In the third week we publish the queue view so people can see the shape of the line in front of them.
The pilot runs four weeks. You see how people actually move through the area, where they get stuck, and whether guidance changes anything. At the end you decide whether a wider deployment makes sense.
Scope
One focused area: a single floor, a busy wing, or a department. We choose it together, based on where people get lost and where the queue is longest.
The prototype runs for the duration of the pilot. Keeping it, expanding it, or maintaining it beyond that is a paid engagement, and we will price it before the pilot ends.
What you get
- A working guidance interface in one area, reached by code or link
- Movement data: which entrances people use, where they stop and ask, how long counters take to serve
- A queue view built on observed service rate, with a time to walk
- Feedback from patients, family members, and your staff
- A published case study with your organisation named
- A clear answer on whether a full deployment is worth the money
What we need from you
- Floor plans or CAD files for the pilot area
- One point of contact who knows the space and can settle questions about routes
- Permission to publish a case study
That is the list. We handle the build, the deployment, and the iteration. You point us at the right rooms and tell us what is working.
How it works
Week 1: Map. We build the digital map from your floor plans and configure routing for the pilot area, including the vertical moves between floors.
Week 2: Deploy. Codes go up at entrances, lift lobbies, and corridor junctions. Patients scan and get turn-by-turn directions on their phone.
Week 3: Guide. We add the journey view: the steps of a visit in order, with durations, and the queue estimate that turns into a time to start walking.
Week 4: Report. We write a case study together and look at the data. If a wider deployment makes sense, we outline scope and pricing. If it does not, we part with what we learned.
What comes next
The pilot reads queue position from staff entry and from what patients report, which works without touching your hospital information system. Connecting to appointment and laboratory systems is the following step, and it makes the estimates exact. That work is on our roadmap and outside the pilot scope.
Where this stands
In pilot. The map, the multi-level routing, the codes, and the operations console run today at Fortis Hospital across six floors. The journey view and the queue estimate are the pieces being built into the pilot.