How to scope a hospital equipment tracking pilot

What should a hospital equipment tracking pilot prove?

A hospital equipment tracking pilot should prove that staff can find the right identified equipment in the agreed area and use that information in their daily work. Start with one equipment group and a defined set of locations. Agree what counts as a correct location, how recent a detection must be and who acts when the information is missing or wrong.

A tag appearing on a dashboard is a technical milestone. The operational test is whether the person looking for equipment can use the result, confirm its identity and follow the hospital's existing process for checking availability and suitability.

Choose one search problem and record the baseline

Ask staff to describe a repeated search: which equipment they need, where they begin looking and what makes the search difficult. Select a representative equipment group with the responsible clinical engineering and operational teams. Include the places it actually moves through, rather than only the easiest room to demonstrate.

Before installing tags, record a small agreed sample of searches. Note the start point, equipment type, time taken and whether the item was found. Use comparable tasks and conditions during the pilot; do not present an isolated successful demonstration as an estate-wide result.

Define room, zone or floor visibility

Write down the decision staff need to make. Finding the correct floor, a ward or a specific equipment store can require different location designs. Ask the supplier to explain how detections become locations and what the displayed timestamp means.

BLE tags are detected by compatible infrastructure; they do not independently calculate a GPS position. Gateway placement, building layout and the selected location method affect the result. Test neighbouring rooms, floor transitions, temporary storage and movement between the agreed areas. Agree how the interface distinguishes a recent detection from an older last-seen record.

Read what RTLS means and compare GPS and BLE asset tracking before selecting the architecture.

Keep identity, location and availability separate

Link each pilot tag to an equipment record using the organisation's existing identifier. Confirm who maintains the relationship when a tag is replaced or equipment leaves the pilot. A location record alone does not establish whether an item is clean, serviced, available or suitable for a particular use.

Where availability or service status is needed, identify its authoritative source and the staff action that updates it. Agree how conflicting or stale records are shown. Avoid designing a search screen that silently turns a location detection into an availability claim.

Test the complete staff workflow

Include the people who search for, return, move and maintain equipment. Test finding an item, returning it to storage, changing its location, reporting an incorrect result and replacing a failed tag. Check how users gain access and where they go for help.

Confirm mounting and cleaning arrangements with the responsible hospital team. Document battery inspection or replacement, missing-tag handling and infrastructure support. These are pilot responsibilities to agree, rather than assumptions to leave until rollout.

Use a practical acceptance checklist

• Identity: the detected tag resolves to the correct equipment record.
• Location: room, zone or floor results meet the agreed test cases, including adjacent areas.
• Freshness: staff can recognise recent detections and older last-seen records.
• Workflow: representative staff can find an item and report an exception.
• Maintenance: tag replacement, batteries and support have named owners.
• Value: repeated search tasks can be compared with the recorded baseline.

Set numerical targets with the hospital before testing. Record missed detections and incorrect locations alongside successful searches. Use those findings to decide whether to adjust the design, extend the trial or proceed to a wider rollout.

Bring a useful brief to the discovery meeting

Prepare an equipment sample list, a map of the pilot areas, examples of difficult searches and the systems that hold equipment records. Identify the staff who will test the workflow and the team responsible for supporting it.

The published Darent Valley Hospital case study provides related Foresolutions healthcare deployment context. Its customer story does not establish the outcome of your pilot; your acceptance evidence should come from your own estate and working conditions.