Medication storage device and methods for determining identity classifications for items stored therein

Abstract

Various embodiments of the present disclosure provide a medication storage device and associated methods for determining identity classifications for items stored in the medication storage device. The medication store device may include an imaging system configured to generate one or more images of one or more items stored in the medication storage device. The medication storage device may include one or more processors configured to determine one or more identity classifications for the one or more items stored in the medication storage device based at least in part on the one or more images. The medication storage device may include a network interface component configured to communicate information to one or more individuals based at least in part on the one or more identity classifications.

Description

MEDICATION STORAGE DEVICE AND METHODS FOR DETERMINING IDENTITYCLASSIFICATIONS FOR ITEMS STORED THEREINCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Appl. No. 63 / 612,724, filed December 20, 2023 the contents of which are incorporated in their entirety by reference.TECHNICAL FIELD

[0002] The present application relates to the technical field of healthcare. In particular, the invention relates to a medication storage device and methods for determining identity classifications for items stored therein.BACKGROUND

[0003] Some individuals may encounter various challenges associated with adhering to medication dosing schedules. For example, forgetfulness, busy daily routines, and various other sources of distraction may make it difficult for an individual to remember to take specific quantities of one or more medications at specific times of the day. In some examples, the fear of side effects or the absence of immediate, noticeable benefits from taking a medication may lead to intentional non-compliance. In other examples, individuals experiencing cognitive decline, cognitive impairments, or disabilities may be more likely to experience challenges in adhering to medication dosing schedules or using a conventional pill bottle. Additionally, or alternatively, some individuals may abuse various medications by either distributing their medications to others illegally or by taking more than a prescribed dosage, which has notoriously contributed to illicit drug epidemics, accidental or intentional overdose, and other adverse health consequences. In many conventional systems, an individual that is prescribed a medication may receive written instructions for taking the medication and may receive a quantity of the medication in a conventional container, such as a pill bottle. However, the use of conventional pill bottles and dosing protocols may increase a likelihood of incorrect dosing by the individual, which may result in adverse health effects.BRIEF SUMMARY

[0004] In accordance with one or more examples described herein, a medication storage device (e.g., a pill bottle) may be equipped with one or more sensing elements. The one or more sensing elements may be configured to detect or sense information. For example, the one or more sensing systems may include a weight measurement system (e.g., a load cell) configured to detect and output weight information for one or more items located inside of the medication storage device. In some examples, the one or more sensing systems may include an imaging system (e.g., an infrared camera) configured to generate one or more images of the one or more items (e.g., medications, objects other than medications) stored in the medication storage device. In some examples, the medication storage device may include one or more processors, which may be configured to perform one or more processing operations to analyze information received from the one or more sensing systems. For example, the one or more processors may determine one or more identity classifications (e.g., item types, item geometries) for the one or more items stored in the medication storage device based on the one or more images.

[0005] In some examples, the medication storage device may include a network interface configured to communicate information to one or more individuals based on information received from the one or more processors. For example, the network interface component may transmit or cause transmission of one or more messages to one or more individuals, such as a healthcare professional, an emergency contact for a user of the medication storage device, the user of the medication storage device, or any combination thereof. The one or more messages may include information, such as dosing information (e.g., indicative of whether a dosing schedule has been adhered to), or information indicating that the medication storage device includes one or more objects or medications other than one or more medications prescribed to the user. In some examples, the information indicating that the medication storage device includes one or more objects or medications other than the one or more medications prescribed to the user may indicate that the medication storage device was improperly loaded at a pharmacy or that the user has intentionally attempted to remove one or more pills without detection. Accordingly, the one or more messages may facilitate improved safety and healthcare outcomes for the user (e.g., an emergency contact or healthcare professional may be notified and may intervene if a user is not correctly dosing a prescribed medication).

[0006] In one embodiment, a medication storage device includes an imaging system configured to generate one or more images of one or more items stored in the medication storage device; one or more processors configured to determine one or more identity classifications for the one or more items stored in the medication storage device based at least in part on the one or more images; and a network interface component configured to communicate information to one or more individuals based at least in part on the one or more identity classifications. In some examples, the information includes an indication that the medication storage device includes an item other than a medication prescribed to a user. In some examples, the medication storage device further includes a weight measurement system configured to generate, at a plurality of time instances, a plurality of weight measurements for respective items stored in the medication storage device at respective time instances of the plurality of time instances.

[0007] In some examples, the imaging system is configured to generate the one or more images of the one or more items based at least in part on a comparison of a first weight measurement of the plurality of weight measurements and a second weight measurement of the plurality of weight measurements. In some examples, the one or more individuals include one or more of (i) a healthcare professional or (ii) an emergency contact for a user. In some examples, the medication storage device further includes an access component configured to enable or disable access to the one or more items stored in the medication storage device based at least in part on the one or more identity classifications.

[0008] In one embodiment, a method includes generating one or more images of one or more items stored in a medication storage device based at least in part on filling the medication storage device with the one or more items; determining one or more identity classifications for the one or more items stored in the medication storage device based at least in part on the one or more images, wherein an identity classification of the one or more identity classifications indicates a type of medication; and communicating information to one or more individuals based at least in part on the one or more identity classifications, wherein the one or more individuals include one or more of (i) a healthcare professional or (ii) an emergency contact for a user.

[0009] Embodiments provided herein include a medication storage device including: a body defining a cavity; a lid configured to close the cavity; an image sensor configured to capture one or more images within the cavity; one or more processors configured to determine, based on the one or more images, one or more identity classifications for one ormore items stored in the cavity; and a network interface component configured to communicate information based at least in part on the one or more identity classifications.

[0010] The image sensor of an example embodiment is configured to capture an image of contents of the cavity in response to the lid closing the cavity. According to some embodiments the image sensor is disposed within the lid. The medication storage device of some embodiments further includes a load cell disposed at a base of the cavity, where the load cell is configured to determine a weight of the one or more items stored in the cavity.

[0011] According to certain embodiments the image sensor is configured to capture the one or more images within the cavity based at least in part on a signal from the load cell. The image sensor of an example embodiment is configured to capture the one or more images within the cavity based at least on a comparison of a first weight measurement of the one or more items stored in the cavity and a second weight measurement of the one or more items stored in the cavity. The comparison of some embodiments reflects a removal of at least one of the one or more items stored in the cavity.

[0012] According to some embodiments the load cell is configured to determine the weight of the one or more items stored in the cavity in response to the lid closing the cavity. The medication storage device of some embodiments further includes a display positioned on the lid, wherein the display depicts information associated with the one or more items stored in the cavity. According to some embodiments the information associated with the one or more items stored in the cavity includes the one or more identity classifications for the one or more items stored in the cavity. The information associated with the one or more items stored in the cavity includes, in some embodiments, a quantity for each of the one or more identity classifications for the one or more items stored in the cavity.

