System and method for monitoring and engaging patients to facilitate medication adherence

Abstract

A system and method are provided for improving medication adherence of a patient, comprising: determining whether a time window for a medication intake event for a patient has occurred; determining a status of the patient by activating a sensor to generate echo signals reflected from objects in a designated space including the patient and a medication location containing a prescribed medication; determining whether the patient's behavior indicates that the patient is available to complete the event; sending to a patient device a first notification instructing the patient to complete the event by taking the prescribed medication; determining whether the patient has interacted with the medication location; sending to the patient device a confirmation request asking the patient to indicate whether the event is completed; and responding to the confirmation reply by storing the completed event and sending a notification to a physician device indicating completion of the event.

Description

HOL-0001-01-USSYSTEM AND METHOD FOR MONITORING AND ENGAGING PATIENTS TO FACILITATE MEDICATION ADHERENCETECHNICAL FIELD

[0001] The present disclosure relates to medication adherence, and more particularly to systems and methods for monitoring patient medication adherence using non-invasive sensor technology and a care management platform to encourage and confirm medication adherence.BACKGROUND

[0002] Ensuring medication adherence by patients on a medication regimen is important for managing and improving patient health. Patients prescribed medication for self-administration frequently fail to consistently take the prescribed medication in the prescribed dose and at the prescribed time(s). Sometimes patients forget to take their medication. Other times, patients intentionally fail to selfadminister their medication because of actual or potential side effects. However, it is known that consistent adherence to a medication regimen improves outcomes, especially for patients with chronic conditions such as heart failure or chronic obstructive pulmonary disease (“COPD”). Some studies indicate that approximately 22% of patients with heart failure and approximately 60% of patients with COPD fail to consistently adhere to their medication regimens.

[0003] During monitoring of a chronic patient it is vital for the physician and / or medical personnel or clinical team to understand the patient’s adherence to the prescribed medication regimen. Such physicians or other care givers, however, need to understand not only the patient’s medication adherence behavior, but also other health-related behaviors such as exercise routine, sleep quality, fatigue and various symptoms and urination patterns. Conventionally, the physician must ask the patient about all of these parameters during a patient interaction either during an office visit or during continuous monitoring. Of course, most patients can provide only vague descriptions of their health-related behaviors, and sometimes even intentionally omit or mischaracterize certain important information. Accordingly, the typical patient interview often results in providing the physician with incomplete- 1 -DSI366492S46W2.IHOL-0001-01-US and / or inaccurate information, and such interviews consume valuable time during each patient interaction I visit.

[0004] Moreover, when patients, especially patients with chronic conditions, fail to consistently adhere to their medication regimens, they are much more likely to be readmitted to a hospital or other healthcare facility - a time consuming, expensive and inconvenient result. Additionally, caregivers (e.g., family members or others) for patients on a medication regimen often spend considerable time and effort trying to ensure that the patient adheres to the medication regimen.

[0005] As such, it is clear that improvements are needed to the conventional approach of patient care management especially regarding medication adherence. More specifically, it would be desirable to provide a system that ensures patient medication adherence, provides physicians with complete and accurate information about the patient’s health-related behaviors without requiring time consuming patient interviews during visits, reduces unnecessary readmissions, and reduces the burden placed on caregivers for ensuring medication adherence, all while allowing the patient to live comfortably at home.SUMMARY

[0006] In one embodiment, the present disclosure provides a method of improving medication adherence, comprising: determining, by a computing device having a processor and a memory, whether a time window for a medication intake event for a patient has occurred; determining a status of the patient by activating a sensor to transmit signals in a designated space at least periodically occupied by the patient, to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient, and to transmit data reflecting the echo signals via a network to the processor; determining, by the processor from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event; responding, by the processor, to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to a patient application running on a patient device a first medication reminder notification instructing the patient to complete the medication intake event- 2 -DSI366492S46W2.IHOL-0001-01-US by taking the prescribed medication at a general time of day, the patient application displaying the first medication reminder notification to the patient on the patient device; determining, by the processor from the data, whether the patient has interacted with the medication location; responding, by the processor, to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a second medication reminder notification reminding the patient to complete the medication intake event, the patient application displaying the second medication reminder notification to the patient on the patient device; responding, by the processor, to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event; responding, by the processor, to a failure to receive the confirmation reply by sending via the network to at least one of a physician device or a caregiver device a message that the patient failed to complete the medication intake event; and responding, by the processor, to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event. One aspect of this embodiment further comprises pre-calibrating the sensor by installing the sensor in the designated space and analyzing the echo signals to map locations of the objects in the designated space. Another aspect further comprises inputting a medication regimen of the patient into at least one of the patient application or a physician application running on the physician device, the medication regimen including at least one medication intake event. In another aspect, determining, by the processor from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event includes analyzing, by the processor, the data from the sensor reflecting the echo signals to determine whether the patient is approaching a bed in the designated space or the patient is exiting the bed. In another aspect, responding, by the processor, to receipt of the confirmation reply includes waiting, by the processor, for a second time window for a second medication intake event to occur, and responding to an occurrence of the second time window by determining, by the- 3 -DSI366492S46W2.IHOL-0001-01-US processor, a next status of the patient by activating the sensor to obtain further data reflecting the echo signals; determining, by the processor from the further data, whether behavior of the patient indicates that the patient is available to complete the second medication intake event; responding, by the processor, to a determination that the patient is available to complete the second medication intake event by sending via the network to the patient application a third medication reminder notification instructing the patient to complete the second medication intake event; determining, by the processor from the further data, whether the patient interacted with the medication location; responding, by the processor, to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a fourth medication reminder notification reminding the patient to complete the second medication intake event; responding, by the processor, to a determination that the patient has interacted with the medication location by sending via the network to the patient application a second confirmation request asking the patient to activate the button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the second medication intake event; responding, by the processor, to a failure to receive the confirmation reply by sending via the network to at least one of the physician device or the caregiver device a message that the patient failed to complete the second medication intake event; responding, by the processor, to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the second medication intake event and sending a notification via the network to the physician device indicating that the patient completed the second medication intake event. In yet another aspect, the time window is a learned time window based on behavioral patterns of the patient that indicate when medication intake events typically occur. In another aspect, the sensor is a radio frequency interferometer having a plurality of transmit antennae and one or more receive antennae. In another aspect, the physician device and the caregiver device are configured to communicate with the patient device over the network. In another aspect, determining whether the time window for a medication intake event has occurred includes referencing, by the processor, at least one of a typical waking time or a typical sleeping time of the patient learned by the processor through analysis of the data from the sensor over time. In still another aspect, determining whether the- 4 -DSI366492S46W2.IHOL-0001-01-US patient has interacted with the medication location includes determining, by the processor from the data, whether an echo signal is received from one of a reflective device or a reflective surface associated with the medication location. In a variant of this aspect, the one of a reflective device or a reflective surface is mounted to a medication box contained in the medication location.

