WO2020160654A1

WO2020160654A1 - Clustering station, system, and method for alert scheduling

Info

Publication number: WO2020160654A1
Application number: PCT/CA2020/050137
Authority: WO
Inventors: Lahav Gil; Yoav RAITER; Igal Roytblat; Laura Karik
Original assignee: Ux Data Sciences Corp.
Priority date: 2019-02-04
Filing date: 2020-02-04
Publication date: 2020-08-13

Abstract

A system includes a base station and a receptacle adapted to receive and cluster medications for a user to consume. Sensors detect data concerning the medications in the receptacle. Communication interfaces transmit and receive the data over a network. A networked database remotely collects and stores the data. Processors analyze the data and generate scheduling prompts when the medications are to be consumed in keeping with a predetermined schedule. They also generate alert notifications when there is a mismatch between the medications clustered in the receptacle and the predetermined schedule for consuming them. The scheduling prompts and the alert notifications are presented to the user. A corresponding clustering station and method for alert scheduling are also disclosed.

Description

CLUSTERING STATION, SYSTEM, AND METHOD FOR ALERT SCHEDULING

FIELD OF THE INVENTION

[0001 ] The present invention relates generally to devices for medication consumption and, more particularly, to a clustering station, system, and method for alert scheduling.

BACKGROUND OF THE INVENTION

[0002] In the prior art, pills (alternately herein,“medications”) may have been stored in various types of containers. Regardless of the types of containers, however, medication consumers (alternately herein,“patients” or“users”) may have clustered their

medications on tables or countertops, or in small cups, before consuming them.

[0003] Prior art medication regimens may have been somewhat difficult to follow, and/or medication consumption information (and adherence to prescribed medication regimens) may have been somewhat difficult to track. Some users, including for example those with visual impairments, may have had difficulty reading information on labels of pill containers. These problems may be multiplied or exacerbated when a variety of distinct medications must be consumed.

[0004] What may be needed is a smart bowl or other receptacle that preferably can count and/or identify any pills that may be clustered in it prior to consumption by the patient.

[0005] What may be needed is a device, system, and/or method that preferably offers one or more advantageous utilities in association with users’ propensity to cluster medications before consumption.

[0006] It may be desirable to provide a device, system, and/or method that can be used to collect medication consumption information and/or to communicate such information to parties who may need, desire, or benefit from it, and/or any who may help the patient or others to benefit from such medication consumption information. For example, the medication consumption information may be communicated to medication users, caregivers, family members, medical staff, GPs, insurance agencies, and/or clinical study administrators.

[0007] It may be an object according to one aspect of the invention to provide a clustering station, system, and/or method for alert scheduling.

[0008] It may be an object according to one aspect of the invention to provide a clustering station, system, and/or method for minimally invasive tracking and/or recording of medication consumption.

[0009] It may be an object according to one aspect of the invention to provide a clustering station, system, and/or method that requires little, minimal, or no change in habits of medication users.

[0010] It is an object of the present invention to obviate or mitigate one or more disadvantages and/or shortcomings associated with the prior art, to meet or provide for one or more needs and/or advantages, and/or to achieve one or more objects of the invention - one or more of which may preferably be readily appreciable by and/or suggested to those skilled in the art in view of the teachings and/or disclosures hereof.

SUMMARY OF THE INVENTION

[0011 ] According to the invention, there is disclosed a clustering system for monitoring medication consumption habits, and for use with one or more medications to be consumed by a user. The system preferably includes one or more user devices and/or one or more processors. The user devices preferably include a receptacle and/or one or more sensors. The receptacle is preferably adapted to receive and cluster the

medications. The sensors preferably detect data concerning the medications clustered in the receptacle and/or and any removal of the medications from the receptacle. The processors preferably analyze the data to identify types and/or quantities of the medications clustered in the receptacle, and/or to identify, after said any removal of the medications from the receptacle, a consumption event. [0012] According to an aspect of a preferred embodiment of the invention, the system is adapted for use with the medications to be consumed in keeping with a predetermined schedule. The user devices further comprise a notification system for presenting one or more scheduling prompts and alert notifications to the user. The processors preferably further analyze the data and/or generate: the scheduling prompts, preferably when the medications are to be consumed in keeping with the predetermined schedule; and/or the alert notifications, preferably when the processors determine that one or more mismatched conditions exist between the predetermined schedule in comparison to the data. Preferably, the processors convey the scheduling prompts and the alert notifications to the notification system for presentation to the user as aforesaid.

[0013] According to an aspect of a preferred embodiment of the invention, the processors may preferably, but need not necessarily, determine that the mismatched conditions exist when: (a) the medications differ in number from those to be consumed in keeping with the predetermined schedule; (b) the medications were not consumed in keeping with the predetermined schedule; (c) the medications were consumed other than in keeping with the predetermined schedule; (d) a restriction in the predetermined schedule was not followed in consuming the medications; and/or (e) the medications differ in type from those to be consumed in keeping with the predetermined schedule. [Restrictions in the predetermined schedule may preferably, but need not necessarily, include that the medications or doses must, for example, be taken four hours (or some other time interval) apart from one another.]

[0014] According to an aspect of a preferred embodiment of the invention, the sensors may preferably, but need not necessarily, include one or more cameras. The data may preferably, but need not necessarily, include one or more images of the medications clustered in the receptacle. (As used herein, the“cameras” may be any instruments capable of generating two- or three-dimensional images, and the“images” may be any two- or three-dimensional depictions or other data sets associated with the medications clustered in the receptacle.) The processors may preferably, but need not necessarily, include one or more image processors that analyze the images to count and identify the medications clustered in the receptacle.

[0015] According to an aspect of a preferred embodiment of the invention, the receptacle may preferably, but need not necessarily, be provided integrally together with at least one of the cameras.

[0016] According to an aspect of a preferred embodiment of the invention, the image processors may preferably, but need not necessarily, analyze colors, shapes, and sizes of the medications in the images, preferably to identify the medications clustered in the receptacle as aforesaid.

[0017] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, also include one or more data analysis algorithms. [The data analysis algorithms may preferably, but need not necessarily, include one or more artificial intelligence (“Al”) algorithms, intelligent assistant algorithms, and/or deep learning algorithms. The data analysis algorithms may preferably, but need not necessarily, analyze the data, the images, and/or other information, preferably to extract one or more useful insights.] The image processors may preferably, but need not necessarily, apply the data analysis algorithms to analyze the images as aforesaid.

[0018] According to an aspect of a preferred embodiment of the invention, the receptacle may preferably, but need not necessarily, have sloped interior walls and/or an interior bottom portion that may preferably, but need not necessarily, be shaped so that the image processors may preferably, but need not necessarily, readily count and/or identify the medications in the receptacle. For example, the interior bottom portion may preferably be shaped to define one or more grooves therein. As such, the medications may preferably, but need not necessarily, be readily arranged in one or more rows. And thus, the image processors may preferably, but need not necessarily, readily count and/or identify the medications in the rows. [0019] According to an aspect of a preferred embodiment of the invention, the sensors may preferably, but need not necessarily, include one or more photosensors, light sensors, capacitive sensors, proximity sensors, ultrasonic sensors, accelerometers, motion sensors, temperature sensors, weight sensors, and/or microphones.

[0020] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, be further adapted for use by a caregiver, who may preferably be associated with the user. The processors may preferably, but need not necessarily, generate and/or convey one or more medication notifications to the caregiver based on: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

[0021 ] According to an aspect of a preferred embodiment of the invention, the

notification system may preferably, but need not necessarily, present the scheduling prompts and/or the alert notifications audibly, visually, and/or by vibrations.

[0022] According to an aspect of a preferred embodiment of the invention, the

notification system may preferably, but need not necessarily, include one or more lights, projectors, speakers, and/or vibration devices, preferably to present the scheduling prompts and/or the alert notifications.

[0023] According to an aspect of a preferred embodiment of the invention, the

scheduling prompts and/or the alert notifications may preferably, but need not necessarily, include one or more text, image, time, date, and/or instruction data that may preferably, but need not necessarily, be presented to the user by the notification system.

[0024] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, be further adapted for use with one or more of the following as the predetermined schedule: a user-entered schedule, a learned schedule, and/or an adaptive schedule. (The processors may adapt and/or modify the predetermined schedule - based on the data, the types and quantities of the medications identified as clustered in the receptacle, the consumption events, the scheduling prompts, the alert notifications, and/or the mismatched conditions - for subsequent use with the system, device, and/or method, in the future, according to an aspect of a preferred embodiment of the invention.)

[0025] According to an aspect of a preferred embodiment of the invention, the user devices may preferably, but need not necessarily, also include a base station.

