Patients may be prescribed multiple medications to treat various conditions. Additionally, patients may regularly take non-prescription drugs (e.g., aspirin) or supplements. Accordingly, some patients may need to manage a regimen involving multiple medications.
Current medication management solutions such as pill sorters still require the patients or caregivers to manually sort and track medications. Compliance with a complicated medication regimen may be difficult for patients. Further, care providers may not know whether a patient is complying with a medication regimen, which may affect the ability of the care provider to assess the effectiveness of the medication regimen.
In view of the foregoing, as well as other factors, there remains a need for improvements over current medication dispensing procedures.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The disclosure provides for a medication dispensing device. The medication dispensing device may include a plurality of trays, each tray including a load cell configured to measure a mass of a medication (e.g., by weight) contained in the respective tray. Each tray is placeable in a medication accessible position and a medication inaccessible position. The medication dispensing device may include a user interface configured to provide instructions with regard to access for each medication. A processor may be configured to provide instructions to selectively place each tray in the medication accessible position, and to determine, based on any change in the mass/weight of the medication placed in the medication accessible position, whether any amount of the medication is removed from the tray. The disclosure also provides methods for loading medication into the medication dispensing device and dispensing medication from the medication dispensing device.
In an aspect, the disclosure provides a medication dispensing device. The medication dispensing device includes a plurality of trays, each tray including mass/weight measurement features, such as a load cell configured to measure the mass/weight of a medication contained in the respective tray, each tray being placeable in a medication accessible position (e.g., the tray being open to access) and a medication inaccessible position (e.g., the tray being closed to access). The medication dispensing device further may include a user interface configured to provide instructions with regard to access for each medication. The medication dispensing device may also include a processor configured to provide instructions to selectively place each tray in the medication accessible position and determine, based on any change in the mass/weight of the medication placed in the medication accessible position, whether any amount of the medication is removed from the tray.
In another aspect, the disclosure provides a medication container. The medication container may include a bowl portion having an outer edge in a first plane. In one example implementation, the outer edge may include a first convex arc segment, a second concave arc segment concentric with the first convex arc segment, and two straight segments connecting respective ends of the first convex arc segment and the second concave arc segment. The length of the first convex arc segment may be greater than a length of the second concave arc segment. A bottom surface of the bowl may be sloped such that the bowl is shallower near the first convex segment than near the second concave arc segment. The medication container may further include a movable lid forming a press fit with the outer edge of the bowl.
In another aspect, the disclosure provides a method of dispensing medication. The method may include receiving medication information for medication to be dispensed from a dispensing device, the medication information including a prescribed medication mass/weight. The method may further include prompting a user to insert the medication into a tray. The method may also include determining a mass/weight of the medication to determine an actual medication mass/weight. The method may additionally include determining whether the actual medication mass/weight matches the prescribed medication mass/weight.
Additional advantages and novel features of these aspects will be set forth in part in the description that follows, and in part will become more apparent to those skilled in the art upon examination of the following or upon learning by practice thereof.
The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate example features and not to limit the disclosed aspects, wherein like designations denote like elements, and in which:
Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific example details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspects may be practiced without these specific details.
The peripheral device 24 may be any suitable device that may obtain medical or biometric data from a patient. For example, the peripheral device 24 may be a glucometer, cardiac monitor, thermometer, respiratory monitor, sleep monitor, pulse oximeter, body scale, inhaler, nebulizer, fitness tracker, blood pressure cuff, syringe, stethoscope, breathalyzer, mobile phone sensor, etc. The peripheral device 24 may provide measurements or biometric data to the medication dispensing device 20, for example, which may in turn transmit the measurements or biometric data to other devices via a network 40.
The medication dispensing device 20 may be communicatively coupled to a network 40. The network 40 may include any network that allows communication between the various entities of the system 10. In an aspect, the network 40 may be a communications network and may include or be connected with other networks. For example, the medication dispensing device 20 may include a modem and be coupled to the network 40 via a wired or wireless connection. The network 40 may include one or more computer servers 42. The computer servers 42 may include information for managing the medication dispensing device 20 and/or a peripheral device 24. In an aspect, for example, the computer servers 42 may include device servers for controlling one or more medication dispensing devices 20, notification servers for providing messages to the patient 30, caregivers 70, or others, such as the remote care team 80. The servers 42 may also receive data generated by medication dispensing device 20 and/or peripheral device 24. The computer servers 42 may also include one or more web servers running web applications that may allow a pharmacy 50, payer 60, caregivers 70, or others, such as the remote care team 80 to interact with the system 10 in defined roles. The computer servers 42 may also include storage servers for storing device information, medication information, patient information, billing information, etc.
In one aspect of the disclosure, various data is, for example, input and/or accessed by the patient 30, pharmacy 50, payer 60, caregivers 70, or other users via terminals such as personal computers (PCs), minicomputers, mainframe computers, microcomputers, telephonic devices, or wireless devices, personal digital assistants (“PDAs”) or a hand-held wireless devices (e.g., wireless telephones). The terminals may be coupled to a computer server 42, such as a PC, minicomputer, mainframe computer, microcomputer, or other device having a processor and a repository for data and/or connection to a repository for data, via, for example, the network 40, such as the Internet or an intranet, and/or a wireless network. The couplings 44 include, for example, wired, wireless, or fiber optic links.
The medication dispensing device 20 may dispense medications provided by a pharmacy 50. In an aspect, a medication may include a solid oral medication (e.g., pills, caplets, capsules, gel caps, tablets, or tabs). In an aspect, the medication may include a prescription medication. The medication may also include over the counter medicine, vitamins, supplements, placebos, or other substances that may be dispensed to the patient 30. The pharmacy 50 may provide medications to the patient for storage in the medication dispensing device 20. The pharmacy 50 may receive prescription information from a doctor via written or electronic script, for example. The pharmacy 50 may fill the prescription and provide the medications to the patient 30 or caregiver 70 in a medication container, for example. The pharmacy 50 may submit medication information to the network 40 indicating the medication type, medication name, condition, total mass/weight, container mass/weight, mass/weight per unit of medication, and/or other medication properties for each medication.
In an aspect, the pharmacy 50 may provide a “quantity sufficient inventory.” A quantity sufficient inventory may refer to an amount of medication to bring a patient's supply of the medication to a prescribed amount for a time period (e.g., an appropriate amount for proper ingestion in a 30 day period). The pharmacy 50 may receive current medication amounts from the medication dispensing device 20 via the network 40 to determine the quantity sufficient inventory. Among other things, providing a quantity sufficient inventory may reduce waste from missed doses and reduce medication costs.
The payer 60 may receive billing information from the network 40 and provide payment. For example, a server 42 may be a billing server that receives bills from the pharmacy 50 and provides the bills to the payer 60.
The remote care team 80 may receive information from the network 40 regarding a patient 30 and operations of the medication dispensing device 20. The remote care team, for example, may monitor for health changes and change prescription schedules.
Further details of the system 10 and its operation are provided in application Ser. No. 15/216,448, which is hereby incorporated by reference herein in its entirety for all purposes.
In an aspect, the door 220 may include a user interface 222, which may correspond to the user interface 22 (
The main body 210 may include multiple trays 230a-230f for storing and dispensing medication. The trays 230a-230f may be arranged vertically and/or horizontally. For example, the trays 230a-230f may be arranged along a vertical axis 232. In an aspect, the trays 230a-230f may be arranged in various manners, for example, with two or more trays in the same horizontal plane or “floor.” The trays 230a-230f may, for example, be selectively placed in a medication accessible position, in which a patient may remove or otherwise access medication contained in a tray. For example, as illustrated in
The trays 230a-230f (as illustrated in
The main body 210 may further include a power supply 280, a power switch 282, and a service port 284. The power supply 280 may accept a DC voltage and charge a battery. The power switch 282 may have an on position, an off position, and a low power position. The low power position may be selected for manual access. In an aspect, a service port 284 (e.g., USB) may allow the medication dispensing device 200 to be connected (e.g., via USB) with a diagnostic device.
In an aspect, the scanners 240 and mirrors 242 may be integrated into a scanning unit. The scanning unit may be mounted, for example, on lead screws or threaded rods to allow the scanning unit to move vertically. The lead screws may be driven by a motor via a timing belt such that the scanning unit moves along all of the lead screws uniformly. The motor may move the scanning unit to an approximate position of a tray 230 and the scanners 240 may scan multiple times while moving. In an aspect, the scanning unit may traverse the height of the medication dispensing device 200 in approximately 6 seconds. Accordingly, a single scanning unit may be used to scan different trays 230a-230f (
A tray 230 may include one or more medication containers 236. A medication container may also be referred to as a pod or RxPod. In an aspect, a medication container 236 may be removable from the tray 230. For example, the medication container 236 may rest in a container port of the tray 230. The indicia 234 may, for example, be located on a tab that overhangs the tray 230 or may be readable by another feature, such as an opening in a portion of the tray 230. A second indicia may be located on the tray 230 behind the indicia 234 and be readable only when no medication container 236 is in the container port. The second indicia may indicate that the container port is empty. In another aspect, the medication container 236 may be integrally formed with the tray 230, or medication may be placed in a container port. A support feature 238, such as a vertical rod, may be located, for example, at or parallel to the vertical axis 232 (
In an aspect, the driving mechanism 244 may include a manual access feature that allows access when the medication dispensing device 200 does not have external power. For example, the manual access feature may include a cam shaft that may be rotated to decouple gears of the driving mechanism 244. When the cam shaft is rotated to a manual access position, the separation of the gears may allow each of the trays 230 to be manually rotated to a medication accessible position. In an aspect, the manual access feature may also activate the power switch 282 to indicate whether the manual access feature was activated. The power switch 282 may be connected to the cam shaft and switch to lower power mode when the cam shaft is rotated. The switch 282 may place the medication dispensing device 200 in a low power mode to conserve battery power. The switch 282 may also initiate a calibration sequence upon repowering of the medication dispensing device 200 to detect the position of each of the trays 230 and place the trays 230 in the medication inaccessible position. The calibration sequence may also include displaying user instructions on the user interface 222 and/or determining current amounts of medication.
In an aspect, a press switch may be used to detect the rotational position of a tray 230. For example, a tray 230 may include notches 264 at various positions. The press switch may generate a signal when aligned with a notch 264, allowing the processor or controller to detect the rotational position of the tray 230. The processor or controller may control the driving mechanism 244 based on the press switch to align the trays 230 in a medication inaccessible position. The processor or controller may control the driving mechanism 244 based on the press switch to stop rotation of a tray 230 upon reaching a medication accessible position.
The support bracket 270 may position the structural support portion 260 on the support feature 238. The support bracket 270 may provide load bearing strength for supporting the support portion 260. For example, the support bracket 270 may be formed from a stronger material (e.g., glass filed nylon) than the material (e.g., plastic) of the support portion 260. The load cell 252 may also be mounted to the support bracket 270. The support bracket 270 may include circuitry and wiring for the load cell 252. For example, the support bracket 270 may include an amplifier for amplifying the signal from the load cell 252 for transmission to the processor. The support bracket 270 may include one or more openings for wires or cables to pass from the load cell 252 into an area adjacent the support feature 238. The wires may pass vertically adjacent to the support feature 238 between vertically adjacent support brackets 270 to the top or bottom of the medication dispensing device 200 (
The bowl 330 may further include a handle 350 extending from the top edge 340 along the convex arc segment 242. For example, the handle 350 may be centered on the convex arc segment 242. The handle 350 may include a vertical surface 352 that may be generally parallel to the convex arc segment 342. The vertical surface 352 may bear an indicia 234. The handle 350 may also include a support feature 354 to strengthen the handle 350. For example, the support feature 354 may be corrugated. The handle 350 may also include a front locking feature 356. For example the front locking feature 356 may be a slot for receiving a tab. The bowl 330 may include one or more rear locking features 358 located in the vertical wall 338 between the bottom surface 332 and the concave arc segment 344 of the top outer edge 340. For example, the rear locking features 358 may be a pair of slots. Each slot may be smaller than a unit of solid oral medication (e.g., a pill).
The lid 320 may be removably attached to the bowl 330. The lid 320 may generally have a shape matching the top edge 340. The lid 320 may have lip 325 matching at least a portion of an internal or external surface of the top edge 340 of the bowl 330. The lip 325 may prevent medication from being removed while the lid 320 is attached to the bowl 330. In an aspect, the lip 325 may form a press fit or interference fit with the bowl 330.
A tab 322 may extend from a convex arc portion of the lid 320 corresponding to the handle 350. The tab 322 may extend further than the handle 350 and/or be narrower than the handle 350. The handle 350 may include a textured surface for gripping while manipulating the lid 320. The tab 322 may also include a vertical locking tab 324 that engages the front locking feature 356. For example, the vertical locking tab 324 may include a flexible portion having a shoulder that engages the front locking feature 356. In an aspect, the flexible portion may be hinged at a bottom of the vertical locking tab 324 and extend to a handle portion above the shoulder. The handle portion may be textured to provide a place to grip. The lid 320 may include one or more rear tabs 326 that engage the rear locking features 358. For example, the rear tabs 326 may be hooks that curve downwardly from the lid 320.
In an aspect, the lid 320 may be positioned on the bowl 330 by inserting the rear tabs 326 into the rear locking features 358 and pivoting the lid 320 down onto the top edge 340. The vertical locking tab 324 may flex as it is inserted through the front locking feature 356 until the shoulder moves past a ridge of the vertical surface 352. The vertical locking tab 324 may then releasably engage the ridge of the vertical surface 352. The lid may be removed by pressing on the handle portion of the vertical locking tab 324 and lifting tab 322. The handle portion may be pinched toward a center stacking feature 328. In an aspect, the lid 320 may be removed from the bowl 330 while the medication container 300 is within a container port 251 (
As illustrated in
The lid 370 may be removably attached to the bowl 380. The lid 370 may have an internal surface matching the top outer edge 340 of the bowl 380, such that the lid 370 may form a press fit or interference fit with the bowl 380. One or more locking features 382 may secure the lid 370 to the bowl 380. The locking features 382 may optionally form a child-resistant closure of the medication container 360. A tab 372 may be also be located on the lid 370, such as extending downwardly from a convex segment of the lid 370. The tab 372 may be concentric with the convex arc segment 342 and include an indicia 376, for example, which may enable more accurate scanning as the medication container 300 rotates along with a tray 230.
The seal 390 may seal the medication container 360 for transport. The seal 390 may be removable by a user (e.g., a caregiver or patient) before or after insertion into a medication dispensing device (e.g., medication dispensing device 200). In an aspect, the seal 390 may comprise a foil that is adhered to the lid 370. The seal 390 may include a main body portion 392 that is sized and shaped to match the lid 370. The main body portion 392 of the seal 390 may also include a label including indicia 396, which may be similar to the indicia 234. The seal 390 may also include a handle portion 394 that may extend beyond an edge of the lid 370. The handle portion 394 may thereby allow a user (e.g., a patient) to easily grasp the seal 390 for removal, for example.
The processor 410 may be a general purpose computer processor capable of executing instructions. For example, the processor 410 may execute software instructions stored in memory 415. The software instructions, when executed by the processor 410, may cause the processor 410 to control the other components of the control system 400 via the bus 430, as described herein. The memory 415 may store instructions executable by the processor 410. In an aspect, the memory 415 may be considered a computer-readable medium. The memory 415 may also store information or data that is manipulated by the processor 410. For example, the memory 415 may store patient information, medication information, etc.
The user interface 420 may correspond to the user interface 22 or user interface 222. In an aspect, the user interface 420 may also correspond to a mobile device of the user (e.g., patient mobile device 32 (
The network interface 425 may provide an interface between the control system 400 and the network 40. In an aspect, for example, the network interface 425 may include a modem for communication via a wired or wireless connection to the network 40.
The bus 430 may connect the other components of the control system 400. The bus 430 may be controlled by the processor 410, for example, to transfer instructions (e.g., movement instructions) and/or data among components.
The scanner 435 may correspond to the scanner 240 (
The controller 440 may control one or more motor/actuators 450 and/or load cells 460. For example, the controller 440 may receive instructions from the processor 410 to place a tray in a medication accessible position or a medication inaccessible position (e.g., a position in which a user may access medication within the tray, or a position where a user may not so access medication). The controller 440 may identify/enable a motor/actuator indicated for use by the instructions and control the identified/enabled motor/actuator so as to cause movement of the appropriate tray. For example, the controller 440 may determine a direction of turning for a motor and energize the motor until a selected tray moved by the motor reaches a desired position. As another example, the controller 440 may energize an actuator (e.g., solenoid) to lock or unlock a door or move a tray. Further, the controller 440 may enable operation of and/or receive information from the load cells 460. For example, the controller 440 may power on a load cell 460 to obtain a measurement of mass/weight for a tray. The controller 440 may also provide a received measurement from a designated load cell to the processor 410, the memory, or another device/system.
The peripheral device 470 may correspond to the peripheral device 24 (
Aspects of the present invention may be implemented using hardware, software, or a combination thereof and may be implemented in one or more computer systems or other processing systems. For example, the user interface 222 (
Computer system 500 includes one or more processors, such as processor 504. The processor 504 is coupled to a communication infrastructure 506 (e.g., a communications bus, cross-over bar, or network). Various software aspects are described in terms of this example computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement aspects hereof using other computer systems and/or architectures.
Computer system 500 may include a display interface 502 that forwards graphics, text, and other data from the communication infrastructure 506 (or from a frame buffer not shown) for display on a display unit 530. Computer system 500 may include a main memory 508, preferably random access memory (RAM), and may also include a secondary memory 510. The secondary memory 510 may include, for example, a hard disk drive 512 and/or a removable storage drive 514, e.g., an optical disk drive. The removable storage drive 514 may read from and/or write to a removable storage unit 518 in a well-known manner. As will be appreciated, the removable storage unit 518 may include a computer readable storage medium having stored therein computer software and/or data.
Alternative aspects of the present invention may include secondary memory 510 and may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 500. Such devices may include, for example, a removable storage unit 522 and an interface 520. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units 522 and interfaces 520, which allow software and data to be transferred from the removable storage unit 522 to computer system 500.
Computer system 500 may also include a communications interface 524. Communications interface 524 may allow software and data to be transferred among computer system 500 and external devices. Examples of the noted communications interface 524 may may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface 524 may be in the form of signals 528, which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface 524. These signals 528 may be provided to communications interface 524 via a communications path (e.g., channel) 526. This path 526 may carry signals 528 and may be implemented using wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link and/or other communications channels. As used herein, the terms “computer program medium” and “computer usable medium” refer generally to media such as a removable storage drive 580, a hard disk installed in hard disk drive 570, and/or signals 528. These computer program products may provide software to the computer system 500. Aspects of the present invention are directed to such computer program products.
Computer programs (also referred to as computer control logic) may be stored in main memory 508 and/or secondary memory 510. Computer programs may also be received via communications interface 524. Such computer programs, when executed, may enable the computer system 500 to perform the features in accordance with aspects of the present invention, as discussed herein. In particular, the computer programs, when executed, may enable the processor 504 to perform the features in accordance with aspects of the present invention. Accordingly, such computer programs may represent controllers of the computer system 500.
Where aspects of the present invention may be implemented using software, the software may be stored in a computer program product and loaded into computer system 500 using removable storage drive 514, hard disk drive 512, or interface 520. The control logic (software), when executed by the processor 504, may cause the processor 504 to perform the functions described herein. In another aspect of the present invention, the system may be implemented primarily in hardware using, for example, hardware components, such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).
In yet another variation, aspects of the present disclosure may be implemented using a combination of both hardware and software.
In block 610, the method 600 may include determining a mass/weight of an empty medication container. The pharmacy 50 may, for example, weigh an empty medication container. The pharmacy 50 may also determine the mass/weight based on an indication from the manufacturer. A patient 30 or caregiver 70 may similarly determine the mass/weight of an empty medication container.
At block 615, the pharmacy 50 may determine a prescribed amount of medication. In an aspect, the prescribed amount of medication may be an amount indicated on a prescription from a physician. In another aspect, the prescribed amount of medication may be a “quantity sufficient inventory” for a designated time period (e.g. 1 month). For a patient, the prescribed amount of medication may be indicated within prescription information provided by a pharmacist. As another example, a non-prescription medication may have an amount of medication indicated by a physician, nutritionist, or other health professional (e.g., one pill per day).
In block 620, the method 600 may include filling the medication container with the prescribed amount of medication. For example, the pharmacy 50 may count a number of units of medication or determine a mass/weight/volume of the medication when filling the medication container. A patient or caregiver may similarly count a number of units of medication.
In block 625, the method 600 may include determining a mass/weight of the prescribed amount of medication within the medication container. For example, the pharmacy 50 may subtract the mass/weight of the empty container from a mass/weight of the filled container. Similarly, a patient 30 or caregiver 70 may determine the mass/weight of the medication within the medication container. In an aspect, the medication dispensing device may be configured to provide instructions and/or automatically determine a mass/weight of medication within the medication container.
In block 630, the method 600 may include associating medication information with indicia of the medication information. The medication information may include prescription information, a mass/weight of the medication, a number of units of medication, a per unit mass/weight of the medication, the identifier of the indicia, and/or patient information. In an aspect, the per unit mass/weight of the medication may be supplied by a manufacturer and entered by the pharmacy 50. In another aspect, the pharmacy 50 may determine the per unit mass/weight of the medication based on the prescribed amount of medication and the mass/weight of the prescribed amount of medication. In an aspect, for example, a pharmacy label including an indicia may be applied to the medication container. In another aspect, the medication container may include a predetermined indicia and the pharmacy 50 may scan the indicia and associate an identifier of the indicia with both the medication container and the medication information.
In block 635, the method 600 may include uploading medication information to the network 40. In an aspect, for example, the pharmacy 50 may upload medication information to the network 40. The medication information may include prescription information, the mass/weight of the medication, the number of units of medication, the per unit mass/weight of the medication, the identifier of the indicia, and/or patient information. The network 40 may forward the medication information to the medication dispensing device 20. For a patient 30 or caregiver 70 the medication dispensing device 20 may upload the medication information to the network 40.
In block 640, the method 600 may optionally include sealing the medication container. For example, the pharmacy 50 may close the medication container and engage any locking features. The pharmacy 50 may provide the sealed medication container to the patient 30 or caregiver 70. In an aspect, a patient 30 or caregiver 70 may place the medication container into the medication dispensing device 20 without sealing the container.
In block 710, the method 700 may include receiving medication information for medication to be dispensed from the medication dispensing device 20 (
In block 715, the method 700 may include prompting for insertion of medication into a tray 230 (
In block 720, the method 700 may include placing a tray in a medication accessible position. In an aspect, for example, the processor 410 may instruct controller 440 (
Referring back to
In block 730, the method 700 may include scanning an indicia. In an aspect, for example, the scanner 240 (
In block 735, the method 700 may include determining whether the scanned indicia matches received medication information. In an aspect, for example, the processor 410 (
In block 740, the method 700 may include determining a mass or weight of the medication. In an aspect, for example the processor 410 (
In block 745, the method 700 may include determining whether the mass/weight of the loaded medication matches the medication information. In an aspect, for example, the processor 410 (
In block 750, the method 700 may include detecting, reporting, and/or correcting errors. In an aspect, for example, the processor 410 may determine that an error has occurred because the medication information does not match the inserted medication. The processor 410 (
In block 810, the method 800 may include alerting a patient to take an amount of medication according to the medication information. In an aspect, for example, the processor 410 (
In block 815, the method 800 may include placing the tray in a medication accessible position. The block 815 may be similar to the block 720. In block 820, the method 800 may include determining that the tray is in the medication inaccessible condition. The block 820 may be similar to the block 725.
In block 825, the method 800 may include determining a mass/weight of the medication removed from the tray. In an aspect, for example, the processor 410 (
In block 830, the method 800 may include determining whether the mass/weight of medication removed from the tray matches the amount of medication. In an aspect, for example, the processor 410 may determine whether the mass/weight of medication removed from the tray matches the amount of medication. For example, the processor 410 (
In block 835, the method 800 may include detecting, reporting, and/or correcting possible errors. In an aspect, for example, the processor 410 (
In block 840, the method 800 may include determining whether the tray is empty. In an aspect, for example, the processor 410 (
While the foregoing disclosure discusses example aspects and/or features, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or features as defined by the appended claims. Furthermore, although elements of the described aspects and/or features may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or feature, unless stated otherwise.
This application is a Divisional of U.S. patent application Ser. No. 16/699,651, filed on Nov. 30, 2019, which claims priority to U.S. patent application Ser. No. 15/216,385, filed on Jul. 21, 2016, titled, “MEDICATION DISPENSING DEVICE AND METHODS,” now U.S. Pat. No. 10,545,048 issued Jan. 28, 2020, which claims priority to U.S. Provisional Patent Application No. 62/196,131, filed on Jul. 23, 2015, titled, “MEDICATION DISPENSING DEVICE AND METHODS”, and U.S. Provisional Patent Application No. 62/196,165, filed on Jul. 23, 2015, titled “MEDICATION DISPENSING DEVICE AND METHODS”. The entire disclosure contents of each of these applications are herewith incorporated by reference into the present application.
Number | Name | Date | Kind |
---|---|---|---|
D273093 | Lunden | Mar 1984 | S |
D274040 | Ridgley | May 1984 | S |
D279864 | Ridgley | Jul 1985 | S |
4899839 | Dessertine | Feb 1990 | A |
5011018 | Keffeler | Apr 1991 | A |
D356904 | Wolff | Apr 1995 | S |
5735406 | Keffeler | Apr 1998 | A |
5752621 | Passamante | May 1998 | A |
5774865 | Glynn | Jun 1998 | A |
5852590 | de la Huerga | Dec 1998 | A |
D408625 | Barker | Apr 1999 | S |
6042858 | Kairys | Mar 2000 | A |
6150942 | O'Brien | Nov 2000 | A |
6259654 | de la Huerga | Jul 2001 | B1 |
6294999 | Yarin et al. | Sep 2001 | B1 |
6380858 | Yarin et al. | Apr 2002 | B1 |
D459987 | Christianson | Jul 2002 | S |
6529446 | de la Huerga | Mar 2003 | B1 |
6615107 | Hubicki | Sep 2003 | B2 |
6636780 | Haitin et al. | Oct 2003 | B1 |
6663846 | McCombs et al. | Dec 2003 | B1 |
6702146 | Varis | Mar 2004 | B2 |
6717598 | Melton, Jr. et al. | Apr 2004 | B1 |
6771174 | Broas | Aug 2004 | B2 |
6973371 | Benouali | Dec 2005 | B1 |
6985869 | Stoll et al. | Jan 2006 | B1 |
7002476 | Rapchak | Feb 2006 | B2 |
7072738 | Bonney et al. | Jul 2006 | B2 |
7097037 | Keffeler et al. | Aug 2006 | B1 |
7126879 | Snyder | Oct 2006 | B2 |
7151456 | Godfrey | Dec 2006 | B2 |
7170823 | Fabricius et al. | Jan 2007 | B2 |
7269476 | Ratnakar | Sep 2007 | B2 |
D555893 | Mulaw | Nov 2007 | S |
7304582 | Kerr et al. | Dec 2007 | B2 |
7369919 | Vonk et al. | May 2008 | B2 |
7395929 | Keffeler et al. | Jul 2008 | B2 |
7424888 | Harvey et al. | Sep 2008 | B2 |
7451876 | Bogash et al. | Nov 2008 | B2 |
D588355 | Muehlhausen et al. | Mar 2009 | S |
D597203 | Tauer | Jul 2009 | S |
D606736 | Coran | Dec 2009 | S |
D609592 | Reid | Feb 2010 | S |
7793785 | Keffeler et al. | Sep 2010 | B2 |
7801745 | Walker et al. | Sep 2010 | B2 |
7821404 | Walker et al. | Oct 2010 | B2 |
D627062 | Tanguay | Nov 2010 | S |
7828147 | Caracciolo et al. | Nov 2010 | B2 |
7844361 | Jean-Pierre | Nov 2010 | B2 |
7926850 | Muncy et al. | Apr 2011 | B1 |
7928835 | Jovanov et al. | Apr 2011 | B1 |
7945461 | Sekura | May 2011 | B2 |
D640050 | Barrass | Jun 2011 | S |
7956727 | Loncar | Jun 2011 | B2 |
7978564 | De La Huerga | Jul 2011 | B2 |
D643618 | Guichet | Aug 2011 | S |
7996243 | Ali et al. | Aug 2011 | B1 |
D645559 | Green et al. | Sep 2011 | S |
8014232 | Niemiec et al. | Sep 2011 | B2 |
8019471 | Bogash et al. | Sep 2011 | B2 |
8032393 | Nadas et al. | Oct 2011 | B2 |
8055509 | Walker et al. | Nov 2011 | B1 |
8068931 | Tran et al. | Nov 2011 | B2 |
8069056 | Walker et al. | Nov 2011 | B2 |
D650986 | Brady et al. | Dec 2011 | S |
8085135 | Alloro et al. | Dec 2011 | B2 |
8108068 | Boucher et al. | Jan 2012 | B1 |
8147381 | Iwashita et al. | Apr 2012 | B2 |
8149096 | Metry et al. | Apr 2012 | B2 |
D662217 | Brown et al. | Jun 2012 | S |
8262394 | Walker et al. | Sep 2012 | B2 |
D670377 | Adams | Nov 2012 | S |
D672457 | Foley | Dec 2012 | S |
D674482 | Wurapa | Jan 2013 | S |
8423181 | Hallin | Apr 2013 | B2 |
8424517 | Sutherland et al. | Apr 2013 | B2 |
8536987 | Metry et al. | Sep 2013 | B2 |
8581709 | Mazur | Nov 2013 | B2 |
8583281 | Bear et al. | Nov 2013 | B2 |
8600548 | Bossi et al. | Dec 2013 | B2 |
8725291 | Czaja et al. | May 2014 | B2 |
8754769 | Stein et al. | Jun 2014 | B2 |
D710126 | Salonen | Aug 2014 | S |
D710701 | Lai | Aug 2014 | S |
D711195 | Cornu et al. | Aug 2014 | S |
8800071 | Sanchez et al. | Aug 2014 | B2 |
8805577 | Buisman et al. | Aug 2014 | B2 |
D715041 | McMillen | Oct 2014 | S |
8884752 | Tai et al. | Nov 2014 | B2 |
D718922 | Lai | Dec 2014 | S |
D718923 | Lai | Dec 2014 | S |
D719344 | Miller et al. | Dec 2014 | S |
8914148 | Wagner | Dec 2014 | B2 |
D727482 | Brathwaite | Apr 2015 | S |
D737959 | Wilson | Sep 2015 | S |
D746979 | Dominguez et al. | Jan 2016 | S |
D748751 | Stallings | Feb 2016 | S |
D761551 | Stueckemann et al. | Jul 2016 | S |
D765389 | Martin | Sep 2016 | S |
D767297 | Madsen et al. | Sep 2016 | S |
9501625 | Tsai | Nov 2016 | B2 |
D773175 | Fagen | Dec 2016 | S |
D781065 | Brownley et al. | Mar 2017 | S |
9597261 | Baarman et al. | Mar 2017 | B2 |
11311460 | Gershoni | Apr 2022 | B1 |
20050178786 | Raines | Aug 2005 | A1 |
20060058724 | Handfield et al. | Mar 2006 | A1 |
20060154642 | Scannell, Jr. | Jul 2006 | A1 |
20060259188 | Berg | Nov 2006 | A1 |
20090012818 | Rodgers | Jan 2009 | A1 |
20100076595 | Nguyen | Mar 2010 | A1 |
20100185456 | Kansal | Jul 2010 | A1 |
20110187549 | Balasingam | Aug 2011 | A1 |
20130030566 | Shavelsky et al. | Jan 2013 | A1 |
20130110283 | Baarman | May 2013 | A1 |
20130191140 | Fotheringham et al. | Jul 2013 | A1 |
20130313311 | Fath et al. | Nov 2013 | A1 |
20140055588 | Bangera et al. | Feb 2014 | A1 |
20140207278 | Czaja et al. | Jul 2014 | A1 |
20140214199 | Utech | Jul 2014 | A1 |
20140236349 | Bae | Aug 2014 | A1 |
20140260985 | Akdogan et al. | Sep 2014 | A1 |
20140262918 | Chu | Sep 2014 | A1 |
20140263391 | Akdogan et al. | Sep 2014 | A1 |
20140263423 | Akdogan et al. | Sep 2014 | A1 |
20140263425 | Akdogan et al. | Sep 2014 | A1 |
20140267719 | Akdogan et al. | Sep 2014 | A1 |
20140277705 | Czaja et al. | Sep 2014 | A1 |
20140277707 | Akdogan et al. | Sep 2014 | A1 |
20140277710 | Akdogan et al. | Sep 2014 | A1 |
20140278508 | Akdogan et al. | Sep 2014 | A1 |
20160015602 | Panzini et al. | Jan 2016 | A1 |
20170017774 | Skoda | Jan 2017 | A1 |
20180000692 | Born | Jan 2018 | A1 |
20190224077 | Stein et al. | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
104760768 | Jul 2015 | CN |
WO2013127564 | Sep 2013 | WO |
WO2014165206 | Oct 2014 | WO |
Number | Date | Country | |
---|---|---|---|
20210278270 A1 | Sep 2021 | US |
Number | Date | Country | |
---|---|---|---|
62196131 | Jul 2015 | US | |
62196165 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16699651 | Nov 2019 | US |
Child | 17327243 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15216385 | Jul 2016 | US |
Child | 16699651 | US |