[0007] In another embodiment, the present disclosure provides a system for improving medication adherence, comprising: a sensor disposed in a designated space at least periodically occupied by a patient, the sensor including one or more transmit antennae configured to transmit signals into the designated space and one or more receive antennae configured to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient; a network in communication with the sensor; a computing device including a processor and a memory, the computing device being in communication with the network and the processor is configured to receive data from the sensor reflecting the echo signals; a patient device running a patient application, the patient device being in communication with the network; and at least one of a physician device running a physician application and a caregiver device running a caregiver application, the at least one of the physician device and the caregiver device being in communication with the network; wherein the processor is configured to: determine a status of the patient by activating the sensor to transmit signals in the designated space, to receive echo signals reflected from the objects in the designated space, and to transmit the data reflecting the echo signals via the network to the processor; determine from the data whether behavior of the patient indicates that the patient is available to complete a medication intake event; respond to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to the patient application a first medication reminder notification instructing the patient to complete the medication intake event by taking the prescribed medication at a general time of day, the patient application displaying the first medication reminder notification to the patient on the patient device; determine from the data whether the patient has interacted with the medication location; respond to a determination that the patient has not interacted with the medication location by sending via the network to the- 5 -DSI366492S46W2.IHOL-0001-01-US patient application a second medication reminder notification reminding the patient to complete the medication intake event, the patient application displaying the second medication reminder notification to the patient on the patient device; respond to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event; respond to a failure to receive the confirmation reply by sending via the network to the at least one of the physician device or the caregiver device a message that the patient failed to complete the medication intake event; and respond to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event. In one aspect of this embodiment, the processor is configured to determine whether behavior indicates that the patient is available to complete the medication intake event by analyzing the data from the sensor reflecting the echo signals to determine whether the patient is approaching a bed in the designated space or the patient is exiting the bed. In another aspect, the processor is configured to respond to receipt of the confirmation reply by waiting for a time window for a second medication intake event to occur, and responding to an occurrence of the second time window by determining a next status of the patient by activating the sensor to obtain further data reflecting the echo signals; determining from the further data whether behavior of the patient indicates that the patient is available to complete the second medication intake event; responding to a determination that the patient is available to complete the second medication intake event by sending via the network to the patient application a third medication reminder notification instructing the patient to complete the second medication intake event; determining from the further data whether the patient has interacted with the medication location; responding to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a fourth medication reminder notification reminding the patient to complete the second medication intake event; responding to a determination that the patient has interacted with the medication location by sending via the network to the patient- 6 -DSI366492S46W2.IHOL-0001-01-US application a second confirmation request asking the patient to activate the button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the second medication intake event; responding to a failure to receive the confirmation reply by sending via the network to the at least one of the physician device or the caregiver device a message that the patient failed to complete the second medication intake event; responding to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the second medication intake event and sending a notification via the network to the physician device indicating that the patient completed the second medication intake event. In another aspect, the processor is further configured to determine whether a time window for the medication intake event has occurred. In a variant of this aspect, the time window is a learned time window based on behavioral patterns of the patient that indicate when medication intake events typically occur. In another variant, the processor is configured to determine whether the time window has occurred by referencing at least one of a typical waking time or a typical sleeping time of the patient learned by the processor through analysis of the data from the sensor over time. In another aspect of this embodiment, the sensor is a radio frequency interferometer. In another aspect, the physician device and the caregiver device are configured to communicate with the patient device over the network. In another aspect, the processor is configured to determine whether the patient has interacted with the medication location by determining from the data whether an echo signal is received from one of a reflective device or a reflective surface associated with the medication location. In a variant of this aspect, the one of a reflective device or reflective surface is mounted to a medication box contained in the medication location. In another aspect, the patient application is configured to generate a menu icon which, when activated, permits the patient to access any of a plurality of pages generated by the patient application, and a notification icon which indicates to the patient an existence of one or more unread notifications. In another aspect, the patient application is configured to generate a daily progress bar that provides a visual indication of a percentage of tasks the patient has completed for a current day. In another aspect, the patient application is configured to generate a reminder pane which notifies the patient of upcoming medication intake events and provides one or more buttons that, when activated, permit the patient to indicate- 7 -DSI366492S46W2.IHOL-0001-01-US whether a medication intake event was completed. In another aspect, the patient application is configured to generate a highlights pane which displays updates of activities completed by the patient In another aspect, the caregiver application is configured to generate a caregiver interface which displays one or more reminders to a caregiver relating to the medication intake event. In another aspect, the physician application is configured to generate a patient identification bar that identifies the patient, and a patient details area that provides at least one of a gender of the patient, an age of the patient, and a date of birth of the patient. In another aspect, the physician application is configured to generate a pending area that indicates a number of pending tasks and notifications for the patient. In another aspect, the physician application is configured to generate a control panel including a patients dashboard button which, when activated, causes the physician device to display a data panel that provides one or more charts indicating one or more behaviors of the patient each day for a desired time period. In another aspect, the physician application is configured to generate an insights panel that provides one or more summary charts depicting data during a desired time period of one or more health related parameters of the patient.

[0008] In yet another embodiment, the present disclosure provides a non- transitory computer readable storage medium with instructions stored thereon configured to cause a processor coupled to a network in communication with a sensor, a patient device, and a physician device to perform functions for improving medication adherence of a patient comprising: determining whether a time window for a medication intake event for the patient has occurred; determining a status of the patient by activating the sensor to transmit signals in a designated space at least periodically occupied by the patient, to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient, and to transmit data reflecting the echo signals via the network to the processor; determining from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event; responding to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to a patient application running on the patient device a first medication reminder notification- 8 -DSI366492S46W2.IHOL-0001-01-US instructing the patient to complete the medication intake event by taking the prescribed medication at a general time of day; determining from the data, whether the patient has interacted with the medication location; responding to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a second medication reminder notification reminding the patient to complete the medication intake event; responding to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event; responding to a failure to receive the confirmation reply by sending via the network to at least one of the physician device or a caregiver device a message that the patient failed to complete the medication intake event; and responding to receipt of the confirmation reply by storing data in a memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above mentioned and other features of the present disclosure, and the manner of attaining them, will become more apparent and the invention itself will be better understood by reference to the following description of embodiments taken in conjunction with the accompanying drawings, wherein:

[0010] FIG. 1 is a conceptual diagram of a system for patient monitoring and care management according to one embodiment of the present disclosure;

[0011] FIG. 2 is a more detailed conceptual diagram of the system of FIG. 1 ;

