But showed up for a 6:15 a.m. OR in-service and our new console booted faster than the breakroom coffee, but the real win was remembering the charge nurse’s barcode headache and showing how the integration kills that double-entry — anyone else let the tech dazzle while you close on the relationship?
But > how the integration kills that double-entry — anyone else let the tech dazzle — I put the scanner in the charge nurse’s hand and go quiet for 15 seconds; when the ADT write-back kills the second swipe, I ask who owns barcode policy and book a quick follow-up. Small caveat: make sure IT flipped the HL7 mapping before a 6:15 a.m. in-service or your faster-than-coffee flex fizzles.
Once it boots faster than the coffee, I pull the materials manager for a 60-second ‘scan → ADT → charge’ and have them screenshot the timestamp so the charge nurse sees the “no double-entry” proof after the case. Small caveat: if GTIN vs HIBC mapping isn’t set, you’ll face-plant, so I ping IT the day before to validate symbologies — @pClarke1992 you ever tie it to a same-day variance report so finance feels it too?
I do a 60‑second “messy label” demo: ask the circulator for the grimiest tray sticker, scan it, and show how the system flags a mismatch and still gets the item counted in one pass. @tony_r88 the timestamp proof is gold; small caveat is to pre‑clear with IT so audit is on or your “show me the receipt” moment vanishes — anyone let biomed run the exception path first?
At 6:15, I live-edit a pref card, demo SSO; if no IT, show audit trail. @ITMike?
Airplane‑mode proof is my closer: I flip the app offline, scan two items, reconnect, and show the queue posting in the log so nobody worries about the network — let the tech sing while I ask the OR lead who wants the next‑day “exceptions” email. Small watch‑out: don’t demo it near shift change or you’ll lose the room. @lila_quinn53 you using offline queuing as your fast trust move?