STARTING WITH REVOLUTIONIZING HOW VITAL SIGNS ARE TAKEN
SleeveSense™ is fueled by University of Arizona Technology. It’s an adhesive-free, mesh vitals sleeve that wirelessly charges and captures continuous clinical-grade biosignals data, seamlessly integrating with Senphonix's Microsoft Azure HIPAA-compliant cloud via encrypted Bluetooth® or LoRa® communication protocols. It's designed to be worn for days, weeks, or months without the need for removal during exercise, bathing, sleeping, etc. Comfort and durability have been prioritized to enable seamless integration into patients' lives, simplifying the process of measuring vital signs such as heart rate, respiration, blood pressure, oxygenation, perspiration, temperature, motion, and more, depending on the needs of the wearer.
Encrypted biosignals data flows continuously or in batches from the SleeveSense device to an Internet router and then to the Senphonix cloud. From there, data is analyzed to detect out-of- range patient vital signs, which then lead to clinician alerts, either via the Senphonix user interface, the patient's electronic health record (EHR), or both, in all cases showing up as a text or in-app notification.
The clinician interface, whether inside or outside of the EHR, will include the ability to configure alerts to the clinician's preference, a dashboard, alert history, and full reporting.
Patient Health Information is Treated with Extreme Care
When implementing with Bluetooth Low Energy (BLE), Senphonix will use it with Secure Connections enabled (Bluetooth 4.2 or later), leveraging AES-128 encryption with Elliptic Curve Diffie-Hellman (ECDH) key exchange for strong authentication and data confidentiality. Data transmitted from the Bluetooth receiver to the Azure IoT Hub or Event Hub will be secured using TLS 1.2 or 1.3.
For LoRa implementations, data from the device to the LoRa gateway will be encrypted using LoRaWAN 1.1 or later with AES-128 encryption—AppSKey for payload confidentiality and NwkSKey for message integrity. Data from the gateway to the LoRaWAN network server, and then to the Azure IoT Hub or Event Hub, will be transmitted over TLS 1.2 or 1.3 for secure transport.
Regardless of the implementation choice, once in Azure, data will be encrypted at rest with AES-256 and in transit with TLS, with proper access controls and key management via Azure Key Vault.