[0012] FIG. 3A is a front view of a patient device providing a display generated by a patient application according to one embodiment of the present disclosure;- 9 -DSI366492S46W2.IHOL-0001-01-US

[0013] FIG. 3B is a front view of a caregiver device providing a display generated by a caregiver interface according to one embodiment of the present disclosure;

[0014] FIG. 3C is a perspective view of a physician device providing a display generated by a physician interface according to one embodiment of the present disclosure; and

[0015] FIG. 4 is a flow chart of a method of monitoring and engaging patients to facilitate medication adherence.

[0016] Corresponding reference characters indicate corresponding parts throughout the several views. Unless stated otherwise the drawings are proportional and drawn to scale.DETAILED DESCRIPTION

[0017] The embodiments disclosed below are not intended to be exhaustive or to limit the invention to the precise forms disclosed in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art may utilize their teachings.

[0018] Referring now to FIG. 1 , a monitoring and care management system 10 is shown. The system 10 generally includes a sensor 14 disposed in a monitored environment 12 and in communication with a network 16. In certain embodiments, the network 16 is in communication with a patient device 18, a caregiver device 20 and a physician device 22. The environment 12 generally includes one or more rooms in a patient’s 34 home, hereinafter referred to as a designated space 24. The designated space 24 in the following description is a bedroom including a bed 26 and a medication location 28 as is further described below.

[0019] In certain embodiments, the sensor 14 may include a radio frequency (“RF”) interferometer configured to transmit signals using one or more transmit antennae 30 and to receive echo signals via one or more receive antennae 32. The sensor 14 may be configured as the system described in U.S. Patent No. 9,520,051 , the entire disclosure of which being expressly incorporated herein by reference. The- 10 -DSI366492S46W2.IHOL-0001-01-US sensor 14 enables passive, contactless monitoring of patient behavior and provides high-resolution clinical data about the patient’s health status as is further described below. The transmit signals generated by the sensor 14 can penetrate clothes, walls and other objects. The sensor 14 is also configured to communicate with a system computing device 35 including one or more processors (hereinafter, “ the processor 36”) via the network 16. The computing device 35 also includes one or more memory devices (hereinafter, “the memory 37”) which stores data and instructions for execution by the processor 36.

[0020] Regarding the network 16, typically one or more computing devices operate as a server, a computer with large storage devices such as hard disk drives and communication hardware to operate peripheral devices such as printers or modems. Other computing devices, sometimes called workstations, provide a user interface so that users of computer networks can access the network resources, such as shared data files, common peripheral devices, and inter-workstation communication. The computing devices have at least one processor for executing machine instructions, and memory for storing instructions and other information. Many combinations of processing circuitry and information storing equipment are known by those of ordinary skill in these arts. A processor, such as the processor 36, may be a microprocessor, a digital signal processor ("DSP"), a central processing unit ("CPU"), or other circuit or equivalent capable of interpreting instructions and / or performing logical actions on information. Users activate computer programs or network resources to create “processes” which include both the general operation of the computer program along with specific operating characteristics determined by input variables and its environment.

[0021] The memory 37 may include both volatile and non-volatile memory, including temporary and cache, in electronic, magnetic, optical, or other format used to store information. The memory 37 may be a computer readable medium and may be a single storage device or may include multiple storage devices, located either locally with the processor 36 or accessible across the network 16, or partially locally with processor 36 and partially on an external device accessible across the network 16. Computer-readable media may be any available media that may be accessed by the processor 36 and includes one or both of removable and non-removable media.- 11 -DSI366492S46W2.IHOL-0001-01-USBy way of example, computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, servers, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the information and instructions described herein and which may be accessed by the processor 36.

[0022] In one embodiment, the processor 36 communicates data, status information, notifications or a combination thereof to a remote device for storage, analysis, or carrying out predetermined commands. In certain embodiments, the memory 37 may further include operating system software. The memory 37 further includes communications software for communication with a network, such network 16, which may be a local area network, a public switched network, a CAN network, and any type of wired or wireless network. An exemplary public switched network is the Internet. Exemplary communications software includes e-mail software, SMS, Bluetooth communication software, radio frequency communication software, near field communication software and internet browser software. Other suitable software which permits the processor 36 to communicate with other devices across a network may be used.

[0023] As is further described below, the patient device 18 may be any computing device capable of communicating with the network 16. In certain embodiments, the patient device 18 is a mobile computing device such as a tablet, laptop and / or smartphone. In other embodiments, the patient device 18 is a desktop computing device. The patient device 18 may be capable of executing an application specifically designed for performing functions as described herein to function as part of the monitoring and care management system 10. In certain embodiments, the patient computing device 18 is generally carried by or maintained a close distance to a patient such as the patient 34 shown in FIG. 1 .

[0024] Similarly, the caregiver device 20 may be any computing device capable of communicating with the network 16. In certain embodiments, the caregiver device 20 is a mobile computing device such as a tablet, laptop and / or smartphone. In other embodiments, the caregiver device 20 is a desktop computing device. The caregiver device 20 may be capable of executing an applicationDSI366492S46W2.I - 12 -HOL-0001-01-US specifically designed for performing functions as described herein to function as part of the monitoring and care management system 10. In certain embodiments, the caregiver device 20 is generally carried by or maintained a close distance to a caregiver of the patient 34, such as a relative, friend or healthcare professional.

[0025] Likewise, the physician device 22 may be any computing device capable of communicating with the network 16. In certain embodiments, the physician device 22 is a mobile computing device such as a tablet, laptop and / or smartphone. In other embodiments, the physician device 22 is a desktop computing device. The physician device 22 may be capable of executing an application specifically designed for performing functions as described herein to function as part of the monitoring and care management system 10. In certain embodiments, the physician device 22 is operated by a physician or other healthcare professional having a physician-patient relationship with the patient 34.

[0026] In general, the system 10 is configured to monitor, analyze and report information relating to the patient’s 34 adherence to a medication regimen and to engage with the patient 34 via the patient device 18. As is further described below, in certain embodiments a medication regimen is input into the processor 36 and the sensor 14 is trained or pre-calibrated to generate a map of the monitored environment 12, including the location of the bed 26 and the medication location 28. After the system 10 is setup generally in this manner, the processor 36 activates the sensor 14, in certain embodiments on a customized schedule designed to capture movement of the patient 34 during times that have been established or learned by the processor 36 as corresponding to prescribed times for the patient 34 to take medication (i.e., a medication intake event). References herein to “a medical intake event” are intended to cover the patient 34 taking one medication or multiple medications, with or without specific instructions regarding food intake, etc. The sensor 14 transmits signals using the transmit antenna 30 and receives echo or reflected signals from the monitored environment 12, such as from the bed 26, the patient 34 and the medication location 28, at the receive antennae 32. The sensor 14 transmits data representing these signals to the processor 36, which is generally configured to determine from the data whether the patient 34 has gotten out of the bed 26 and walked to the medication location 28. The signals from the sensor 14DSI366492S46W2.I - 13 -HOL-0001-01-US are sufficient to determine whether the patient 34 has accessed the medication location 28 to take the prescribed medication according to the medication regimen. As is further described below, the processor 36 may communicate with the patient device 18 during this process to remind the patient 34 to take medication or obtain confirmation from the patient 34 that the prescribed medication has been taken. As is also further described below, the processor 36 may communicate with the caregiver device 20 and / or the physician device 22 during this process to provide notifications and / or data relating to the medication intake event.