[0013] The medication storage device of some embodiments further includes at least one rechargeable power supply for powering the image sensor, the one or more processors, and the network interface component. The medication storage device of some embodiments further includes a lock to secure the lid to the body preventing access to the cavity, where the lock is configured to enable or disable access to the one or more items stored in the medication storage device based at least in part on the one or more identity classifications.

[0014] According to some embodiments the lock is configured to enable access to the one or more items stored in the medication storage device in response to a quantity of the one ormore items stored in the medication storage device falling below a predetermined threshold. According to certain embodiments the lock is configured to enable access to the one or more items stored in the medication storage device in response to the one or more identity classifications not including a controlled substance.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0016] FIG. 1 provides an exemplary overview of a system that can be used to practice embodiments of the present disclosure.

[0017] FIG. 2 provides an exemplary computing entity in accordance with some embodiments discussed herein.

[0018] FIG. 3 provides an exemplary external computing entity in accordance with some embodiments discussed herein.

[0019] FIG. 4 illustrates an exemplary medication storage device, according to one or more embodiments described herein;

[0020] FIG. 5 illustrates an exemplary assembly view, according to one or more embodiments described herein;

[0021] FIG. 6 illustrates an exemplary assembly view, according to one or more embodiments described herein;

[0022] FIG. 7 illustrates an exemplary electronics module, according to one or more embodiments described herein;

[0023] FIG. 8 illustrates an exemplary medication storage device, according to one or more embodiments described herein;

[0024] FIG. 9 illustrates an exemplary medication storage device, according to one or more embodiments described herein;

[0025] FIG. 10 illustrates an exemplary audio visual system, according to one or more embodiments described herein; and

[0026] FIG. 11 illustrates an exemplary flowchart, according to one or more embodiments described herein.DETAILED DESCRIPTION

[0001] Various embodiments of the present disclosure are described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the present disclosure are shown. Indeed, the present disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term “or” is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms “illustrative” and “example” are used to be examples with no indication of quality level. Terms such as “computing,” “determining,” “generating,” and / or similar words are used herein interchangeably to refer to the creation, modification, or identification of data. Further, “based on,” “based at least in part on,” “based at least on,” “based upon,” and / or similar words are used herein interchangeably in an open-ended manner such that they do not necessarily indicate being based only on or based solely on the referenced element or elements unless so indicated. Like numbers refer to like elements throughout.I. Computer Program Products, Methods, and Computing Entities

[0002] Embodiments of the present disclosure may be implemented in various ways, including as computer program products that comprise articles of manufacture. Such computer program products may include one or more software components including, for example, software objects, methods, data structures, or the like. A software component may be coded in any of a variety of programming languages. An illustrative programming language may be a lower-level programming language such as an assembly language associated with a particular hardware framework and / or operating system platform. A software component comprising assembly language instructions may require conversion into executable machine code by an assembler prior to execution by the hardware framework and / or platform. Another example programming language may be a higher-level programming language that may be portable across multiple frameworks. A software component comprising higher-level programming language instructions may require conversion to an intermediate representation by an interpreter or a compiler prior to execution.

[0003] Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database query, or search language, and / or a report writing language. In one or more example embodiments, a software component comprising instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form. A software component may be stored as a fde or other data storage construct. Software components of a similar type or functionally related may be stored together such as in a particular directory, folder, or library. Software components may be static (e.g., pre- established, or fixed) or dynamic (e.g., created or modified at the time of execution).

[0004] A computer program product may include non-transitory computer-readable storage medium storing applications, programs, program modules, scripts, source code, program code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and / or the like (also referred to herein as executable instructions, instructions for execution, computer program products, program code, and / or similar terms used herein interchangeably). Such non-transitory computer-readable storage media include all computer-readable media (including volatile and non-volatile media).

[0005] In one embodiment, a non-volatile computer-readable storage medium may include a floppy disk, flexible disk, hard disk, solid-state storage (SSS) (e.g., a solid-state drive (SSD)), solid state card (SSC), solid state module (SSM), enterprise flash drive, magnetic tape, or any other non-transitory magnetic medium, and / or the like. A non-volatile computer-readable storage medium may also include a punch card, paper tape, optical mark sheet (or any other physical medium with patterns of holes or other optically recognizable indicia), compact disc read only memory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc (DVD), Blu-ray disc (BD), any other non-transitory optical medium, and / or the like. Such a non-volatile computer-readable storage medium may also include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., Serial, NAND, NOR, and / or the like), multimedia memory cards (MMC), secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF) cards, Memory Sticks, and / or the like. Further, a non-volatile computer-readablestorage medium may also include conductive-bridging random access memory (CBRAM), phase-change random access memory (PRAM), ferroelectric random-access memory (FeRAM), non-volatile random-access memory (NVRAM), magnetoresistive random-access memory (MRAM), resistive random-access memory (RRAM), Silicon-Oxide-Nitride-Oxide- Silicon memory (SONOS), floating junction gate random access memory (FJG RAM), Millipede memory, racetrack memory, and / or the like.

[0006] In one embodiment, a volatile computer-readable storage medium may include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data-out dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), double data rate type two synchronous dynamic random access memory (DDR2 SDRAM), double data rate type three synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM), dual in-line memory module (DIMM), single in-line memory module (SIMM), video random access memory (VRAM), cache memory (including various levels), flash memory, register memory, and / or the like. It will be appreciated that where embodiments are described to use a computer-readable storage medium, other types of computer-readable storage media may be substituted for or used in addition to the computer-readable storage media described above.

[0007] As should be appreciated, various embodiments of the present disclosure may also be implemented as methods, apparatuses, systems, computing devices, computing entities, and / or the like. As such, embodiments of the present disclosure may take the form of an apparatus, system, computing device, computing entity, and / or the like executing instructions stored on a computer-readable storage medium to perform certain steps or operations. Thus, embodiments of the present disclosure may also take the form of an entirely hardware embodiment, an entirely computer program product embodiment, and / or an embodiment that comprises combination of computer program products and hardware performing certain steps or operations.

[0008] Embodiments of the present disclosure are described below with reference to block diagrams and flowchart illustrations. Thus, it should be understood that each block of the block diagrams and flowchart illustrations may be implemented in the form of a computer program product, an entirely hardware embodiment, a combination of hardware and computer program products, and / or apparatuses, systems, computing devices, computing entities, and / or the like carrying out instructions, operations, steps, and similar words used interchangeably (e.g., the executable instructions, instructions for execution, program code, and / or the like) on a computer-readable storage medium for execution. For example, retrieval, loading, and execution of code may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some example embodiments, retrieval, loading, and / or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and / or executed together. Thus, such embodiments can produce specifically configured machines performing the steps or operations specified in the block diagrams and flowchart illustrations. Accordingly, the block diagrams and flowchart illustrations support various combinations of embodiments for performing the specified instructions, operations, or steps.II. Example System Framework