[0026] According to an aspect of a preferred embodiment of the invention, the receptacle may preferably, but need not necessarily, be a bowl. The bowl may preferably, but need not necessarily, be removable from the base station.

[0027] According to an aspect of a preferred embodiment of the invention, the user devices may preferably, but need not necessarily, also include a device

communications interface that preferably remotely transmits the data. The system may preferably, but need not necessarily, also include a networked communications interface and/or a networked database. The networked communications interface may preferably, but need not necessarily, receive the data remotely from the device communications interface. The networked database, preferably remotely from the user devices, may preferably, but need not necessarily, collect and/or store: the data, the types and quantities of the medications identified as clustered in the receptacle, and/or the consumption event.

[0028] According to an aspect of a preferred embodiment of the invention, the base station may preferably, but need not necessarily, be provided integrally together with the device communications interface and/or the notifications system.

[0029] According to an aspect of a preferred embodiment of the invention, the device communications interface may preferably, but need not necessarily, use a wireless communication protocol to remotely transmit the data. [0030] According to an aspect of a preferred embodiment of the invention, the base station may preferably, but need not necessarily, also include a battery preferably to at least partially power the device communications interface and/or the sensors.

[0031 ] According to an aspect of a preferred embodiment of the invention, the base station may preferably, but need not necessarily, also include a wired power input preferably to at least partially power the device communications interface and/or the sensors.

[0032] According to an aspect of a preferred embodiment of the invention, the

processors may preferably, but need not necessarily, include a base station processor and/or a networked processor. The base station processor may preferably, but need not necessarily, be onboard the base station. It may preferably, but need not necessarily, process and/or convey the data detected by the sensors for transmission by the device communications interface. The networked processor may preferably, but need not necessarily, access the data, stored in the networked database, concerning the medications clustered in the receptacle portion.

[0033] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, also include a mobile and/or web-based application. Preferably, but not necessarily, the mobile and/or web-based application may selectively grant permission for the user and/or for a third party to access and/or review, substantially in real-time: the predetermined schedule; the data; the types and quantities of the medications identified as clustered in the receptacle; the consumption events; the scheduling prompts; the alert notifications; and/or the mismatched

conditions.

[0034] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, also include one or more application programming interfaces (“APIs”). The APIs may preferably, but need not necessarily, enable access to the user devices, the networked database, and/or the processors. [0035] According to an aspect of a preferred embodiment of the invention, the APIs may preferably, but need not necessarily, be adapted for use with a mobile and/or

web-based application, preferably to selectively grant permission for the user and/or for a third party to access or review, substantially in real-time: the predetermined schedule; the data; the types and quantities of the medications identified as clustered in the receptacle; the consumption events; the scheduling prompts; the alert notifications; and/or the mismatched conditions.

[0036] According to an aspect of a preferred embodiment of the invention, the system may preferably, but need not necessarily, be adapted for use by one or more

caregivers, family members, doctors, nurses, medical staff, clinical trial administrators, pharmacists, pharmacies, medication-related solution providers, and/or insurance agencies, as the third party.

[0037] According to the invention, there is also disclosed a clustering device monitoring medication consumption habits, and/or for use with one or more medications to be consumed by a user. The device preferably includes a receptacle, one or more sensors, and/or one or more processors. The receptacle is preferably adapted to receive and/or cluster the medications. The sensors preferably detect data concerning the medications clustered in the receptacle. The processors preferably analyze the data to identify types and quantities of the medications clustered in the receptacle and to identify, after any said removal of the medications from the receptacle, one or more consumption eventsand/or generate one or more: scheduling prompts, preferably when the

medications are to be consumed in keeping with the predetermined schedule; and/or alert notifications, preferably when the processors determine that one or more

mismatched conditions exist between the predetermined schedule in comparison to the data concerning the medications clustered in the receptacle. The notification system preferably receives and/or presents the scheduling prompts and/or the alert notifications to the user. [0038] According to an aspect of a preferred embodiment of the invention, the device may preferably, but need not necessarily, be also for use with the medications to be consumed in keeping with a predetermined schedule.

[0039] According to an aspect of a preferred embodiment of the invention, the device may preferably, but need not necessarily, be also for use with a networked

communications interface and/or a networked database.

[0040] According to an aspect of a preferred embodiment of the invention, the device may preferably, but need not necessarily, include a base station, a device

communications interface, and/or a notification system.

[0041 ] According to an aspect of a preferred embodiment of the invention, at least one of the processors may preferably, but need not necessarily, be onboard the base station.

[0042] According to the invention, there is also disclosed a clustering method for monitoring medication consumption habits, and for use with one or more medications to be consumed by a user. The method preferably includes a clustering step, wherein the medications are preferably received and/or clustered in a receptacle. It preferably also includes a detection step, wherein one or more sensors are preferably used to detect data concerning the medications clustered in the receptacle and any removal of the medications from the receptacle. Preferably, in a processing step, one or more processors analyze the data to identify types and/or quantities of the medications clustered in the receptacle and/or to identify, after any said removal of the medications from the receptacle, one or more consumption events.

[0043] According to an aspect of a preferred embodiment of the invention, the method may preferably, but need not necessarily, be for use with the medications to be consumed in keeping with a predetermined schedule.

[0044] According to an aspect of a preferred embodiment of the invention, preferably in the processing step, the processors may preferably, but need not necessarily, further analyze the data and/or generate one or more: scheduling prompts, preferably (but not necessarily) when the medications are to be consumed in keeping with the

predetermined schedule; and/or alert notifications, preferably (but not necessarily) when the processors determine that one or more mismatched conditions exist between the predetermined schedule in comparison to the data. The method may preferably, but need not necessarily, also includes a notification step, wherein the scheduling prompts and/or the alert notifications are preferably presented to the user.

[0045] According to an aspect of a preferred embodiment of the invention, the method may preferably, but need not necessarily, also includes a transmission step, wherein the data is transmitted, preferably (but not necessarily) using a device communications interface, to a remote networked communications communications interface. The method may preferably, but need not necessarily, also includes a step of collecting and/or storing the data in a networked database. The networked database may preferably, but need not necessarily, be located remotely from the receptacle.

[0046] According to an aspect of a preferred embodiment of the invention, preferably in the processing step, the processors may preferably, but need not necessarily, determine that the mismatched conditions exist when: (a) the medications differ in number from those to be consumed in keeping with the predetermined schedule; (b) the medications were not consumed in keeping with the predetermined schedule; (c) the medications were consumed other than in keeping with the predetermined schedule; and/or (d) the medications differ in type from those to be consumed in keeping with the predetermined schedule.

[0047] According to an aspect of a preferred embodiment of the invention, preferably in the detection step, the sensors may preferably, but need not necessarily, include one or more cameras, and/or the data may preferably, but need not necessarily, include one or more images of the medications clustered in the receptacle. Preferably, in the

processing step, the processors may include one or more image processors that may preferably, but need not necessarily, analyze the images to count and/or identify the medications clustered in the receptacle.

[0048] According to an aspect of a preferred embodiment of the invention, preferably in the processing step, the image processors may preferably, but need not necessarily, analyze colors, shapes, and/or sizes of the medications in the images, preferably to identify the medications clustered in the receptacle as aforesaid.

[0049] According to an aspect of a preferred embodiment of the invention, preferably in the processing step, the image processors may preferably, but need not necessarily, apply one or more data analysis algorithms to analyze the images as aforesaid.

[0050] According to an aspect of a preferred embodiment of the invention, preferably before the clustering step, the receptacle may preferably, but need not necessarily, be provided with sloped interior walls and an interior bottom portion that may preferably, but need not necessarily, be shaped so that, preferably after the clustering step in the processing step, the image processors may preferably, but need not necessarily, readily count and/or identify the medications in the receptacle. For example, the interior bottom portion that may preferably, but need not necessarily, be shaped to define one or more grooves therein. As such, preferably in the clustering step, the medications may preferably, but need not necessarily, be readily arranged in one or more rows. And thus, preferably in the processing step, the image processors may preferably, but need not necessarily, readily count and/or identify the medications in the rows.

[0051 ] According to an aspect of a preferred embodiment of the invention, the method may preferably, but need not necessarily, be further adapted for use by a caregiver who is associated with the user. Preferably in the processing step, the processors may preferably, but need not necessarily, generate and/or convey one or more medication notifications to the caregiver based on: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events. [0052] According to an aspect of a preferred embodiment of the invention, preferably in the notification step, the scheduling prompts and/or the alert notifications may preferably, but need not necessarily, be presented audibly, visually, and/or by vibrations.