[0027] Referring now to FIG. 2, a conceptual diagram is provided to represent certain functions and data performed and / or generated by the various components of the system 10. As shown, the sensor 14 performs motion and other sensing functions as represented by block 38 and communicates with the processor 36 via the network 16. In performing its functions, the sensor 14, when activated, provides continuous data collection (as indicated by block 40), situational awareness (as indicated by block 42) and data analysis (as indicated by block 44). In block 40, the sensor 14 continuously scans the monitored environment 12 to detect the presence of individuals, determine their location, and monitor their movements, including both macro and micro movements. In block 42, based on the acquired signals at a specific moment, along with data from previous points in time, the processor 36 perceives and interprets what is happening in the monitored environment 12, identifying details such as the number of individuals in the monitored environment 12, their locations, and their states — whether they are in bed, asleep, sleep posture, waking up, sitting, leaving the bed, or heading towards the bathroom etc. In block 44, the processor 36 analyzes the acquired signals at a specific moment, along with data from previous points in time, to derive clinical and behavioral parameters such as: heart rate, respiration, sleep quality, fatigue, coughing, urination routine, etc.

[0028] The patient device 18, in certain embodiments, executes an application or program (hereinafter, “the patient application 46”) which enables the patient device 18 to perform a variety of functions, including communication with the processor 36 via the network 16 and interaction with the patient 34. The patient application 46 enables the patient device 18 to collect data (in addition to the data collected by the sensor 14) by passively gathering data such as the location of the- 14 -DSI366492S46W2.IHOL-0001-01-US patient device 18 and movement steps of the patient 34 (as indicated by block 48), actively gathering data including confirmations from the patient 34 regarding medication adherence, responses to questionnaires about symptoms and status, and entries of additional details such as hospitalization events and measurements like weight, 02 saturation, temperature and blood pressure (as indicated by block 50) and obtaining data from external devices connected via Bluetooth or other connection method to the patient device 18, which share data such as weight, 02 saturation, temperature and blood pressure with the patient device 18 (as indicated by block 52). The patient application 46 further enables the patient device 18 to engage with the patient 34 by providing the ability to communicate with the physician device 22 through “Physician Communication,” which includes messages and questionnaires sent by the clinical team to the patient 34 (as indicated by block 54), providing analytics feedback to the patient 34, which show health, behavioral and adherence data to the patient 34, feedback on medication adherence, sleep quality, task completion, and overall wellness engagement (as indicated by block 56), and providing recommendations to the patient 34 for improving health management, such as adhering to medications, tracking weight, ensuring adequate sleep, encouraging walks, promoting healthy eating habits, and reducing salt intake (as indicated by block 58).

[0029] As is also shown in FIG. 2 and further described below, the processor 36 is configured to provide, via the network 16, analytics and alerts or notifications to a caregiver interface or application (hereinafter, “the caregiver application 60”) executed by the caregiver device 20. Similarly, as shown in FIG. 2 and further described below, the processor 36 is further configured to provide, via the network 16, clinical, behavioral, and wellness data to a physician application 62 executed by the physician device 22. The physician application 62 also enables the physician device 22 to provide feedback to the processor 36 via the network 16.

[0030] Referring now to FIG. 3A, a screenshot is shown of a page generated by the patient application 46 running on the patient device 18. The patient application 46 provides a menu icon 64 for accessing other pages of the patient application 46, and a notifications icon 66 providing the patient 34 an indication of the existence of unread notifications. The patient application 46 further provides a- 15 -DSI366492S46W2.IHOL-0001-01-US daily progress bar 68 that provides a visual indication of the percentage of tasks (e.g., including medication intake events) the patient 34 has completed for the current day. The patient application 46 also includes a reminder pane 70 and a highlights pane 72. The reminder pane 70 includes, in this example, a weight reminder 74, which notifies the patient 34 when it is time to obtain a weight measurement, and a medication reminder 76, which notifies the patient 34 when it is time to take medication and provides buttons that permit the patient 34 to indicate whether the medication for the relevant time frame was taken (taken button 78) or missed (missed button 80). The medication reminder 76 also includes a snooze button 82 that, when activated by the patient 34 causes the medication reminder 76 to be removed and to reappear at a predetermined time in the future. The highlights pane 72 includes, in this example, an activities tracking notification 84 which provides the patient 34 updates on the patient’s 34 physical activity (e.g., hours standing, steps taken, etc.) for the day. The lower portion of the patient application 46 provides a physician icon 86 indicating the patient’s 34 current physician, a goals icon 88, which permits the patient 34 to activate a screen with information about the patient’s 34 health goals, a status icon 90, which permits the patient 34 to activate a screen showing the patient’s 34 performance on a variety of health-related metrics, and an add icon 92, which allows the patient 34 to answer health-related questionnaires and log health events such as hospitalizations, symptoms, and other measurements such as weight, blood pressure, 02 saturation, etc.

[0031] Referring now to FIG. 3B, a screenshot is shown of a page generated by the caregiver application 60 running on the caregiver device 20. The caregiver application 60 provides a menu icon 94 for accessing other pages of the caregiver application 60, and a notifications icon 96 providing the caregiver an indication of the existence of unread notifications. The caregiver application 60, in this example, provides a reminder 98 which informs the caregiver that the patient 34 missed his medications yesterday and asks that the caregiver remind the patient 34 to take his medication today. The reminder 98 includes a remove icon 100 that permits the caregiver to exit the reminder 98 and a sure button 102 that permits the caregiver to notify the system 10 that she will follow up with the patient 34.- 16 -DSI366492S46W2.IHOL-0001-01-US

[0032] Referring now to FIG. 3C, a screenshot is shown of a page generated by the physician application 62 running on the physician device 22, which has a display 63 and one or more input devices 65 such as a keyboard. The physician application 62 provides a menu icon 104 for accessing other pages of the physician application 62, and an identification icon 106 identifying the physician. The physician application 62 also includes a patient identification bar 108 that identifies the patient 34 and a patient details area 110 that provides the gender, age and date of birth of the patient 34. The physician application 62 further includes a pending area 112 that indicates to the physician the number of pending tasks and notifications for the patient 34. The physician application 62 also includes an actions area 114 that includes buttons to allow the physician to manage the patient’s 34 account, send a message to the patient 34, or assign a task to the patient 34.