[0009] FIG. 1 provides an example overview of a system 100 that can be used to practice embodiments of the present disclosure. The system 100 includes a medication storage system 101 comprising a computing entity 106 configured to perform processing or computing operations associated with the medication storage system 101. The medication storage system 101 may communicate with one or more external computing entities 102 using one or more communication networks. Examples of communication networks include any wired or wireless communication network including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software and / or firmware required to implement it (e.g., network routers, and / or the like).

[0010] The system 100 includes a storage subsystem 108 configured to store at least a portion of the data utilized by the medication storage system 101. The computing entity 106 may be in communication with one or more external computing entities 102. In oneexample, the computing entity 106 may be configured to generate a prediction, classification, and / or any other data insight based on data provided by a sensing element (not shown) of the medication storage system 101.

[0011] The computing entity 106 may be configured to receive requests and / or data from the one or more external computing entities 102, process the requests and / or data to generate outputs (e.g., classification outputs), and provide the outputs to at least one of the external computing entities 102. In some embodiments, the external computing entity 102, for example, periodically updates / provides raw and / or processed input data to the medication storage system 101. The external computing entities 102 may further generate user interface data (e.g., one or more data objects) corresponding to the outputs and may provide (e.g., transmit, send, and / or the like) the user interface data corresponding with the outputs for presentation to the external computing entity 102 (e.g., to an end-user).

[0012] The storage subsystem 108 may be configured to store at least a portion of the data utilized by the computing entity 106 to perform one or more steps / operations and / or tasks described herein. The storage subsystem 108 may be configured to store at least a portion of operational data and / or operational configuration data including operational instructions and parameters utilized by the computing entity 106 to perform the one or more steps / operations described herein. The storage subsystem 108 may include one or more storage units, such as multiple distributed storage units that are connected through a computer network. Each storage unit in the storage subsystem 108 may store at least one of one or more data assets and / or data about the computed properties of one or more data assets. Moreover, each storage unit in the storage subsystem 108 may include one or more non-volatile storage or memory media including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, memory sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, and / or the like.

[0013] In accordance with one or more examples described herein, the medication storage system 101 (e.g., a medication storage device) may be equipped with one or more sensing elements (not shown). The one or more sensing elements may be configured to detect or sense information. For example, the one or more sensing systems may include a weight measurement system (e.g., a load cell) configured to detect and output weight informationfor one or more items located inside of the medication storage system 101. In some examples, the one or more sensing systems may include an imaging system which includes an image sensor (e.g., an infrared camera) configured to generate one or more images of the one or more items (e.g., medications, objects other than medications) stored in the medication storage system 101. In some examples, the medication storage system 101 may include one or more processors (e.g., of the computing entity 106), which may be configured to perform one or more processing operations to analyze information received from the one or more sensing systems. For example, the one or more processors may determine one or more identity classifications (e.g., item types) for the one or more items stored in the medication storage system 101 based on the one or more images.

[0014] In some examples, the medication storage system 101 may include a network interface (e.g., of the computing entity 106) configured to communicate information to one or more external computing entities 102 based on information received from the one or more processors. For example, the network interface component may transmit or cause transmission of one or more messages to one or more external computing entities 102, which may be utilized by or associated with one or more individuals, such as a healthcare professional, an emergency contact for a user of the medication storage system 101, the user of the medication storage system 101, or any combination thereof. The one or more messages may include information, such as information indicating that the medication storage system 101 includes one or more objects or medications other than one or more medications prescribed to the user. Accordingly, the one or more messages may facilitate improved safety and healthcare outcomes for the user (e.g., an emergency contact or healthcare professional may be notified and may intervene if a user is not correctly dosing a prescribed medication).Example Computing Entity

[0015] FIG. 2 provides an example computing entity 106 in accordance with some embodiments discussed herein. In general, the terms computing entity, computer, entity, device, system, and / or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, desktops, mobile phones, tablets, notebooks, laptops, distributed systems, kiosks, input terminals, servers or server networks, blades,gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and / or any combination of devices or entities adapted to perform the functions, steps / operations, and / or processes described herein. Such functions, steps / operations, and / or processes may include, for example, transmitting, receiving, operating on, processing, displaying, storing, determining, creating / generating, monitoring, evaluating, comparing, and / or similar terms used herein interchangeably. In one embodiment, these functions, steps / operations, and / or processes can be performed on data, content, information, and / or similar terms used herein interchangeably.

[0016] The computing entity 106 may include a network interface 208 for communicating with various computing entities, such as by communicating data, content, information, and / or similar terms used herein interchangeably that can be transmitted, received, operated on, processed, displayed, stored, and / or the like.

[0017] In one embodiment, the computing entity 106 may include or be in communication with a processing element 202 (also referred to as one or more processors, processing circuitry, and / or similar terms used herein interchangeably) that communicate with other elements within the computing entity 106 via a bus, for example. As will be understood, the processing element 202 may be embodied in a number of different ways including, for example, as at least one processor / processing apparatus, one or more processors / processing apparatuses, and / or the like.

[0018] For example, the processing element 202 may be embodied as one or more complex programmable logic devices (CPLDs), microprocessors, multi-core processors, coprocessing entities, application-specific instruction-set processors (ASIPs), microcontrollers, and / or controllers. Further, the processing element 202 may be embodied as one or more other processing devices or circuitry. The term circuitry may refer to an entirely hardware embodiment or a combination of hardware and computer program products. Thus, the processing element 202 may be embodied as integrated circuits, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), hardware accelerators, other circuitry, and / or the like.

[0019] As will therefore be understood, the processing element 202 may be configured for a particular use or configured to execute instructions stored in one or more memory elements including, for example, one or more volatile memories 206 and / or non-volatilememories 204. As such, whether configured by hardware or computer program products, or by a combination thereof, the processing element 202 may be capable of performing steps or operations according to embodiments of the present disclosure when configured accordingly. The processing element 202, for example in combination with the one or more volatile memories 206 and / or or non-volatile memories 204, may be capable of implementing one or more methods or computer-implemented methods as described herein. In some implementations, the computing entity 106 can include a computing apparatus, the processing element 202 can include at least one processor of the computing apparatus, and the one or more volatile memories 206 and / or non-volatile memories 204 can include at least one memory including program code. The at least one memory and the program code can be configured to, upon execution by the at least one processor, cause the computing apparatus to perform one or more steps / operations described herein.