[0053] According to an aspect of a preferred embodiment of the invention, preferably in the notification step, one or more text, image, time, date, and/or instruction data may preferably, but need not necessarily, be presented.

[0054] According to an aspect of a preferred embodiment of the invention, preferably in the transmission step, the device communications interface may preferably, but need not necessarily, use a wireless communication protocol to remotely transmit the data.

[0055] According to an aspect of a preferred embodiment of the invention, preferably in the processing step: a base station processor (preferably onboard a base station that is located locally to the receptacle) may preferably, but need not necessarily, process and/or convey the data detected by the sensors for transmission by the device communications interface; and/or a networked processor may preferably, but need not necessarily, access the data stored in the networked database.

[0056] According to an aspect of a preferred embodiment of the invention, the method may preferably, but need not necessarily, also include an access step, wherein a mobile or web-based application may preferably, but need not necessarily, selectively grant permission for the user and/or for a third party to access and/or review, substantially in real-time: the predetermined schedule; the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events; the scheduling prompts; the alert notifications; and/or the mismatched conditions.

[0057] According to an aspect of a preferred embodiment of the invention, preferably in the access step, the mobile or web-based application may preferably, but need not necessarily, work with one or more application programming interfaces to enable said access and/or review. [0058] According to an aspect of a preferred embodiment of the invention, preferably in the access step, the third party may preferably, but need not necessarily, be a caregiver, family member, doctor, nurse, medical staff member, clinical trial

administrator, pharmacists, pharmacies, medication-related solution providers, and/or insurance agency.

[0059] Other advantages, features and characteristics of the present invention, as well as methods of operation and functions of the related elements of the structure, and the combination of parts and economies of manufacture, will become more apparent upon consideration of this detailed description with reference to the figures which accompany this application.

BRIEF DESCRIPTIONS OF THE DRAWINGS

[0060] The novel features which are believed to be characteristic of the present invention, and related systems and methods according to the present invention, as to their structure, organization, use and method of operation, together with further objectives and advantages thereof, may be better understood from figures which accompany this application, in which presently preferred embodiments of the invention are illustrated by way of example. It is expressly understood, however, that any such figures are for the purpose of illustration and description only, and not intended as a definition of the limits of the invention. In the accompanying figures:

[0061 ] Figure 1 depicts a base station of according to a preferred embodiment of the invention;

[0062] Figure 2 depicts a system for use with the base station of Figure 1 according to an aspect of the preferred embodiment of the invention;

[0063] Figure 3 depicts another system for use with the base station of Figure 1 according to another aspect of the preferred embodiment of the invention; [0064] Figure 4 depicts a method for use with the system of Figure 2 according to an aspect of the preferred embodiment of the invention;

[0065] Figure 5 depicts another method for use with the system of Figure 3 according to another aspect of the preferred embodiment of the invention; and

[0066] Figure 6 depicts another method for use with the system of Figure 2 according to an aspect of the preferred embodiment of the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0067] Figures 1-3 depict elements of preferred systems 100,100’ for medication clustering, communication, and management for users. According to various preferred aspects of the invention, medications can be stored in one or more containers, 104 (as shown in Figure 2) and/or 104-1 , 104-2, 104-3 (as shown in Figure 3), before using a clustering station (alternately herein, a“base station”) 144, 144’ and/or a receptacle 170 (as shown in Figure 1 ) to take the medications.

[0068] The system preferably includes: a. The receptacle 170 which enables clustering of the medications. In some

embodiments, the receptacle may have one or more cameras, other built-in sensors, a communication interface, a processor (alternately herein, a“CPU”), and/or a battery. In other embodiments, the receptacle may be a totally passive bowl. b. The base station 144, 144’ includes sensors 160, a communication interface 156, and a CPU 148. (The receptacle 170 and/or the base station 144, 144’ preferably has a camera 208 as shown in Figure 1.) Preferably, the base station 144 is connected to power 174 and also has a battery 176 so it can be readily moved from one place to another. In some embodiments, the base station may be provided with cameras, and a charger (e.g., when the receptacle is wired) c. A cloud-based server 120 that collects reports from all the receptacles

(alternately herein,“bowls”). The server 120 preferably tags and stores such reports in a database 140. The server 120 is also used to compare the reports to a predefined schedule and, in the event of severe mismatches, to generate notifications / alerts. The server 120 is also adapted to work with one or more artificial intelligence (“Al”), intelligent assistant, and/or deep learning algorithms and/or features, and with image processing (alternately herein,“machine vision”) systems 180 that analyze the information and extract useful insights. d. Machine vision systems 180, 182 that rely on the sensors 160 (for example,

cameras) to peer into the bowl 170 in a minimally intrusive way with a minimally required illumination. This system will be described in greater detail below: i. The machine vision systems 180, 182 preferably identify whether, or not, there are pills in the bowl 170. In some embodiments, they may count the pills, and/or record their colors, shapes and/or sizes. ii. In some embodiments, a time series analysis performed by the systems 180, 182 can learn one or more habits of the medication consumer, and potentially alert a caregiver when the consumer’s behaviour seems unusual, for example: when it appears there are too many or too few pills for an expected dose; when a dose appears to have been missed during an expected time window; when there appears to be an extra dose at an unexpected time; and/or when different types of pills appear to be clustered at an expected dose time. e. According to an aspect of the invention, placing two cameras on opposite sides of (or placing three cameras about 120 degrees apart from each other around) the bowl 170 may help the system 100, 100’ to see each and all of the pills, without obstruction by any of the other pills, in the bowl 170. f. In some embodiments, a 3D camera may use laser-mapping, e.g., for dimensional measurements that are more highly accurate than those which may be afforded by visible-light machine vision systems. g. In some embodiments, one or more markings may be provided on the inner walls and bottom of the bowl 170 which, for example, may be used for registration and/or dimension reference. h. A mobile app 290 preferably enables caregivers to review potentially relevant events in near real time. Events may be presented in textual, graphical, and/or streaming video forms. And/or, i. A dashboard 161 is preferably provided for users such as doctor’s, nurses,

clinical trial administrators, etc. The dashboard 161 preferably enables these users to view data from individual users, and/or to see stats or other data for groups of users.

[0069] In some embodiments, capacitive sensors 160 may be attached to a conductive bowl shell. The capacitive sensors 160 may detect whether, or not, a human (or animal) is touching the bowl, e.g., trying to take the medications.

[0070] Other sensors 160 can also help, among other things, to identify the presence (or absence) of pills in the bowl 170 - for example, as follow: a. A proximity sensor 160 at the bottom of the bowl 170 where all the pills may be collected. b. A light sensor 160 at the bottom of the bowl 170 might be obstructed by pills at the bottom. c. An ultrasonic volume sensor 160 aimed at the opening of the bowl 170 may

detect objects inside. And/or, d. An accelerometer 160 may detect movement of the bowl 170 when a consumer handles it.

[0071 ] As shown in Figure 2, a confirmation button 173 is preferably selectively actuated by the consumer to indicate that a dose is taken. In some embodiments, this button 173 may be removed if the machine vision systems 180, 182 can reliably identify the presence of pills in a bowl 170 and an empty bowl 170. The transition event from a“pills in the bowl” state to an“empty bowl” state may be understood as an event of medication consumption.

[0072] The output devices / indicators 171 of the system 100 shown in Figure 2 preferably include simple LEDs that light up when a button is pressed, as well as machine vision system that output medication consumption events to complex smartphone-like graphic screens with menus, options, and/or graphic / video

illustrations of pills.

[0073] The system 100 is preferably connected to a home’s local area network (e.g., a Wi-Fi network) 156. This connection is preferably enabled using a wireless

communication element 294 associated with the caregiver mobile app 290, 292. a. The app 290, 292 preferably connects the bowl 170 using a Bluetooth Low

Energy (“BLE”) variation of the Bluetooth wireless standard that is designed for low power consumption. b. The caregiver preferably enters the Wi-FI network SSID and password. c. The bowl 170 sets its network parameters and reconnects via the Wi-Fi network.

And/or, d. The app 300, 302 preferably receives confirmation of a successful connection by retrieving the IP address for the bowl 170 via the BLE connection.

[0074] In some embodiments, the shape of the bottom of the bowl 170 helps to cluster and/or control distribution of the pills when they are dropped in. According to an aspect of the invention, an elongated groove shaped in the interior bottom portion of the bowl 170 will help arrange the pills in a row. Whereas, a flat bottom may create randomized but separated distribution of the pills, and/or a deep crater may collect them all in one pile. Controlling the shape, according to an aspect of the invention, preferably helps control the pill distribution for better machine vision results.

