Various embodiments of the present invention generally relate to medication management. More specifically, some embodiments of the present invention relate to systems and methods for portable management and monitoring of an eye drop medication regiment.
Approximately thirty percent of medication prescriptions are never filled. In addition, approximately fifty percent of medications for chronic disease are not taken as prescribed. This lack of adherence has dramatic effects on health. Non adherence has been estimated to cost the U.S. health care system $200 billion annually. In ophthalmology, the problem of noncompliance is particularly significant in the management of chronic conditions such as glaucoma where a strict adherence to the medication plan is vital for preventing visual loss and blindness. Almost seventy-five percent of patients admit to some form of noncompliant behavior, over thirty percent do not fill their prescriptions, and nearly fifty percent discontinue prescribed drops within six months.
While forgetfulness is one barrier to medication adherence, it is not the only barrier. In addition, taking the medication at the wrong time, stopping too early or taking the wrong dose also represent other serious barriers. Unfortunately, there are no effective systems for managing adherence to a medication plan which can be vital for preventing visual loss and/or blindness.
Embodiments of the present invention will be described and explained through the use of the accompanying drawings in which:
The drawings have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be expanded or reduced to help improve the understanding of the embodiments of the present invention. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present invention. Moreover, while the invention is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the invention to the particular embodiments described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the appended claims.
Various embodiments of the present invention generally relate to medication management. More specifically, some embodiments of the present invention relate to systems and methods for portable management and monitoring of an eye drop medication regiment. In some embodiments, a portable medication management and monitoring system is disclosed for eye drop instillation in ocular chronic conditions. Various embodiments of the system provide for a management care system that reminds (e.g., with visual or audible indicators) the user of the time and date of each eye drop instillation, notifies the user if any doses are being missed, records for medication management purposes each instillation, sends progress reports to the third-parties (family members or doctors), and provides a refill notification to the pharmacist. One advantage of the reminder system provided by embodiments of the present invention is the improvement in compliance with medication treatment routines and is advantageous for people who struggle remembering to instill their eye drops. The solution also improves the clinical outcomes.
Various embodiments of the device can include one or more of the following components: (a) a jacket that goes around an eye drop bottle; (b) tactile sensors to detect the user's fingers and generate data to activate the system; (c) motion sensors to detect the motion of the medication bottle when it is grabbed and moved by the user; (d) a wireless communication module to send and receive data to a computer and a portable communication device; and/or (e) a compartment for holding the electronic components.
Various embodiments of the present invention are compatible with a web-based medication adherence system. A user can log into the web-based system and load data regarding a medication regiment manually on a web site. This information can optionally be shared or sent to an eye care provider (e.g., for tracking medication adherence) or pharmacist (e.g., for automatic medication refills). In addition, some embodiments of the present invention provide for different types of external and/or device-based reminding systems such as automated text messaging, phone calls, or auditory (beeper) and visual reminders such as a flashing or changing color LED light. For example, in one embodiment, the text messaging system may allow a profile to be created the first time a user logs into the web-based system. The system may request or automatically populate information such as a phone number or email address
Various embodiments of the present invention provide for proactive and reactive reminding systems that require users to send back confirmation receipts (e.g., a text reply or simply an intuitive gesture using the mobile phone). For example, moving the mobile phone to simulate the gesture of eye drop instillation would say, “Yes, I took my eye drop”. Engaging the patient in the process improves and sustains the motivation for medication adherence. The system uses a small battery or can be charged on a small station.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. While, for convenience, embodiments of the present invention are described with reference to portable medication management, embodiments of the present invention are equally applicable to various other types of liquid dispensing and tracking needs outside of the medical industry.
Moreover, the techniques introduced here can be embodied as special-purpose hardware (e.g., circuitry), as programmable circuitry appropriately programmed with software and/or firmware, or as a combination of special-purpose and programmable circuitry. Hence, embodiments may include a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), magneto-optical disks, ROMs, random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or other types of media/machine-readable mediums suitable for storing electronic instructions.
Brief definitions of terms, abbreviations, and phrases used throughout this application are given below.
The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct physical connection or coupling. Thus, for example, two devices may be coupled directly, or via one or more intermediary media or devices. As another example, devices may be coupled in such a way that information can be passed therebetween, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which connection or coupling exists in accordance with the aforementioned definition.
The phrases “in some embodiments,” “according to some embodiments,” “in the embodiments shown,” “in other embodiments,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one implementation of the present invention, and may be included in more than one implementation. In addition, such phrases do not necessarily refer to the same embodiments or different embodiments.
If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.
The term “module” refers broadly to a software, hardware, or firmware (or any combination thereof) component. Modules are typically functional components that can generate useful data or other output using specified input(s). A module may or may not be self-contained. An application program (also called an “application”) may include one or more modules, or a module can include one or more application programs.
Tactile sensor 130 can be used to provide a touch input interface (e.g., to detect the finger of a user). The user's touch can then activate/deactivate (i.e., turn on-off) the device. In some embodiments, the sensors can also detect and record other types of data such as pulse and heart rate. Drop detector sensor 140 can detect when a drop of liquid leaves the bottle. Drop sensor 140 could be an optical (e.g., LED/phototransistor) sensor capable of detecting if a drop has been released from the bottle. In these cases, when a drop is released from the bottle, the drop will refract a beam and produce a signal on the output. Drop sensor 140 may be placed at the top of the expansion pack and could be activated only in a specific position of the bottle to conserve power.
Electronic module compartment 150 can house one or more modules and/or components (e.g., processors, communication devices, integrated electronics, memory storage devices, batteries, etc.) of the medication management device. For example, in some embodiments, electronic module compartment 150 can include a gesture recognition module. The gesture recognition module can be used for detecting and providing the hand and bottle motion and position. In order to avoid false and unwanted motion measurement, in some embodiments, the gesture recognition module may be activated only when the tactile sensors detect the user's fingers' touch.
As another example, a wireless communication module can be used to send and receive data to and from a computer and portable communication devices. An embedded controller module can include signal preprocessing electronics. Still yet, the device may include Bluetooth wireless technology to send and load data to a mobile device or computer.
In some embodiments, jacket 100 may have integrated electronics and components embedded throughout. As illustrated in
As the user moves the bottle during movement operation 530, the motion sensors are capable of detecting the bottle's motion and activating a drop sensor during activation operation 540. In some embodiments, if no movement is detected within a certain amount of time (e.g., ten seconds), the motion detectors may be deactivated. Once the drop sensor is activated, monitoring operation 550 determines if a drop has been released from the bottle. Data (e.g., number of drops, time, date, etc.) may then be transmitted to a medication adherence system or a communications device for processing and/or tracking.
As the user moves the bottle during movement operation 730, the motion sensors are capable of detecting the bottle's motion and activating a drop sensor during activation operation 740. Once the drop sensor is activated, monitoring operation 750 determines if a drop has been released from the bottle. Drop data (e.g., number of drops, time, date, etc.) may then be transmitted to a medication adherence system or a communications device for processing and/or tracking.
If motion-sensing operation 720 does not detect any movement of the bottle by the user, holding operation 770 determines if the user continues to hold the one or more tactile sensors (e.g., for more than five or ten seconds). Once a holding threshold has been exceeded, a pulse rate measuring algorithm may be activated during pulse rate activation operation 780 to measure the user's pulse rate, heart rate, or even blood chemistry. The pulse rate data can then be transmitted to another device and/or monitoring system.
Embodiments of the present invention include various steps and operations, which have been described above. A variety of these steps and operations may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software, and/or firmware.
In conclusion, various embodiments of the present invention provide novel systems, methods and arrangements for management and monitoring of an eye drop medication regiment. While detailed descriptions of one or more embodiments of the invention have been given above, various alternatives, modifications, and equivalents will be apparent to those skilled in the art without varying from the spirit of the invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combinations of features and embodiments that do not include all of the described features.
This application is a continuation of U.S. application Ser. No. 14/281,001, filed May 19, 2014, entitled “PORTABLE MANAGEMENT AND MONITORING SYSTEM FOR EYE DROP MEDICATION REGIMENT,” which is a 371 of International Application No. PCT/US2013/066450, filed Oct. 23, 2013, entitled “PORTABLE MANAGEMENT AND MONITORING SYSTEM FOR EYE DROP MEDICATION REGIMENT,” which is a continuation of U.S. application Ser. No. 13/844,233, filed Mar. 15, 2013, entitled “PORTABLE MANAGEMENT AND MONITORING SYSTEM FOR EYE DROP MEDICATION REGIMENT,” which claims priority from U.S. Provisional Application No. 61/717,559, filed Oct. 23, 2012, entitled “PORTABLE MANAGEMENT AND MONITORING SYSTEM FOR EYE DROP MEDICATION REGIMENT,” all of which are incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5152424 | Weinreb et al. | Oct 1992 | A |
7949426 | Handfield et al. | May 2011 | B2 |
9728068 | Engelhard et al. | Aug 2017 | B2 |
20040039355 | Gonzalez | Feb 2004 | A1 |
20040188290 | Sterns | Sep 2004 | A1 |
20040204674 | Anderson et al. | Oct 2004 | A1 |
20060071825 | Demos | Apr 2006 | A1 |
20070024465 | Howell | Feb 2007 | A1 |
20090045078 | Gelardi et al. | Feb 2009 | A1 |
20090240215 | Humayun | Sep 2009 | A1 |
20090259204 | Galdeti et al. | Oct 2009 | A1 |
20090306633 | Trovato et al. | Dec 2009 | A1 |
20100286634 | Marx | Nov 2010 | A1 |
20110025830 | Mcnamer et al. | Feb 2011 | A1 |
20110264028 | Ramdas et al. | Oct 2011 | A1 |
20120143152 | Hunter | Jun 2012 | A1 |
20120176506 | Tajiri | Jul 2012 | A1 |
20120222979 | Baym et al. | Sep 2012 | A1 |
20140062918 | Chen et al. | Mar 2014 | A1 |
20140081100 | Muhsin et al. | Mar 2014 | A1 |
20140228783 | Kraft | Aug 2014 | A1 |
20140257206 | Fateh | Sep 2014 | A1 |
20140262918 | Chu | Sep 2014 | A1 |
20140276476 | Fateh | Sep 2014 | A1 |
20160155267 | Bean et al. | Jun 2016 | A1 |
20160220180 | Fateh | Aug 2016 | A1 |
20160239635 | Fateh | Aug 2016 | A1 |
20170173262 | Veltz | Jun 2017 | A1 |
20170340846 | Gramann et al. | Nov 2017 | A1 |
20170357775 | Ekin | Dec 2017 | A1 |
20180042417 | Brown et al. | Feb 2018 | A1 |
Number | Date | Country |
---|---|---|
1759398 | Apr 2006 | CN |
201173771 | Dec 2008 | CN |
1656923 | May 2006 | EP |
2418049 | Mar 2006 | GB |
H09226785 | Sep 1997 | JP |
2003117988 | Apr 2003 | JP |
2007525276 | Sep 2007 | JP |
2008532568 | Aug 2008 | JP |
2006511263 | Apr 2009 | JP |
5028637 | Jul 2012 | JP |
2013529117 | Jul 2013 | JP |
2014513612 | Jun 2014 | JP |
2014528793 | Oct 2014 | JP |
2016537810 | Dec 2016 | JP |
0124690 | Apr 2001 | WO |
2004028420 | Apr 2004 | WO |
2011113028 | Sep 2011 | WO |
2013043607 | Mar 2013 | WO |
2014004437 | Jan 2014 | WO |
2014066546 | May 2014 | WO |
2015002492 | Jan 2015 | WO |
Entry |
---|
Non-Final Office Action dated Mar. 30, 2018 for U.S. Appl. No. 14/621,293 of Fateh, S. filed Feb. 12, 2015. |
Notification of Registration and Granting a Patent Right dated Mar. 28, 2018 for Chinese Patent Application No. 201380067442.1, 18 pages. |
Restriction Requirement dated Jan. 5, 2018 for U.S. Appl. No. 14/621,293 of Fateh, S. filed Feb. 12, 2015. |
Extended European Search Report dated Dec. 15, 2017 for European Patent Application No. 16744225.0, 9 pages. |
Final Office Action dated Jun. 16, 2016 for U.S. Appl. No. 13/844,233 of Fateh, S, filed Mar. 15, 2013. |
Final Office Action dated Jun. 9, 2017 for U.S. Appl. No. 13/844,233 of Fateh, S, filed Mar. 15, 2013. |
Non-Final Office Action dated Dec. 1, 2016 for U.S. Appl. No. 13/844,233 of Fateh, S, filed Mar. 15, 2013. |
Non-Final Office Action dated Oct. 30, 2015 for U.S. Appl. No. 13/844,233 of Fateh, S., filed Mar. 15, 2013. |
Second Office Action dated Feb. 21, 2017, for Chinese Patent Application No. 201380067442.1, 18 pages. |
Supplementary European Search Report dated Oct. 9, 2017 for European Patent Application No. 16749887.2, 8 pages. |
Third Office Action dated Sep. 19, 2017, for Chinese Patent Application No. 201380067442.1, 10 pages. |
Extended European Search Report dated May 27, 2016 for EP Patent Application No. 13848685.7, 9 pages. |
First Office Action dated Mar. 25, 2016, for Chinese Patent Application No. 201380067442.1, 21 pages. |
International Search Report and Written Opinion dated Jun. 30, 2016, for International Application No. PCT/US2016/017563 filed Feb. 11, 2016, 7 pages. |
International Search Report and Written Opinion dated May 19, 2016, for International Application No. PCT/US16/15784 filed on Jan. 29, 2016, 7 pages. |
International Search Report and Written Opinion of International Application No. PCT/US2013/066450, dated Feb. 14, 2014. |
Non-Final Office Action dated Aug. 29, 2014 for U.S. Appl. No. 14/281,001 of Fateh, S. et al. filed May 19, 2014. |
Notice of Allowance dated Jan. 13, 2015 for U.S. Appl. No. 14/281,001 of Fateh, S. et al. filed May 19, 2014. |
Restriction Requirement dated Aug. 7, 2015 in Co-Pending U.S. Appl. No. 13/844,233 of Fateh, S., filed Mar. 15, 2013. |
U.S. Appl. No. 14/608,704 of Fateh, S., filed Jan. 29, 2015. |
U.S. Appl. No. 14/621,293 of Fateh, S., filed Feb. 12, 2015. |
Final Office Action dated Jul. 26, 2018 for U.S. Appl. No. 14/621,293 of S. Fateh filed Feb. 12, 2015. |
Notice of Allowance dated May 16, 2018 of U.S. Appl. No. 13/844,233 of Fateh, S., filed Mar. 15, 2013. |
Restriction Requirement dated Jul. 2, 2018 for U.S. Appl. No. 14/608,704 of Fateh, S. filed Jan. 29, 2015. |
Number | Date | Country | |
---|---|---|---|
20150173945 A1 | Jun 2015 | US |
Number | Date | Country | |
---|---|---|---|
61717559 | Oct 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14281001 | May 2014 | US |
Child | 14639989 | US | |
Parent | PCT/US2013/066450 | Oct 2013 | US |
Child | 14281001 | US | |
Parent | 13844233 | Mar 2013 | US |
Child | PCT/US2013/066450 | US |