Claims for Patent: 11,173,259

Summary for Patent: 11,173,259

Title:	Drug delivery device with electronics and power management
Abstract:	A system may limit the number of times an inhalation device transmits inhalation data to a single time to reduce the battery usage of the inhalation device. The system may include an inhalation device that has medicament and an electronics module. The system may limit the number of times the inhalation device transmits new inhalation data to any mobile device to a single time by causing the server to receive the new inhalation data from one of the mobile devices and causing the server to transmit the new inhalation data to other of the mobile devices prior to the other mobile devices transmitting a request for the new inhalation data to the inhalation device. The inhalation device may include a Quick Response (QR) code, and a mobile application may determine at least one of a medication type or a number of doses of the inhalation device from the QR code.
Inventor(s):	Calderon Oliveras; Enrique (Barcelona, ES), Kesten; Amir (Har Adar, IL)
Assignee:	Norton (Waterford) Limited (Waterford, IE)
Application Number:	16/921,193
Patent Claims:	1. A system comprising: a cloud-based server comprising a processor, memory, and a communication circuit; an inhaler comprising a mouthpiece, medicament, and an electronics module, the electronics module comprising a processor, memory, and a communication circuit; a first mobile application residing on a first mobile device, the first mobile device comprising a processor, a communication circuit, and memory, and the first mobile application configured to cause the processor of the first mobile device to: send a request for inhalation data to the inhaler; receive the inhalation data from the inhaler, the inhalation data associated with a timestamp; and transmit the inhalation data and timestamp to the cloud-based server; and a second mobile application residing on a second mobile device, the second mobile device comprising a processor, a communication circuit, and memory, and the second mobile application configured to cause the processor of the second mobile device to: transmit a request to the cloud-based server that includes a timestamp of the most recent inhalation data of the inhaler that is stored on the second mobile device in response to entering a connected mode with the inhaler and prior to causing the second mobile device to transmit a request for inhalation data to the inhaler; and receive the inhalation data of the inhaler from the cloud-based server in response to the request, wherein the timestamp associated with the inhalation data is subsequent to the timestamp of the most recent inhalation data of the inhaler that is stored on the second mobile device. 2. The system of claim 1, wherein the system is configured to limit the number of times the inhaler transmits the inhalation data to any mobile device to a single time. 3. The system of claim 1, wherein the second mobile application is configured to cause the second mobile device to transmit a product identification (ID) associated with the inhaler or a patient ID associated with a patient of the inhaler to the cloud-based server prior to the second mobile application receiving the inhalation data of the inhaler from the cloud-based server. 4. The system of claim 1, wherein the second mobile application is configured to cause the processor of the second mobile device to periodically transmit the request to the cloud-based server that comprises the timestamp of the most recent inhalation data of the inhaler that is stored on the second mobile device. 5. The system of claim 1, wherein the second mobile application is configured to cause the second mobile device to transmit a request to the inhaler, receive second inhalation data from the inhaler, and transmit the second inhalation data and an associated timestamp to the cloud-based server; and wherein the first mobile application is configured to transmit a request to the cloud-based server that includes an indication of a last synchronization time between the first mobile application and the inhaler, and receive the second inhalation data and the associated timestamp of the inhaler from the cloud-based server, wherein the timestamp associated with the second inhalation data is subsequent to the last synchronization time between the first mobile application and the inhaler. 6. The system of claim 1, wherein the electronics module of the inhaler is configured to: start a counter in response to the electronics module being changed from an off state to an active state for the first time; record the inhalation data in response to a use of the inhaler by the user; associate a counter value with the inhalation data; and send the inhalation data and the counter value to the first mobile device; and wherein the first mobile application is configured to cause the processor of the first mobile device to determine the timestamp using the counter value, wherein the timestamp indicates a local mean time of the inhalation data based on the time zone of the first mobile device. 7. The system of claim 1, wherein the inhaler is configured to dispense discrete doses of the medicament, and wherein the medicament comprises one of: albuterol sulfate, 117 microgram (mcg) of albuterol sulfate per discrete dose; fluticasone propionate, 55 mcg, 113 mcg, or 232 mcg of fluticasone propionate per discrete dose; or fluticasone propionate combined with salmeterol xinafoate, 55 mcg, 113 mcg, or 232 mcg of fluticasone propionate, and 14 mcg of salmeterol xinafoate per discrete dose. 8. The system of claim 1, wherein the medicament comprises one of albuterol sulfate, fluticasone propionate or furoate, beclomethasone dipropionate, or fluticasone propionate or furoate combined with salmeterol. 9. The system of claim 1, wherein the inhaler further comprise a Quick Response (QR) code; and wherein the first mobile device further comprises a camera, and the first mobile application is configured to cause the processor of the first mobile device to: receive an image of the QR code of the inhaler using the camera of the first mobile device; determine a product identifier (ID) of the inhaler based on the image of the QR code; determine a dosing schedule of the inhaler using the product ID; and generate an alert indicating that a scheduled dose is due based on the dosing schedule of the inhaler. 10. A system comprising: a cloud-based server comprising a processor, memory, and a communication circuit; an inhaler comprising a mouthpiece, medicament, and an electronics module, the electronics module comprising a processor, memory, and a communication circuit; a first mobile application residing on a first mobile device, the first mobile device comprising a processor, a communication circuit, and memory, and the first mobile application configured to cause the processor of the first mobile device to: send a request for inhalation data to the inhaler; receive the inhalation data from the inhaler, the inhalation data associated with a timestamp; and transmit the inhalation data and timestamp to the cloud-based server; and a second mobile application residing on a second mobile device, the second mobile device comprising a processor, a communication circuit, and memory, and the second mobile application configured to cause the processor of the second mobile device to: transmit a request to the cloud-based server for the inhalation data of the inhaler in response to detecting a user login event to the second mobile application and prior to causing the second mobile device to transmit a request for the inhalation data to the inhaler; and receive the inhalation data of the inhaler from the cloud-based server in response to the request. 11. The system of claim 10, wherein the inhaler further comprise a Quick Response (QR) code; and wherein the first mobile device further comprises a camera, and the first mobile application is configured to cause the processor of the first mobile device to: receive an image of the QR code of the inhaler using the camera of the first mobile device, wherein the QR code provides a product identifier (ID) of the inhaler; determine one or more of a medication type or a strength of the medication based on the product identifier; determine that the inhaler is not compatible with the first mobile application or the user based on the medication type or the strength of the inhaler; and generate an error message on a display device of the first mobile device based on the inhaler being not compatible with the mobile application or the user. 12. The system of claim 11, wherein the first mobile application is configured to cause the processor of the first mobile device to: send the medication type or the strength of the inhaler to the cloud-based server; and receive an indication of the user's compatibility with the medication type or the strength of the inhaler from the cloud-based server. 13. The system of claim 11, wherein the first mobile application is further configured to cause the processor of the first mobile device to reject a pairing process of the inhaler with the first mobile device based on the inhaler being not compatible with the first mobile application. 14. The system of claim 10, wherein the inhaler further comprise a Quick Response (QR) code, but the inhaler does not comprise an actuator, button, or switch to initiate a communication pairing process with the first mobile device. 15. The system of claim 14, wherein the first mobile application is further configured to cause the processor of the first mobile device to: receive an image of the QR code of the inhaler using a camera of the first mobile device; determine a communication passkey that is unique to the inhaler based on the QR code; and transmit the communication passkey to the electronics module of the inhaler to enable communication between the electronics module and the first mobile application. 16. The system of claim 15, wherein the communication passkey comprises a product identifier and a Bluetooth Low Energy (BLE) passkey. 17. The system of claim 10, wherein the second mobile application is configured to cause the second mobile device to transmit a product identification (ID) associated with the inhaler or a patient ID associated with a patient of the inhaler to the cloud-based server prior to the second mobile application receiving the inhalation data of the inhaler from the cloud-based server. 18. The system of claim 10, wherein in response to entering a connected mode with the inhaler, the second mobile application is configured to cause the second mobile device to transmit the request to the cloud-based server prior to causing the second mobile device to transmit a request for inhalation data to the inhaler. 19. The system of claim 10, wherein the system is configured to limit the number of times the inhaler transmits the inhalation data to any mobile device to a single time. 20. The system of claim 10, wherein the second mobile application is configured to cause the processor of the second mobile device to periodically transmit a request to the cloud-based server that comprises a timestamp of the most recent inhalation data of the inhaler that is stored on the second mobile device. 21. The system of claim 10, wherein the inhaler further comprise a Quick Response (QR) code; and wherein the first mobile device further comprises a camera, and the first mobile application is configured to cause the processor of the first mobile device to: receive an image of the QR code of the inhaler using the camera of the first mobile device; determine a product identifier (ID) of the inhaler based on the image of the QR code; determine a dosing schedule of the inhaler using the product ID; and generate an alert indicating that a scheduled dose is due based on the dosing schedule of the inhaler. 22. A system comprising: a cloud-based server comprising a processor, memory, and a communication circuit; an electronics module configured to be attached to and removed from an inhaler, the electronics module comprising a processor, memory, and a communication circuit; a first mobile application residing on a first mobile device, the first mobile device comprising a processor, a communication circuit, and memory, and the first mobile application configured to cause the processor of the first mobile device to: send a request for usage data to the electronics module; receive the usage data from the electronics module, the usage data associated with a timestamp; and transmit the usage data and timestamp to the cloud-based server; and a second mobile application residing on a second mobile device, the second mobile device comprising a processor, a communication circuit, and memory, and the second mobile application configured to cause the processor of the second mobile device to: transmit a request to the cloud-based server for the usage data of the electronics module in response to detecting a user login event to the second mobile application and prior to causing the second mobile device to transmit a request for the usage data to the electronics module; and receive the usage data of the inhaler from the cloud-based server in response to the request. 23. The system of claim 22, wherein the second mobile application is configured to cause the second mobile device to transmit a product identification (ID) associated with the electronics module or a patient ID associated with a patient of the electronics module to the cloud-based server prior to the second mobile application receiving the usage data of the electronics module from the cloud-based server. 24. The system of claim 22, wherein the second mobile application is configured to cause the processor of the second mobile device to periodically transmit a request to the cloud-based server that comprises a timestamp of the most recent usage data of the electronics module that is stored on the second mobile device.