[0075] Turning now to the system 100’ shown in Figure 3, each container 104-1 , 104-2, 104-3 will be seen to include an accessory (e.g., an audio accessory) 108-1 , 108-2 and 108-3 respectively affixed thereto. The accessories 108-1 , 108-2, 108-3 are preferably affixed to the containers 104-1 , 104-2, 104-3 by any suitable mechanisms, including adhesives, integral fabrication within the structure of their corresponding containers 104-1 , 104-2, 104-3, and the like. Each such accessory 108-1 , 108-2, 108-3 preferably includes a communication interface (e.g., Bluetooth, Wi-Fi, or the like) and a

microcontroller (not shown). The microcontroller can include a memory (e.g., one or more non-volatile memory elements) storing an audio alert for generation via a speaker 110-1 under control of the microcontroller. As will be discussed below, the

above-mentioned alert is typically generated responsive to an instruction received at the accessory 108-1 from another component of the system 100’. In some examples, however, the accessory 108-1 can also store scheduling data defining when the alert is to be generated, and can initiate such generation autonomously.

[0076] The accessory 108-1 preferably also includes an input 112-1. The input 112-1 preferably includes one or more of a button or other actuator, a motion sensor such as an accelerometer, capacitive sensor to identify touch by a human hand, and the like. As will be discussed below, the input can be actuated by the patient to initiate playback of the above-mentioned audio alert, or of other audio data stored in the accessory 108-1 (e.g., a stored audio file stating the name of the medication in the container 104-1 , pre-defined administration scheduling data corresponding to the medication, and the like). [0077] Figure 2 shows other devices and applications 104/108 which may be likened to the containers 104-1 , 104-2, 104-3 and accessories 108-1 , 108-2, 108-3 shown in Figure 3 in many respects. The devices and applications 104/108 shown in Figure 2 also include electronic pill packages (and other storage solutions, dispensers, and the like) 190 and other connected medical devices and applications 191.

[0078] The system 100, 100’ also includes a network 116 and a server 120, 120’. The network 116 can be a wide-area network (WAN), for example including cellular networks, and the like, a local-area network (LAN) or a combination thereof. The server 120, 120’ includes a CPU (alternately herein, a“processor”) 124 interconnected with a non-transitory computer readable storage medium, such as a memory (alternately herein, a“repository” or“database”) 140. The memory 140 includes any suitable combination of volatile and non-volatile memory. The processor 124 and the memory 140 may each include one or more integrated circuits (ICs). The server 120, 120’ also includes a communications interface 132, enabling the server 120, 120’ to exchange data with other computing devices via the network 116. Generally, the server 120, 120’ is used for the identification of medication taken through the clustering station 144, 144’ and for the configuration of scheduling data according to which the accessories

104/108, 108-1 , 108-2, 108-3 or the clustering station 144 are controlled to generate alerts for the patient. To that end, the server 120 includes an image processing system 180 and a scheduling control application 136, the functionality of each will be discussed in greater detail below. The server 120 also stores a repository 140 of medications and account records.

[0079] The system 100 also includes a clustering station 144, configured to establish communications between the accessories 108 and the network 116, and the mobile apps 16 . The base station 144 includes a processor 148 interconnected with a memory 152 and a communications interface 156. The memory 152 stores executable instructions that, when executed by the processor 148, implement the functionality of the base station 144 discussed below. The memory 152 can also store scheduling data in some examples, for example by periodically retrieving the scheduling data from the server 120.

[0080] The communications interface 156 enables the clustering station 144 to communicate with the server 120 via the network 116, and also with the accessories 108 via local communications links. For example, the interface 156 of the base station 144 can include both a wide-area radio (e.g., 3G, CDMA and the like) for

communicating via the network 116, and a local-area radio (e.g., Bluetooth, WiFi and the like) for communicating with the accessories 108. In other words, the base station could be an access point through which the accessories 108 are connected with the network 116 and therefore the server 120. Alternatively, an API 175 in the clustering station 144 or an API 181 in the server 120 is preferably an access point for other connected devices and applications. The base station 144 is typically deployed in the home, the workplace, or the like of a patient associated with the containers 104 (e.g., who must self-administer the medications in the containers 104).

[0081 ] The clustering station 144, in addition to acting as an access point permitting communications between the server 120 and the accessories 108, includes

components configured to assist the patient in administering a plurality of medications from the containers 104. For example, as will be described below, the base station 144 includes a receptacle 170 with an integral cluster feature in which a plurality of medications may be collected following their removal from the containers 104 and prior to their administration (e.g., consumption by the patient). The base station 144 can further be configured to validate the collected medications against scheduling data prior to administration.

[0082] In addition to the receptacle 170 mentioned above, the base station 144 includes one or more sensors 160 configured to collect sensor data corresponding to the contents of the receptacle 170. The sensors 160 can include any one of, or any combination of, image sensors (e.g., cameras), temperature sensors, weight sensors (e.g., strain gauges), motion sensors, capacitive sensors (touch) and the like configured to assess the contents of the receptacle 170 for comparison to its expected contents according to the scheduling data mentioned above. Based on the detected contents of the receptacle 170, the base station 144 is configured to control the accessories 108 to generate guidance (e.g., audible guidance) to the patient to assist the patient in adhering to the scheduled administration of medication(s) defined by the scheduling data or to generate the guidance through its own outputs 171.

[0083] Figure 1 illustrates an exemplary base station 144 according to a preferred embodiment of the invention. As shown in Figure 1 , the base station 144 includes a base 200 which can contain the processor 148, the memory 152 and the

communications interface 156 mentioned above (and shown in Figures 2 and 3). Figure 1 also illustrates the above-mentioned receptacle 170 with its integral cluster feature, in the form of a bowl-shaped receptacle 170 sized to receive and contain a plurality of pills or similarly-shaped and sized objects, following retrieval of such objects from the containers 104. Also shown in Figure 1 are examples of the sensors 160, such as a camera 208 having a field of view oriented to capture images of the interior of the receptacle 170. The machine vision and image processing system 180, 182 is configured to, via the camera 208, capture images of the contents of the receptacle 170 with its integral cluster feature, and to detect various attributes of the contents, including any suitable combination of a number of objects (e.g., pills) in the receptacle 170, types of each object in the receptacle 170, and the like. Certain of the sensors 160 can also be supported by the base 200. For example, the sensors 160 may include one or more strain gauges, for measuring changes in the weight of the receptacle 170, that can be incorporated into the base 200.

[0084] The base station 144, 144’ can also include a motion sensor or a projector 212 (or other means for displaying data) supported by the base 200, with a motion sensing field or a projection field 216 extending through an aperture in the receptacle 170, towards a portion of the interior of the receptacle 170. The projector 212 can therefore project text, images, or a combination thereof onto an interior surface of the receptacle 170, including the time and date, instructions relating to the scheduling functionality (e.g., the audible scheduling functionality) discussed herein, and the like.

[0085] Among the output devices 171 (shown in Figure 2) that can be provided as part of the base station 144, an LED strip or other light emitter 220 may preferably be provided around the base 200 as shown in Figure 1. The light emitter 220 is controllable by the processor 148 (shown in Figure 2) to illuminate in response to various events, including the receipt of an alert instruction from the server 120 (or the generation of an alert instruction at the base station 144 itself), as will be discussed below.

[0086] As shown in Figure 2, the system 100 includes the API 175 in the clustering station 144, and the API 181 in the server 120. The APIs 175, 181 enable the system 100 to interface with third party apps and software to allow them to control and access the information from the system 100. For example, the system 100 could be used with existing reminder apps. Another example is in the telehealth scenario, where the existing system for interfacing with patients could also receive data from the base station 144 and could about the patient's medication usage history.

[0087] In Figure 5, a method 300 for alert scheduling is illustrated. The method 300 is performed by the server 120, 120’ via execution of the application 136 (shown in Figure 3) or execution of the mobile app 290 or the web app 161 (shown in Figure 2). At block 305, the server 120, 120’ is configured to receive a setup request. In one example, the setup request may be initiated by, for example, pressing and holding the input 112-1 of the accessory 108-1. In other examples, the setup request can be initiated via an input at the base station 144, 144’.

[0088] Upon receipt of the setup request, the server 120, 120’ is configured to prompt an operator of the accessory 108, 108-1 or the base station 144, 144’ (depending on which device initiated the setup request) for a patient identifier. In the example discussed below, the data obtained by the server 120, 120’ is obtained via input from the application 136 (shown in Figure 3) or via input from the mobile app 290 or web application 161 (shown in Figure 2). Various other mechanisms (e.g., web sessions and the like) will also occur to those skilled in the art.

