STATvault Request a demoDemo

How does NFC tap proof work at clinic boxes?

Drivers tap the NFC tag at each clinic box. StatVault matches every tap to the stop, shows scan health per account, and finds dead tags for you.

A pickup is only as good as the proof behind it. StatVault uses an NFC tag on the clinic's lockbox: the driver taps it with their phone, and the tap becomes part of the order's custody record.

Tap at the box

Each pickup location has a lockbox with an NFC tag. The driver arrives, taps the tag with the phone, and the app records the tag, the time and the position. The tap goes to the server through the app's outbox, so it survives a dead zone in a hospital basement and lands as soon as the phone reconnects. On Android the phone reads the tag on contact. On iPhone the driver presses scan and holds the phone to the tag.

Each tap is matched to the stop or order it belongs to. A tap at the wrong box shows as a tap at the wrong box. A stop completed with no tap shows as NFC scan missing.

What counts as a scan

There is one rule, and every screen uses it. A unit is scannable when its location has a registered box. It counts as scanned when a tap is linked to it, or when that box's tag was read near the time of the stop. Raw taps are the truth: the record is built from what the phone actually read, not from a checkbox.

Scan health for every account

Every account you serve gets a scan-health view: orders picked up and route stops completed, rolled up by day, by month, by stop and by driver, with the share that carried a real tap. It answers the question a lab manager will eventually ask: how often does your driver actually scan our box?

Dead tags are found for you

Tags fail. A tag that several different drivers have tried, with no successful read, is flagged as a dead tag and kept out of the drivers' scan rates, so nobody is blamed for hardware. A diagnosis panel explains each problem in plain language: a moved tag, an unregistered tag near the stop, a phone that cannot read, or a driver who is not tapping. Fixes are one click away: register the box to the site, mark a placeholder, or message the driver.

The box registry

StatVault keeps its own registry of which box sits at which building and access point. Taps keep it honest: when a driver reads a tag nobody has registered, it shows up as an unregistered box at that account, ready to place. A registered box can also carry its own proof rule: switch on the box-clear photo and the driver making the last pickup of the day there is asked for a photo of the empty box, which dispatch reads back as boxes cleared at the end of the day.

How it fits

NFC proves presence. A SmartBox adds what the box itself observed. The tap joins the chain of custody on the order, with the box's readings beside it. The tap happens in the driver app, on the phones drivers already own.

Related

Questions couriers ask

What phones does it work on?
Android phones with NFC and iPhones. On iPhone the driver presses a scan button and holds the phone to the tag.
What counts as a scan?
A tap the server matches to the stop or order, either directly or by that box's tag read near the time of the stop. A completed stop without a matched tap does not count.
What is a dead tag?
A tag that several different drivers have tried and none could read. StatVault flags it so it gets replaced, and it does not count against the drivers.
Do I need new boxes?
No. A tag goes on the lockbox the site already has. SmartBox is a separate, connected box for the stops that need more.
Can dispatch see a missed tap right away?
Yes. Stops show NFC verified or NFC scan missing as the day runs, so a dispatcher can follow up while the driver is still nearby.