Is this HIPAA-compliant?+
The system is purpose-built to be HIPAA-aware. It captures device proximity (MAC address, signal strength, timestamp) only. It does not capture, store, or transmit any patient health information, clinical content, audio, video, or identifying patient data. Because it does not handle PHI, it does not fall under the Business Associate framework in the same way an EMR or billing vendor would. The deployment is reviewed alongside the hospital's privacy officer and risk management team, and standard policy disclosure framework is provided for visitor and contractor signage.
Will this disrupt clinical workflow?+
No. Nodes are passive sensors hidden inside door frames, behind cabinets, and inside hardware that clinicians do not interact with. There is nothing for nurses, physicians, or pharmacy staff to scan, badge, or remember. The system is intentionally invisible to the clinician, which is also why it produces a defensible record: the people being logged do not know they are being logged at the device level, which is exactly what you need for a diversion investigation.
How does this interact with our infant security system?+
It runs alongside your existing infant-tag system as an independent backup record. The infant tag is the primary alert mechanism and remains in place. The Digital Tripwire node at the L&D and nursery threshold is the forensic record that survives any tag tampering, malfunction, or workflow gap. In the catastrophic-failure scenario where the tag system fails, the proximity log is what hands the FBI the device cluster of every person who crossed the threshold during the abduction window. The two systems are complementary, not redundant.
Is the proximity log admissible to DEA and Joint Commission?+
The export is designed specifically for regulatory and federal evidentiary use. Each log entry is hash-signed at the moment of capture, the upload chain is documented, and the export package includes chain-of-custody metadata showing every transformation between capture and delivery. Digital Tripwire is built around the same evidence-handling standards used in digital forensics. DEA diversion investigators, Joint Commission auditors, and CMS surveyors review supplemental electronic logs as part of standard practice, and the Digital Tripwire export is structured to fit that review process.
What about visitor and patient privacy?+
The intended deployment is in restricted-access zones (pharmacy, L&D, OR, behavioral health, materials management, morgue) where patients and visitors already operate under documented monitoring frameworks (cameras, badge access, signage). The system does not capture identity, content, or any data outside of MAC address proximity. This is functionally similar to the proximity logging that hospital Wi-Fi infrastructure already performs for network management and asset tracking, and it falls under the same disclosure framework.
How do we pilot this in a hospital environment?+
Standard hospital pilots run 90-120 days, focused on the highest-stakes zones first: pharmacy with Pyxis, L&D and nursery, and the ED. Six to nine nodes plus a hub. Installation is non-invasive and is typically done by hospital facilities during a routine maintenance window. The pilot is structured as a formal evaluation with security, pharmacy, risk management, the privacy officer, and nursing leadership at the table. Most hospitals expand from a single-unit pilot to a system-wide deployment within twelve months. Contact us for hospital scoping.