[0089] The patent identifier obtained at block 305 can include any suitable one or combination of attributes identifying the patient. For example, the server 120, 120’ can prompt the operator for a patient name and a patient date of birth at block 305. At block 310, the server 120, 120’ is configured to retrieve an account record from the repository 140 that matches the patient identifier. Alternatively, the server 120, 120’ can be configured to create an account record and store the patient identifier therein. At block 310, the server 120, 120’ is also configured to store an identifier of an accessory 108, 108-1 in the account record. For example, when the request received at block 305 was initiated via activation of the input 112-1 of the accessory 108-1 , the request itself may include an accessory identifier (e.g., stored in the onboard memory of the accessory 108-1 ). In other examples in which the request received at block 305 was initiated by the base station 144, 144’ rather than by the accessory 108, 108-1 , at block 310, the server 120, 120’ may instruct the base station 144, 144’ to prompt an operator to activate the input 112-1 in order to cause the accessory 108-1 to transmit its identifier to the base station 144, 144’ for relaying to the server 120, 120’. Following receipt of the accessory identifier at the server 120, 120’, the accessory identifier is stored in the account record corresponding to the patient identifier received at block 305.

[0090] At block 315, the server 120, 120’ is configured to obtain (e.g., via further IVR prompts and responses) scheduling data. In particular, in the present example the server 120, 120’ is configured to obtain a medication name and scheduling data defining a frequency and a time of day for administration of the medication. The medication name obtained at block 315 can be compared to a master list of medications stored in the repository 140 for validation, and associated with the account record retrieved at block 310.

[0091 ] As will now be apparent, blocks 305-315 can be repeated as required to set up additional accessory devices 108, 108-1 , etc. Following additional performances of blocks 305-315, a given account record at the server 120, 120’ may be associated with a plurality of accessory devices 108, each with a distinct medication identifier and administration schedule.

[0092] Following block 315, the server 120, 120’ can be configured to transmit scheduling commands to the relevant accessories 108, 108-1 setting an alarm schedule in each of the accessories 108, 108-1.

[0093] At block 320, the server 120, 120’ is configured to determine whether to cause an accessory device 108, 108-1 to generate an alert. The performance of block 320 need not immediately follow the performance of block 315. More generally, the server 120, 120’ is configured to monitor any scheduling data in the repository 140 in comparison to the current time, and to determine whether the current time matches any of the schedule data. When the determination at block 320 is negative, the server 120, 120’ continues to monitor the scheduling data (e.g., to repeat the determination at block 320). When the determination at block 320 is affirmative, the performance of the method 300 proceeds to block 325. When the server 120, 120’ deploys scheduling commands to the accessories 108, 108-1 as noted above, the accessories 108, 108-1 can be configured to wake up shortly before any scheduled alerts and, prior to beginning generation of an alert, to request instructions from the server 120, 120’. In such embodiments, the performance of block 320 can include a determination of whether any requests have been received from the accessories 108, 108-1. As will now be apparent, when an accessory 108, 108-1 receives no response from the server 120, 120’, the accessory can simply generate the alert according to the previously deployed schedule.

[0094] At block 325, the server 120, 120’ is configured to select an accessory identifier corresponding to the current scheduling data. In other words, when an account record contains scheduling data indicating that an alert is due, the accessory identifier stored in connection with the scheduling data within the account record (e.g., the identifier of the accessory device 108-1 attached to the container 104-1 to which the scheduling data pertains) is selected. When a plurality of alerts associated with the same account record are due at the same time, at block 325, the server 120, 120’ is configured to select a single one of the plurality. Having selected an accessory identifier, the server 120, 120’ is configured to transmit a command to the selected accessory device 108, 108-1 to generate an alert (e.g., an audible alert). The command can be addressed, for example, to the base station 144, 144’, and can include the accessory identifier (for routing of the command from the base station 144, 144’ to the relevant accessory device 108, 108-1 ) as well as data (e.g., audio data). The nature of the data is not particularly limited. For example, audio data may include a recording stating the name of the medication and an indication that the medication is scheduled to be administered.

[0095] In some examples, at block 325, the alert can be generated by the base station 144, 144’ itself, as well as, or instead of, the selected accessory device 108, 108-1. In further examples, the base station 144, 144’ or the server 120, 120’ can be configured to transmit an alert instruction to a distinct device, such as a smartphone or the like, instead of or in addition to the instruction to the accessory device(s) 108, 108-1.

[0096] At block 330, the server 120, 120’ is configured to determine whether a confirmation has been received from the accessory device 108, 108-1 to which the alert command was sent at block 325. For example, each accessory device 108-1 can be configured, after receiving an alert command, to transmit a confirmation message when the input 112-1 is activated. Until the confirmation is received, the alert continues to be generated (e.g., by repeating playback of the above-noted recording). Following receipt of the confirmation message, at block 335, the server 120, 120’ is configured to instruct the accessory device 108, 108-1 to cease generating the alert. In other embodiments, the accessory device 108-1 is configured to automatically interrupt generation of the alert responsive to activation of the input 112-1 (e.g., without awaiting instruction to cease the alert from the server 120’).

[0097] In addition to, or instead of, the above-noted use of the inputs 112-1 of the accessories 108-1 for confirmation at block 330, the base station 144, 144’ can generate confirmation signals. In particular, the processor 148 of the base station 144, 144’ is configured to control the sensors 160 to detect the placement of medications (or other suitable objects) in the receptacle 170 following the transmission of an alert command at block 325.

[0098] For example, following the transmission of an alert command to the accessory 108-1 at block 325, the base station 144’ can be configured to monitor the motion sensor 212 to detect the placement of an object in the receptacle 170. When the placement of an object in the receptacle 170 is detected, the base station 144, 144’ can further be configured to control the camera 208 to capture an image of the interior of the receptacle 170 for analysis to detect any medications contained therein. The base station 144, 144’ can also be configured to obtain a weight reading from a weight sensor in the base 200 following such detection, to detect the weight of the object detected via the sensor 212 as a change in weight of the receptacle 170. The data collected via the sensors (e.g., the weight of the object, the appearance of the object as sensed by the camera 208, such as colour, shape and the like) can be compared to stored attributes of the medication expected according to the scheduling data (and therefore according to the alert generated at block 325).

[0099] When the base station 144, 144’ determines that the medication expected in the receptacle 170 based on the alert command transmitted at block 325 is indeed present in the receptacle 170, the base station 144, 144’ can be configured to generate and transmit a confirmation signal to the server 120, 120’ for receipt at block 330.

[0100] At block 340, the server 120, 120’ is configured to determine whether any alerts remain to be generated for the current time. Thus, when one of a plurality of

concurrently scheduled accessory devices 108, 108-1 , 108-2, 108-3 was selected at block 325, the performance of blocks 325-335 is repeated for each concurrently scheduled alert, rather than the plurality of alerts being generated simultaneously. When no further alerts remain to be generated for the current time (i.e. when the determination at block 340 is negative) the performance of the method 300 proceeds to block 345. [0101 ] At block 345, the server 120, 120’ is configured to determine whether a completion message has been received. The completion message indicates that the medications collected in the receptacle 170 through one or more performances of blocks 325-335 have been administered (e.g., consumed by the patient). The

completion message can be generated by the base station 144, 144’ - for example, responsive to detecting that the receptacle 170 has been emptied.

[0102] Following receipt of the completion message, the performance of the method 300 returns to block 320 for continued monitoring of the scheduling data and generation of future alerts.

[0103] The server 120, 120’ may also be configured to store further data in the account record, including data collected during the performance of blocks 325-345. For example, the server 120, 120’ can store the patient’s response time (e.g., the time between transmission of the alert command at block 325 and receipt of each of the confirmation message at block 330 and the completion message at block 345). Environmental conditions at the accessory device 108, 108-1 , 108-2, 108-3 (e.g., the temperature) may also be reported to the server 120, 120’ by the accessory device 108, 108-1 , 108-2, 108-3 and/or the base station 144, 144’ for storage in the account record.

[0104] In some embodiments, the server 120, 120’ may also be configured to generate notifications for transmission to a mobile device (e.g., a smartphone) or other computing device, via email, SMS or the like. For example, each account record in the repository 140 can include an auxiliary contact identifier (e.g., corresponding to a caregiver of the patient associated with the account record). The server 120, 120’ can be configured to transmit notifications to the auxiliary contact identifier in response to configurable conditions. For example, a notification may be transmitted when no confirmation message is received at block 330 for a predefined period of time (e.g., ten minutes), or when no completion message is received at block 345.

[0105] Referring to Figure 4, the method 400 has one or more cameras 208 (at block 401 ) captures images and/or video of the bowl 170 content. An optional motion detection mechanism (at block 402) analyzes the camera 208 output to determine whether or not there is any significant information to analyze. At block 403, the sensors 160 may preferably, but need not necessarily, be one or more weight cells,

