Systems, apparatuses, and methods for enhanced notifications to users of wearable medical devices
The wearable medical device uses secure Bluetooth bonding with standard protocols to ensure secure control and accessible alerts, addressing security and alert visibility issues for users with sensory impairments.
Patent Information
- Application Number
- JP2024153978
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2018-12-31
- Filing Date
- 2024-09-06
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2039-12-20
AI Technical Summary
Wearable medical devices face security concerns against man-in-the-middle and eavesdropping attacks, and users may struggle to receive alerts due to visual impairments or clothing obstruction.
Implementing a wearable medical device with a Bluetooth stack that allows secure bonding with a controller and uses standard Bluetooth protocols for less secure notifications, paired with devices like smartwatches or headsets for audible or tactile alerts.
Enhances notification security and accessibility for users with sensory impairments without increasing device complexity or cost, ensuring timely responses to critical device conditions.
Smart Images

Figure 2024166270000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention, in exemplary embodiments herein, relates to systems, methods, and apparatus for enhancing the generation of notifications to a user of a wearable medical device, such as a fluid delivery device. [Background technology]
[0002] Demand for on-body or wearable medical devices, and body area network (BAN) medical devices (e.g., wireless controllers for on-body devices, and smartphones or smartwatches with medical condition management apps and health / fitness apps) is increasing with increasing patient and healthcare provider desires for better and more convenient patient management of medical conditions such as diabetes. For example, one type of wearable medical device is a wearable drug delivery device worn against the patient's skin (e.g., a patch pump with a cannula or needle inserted into the patient's skin) or a pump device that can be connected to the patient's skin, e.g., a belt, and an infusion set with tubing extending from the pump to an adhesive mount with a subcutaneous cannula.
[0003] Wearable medical devices can communicate wirelessly with a separate dedicated controller or with a smartphone (e.g., a smartphone with an app configured to wirelessly interface with the wearable medical device for various operations). Bluetooth® Low Energy (BLE), marketed as Bluetooth® Smart, is a wireless technology that provides an effective low-power protocol for wirelessly connected devices, including devices that run on power sources such as coin cell batteries, as is common in wearable medical devices.
[0004] A concern with wirelessly controlling wearable medical devices, especially devices that deliver medicines to a patient's body, is the security of the wireless control communications link against man-in-the-middle (MITM) and eavesdropping attacks. Of particular concern is the security of wearable medical devices against malicious or unintentional attacks in which the control of the medical device is undesirably altered by another device.
[0005] Another concern with wearable medical devices is whether users can receive alerts from their devices. For example, visual alerts generated by a wearable medical device's display may be difficult for some users to see, especially if the display is obscured by the user's clothing or if the user has a visual impairment. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] WO2018 / 183036 [Patent Document 2] WO2018 / 183038 Summary of the Invention
[0007] The problems are overcome, and additional advantages are realized, by the exemplary embodiments described below.
[0008] According to an exemplary embodiment, a wearable medical device (e.g., a wearable drug delivery pump) sends a request to another device to generate an audible or vibration notification at the other device, which is useful when the wearable medical device is hidden by the user's clothing or the user's vision or hearing is impaired. The other device that receives the notification generation request is a remote controller or smartphone paired with the wearable medical device, or a smart watch or Bluetooth (BT) enabled headset or other device paired with the remote controller. The wearable medical device is configured with a BT stack, which allows the device to be paired with the controller in a secure binding relationship, but can send less security-requiring signals (e.g., a request to generate a notification) to other devices (e.g., a BT enabled headset or smartwatch). Enable the headset or smartwatch to use a more ubiquitous wireless protocol, such as the standard BT protocol in broadcast mode.
[0009] According to an exemplary embodiment, a medical device is provided that includes a radio frequency (RF) circuit configured to exchange RF signals with a second device, a memory device, and a processing device connected to the RF circuit and the memory device and configured to detect at least one specified notification condition in the medical device, generate a request for notification in response to detecting the at least one specified notification condition, and transmit the request wirelessly to the second device via the RF circuit to prompt the second device to activate an indicator remote from the medical device.
[0010] According to aspects of the exemplary embodiment, the medical device is a wearable device, and the second device is at least one device selected from a controller and a smartphone, and is wirelessly paired with the medical device, the second device having at least one indicator selected from an audible indicator and a tactile indicator.
[0011] According to aspects of an exemplary embodiment, the second device is paired with a third device, the third device comprising at least one indicator selected from an audible indicator and a tactile indicator, for example, the third device is selected from the group consisting of a smart watch, a Bluetooth enabled headset, a portable monitoring device, and a Bluetooth enabled wristband device.
[0012] According to aspects of an exemplary embodiment, the processing device and the RF circuitry of the medical device are configured to use a selected one of at least two wireless communication protocols to exchange RF signals with at least one device selected from the second device and the third device via the RF circuitry, the at least two wireless communication protocols including a first communication protocol used by the processing device to pair the second device with the medical device and securely transmit secure information selected from configuration data, medical device operational data, and control signals for operating the medical device, and a second communication protocol used by the processing device to pair with at least one of the second device and the third device and transmit information selected from medical device status data and notifications that require less wireless security than the secure information.
[0013] According to an aspect of an exemplary embodiment, the medical device further comprises a user interface, the processing device configured to operate the user interface to generate a user selection prompt guiding a user to configure notification preferences based on criteria selected from a paired device selection and a corresponding notification mode, the paired device selection prompting the user to indicate at least one device paired with the medical device, and the notification mode prompting the user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for the notification.
[0014] According to an exemplary embodiment, a device is provided for generating a notification from a medical device, the device comprising: at least one indicator; a radio frequency (RF) circuit configured to exchange RF signals with the medical device; a memory device; and a processing device connected to the at least one indicator, the RF circuit and the memory device and configured to wirelessly receive a notification request from the medical device via the RF circuit, wherein the medical device generates a notification request in response to detection of at least one specified notification condition, and performs a notification operation selected from generating an audible signal via the at least one indicator, wirelessly transmitting a request via the RF circuit to a third device to generate an audible signal, generating a vibration notification signal via the at least one indicator, and wirelessly transmitting a request via the RF circuit to the third device to generate a vibration notification signal.
[0015] According to an aspect of an exemplary embodiment, the device is at least one device selected from a controller and a smartphone, and is wirelessly paired with the medical device, and the third device is selected from the group consisting of a smart watch, a Bluetooth enabled headset, a portable monitoring device, and a Bluetooth enabled wristband device.
[0016] According to an aspect of an exemplary embodiment, the device further comprises a user interface, and the processing device is configured to operate the user interface to generate a user selection prompt that guides a user to configure notification preferences based on criteria selected from a paired device selection and a corresponding notification mode, the paired device selection prompts a user to indicate at least one device to be paired with the medical device, the notification mode prompts a user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for notification, and the paired device is selected from the first device, a third device, and a fourth device.
[0017] According to an exemplary embodiment, a method of generating a notification from a medical device is provided, the method including: configuring the medical device to detect at least one specified notification condition; configuring the medical device to generate a request for a notification in response to detecting the at least one specified notification condition; and wirelessly transmitting the request to a second device including an indicator, the second device activating the indicator in response to the request.
[0018] According to an aspect of an exemplary embodiment, the indicator is an audio output device configured to output an audible output signal, and the second device is selected from the group consisting of a mobile phone, a Bluetooth enabled earpiece, a smart watch, a portable communication device, a portable computing device, and a portable wireless controller configured to control the medical device.
[0019] According to an aspect of an exemplary embodiment, the notification condition is selected from the group consisting of a life state of the medical device, corrupted memory in the medical device, a nearly empty reservoir in the medical device, an empty reservoir in the medical device, and a low battery in the medical device.
[0020] According to aspects of an exemplary embodiment, the method of generating a notification from a medical device further includes generating a user selection prompt that guides a user to configure notification preferences based on criteria selected from a paired device selection and a corresponding notification mode, the paired device selection prompting the user to indicate at least one device paired with the medical device, and the notification mode prompting the user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for the notification.
[0021] According to an exemplary embodiment, a method of generating a notification from a medical device includes wirelessly receiving a notification request from the medical device at a second device, the medical device being configured to generate the notification request in response to detection of at least one specified notification condition, and operating the second device to perform a notification action selected from generating an audible signal via at least one indicator, wirelessly sending a request to a third device to generate an audible signal, generating a vibration notification signal via at least one indicator, and wirelessly sending a request to the third device to generate a vibration notification signal.
[0022] According to aspects of an example embodiment, the method further includes the third device activating an indicator in response to receiving the request sent from the second device.
[0023] According to an aspect of an exemplary embodiment, the method further includes generating a user selection prompt to guide a user to configure notification preferences based on criteria selected from a paired device selection and a corresponding notification mode via a device selected from the medical device, the second device, and the third device. The paired device selection prompts a user to indicate at least one device paired with the medical device, and the notification mode prompts a user to select a mode selected from an audible mode and a tactile mode to be used by the paired devices for the notification. The paired devices are selected from the second device, the third device, and a fourth device.
[0024] Additional and / or other aspects and advantages of the invention will be set forth in the following description, or will be apparent from the description, or may be learned by practice of the invention. The invention includes paired devices and methods for operating the same having one or more of the above-described aspects and / or one or more features and combinations thereof. The invention may include, for example, one or more of the features and / or combinations of the above-described aspects as recited in the appended claims. [Brief description of the drawings]
[0025] The above and / or other aspects and advantages of embodiments of the present invention will be more readily understood from the following detailed description taken in conjunction with the accompanying drawings. [Figure 1] FIG. 1 is an illustration showing a medical device and a controller in accordance with an exemplary embodiment. [Figure 2A] 2 is a block diagram of the medical device and controller of FIG. 1 and another device in accordance with an exemplary embodiment. [Figure 2B] 2 is a block diagram of the medical device and controller of FIG. 1 and another device in accordance with an exemplary embodiment. [Figure 2C]2 is a block diagram of the medical device and controller of FIG. 1 and another device in accordance with an exemplary embodiment. [Diagram 3] FIG. 1 is an illustration of signals transmitted from a medical device and a controller, according to an exemplary embodiment. [Figure 4] FIG. 1 is an illustration of signals transmitted from a medical device and a controller, according to an exemplary embodiment. [Diagram 5] FIG. 1 is an illustration of signals transmitted from a medical device and a controller, according to an exemplary embodiment. [Figure 6A] FIG. 1 is an illustrative diagram showing a first use example of a medical device requesting an audible notification generated by another device, according to an exemplary embodiment. [Figure 6B] FIG. 1 is an illustrative diagram showing a first use example of a medical device requesting an audible notification generated by another device, according to an exemplary embodiment. [Figure 6C] FIG. 1 is an illustrative diagram showing a first use example of a medical device requesting an audible notification generated by another device, according to an exemplary embodiment. [Figure 7A] FIG. 11 is an illustrative diagram showing a second use example of a medical device requesting a vibration notification generated by another device, according to an exemplary embodiment. [Figure 7B] FIG. 11 is an illustrative diagram showing a second use example of a medical device requesting a vibration notification generated by another device, according to an exemplary embodiment. [Figure 7C] FIG. 11 is an illustrative diagram showing a second use example of a medical device requesting a vibration notification generated by another device, according to an exemplary embodiment. [Figure 8A] FIG. 11 is an illustrative diagram showing a third example use of a medical device to request an audible and / or vibration notification generated at another device and sending a message to yet another device via cellular communication in accordance with an exemplary embodiment. [Figure 8B] FIG. 11 is an illustrative diagram showing a third example use of a medical device to request an audible and / or vibration notification generated at another device and sending a message to yet another device via cellular communication in accordance with an exemplary embodiment. [Figure 9] 11 is a flowchart illustrating the operation of a medical device to request a notification generated at another device, according to an example embodiment. [Figure 10] 11 is a flowchart illustrating the operation of at least one other device to generate a requested notification, according to an example embodiment.
[0026] Throughout the drawings, like reference numbers will be understood to refer to like elements, features and structures. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings.
[0028] Problems are overcome and advantages are realized by the exemplary embodiments described below: A wearable medical device communicates a request for indication generation (e.g., alarm / notification of a particular wearable medical device condition) by another wearable or portable handheld device. The wearable medical device is configured with a Bluetooth (BT) stack that allows the device to pair with a controller in a securely coupled relationship, but transmits less secure signals (e.g., a request to generate a notification) to other devices (e.g., a BT-enabled headset or smartwatch) using the more ubiquitous standard BT protocol in broadcast mode. The wearable medical device communicates said request for indication generation using the standard BT protocol. This allows the wearable medical device to be used by a variety of devices for alarm / notification generation with additional security against unintended control actions of the wearable medical device by other devices, not just the controller with which it is paired using its own BT protocol.
[0029] Referring to FIG. 1, an exemplary drug delivery system 10 is shown having a wearable medical device 12 and a controller 14 with a display 24 or other user interface. As described herein, according to an exemplary embodiment, the medical device 12 can be used with a dedicated controller 14 or a smartphone with an app 14 configured to operate as the controller 14, and the medical device 12 can be connected, directly or indirectly, through its controller 14 to other devices 16 or smartphone apps 16 that provide additional functionality. These other devices 16 or smartphone apps 16 can be associated with one or more BAN devices, such as, for example, blood glucose meters, smart watches, motion monitors, Bluetooth headsets, etc. The medical device 12, the dedicated controller 14 or device control app 14 in the smartphone, and the other devices 16 or smartphone apps 16 that provide additional functionality are configured to have communication links with each other and, optionally, with additional devices in a LAN, WAN, or Internet cloud, while minimizing the possibility of eavesdropping attacks, such as MITM and malicious attacks in which the control of the medical device 12 is undesirably altered by another device. For example, as described below in connection with exemplary embodiments, the medical device 12 and controller 14 can use a secure BLE-based intra-device communication protocol for secure control operations such as drug delivery, and a standard device-to-device Bluetooth® protocol (e.g., legacy Classic Bluetooth®) can be used to pair the medical device 12 with the controller device 14 and / or device 16 (e.g., a Bluetooth® headset or earpiece or smart watch) to simply generate notifications or exchange information (e.g., status or log data) but not control configuration or administration operations of the medical device 12 (e.g., do not specify or set bolus amounts, start and end pump delivery operations, or provide sensitive device data such as delivered drug amounts).
[0030] The medical device 12 may be a disposable insulin delivery device (IDD) 12 for single patient use configured for continuous subcutaneous delivery of insulin at set variable basal (24-hour) rates and bolus (on-demand) doses, for example, for management of patients with type 2 diabetes mellitus (T2DM) requiring insulin therapy. However, it should be understood that the medical device 12 may be any on-body medical device (e.g., a wearable infusion pump or continuous glucose meter) or BAN medical device (e.g., a portable glucose meter, a smartphone with a medical condition management app, an on-body device, a smart watch, or a wireless controller dedicated to a wearable fitness and health monitor). However, it should also be understood that if the medical device 12 is a drug delivery device, it may be used to deliver any type of fluid and is not limited to insulin delivery.
[0031] The IDD 12 addresses the unmet needs of many type 2 patients who take multiple daily injections (MDI), who require an unobtrusive, simple, cost-effective insulin delivery alternative to traditional complex insulin pumps. As shown in Figures 1, 2A and 2B, the IDD 12 is part of System 10, an advanced insulin delivery system for use by patients with T2DM. The IDD 12 is configured for 24-hour use in all environments typically inhabited by the target user. The IDD 12 is configured to allow the patient-user to wear the IDD for a period of three days (up to 84 hours). The IDD 12 has four main functions: providing a user-set daily basal insulin rate, providing a user-set bolus insulin amount, providing manual bolus insulin doses, and generating system status and notifications.
[0032] As described below, the IDD 12 communicates wirelessly with its controller (i.e., hereafter referred to as wireless controller (WC 14)) via a Bluetooth® Low Energy (BLE) interface. In addition to operational data of the IDD, the IDD 12 sends feedback to the WC 14 when it detects problems with the IDD (e.g., memory corruption, low or no reservoir, low battery). The WC 14 is configured to program the IDD 12 to provide the patient with daily basal insulin rates and bolus or prandial insulin amounts. The WC 14 is also configured to provide status information regarding the system 10. The WC 14 also enables connection to a BLE wireless connected device interface (BWCDI) of an external device 16 for data exchange. Thus, the WC 14 can send notifications, or optionally requests for the generation of IDD 12 data, to the external device 16 via the BWCDI.
[0033] An important feature supported by the communications software of system 10 is wireless communication between the WC 14 and the IDD 12, so that the IDD 12 can provide feedback to the WC 14 and the user can wirelessly control insulin delivery by the IDD 12 via the WC 14 in a simple and unobtrusive manner. If the IDD 12 feedback to the WC 14 indicates an issue with the IDD (e.g., an IDD malfunction or problem), a notification may need to be generated and provided to the user. The notification may be, for example, a visual alert, such as a display on a graphical user interface screen or activation of a light emitting diode (LED) provided on the IDD 12 or WC 14. However, a visual alert may be confusing to some users, especially if an alert is generated on the IDD 12 and the IDD 12 is obscured by the user's clothing or if the user has a visual impairment.
[0034] Therefore, there is a need to provide enhanced notification to users of wearable medical devices. In accordance with exemplary embodiments, several exemplary enhanced notification methods and associated devices are described below. An example IDD 12 and an example WC 14 are described below with reference to Figs. 2A-10. It should be understood that the enhanced notification methods in the exemplary embodiments can be used with different medical devices 12 (e.g., IDDs) and controllers or WCs 14 having configurations, functions, and operations different from those shown and described with reference to Figs. 2A-10. As described herein, the exemplary IDD 12 is disposable. Therefore, there is also a need for enhanced notification operations of the IDD 12 that do not increase the complexity and cost of the IDD.
[0035] In the illustrated embodiment shown in FIG. 2A, the IDD 12 has a pumping mechanism 52, wireless communication with the WC (e.g., via RF circuitry 54 having a matching circuit and an antenna), and a microcontroller 60 configured to control pump operation. The IDD has a bolus button 64 for manual delivery of medication in addition to programmed medication delivery. The pumping mechanism 52 includes a reservoir 76 for storing a fluid medication (e.g., insulin) to be delivered to a patient wearing the IDD via a cannula 68, and a pump 72 for controllably delivering a specified amount of medication from the reservoir through the cannula. The reservoir 76 can be filled via a septum 78 using a syringe. The IDD has a manual insertion mechanism 66 for inserting the cannula 68 into the patient. However, the processor 60 can be configured to operate an optional drive circuit to automate operation of the insertion mechanism 66 to deploy the cannula 68 into the patient. Additionally, the IDD 12 may optionally include a fluid sensor 74 or a pressure sensor 70, for example, for occlusion detection. The LED 62 may be operated by the microcontroller 60 to turn on or flash during one or more pump operations, such as during reservoir priming. As noted above, the LED may be obscured by the user's clothing or positioned on the IDD such that it is not visible after the IDD is attached to the user's skin. The IDD 12 is powered from a battery and regulator, as shown at 58. When the IDD 12 is initialized (e.g., when powered on and begins pairing with the WC 12), a bolus button 64, when activated by the user, wakes the IDD 12 from a power-saving shelf mode. In the illustrated embodiment, the IDD 12 does not include a user interface other than the wake-up button, as such addition of a touch screen or other display screen to the IDD 12 would disadvantageously increase its cost and possibly its form factor size.
[0036] In the illustrated embodiment shown in Figure 2B, the WC 14 may be implemented as a dual microprocessor component having 1) a WC main processor (WCMP) 30, and a WC communications processor (WCCP) 32. However, it should be understood that the WC 14 may be configured as a single processor device. The two processors 30, 32 communicate with each other via a serial peripheral interface (SPI). The two processors 30, 32 may also interrupt each other via two interrupt pins, M_REQ_INT and S_REQ_INT.
[0037] Referring to FIG. 2B, the WCMP 30 is connected to user interface (UI) components such as a liquid crystal display with touch screen 24, one or more buttons 28, and optional indicators 26 (e.g., speaker, vibration circuit, LED, buzzer). The WCCP 32 is connected to radio frequency (RF) components 38 (e.g., antenna and matching circuit) and is primarily responsible for the WC 14's wireless communication with the IDD 12. However, it should be understood that the RF components 38 may comprise one or more antennas and associated circuitry for communicating with other devices 16 via different communication protocols. The WC 14 is designed to be non-field usable (i.e., there are no parts that need to be inspected, adjusted, replaced, or maintained by the user), except for a replaceable alkaline battery 34 for power. A non-volatile memory (e.g., flash memory) 36 is provided in the WC for storing delivery and status data received from the IDD 12, such as delivery date and amount.
[0038] With continued reference to FIG. 2B, the LCD with capacitive touchscreen 24 serves as a visual interface for the user by rendering visual and graphical output (e.g., system information, instructions, visual notifications, user configuration, data output, etc.) to the user and by providing a visual interface for the user to enter input (e.g., device operational inputs such as IDD pairing and setup and dosing, and configuration parameters, etc.). The WC display with capacitive touchscreen 24 detects at least single-touch gestures across its display area. For example, the touchscreen is configured to recognize user tactile inputs (taps, swipes, button presses) to enable navigation within UI screens and applications. Through certain user interactions, the touchscreen 24 assists in the execution of certain system functions (i.e., setting up and pairing the IDD 12 with the WC 14, administering insulin, providing a user with a medication history, and deactivating and replacing the IDD with another IDD, etc.). The WC 14 also includes a button 28, such as a device wake-up button that, when activated by the user, wakes the WC 14 from a power-saving sleep mode. The WC 14 may also have an LED 26 to indicate a low battery condition (eg, indicating a low battery condition when 12 hours or less of use remain).
[0039] The WC 14 radio frequency (RF) interface with the IDD 12 is based on, for example, Bluetooth low energy or BLE-based communication protocols, although other wireless communication protocols can be used. In the example drug delivery system 10, the WC 14 and the IDD 12 communicate wirelessly within a distance of up to 10 feet or about 3 meters utilizing the ISM band from 2400 MHz to 2480 MHz spectrum. The WC 14 communicates with the IDD 12 while the IDD is attached to the body outdoors. The WC 14 is the central device or master, and the IDD 12 is the peripheral device or slave. Whenever the WCPM 30 transmits information to or retrieves information from the IDD 12, it does so by interacting with the WCCP 32, which in turn communicates with the IDD 12 over the BLE link via respective RF circuits 54 and 38, as shown in Figures 2A and 2B, respectively.
[0040] 2C is a block diagram illustrating an example device 16. The device 16 can be, for example, a smartphone, a smartwatch, a Bluetooth-enabled health and / or fitness monitoring device, a Bluetooth-enabled headset or earpiece, a Bluetooth-enabled wireless device 16. The device 16 includes a processor and memory 80, which may be integrated or separate components. The device 16 can have, for example, a Bluetooth-enabled wireless communication interface 84 and an optional cellular communication interface 82. The device 16 can also have a different user interface, such as one or more of a microphone 88, a touch screen 86 or keypad or other user input device, an audio signal output device (e.g., a speaker or buzzer) 90, and / or another indicator 92, such as a vibration circuit. The WC 14 communicates with the device 16 over a BLE link, for example, via the respective RF circuitry and the BLE wireless interface.
[0041] According to one aspect of the exemplary embodiment, the WC 14 (e.g., its WCCP 32) and the IDD 12 may communicate according to a specific in-device pairing protocol and various operations to mitigate the risk of the WC 14 pairing with an unintended IDD 12', or vice versa, the intended IDD 12 pairing with an unintended WC 14', as described, for example, in the publicly owned PCT published application. US Pat. No. 6,399,323 and US Pat. No. 6,399,323 are incorporated herein by reference. As defined herein, "in-device" refers to a WC 14 that is paired and coupled with one particular medical device 12 (e.g., the IDD 12). An unintended pairing scenario may cause unintended operation or control of the pump mechanism 52, resulting in over-infusion of insulin that may be harmful to the patient. According to another aspect of the exemplary embodiment, the WC 14 may also communicate with other devices 16 according to a more ubiquitous inter-device communication protocol (e.g., a protocol more commonly used by different commercially available devices 16), thereby allowing the WC 14 to transmit less sensitive data than medical device control commands to various devices 16. As defined herein, "inter-device" refers to a WC 14 that can transmit selected IDD 12 information with one or more other devices 16.
[0042] For example, Bluetooth® Low Energy (BLE), marketed as Bluetooth® Smart, is a wireless technology for establishing packet-based wireless networks between wireless devices operating in the 2.4 GHz to 2.4835 GHz frequency range, and consumes significantly less power than conventional Bluetooth® devices, sometimes called Classic Bluetooth® devices. Low-power wireless devices conforming to the Bluetooth® Smart specification are advantageous for healthcare applications, since they are expected to operate for long periods on button or coin batteries. Bluetooth® Smart Ready devices are wireless devices with dual protocol stacks that can communicate with conventional Classic Bluetooth® devices as well as Bluetooth® Smart devices. For example, a smartphone equipped with an IDD control app 16 can be equipped with Bluetooth® SmartReady operations that enable it to communicate with not only traditional classic Bluetooth® devices 16 such as activity monitors or continuous glucose monitors (CGMs), but also personal devices such as an IDD 12 that have Bluetooth® Smart operations, e.g., enabling pairing using a specific in-device pairing protocol and limiting the devices 14 from which the IDD 12 can exchange pump operation data and receive control commands.
[0043] An illustrative example of a particular intra-device pairing protocol for pairing the IDD 12 with the WC 14 will now be described with reference to Figures 3, 4 and 5. According to an illustrative embodiment, as described below, the intra-device pairing protocol has particular advertisement and scan window periods, and corresponding intra-device pairing software is provided to the IDD 12 and the WC 14 for a secure coupled relationship. It should be understood that the timing described with reference to Figures 3, 4 and 5 is for illustrative purposes, and timing specifications may vary depending on the design and inputs used for a particular device pairing application. As also described below, the legacy Classic Bluetooth® pairing protocol, which is commonly used and available between devices, various devices 16, may alternatively be used for non-coupled communications between the IDD 12 and the WC 14, which may require less security than, for example, distribution device control communications.
[0044] FIG. 3 shows an example of IDD 12 advertising and WC 14 scanning before intra-device pairing. Upon wake-up and before pairing, every 250 ms (+ / - 10%), as shown at 106, the IDD 12 advertises with an IDD startup advertising data packet 100 and waits 3 ms (+ / - 10%) for a possible response from the WC 14. At the request of the WCMP 30, the WCCP 32 starts communication by starting to scan for IDD advertisements every 746 ms (+ / - 10%) 104 during a scan window 102 of approximately 505 ms (+ / - 10%). At the end of the scan period 104, if the WCCP 32 does not detect an advertising packet 100 within the transport layer timeout period, the WCCP stops scanning and sends a NACK response with a transmission timeout error code. If no advertisement is detected, the WCCP 32 goes to sleep.
[0045] The WC14 can determine whether a particular type of device 12 is in its vicinity. For example, the IDD12 start-up advertisement data can include IDD identification information (e.g., selected dynamic and / or static parameters, or values identifying the type of device, such as the manufacturer and / or model or other characteristics) such that the WC14 can be configured to pair only with devices or IDDs having specified IDD identification information identifying information, and not with other devices having specified IDD identification information identifying information. Thus, if the WCCP32 determines that the IDD12 start-up advertisement data has IDD identification information associated with, for example, that particular manufacturer, the WC14 can pair with the advertising IDD12. If not, the WCCP32 continues scanning.
[0046] FIG. 4 shows an example of IDD 12 advertising and WC 14 scanning after pairing. After intra-device pairing, and optionally when the IDD 12 is not actively pumping, the IDD advertises with IDD periodic data packets 100 at a selected interval 108 (e.g., every 1 second (+ / -10%)). The IDD periodic data packets can provide an alert code or other data indicating a condition that requires the generation of a notification to the user, or other indication of a request for notification. After each advertisement 100, the IDD 12 waits 30 ms (+ / -10%) for a possible response from the WC 14. After pairing, at the request of the WCPM 30, the WCCP 32 begins communication by starting to scan for IDD advertisements every 746 ms (+ / -10%) 104 during a scan window 102 of 505 ms (+ / -10%).
[0047] FIG. 5 shows an example of IDD 12 advertising and WC 14 scanning while pumping. If the IDD 12 is delivering a drug such as insulin, it can optionally advertise every 500 ms for 2 seconds at the end of the dispense stroke 112. Although not shown in FIG. 6, during the rest period between the IDD draw period 110 and the dispense period 112, the IDD 12 still attempts to advertise if possible. When the IDD 12 is pumping, at the request of the WCMP 30, the WCCP 32 begins communication by starting to scan for IDD advertisements every 746 ms (+ / - 10%) 104 during a scan window 102 of 505 ms (+ / - 10%).
[0048] In the illustrated example of Figures 3, 4, and 5, the in-device wireless protocol implemented by the WC 14 and its paired IDD 12 configures the IDD 12 to only accept control commands from the paired WC 14, such as wireless commands to deliver insulin or configure dosage, or to only transmit sensitive device data or information (e.g., delivered drug amount) to the paired WC 14. This bonded specific in-device communication relationship between the WC 12 and the IDD 14 ensures that other devices cannot control the operation of the IDD 12 or receive sensitive data or information for safety and security reasons, and this bonded specific in-device communication relationship remains intact until the IDD is deactivated. After deactivation of the IDD, the WC 14 is free to pair with a new IDD 12. However, at any time, the WC 14 is preferably only allowed to pair with one IDD 12. If the WC 14 is a smartphone rather than a dedicated wireless controller, the smartphone may be configured with a medical device control app 14 that controls the pairing and resulting binding relationship of the smartphone with only one IDD 12 at a time.
[0049] However, it should be understood that the standard or legacy Classic Bluetooth® protocol can be used by the IDD 12 to pair with a WC or smartphone 14, and optionally with another device 16 (e.g., a smart watch or a Bluetooth® enabled headset or earpiece), or by the WC 14 to pair with another device 16 simply to exchange medical device data that does not require the same binding relationship restrictions as the intra-device pairing protocols described above in connection with Figures 3, 4 and 5. For example, if the IDD 12 is simply using a Bluetooth® link to request the WC 14 or other devices 16 to generate notifications, then the IDD 12 does not transmit sensitive IDD operational status data or receive commands, but rather uses a generic device-to-device protocol (e.g., legacy Classic Bluetooth®) to pair with another device 14, 16 that supports the same protocol and to request notifications. To transmit less sensitive information, such a legacy Classic Bluetooth® enabled connection would be advantageous because it would not need to restrict the device 16 with which the IDD 12 is paired or require specific non-standard intervals, thus allowing the IDD 12 and the WC 14 and / or secure medical device to communicate with each other. There is no need for software on the other device 16 to support a specific intra-device protocol for wireless connectivity with the required level of security for device operation. In other words, the IDD 12 and WC 14 can be equipped with a secure intra-device BLE-based communication protocol for safe drug delivery control operation, and a common device-to-device and standard Bluetooth® protocol (e.g., legacy classic Bluetooth) can be used to pair the IDD 12 with the device 14 and / or a device 16 (e.g., a Bluetooth® earpiece or smartwatch) that only receives requests for notifications regarding IDD operational issues or collects status or log data from the IDD 12.
[0050] The medical device 12, the dedicated controller 14, and the smartphone with the medical device controller app 14 are each configured to implement at least two different wireless communication protocols for exchanging data or signals that are characterized as having at least two different levels of security requirements. For example, with reference to Figures 2A, 2B, and 2C, the RF component 54 of the medical device 12, the RF component 38 of the dedicated controller 14, or a similar RF component of the smartphone, may be equipped with antennas and matching circuits as necessary to accommodate at least two different wireless communication protocols. For example, the wearable medical device 12 is configured with a BT stack that allows the device 12 to pair with its controller 14 in a secure binding relationship, but to transmit signals requiring less security (e.g., requests to generate notifications) to other devices (e.g., BT-enabled headsets or smartwatches) 16 using the more ubiquitous standard BT protocol in broadcast mode. The medical device 12, the controller 14, or the medical device control app 14 for the smartphone are programmed or otherwise configured to determine when to use the two different wireless communication protocols depending on the type of operation and / or the type of information exchanged. For example, the medical device 12 and controller or control app 14 may be programmed or otherwise configured to constrain the medical device's configuration, control operations, and associated data and signals (e.g., setting dosage amounts, commands to begin and end delivery operations, amount of drug delivered) to communicate via the more secure of two different wireless communication protocols (e.g., specific intra-device protocols).
[0051] For example, data related to configuration and control operations that require more secure communications is provided with the metadata or stored in a designated memory location that indicates that the more secure of the two communications protocols is required for its exchange between the medical device 12 and the controller or control app 14, and to preclude communications to devices 16 that do not also use the same secure over-the-air protocol, such as a particular intra-device protocol. Similarly, device 12 requests to generate notifications, or log or historical data, designated as less sensitive than the device 12 configuration and control data, is provided with the metadata or stored in a designated memory location that indicates that the less secure of the two communications protocols can be used to communicate the notification generation request or to transmit log data from the medical device 12 to the controller or control app 14 and / or device 16 and / or from the controller or control app 14 to the device 16.
[0052] As described above, the LED 62 can be used for notifications. For example, the LED 62 can flash on an important notification of the IDD 12. Important notifications include, but are not limited to, memory corruption of the IDD 12, an empty or nearly empty reservoir condition, pump malfunction such as the IDD 12 pump mechanism 52 not operating during intended insulin delivery, a low IDD battery, or other conditions that lead to the end of the IDD life, etc. Wearable medical devices, such as the patch pump 12, are often worn under the patient's clothing. Thus, if the wearable medical device has an indicator (e.g., the LED 62), the patient's view of the indicator is often obscured by the patient's clothing. Furthermore, even if the visual indicator 62 is not obscured by clothing, the LED notification on the wearable medical device 12 may not be perceived by a patient who is visually impaired, or an elderly or mentally impaired patient. Thus, the tactile and / or auditory indicator 62 can be useful as a tactile indicator for these types of patients, particularly those who are deaf or hard of hearing.
[0053] As shown in Figures 6A to 10, apparatus and methods are provided according to three exemplary embodiments for notifying a patient wearing a medical device when a critical notification occurs. As described below, a medical device 12 (e.g., an IDD) can be configured to (1) use BLE communication from the IDD 12 to generate a request for an audio signal generated at the WC 14 or at another device 16, such as a smartphone or a BT-enabled headset, and / or (2) use BLE communication from the IDD 12 to generate a request for a vibration notification generated at the WC 14 or at another device 16, such as a smartphone, a swartwatch, or a BT-enabled wristband (e.g., a fitness monitor), and / or (3) send a BLE signal from the IDD 12 to the WC 12 or to another device 16, such as a smartphone, a swartwatch, to request that the device 14 or 16 send a message to another person (e.g., a caregiver), for example via the other person's smartphone. One or a combination of these three notification methods can be implemented using the BT stacks of the IDD 12 and WC 14 described above. Furthermore, if the IDD 12 request for notification generation is fulfilled by the WC 14 or by a smartphone 14 configured to control IDD operations, the request may be transmitted using either the intra-device or inter-device BT protocols described above. If the IDD 12 request for notification generation is fulfilled by a device 16 not configured to control IDD operations, the request may be transmitted using a wireless communication protocol that is compatible with the device 16 and that may have less security associated with it, such as the inter-device BT protocol described above.
[0054] The exemplary embodiment realizes many advantages over existing wearable medical devices, including but not limited to ensuring that patients of different sensory and cognitive abilities can receive notifications regarding their medical device 12, especially notifications regarding critical conditions occurring in their device 12. For example, patients can hear an audio signal requested by their medical device 12 (e.g., IDD) and generated by a BT-enabled headset 16 or by a smartphone 14, 16 or WC 14. Patients can feel a vibration requested by the medical device 12 and generated by a BT-enabled wristband 16 or by a smartphone 14, 16 or WC 14. Patients' caregivers can receive messages generated on their devices (e.g., smartphones) in response to a request for the generation of a message by the IDD 12. It would be great to take the right action at the right time. In any case, the exemplary embodiment facilitates that, in response to a timely notification, the patient or caregiver can take the right action regarding the condition of the patient's medical device 12 (e.g., replace the IDD 12 or reset or power it, replace the battery, etc.). Furthermore, by having the medical device 12 simply generate a request for notification to be fulfilled by a different device 14 or 16, the request for notification can be generated and transmitted from the medical device 12 using a wireless communication interface already present in the medical device 12, so there is no need to modify the existing medical device 12 hardware or increase the complexity or cost of the medical device 12. Furthermore, the requested notification can be, for example, an unobtrusive vibration notification from a smartphone or smart wristband, or an audible signal on a BT-enabled headset, so patients can use the enhanced notification provided by the exemplary embodiment without hesitation in public areas. The enhanced notification provided by the exemplary embodiment limits the operation on the third device 16 to only notification and not control of the medical device 12, so security of the medical device 12 (e.g., IDD) and controller 14 (e.g., WC) control operations is maintained.
[0055] FIG. 6A generally illustrates an exemplary medical device 12 (e.g., an IDD) generating a request for an audible notification. With reference to FIG. 6B, the request for an audible notification can be wirelessly transmitted by the IDD 12 to a dedicated WC 14 or directly to a smartphone 14 acting as an IDD controller, the WC or smartphone 14 being configured to generate an audible notification via a speaker and / or buzzer or other sound generating device. As described above, the wireless protocol for transmitting the notification request from the IDD 12 to the controller 14 can be either an intra-device protocol or an inter-device protocol. FIG. 6C illustrates an exemplary embodiment in which the patient does not have a smartphone, but rather uses a dedicated wireless controller 14 with the IDD 12. As shown in FIG. 6C, the IDD 12 can transmit the request for notification to the WC 14 (e.g., using either an intra-device protocol or an inter-device protocol). The WC 14 is then configured to transmit an audible signal to a device 16, such as a BT-enabled headset, for playback to a user (e.g., a diabetic patient using a BT-enabled device for audio signals).
[0056] FIG. 7A generally illustrates an exemplary medical device 12 (e.g., an IDD) that generates a request for a vibration or haptic notification. With reference to FIG. 7B, the request for a vibration or haptic notification can be wirelessly transmitted by the IDD 12 to a dedicated WC 14 or directly to a smartphone 14 acting as an IDD controller, with the WC or smartphone 14 generating the vibration or haptic notification via its vibration device or other haptic indicator. Alternatively, the reusable dedicated WC 14 can be configured without a haptic indicator to minimize its complexity and cost, in which case the WC 14 or the IDD 12 is configured to transmit a request for a haptic notification to a device 16 that includes a haptic indicator. As described above, the wireless protocol for transmitting the notification request from the IDD 12 to the controller 14 can be either an intra-device protocol or an inter-device protocol. To maintain security of the IDD control operations, the wireless protocol for transmitting the notification request from the IDD 12 or controller 14 to the device 16 is via an inter-device protocol that is not configured to transmit or receive IDD control commands or sensitive device data. 7C illustrates an exemplary embodiment in which the patient does not have a smartphone, but rather uses a dedicated wireless controller 14 with the IDD 12. As shown in FIG. 7C, the IDD 12 can send a request for notification to the WC 14 (e.g., using either an intra-device or inter-device protocol). The WC 14 is then configured to send a request for generation of a vibration or other tactile indication to a device 16, such as a smartwatch or other smart wristband device, configured to communicate with the WC 14 via Near Field Communication (NFC) or other wireless protocol, which may be BT-enabled or a device-to-device protocol that is not configured to send or receive IDD control commands or sensitive data.
[0057] For example, a patient may use a wristband or wearable patch device 16 that includes a BLE interface, a vibration motor, and a battery. Operating a vibration motor or other tactile indicator electronic circuitry in the remote device 16 to indicate notifications aids hearing-impaired patients, caregivers, and patients wearing the IDD 12 in noisy environments, such as the workplace, characterized by noise from the operation of industrial plants or from other sources (equipment or airplane motors) to ensure access to notifications to timely address critical conditions detected or encountered by the IDD 12.
[0058] FIG. 8A generally illustrates an exemplary medical device 12 (e.g., an IDD) that (1) generates a request for an audible and / or tactile notification and sends the request to a controller 14 or other device that fulfills the request by outputting the requested notification to the patient as described above in connection with FIGS. 6A-7C, and (2) also generates a request to send a message to a caregiver regarding a critical condition of the IDD. For example, the IDD 12 can be paired with a WC 14 or a smartwatch or smartphone 161 that stores the cell number of the caregiver. The IDD 12 and WC 14 can use, for example, BLE to communicate the notification request from the IDD 12 to the WC 14 or smartphone 14 acting as an IDD controller. The WC or other IDD controller 14 can then use cellular communication to complete the call to a device 162 used by a family member or doctor or school nurse or other caregiver. The device 162 then receives the message or notification request and generates the notification, as shown in FIGS. 8A and 8B. This exemplary embodiment is advantageous because messages to the caregiver are sent via a smartphone interface to the wireless controller 14 using BLE or other device-to-device protocols that do not need to be configured to send or receive IDD control commands. The IDD and WC do not require additional hardware for this functionality, thus avoiding added complexity and cost.
[0059] Additionally, the IDD 12 and / or WC or other IDD controller 14 can be configured to allow the patient to select from different modes of enhanced remote notification, such as vibration or tactile notification and / or audible notification, depending on the controller 14 and the device 16 paired with the controller 14 and / or IDD 12. For example, the controller 14 can be programmed to generate a display screen during a setup mode with user prompts that allow the IDD user 12 to indicate criteria such as a paired device selection (e.g., indicating that the paired device 16 has been selected) and a corresponding notification mode (e.g., an audible and / or tactile mode used by that paired device for notifications). For example, any of the medical device 12, controller 14, or other device 16 can be configured to generate user prompts that allow the user, depending on the notification circuitry and capabilities in the controller 14 (i.e., WC or smartphone) and paired device, to select a preferred type of notification to be generated by the controller 14 and / or device 16.
[0060] FIG. 9 is a flow chart illustrating the operation of an exemplary medical device 12 (e.g., IDD 12) to request a notification generated by another device 14, 16, according to an exemplary embodiment. The IDD 12 can be programmed or otherwise configured to perform the operations, for example, and the operations can incorporate all or only a subset of the steps illustrated in FIG. 9. The IDD 12 is paired with a dedicated WC 14 or smartphone 14 configured to control the IDD 12 (block 120). The IDD 12 is configured to monitor conditions occurring within the IDD that require a user to be notified, such as, for example, the critical conditions discussed above (block 122). If a condition requiring user notification is detected (block 124), the IDD 12 is configured to generate a notification request (blocks 128 and 130) for transmission to the controller 14 (block 132) and / or to the other device 16 (block 124). As described above, if the WC 14 has the necessary indicators for the desired notification mode (e.g., auditory or tactile), the IDD 12 can transmit the request for notification using a secure BLE intra-device protocol. Alternatively, the IDD 12 can send a request for notification directly to the device 16 or via the controller 14, for example via a less secure BT device-to-device protocol. Upon receiving a notification (e.g., via the LED 62 or via an enhanced notification generated at a device 14, 16 remote from the IDD 12), the IDD user or caregiver can attempt to resolve the IDD problem that would result in detection of a condition that warrants notification to the user (block 134). If the condition cannot be resolved, the IDD 12 can be disabled (block 136), either manually by the user or caregiver or automatically via its processor 60.
[0061] FIG. 10 is a flow chart illustrating the operation of at least one other device 14, 16 to generate a notification requested by a wearable medical device (e.g., IDD 12), according to an exemplary embodiment. Referring to block 140, the device 14, 16 is programmed or otherwise configured to determine whether a request for a notification has been received (e.g., directly from the IDD 12, or from a WC 14 or smartphone 14 used to control the IDD 12). As described above, the IDD can request remote generation of a notification at the device 14 and / or 16 using one or more modes, such as an auditory mode (block 142), a haptic mode (154), and a messenger mode (block 166). For example, it should be understood that the device 14, 16 may operate either only in an auditory mode or a haptic mode for notifications, or in a different combination of a subset of all modes, or in all available modes, depending on how the IDD 12, WC 14, and / or device 16 are configured.
[0062] 10, blocks 144 and 156, if the medical device 12 (e.g., the IDD) is controlled by the smartphone 14 (as opposed to, e.g., a dedicated WC without cellular operation, or limited indicators such as an LCD display only), the smartphone 14 can fulfill the notification request of the IDD 12 by generating an audible notification (block 146) and / or a haptic notification (block 158), respectively. On the other hand, with reference to blocks 148 and 160 of FIG. 10, if, for example, the IDD 12 is controlled by a dedicated WC 14, the WC 14 can fulfill the notification request of the IDD 12 by generating a notification (block 150) and / or a haptic notification (block 162), respectively, depending on the hardware and software configuration for generating the indication. Alternatively, with reference to blocks 152 and 164 of FIG. 10, the IDD 12 or the WC 14 can pair with another device 16, for example, using a device-to-device wireless protocol, and request the generation of a notification at that device 16. For example, the IDD 12 or WC 14 can instruct a BT-enabled headset to generate an audible notification (block 152). The IDD 12 or WC 14 can instruct a BT-enabled smartwatch or other BT wristband to generate a haptic notification (block 164). Thus, a device 14, 16 (e.g., a smartphone, a WC, a BT headset, a smartwatch, a BT-enabled wristband, or other device 16 with an indicator) can receive a request for a notification directly from the IDD 12 or from the IDD, depending on how the IDD 12 and / or controller 14 are configured to generate notifications or indications, and can generate the requested notification using its indicator hardware and / or software.
[0063] 10, block 166, the WC or smartphone 14 controlling the IDD 12 may store the number of the caregiver and operate in messenger mode to send notifications (e.g., via cellular communication) to the caregiver in response to receiving a notification request from the IDD 12. If the IDD 12 and / or WC 14 indicates an end of life status of the IDD 12, the request fulfillment process shown in FIG.
[0064] It will be understood by those skilled in the art that the present disclosure is not limited in its application to the details of construction and the arrangement of components described below or illustrated in the drawings. The embodiments herein are capable of other embodiments and can be implemented or carried out in various ways. It is also understood that the expressions and terms used herein are for the purpose of description and should not be considered as limiting. The use of "including", "comprising" or "having" and variations thereof herein is meant to encompass the items listed thereafter, as well as additional items, and equivalents thereof. Unless otherwise limited, the terms "connected", "coupled" and "mounted" and variations thereof herein are used broadly to encompass direct and indirect connections, couplings, and attachments. Furthermore, the terms "connected" and "coupled" and variations thereof are not limited to physical or mechanical connections or couplings. Furthermore, terms such as top, bottom, bottom, and upper surface are relative and are used to aid in illustration, but are not limiting.
[0065] Components of the example devices, systems, and methods provided in accordance with the illustrated embodiments may be implemented at least in part in digital electronic circuitry, analog electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof. These components may be implemented as a computer program product, such as a computer program, program code, or computer instructions tangibly embodied in an information medium or machine-readable storage device for execution by, or to control the operation of, a data processing apparatus, such as a programmable processor, a computer, or multiple computers.
[0066] The computer program may be written in any type of programming language, including compiled or interpreted languages, and the computer program may be deployed in any type, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program may be arranged to be executed on one computer or multiple computers at one site, or may be distributed across multiple sites and interconnected by a communication network. Also, functional programs, codes, and code segments for achieving the exemplary embodiments may be readily interpreted as being within the scope of the present invention by those skilled in the art to which the exemplary embodiments pertain. The method steps associated with the exemplary embodiments may be performed by one or more programmable processors that execute computer programs, codes, or instructions to perform functions (e.g., by manipulating input data and / or generating output). The method steps and apparatus of the exemplary embodiments may also be implemented by and as special purpose logic circuitry, such as, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC).
[0067] The various example logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed by a general purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or other such configuration.
[0068] Processors suitable for the execution of a computer program include, by way of example, both general purpose and special purpose microprocessors, and any one or more processors of any kind of digital computer. Typically, a processor receives instructions and data from a read-only memory and / or a random access memory. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer also includes one or more mass storage devices for storing data, such as, for example, magnetic, magneto-optical, or optical disks, or is operatively coupled to receive data from or transfer data to them, or both.
[0069] Suitable information media for embodying computer program instructions and data include, by way of example, semiconductor memory devices such as Electrically Programmable Read Only Memory or ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory devices, and all forms of non-volatile memory, including data storage disks (magnetic disks, internal hard disks or removable disks, magneto-optical disks, CD-ROM and DVD-ROM disks, etc.) The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.
[0070] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0071] The above description and illustrations are intended to be illustrative only and are not intended to be limiting in any manner, except as set forth in the following claims. It is particularly noted that those skilled in the art may readily combine the various technical aspects of the various elements of the various exemplary embodiments described above in many other ways.
Claims
1. A medical device for a user, comprising: a radio frequency (RF) circuit configured to exchange RF signals with a second device; A memory device; a processing device coupled to the RF circuitry and the memory device and configured to detect at least one specified notification condition in the medical device, generate a request for notification in response to detecting the at least one specified notification condition, and wirelessly transmit the request to the second device via the RF circuitry to prompt the second device to activate an indicator remote from the medical device; Including, The second device is at least one device selected from a controller and a smartphone, and is wirelessly paired with the medical device, the second device having at least one indicator selected from an audible indicator and a tactile indicator; the second device is paired with a third device, the medical device is connected directly or indirectly to the third device via the second device, and the third device comprises at least one indicator selected from an audible indicator and a tactile indicator; a second communication protocol used by the processing device to pair with at least one of the second and third devices and to transmit information selected from configuration data, medical device operational data, and control signals for operating the medical device, the second communication protocol being used by the processing device to pair with at least one of the second and third devices and to transmit information selected from status data of the medical device and notifications about the medical device, the second communication protocol being used by the processing device to pair with at least one of the second and third devices and to transmit information selected from configuration data, medical device operational data, and control signals for operating the medical device, the second communication protocol being used by the processing device to pair with at least one of the second and third devices and to transmit information selected from status data of the medical device and notifications about the medical device, the second communication protocol requiring less wireless security than the secure information.
2. The medical device of claim 1, wherein the medical device is a wearable device.
3. 10. The medical device of claim 1, wherein the third device is selected from the group consisting of a smart watch, a Bluetooth enabled headset, a portable monitoring device, and a Bluetooth enabled wristband device.
4. 13. The medical device of claim 1, further comprising a user interface, wherein the processing device is configured to operate the user interface to generate a user selection prompt that guides the user to configure notification preferences based on criteria selected from a selection of a paired device and a corresponding notification mode, the selection of the paired device prompting the user to indicate at least one device paired with the medical device, and the notification mode prompting the user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for the notification.
5. 1. A device for generating a notification from a medical device, comprising: At least one indicator; a radio frequency (RF) circuit configured to exchange RF signals with the medical device; A memory device; a processing device coupled to the at least one indicator, the RF circuit, and the memory device and configured to wirelessly receive a request for notification from the medical device via the RF circuit, wherein the medical device generates the request for notification in response to detecting at least one designated notification condition, and performs a notification operation selected from generating an audible signal via the at least one indicator, wirelessly transmitting a request via the RF circuit to a third device to generate an audible signal, generating a vibration notification signal via the at least one indicator, and wirelessly transmitting a request via the RF circuit to the third device to generate a vibration notification signal; A device further comprising a user interface, wherein the processing device is configured to operate the user interface to generate a user selection prompt that guides a user to configure notification preferences based on criteria selected from a selection of paired devices and corresponding notification modes, wherein the selection of paired devices prompts the user to indicate at least one device paired with the medical device, and the notification mode prompts the user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for the notification, and wherein the paired devices are selected from the medical device, the third device, and a fourth device.
6. The device of claim 5, wherein the device is at least one device selected from a controller and a smartphone, wirelessly paired with the medical device, and wirelessly transmitting the request to the third device via the RF circuit, the third device being selected from the group consisting of a smart watch, a Bluetooth enabled headset, a portable monitoring device, and a Bluetooth enabled wristband device.
7. 1. A method for generating a notification from a medical device, comprising: configuring the medical device to detect at least one specified notification condition; configuring the medical device to generate a request for notification in response to detection of at least one specified notification condition; transmitting the request wirelessly to a second device including an indicator, the second device activating the indicator in response to the request; Including, and generating a user selection prompt to guide the user to configure notification preferences based on criteria selected from a selection of paired devices and corresponding notification modes, wherein the selection of paired devices prompts the user to indicate at least one device paired with the medical device, and the notification mode prompts the user to select a mode selected from an audible mode and a tactile mode to be used by the paired device for the notification.
8. 8. The method of claim 7, wherein the indicator is an audio output device configured to output an audible output signal.
9. 8. The method of claim 7, wherein the second device is selected from the group consisting of a mobile phone, a Bluetooth enabled earpiece, a smart watch, a portable communication device, a portable computing device, and a portable wireless controller configured to control the medical device.
10. 8. The method of claim 7, wherein the at least one specified notification condition is selected from the group consisting of a life condition of the medical device, a corrupted memory in the medical device, a nearly empty reservoir in the medical device, an empty reservoir in the medical device, and a low battery in the medical device.
11. 1. A method for generating a notification from a medical device, comprising: receiving, at a second device, a request for notification from the medical device, the medical device being configured to generate the request for notification in response to detecting at least one specified notification condition; operating the second device to perform a notification action, the notification action being selected from generating an audible signal via at least one indicator, wirelessly sending a request to a third device to generate an audible signal, generating a vibration notification signal via at least one indicator, and wirelessly sending a request to the third device to generate a vibration notification signal; Including, and generating, via a device selected from the medical device, the second device, and the third device, a user selection prompt that guides the user to configure notification preferences based on criteria selected from a selection of paired devices and corresponding notification modes, wherein the selection of paired devices prompts the user to indicate at least one device paired with the medical device, the notification mode prompts the user to select a mode selected from an audible mode and a tactile mode to be used by the paired devices for the notification, and the paired devices are selected from the second device, the third device, and a fourth device.
12. 12. The method of claim 11, further comprising the third device activating an indicator in response to receiving the request sent from the second device.
Citation Information
Patent Citations
Telemedicine device alarm
JP2014502448A
Method for on-body fluid delivery using primary user interface that can be connected to primary patch pump
JP2018027339A
Devices used in connection with continuous analyte monitoring that provide the user with one or more notifications, and related methods
US20150119667A1
Infusion management system
WO2017159683A1
Systems, apparatuses and methods for device pairing having range control and unintended device coexistence detection
WO2018183036A1
