Systems and methods for distributed medication management
By incorporating systems such as drawers, lockable containers, and smart pads into smaller dispensing units, the problem of inscalability of existing automated medication systems is solved and an efficient, safe, and low-cost solution for medication distribution is achieved.
Patent Information
- Application Number
- CN202411468554.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-06-08
- Filing Date
- 2019-05-21
- Publication Date
- 2025-01-24
Smart Images
Figure CN119361073A_ABST
Abstract
Description
[0001] This application is a divisional application of an application with an application date of May 21, 2019, application number 201980038978.8 (international application number PCT / US2019 / 033349), and invention name “System and method for distributed drug management”. Technical Field
[0002] The present disclosure generally relates to automated medication management for healthcare applications. More specifically, the present disclosure relates to devices and methods that provide more scalable solutions, lower costs, and smaller footprints to perform automated medication dispensing over a distributed network of healthcare facilities associated with a central pharmacy server or cloud. Background Art
[0003] Some approaches for automated medication delivery from a central pharmacy server involve expensive equipment with a large footprint, typically located within a single centralized healthcare facility or hospital, where local networking can provide a fast and efficient medication control process. Summary of the invention
[0004] Smaller and more remote facilities still have not implemented automated medication systems, primarily because automated medication systems are not scalable to smaller dispensing units.
[0005] The system for automated medication disclosed herein provides inventory visibility on a continuous system of medication distribution. The system uses devices such as drawers, lockable containers, and smart pads (which are optionally gateways) that interact with each other and exchange information (e.g., inventory information) from a central pharmacy to a remotely located clinic. The system is highly scalable because multiple devices can be seamlessly integrated into the network through instrument identification protocols and multiple wireless connections. The system provides a wide range of devices for all levels of medication distribution. Additional embodiments involving principles similar to those described above are described herein.
[0006] In a first embodiment described herein, a method includes authorizing a user to access a dispensing unit for the purpose of dispensing or loading a drug. The dispensing unit includes a storage location or other secure storage device with a door enclosure. The method further includes storing at least one container and providing a visual indicator to a user for a selected container, the selected container including a drug associated with a drug request in a storage location or other secure storage device with a door enclosure. The storage location or other secure storage device with a door enclosure can be securely unlocked using identity management, and then a latch is activated, which can be done wirelessly. The method further includes unlocking the selected container for the user by wirelessly actuating a latch for the selected container from a smart pad connected to the container, and locking the selected container when the user verifies a transaction including a drug request. The method also includes updating records and drug inventory in a remote server based on the transaction. In some embodiments, when the connection is not immediately available, the transaction record can be synchronized with the server at a later time. In some embodiments, when the connection is not immediately available, the transaction record is synchronized with the server at a later time.
[0007] In a further embodiment, a device includes a surface configured to receive a mobile smart container or device configured to store medication to be dispensed to a patient. The device includes a charging device configured to wirelessly power the mobile smart container or device, and an antenna configured to receive an identification signal from the mobile smart container or device. The device also includes a processor configured to determine medication contents of the mobile smart container or device, and a communication module configured to update medication inventory in a central pharmacy server based on the medication contents of the mobile smart container or device.
[0008] Another embodiment includes a storage device with a door housing or a device for storing at least one container with an identification tag, the storage device having an electronically actuated latch. The device also includes: an antenna configured to scan the identification tag in the closed housing; a processor configured to control the antenna and process information received in the antenna; and a communication module that updates a database in a remote server based on the contents of the at least one container and is processed by the processor. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 A system for distributed medication management according to some embodiments is shown.
[0010] Figure 2 A container for use in a medication dispensing unit according to some embodiments is shown.
[0011] Figures 3A-3FVarious embodiments of a storage device with a door housing for storing multiple storage containers for use in a smart drawer or secure storage device are shown.
[0012] Figure 4 A pad for use in a medication dispensing unit is shown according to some embodiments.
[0013] Figure 5 A mobile medication dispensing unit is shown according to some embodiments.
[0014] Figure 6 A flow chart showing steps in a method for distributed medication dispensing according to some embodiments.
[0015] Figure 7 is a block diagram illustrating an exemplary computer system for distributed medication dispensing, according to some embodiments.
[0016] In the drawings, elements having the same or similar reference numerals have the same or similar function or configuration, unless explicitly stated otherwise. DETAILED DESCRIPTION
[0017] The present disclosure relates to drug delivery systems, related devices, and methods of using the above-mentioned systems and devices. More specifically, some embodiments disclosed herein include methods for distributing drugs and for drug management, including large centralized units located in acute care units (e.g., large hospitals, specialty clinics, etc.) that distribute drugs to distribution systems located in smaller remote facilities (e.g., doctor's offices, nursing homes, etc. in remote villages or towns).
[0018] The system for automated medication disclosed herein provides inventory visibility on multiple levels of medication distribution. The system uses devices such as drawers, lockable containers, and smart pads that interact with each other and exchange information (e.g., inventory information) and are updated on multiple levels of medication distribution from a central pharmacy to a remotely located clinic. In some embodiments, a health care professional requests access to a storage device with one or more door shells in an automatic dispensing machine (ADM). After verifying the authorization credentials of the health care professional, the ADM opens a storage device with one or more door shells, which may include multiple intelligent lockable containers storing multiple medication orders, each container including a display with a visual indicator. An intelligent lockable container is a mobile intelligent container or device that can communicate wirelessly with other devices and networks. An intelligent lockable container can use a visual indicator to signal to a health care professional that the desired medication is stored therein, and automatically unlocks for access. The storage drawer or storage device can be securely unlocked using identity management, and then the latch is wirelessly activated. After taking out the medication, the intelligent lockable container automatically locks and transmits the updated medication inventory information to the central pharmacy server. In some configurations, a storage device with a door housing has a smart pad (e.g., at the bottom of a drawer) that wirelessly exchanges information and provides power to a smart lockable container. In some embodiments, if a connection is not immediately available, the transaction record is synchronized with the server at a later time.
[0019] Some advantages of embodiments consistent with the present disclosure include a mobile dispensing system that operates a cloud-based application, in which users can authenticate access to resources available in the cloud (e.g., drug inventory, requests for drugs, etc.) through a network. The mobile dispensing system includes devices with computing and networking capabilities, such as devices found in the Internet of Things (IOT) configuration (e.g., "smart" devices), namely: near field communication (NFC) protocols and devices, Bluetooth protocols and devices, Bluetooth low energy (BLE) protocols and devices, and also Wi-Fi and cellular communications. More generally, the mobile dispensing system disclosed herein can utilize radio frequency (RF) circuits including antennas, transmitters, and receivers. Some devices also provide contactless charging or wireless charging through RF oscillation near-field magnetic induction or through RF oscillation propagation electromagnetic fields. Some devices are also configured to utilize propagated RF electromagnetic fields and related circuits for RF identification (RFID), low frequency (LF) identification, high frequency (HF) identification, and ultra-high frequency (UHF) identification.
[0020] Therefore, in the system disclosed herein, medicine can be collected at a central pharmacy or at a collection point, where the medicine is collected in a container with an RFID tag. The medicine container is transported to a distributed device at or near a medium-sized or smaller health care facility, where they are collected in a storage device (e.g., a storage drawer) with a door shell, which also has RFID capabilities to identify the container. All equipment in the entire system is constructed to identify the container and determine its contents through RFID tags and related capabilities. A health care professional can carry a mobile unit or trolley with one or more storage devices with a door shell, as well as a mobile dispenser or computer that communicates with the storage device and container with the door shell. A user can retrieve any desired information for delivering medicine from a container in a storage device with a door shell to a specific patient.
[0021] Current methods for medication management and delivery in distributed, smaller-scale health care facilities involve either paper-based systems and non-secure storage at some or all distribution points, or expensive, high-volume automated systems. The embodiments disclosed herein improve upon existing methods by providing security, chain of custody, and full transaction control in a system that scales from a single unit of measure (e.g., a secure container) to any quantity without the need for a single, traditional automated dispensing machine or physical hardware. Large machines typically limit storage and delivery to predetermined volumes, which is often incompatible with small-volume applications.
[0022] These systems and methods can provide devices and inventory at each point of origin and are used in healthcare systems that are geographically dispersed and involve points of care that require a combination of high, medium, and low stock keeping unit (SKU) counts. In addition, the number of SKUs at any point of use can typically be scaled up or down based on demand without the need to install or dismantle hardware and other infrastructure. This is achieved through the logistics and distribution features of the system.
[0023] Some embodiments include multiple physical and software elements and workflows that include a scalable approach for medication management and continuous inventory management.
[0024] Figure 1A system 100 for distributed medication management according to some embodiments is shown. A mobile dispenser 110 includes a memory 20, a processor 12, and a communication module 18. The memory 20 includes an application 22 and patient data 25. The patient data 25 may include information associated with a patient receiving medication from the mobile dispenser 110. The mobile dispenser 110 also includes an input device 14 (e.g., a mouse, a keyboard, a touch screen display, etc.) and an output device 16 (e.g., a display, a speaker, etc.). In some embodiments, the input device 14 and the output device 16 may at least partially include a smart pad that is configured to collect data from sensors and other devices associated with the patient, which may be in close proximity to the smart pad or placed directly on the surface of the smart pad. Thus, a user of the mobile dispenser 110 may input commands and queries to the mobile dispenser 110 through the input device 14, and receive graphics and other information from the mobile dispenser 110 through the output device 16.
[0025] Likewise, the central pharmacy server 130 includes a memory 40, a processor 36, and a communication module 38. In some embodiments, the central pharmacy server 130 may include multiple servers 130 based on a cloud architecture. The memory 40 may include patient data 45 that may be the same or similar to the patient data 25. The patient data 45 may include information associated with a patient receiving medication from the central pharmacy. In some embodiments, the patient data 45 includes the patient data 25 and additional information of other patients that are not associated with the mobile dispenser 110. The memory 40 also includes medication data 47. In some embodiments, the medication data 47 may further include an inventory list of all medications in the central pharmacy, and the patients associated with each medication. In addition, in some embodiments, the central pharmacy server 130 may be connected to a medication database 160, which may be external to the central pharmacy server 130.
[0026] The mobile dispensing machine 110 can be connected to the central pharmacy server 130 through the network 150 via the communication module 18 in the mobile dispensing machine 110 and the communication module 38 in the central pharmacy server 130. The network 150 may include, for example, any one or more of a local area network (LAN), a wide area network (WAN), the Internet, etc. In addition, the network 150 may include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star bus network, a tree or hierarchical network, etc. The communication modules 18 and 38 can be configured to connect to the network 150 to exchange information between the mobile dispensing machine 110 and the central pharmacy server 130. In some embodiments, the communication modules 18 and 38 can be configured as a wireless communication hub (for example, under the IEEE 802.11.xx protocol, the IEEE 802.15.4 protocol, the NFC protocol, the Bluetooth protocol, the BLE protocol, etc.). The application 22 may include an IOT-based application having instructions to access the central pharmacy server 130 and request, retrieve, provide, or update medical information from a patient.
[0027] Either processor 12 or 36 may include an operating system and an embedded system microcontroller configured to execute instructions stored in either memory 20 and / or 40 .
[0028] Figure 2 A container 200 is shown for use in a medication dispensing unit according to some embodiments. In some embodiments, the container 200 may include an IOT cube for storing and dispensing medication.
[0029] The container 200 includes an electrically operable locking lid 202 on top of the body 201. A latch 209 secures the lid 202 to the body 201. In some embodiments, the latch 209 is electrically operated and can be accessed remotely (e.g., by any of the mobile dispensing machine 110 or the central pharmacy server 130, or by a smartphone, tablet, mobile PC, web application, etc. accessible and operable by an authorized user). The container 200 is sturdy and can be made in a variety of sizes and shapes. The container 200 may include a processor 212, a memory 220, a display 216, and a communication module 218. The container 200 also includes a label 205 with a unique identifier (preferably the same as a unique serial number), such as an RFID tag, a linear barcode, or a two-dimensional 2D barcode (e.g., a QR code, etc.). Thus, an external system (eg, mobile dispensing machine 110 and / or central pharmacy server 130) may track and locate container 200 using, for example, BLE beacons, UHF RFID systems, barcode scanners, QR code scanners, and the like.
[0030] Processor 212 may be configured to execute instructions stored in memory 220 to at least partially perform steps in a method consistent with the present disclosure (e.g., processors 12 and 36, and memories 20 and 40). In some embodiments, display 216 may include electronic ink display technology or other display technology capable of electronically adjusting or updating information on display 216. Display 216 may include programmable markings to display information (e.g., a unique serial number, a drug name, an expiration date, the amount of drug stored in container 200, etc.). Power supply 207 (e.g., a battery, a transformer, a rechargeable battery, etc.) provides power to display 216, processor 212, memory 220, and communication module 218. Power supply 207 may include circuitry configured to transmit power from an external source. Communication module 218 may be configured for wireless communication and power, particularly including star and mesh GEN2 UHF RFID power and communication. Power supply 207 (e.g., a capacitor, a battery, or a supercapacitor) provides power, wherein memory 220 may include instructions for processor 212 to execute a power management application to regulate the use of power from power supply 207.
[0031] The container 200 is constructed so that a successful but unauthorized attempt to access its contents is tamper evident. In this way, unauthorized use can be traced back to the last authorized user. In this regard, the memory 220 may include a log file having a history of all access attempts (successful or unsuccessful) to the container 200.
[0032] Management of the container 200 can be accomplished remotely through standard forward and reverse logistics operations from the mobile dispensing unit 110 and the central pharmacy server 130. The container 200 can be delivered to the point of care (e.g., the patient's room or bedside) on a planned or emergency basis. In addition, empty or substandard units of medication in the container 200 can be returned to the central pharmacy for refilling as needed, or moved to another point of care.
[0033] Figures 3A-3F Multiple embodiments of storage devices 300A, 300B, 300C, 300D, 300E and 300F with door housings (hereinafter collectively referred to as "storage devices with door housings 300") are shown, which are used to store multiple storage containers used in smart drawers or other storage devices.
[0034] Figure 3AA storage device 300A with one or more door housings is shown for storing a plurality of storage containers 200 for use in a medication dispensing unit according to some embodiments. More generally, the storage device 300A with door housings can also store a variety of RFID-tagged items that are not enclosed in the container 200, such as a bag of medication and instruments (such as needles, syringes, etc.). The storage device 300A with door housings includes a housing 301 covered by a cover 302 and a locking latch 315, which is used to lock and unlock the housing 301 with the cover 302 based on a control signal received from an authorized user in an antenna 310. The power inlet 307 can include an alternating current (AC) or direct current (DC) power inlet, or a power over Ethernet (POE) inlet, in which case the power inlet 307 can also be configured to receive and provide Ethernet communications with remote devices via a network or cloud architecture (e.g., a central pharmacy server 130 and a network 150). The antenna 310 can include RF circuits for receiving, processing, and transmitting RF signals. In some embodiments, the antenna 310 includes an RFID tag identifier to receive information from one or more containers 200 stored in the housing 301. The communication module 318 (in conjunction with the antenna 310) interrogates the closed space of the storage device 300A with a door housing (e.g., scans the RFID tag from the container 200) and reports them to an external computer. The processor 312 is configured to control the antenna 310 and process the information received in the antenna 310 to execute the instructions stored in the memory 320, so that the storage device 300A with a door housing at least partially performs the steps in the method consistent with the present disclosure. The locking latch 315 may include an electronically actuated latch. Therefore, the communication module 318 (in conjunction with the antenna 310 and the processor 312) can be configured to remotely actuate the locking latch 315 to open or lock the housing 301 with the lid 302. In some embodiments, the storage device 300A with a door housing can use the processor 312, the communication module 318 and the memory 320 to operate as an automatic medication dispensing machine. In some embodiments, the housing 301 may also include different types of devices proximate to the container 200, such as sensors (eg, temperature sensors), beacons, authentication devices, and the like.
[0035] Figure 3B A storage device 300B with one or more door housings is shown for storing multiple storage containers for use in a smart drawer / storage device. The storage device 300B with door housings includes two versions: one with a single door housing that opens to one side of the storage portion, and one with a double door that opens on both sides of the storage portion and closes in the middle of the front side. The storage device 300B with door housings includes an antenna 310, a locking latch 315, and a power inlet 307, as described in detail above.
[0036] Figure 3C A storage device 300C with one or more door shells is shown for storing multiple storage containers used in a smart drawer / storage device. The storage device 300C with a door shell includes a power inlet 307, a memory 320, a processor 312, a communication module 318, and a wireless antenna 310. A locking latch 315 opens the drawer containing the medication. The storage device 300C with a door shell also includes a panel 316 (e.g., an update display 216). In some embodiments, the panel 316 may include electronic ink display technology or other display technology that can electronically adjust or update the information on the panel 316. The panel 316 may include programmable markings to display information (e.g., a unique serial number, a medication name, an expiration date, the amount of medication stored in the storage device 300C with a door shell, etc.). The latch 309 secures the lid for supervision of opening (e.g., latch 209).
[0037] Figure 3D A storage device 300D with one or more door housings is shown for storing multiple storage containers for use in a smart drawer / storage device. The latch 309 is as described above in connection with the storage device with housing 300C.
[0038] Figure 3E A storage device 300E with one or more door shells is shown for storing multiple storage containers used in a smart drawer / storage device. In some embodiments, the storage device 300E with door shells is a modular stack of multiple storage devices 300C with door shells.
[0039] Figure 3F A storage device 300F with one or more door shells is shown for storing multiple storage containers used in a smart drawer / storage device. Thus, the storage device 300F with door shells includes a storage device 300E with door shells inside a storage device 300B with door shells.
[0040] Figure 4An electronically operated control unit or "pad 400" is shown that provides power and communication to the container 200, either wired or wirelessly. According to some embodiments, the pad 400 can be used in a medication dispensing unit. Although the pad 400 is depicted as a flat square shape, in some embodiments, it can include different form factors and more complex surface shapes (e.g., suitable for placement on a three-dimensional object). In some embodiments, the pad 400 can be a network device that is communicatively connected to any of the mobile dispensing machine 110, the central pharmacy server 130, or any mobile device operated by an authorized user (e.g., a medical staff) through a communication module 418 (e.g., communication modules 18 and 38). The communication module 418 can enable the pad 400 to communicate with one or more servers in the cloud architecture (e.g., the central pharmacy server 130) or a local computer near the pad 400. Therefore, in some embodiments, the pad 400 can be integrated with a local application-level computing device. The electronic components in the container 200 can be configured to become fully functional when placed on the pad 400. Processor 412 can communicate with processor 212 in container 200 to transfer data, status and commands, and operate lid 202 (e.g., open and / or lock lid 202 and processors 12 and 36), and change, adjust or update display 216. In some embodiments, processor 412 can be configured to execute commands stored in memory 420 (e.g., memory 20 and 40) to at least partially perform steps in a method consistent with the present disclosure. Identity management port 403 enables user access to wirelessly open the smart container.
[0041] In some embodiments, the processor 412 may include an IOT gateway. Thus, the pad 400 may operate as an IOT gateway for sensors and other devices and apparatuses communicatively coupled to the pad 400. In this regard, sensors and apparatuses that communicate with the pad 400 may include "self-powered" devices that do not need to be near the pad 400 (e.g., temperature sensors, authentication devices, beacons, and other peripherals in the patient's room). In some embodiments, the processor 412 enables the pad 400 to perform local processing (e.g., perform control operations on data provided by the devices and apparatuses or perform inventory operations based on the data) and communicate with a server or cloud device (e.g., the central pharmacy server 130).
[0042] In some embodiments, the pad 400 is configured to power and communicate with an "energy harvesting" device (e.g., container 200). To this end, the pad 400 may include a contactless charging device 405 to wirelessly power the power source 207 in the container 200. Thus, the contactless charging device 405 may be configured to provide inductive or resonant power through a near field, an RF oscillating magnetic field, a propagated resonant RF electromagnetic field, or an optical charging device (e.g., through a light emitting diode or laser). The choice of charging strategy in the contactless charging device 405 can vary depending on the desired device or equipment to be charged, the range and power available from the contactless charging device 405, and the power desired to charge the external device.
[0043] The pad 400 can be configured to receive a device with a variable form factor or an "any surface" smart device on or near its surface. The device placed on the pad 400 can be configured to receive power from the contactless charging device 405 and communicate with a computer or other cloud-based device (e.g., a smartphone, a tablet, a mobile computer, etc.) to operate the device (e.g., container 200). Other devices that can be placed on and interact with the pad 400 may include display modules, sensor modules, identification modules, third-party devices, consumer devices, etc. In addition, the pad 400 can receive and interact with other self-powered mobile devices (such as BLE beacons, sensors, and even smart phones) with additional ranges. In this regard, the device or device that is communicatively connected to and interacts with the pad 400 may not be placed directly on top of the surface of the pad 400, and may be within the range of any of a variety of communication protocols between the pad 400 and the device or device. The communication module 418 can also be configured in some applications to communicate with a network (e.g., network 150), a local computer, and other devices as needed.
[0044] The pad 400 may include a power inlet 407. In some embodiments, the power inlet 407 may include an alternating current (AC) or direct current (DC) power inlet, or a power over Ethernet (POE) inlet, in which case the power inlet 407 may also be configured to receive and provide Ethernet communications with a remote device via a network or cloud architecture (e.g., the central pharmacy server 130 and the network 150). In some embodiments, the pad 400 includes a sensor 409 that is configured to determine the physical properties (e.g., weight, size, and shape) of a device placed on the pad surface. Thus, the sensor 409 may include an electrical sensor, a magnetic sensor, an optical sensor (e.g., a photodetector or a camera), or a mechanical sensor. The pad 400 may also include an antenna 410. In some embodiments, the antenna 410 is an identification device that may include an RFID antenna (e.g., a GEN2 RFID reader / antenna) that provides RFID power in addition to reading identification data from the container 200. In some embodiments, the antenna 410 may include an NFC identification reader, or a LF or HF identification reader. Antenna 410 may be configured to perform multiple forms of communication, or may include more than one type of antenna (e.g., Wi-Fi, Bluetooth, etc.). In some embodiments, in addition to identification signals, communications between mat 400 and any device or equipment placed on its surface or in sufficient proximity to mat 400 may include sensor data, inventory data, maintenance data, and control information for operating the equipment (e.g., opening or closing a lid, drawer, updating a display, etc.).
[0045] In some embodiments, the pad 400 may include a sensor (e.g., a weight sensor) for determining physical properties of a device placed on its surface (e.g., the weight and / or size of the container 200). In addition, the processor 412 may be configured to process the physical properties of the device as relevant information, which may be stored in the memory 420 or sent to the central pharmacy server via the communication module 418. For example, in some embodiments, the pad 400 may be configured to track equipment, materials, and supplies that are placed directly (accidentally or unintentionally) on the pad 400 by a health care provider or within range of the communication module 418.
[0046] When the processor 412, memory 420, and communication module 418 are integrated with the Gen2 UHF RFID option, then the mat 400 can be configured to open and access any secure enclosure (e.g., storage device 300A with door enclosure) with RFID-tagged items placed on the mat 400. For example, in some embodiments, the mat 400 can power and operate latches (e.g., latch 315 and lid 302) for the lid of the secure enclosure.
[0047] In some embodiments, the pad 400 can be integrated with a computing device at the local application level. In addition, in some embodiments, the pad 400 can be instantiated or configured as a HUB or gateway device that allows smart devices to communicate and is optionally powered on the pad 400. For example, in some embodiments, the pad 400 can be configured to receive data from inside the patient's room or near the patient's bed. Therefore, the pad can receive patient identification data (e.g., from a beacon placed near the patient's bed) and other medical data associated with the patient, including body temperature (e.g., from a temperature sensor in the patient's body), room temperature, or cardiopulmonary status (e.g., heart rate, amount of air in breathing, etc.). In other embodiments, the pad 400 can be configured to provide and update drug information about patients near the pad 400 once a nurse or other medical staff member places a portable computer (e.g., a smartphone, tablet computer, or any other mobile computer device) on the surface of the pad 400.
[0048] In some embodiments, the mat 400 can be configured to form a bottom surface in the storage device with door shell 300A (e.g., the bottom plate of the storage device with door shell 300A, see Figure 3A ). More generally, any side of the storage device with door housing 300A (including the lid 302) can be configured at least in part as a mat 400. Thus, the mat 400 can communicate with the storage device with door housing 300A via antennas 410 and 310 located in the mat 400 and the storage device with door housing 300A, respectively. In addition, the mat 400 can communicate directly with the container 200 and any other device inside the housing 301, and perform inventory operations or alarm communications based on the received data. For example, the sensor inside the housing 301 can be a temperature sensor that indicates that the contents of the container 200 can be expected to be replaced, arranged, removed, or that the storage device with door housing 300A may need to be moved to a different device.
[0049] Figure 5A mobile medication dispensing unit 500 is shown according to some embodiments. The mobile medication dispensing unit 500 may include a cart 501 with wheels to allow a health care professional to carry the mobile medication dispensing unit 500 from the vicinity of a first patient to the vicinity of a second patient. The mobile medication dispensing unit 500 may include a plurality of containers 200 stored within a storage device 501A with a door housing (e.g., any of the storage devices 300 with door housings). Additionally, in some embodiments, the medication dispensing unit 500 includes a pad 400 that communicates with a computer 503 including a display 516. An input device 514 (e.g., a keyboard, a mouse, a pointer, etc.) may be coupled to the computer 503 so that a user may provide commands and request actions from the computer 503. Thus, certain aspects of the mobile medication dispensing unit 500 may be as described above with respect to the mobile dispensing machine 110. More specifically, the mobile medication dispensing unit 500 may include the mobile medication dispensing machine 110 described above (see Figure 1 ) features and capabilities. The mobile medication dispensing unit 500 can be transported to a location near a medication dispensing point (e.g., a patient's bedside, an operating room, etc.). In some embodiments, a plurality of storage devices 501B with door shells can be arranged in a vertical stack of different plan view sizes to achieve a specific storage capacity (hereinafter collectively referred to as "storage devices 501 with door shells"). Therefore, the mobile medication dispensing unit 500 can be conveniently expanded from one or two storage devices 501A and 501B with door shells to any number (e.g., three, four, or even more). In addition, the mobile medication dispensing unit 500 can include location tracking capabilities (e.g., beacons, real-time location systems (RTLS), radio frequency identification (RFID) tags, etc.).
[0050] The health care provider can refill, replace or empty the medication stored in the container 200 by communicating with the central pharmacy server 130 using the computer 503 through the mobile medication dispensing unit 500. Thus, a user (e.g., a health care provider) can receive instructions from the central pharmacy server 130 to refill, replace or empty the contents of one or more containers 200. The user can then carry one or more containers 200 or the storage device with door housing 501 to the central pharmacy, where the contents of one or more containers 200 are refilled, replaced or emptied. The user can also return, import or remove one or more containers 200 to the storage device with door housing 501 according to the instructions from the central pharmacy server 130. In some embodiments, the user may be authorized to access the storage device with door housing 501 and any one of the containers 200 to increase or decrease the quantity of the contained items at the user's discretion. In such a configuration, the registration information of the removed items and their quantities can be recorded in the memory of the computer 503 and transmitted to the central pharmacy server 130 to update the patient data 45 and the medication data 47. In some embodiments, the container 200 implements an RFID that is directly coupled to a processor (e.g., processor 412) in the mobile medication dispensing unit 500.
[0051] Additional information such as the user's associated information (e.g., identity, authorization level, contact with the patient, etc.), the serial number of the container 200, or the quantity and description of the items inside the container 200 (including metadata (e.g., expiration date)) can be remotely retrieved by the mobile medication dispensing unit 500 from the central pharmacy server 130.
[0052] The mobile medication dispensing unit 500 ensures the physical security of medications delivered to patients regardless of the distance to a central pharmacy, such as during transport. Thus, items stored in the container 200 are conveniently and safely dispensed to and returned from geographically remote points of use. At the point of use, the container 200 is received and can be stored in a storage device 501 with a door housing.
[0053] Figure 6A flowchart of various steps in a method 600 for distributed medication dispensing according to some embodiments is shown. At least some of the steps in method 600 may be performed by a computer having a processor that executes commands stored in a memory of the computer (e.g., mobile dispensing machine 110, central pharmacy server 130, pad 400, processor 12, 36, 212, 312, or 412, and memory 20, 40, 220, or 420). At least some of the steps in method 600 may be performed by a mobile medication dispensing device that includes one or more storage devices with door housings, each storage device with door housing having at least one or more containers that include medication or any other labeled items (e.g., medication dispensing device 500, container 200, storage device with door housing 300A, and pad 400). In some embodiments, the steps in method 600 may be partially performed by a mobile dispensing machine and a central pharmacy server that are communicatively coupled to each other via a communication module over a network (e.g., communication modules 18 and 38, and network 150). In addition, the steps disclosed in method 600 may include retrieving, editing, and / or storing files in a database that is part of or communicatively coupled to the computer (e.g., drug database 160). Methods consistent with the present disclosure may include at least some, but not all, of the steps shown in method 600 performed in a different order. In addition, methods consistent with the present disclosure may include at least two or more steps as in method 600 that overlap in time or are performed nearly simultaneously.
[0054] Step 602 includes authorizing a user to access a dispensing unit based on a medication request. In some embodiments, step 602 includes authorizing a user to access a storage device with a door housing in a mobile dispensing machine through a central pharmacy server.
[0055] Step 604 includes indicating to the user a storage device with a door housing in the dispensing unit associated with the medication request.
[0056] Step 606 includes displaying to the user a list of one or more medications in the storage device with the door housing indicated in the medication request.
[0057] Step 608 includes providing access to the storage device with the door housing to the user. In some embodiments, step 608 may include remotely actuating a latch to open a lid in the storage device with the door housing.
[0058] Step 610 includes providing a visual indicator to a user for a selected container in a storage device with a door housing that is associated with a medication request. In some embodiments, step 610 may include flashing a light emitting diode (LED) in the selected container (e.g., in red, green, or blue). In some embodiments, step 610 may include adjusting a display in the selected container so that it attracts the user's visual attention (e.g., a flashing logo on a display, etc.). In some embodiments, step 610 may further include providing an audio indicator (e.g., a beep, buzzer, etc.) or a mechanical indicator (e.g., a vibration pattern, etc.) to the container.
[0059] Step 612 includes providing access to at least one storage container to the user. In some embodiments, step 612 may include unlocking the selected container for the user (e.g., by wirelessly actuating a latch for a lid in at least one storage container from the pad). Thus, in some embodiments, step 612 may include receiving a storage container on a surface of a pad that is configured to recognize the selected container and unlock the lid in the selected container upon recognition. In some embodiments, step 612 includes sending an NFC, Bluetooth, or BLE command, etc., to a processor in the selected container (e.g., pad 400) to unlock the container lid or release a latch in the container lid.
[0060] Step 614 includes determining the contents of the medication in the selected container based on medication removal or medication addition by the user.
[0061] Step 616 includes displaying to the user a verification list in which at least some of the medications were removed from or added to the at least one storage container.
[0062] Step 618 includes locking at least one storage container when the user has authenticated the transaction.In some embodiments, step 618 may include receiving the selected container on a pad surface configured to wirelessly actuate a latch for a lid in the selected container.
[0063] Step 620 includes updating the records and medication inventory in the remote server based on the transaction. In some embodiments, step 620 may include scanning the contents of the storage device with the door shell and each container stored therein and reporting the serial number of the tag in the storage device with the door shell. In some embodiments, step 620 may include updating the contents of the storage device with the door shell, including serial numbers for new containers and removed containers since the storage device with the door shell was last unlocked. In this way, the device of the container 200 and any other tagged items that may be stored in the storage device with the door shell can be determined. In some embodiments, step 620 may include accessing the central pharmacy server to update the database in the mobile dispensing machine and in the central pharmacy server.
[0064] Figure 7 is a block diagram illustrating an exemplary computer system 700 according to some embodiments, which may be utilized to implement the methods and steps illustrated in method 600. In certain aspects, computer system 700 may be implemented in hardware or a combination of software and hardware in a dedicated server integrated into another entity, or in dedicated servers distributed among multiple entities.
[0065] The computer system 700 includes a bus 708 or other communication mechanism for communicating information, and a processor 702 coupled to the bus 708 for processing information. For example, the computer system 700 may be implemented with one or more processors 702. The processor 702 may be a general purpose microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a state machine, a gated logic, a discrete hardware component, or any other suitable entity that can perform calculations or other information manipulations. In some embodiments, the processor 702 may include modules and circuits configured as a "placement" tool or engine or a "routing" tool or engine to place devices and routing channels in a circuit layout accordingly and as disclosed herein.
[0066] In addition to the hardware, the computer system 700 also includes code that creates an execution environment for the computer program in question, for example, code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them, stored in the included memory 704 coupled to the bus 708 for storing information and instructions to be executed by the processor 702, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable PROM (EPROM), registers, hard disk, removable disk, CD-ROM, DVD, or any other suitable storage device. The processor 702 and memory 704 may be supplemented by or integrated into special purpose logic circuitry.
[0067] These instructions may be stored in memory 704 and implemented in one or more computer program products (i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by computer system 700 or for controlling the operation of the computer system) and according to any method known to those skilled in the art, including but not limited to computer languages, such as data-oriented languages (e.g., SQL, dBase), system languages (e.g., C, Objective-C, C++, assembly), framework languages (e.g., Java, .NET), and application languages (e.g., PHP, Ruby, Perl, Python). The instructions may also be implemented in a computer language, such as an array language, an aspect-oriented language, an assembly language, an editing language, a command line interface language, a compiled language, a concurrent language, a curly brace language, a data flow language, a data structured language, a declarative language, an esoteric language, an extended language, a fourth generation language, a functional language, an interactive mode language, an interpreted language, an iterative language, a list-based language, a small language, a logic-based language, a machine language, a macro language, a metaprogramming language, a multi-paradigm language, a numerical analysis, a non-English-based language, an object-oriented class-based language, an object-oriented prototype-based language, an off-site rule language, a procedural language, a reflective language, a rule-based language, a scripting language, a stack-based language, a synchronous language, a syntax processing language, a visual language, a Wirth language, an embeddable language, and an xml-based language. The memory 704 may also be used to store temporary variables or other intermediate information during the execution of instructions executed by the processor 702.
[0068] The computer programs discussed herein do not necessarily correspond to files in a file system. A program may be stored in a portion of a file that stores other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., a file storing a portion of one or more modules, subroutines, or codes). A computer program may be deployed to be executed on one or more computers, which are located at one site or distributed at multiple sites and interconnected by a communication network. The processes and logic flows described in this specification may be performed by one or more programmable processors, which execute one or more computer programs to perform functions by operating on input data and generating outputs.
[0069] Computer system 700 further includes a data storage device 706 , such as a magnetic or optical disk, coupled to bus 708 for storing information and instructions.
[0070] The computer system 700 is connected to various devices via an input / output module 710. The input / output module 710 is any input / output module. An exemplary input / output module 710 includes a data port, such as a USB port. The input / output module 710 is configured to connect to a communication module 712. An exemplary communication module 712 includes a network interface card, such as an Ethernet card and a modem. In some aspects, the input / output module 710 is configured to connect to multiple devices, such as an input device 714 and / or an output device 716. An exemplary input device 714 includes a keyboard and a pointing device, such as a mouse or a trackball, through which a user can provide input to the computer system 700. Other types of input devices 714 are also used to provide interaction with the user, such as a tactile input device, a visual input device, an audio input device, or a brain-computer interface device. For example, the feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and the input from the user can be received in any form, including sound, speech, tactile, or brain wave input. Exemplary output devices 716 include display devices such as LED (light emitting diode), CRT (cathode ray tube), or LCD (liquid crystal display) screens for displaying information to a user.
[0071] The methods disclosed herein may be performed by the computer system 700 in response to the processor 702 executing one or more sequences of one or more instructions contained in the memory 704. Such instructions may be read into the memory 704 from another machine-readable medium (such as a data storage device 706). The execution of the sequence of instructions contained in the main memory 704 causes the processor 702 to perform the process steps described herein (e.g., as described in the method 600). One or more processors in a multi-processing arrangement may also be employed to execute the sequence of instructions contained in the memory 704. In alternative aspects, hard-wired circuits may be used in place of software instructions or in combination with software instructions to implement various aspects of the present disclosure. Therefore, aspects of the present disclosure are not limited to any specific combination of hardware circuitry and software.
[0072] Various aspects of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, such as a data server; or includes a middleware component, such as an application server; or includes a front-end component, such as a client computer with a graphical user interface or a web browser (a user can interact with the implementation of the subject matter described in this specification through the graphical user interface or the web browser), or any combination of one or more such back-end, middleware or front-end components. The components of the system can be interconnected by digital data communication (such as a communication network) in any form or medium. The communication network can include, for example, any one or more of a personal area network (PAN), a local area network (LAN), a campus network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, etc. In addition, the communication network can include, but is not limited to, for example, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star bus network, a tree or hierarchical network, etc. The communication module can be, for example, a modem or an Ethernet card.
[0073] Computing system 700 includes server and personal computer equipment. Personal computing equipment and server are usually far away from each other, and usually interact through communication network. The relationship between client and server is produced by means of computer programs running on respective computers and having client-server relationship between each other. Computer system 700 can be, for example, but not limited to desktop computer, portable computer or tablet computer. Computer system 700 can also be embedded in another device, for example, but not limited to mobile phone, personal digital assistant (PDA), mobile audio player, global positioning system (GPS) receiver, video game console and / or TV set-top box.
[0074] The term "machine-readable storage medium" or "computer-readable medium" as used herein refers to any medium or multiple media that participates in providing instructions or data to processor 702 for execution. Such media can take multiple forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical disks, disks, or flash memory, such as data storage device 706. Volatile media include dynamic memory, such as memory 704. Transmission media include coaxial cables, copper wires, and optical fibers, including wires including bus 708. Common forms of machine-readable media include, for example, floppy disks, floppy disks, hard disks, tapes, any other magnetic media, CD-ROMs, DVDs, any other optical media, punch cards, paper tapes, any other physical media with hole patterns, RAM, PROMs, EPROMs, FLASH EPROMs, any other memory chips or cassettes, or any other media that a computer can read. The machine-readable storage medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of substances that affect machine-readable propagation signals, or a combination of one or more of them.
[0075] In one aspect, a method may be an operation, an instruction, or a function, and vice versa. In one aspect, a clause or claim may be modified to include some or all of the words (e.g., instructions, operations, functions, or components) cited in one or more other clauses, one or more words, one or more sentences, one or more phrases, one or more paragraphs, and / or one or more claims.
[0076] To illustrate the interchangeability of hardware and software, items such as various illustrative blocks, modules, components, methods, operations, instructions, and algorithms have been generally described in terms of their functionality. Whether such functionality is implemented as hardware, software, or a combination of hardware and software depends on the specific application and the design constraints imposed on the overall system. A skilled person may implement the described functionality in different ways for each specific application.
[0077] As used herein, the phrase "at least one of" preceding a list of items (with the terms "and" or "or" separating any of the items) modifies the list as a whole, rather than each member of the list (e.g., each item). The phrase "at least one of" does not require selection of at least one item; rather, the phrase allows for a meaning that includes at least one of any one item, and / or at least one of any combination of items, and / or at least one of each item. For example, the phrase "at least one of A, B, and C" or "at least one of A, B, or C" all mean only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.
[0078] To the extent that the terms "including," "having," and the like are used in the specification or claims, such terms are intended to be inclusive in a manner similar to the term "comprising" as interpreted when "including" is used as a transitional word in a claim.
[0079] The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as "exemplary" in this article is not necessarily to be interpreted as being preferred or advantageous to other embodiments. Phrases such as one aspect, this aspect, another aspect, some aspects, one or more aspects, an embodiment, this embodiment, another embodiment, some embodiments, one or more embodiments, an embodiment, this embodiment, another embodiment, some embodiments, one or more embodiments, a construction, this construction, another construction, some constructions, one or more constructions, subject technology, the disclosure, the present disclosure, other variations thereof, etc. are for convenience and do not mean that the disclosures associated with these phrases are necessary for the subject technology, or that these disclosures are applicable to all constructions of the subject technology. The disclosures associated with such phrases may apply to all constructions or one or more constructions. The disclosures associated with such phrases may provide one or more examples. Phrases such as one aspect or some aspects may refer to one or more aspects, and vice versa, and this applies similarly to the other aforementioned phrases.
[0080] Unless otherwise stated, referring to an element in the singular form is not intended to mean "one and only one", but "one or more". The term "some" refers to one or more. The underlined and / or italicized titles and subtitles are used for convenience only, not to limit the subject technology, and do not indicate a connection with the explanation of the description of the subject technology. Relevant terms such as first and second can be used to distinguish one entity or action from another, without requiring or implying any actual such relationship or order between these entities or actions. All structural and functional equivalents of the elements of the various configurations described throughout the present disclosure are known to or will be known to those of ordinary skill in the art in the future, which are expressly incorporated herein by reference and are intended to be covered by the subject technology. In addition, none of the contents disclosed herein are intended to be contributed to the public, regardless of whether such disclosure is explicitly stated in the above description. The elements of the claims are not interpreted according to the provisions of the sixth paragraph of 35 U.S.C. §112 (f), unless the phrase "device for..." is used to clearly state the element, or in the case of a method claim, the phrase "step for..." is used to state the element.
[0081] Although this specification contains many details, these details should not be interpreted as limitations on the scope of the claimed protection, but rather as descriptions of specific implementations of the subject matter. Certain features described in the context of each individual embodiment in this specification may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable sub-combination. In addition, although features may be described above as working in certain combinations, and even initially claimed as such, in some cases, one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.
[0082] The subject matter of this specification has been described according to specific aspects, but other aspects may also be implemented and are within the scope of the appended claims. For example, although operations are described in a particular order in the drawings, this should not be understood as requiring that these operations be performed in the particular order or sequential order shown, or requiring that all operations shown be performed to obtain the desired results. The actions listed in the claims can be performed in different orders and still obtain the desired results. As an example, the processes described in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above aspects should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
[0083] The title, background, brief description of the drawings, abstract, and drawings are incorporated into this disclosure and are provided as illustrative examples of the disclosure, not as limiting descriptions. The present application is submitted with the understanding that they are not used to limit the scope or meaning of the claims. In addition, in the specific embodiments, it can be seen that the description provides illustrative examples, and in order to simplify the disclosure, various features are combined together in various embodiments. The method of the present disclosure should not be interpreted as reflecting the intention that the claimed subject matter requires more features than those explicitly stated in each claim. On the contrary, as reflected in the claims, the inventive subject matter lies in less than all the features of a single disclosed construction or operation. The claims are thus incorporated into the detailed description, and each claim is independently a separately claimed subject matter.
[0084] The claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims and including all legal equivalents. Nevertheless, any claims are not intended to include subject matter that does not satisfy the requirements of applicable patent law, nor should they be interpreted in such a manner.
Claims
1. A smart mat, comprising: a planar surface configured to receive a mobile smart container configured to store one or more medications; an antenna configured to wirelessly communicate with the mobile smart container when the mobile smart container is received on the surface; a communication module configured to communicate with a server; as well as A processor configured to: upon receiving a medication request indicating one or more medications, determining whether the user is authorized to access the dispensing unit; The processor is configured to, when the user is authorized: identifying a mobile smart container within the dispensing unit based on the medication request, the mobile smart container being identified by activating a visual indicator via a display associated with the mobile smart container; receiving input from a user to access the mobile smart container; unlocking the mobile smart container by wirelessly unlocking a lid of the mobile smart container using the smart pad based on the input; In response to a mobile smart container being received on the surface of the smart mat, determining a medication content of the mobile smart container; Based on the drug contents of the mobile smart container, the drug inventory in the central pharmacy server is updated; as well as When the medication contents of the mobile smart container are not verified with the central pharmacy server's database, a display alert is provided to the user.
2. The smart mat according to claim 1, wherein: The processor is further configured to: Based on the antenna scanning one or more RFID tags of the mobile smart container, the drug content of the mobile smart container is determined.
3. The smart mat according to claim 1, wherein: The processor is further configured to: When a mobile smart container is placed on the surface of the smart mat, the mobile smart container is identified based on transmission between an RFID tag of the mobile smart container and an antenna of the smart mat.
4. The smart mat according to claim 3, wherein: The processor is further configured to: In response to recognizing a mobile smart container with the smart pad, a lid of the mobile smart container is wirelessly unlocked.
5. The smart mat according to claim 1, further comprising: a sensor configured to determine a physical property of the mobile smart container when the mobile smart container is placed on a surface of the smart mat, Wherein, the processor is further configured to transmit the physical attributes to the server.
6. The smart mat according to claim 1, wherein: The processor is further configured to, when the user is authorized: receiving patient data associated with the patient; and providing the patient data to the central pharmacy server using the communication module so as to be associated with the patient on the central pharmacy server, The patient data includes the patient's body temperature, the room temperature associated with the patient, or the patient's cardiopulmonary condition.
7. The smart mat according to claim 6, wherein: Receiving patient data includes: When a patient is located in proximity to the smart mat, patient identification data associated with the patient is received using the antenna.
8. The smart mat according to claim 6, wherein: Providing patient data includes: In response to a mobile computing device being placed on the surface of the smart mat, medication information about the patient is provided and updated, the mobile computing device being associated with a medical professional associated with the patient.
9. The smart mat according to claim 8, wherein: Patient data is received in response to a mobile computing device associated with a clinician being placed on the surface of the smart mat.
10. The smart mat according to claim 1, wherein: The processor is further configured to, when the user is authorized: verifying a transaction associated with the medication request; and Based on the transaction and the determined medication contents of the mobile smart container, records and medication inventory in the central pharmacy server are updated.
11. The smart mat according to claim 1, further comprising: A charging device is configured to wirelessly power the mobile smart container when the mobile smart container is received on the surface.
12. A dispensing system comprising: a planar smart mat comprising an antenna and a communication module, the smart mat being configured to receive a mobile smart container configured to store one or more medications; a dispensing unit comprising one or more housings securing storage locations, wherein the smart mat forms a surface of a corresponding housing; as well as A processor configured to: upon receiving a medication request indicating one or more medications, determining whether a user is authorized to access the dispensing unit; and When the user is authorized: identifying a selected smart container within the dispensing unit based on the medication request, identifying the selected smart container by activating a visual indicator via a display associated with the selected smart container; receiving input from a user to access a selected smart container; unlocking the selected smart container by wirelessly unlocking a lid of the selected smart container using the smart pad based on the input; determining the drug contents of the selected smart container using an antenna of the smart mat based on the selected smart container being placed on the surface of the smart mat; updating the drug inventory in the server based on the drug contents of the mobile smart container; as well as When the drug contents of the selected smart container are not verified with the server's database, a display alert is provided to the user.
13. The dispensing system of claim 12, wherein: The processor is further configured to: The smart mat is utilized to determine the pharmaceutical contents of the selected smart container based on the antenna scanning the one or more RFID tags of the selected smart container.
14. The dispensing system of claim 12, wherein: The processor is further configured to: When a selected smart container is placed on the surface of the smart mat, the selected smart container is identified based on transmissions between an RFID tag of the selected smart container and an antenna of the smart mat.
15. The dispensing system of claim 14, wherein: The processor is further configured to: In response to identifying the selected smart container with the smart mat, the lid of the selected smart container is wirelessly unlocked using the antenna of the smart mat.
16. The dispensing system of claim 12, further comprising: a sensor configured to determine a physical property of a selected smart container when the selected smart container is placed on a surface of the smart mat, Wherein, the processor is further configured to transmit the physical attributes to the server.
17. The dispensing system of claim 12, further comprising: receiving patient data associated with a patient; as well as providing the patient data to the server using the communication module for association with the patient on the server, The patient data includes the patient's body temperature, the room temperature associated with the patient, or the patient's cardiopulmonary condition.
18. The dispensing system of claim 17, wherein: Receiving patient data includes: When the patient is located in the vicinity of the smart mat, receiving patient identification data associated with the patient using an antenna of the smart mat; and In response to a mobile computing device associated with the patient being placed on the surface of the smart mat, medication information about the patient is provided and updated, the mobile computing device being associated with a medical professional associated with the patient.
19. The dispensing system of claim 17, wherein: The processor is further configured to: In response to a mobile computing device associated with a medical professional being placed on the surface of the smart mat, medication information about the patient is updated.
20. The dispensing system of claim 12, wherein: The processor is further configured to: verifying a transaction associated with the medication request; and Based on the transaction and the determined medication contents of the mobile smart container, records and medication inventory in the server are updated.
21. A method comprising: Providing a planar smart mat including an antenna and a communication module, the smart mat being configured to receive a mobile smart container configured to store one or more medications; upon receiving a medication request indicating one or more medications, determining whether a user is authorized to access a dispensing unit, the dispensing unit comprising one or more housings securing storage locations, wherein the smart mat forms a surface of a corresponding housing; as well as When the user is authorized: identifying a selected smart container within the dispensing unit based on the medication request, identifying the selected smart container by activating a visual indicator via a display associated with the selected smart container; receiving input from a user to access a selected smart container; unlocking the selected smart container by wirelessly unlocking a lid of the selected smart container using the smart pad based on the input; determining the drug contents of the selected smart container using an antenna of the smart mat based on the selected smart container being placed on the surface of the smart mat; updating the drug inventory in the server based on the drug contents of the mobile smart container; as well as When the drug contents of the selected smart container are not verified with the server's database, a display alert is provided to the user.