accelerometers, capacitive surfaces, ultrasonic volumetric sensor, laser range measure and others.

[0106] A state classification engine (at block 404) uses images/videos and inputs from the various sensors 160 (at block 403) to determine if the bowl 170 is empty or contains pills. The state machine (at block 405) processes the different state changes and generates a consumption event (at block 420). The consumption event indicates that the patient put some pills in the bowl and then they took it out.

[0107] Upon a consumption event, images, and/or videos of interest are saved (at block 408) for later review by humans and processed by image processing algorithms.

[0108] After a consumption event was triggered, the pill detection, count, and

identification (“PDCI”) engine is triggered at block 410. The algorithm can also operate offline at a later time.

[0109] The PDCI algorithm will detect, locate, count and identify the pills in the bowl 170 prior to consumption event and will feed this information into a time-series prediction engine (at block 409) that will be able to calculate expected pill count, types and time when this specific patient is supposed to consume their medication based on their consumption patterns.

[0110] Each additional time-series information will reinforce (at block 407) the

time-series for this specific patient with better and more accurate predictions.

[0111 ] The consumption event together with the pill count and types is compared to past patterns and prescribed regime (at block 412) and if anomalies are detected, it is reported to the caregiver through a mobile app, SMS, email or other notification (at block 413). [0112] The caregiver either confirms or flags the reported event (at block 414) and they can take corrective action (outside the system) to improve patient compliance.

[0113] The feedback is in turn fed into the reinforcement loop (at block 411 ) to improve the PDCI engine results over time.

[0114] Preferably, according to the invention, the machine vision will be able to: classify bowl state [no_bowl, empty_bowl, non_empty_bowl, and/or other] from videos;

determine if medicine has been taken; determine number of pills in the bowl [1 pill, 2 pills, 3 pills, 4 pills, 5 pills, 6-10 pills, and/or 10-20 pills]; determine number of pill types in the bowl [1...5]; determine the type/name of each pill in the bowl; and/or perform a time series analysis (anomaly detection).

[0115] Preferably, according to the invention, the time series data will be useful to: determine if medication was taken in time (based on prior behavior and/or pre-defined plan); determine if medication was taken correctly with respect to number of pills and/or number of types of pills (based on prior behavior and/or pre-defined plan); and/or determine if medication was taken correctly with respect to specific pill types (based on prior behavior and/or pre-defined plan).

[0116] Preferably, according to the invention, the machine vision will be able to collect information about: most common types of medications; and/or duration of drug being consumed.

[0117] Figure 6 depicts a general medication consumption flow 600 and where the system 100,100’ preferably fits into this scheme.

[0118] In Figure 6, activities 600 related to the use of the system 100, 100’ are grouped as follows: the medication user (in column 610), the system 100, 100’ (in column 620), third party devices or apps (in column 630), and the caregiver including, e.g., family members of the medication user, doctors, nurses, clinical trial administrators (in column 640). [0119] The medications 601 that the medication user 610 may take via the clustering station could be contained in a variety of containers 108, 108-1 , 108-2, 108-3, 108-4, for example, pill bottles, blister packs, dispensers, etc.

[0120] The medication user 610 is reminded (at block 611 ) by some means to take the medication. The patient 610 either remembers (reminds themself) or is reminded by 3rd party (at block 631 ) or by the system reminder to take medication (at block 611 ).

[0121 ] If system reminders are enabled, then during the window of time when the user is to take their medication (something that may preferably be defined and/or configured according to the invention), a reminder light may preferably turn on red (or any other colour as may preferably be configured according to the invention) for a period of time (something else that may preferably be defined and/or configured according to the invention) and, in some embodiments, an audible signal may be included (and may preferably be configurable).

[0122] The patient 610 will then collect medication for the current dose (at block 612) from different containers (601 ). And, in activities within the scope of the present invention but where the systems 100, 100’ may not be used, the patient 610 may cluster them in the palm of their hand, on a countertop, in a small cup, or elsewhere (not shown in Figure 6). Thereafter, the patient 610 can consume the pills (at block 614) with or without water.

[0123] The system 620 provides a convenient clustering station 144, 144’ or bowl 170 (with its integral clustering feature) that, at the time of clustering the medications, records (at block 621 ) the content and the time of the consumption event.

[0124] As shown in Figure 6, the activities 600 then proceed as follows: the medication user places the medication they are going to take into the receptacle 170; and/or the clustering station 144, 144’ may respond when the medication enters the bowl (e.g., lights may turn on blue, or any colour as may preferably be defined and/or configured, with such light change initiated by the system 100, 100’ based on a motion sensor). In one embodiment of the invention, the patient may preferably press the button 173 to acknowledge that they are taking the medication, and the systems 100, 100’ may preferably respond, e.g., with an audio signal and/or the light turning green (or any colour as may preferably be defined and/or configured). Thereafter, the medication user may selectively remove the medication from the bowl 170 and consume the medication.

[0125] In another preferred embodiment, after placing the medication in the receptacle 170, the medication user simply removes the medication from the receptacle and takes the medication. In this case, the medication user does not need to press the button 173 to confirm the medication taking event. Instead, the machine vision algorithm identifies that medication has been placed in the bowl 170 and subsequently removed, and then records the medication taking event automatically.

[0126] In either case, the medication taking event, and related data, e.g., time stamp, images, videos, etc. is recorded and sent to the cloud. Also, in either case, data is regularly being uploaded to the cloud for processing.

[0127] To better reflect the patient environment and their biomedical state, the system is also open to third party information streams (e.g., at block 632) such as wearable monitors, apps, smart home and Internet-of-Things (“loT”) devices through APIs that are available on the clustering station 144, 144’ and the cloud server 120, 120’.

[0128] Then, the system 100, 100’ analyzes the recorded date (at block 622) - more details of the analysis process are described elsewhere herein, e.g., with reference to Figure 4 - and then reports (at block 623) any anomalies and stats to the caregiver 640. The caregiver 640, in turn, can take corrective action such as talking with the patient, physically assisting them with the medication, and/or other.

[0129] Reports (at block 623) can be embodied in or presented by the mobile app 290 or the web application 161. [0130] The use of the mobile app report (at block 623) is as follows:

- In this scenario the caregiver is most likely a loved one.

- The caregiver installs and sets-up the app 290 on their phone. Set-up may

include: connecting the clustering station 144, 144’ to the app 290 via bluetooth, entering the clustering station ID to the app 290 to confirm and connect the bowl 170, entering the medications, entering the medication user’s medication schedule, entering the medication user’s name, connecting to a Wi-Fi network to connect the clustering station 144, 144’ to the server 120, 120’.

- When the caregiver opens the app 290, they may preferably see a timeline with the schedule of when the medication is supposed to be taken. They will also see check marks that indicate when the user pressed the button 173 to acknowledge they are taking their medication. There will be images or videos showing the activity before each medication taking event (e.g., images of the pills that the medication user is going to take), and the caregiver will preferably be afforded an opportunity to review. There will also be an indication of whether the medication was taken as per the prescribed protocol.

- The app 290 preferably also provides push notifications to the caregiver when a medication taking event occurs. Notifications can also be in the form of an email. In the case of an email notification, the email will also include a link to either view or download the image/video associated with the medication taking event. Email notifications can be configured to send to multiple caregivers.

- The app 290 preferably also includes a settings page where various configuration settings can be controlled and maintained. For example, the caregiver can: o Input and/or maintain the medications that the user is taking. o Input and/or maintain a schedule of when the medication user should take the medications. o Input and/or maintain the Wi-Fi network and/or password data. o Input and/or maintain identification data for the base station 144, 144’. o Input and/or maintain medication user’s name o Enable or disable push notifications. o Enable, disable, or maintain email notifications, and/or input email(s)

where the notifications should be sent. o Enable, disable, and configure reminders for the medication user. And/or, o Configure base station settings (e.g., light colours, timings, audio signals, etc.)

- All of these settings can preferably also be configured from the cloud server.

[0131 ] The use of the web application report (from block 623) is preferably as follows:

- In this scenario the caregiver is most likely a paid caregiver (e.g., a doctor, nurse, etc.) and/or a clinical trial or study administrator (hereinafter, an“app user”).

- The app user in this scenario would normally be caring for multiple medication users, for example, in hospitals, senior homes, family physicians, telehealth physicians, etc. In the case of the study administrator, the app user may prefer to see the medication usage data in aggregate.

