Skip to main content
Every barcode scan in Forager produces a confirmation — a structured record of which asset was seen, where, by whom, and when. These records are the core compliance output of Forager.

Confirmation types

When each type comes up

Match is the routine outcome. Tech is in the correct room scanning a device that belongs there. This should account for the majority of confirmations on a well-maintained floor with accurate survey data. Mismatch — confirmed happens when equipment was moved since the last scan. Common with shared portable assets: infusion pumps borrowed by another department, laptops pulled for repair, medical carts relocated between floors. Confirming the new location updates the record so the floor plan stays accurate. Mismatch — dismissed is appropriate when a tech picked up a device to service it and will return it to its original room, or when the app is misidentifying the current room and the tech knows the recorded location is still correct. Use dismiss when the CMDB record does not need to change. New asset comes up when IT receives new equipment mid-cycle, when devices arrive at a site that joined Forager after initial deployment, or when an asset was previously tracked under a different barcode. The first scan seeds the record — admin can add the name, type, and other metadata from the dashboard.

What gets recorded

Every confirmation captures:
  • Asset tag — the barcode scanned
  • Location — the room the tech was in when they scanned
  • Tech — who scanned it
  • Timestamp — when the scan happened
  • Type — match, mismatch confirmed, mismatch dismissed, or new asset
This record is permanent and cannot be edited. It is your audit trail.

How location is determined

Forager determines the tech’s current room by comparing live Wi-Fi and Bluetooth signals against a fingerprint database built during survey. The room with the closest matching signal pattern is selected. The app shows a confidence level alongside the current room. Higher confidence means the signal pattern closely matched a surveyed room. If confidence is low, consider re-surveying that area.

Compliance use

Confirmation records are the evidence that a device was physically located and verified. For Joint Commission, OIG, or similar audits, each record shows:
  • The device was physically present in a specific room
  • A named technician verified it
  • It happened at a specific time
Your IT director can view and export these records from the dashboard.

Points

Every confirmation earns points based on how long it has been since the asset was last confirmed: After each confirmation, a sheet shows how many points you earned. Tap Next in queue → to return to the Most Wanted queue and keep your momentum going. Points accumulate on the leaderboard under This Month and All Time. During a sprint, they also count toward the sprint leaderboard.

Most Wanted

Full guide: point tiers, the queue, the leaderboard, and sprint competitions.

When confirmations do NOT fire

  • Scanning a barcode that cannot be read (damaged label, wrong format)
  • Scanning while the app has not yet determined a room (the “Locating…” state)
  • The app is offline and storage is full (extremely rare)
Do not scan assets while walking between rooms. Wait for the app to lock onto a room before scanning to ensure the location is recorded accurately.