[0020] The non-volatile memories 204 (also referred to as non-volatile storage, memory, memory storage, memory circuitry, media, and / or similar terms used herein interchangeably) may include at least one non-volatile memory device, including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, and / or the like.

[0021] As will be recognized, the non-volatile memories 204 may store databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and / or the like. The term database, database instance, database management system, and / or similar terms used herein interchangeably may refer to a collection of records or data that is stored in a computer-readable storage medium using one or more database models, such as a hierarchical database model, network model, relational model, entity-relationship model, object model, document model, semantic model, graph model, and / or the like.

[0022] The one or more volatile memories (also referred to as volatile storage, memory, memory storage, memory circuitry, media, and / or similar terms used herein interchangeably) can include at least one volatile memory 206 device, including but not limited to RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM,DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and / or the like.

[0023] As will be recognized, the volatile memories 206 may be used to store at least portions of the databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and / or the like being executed by, for example, the processing element 202. Thus, the databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and / or the like may be used to control certain embodiments of the operation of the computing entity 106 with the assistance of the processing element 202.

[0024] As indicated, in one embodiment, the computing entity 106 may also include the network interface 208 for communicating with various computing entities, such as by communicating data, content, information, and / or the like that can be transmitted, received, operated on, processed, displayed, stored, and / or the like. Such communication data may be executed using a wired data transmission protocol, such as fiber distributed data interface (FDDI), digital subscriber line (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay, data over cable service interface specification (DOCSIS), or any other wired transmission protocol. Similarly, the computing entity 106 may be configured to communicate via wireless client communication networks using any of a variety of protocols, such as general packet radio service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 IX (IxRTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), ultra-wideband (UWB), infrared (IR) protocols, near field communication (NFC) protocols, Wibree, Bluetooth protocols, wireless universal serial bus (USB) protocols, and / or any other wireless protocol.

[0025] In accordance with one or more examples described herein, the medication storage system 101 (e.g., a medication storage device) may be equipped with one or more sensing elements (not shown). The one or more sensing elements may be configured to detect or sense information. For example, the one or more sensing systems may include a weight measurement system (e.g., a load cell) configured to detect and output weight information for one or more items located inside of the medication storage system 101. In some examples, the one or more sensing systems may include an imaging system including an image sensor (e.g., an infrared camera) configured to generate one or more images of the one or more items (e.g., medications, objects other than medications) stored in the medication storage system 101. In some examples, the processing element 202 may receive information from the one or more sensing systems and may perform one or more processing operations using the information. For example, the processing element 202 may determine one or more identity classifications (e.g., item types) for the one or more items stored in the medication storage system 101 based on the one or more images.

[0026] In some examples, the processing element 202 may communicate information to the network interface 208. For example, the processing element 202 may communicate the one or more identity classifications or information associated with the one or more identify classifications to the network interface 208. The network interface 208 may be configured to communicate information to one or more external computing entities 102 based on information received from the processing element 202. For example, the network interface component may transmit or cause transmission of one or more messages to one or more external computing entities 102, which may be utilized by or associated with one or more individuals, such as a healthcare professional, an emergency contact for a user of the medication storage system 101, the user of the medication storage system 101, or any combination thereof. The one or more messages may include information, such as information indicating that the medication storage system 101 includes one or more objects or medications other than one or more medications prescribed to the user. Accordingly, the one or more messages may facilitate improved safety and healthcare outcomes for the user (e.g., an emergency contact or healthcare professional may be notified and may intervene if a user is not correctly dosing a prescribed medication).Example External Computing Entity

[0027] FIG. 3 provides an example external computing entity 102 in accordance with some embodiments discussed herein. In general, the terms device, system, computing entity, entity, and / or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, desktops, mobile phones, tablets, phablets, notebooks, laptops, distributed systems, kiosks, input terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and / or any combination of devices or entities adapted to perform the functions, steps / operations, and / or processes described herein. The external computing entities 102 can be operated by various parties (e.g., a user of a medication storage system, a healthcare professional, an emergency contact for the user, etc.). As shown in FIG. 3, the external computing entity 102 may include an antenna 312, a transmitter 304 (e.g., radio), a receiver 306 (e.g., radio), and / or an external entity processing element 308 (e.g., CPLDs, microprocessors, multi-core processors, coprocessing entities, ASIPs, microcontrollers, and / or controllers) that provides signals to and receives signals from the transmitter 304 and the receiver 306, correspondingly. As will be understood, the external entity processing element 308 may be embodied in a number of different ways including, for example, as at least one processor / processing apparatus, one or more processors / processing apparatuses, and / or the like as described herein with reference the processing element 202.

[0028] The signals provided to and received from the transmitter 304 and the receiver 306, correspondingly, may include signaling information / data in accordance with air interface standards of applicable wireless systems. In this regard, the external computing entity 102 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the external computing entity 102 may operate in accordance with any of a number of wireless communication standards and protocols, such as those described above with regard to the computing entity 106. In a particular embodiment, the external computing entity 102 may operate in accordance with multiple wireless communication standards and protocols, such as UMTS, CDMA2000, IxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, USB, and / or thelike. Similarly, the external computing entity 102 may operate in accordance with multiple wired communication standards and protocols, such as those described above with regard to the computing entity 106 via an external entity network interface 320.

[0029] Via these communication standards and protocols, the external computing entity 102 can communicate with various other entities using means such as Unstructured Supplementary Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and / or Subscriber Identity Module Dialer (SIM dialer). The external computing entity 102 can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including executable instructions, applications, program modules), operating system, and / or the like.

[0030] According to one embodiment, the external computing entity 102 may include location determining embodiments, devices, modules, functionalities, and / or the like. For example, the external computing entity 102 may include outdoor positioning embodiments, such as a location module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, direction, heading, speed, universal time (UTC), date, and / or various other information / data. In one embodiment, the location module can acquire data such as ephemeris data, by identifying the number of satellites in view and the relative positions of those satellites (e.g., using global positioning systems (GPS)). The satellites may be a variety of different satellites, including Low Earth Orbit (LEO) satellite systems, Department of Defense (DOD) satellite systems, the European Union Galileo positioning systems, the Chinese Compass navigation systems, Indian Regional Navigational satellite systems, and / or the like. This data can be collected using a variety of coordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes, Seconds (DMS); Universal Transverse Mercator (UTM); Universal Polar Stereographic (UPS) coordinate systems; and / or the like. Alternatively, the location information / data can be determined by triangulating a position of the external computing entity 102 in connection with a variety of other systems, including cellular towers, Wi-Fi access points, and / or the like. Similarly, the external computing entity 102 may include indoor positioning embodiments, such as a location module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, direction, heading, speed, time, date, and / or various other information / data. Some of the indoor systems may use various position or location technologies including RFID tags,indoor beacons or transmitters, Wi-Fi access points, cellular towers, nearby computing devices (e.g., smartphones, laptops) and / or the like. For instance, such technologies may include the iBeacons, Gimbal proximity beacons, Bluetooth Low Energy (BLE) transmitters, NFC transmitters, and / or the like. These indoor positioning embodiments can be used in a variety of settings to determine the location of someone or something to within inches or centimeters.