- The app users will preferably have access to an online dashboard portal through a secure login. They will preferably have access to all of the data for the medication user’s that they have been granted access to (e.g., by the medication user, by another caregiver, or though being part of the clinical trial/study).

- The app users will preferably be able to see the detailed medication taking

history of each medication user preferably, but not necessarily, including (but not limited to): all medications that the medication user is taking; medication protocol/schedule; instances where the medication was not taken as per the protocol and details of these anomoles; statistics such as percent adherence to protocol; trends for when the medication user takes the medication (e.g., bands of time showing average deviation), etc.

- There preferably will also be space to enter qualitative data about the medication user, for example, how they are feeling, and/or if there were any medically significant events (e.g., a fall).

- The app users will also preferably be able to edit and modify the medication data for each medication user, for example, to add a new medication.

G01321 User flow

[0133] Initial setup: The initial setup of the system 100, 100’ at a medication user’s home - or other location where they may prefer to use it and/or receive training on it (e.g., in a hospital) - preferably includes first plugging the base station 144, 144’ into an electrical outlet, and then connecting it to the Internet. The base station 144, 144’ generally connects through a Wi-Fi network, although some embodiments and/or configurations can include wired connections. The Wi-Fi connection preferably can either be pre-configured with the Wi-Fi name and/or password, or be configured by connecting to the app (as described elsewhere herein), e.g., via a Bluetooth connection to the base station 144, 144’ to set the Wi-Fi name and/or password.

[0134] Use of the base station and receptacle: The light may be on white all the time that it is plugged in (or any other colour as may preferably be defined and/or configured) or it may be off if so configured.

[0135] The invention is contemplated for use in association with medications to afford increased advantageous utilities in association with same. The invention, however, is not so limited, and can be readily used with other items (e.g., such items as may be regularly meted out) to afford various advantageous utilities within the scope of the invention. Other embodiments, which fall within the scope of the invention, may be provided.

[0136] The foregoing description has been presented for the purpose of illustration and is not intended to be exhaustive or to limit the invention to the precise form disclosed.

[0137] Naturally, in view of the teachings and disclosures herein, persons having ordinary skill in the art may appreciate that alternate designs and/or embodiments of the invention may be possible (e.g., with substitution of one or more components for others, with alternate configurations of components, etc). Although some of the components, relations, configurations, and/or steps according to the invention are not specifically referenced and/or depicted in association with one another, they may be used, and/or adapted for use, in association therewith. All of the aforementioned and various other structures, configurations, relationships, utilities, any which may be depicted and/or based hereon, and the like may be, but are not necessarily, incorporated into and/or achieved by the invention. Any one or more of the aforementioned and/or depicted structures, configurations, relationships, utilities and the like may be implemented in and/or by the invention, on their own, and/or without reference, regard or likewise implementation of any of the other aforementioned structures, configurations, relationships, utilities and the like, in various permutations and combinations, as will be readily apparent to those skilled in the art, without departing from the pith, marrow, and spirit of the disclosed invention.

[0138] Other modifications and alterations may be used in the design, manufacture, and/or implementation of other embodiments according to the present invention without departing from the spirit and scope of the invention, which is limited only by the claims of this patent application and any divisional and/or continuation applications stemming from this patent application.

Claims

CLAIMS:

1. A clustering system for monitoring medication consumption habits, and for use with one or more medications to be consumed by a user, the system comprising: a) one or more user devices that comprise: i) a receptacle adapted to receive and cluster the medications; and ii) one or more sensors that detect data concerning the medications

clustered in the receptacle and any removal of the medications from the receptacle; b) one or more processors that analyze the data to identify types and quantities of the medications clustered in the receptacle and to identify, after any said removal of the medications from the receptacle, one or more consumption events.

2. The system according to claim 1 , wherein the sensors comprise one or more cameras, wherein the data comprise one or more images of the medications clustered in the receptacle, and wherein the processors comprise one or more image processors that analyze the images to count and identify the medications clustered in the

receptacle.

3. The system according to claim 2, wherein the receptacle is provided integrally together with at least one of the cameras.

4. The system according to any one of claims 2 and 3, wherein the image

processors analyze colors, shapes, and sizes of the medications in the images to identify the medications clustered in the receptacle as aforesaid.

5. The system according to any one of claims 2 to 4, further comprising one or more data analysis algorithms, and wherein the image processors apply the data analysis algorithms to analyze the images as aforesaid.

6. The system according to any one of claims 2 to 5, wherein the receptacle has sloped interior walls and an interior bottom portion that are shaped so that the image processors can readily count and identify the medications in the receptacle.

7. The system according to any one of claims 1 to 6, wherein the sensors comprise one or more photosensors, light sensors, capacitive sensors, proximity sensors, ultrasonic sensors, accelerometers, motion sensors, temperature sensors, weight sensors, or microphones.

8. The system according to any one of claims 1 to 7, further adapted for use by a caregiver who is associated with the user, wherein the processors generate and convey one or more medication notifications to the caregiver based on: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

9. The system according to any one of claims 1 to 7, wherein the system is adapted for use with the medications to be consumed in keeping with a predetermined schedule; wherein the user devices further comprise a notification system for presenting one or more scheduling prompts and alert notifications to the user; wherein the processors further analyze the data and generate: (i) the scheduling prompts when the medications are to be consumed in keeping with the predetermined schedule; and (ii) the alert notifications when the processors determine that one or more mismatched conditions exist between the predetermined schedule in comparison to the data; and wherein the processors convey the scheduling prompts and the alert notifications to the notification system for presentation to the user as aforesaid.

10. The system according to claim 9, wherein the processors determine that the mismatched conditions exist when: (a) the medications differ in number from those to be consumed in keeping with the predetermined schedule; (b) the medications were not consumed in keeping with the predetermined schedule; (c) the medications were consumed other than in keeping with the predetermined schedule; (d) a restriction in the predetermined schedule was not followed in consuming the medications; and/or (e) the medications differ in type from those to be consumed in keeping with the predetermined schedule.

11. The system according to any one of claims 9 to 10, wherein the notification system presents the scheduling prompts and the alert notifications audibly, visually, or by vibrations.

12. The system according to any one of claims 9 to 11 , wherein the notification system comprises one or more lights, projectors, speakers, or vibration devices to present the scheduling prompts and the alert notifications.

13. The system according to any one of claims 9 to 12, wherein the scheduling prompts and the alert notifications comprise one or more text, image, time, date, and/or instruction data that are presented to the user by the notification system.

14. The system according to any one of claims 9 to 13, further comprising a mobile or web-based application that selectively grants permission for the user or for a third party to review, substantially in real-time: the predetermined schedule; the data; the types and quantities of the medications identified as clustered in the receptacle; the consumption events; the scheduling prompts; the alert notifications; and/or the mismatched conditions.

15. The system according to any one of claims 9 to 14, wherein the system is further adapted for use with one or more of the following as the predetermined schedule: a user-entered schedule, a learned schedule, and/or an adaptive schedule.

16. The system according to any one of claims 9 to 15, wherein the user devices further comprise a base station, and wherein the base station is provided integrally together with the notifications system.

17. The system according to any one of claims 1 to 15, wherein the user devices further comprise a base station, and wherein the receptacle is a bowl that is removable from the base station.

18. The system according to any one of claims 1 to 15, wherein the user devices further comprise a device communications interface that remotely transmits the data; and wherein the system further comprises: a networked communications interface that receives the data remotely from the device communications interface; and a networked database that, remotely from the user devices, collects and stores the data, the types and quantities of the medications identified as clustered in the receptacle, and the consumption events.

19. The system according to claim 18, wherein the device communications interface uses a wireless communication protocol to remotely transmit the data.

20. The system according to any one of claims 18 to 19, wherein the user devices further comprise a base station, and wherein the base station is provided integrally together with the device communications interface.

21. The system according to any one of claims 18 to 19, wherein the user devices further comprise a base station, and wherein the base station further comprises a battery to at least partially power the device communications interface and the sensors.

22. The system according to any one of claims 18 to 19, wherein the user devices further comprise a base station, and wherein the base station further comprises a wired power input to at least partially power the device communications interface and the sensors.

23. The system according to any one of claims 18 to 19, wherein the user devices further comprise a base station, and wherein the processors comprise: a base station processor, onboard the base station, that processes and conveys the data detected by the sensors for transmission by the device communications interface; and a networked processor that accesses the data stored in the networked database.

24. The system according to any one of claims 18 to 23, further comprising one or more application programming interfaces that enable access to the user devices, the networked database, and/or the processors.

25. The system according to claim 24, wherein the application programming interfaces are adapted for use with a mobile or web-based application to selectively grant permission for the user or for a third party to review, substantially in real-time: the data; the types and quantities of the medications identified as clustered in the