[0033] The physician application 62 also generally includes a control panel 116, a data panel 118 and an insights panel 120. The control panel 116 includes an administration button 122 which allows the physician to access administrative functions of the physician application 62, a patients dashboard button 124 which displays the screenshot depicted in FIG. 3C, a care plan button 126 which permits the physician to access the care plan for the selected patient 34, a reports button 128 which permits the physician to generate a plurality of different reports, a team button 130 which, when activated, displays the healthcare team associated with the patient 34 to the physician, an organization button 132 which permits the physician to access information relating to the healthcare organization providing medical care to the patient 34, and a help button 134 which permits the physician to access various help and support features of the physician application 62.

[0034] The data panel 118 of the physician application 62 includes a time period drop down 136 which allows the physician to set the desired time period for the data displayed on the data panel 118. In the example shown, the data panel 118 displays charts depicting data during the desired time period of various behaviors of the patient 34, including an awakenings chart 138 which shows the number of times per night the patient 34 awakened, a steps chart 140 which shows the number of steps the patient 34 walked per day, and a sleep chart 142 which shows the number of hours the patient 34 slept per night.- 17 -DSI366492S46W2.IHOL-0001-01-US

[0035] The insights panel 120 includes a time period drop down 144 which allows the physician to set the desired time period for the information displayed on the insights panel 120. In the example shown, the insights panel 120 displays summary charts depicting data during the desired time period of various health related parameters, including a medication adherence chart 146 which shows medication compliance data relating to the patient’s 34 adherence to the medication regimen, a heart rate chart 148 which shows the average heart rate and range of heart rates for the patient 34 during the desired time period, and a steps chart 150 which shows a summary of the patient’s 34 record of achieving a target number of steps per day during the desired time period.

[0036] Referring now to FIG. 4, a flow chart of a method 200 for monitoring and care management according to certain embodiments of the present disclosure is shown. The method 200 begins at the sensor pre-calibration step 202. During the pre-calibration step 202 the sensor 14 is installed and the monitored environment 12 is mapped. More specifically, an installer installs the sensor 14 in the designated space 34 (e.g., a bedroom having a bed 26) of the monitored environment 12. In certain embodiments, the sensor 14 may be installed on a wall or ceiling of the designated space 24. In other embodiments, the sensor 14 may be configured to resemble a lamp or other common object and be placed on a piece of furniture in the designated space 24. The medication location 28 is also within range of the sensor 14 in the designated space 24. During installation, the installer defines the location of the bed 26 and the medication location 28 and activates the sensor 14 which is configured to determine the coordinates of these objects in the designated space 24. In certain embodiments, the sensor 14 may have a range of approximately 40 square meters, so the designated space 24 in such embodiments should be equal to or less than 40 square meters.

[0037] After the pre-calibration step 202, the medication regimen for the patient 34 is inputted into the system 10 in the input medication total prescriptions (“TRX”) step 204. TRX is the number of times an individual can have their drug prescription (Rx) filled. It is calculated as TRX = NRX + refills, with NRX being a new prescription and refills being the number of times a patient can have their prescription refilled. During the input medication TRX step 204, the patient 34 or the- 18 -DSI366492S46W2.IHOL-0001-01-US physician (or other healthcare provider) inputs the medication TRX regimen into either the patient application 46 or the physician application 62. The medication regimen identifies one or medication intake events, wherein each medication intake event includes a prescribed medication, a dosage for the prescribed medication, a general time of day the prescribed medication should be taken, and other information about the medication prescribed to the patient 34 such as whether the medication should be taken with or after a meal. The medication regimen is transmitted to the processor 36 via the network 16 after entry into the patient application 46 or the physician application 62.

[0038] After the pre-calibration step 20 and the input medication TRX step 204 are completed, the method 200 proceeds with the monitoring and management functions of the system 10. More specifically, at the determine patient status step 206 the system 10 activates the sensor 14 to determine the status of the patient 34. The sensor 14 transmits signals via the transmit antennae 30 and the transmitted signals are reflected back after encountering the objects in the monitored environment 12, including the patient 34, the bed 26 and the medication location 28. The reflected signals are received at the receive antennae 32 and then transmitted by the sensor 14 to the processor 36 via the network 16. The processor 36 analyzes the signals using the mapping of the monitored environment 12 to identify the objects. It should be understood that in an alternative embodiment, the sensor 14 is configured to analyze the signals or the processor 36 is incorporated as part of the sensor 14 and the processor 36 analyzes the signals. In other embodiments, the analysis is performed by other processors connected to the network 16 or a combination of the sensor 14, the processor 36 and other processors. In analyzing the stream of data from the sensor 14 in or near real-time, the processor 36 determines whether the patient 34 is going to sleep, waking up, walking or otherwise moving from one place to another in the monitored environment 12, approaching and / or opening the medication location 28, etc. The processor 36 records the patient’s 34 movements and activities along with the time of day of the movements and activities to determine the status of the patient 34 at the various times of day. The data inputted during the input medication TRX step 204, specifically the dosage times for the prescribed medications, permits the processor 36 to anticipate the- 19 -DSI366492S46W2.IHOL-0001-01-US times of day that the patient 34 should open the medication location 28 to take the prescribed medication. Over time, the processor 36 learns the habits of the patient 34 such as waking time and sleeping time and activates the sensor 14 during a time range or time window encompassing the typical waking time and sleeping time of the patient 34. As such, the processor 36 in certain embodiments need not continuously monitor the patient 34 (i.e. , activate the sensor 14) over a 24 hour period.

[0039] In the example described herein, the medication regimen of the patient 34 requires that the patient 34 take medication within a predetermined time period after waking up. Thus, after the patent status is determined by the processor 36 at the determine patient status step 206, the processor 36 determines, at the patient available step 208, whether the data from the sensor 14 indicates that the patient 34 is available to complete a medication intake event in that the data indicates that the patient 34 is waking up. It should be understood, however, that this is simply one example of the general function of determining whether behavior of the patient 34 indicates that the patient 34 is available to complete a medication intake event. For example, for a medication regimen that requires the patient 34 to take a medication before going to bed, the patient available step 208 may entail the processor 36 determining from the data from the sensor 14 whether the patient 34 is approaching the bed 26.