[0031] The external computing entity 102 may include a user interface 316 (e.g., a display, speaker, and / or the like) that can be coupled to the external entity processing element 308. In addition, or alternatively, the external computing entity 102 can include a user input interface 318 (e.g., keypad, touch screen, microphone, and / or the like) coupled to the external entity processing element 308).

[0032] For example, the user interface 316 may be a user application, browser, and / or similar words used herein interchangeably executing on and / or accessible via the external computing entity 102 to interact with and / or cause the display, announcement, and / or the like of information / data to a user. The user input interface 318 can comprise any of a number of input devices or interfaces allowing the external computing entity 102 to receive data including, as examples, a keypad (hard or soft), a touch display, voice / speech interfaces, motion interfaces, and / or any other input device. In embodiments including a keypad, the keypad can include (or cause display of) the conventional numeric (0-9) and related keys (#, *, and / or the like), and other keys used for operating the external computing entity 102 and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface 318 can be used, for example, to activate or deactivate certain functions, such as screen savers, sleep modes, and / or the like.

[0033] The external computing entity 102 may also include one or more external entity non-volatile memories 322 and / or one or more external entity volatile memories 324, which can be embedded within and / or may be removable from the external computing entity 102. As will be understood, the external entity non-volatile memories 322 and / or the external entity volatile memories 324 may be embodied in a number of different ways including, for example, as described herein with reference the non-volatile memories 204 and / or the external volatile memories 206.

[0034] In accordance with one or more examples described herein, the medication storage system 101 (e.g., a medication storage device) may be configured to communicate with one or more external computing entities 102. For example, a network interface (e.g., of the medication storage system 101) may transmit one or more messages to one or more external computing entities 102 based on information received from the one or more processors. The one or more messages may include information indicating that the medication storage system 101 includes one or more objects or medications other than one or more medications prescribed to the user. Accordingly, the one or more messages may facilitate improved safety and healthcare outcomes for the user (e.g., an emergency contact or healthcare professional may be notified and may intervene if a user is not correctly dosing a prescribed medication).III. Overview

[0035] Medications may be stored in various types of containers. For example, a pharmacy may fill a prescription by loading a plurality of pills into a pill bottle for a customer. The pill bottle may include a cylindrical body and a lid that seals or otherwise closes the cylindrical body. In some examples, the pill bottle may not be equipped with any electronic components and may enable an individual to remove any quantity of pills from the pill bottle at any time. However, such pill bottles may present various challenges. For example, it may be difficult for some individuals to remember and adhere to specific dosing schedules. Additionally, or alternatively, some individuals may abuse various medications by either distributing their medications to others illegally or by taking more than a recommend dosage, which may lead to overdose or other adverse health consequences.

[0036] In some examples, a medication storage device may be equipped with a weight measurement system, which may be configured to detect when a user removes a pill from the medication storage device. Accordingly, the medication storage device may track or monitor whether the user is adhering to a dosing schedule based on detecting when pills are removed from the medication storage device. However, utilizing a weight measurement system to monitor whether a user is adhering to a dosing schedule may be associated with various limitations. For example, in some instances, a user may defeat the weight measurement system by removing a pill from the pill bottle and replacing the pill with adifferent pill or an object having a similar weight. In such examples, the weight measurement system may fail to detect that a pill has been removed from the bottle, which may lead to adverse health effects for the user. Additionally, a medication storage device that is only equipped with a weight measurement system may not function properly if the medication storage device is rotated and one or more items in the medication storage device does note exert a force on a weight measurement component. For example, a pill bottle including a load cell at the base of the pill bottle may not be capable of effectively measuring the weight of pills stored in the pill bottle if the pill bottle is rotated on its side or turned upside down.

[0037] In accordance with one or more examples described herein, a medication storage device (e.g., a pill bottle) may be equipped with an imaging system (e.g., an infrared camera) configured to generate one or more images of the one or more items (e.g., medications, objects other than medications) stored in the medication storage device. The medication storage device may also be equipped with one or more processors, which may identify the one or more items or one or more characteristics for the one or more items (e.g., geometric shape) in the medication storage device based on the one or more images. In some examples, the one or more processors may determine whether an object other than a medication prescribed to the user is located inside of the medication storage device. Additionally, or alternatively, the one or more processors may determine one or more types of medications stored in the medication storage device (e.g., the one or more processors may determine one or more identity classifications).

[0038] In some examples, if the medication storage device includes one or more items other than a medication prescribed to the user or a type of medication other than a type of medication prescribed to the user, the medication storage device may alert one or more individuals. For example, the medication storage device (e.g., a network interface of the medication storage device) may transmit a message to a healthcare professional or an emergency contact for the user. The message may indicate that the user is not adhering to a dosing schedule for the medication or that an item other than the medication has been placed in the medication storage device. In some examples, the medication storage device may include one or more audio visual components, which may be triggered if the medication storage device detects that a dosing schedule is not being adhered to.

[0039] Examples of technologically advantageous embodiments of the present disclosure include techniques for alerting a user or other individuals that a dosing schedule for a medication is not being followed or that an item other than a prescribed medication has been placed in a medication storage device, among other examples. Other technical improvements and advantages may be realized by one of ordinary skill in the art.IV. Example System Frameworks

[0040] As indicated, various embodiments of the present disclosure make important technical contributions to the field of healthcare. In particular, systems and methods are disclosed herein that enable medication usage to be accurately monitored. When compared to traditional techniques, monitoring techniques described herein provide increased monitory accuracy, thereby improving patient health outcomes.

[0041] FIG. 4 provides an example medication storage device 400 in accordance with some embodiments discussed herein. The medication storage device 400 may include a base 405, a body 410, and a lid 415. In some examples, the medication storage device 400 may have a cylindrical shape, although other geometries may be utilized. For example, the medication storage device 400 may have a square or rectangular shape. The medication storage device 400 may be utilized to store one or more items, such as one or more medications (e.g., one or more pills). When assembled, the base 405, the body 410, and the lid 415 may form a cavity or an enclosure where the one or more items may be stored.

[0042] The base 405 of the medication storage device 400 may be formed in the shape of a cylinder, or may have any other geometry, such as a square or a rectangle. In some examples, the base 405 may provide mechanical support for the body 410 of the medication storage device 400. For example, the base 405 may enable the medication storage device 400 to balance in an upright position. The base 405 may enable the medication storage device 400 to be placed on a surface (e.g., a flat surface). For example, the base 405 of the medication storage device 400 may be placed on a flat surface, which may cause the contents of the medication storage device 400 to accumulate at the bottom of the medication storage device 400.

[0043] The base 405 may include one or more subcomponents, such as a weight measurement system (e.g., a load cell). The weight measurement system may be configuredto weigh one or more items stored in the medication storage device 400 (e.g., when the medication storage device 400 is in an upright position). The base 405 of the medication storage device 400 may include one or more other components, such as a plate mechanically coupled with the load cell. In some examples, one or more items stored in the medication storage device 400 may exert downward forces on the plate, which may enable the weight of the one or more items to be measured.

[0044] The body 410 of the medication storage device 400 may be formed in the shape of a cylinder, or may have any other geometry, such as a square or a rectangle. The body 410 may be physically coupled with the base 405 such that a seal is formed between the body 410 and the base 405. In some examples, the body 410 may be physically coupled with the lid 415. In the closed position, a seal may be formed between the body 410 and the lid 415.

[0045] The lid of the medication storage device 400 may be formed in the shape of a cylinder, or may have any other geometry, such as a square or a rectangle. The lid 415 may be physically coupled with the body 410 and may enclose an interior portion of the medication storage device 400. In some examples, the lid 415 may have an interior portion (e.g., a cavity), which may house an electronics module. The electronics module may include one or more processors, one or more network interfaces, and one or more imaging systems. In one example, the one or more imaging systems may include an infrared camera, which may be configured to generate one or more images of the interior of the medication storage device 400.

[0046] FIG. 5 provides an example assembly view 500 showing various subcomponents of a medication storage device in accordance with some embodiments discussed herein. The assembly view 500 may illustrate examples of a base 405 and a body 410, which may be examples of the base 405 and the body 410 described with reference to FIG. 4. Additionally, the assembly view 500 may illustrate examples of one or more subcomponents of a base 405. For example, the base 405 may include or may otherwise be physically coupled with a load cell 505 and a plate 510.

[0047] In some examples, the base 405 may include a cylindrical pocket structure 515. The load cell 505 may be placed into the cylindrical pocket structure 515. In some examples, the load cell 505 may include one or more wires (e.g., one or more wires for powering the load cell 505 and one or more wires for an analog output of the load cell 505). Additionally, asidewall of the cylindrical pocket structure 515 may include an opening 520-a that one or more wires of the load cell 505 may pass through.

[0048] The load cell 505 may include a cylindrical component 525, which may be compressed when an object exerts a downward force on the cylindrical component 525. In some examples, compressing the cylindrical component 525 may cause the load cell 505 to output a signal (e.g., an analog signal), which may be indicative of a weight of the object compressing the cylindrical component 525. In some examples, a plate 510 may be physically coupled with the cylindrical component 525. Accordingly, a weight of one or more items placed on the plate 510 may be measured by the load cell 505. In some examples, the plate 510 may include an opening 520-b, which one or more wires of the load cell 505 may pass through.

[0049] The body 410 may be adhered to or otherwise coupled with the base 405. In some examples, the body 410 may include a channel 530. The channel 530 may provide a pathway for the one or more wires of the load cell 505 to pass through. Additionally, the body 410 may include one or more electrical contacts 535 (e.g., pins). In some examples, the one or more wires of the load cell 505 may be coupled with the one or more electrical contacts 535. The one or more electrical contacts 535 may be configured to electrically coupled the one or more wires of the load cell with an electronics module in the lid of the medication storage device. For example, the lid of the medication storage device may also include electrical contacts (not shown), which may connect with the electrical contacts 535 of the body 410 when the lid is closed. The electrical contacts of the lid are described in further detail with reference to FIG. 8.

[0050] FIG. 6 provides an example assembly view 600 showing various subcomponents of a medication storage device in accordance with some embodiments discussed herein. The assembly view 600 may illustrate examples of a base 405, a body 410, and a lid 415, which may be examples of the base 405, the body 410, and the lid 415 described with reference to FIGs. 4 and 5. In some examples, the lid 415 may include one or more subcomponents. For example, the lid 415 may include an electronics module 605 and a hinged plate 610.

[0051] In some examples, the electronics module 605 may include a processor board, a power supply and a camera board. The processor board may include one or more processors and one or more network interface components. The hinged plate 610 may include anopening 615 that a camera lens 620 of the camera board may pass through. In some examples, the electronics module 605 may be adhered to the hinged plate 610 via the camera lens 620 (e.g., the camera lens 620 may be rigidly adhered to the hinged plate 610). Additionally, the lid 415 may be adhered to the hinged plate 610. In some examples, the hinged plate 610 may include a hinge component 625-a, which may be at least partially adhered to a hinge component 625-b of the body 410. Accordingly, the hinged plate 610 may rotate about the hinge component 625-b.

[0052] FIG. 7 provides an example electronics module 605 of a medication storage device in accordance with some embodiments discussed herein. The electronics module 605 may be an example of the electronics module 605 described with reference to FIG. 6. In some examples, the electronics module 605 may include a power supply 705, a processor board 710, and a camera board 715. As described herein, the electronics module 605 may be located within a lid of a medication storage device. In some examples, subcomponents of the electronics module 605 may be physically and / or electronically coupled with one another. For example, the camera board 715 may be physically and / or electronically coupled with the processor board 710, and the power supply 705 may be physically and / or electronically coupled with the processor board 710.

[0053] The camera board 715 may include one or more imaging systems, which may be configured to generate one or more images of an interior portion of the medication storage device. For example, the camera board 715 may include a camera (e.g., an infrared camera), which may be configured to generate one or more photographs of one or more items stored in the medication storage device. In one illustrative example, the camera may have a focal length of 3.6 millimeters (mm) and a field of view of 64 degrees. A lens of the camera may be directed downwards, such that each item in the medication storage device may be photographed. In some examples, one or more images may be communicated between the camera board 715 and the processor board 710 (e.g., via a wired connection or wirelessly).

[0054] The processor board 710 may include one or more processors, which may be configured to determine one or more identity classifications (e.g., item shapes, item types, and / or the like). In some examples, the one or more processors of the processor board 710 may determine the one or more identity classifications based on one or more images (e.g., one or more infrared images) received from the camera board 715. For example, the cameraboard 715 may generate one or more images of an interior portion of the medication storage device. The image may include one or more items (e.g., one or more medications, one or more items, etc.). The one or more processors of the processor board 710 may then receive the one or more images and perform one or more processing operations to determine information associated with the one or more images. For example, the one or more processors may determine one or more identity classifications for items depicted in the one or more images.

[0055] In some examples, an identity classification may indicate a type of medication, or one or more other characteristics associated with one or more medications. Additionally, or alternatively, an identity classification may indicate a type of object. For example, the identity classification may indicate whether an object is a medication or an object other than a medication. In some examples, a geometric shape or any other physical characteristic of an item may be an example of an identity classification. In such examples, the one or more processors may determine or otherwise identify one or more geometric shapes for one or more items located in the mediation storage device. The one or more processors may then determine whether improper use of the medication storage device has occurred based on the one or more identified geometric shapes. For example, the one or more processors may determine that a user has placed on item in the medication storage device other than a medication prescribed to the user based on detecting two or more items with different geometric shapes in the medication storage device or based on detecting one or more items with geometric shapes that do not match a known geometric shape of a medication prescribed to the user.

[0056] In some examples, the one or more processors may determine one or more identity classifications for objects located in the medication storage device and output one or more signals based on the one or more identity classifications. For example, the one or more processors may transmit one or more signals to an audiovisual component of the medication storage device if a medication in the medication storage device does not match a medication prescribed to a user. Additionally, or alternatively, the one or more processors may cause transmission of one or more messages to one or more individuals, which may alert the one or more individuals that a medication in the medication storage device does not match amedication prescribed to a user, or that the user has not adhered to a dosing schedule for a medication.

[0057] The power supply 705 may include one or more components that provide power to the processor board 710 and the camera board 715. For example, the power supply 705 may include one or more batteries. In some examples, the power supply 705 may include one or more rechargeable batteries. Additionally, or alternatively, the power supply 705 may include one more photovoltaic components, which may charge the one or more batteries using solar energy. In some examples, the power supply 705 may include one or more coin or button cell batteries. Additionally, or alternatively, the power supply 705 may include one or more lithium polymer batteries.

[0058] FIG. 8 provides an example medication storage device 800 in accordance with some embodiments discussed herein. The medication storage device 800 may include a base 405, a body 410, and a lid 415, which may be examples of the base 405, the body 410, and the lid 415 described with reference to FIGs. 4-7. The medication storage device 800 may also include one or more electrical contacts 535, and a channel 530, which may be examples of the electrical contacts 535 and the channel 530 described with reference to FIG. 5. As shown, the expanded view 805 may illustrate a portion of the medication storage device 800. For example, the expanded view 805 may illustrate a portion of the lid 415 and a portion of the body 410.

[0059] As described herein, the medication storage device may include one or more electrical contacts 535. For example, the body 410 may include the electrical contact 535-a, the electrical contact 535-b, the electrical contact 535-c, and the electrical contact 535-d. The lid 415 may include the electrical contact 535-e, the electrical contact 535-f, the electrical contact 535-g, and the electrical contact 535-h. Additionally, or alternatively, the base 405 may include one or more electrical contacts 535 (not shown). In some examples, one or more electrical contacts 535 may be coupled with one or more other electrical contacts 535 when the lid 415 is in a closed position. For example, when the lid 415 is closed, the electrical contact 535-a may be electrically coupled with the electrical contact 535-e, the electrical contact 535-b may be electrically coupled with the electrical contact 535-f, the electrical contact 535-c may be electrically coupled with the electrical contact535-g, and the electrical contact 535-d may be electrically coupled with the electrical contact 535-h.

[0060] In some examples, an electronics module of the medication storage device (e.g., located in the lid 415) may be electrically coupled with one or more other components of the medication storage device via one or more electrical contacts 535. For example, the electronics module may be electrically coupled with a load cell located in the base 405 via one or more electrical contacts 535. In such examples, a wire of a load cell (e.g., a first power wire) may be routed from the load cell to the electrical contact 535-a. The electrical contact 535-a may then be coupled with the electrical contact 535-e (e.g., when the lid 415 is closed) and a wire may couple the electrical contact 535-e with the electronics module (e.g., with a power supply of the electronics module). Additionally, one or more other wires of the load cell may be routed from the load cell to one or more other electrical contacts 535 and may be coupled with the electronics module in a similar fashion.

[0061] FIG. 9 provides an example medication storage device 900 in accordance with some embodiments discussed herein. The medication storage device 900 may include a base 405, a body 410, and a lid 415, which may be examples of the base 405, the body 410, and the lid 415 described with reference to FIGs. 4-8. The medication storage device 900 may also include a display 905, which may be used to provide information to one or more individuals, such as a user, a healthcare professional, or a caretaker for the user. In some examples, the display 905 may be installed at a top portion 910 of the lid 415.

[0062] The display 905 may be configured to provide one or more types of information. For example, the display 905 may provide any one or more of time information (e.g., a current time), power information (e.g., for the power supply), a day of the week, health information for a user, alert information, or information associated with one or more items located inside of the medication storage device 900. In one example, the health information for the user may include a daily step count for the user, a daily quantity of calories burned by the user, and a distance traveled by the user. In some examples, a network interface of the medication storage device 900 may receive the health information from a user device (e.g., a smartwatch, a smartphone).

[0063] In some examples, the information associated with the one or more items located inside of the medication storage device 900 may include an indication of a quantity or typeof pills located inside of the medication storage device 900. Additionally, or alternatively, the display 905 may provide information indicative of a remaining quantity of pills inside of the medication storage device 900 (e.g., relative to an initial quantity of pills located inside of the medication storage device 900). In some examples, the display 905 may provide one or more messages or alerts. For example, if an item or medication other than a medication prescribed to a user is identified inside of the medication storage device 900, the display 905 may provide an alert or a notification indicating that the item or medication has been identified. In some examples, the display 905 may display dosing information, such as a dosing schedule. Additionally, or alternatively, the display 905 may provide one or more messages or alerts indicating that a medication should be taken (e.g., the alert may be provided at a specific time or indicate a specific time when the medication should be taken).

[0064] According to some embodiments, the medication storage device may be configured to be locked between medication dosage times to help avoid overdoses. The locking mechanism can be an electronically operated lock that latches the lid 415 to the body 410. The locked / unlocked status can be provided for display on display 905. The lock may be enabled for various circumstances, such as based on a type of medication stored within the container, a property of a user of the medication (e.g., addiction or propensity thereof). The lock of an example embodiment may become disabled permitting access to the storage device in response to the quantity of a medication falling below a threshold value, such as a quantity below which overdose is not considerably likely, or if the medication type of concern has been completely used. For example, if a narcotic is stored within the medication storage container, the medication storage container may remain locked between doses. If the narcotic is no longer stored in the storage device or if the last narcotic has been used, the lock may be disabled providing access to the storage container at all times as the controlled substance is no longer present.

[0065] FIG. 10 provides an example audio visual system 1000 in accordance with some embodiments discussed herein. The audio visual system 1000 may include a structural component 1005, which may support one or more audio visual components, such as one or more visual component 1010 (e.g., one or more light-emitting diodes (LEDs)), one or more auditory components 1015 (e.g., one or more speakers), and one or more motion components 1020 (e.g., one or more vibrator motors). For example, the one or more visualcomponents 1010, the one or more auditory components 1015, and the one or more motion components 1020 may be adhered to or otherwise physically coupled with the structural component 1005. In some embodiments, the structural component 1005 may be an example of or may be coupled with the base 405, the body 410, or the lid 415, as described with reference to FIGs. 4-9.

[0066] The audio visual system 1000 may include any quantity of visual components 1010. For example, the audio visual system 1000 may include the visual component 1010-a, the visual component 1010-b, the visual component 1010-c, and the visual component 1010-d. In some examples, the audio visual system 1000 may include one or more additional visual components 1010 (not shown), which may be located, for example, on a back side of the structural component 1005. In some examples, the visual components 1010 may be coupled with each other by one or more wires. Additionally, the visual components 1010 may be coupled with one or more components of the electronics module by one or more wires. For example, the visual components 1010 may be coupled with the processor board. As described herein, one or more of the visual components 1010 may be configured to illuminate (e.g., in a steady or flashing pattern) in response to one or more events. The one or more events may include a user forgetting to take a medication or removing an incorrect quantity of pills from the medication storage device relative to a dosing schedule. In some examples, the one or more visual components 1010 may illuminate or flash if one or more items other than a medication prescribed to a user is placed into the medication storage device.

[0067] The audio visual system 1000 may include any quantity of auditory components 1015. In some examples, the one or more auditory components 1015 may be coupled with one or more components of the electronics module by one or more wires. For example, the one or more auditory components 1015 may be coupled with the processor board by one or more wires. As described herein, the one or more auditory components 1015 may be configured to emit one or more sounds in response to one or more events. For example, the one or more auditory components 1015 may emit one or more alarm sounds or audio messages. The one or more events may include a user forgetting to take a medication or removing an incorrect quantity of pills from the medication storage device relative to a dosing schedule. In some examples, the one or more auditory components 1015 may emitsounds if one or more items other than a medication prescribed to a user is placed into the medication storage device.

[0068] The audio visual system 1000 may include any quantity of motion components 1020. In some examples, the one or more motion components 1020 may be coupled with one or more components of the electronics module by one or more wires. For example, the one or more motion components 1020 may be coupled with the processor board by one or more wires. As described herein, the one or more motion components 1020 may be configured to vibrate in response to one or more events. The one or more events may include a user forgetting to take a medication or removing an incorrect quantity of pills from the medication storage device relative to a dosing schedule. In some examples, the one or more motion components 1020 may vibrate if one or more items other than a medication prescribed to a user is placed into the medication storage device.

[0069] FIG. 11 provides an example flowchart 1100 in accordance with some embodiments described herein. The flowchart 1100 may include one or more examples of operations performed by a medication storage device or one or more subcomponents of a medication storage device, as described with reference to FIGs. 1-10. In accordance with examples described herein, any of the described operations may be performed multiple times or independently of other operations described herein.

[0070] As shown in block 1105, the medication storage device may include means, such as the camera board, or the like, for generating one or more images of one or more items stored in the medication storage device. In some examples, the medication storage device may generate the one or more images based at least in part on the medication storage device being filled with the one or more items.

[0071] As shown in block 1110, the medication storage device may include means, such as the processor board, or the like, for determining one or more identity classifications for the one or more items. In some examples, the medication storage device may determine the one or more identity classifications based at least in part on the one or more images. In some examples, an identity classification of the one or more identity classifications may indicate a type of medication.

[0072] As shown in block 1115, the medication storage device may include means, such as the processor board, or the like, for communicating information to one or more individuals. In some examples, the information may be communicated based at least in part on the one or more identity classifications. In some examples, the one or more individuals may include one or more of: (i) a healthcare professional or (ii) an emergency contact or caretaker for a user.

[0073] The flowchart 1100 depicts methods according to an example embodiment. It will be understood that each block and combination of blocks may be implemented by various means, such as hardware, firmware, processor, circuitry, and / or other communication devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by memory of a computing entity as described herein. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.

[0074] Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.V. Conclusion

[0075] Many modifications and other embodiments will come to mind to one skilled in the art to which this disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS1. A medication storage device comprising: a body defining a cavity; a lid configured to close the cavity; an image sensor configured to capture one or more images within the cavity; one or more processors configured to determine, based on the one or more images, one or more identity classifications for one or more items stored in the cavity; and a network interface component configured to communicate information based at least in part on the one or more identity classifications.

2. The medication storage device of claim 1, wherein the image sensor is configured to capture an image of contents of the cavity in response to the lid closing the cavity.

3. The medication storage device of claim 1, wherein the image sensor is disposed within the lid.

4. The medication storage device of claim 1, further comprising a load cell disposed at a base of the cavity, wherein the load cell is configured to determine a weight of the one or more items stored in the cavity.

5. The medication storage device of claim 4, wherein the image sensor is configured to capture the one or more images within the cavity based at least in part on a signal from the load cell.

6. The medication storage device of claim 5, wherein the image sensor is configured to capture the one or more images within the cavity based at least on a comparison of a first weight measurement of the one or more items stored in the cavity and a second weight measurement of the one or more items stored in the cavity.

7. The medication storage device of claim 6, wherein the comparison reflects a removal of at least one of the one or more items stored in the cavity.

8. The medication storage device of claim 4, wherein the load cell is configured to determine the weight of the one or more items stored in the cavity in response to the lid closing the cavity.

9. The medication storage device of claim 1 further comprising a display positioned on the lid, wherein the display depicts information associated with the one or more items stored in the cavity.

10. The medication storage device of claim 9, wherein the information associated with the one or more items stored in the cavity comprises the one or more identity classifications for the one or more items stored in the cavity.

11. The medication storage device of claim 10, wherein the information associated with the one or more items stored in the cavity comprises a quantity for each of the one or more identity classifications for the one or more items stored in the cavity.

12. The medication storage device of claim 1, further comprising at least one rechargeable power supply for powering the image sensor, the one or more processors, and the network interface component.

13. The medication storage device of claim 1, further comprising a lock to secure the lid to the body preventing access to the cavity, wherein the lock is configured to enable or disable access to the one or more items stored in the medication storage device based at least in part on the one or more identity classifications.

14. The medication storage device of claim 13, wherein the lock is configured to enable access to the one or more items stored in the medication storage device in response to a quantity of the one or more items stored in the medication storage device falling below a predetermined threshold.

15. The medication storage device of claim 13, wherein the lock is configured to enable access to the one or more items stored in the medication storage device in response to the one or more identity classifications not including a controlled substance.

Images