receptacle; and/or the consumption events.

26. The system according to any one of claims 14 and 25, adapted for use by one or more caregivers, family members, doctors, nurses, medical staff, clinical trial

administrators, pharmacists, pharmacies, medication-related solution providers, or insurance agencies as the third party.

27. A clustering device for monitoring medication consumption habits, and for use with one or more medications to be consumed by a user, the device comprising: a) a receptacle adapted to receive and cluster the medications; b) one or more sensors that detect data concerning the medications clustered in the receptacle; and c) one or more processors that analyze the data to identify types and quantities of the medications clustered in the receptacle and to identify, after any said removal of the medications from the receptacle, one or more consumption events.

28. The device according to claim 27, wherein the sensors comprise one or more cameras, wherein the data comprise one or more images of the medications clustered in the receptacle, and wherein the processors comprise one or more image processors that analyze the images to count and identify the medications clustered in the

receptacle.

29. The device according to claim 28, wherein the receptacle is provided integrally together with at least one of the cameras.

30. The device according to any one of claims 28 and 29, wherein the image processors analyze colors, shapes, and sizes of the medications in the images to identify the medications clustered in the receptacle as aforesaid.

31. The device according to any one of claims 28 to 30, further comprising one or more data analysis algorithms, and wherein the image processors apply the data analysis algorithms to analyze the images as aforesaid.

32. The device according to any one of claims 28 to 31 , wherein the receptacle has sloped interior walls and an interior bottom portion that are shaped so that the image processors can readily count and identify the medications in the receptacle.

33. The device according to any one of claims 27 to 32, wherein the sensors comprise one or more photosensors, light sensors, capacitive sensors, proximity sensors, ultrasonic sensors, accelerometers, motion sensors, temperature sensors, weight sensors, or microphones.

34. The device according to any one of claims 27 to 33, further adapted for use by a caregiver who is associated with the user, wherein the processors generate and convey one or more medication notifications to the caregiver based on: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

35. The device according to any one of claims 27 to 33, wherein the device is adapted for use with the medications to be consumed in keeping with a predetermined schedule; wherein the device further comprises a notification system for presenting one or more scheduling prompts and alert notifications to the user; wherein the processors further analyze the data and generate: (i) the scheduling prompts when the medications are to be consumed in keeping with the predetermined schedule; and (ii) the alert notifications when the processors determine that one or more mismatched conditions exist between the predetermined schedule in comparison to the data; and wherein the processors convey the scheduling prompts and the alert notifications to the notification system for presentation to the user as aforesaid.

36. The device according to claim 35, wherein the processors determine that the mismatched conditions exist when: (a) the medications differ in number from those to be consumed in keeping with the predetermined schedule; (b) the medications were not consumed in keeping with the predetermined schedule; (c) the medications were consumed other than in keeping with the predetermined schedule; (d) a restriction in the predetermined schedule was not followed in consuming the medications; and/or (e) the medications differ in type from those to be consumed in keeping with the predetermined schedule.

37. The device according to any one of claims 35 to 36, wherein the notification system presents the scheduling prompts and the alert notifications audibly, visually, or by vibrations.

38. The device according to any one of claims 35 to 37, wherein the notification system comprises one or more lights, projectors, speakers, or vibration devices to present the scheduling prompts and the alert notifications.

39. The device according to any one of claims 35 to 38, wherein the scheduling prompts and the alert notifications comprise one or more text, image, time, date, and/or instruction data that are presented to the user by the notification system.

40. The device according to any one of claims 35 to 39, further comprising a base station that is provided integrally together with the notifications system.

41. The device according to any one of claims 27 to 39, further comprising a base station, wherein the receptacle is a bowl that is removable from the base station.

42. The device according to any one of claims 27 to 39, further adapted for use with a networked communications interface and a networked database; wherein the device further comprises a device communications interface that remotely transmits the data to the networked communications interface for collection and storage in the networked database.

43. The device according to claim 42, wherein the device communications interface uses a wireless communication protocol to remotely transmit the data.

44. The device according to any one of claims 42 to 43, further comprising a base station that is provided integrally together with the device communications interface.

45. The device according to any one of claims 42 to 43, further comprising a base station having a battery to at least partially power the device communications interface and the sensors.

46. The device according to any one of claims 42 to 43, further comprising a base station having a wired power input to at least partially power the device communications interface and the sensors.

47. The device according to any one of claims 40-41 , 44-46, wherein at least one of the processors is onboard the base station.

48. The device according to any one of claims 27 to 47, further comprising one or more application programming interfaces that are adapted for use with a mobile or web-based application to selectively grant permission for the user or for a third party to review, substantially in real-time: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

49. A clustering method for monitoring medication consumption habits, and for use with one or more medications to be consumed by a user, the method comprising the steps of: a) a clustering step, wherein the medications are received and clustered in a

receptacle; b) a detection step, wherein one or more sensors are used to detect data concerning the medications clustered in the receptacle and any removal of the medications from the receptacle; c) a processing step, wherein one or more processors analyze the data to identify types and quantities of the medications clustered in the receptacle and to identify, after any said removal of the medications from the receptacle, one or more consumption events.

50. The method according to claim 49, wherein in the detection step, the sensors comprise one or more cameras, and the data comprise one or more images of the medications clustered in the receptacle, and in the processing step, the processors comprise one or more image processors that analyze the images to count and identify the medications clustered in the receptacle.

51. The method according to claim 50, wherein in the processing step, the image processors analyze colors, shapes, and sizes of the medications in the images to identify the medications clustered in the receptacle as aforesaid.

52. The method according to any one of claims 50 to 51 , wherein in the processing step, the image processors apply one or more data analysis algorithms to analyze the images as aforesaid.

53. The method according to any one of claims 50 and 52, wherein before the clustering step, the receptacle is provided with sloped interior walls and an interior bottom portion that are shaped so that, after the clustering step in the processing step, the image processors can readily count and identify the medications in the receptacle.

54. The method according to any one of claims 49 to 53, further adapted for use by a caregiver who is associated with the user, wherein in the processing step, the processors generate and convey one or more medication notifications to the caregiver based on: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

55. The method according to any one of claims 49 to 53, wherein the method is adapted for use with the medications to be consumed in keeping with a predetermined schedule; wherein in the processing step, the processors further analyze the data and generate one or more: (i) scheduling prompts when the medications are to be consumed in keeping with the predetermined schedule, and (ii) alert notifications when the processors determine that one or more mismatched conditions exist between the predetermined schedule in comparison to the data; and wherein the method further comprises a notification step, wherein the scheduling prompts and the alert notifications are presented to the user.

56. The method according to claim 55, wherein in the processing step, the processors determine that the mismatched conditions exist when: (a) the medications differ in number from those to be consumed in keeping with the predetermined schedule; (b) the medications were not consumed in keeping with the predetermined schedule; (c) the medications were consumed other than in keeping with the

predetermined schedule; (d) a restriction in the predetermined schedule was not followed in consuming the medications; and/or (e) the medications differ in type from those to be consumed in keeping with the predetermined schedule.

57. The method according to any one of claims 55 to 56, wherein in the notification step, the scheduling prompts and the alert notifications are presented audibly, visually, or by vibrations.

58. The method according to any one of claims 55 to 57, wherein in the notification step, one or more text, image, time, date, and/or instruction data that are presented.

59. The method according to any one of claims 49 to 58, further comprising a transmission step of transmitting the data, using a device communications interface, to a remote networked communications communications interface; and wherein the method further comprises a step of collecting and storing, in a networked database that is located remotely from the receptacle: the data, the types and quantities of the medications identified as clustered in the receptacle, and the consumption events.

60. The method according to claim 59, wherein in the transmission step, the device communications interface uses a wireless communication protocol to remotely transmit the data.

61. The method according to any one of claims 59 to 60, wherein in the processing step: a base station processor, onboard a base station that is located locally to the receptacle, processes and conveys the data detected by the sensors for transmission by the device communications interface; and a networked processor accesses the data stored in the networked database.

62. The method according to any one of claims 49 to 61 , further comprising an access step, wherein a mobile or web-based application selectively grants permission for the user or for a third party to access or review, substantially in real-time: the data; the types and quantities of the medications identified as clustered in the receptacle; and/or the consumption events.

63. The method according to claim 62, wherein in the access step, the mobile or web-based application works with one or more application programming interfaces to enable said access or review.

64. The method according to any one of claims 62 and 63, wherein in the access step, the third party is a caregiver, family member, doctor, nurse, medical staff member, clinical trial administrator, pharmacists, pharmacies, medication-related solution providers, or insurance agency.