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.Documentation Index
Fetch the complete documentation index at: https://docs.hiveriselabs.com/llms.txt
Use this file to discover all available pages before exploring further.
Confirmation types
| Type | What it means |
|---|---|
| Match | Asset is in its recorded location. No action needed. |
| Mismatch — confirmed | Asset was in a different room. Tech confirmed the new location. Location updated. |
| Mismatch — dismissed | Asset was in a different room. Tech dismissed the update. Location unchanged. |
| New asset | Asset tag not previously seen. Current location recorded as first known location. |
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
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
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)