[0040] Returning to the example depicted in FIG. 4, if the processor 36 determines that the patient 34 is not waking up at the patient available step 208, then the method 200 returns to the determine patient status step 206. If, however, the processor 36 determines that the patient 34 is waking up, then the processor 36 sends the patient 34 a first medication reminder notification at step 210. More specifically, the processor 36 generates a first medication reminder notification informing the patient that it is time to take medication and specifically identifying the particular medication and dosage according to the medication regimen inputted during the input medication TRX step 204. The first medication reminder notification is transmitted via the network 16 to the patient device 18, which activates the patient application 46. The patient application 46 then displays a medication reminder 76 such as that shown in FIG. 3A. In other embodiments, the patent application 46 causes the patient device 18 to provide an audible notification to the patient 18 such- 20 -DSI366492S46W2.IHOL-0001-01-US as a voice message and / or alter tone. In certain embodiments where the patient 34 is required to eat prior to taking the medication, the first medication reminder notification includes instructions to the patient 34 to eat breakfast prior to taking the prescribed medication. It should be understood that causing the display of the medication reminder 76 at the send notification step 210 results from actually detecting that the patient 34 has awakened (or other behavior indicating that the patient 34 is available to complete a medication intake event); it is not a scheduled reminder provided daily, which may be provided too early or too late and therefore missed by the patient 34.

[0041] At the track patient step 212, the system 10 determines whether the patient 34 walks to the medication location 28. The system 10, over time, learns the patterns of the patient’s 34 behavior to anticipate when the patient 34 should approach the medication location 28 to take the prescribed medication. For example, the system 10 may learn that when food intake is required before taking a medication, it typically takes the patient 34 a certain amount of time to leave the monitored environment 12 to eat breakfast and return to the monitored environment 12 to take the medication. Thus, at the track patient step 212 the processor 36 may wait a certain amount of time (based on the learned behavior of the patient 34) for the patient 34 to approach the medication location 28.

[0042] At the medication location interaction step 214, the processor 36 determines from the data provided by the sensor 14 whether the patient 34 has opened the medication location 28, walked to a vicinity near the medication location 28, or stopped in the vicinity of the medication location 28 for a predetermined period of time. Hereinafter, any and all of these determinations are referred to as the patient 34 “interacting” with the medication location 28. In certain embodiments, the medication location 28 is a drawer or cabinet door, which the sensor 14 can detect being opened. In some embodiments, the medication location 28 may be equipped with a reflective device or a reflective surface that provides a very clear indication to the sensor 14 whether the medication location 28 is closed or opened. In other embodiments, the medication location 28 may contain a medication box (not shown) with a reflective device or reflective surface. In such embodiments, the processor 36 will not determine that the patient 34 actually accessed the medication if only the- 21 -DSI366492S46W2.IHOL-0001-01-US medication location 28 is opened (e.g., the patient 34 opened the medication location 28 to obtain some other object such as toothpaste). Instead, the processor 36 will only determine that the patient 34 accessed the medication if the medication box was opened.

[0043] If, at the medication location interaction step 214, the processor 36 determines from the data from the sensor 14 that the patient 34 has not interacted with the medication location 28 (e.g., the patient 34 was near the medication location 28 to brush his or her teeth, but did not open the medication location 28), then the processor 36 sends a second medication reminder notification at the send reminder step 216 as described above and the method 200 returns to the track patient step 212. In the event that the patient 34 moves the medication and therefore does not open the medication location 28 to take the medication or even approach the medication location 28, the second medication reminder notification may include an inquiry to the patient 34 about whether the medication location 28 has been moved.

[0044] If, instead, the processor 36 determines that the patient 34 has interacted with the medication location 28, the processor 36 sends a confirmation request to the patient 34 at the send confirmation request step 218. More specifically, the processor 36 generates a confirmation request to send to the patient device 18 via the network 16. The patient device 18 activates the patient application 46 to display a confirmation request similar to the medication reminder 76 shown in FIG. 3A with a taken button 78 (permitting the patient 34 to confirm taking the medication), a missed button 80 (permitting the patient 34 to indicate that the patient 34 missed taking the medication, and a snooze button 82 (permitting the patient 34 to indicate that more time is needed to take the medication). In this manner, the patient 34 is prohibited from being dishonest about medication adherence. In fact, the patient’s 34 knowledge that his or her adherence to a medication regimen is being monitored by the system 10 may provide added motivation to the patient 34 to adhere to the medication regimen.

[0045] At the confirmation received step 220, the processor 36 determines whether the patient 34 responded to the confirmation request indicating that the medication was taken, such as by activating the taken button 78 which causes the patient application 46 to generate a confirmation reply. If the processor 36- 22 -DSI366492S46W2.IHOL-0001-01-US determines that a confirmation reply was not received, then the processor 36 may, in certain embodiments, transmit a message to the caregiver and / or the physician at the notify caregiver / physician step 222 and the method 200 returns to the determine patient status step 206. The message may be similar to the reminder 98 shown in FIG. 3B, but include a prompt to contact the patient 34 to remind the patient 34 to take the prescribed medication.

[0046] If, on the other hand, the processor 36 receives a confirmation reply that the patient 34 has taken the medication, then at the store results step 224 the processor 36 stores data in the memory 37 indicating that the patient 34 took the prescribed medication at a particular time during the current day. Over time, the data stored in the memory 37 establishes a baseline of the behavior of the patient 34. As such, as described herein, the processor 36 can customize the monitoring of the patient 34 according to the baseline behavior of the patient 34. The processor 36 can also identify deviations from the baseline which may indicate one or more potentially significant changes in the patient’s 34 medical condition(s).

[0047] At the send confirmation data step 226, the processor 36 also may send an indication via the network 16 to the physician device 22 that the patient 34 took the prescribed medication at a particular time during the current day. The notification may be registered as a new notification in the pending area 112 as described with reference to FIG. 3C and used by the physician application 62 to update data in the medication adherence chart 146 of the insights panel 120 described above with reference to FIG. 3C. In this manner, the physician is provided with accurate, real-time data about the patient’s 34 medication adherence, the need for asking the patient 34 to provide such information during a medical visit is eliminated and action by the physician based on incomplete or inaccurate data is avoided. Additionally, the processor 36 may send a notification to the caregiver device 20 via the network 16 indicating that the patient 34 took the prescribed medication at a particular time during the current day. The caregiver application 60 may register the notification in the notifications icon 96 as described above with reference to FIG. 3B. Finally, in certain embodiments the processor 36 may also send a notification to the patient device 18 via the network 16 to provide the patient- 23 -DSI366492S46W2.IHOL-0001-01-US34 with a congratulatory message for taking the prescribed medication in a timely fashion.

[0048] After the processor 36 confirms that the patient 34 took the prescribed medication in a timely manner and generates and sends the associated notifications described above, the processor 36 may wait a period of time before again activating the sensor 14 to determine the patient’s 34 status at the determine patient status step 206. Depending upon the medication regimen inputted at the input medication TRX step 204, the patient 34 may only be required to take medication in the morning after waking up and / or eating breakfast. The patient 34 may also, however, be required to take other medications at other times of the day, such as with a mid-day meal or before going to bed. Overtime, the processor 36 learns the behavioral patterns of the patient 34 to determine when each of the applicable medication intake events usually occurs, and can generate a time window (e.g. one hour centered on the learned time for each of the medication intake events) for monitoring the patient 34. The processor 36 then need only activate the sensor 14 during the learned time windows. It should be understood then, in certain embodiments the processor 36 may also wait for the expiration of a learned time window before sending the second medication reminder notification at the send reminder step 216 as described above.

[0049] At the next monitoring time step 228, the processor 36 determines whether the next time window for monitoring the patient 34 has occurred. If not, the processor 36 continues to wait at the next monitoring time step 228. If the next time window has occurred, then the method 200 returns to the determine patient status step 206 where the processor 36 again activates the sensor 14 to monitor the patient 34 as described above. It should be understood that in alternative embodiments the next monitoring time step 228 may be omitted and the processor 36 may immediately cause the sensor 14 to begin monitoring the patient 34 such that the patient’s 34 activity in the monitored environment 12 is essentially continuously monitored. The above-described method (excluding the sensor pre-calibration step 202 and the input medication TRX step 204) may be repeated automatically every day to ensure medication adherence of the patient 34. Of course, if the prescribedDSI366492S46W2.I - 24 -HOL-0001-01-US medications for the patient 34 are changed by the physician or other healthcare provider, then the input medication TRX step 204 would also be repeated.

[0050] In certain embodiment, the system 10 executing the method 200 may periodically generate adaptive questionnaires based on the patient’s 34 behavior to obtain additional health-related information. For example, the processor 36 may send via the network 16 a questionnaire to the patient device 18 once a month asking the patient to provide a generalized assessment of their current health and / or a description of any pain or other potentially significant health parameter that is not readily detected by the system 10 as described above.

[0051] It should also be understood that, unless a term is expressly defined in this patent using the sentence "As used herein, the term ‘term’ is hereby defined to mean..." or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based on any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this patent is referred to in this patent in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, the patent claims at the end of this patent application are not intended to be construed under 35 U.S.C. § 112(f) unless traditional means- plus-function language is expressly recited, such as "means for" or "step for" language being explicitly recited in the claim(s). The systems and methods described herein are directed to an improvement to computer functionality, and improve the functioning of conventional computer systems.

[0052] While this invention has been described as having an exemplary design, the present invention may be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains.DSI366492S46W2.I - 25 -

Claims

HOL-0001-01-USCLAIMSWhat is claimed is:

1. A method of improving medication adherence, comprising: determining, by a computing device having a processor and a memory, whether a time window for a medication intake event for a patient has occurred; determining a status of the patient by activating a sensor to transmit signals in a designated space at least periodically occupied by the patient, to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient, and to transmit data reflecting the echo signals via a network to the processor; determining, by the processor from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event; responding, by the processor, to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to a patient application running on a patient device a first medication reminder notification instructing the patient to complete the medication intake event by taking the prescribed medication at a general time of day, the patient application displaying the first medication reminder notification to the patient on the patient device; determining, by the processor from the data, whether the patient has interacted with the medication location; responding, by the processor, to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a second medication reminder notification reminding the patient to complete the medication intake event, the patient application displaying the second medication reminder notification to the patient on the patient device; responding, by the processor, to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event;- 26 -DSI366492S46W2.IHOL-0001-01-US responding, by the processor, to a failure to receive the confirmation reply by sending via the network to at least one of a physician device or a caregiver device a message that the patient failed to complete the medication intake event; and responding, by the processor, to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event.

2. The method of claim 1 , further comprising: pre-calibrating the sensor by installing the sensor in the designated space and analyzing the echo signals to map locations of the objects in the designated space.

3. The method of claim 1 , further comprising inputting a medication regimen of the patient into at least one of the patient application or a physician application running on the physician device, the medication regimen including at least one medication intake event.

4. The method of claim 1 , wherein determining, by the processor from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event includes analyzing, by the processor, the data from the sensor reflecting the echo signals to determine whether the patient is approaching a bed in the designated space or the patient is exiting the bed.

5. The method of claim 1 , wherein responding, by the processor, to receipt of the confirmation reply includes waiting, by the processor, for a second time window for a second medication intake event to occur, and responding to an occurrence of the second time window by determining, by the processor, a next status of the patient by activating the sensor to obtain further data reflecting the echo signals; determining, by the processor from the further data, whether behavior of the patient indicates that the patient is available to complete the second medication intake event;DSI366492S46W2.I - 27 -HOL-0001-01-US responding, by the processor, to a determination that the patient is available to complete the second medication intake event by sending via the network to the patient application a third medication reminder notification instructing the patient to complete the second medication intake event; determining, by the processor from the further data, whether the patient interacted with the medication location; responding, by the processor, to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a fourth medication reminder notification reminding the patient to complete the second medication intake event; responding, by the processor, to a determination that the patient has interacted with the medication location by sending via the network to the patient application a second confirmation request asking the patient to activate the button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the second medication intake event; responding, by the processor, to a failure to receive the confirmation reply by sending via the network to at least one of the physician device or the caregiver device a message that the patient failed to complete the second medication intake event; responding, by the processor, to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the second medication intake event and sending a notification via the network to the physician device indicating that the patient completed the second medication intake event.

6. The method of claim 1 , wherein the time window is a learned time window based on behavioral patterns of the patient that indicate when medication intake events typically occur.

7. The method of claim 1 , wherein the sensor is a radio frequency interferometer having a plurality of transmit antennae and one or more receive antennae.

8. The method of claim 1 , wherein the physician device and the caregiver device are configured to communicate with the patient device over the network.- 28 -DSI366492S46W2.IHOL-0001-01-US9. The method of claim 1 , wherein determining whether the time window for a medication intake event has occurred includes referencing, by the processor, at least one of a typical waking time or a typical sleeping time of the patient learned by the processor through analysis of the data from the sensor over time.

10. The method of claim 1 , wherein determining whether the patient has interacted with the medication location includes determining, by the processor from the data, whether an echo signal is received from one of a reflective device or a reflective surface associated with the medication location.11 . The method of claim 10, wherein the one of a reflective device or a reflective surface is mounted to a medication box contained in the medication location.

12. A system for improving medication adherence, comprising: a sensor disposed in a designated space at least periodically occupied by a patient, the sensor including one or more transmit antennae configured to transmit signals into the designated space and one or more receive antennae configured to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient; a network in communication with the sensor; a computing device including a processor and a memory, the computing device being in communication with the network and the processor is configured to receive data from the sensor reflecting the echo signals; a patient device running a patient application, the patient device being in communication with the network; and at least one of a physician device running a physician application and a caregiver device running a caregiver application, the at least one of the physician device and the caregiver device being in communication with the network; wherein the processor is configured to: determine a status of the patient by activating the sensor to transmit signals in the designated space, to receive echo signals reflected from the objects in the designated space, and to transmit the data reflecting the echo signals via the- 29 -DSI366492S46W2.IHOL-0001-01-US network to the processor; determine from the data whether behavior of the patient indicates that the patient is available to complete a medication intake event; respond to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to the patient application a first medication reminder notification instructing the patient to complete the medication intake event by taking the prescribed medication at a general time of day, the patient application displaying the first medication reminder notification to the patient on the patient device; determine from the data whether the patient has interacted with the medication location; respond to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a second medication reminder notification reminding the patient to complete the medication intake event, the patient application displaying the second medication reminder notification to the patient on the patient device; respond to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event; respond to a failure to receive the confirmation reply by sending via the network to the at least one of the physician device or the caregiver device a message that the patient failed to complete the medication intake event; and respond to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event.

13. The system of claim 12, wherein the processor is configured to determine whether behavior indicates that the patient is available to complete the medication intake event by analyzing the data from the sensor reflecting the echo signals to- 30 -DSI366492S46W2.IHOL-0001-01-US determine whether the patient is approaching a bed in the designated space or the patient is exiting the bed.

14. The system of claim 12, wherein the processor is configured to respond to receipt of the confirmation reply by waiting for a time window for a second medication intake event to occur, and responding to an occurrence of the second time window by determining a next status of the patient by activating the sensor to obtain further data reflecting the echo signals; determining from the further data whether behavior of the patient indicates that the patient is available to complete the second medication intake event; responding to a determination that the patient is available to complete the second medication intake event by sending via the network to the patient application a third medication reminder notification instructing the patient to complete the second medication intake event; determining from the further data whether the patient has interacted with the medication location; responding to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a fourth medication reminder notification reminding the patient to complete the second medication intake event; responding to a determination that the patient has interacted with the medication location by sending via the network to the patient application a second confirmation request asking the patient to activate the button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the second medication intake event; responding to a failure to receive the confirmation reply by sending via the network to the at least one of the physician device or the caregiver device a message that the patient failed to complete the second medication intake event; responding to receipt of the confirmation reply by storing data in the memory indicating that the patient completed the second medication intake event and sending a notification via the network to the physician device indicating that the patient completed the second medication intake event.- 31 -DSI366492S46W2.IHOL-0001-01-US15. The system of claim 12, wherein the processor is further configured to determine whether a time window for the medication intake event has occurred.

16. The system of claim 15, wherein the time window is a learned time window based on behavioral patterns of the patient that indicate when medication intake events typically occur.

17. The system of claim 15, wherein the processor is configured to determine whether the time window has occurred by referencing at least one of a typical waking time or a typical sleeping time of the patient learned by the processor through analysis of the data from the sensor over time.

18. The system of claim 12, wherein the sensor is a radio frequency interferometer.

19. The system of claim 12, wherein the physician device and the caregiver device are configured to communicate with the patient device over the network.

20. The system of claim 12, wherein the processor is configured to determine whether the patient has interacted with the medication location by determining from the data whether an echo signal is received from one of a reflective device or a reflective surface associated with the medication location.21 . The system of claim 20, wherein the one of a reflective device or reflective surface is mounted to a medication box contained in the medication location.

22. The system of claim 12, wherein the patient application is configured to generate a menu icon which, when activated, permits the patient to access any of a plurality of pages generated by the patient application, and a notification icon which indicates to the patient an existence of one or more unread notifications.- 32 -DSI366492S46W2.IHOL-0001-01-US23. The system of claim 12, wherein the patient application is configured to generate a daily progress bar that provides a visual indication of a percentage of tasks the patient has completed for a current day.

24. The system of claim 12, wherein the patient application is configured to generate a reminder pane which notifies the patient of upcoming medication intake events and provides one or more buttons that, when activated, permit the patient to indicate whether a medication intake event was completed.

25. The system of claim 12, wherein the patient application is configured to generate a highlights pane which displays updates of activities completed by the patient.

26. The system of claim 12, wherein the caregiver application is configured to generate a caregiver interface which displays one or more reminders to a caregiver relating to the medication intake event.

27. The system of claim 12, wherein the physician application is configured to generate a patient identification bar that identifies the patient, and a patient details area that provides at least one of a gender of the patient, an age of the patient, and a date of birth of the patient.

28. The system of claim 12, wherein the physician application is configured to generate a pending area that indicates a number of pending tasks and notifications for the patient.

29. The system of claim 12, wherein the physician application is configured to generate a control panel including a patients dashboard button which, when activated, causes the physician device to display a data panel that provides one or more charts indicating one or more behaviors of the patient each day for a desired time period.- 33 -DSI366492S46W2.IHOL-0001-01-US30. The system of claim 12, wherein the physician application is configured to generate an insights panel that provides one or more summary charts depicting data during a desired time period of one or more health related parameters of the patient.31 . A non-transitory computer readable storage medium with instructions stored thereon configured to cause a processor coupled to a network in communication with a sensor, a patient device, and a physician device to perform functions for improving medication adherence of a patient comprising: determining whether a time window for a medication intake event for the patient has occurred; determining a status of the patient by activating the sensor to transmit signals in a designated space at least periodically occupied by the patient, to receive echo signals reflected from objects in the designated space including the patient and a medication location containing a prescribed medication for the patient, and to transmit data reflecting the echo signals via the network to the processor; determining from the data, whether behavior of the patient indicates that the patient is available to complete the medication intake event; responding to a determination that the behavior indicates that the patient is available to complete the medication intake event by sending via the network to a patient application running on the patient device a first medication reminder notification instructing the patient to complete the medication intake event by taking the prescribed medication at a general time of day; determining from the data, whether the patient has interacted with the medication location; responding to a determination that the patient has not interacted with the medication location by sending via the network to the patient application a second medication reminder notification reminding the patient to complete the medication intake event; responding to a determination that the patient has interacted with the medication location by sending via the network to the patient application a confirmation request asking the patient to activate a button displayed on the patient device to send a confirmation reply via the network to the processor indicating that the patient completed the medication intake event;DSI366492S46W2.I - 34 -HOL-0001-01-US responding to a failure to receive the confirmation reply by sending via the network to at least one of the physician device or a caregiver device a message that the patient failed to complete the medication intake event; and responding to receipt of the confirmation reply by storing data in a memory indicating that the patient completed the medication intake event and sending a notification via the network to the physician device indicating that the patient completed the medication intake event.- 35 -DSI366492S46W2.I

Images