Locking Cap Assembly

Abstract

The locking cap assembly includes an upper housing, a lower housing rotatably connected to the upper housing and configured to mate with the container, an NFC module configured to wirelessly receive a near field communication NFC input, an inductive charging coil, a microprocessor, and a latching mechanism including a locking latch configured to prevent the upper and lower housings from rotating relative to one another and an electrically actuated component configured to lock and unlock a current generated by the latch and the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, the locking vanes configured to variably define an inner diameter size of the lower housing responsive to rotation of the upper housing relative to the lower housing when the lower housing is in mechanical engagement with the container.

Description

Technical Field

[0005] ,

[0004] , , , , ,

[0006] ,

[0001] This application claims priority to U.S. Provisional Application No. 63 / 162482, filed on March 17, 2021, entitled "Locking Cap Assembly", which is hereby incorporated by reference in its entirety.

[0002] This application generally relates to a locking cap assembly.

Background Art

[0003] Unauthorized access to a medical container or administering a drug before the scheduled time for a subsequent dose can pose a risk to patient safety.

Summary of the Invention

[0004] Patient safety can be enhanced by ensuring that authorized access to a container storing a drug is provided only to an authorized person at an authorized time. Some patients may not be able to adhere to the schedule for self - administration of a prescribed drug. As a result, inadvertently administering a subsequent dose of a drug before the intended time for that dose can pose a risk to patient safety. In some cases, a patient may not remember when the last dose was administered, which can make it uncertain when the next dose should be administered.

[0005] [[ID=Z7]]Therefore, there is a need for systems, devices, and methods to assist patients in adhering to the dosing schedule of prescribed drugs. Patient safety can be improved by providing authorized access to the drug only to the patient or caregiver at an authorized time (e.g., the time of a subsequent dose) and automatically logging the time when the drug is accessed from the container.

[0006] The systems, apparatus, and methods described herein provide automated methods for unlocking a drug container only when a valid authorization code is provided to the locking cap assembly that locks the drug container and secures the drug. Depending on the various implementations, the drug container may only be unlocked within a time frame in which a subsequent dose of the drug is administered. The authorization code may be communicated between the caregiver and / or the patient to allow additional or different authorized personnel to access the drug container.

[0007] The devices and systems of this disclosure include a locking cap assembly having an upper housing, a lower housing rotatably connected to the upper housing and configured to fit into a container, an NFC module configured to wirelessly receive near-field communication (NFC) inputs, an inductive charging coil, a microprocessor, and a latching mechanism. The latching mechanism includes a locking latch configured to prevent the upper and lower housings from rotating relative to each other, and an electrically actuated component configured to lock and unlock the latch in response to signals received from the microprocessor and currents generated by the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, the locking vanes configured to variably define the inner diameter size of the lower housing in response to the rotation of the upper housing relative to the lower housing when the lower housing is mechanically engaged with the container. The locking cap assembly is configured to lock the container by retracting the plurality of vanes around the container in response to the rotation of the upper housing relative to the lower housing in a first direction. The microprocessor is configured to receive an NFC input from the NFC module and, in response to the microprocessor determining that the NFC input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, unlock the locking latch, allow the upper housing to rotate in a second direction relative to the lower housing, retract the multiple locking vanes, and release the lower housing from the container.

[0008] The subject matter of this disclosure also relates to a method for securing a drug container, the method comprising the step of receiving an authorization code wirelessly transmitted via a communication channel of a Near Field Communication (NFC) module in a locking cap assembly from a device placed near the locking cap assembly. According to the determination that the authorization code is a valid authorization code, it is determined whether the current time is within a drug administration time interval. According to the determination that the current time is within a drug administration time interval, if the input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, the locking latch of the locking cap assembly is released to allow the multiple locking vanes of the locking cap assembly to retract. The multiple locking vanes variably define the size of the central opening, and the central opening defined by the multiple locking vanes is configured to mechanically engage with the drug container in the locked state of the locking cap assembly. Power to release the locking latch is provided by wireless energy transfer from a device via a communication channel to a motor of the locking cap assembly.

[0009] Other embodiments include corresponding systems and corresponding devices for implementing their features, and computer program products.

[0010] Other configurations of this technology will be readily apparent to those skilled in the art from the following detailed description, which illustrates and explains various configurations of this technology. As will be understood, other different configurations of this technology are possible, and some of its details can be modified in various other ways without departing entirely from the scope of this technology. Therefore, the drawings and detailed description should be considered illustrative and not limiting in nature.

[0011] To better understand the various implementation configurations described, the following explanations should be referenced in conjunction with the following diagrams. Throughout the diagrams and explanations, the same reference numbers refer to the corresponding parts. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows an example of an in-facility patient care system in a healthcare organization, based on an embodiment of this technology. [Figure 2A] This figure shows an example of a locking cap assembly fixed to a medicine container according to an embodiment of this technology. [Figure 2B] This figure shows an example of a locking cap assembly having two different configurations of locking vanes according to an aspect of this technology. [Figure 2C] This figure shows two different configurations of locking vanes according to an aspect of this technology. [Figure 2D] Figure 2A is a cross-sectional view of a locking cap assembly and medicine bottle according to an embodiment of this technology. [Figure 3A] This is an exploded view of a locking cap assembly according to an embodiment of this technology. [Figure 3B] This is a detailed diagram of the components of a locking cap assembly according to an aspect of this technology. [Figure 3C] This is a detailed diagram of a locking latch according to an embodiment of this technology. [Figure 3D] This is a detailed view of a portion of a locking cap assembly in a locked state according to an embodiment of this technology. [Figure 3E] This is a detailed view of a portion of a locking cap assembly in the unlocked state according to an embodiment of this technology. [Figure 3F] This is a perspective view of a portion of a locking cap assembly in the unlocked state according to an aspect of this technology. [Figure 3G] This is a perspective view of a portion of a locking cap assembly in a locked state according to an aspect of this technology. [Figure 3H]This is a perspective view of a portion of a locking cap assembly in a locked state according to an aspect of this technology. [Figure 4A] This figure shows the system architecture of a locking cap assembly according to an embodiment of this technology. [Figure 4B] This figure shows a functional flowchart of a locking cap assembly according to an embodiment of this technology. [Figure 5A] This figure shows a system used to control a locking cap assembly according to an aspect of this technology. [Figure 5B] This figure shows an exemplary method for securing a medicine container according to an aspect of this technology. [Figure 6] This is a conceptual diagram illustrating an exemplary electronic system for controlling a locking cap assembly according to an aspect of this technology. [Modes for carrying out the invention]

[0013] Here, we will discuss the implementation configurations, and examples are shown in the attached drawings. The following description includes numerous specific details to provide an understanding of the various implementation configurations described. However, it will be apparent to those skilled in the art that the various implementation configurations described can be implemented without these specific details. In other cases, well-known methods, procedures, components, circuits, and networks are not described in detail to avoid unnecessarily obscuring the nature of the implementation configurations.

[0014] FIG. 1 shows an example of an in-facility patient care system 100 of a healthcare organization according to an aspect of the present technology. In FIG. 1, a patient care device (or generally a "medical device") 12 is connected to a hospital network 10. The term "patient care device" (or "PCD: patient care device") may be used interchangeably with the term "patient care unit" (or "PCU: patient care unit"), and in either case, it may include various auxiliary medical devices such as an infusion pump, a vital sign monitor, a drug dispensing device (e.g., a cabinet, a tote), a drug preparation device, an automatic dispensing device, a module coupled to one of the foregoing (e.g., a syringe pump module configured to be attached to an infusion pump), or other similar devices. Each patient care device 12 is connected to an internal healthcare network 10 by a transmission channel 31. The transmission channel 31 is any wired or wireless transmission channel, such as an 802.11 wireless local area network (LAN). In some implementations, the network 10 also includes computer systems located in various departments throughout the hospital. For example, the network 10 in FIG. 1 optionally includes an inpatient department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, and / or a computer system associated with a medical decision support system. As will be further described below, the network 10 may include individual sub-networks. In the illustrated example, the network 10 includes a device network 41, and the patient care devices 12 (and other devices) communicate according to normal operation by means of the device network 41.

[0015] In addition, the in-facility patient care system 100 may incorporate a separate information system server 130, the functions of which are described in more detail below. Furthermore, although the information system server 130 is shown as a separate server, the functions and programming of the information system server 130 may be incorporated into a separate computer if desired by the technicians designing the facility's information system. The in-facility patient care system 100 may further include one or more device terminals 132 for connecting to and communicating with the information system server 130. The device terminals 132 may include personal computers, personal data assistants, mobile devices such as laptops, tablet computers, augmented reality devices, or smartphones, configured to have software for communicating with the information system server 130 via the network 10.

[0016] The patient care device 12 comprises a system for providing patient care, such as that described by Eggers et al., which is incorporated herein by reference for that purpose. The patient care device 12 may include or incorporate a pump, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapeutic devices, and other drug delivery devices may be used in accordance with the teachings described herein. In the illustrated example, the patient care device 12 comprises a control module 14, also called an interface unit 14, connected to one or more functional modules 116, 118, 120, 122. The interface unit 14 includes a central processing unit 50 connected to memory, e.g., random access memory (RAM) 58, and one or more interface devices such as a user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices. The interface unit 14 also includes, although not required, a non-volatile main memory unit 56 such as a hard disk drive or non-volatile flash memory for storing software and data, and one or more internal buses 64 for interconnecting the aforementioned elements.

[0017] In various implementations, the user interface device 54 is a touch screen for displaying information to the user and allowing the user to input information by touching a defined area of ​​the screen. Additionally or alternatively, the user interface device 54 may include any means for displaying and inputting information, such as a monitor, printer, keyboard, soft keys, mouse, trackball, and / or light pen. The data input device 60 may be a barcode reader capable of scanning and interpreting data printed in barcode format. Additionally or alternatively, the data input device 60 may be any device for inputting encoded data into a computer, such as a device for reading magnetic strips, an RFID device in which digital data encoded in an RFID (radio-frequency identification) tag or smart label (as defined below) is captured by the reader 60 via radio waves, a PCMCIA smart card, a radio frequency card, a memory stick, a CD, a DVD, or other analog or digital storage medium. Other examples of the data input device 60 include voice-activated or recognition devices, or personal data assistants (PDAs). Depending on the type of interface device used, the user interface device 54 and the data input device 60 may be the same device. Although Figure 1 shows the data input device 60 located within the interface unit 14, it is recognized that the data input device 60 may be integrated into the pharmacy system 34 or located externally and communicate with the pharmacy system 34 via an RS-232 serial interface or any other suitable means of communication. The auxiliary interface 62 may be an RS-232 communication interface, but any other means of communication with peripheral devices such as a printer, patient monitor, infusion pump, or other medical device may be used without departing from this technology.Additionally, the data input device 60 can be made up of separate functional modules such as modules 116, 118, 120, and 122, and may be configured to communicate with the controller 14 or any other system on the network using suitable programming and communication protocols.

[0018] The network connection 52 can be a wired or wireless connection, such as an Ethernet®, WiFi®, BLUETOOTH®, integrated services digital network (ISDN) connection, digital subscriber line (DSL) modem, or cable modem. Any direct or indirect network connection may be used, including, but not limited to, a telephone modem, MIB system, RS232 interface, auxiliary interface, optical link, infrared link, radio frequency link, microwave link, or WLAN connection or other wireless connection.

[0019] The functional modules 116, 118, 120, 122 are any devices for providing care to a patient or monitoring the patient's condition. As shown in FIG. 1, at least one of the functional modules 116, 118, 120, 122 may be an infusion pump module, such as an intravenous infusion pump for delivering a drug or other infusion to a patient. For the purposes of this description, functional module 116 is an infusion pump module. Each of the functional modules 118, 120, and 122 may be any device for patient treatment or monitoring, including, but not limited to, an infusion pump, syringe pump, PCA pump, epidural pump, enteral pump, blood pressure monitor, pulse oximeter, EKG monitor, EEG monitor, heart rate monitor, or intracranial pressure monitor. Functional modules 118, 120, and / or 122 may be a printer, scanner, barcode reader, or any other peripheral input, output, or input / output device.

[0020] Each functional module 116, 118, 120, and 122 communicates directly or indirectly with the interface unit 14, which provides overall monitoring and control of the device 12. The functional modules 116, 118, 120, and 122 may be physically and electronically serially connected to one or both ends of the interface unit 14, as shown in Figure 1 or as detailed in Eggers et al. However, it is recognized that other means may be used to connect the functional modules to the interface unit without departing from the present art. It will also be understood that devices such as pumps or patient monitoring devices that provide sufficient programmability and connectivity can operate as standalone devices and communicate directly with the network without being connected via a separate interface unit or control unit 14. As described above, additional medical devices or peripheral devices may be connected to the patient care device 12 via one or more auxiliary interfaces 62.

[0021] Each functional module 116, 118, 120, and 122 may include module-specific components 76, a microprocessor 70, volatile memory 72, and non-volatile memory 74 for storing information. While four functional modules are shown in Figure 1, it should be noted that any number of devices may be directly or indirectly connected to the controller unit 14. The number and types of functional modules described herein are illustrative and do not limit the scope of the Art. Module-specific components 76 may include any components necessary for the operation of a particular module, such as a pumping mechanism for the injection pump module 116.

[0022] Each functional module may be capable of at least some level of independent operation, while the interface unit 14 monitors and controls the overall operation of the device 12. For example, as will be described in more detail below, the interface unit 14 provides programming instructions to functional modules 116, 118, 120, and 122 and monitors the status of each module. The programming instructions may be based on volume or flow rate detected using at least some of the described functions.

[0023] The patient care device 12 can operate in several different modes or personalities, each personality defined by a configuration database. The configuration database may be an internal database 56 of the patient care device or an external database 37. A particular configuration database is selected based at least in part on patient-specific information such as the patient's location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, the patient's diagnosis, treatment prescriptions, medical history, medical records, identification information of the patient care provider, physiological characteristics, or psychological characteristics. Patient-specific information used herein also includes care provider information (e.g., physician identification information) or the location of the patient care device 10 in the hospital or the hospital's computer network. Patient care information may be entered via interface devices 52, 54, 60, or 62 and may originate from any location in the network 10, such as a pharmacy server, admission server, or laboratory server.

[0024] A medical device incorporating aspects of this technology may be equipped with a Network Interface Module (NIM) to enable the medical device to participate in a network as a node. For clarity, this technology is described as operating within an Ethernet® network environment using the Internet Protocol (IP), but it is understood that the concepts of this technology are equally applicable to other network environments, and that such environments are intended to fall within the scope of this technology.

[0025] Data exchanged between various data sources can be converted into network-compatible data using existing technologies, and the movement of information between medical devices and networks can be realized by various means. For example, the patient care device 12 and the network 10 may communicate via automated interaction, manual interaction, or a combination of both automated and manual interaction. Automated interaction may be continuous or intermittent and may be conducted via a direct network connection 54 (as shown in Figure 1), or via an RS232 link, MIB system, RF link such as Bluetooth, IR link, WLAN, digital cable system, telephone modem, or other wired or wireless means. Manual interaction between the patient care device 12 and the network 10 may include physically transmitting data intermittently or periodically between systems, for example, using a user interface device 54, coded data input device 60, barcodes, computer disks, portable data assistants, memory cards, or any other medium for storing data. Communication methods in various forms are bidirectional communication by accessing data from as many locations as possible within a distributed data source. Decision-making may take place in various locations within the network 10. For example, but not limited to, decisions can be made in the health information server (HIS) 30, decision support 48, remote data server 49, hospital departments or unit stations 46, or within the patient care device 12 itself.

[0026] Direct communication with medical devices operating on a network according to this technology may be performed via an information system server 30 known as a remote data server (RDS). According to an embodiment of this technology, a network interface module incorporated into a medical device, such as an infusion pump or a vital sign measuring device, ignores all network traffic that does not originate from an authenticated RDS. The main role of the RDS in this technology is to track the location and status of all networked medical devices with NIM and to maintain open communication.

[0027] Figure 2A shows an example of a locking cap assembly fixed to a medicine container according to an aspect of the present technology. Figure 2A shows a locking cap assembly 200 that secures a medicine bottle 208. The locking cap assembly 200 includes an upper housing 202, a lower housing 204, and a display 206 positioned on the upper housing 202. The lower housing 204 is rotatably connected to the upper housing and configured to fit onto the medicine bottle 208. The lower housing 204 is positioned between the upper housing 202 and the medicine bottle 208. Electronic and communication components, which will be described in more detail in Figures 3A and 4A, are located within the upper housing 202.

[0028] In various implementations, the locking cap assembly 200 may display and / or store a unique identifier associated with the patient and the medication contained in the medication bottle 208. The unique identifier may be transmitted wirelessly to the locking cap assembly 200 or stored internally by the locking cap assembly 200. The locking cap assembly 200 includes a communication module that allows other devices to read its unique identifier. The communication module may include an NFC module configured to wirelessly receive Near Field Communication (NFC) input. In some implementations, the unique identifier may be read by an NFC module in another device (e.g., a phone, tablet). In some implementations, the locking cap assembly 200 is configured to transmit the unique identifier to a device in close proximity to the locking cap assembly 200, and after the unique identifier has been transmitted to the device and read by the device, it is to be acknowledged by the device in close proximity to the locking cap assembly via an NFC module.

[0029] In some implementations, the display 206 on the locking cap assembly 200 may display an optically scannable indicator (e.g., a 2D barcode) that can be scanned by a device (e.g., a phone, tablet, or handheld optical scanner). When a device is placed near the locking cap assembly 200 (e.g., within 5.08 cm (2 inches) or in contact with it), an NFC reader in the device can read the unique identifier of the locking cap assembly 200. The device may then provide the locking cap assembly 200 with an authorization code specific to the locking cap assembly 200 in order to enable the locking cap assembly 200 to be unlocked. In some implementations, the valid authorization code is transmitted from the device to the locking cap assembly as an encrypted hash code, and the locking cap assembly may store a decryption key that allows a microprocessor on the locking cap assembly to decrypt the valid authorization code.

[0030] In some implementations, the authorization code is provided to the authorized device via an application installed on the device. For example, the authorization code is sent from a cloud server to an application installed on the device. The cloud server may use other methods to authenticate the device user's identity to confirm that the user granted access to the medication in the medication bottle 208 is an authorized user. Scannable indicators displayed on the display 206 may allow the device to identify the medication stored in the medication bottle, even for users who do not have access to the application relaying the authorization code from the cloud server. By scanning the scannable indicators, such users can be directed to the manufacturer of the drug and receive further information such as side effects, recommended dosage, or precautions related to the drug. In case of emergency, contact information for a doctor or caregiver may also be provided to the user.

[0031] The locking cap assembly 200 may be used to lock a single medicine bottle, or it may be used in situations where multiple bottles need to be controlled and monitored, such as in a hospital, school, facility, or clinic.

[0032] Figure 2B shows an example of a locking cap assembly having two different configurations of locking vanes according to an aspect of the present art. Figure 2B shows the locking vanes 210 in two different positions by rotating the upper housing 202 relative to the lower housing 204. The locking cap assembly 200 is placed over the mouth or opening of the medicine bottle 208. By rotating the upper housing 202 clockwise, as indicated by arrow 214, the locking vanes 210 (initially in the retracted position and not engaged with the corresponding protruding lip 212 or locking rim of the medicine bottle 208) may begin to extend and engage with the lip 212. By rotating the upper housing 202 counterclockwise, as indicated by arrow 216, the locking vanes 210 (initially in the extended position and engaged with the corresponding protruding lip 212 of the medicine bottle 208) may begin to retract, thereby allowing the locking cap assembly 200 to be removed from the medicine bottle 208. The locking vane 210 is configured to variably define the inner diameter size of the lower housing 204 in response to the rotation of the upper housing 202 relative to the lower housing 204 when the lower housing 204 is mechanically engaged with the medicine bottle 208. For example, the locking cap assembly 200 is configured to lock the medicine bottle 208 by contracting the locking vane 210 around the medicine bottle 208 in response to the rotation of the upper housing 202 relative to the lower housing 204 in a first direction (e.g., counterclockwise).

[0033] The adjustable locking vanes 210 allow the locking cap assembly 200 to adapt to various bottle sizes with different diameters of openings. This feature enables the locking cap assembly 200 to accommodate multiple different bottle sizes. The locking cap assembly 200 is removed from the medicine bottle 208 by twisting the upper housing 202 relative to the lower housing 204 until the locking vanes 210 are in the retracted position and no longer engage with the protruding lip 212 of the medicine bottle 208.

[0034] Figure 2C shows two different configurations of a locking vane according to an aspect of the present technology. Figure 2C shows the locking vane 210 positioned within the lower housing 204 when the upper housing 202 is removed from the lower housing. The left portion of Figure 2C shows the locking vane 210 in the retracted position. The right portion of Figure 2C shows the locking vane 210 in the extended position. Counterclockwise rotation of the vane positioning ring 218 retracts the locking vane 210. The vane positioning ring 218 is located within the lower housing 204 and is coupled to the locking vane 210 and the upper housing 202. When the vane positioning ring 218 rotates relative to the lower housing 204 together with the upper housing 202, the vane positioning ring 218 extends or retracts the locking vane 210. Clockwise rotation of the vane positioning ring 218 extends the locking vane 210. The vane positioning ring 218 is connected to the upper housing 202 and rotates when the upper housing 202 is twisted. When the upper housing 202 is twisted clockwise, the locking vane 210 closes, and when the upper housing 202 is twisted counterclockwise, the locking vane 210 opens.

[0035] Figure 2D shows a cross-sectional view of the locking cap assembly and medicine bottle shown in Figure 2A, according to an embodiment of the present technology. Figure 2D shows a cross-sectional view of the locking cap assembly 200 and medicine bottle 208. The upper housing 202 is located above the medicine bottle 208 overall (shown as being to the right of the medicine bottle 208 overall in Figure 2D). The lower housing 204 surrounds the neck or mouth area of ​​the medicine bottle 208. The vane positioning ring is located further away from the medicine bottle 208 compared to the locking vane 210 (extending further to the right in Figure 2D). When the locking vane 210 is in the extended position, it engages with the protruding lip 212 of the neck area of ​​the medicine bottle 208, preventing the locking cap assembly 200 from detaching from the medicine bottle 208. When the locking vane 210 is in the retracted position, it is no longer engaged with the protruding lip 212 of the medicine bottle 208, and the locking cap assembly 200 can be removed from the medicine bottle 208. Some medicine containers include a lip at the opening of the container for engaging with a corresponding snap bottle cap. The locking vane 210 may lock onto the lip of such a medicine container. Some medicine containers include threads for engaging with a corresponding spiral cap. The locking vane 210 may also lock onto the threads of such a medicine container. In other words, the locking cap assembly 200 is adapted to work with a variety of existing medicine bottles.

[0036] Figure 3A shows an exploded view of a locking cap assembly according to an embodiment of the present technology. Figure 3A shows exploded views of various components of the locking cap assembly 200. The upper part of the locking cap assembly 200 includes an upper housing cover 220 surrounding the display 206. The circuit board 222 and the near-field communication (NFC) antenna or coil 224 are located behind the upper housing cover. The supercapacitor 226 and the electrically actuated components 228 are housed within the upper housing 202. The vane positioning ring 218 and the locking ring 210 are housed within the lower housing 204.

[0037] Figure 3B shows a detailed view of the components of a locking cap assembly according to an embodiment of the present technology. Figure 3B shows an exploded view of some components of the locking cap assembly 200. Inside the upper housing 202 are an electrically operated component 228, a locking latch 232, a latch position sensor 234, and a latch tension spring 236. The latch position sensor 234 is configured to sense the position of the locking latch 232 and determine whether the locking latch 232 is positioned in a locked (extended) state or an unlocked (retracted) state. The latch tension spring 236 may control the movement of the locking latch 232 between the locked and unlocked states. The locking latch 232 is configured to prevent the upper housing 202 and the lower housing 204 from rotating relative to each other. The electrically operated component 228 is configured to lock and unlock the locking latch 232 in response to signals received from the microprocessor of the locking cap assembly and the current generated by the inductive charging coil of the locking cap assembly.

[0038] The lower housing 204 contains a locking vane 210 and a number of latch locking slots 230. The latch locking slots 230 are arranged at regular intervals, and each latch locking slot has a width that allows the slot to receive a locking latch 232 and hold the locking latch 232 in the engaged position in a locked (extended) state. When one of the latch locking slots 230 engages with the locking latch 232, rotation between the upper housing 202 and the lower housing 204 is prevented, and the retraction of the locking vane 210 is prevented.

[0039] Figure 3C shows a detailed view of a locking latch according to an embodiment of the present technology. Figure 3C shows a detailed view of the locking latch 232 when the latch tension spring 236 is loaded. In some implementations, the spring 236 is loaded when it is compressed. When unlocked, the locking latch 232 is free to retract, allowing the locking cap assembly 200 to rotate so that the medicine bottle 208 can be opened (for example, the upper housing 202 can be twisted or rotated relative to the lower housing 204). When locked, the locking latch 232 is prevented from retracting, preventing the locking cap assembly 200 from rotating (for example, the upper housing 202 is locked relative to the lower housing 204 so that rotation is prevented), and the locking vanes are locked in place so that the medicine bottle 208 cannot be opened.

[0040] Figure 3D shows a detail view of a portion of a locking cap assembly in the locked state according to an embodiment of the art. Figure 3D shows a detail view of the locking cap assembly 200 in the locked state. In the locked state, the lock 238 extends, preventing the locking latch 232 from retracting and preventing the locking cap assembly 200 from rotating. The lock 238 extends as it moves to the right in the drawing, further away from the electrically actuated component 228. The electrically actuated component 228 acts on the lock 238, moving it from left (unlocked state, lock 238 positioned close to the electrically actuated component 228) to right (locked state, lock 238 positioned far from the electrically actuated component 228). In some implementations, the electrically actuated component 228 includes a lock motor. In some implementations, the electrically actuated component 288 includes a solenoid. In some implementations, the electrically actuated component 228 does not rotate. For example, the electrically operated component 228 may be a linear actuator that retracts the locking mechanism.

[0041] When lock 238 is engaged, the locking cap assembly 200 cannot be removed from the medicine bottle 208. In the locked state, the latch tension spring 236 extends, and the locking latch 232 extends / protrudes into the latch locking slot 230 and is held within the latch locking slot 230.

[0042] Figure 3E shows a detail view of a portion of the locking cap assembly in the unlocked state according to an embodiment of the present technology. Figure 3E shows a detail view of the locking cap assembly 200 in the unlocked state. In the unlocked state, the lock 238 retracts (moves to the left in the drawing and approaches the electrically actuated component 228), and the locking latch 232 retracts freely. When the locking latch 232 retracts, the locking cap assembly 200 can rotate to retract the locking vane 210, allowing the locking cap assembly 200 to be removed from the medicine bottle 208. In the locked state shown in Figure 3D, the latch position flag 240 blocks the signal from the latch position sensor 234, indicating that the mechanism is locked. In the unlocked state, the latch position flag 240 no longer blocks the latch position sensor 234, indicating that the locking cap assembly 200 is unlocked.

[0043] Figure 3F shows a perspective view of a portion of a locking cap assembly in the unlocked state according to an embodiment of the present technology. Figure 3F shows a detailed perspective view of the unlocked state. The lock 238 is retracted and the latch position flag 240 is separated from the latch position sensor 234. The locking latch 232 is also retracted and not engaged in the latch locking slot 230. Each pair of latch locking slots 230 is separated by a latch locking projection 242. In the unlocked state, the latch locking projection 242 can push the locking latch 232 and compress the latch tension spring 236.

[0044] Figure 3G shows a perspective view of a portion of a locking cap assembly in the locked state according to an aspect of the present technology. Figure 3G shows a detailed cross-sectional perspective view of the locked state. The locking latch 236 is in the extended position and engaged within the latch locking slot 230. The latch tension spring 236 extends in the locked state. The latch position flag 240 is located below the latch position sensor 234 and blocks the signal between the upper part 243 and the lower part 244 of the latch position sensor 234. The blockage of the signal indicates that the mechanism is locked.

[0045] Figure 3H shows a perspective view of a portion of a locking cap assembly in the locked state according to an embodiment of the art. Figure 3H shows a detailed cross-sectional perspective view of the locked state. The electrically actuated component 228 has not fully retracted the lock 238, and a portion 246 of the lock 238 remains in contact with the latch position flag 240, preventing the latch 232 from retracting. In some implementations, the lock 238 includes a set of teeth that engage with the corresponding portion of the electrically actuated component 228 to actuate the lock 238.

[0046] In some implementations, the electrically actuated component is coupled to a vane positioning ring or lower housing 204 and is configured to cause a motor-driven rotation of the upper housing 202 relative to the lower housing 204 in response to a signal received from a microprocessor, thereby locking or unlocking the locking cap assembly 200 on the medicine bottle 208. Such implementations may use a larger motor and more power to actuate or cause the rotation. In addition, a separate lock may be provided to prevent the larger motor connected to the cap of the locking cap assembly from rotating. The size of the cap of the locking cap assembly may be increased, and more power may be used in addition to the power provided by the NFC coil.

[0047] In some implementations, the locking cap assembly may include a solenoid for disengaging the lock.

[0048] Figure 4A shows the system architecture of a locking cap assembly according to an aspect of the present technology. Figure 4A shows the system architecture 400 of the hardware components of the locking cap assembly 200. A microprocessor 408 located on a circuit board 222 controls various components of the locking cap assembly 200. The microprocessor 408, having associated firmware 410, controls a display 206, a power management system 402, an NFC reader 406, output devices 414 such as a buzzer, and a Bluetooth communication module 412. The output devices 414 may emit human-recognizable outputs such as sound or vibration. The microprocessor 408 also controls a latch-locking mechanism 416, which includes a latch position sensor 234, a MOSFET driver and isolation system 418, and an electrically operated component 228.

[0049] The power management system 402 controls charging by one or more energy sources, namely the battery 404, the supercapacitor 226, and the inductive charging coil 224. The battery 404 can provide a higher energy density for storage, and the supercapacitor 226 can have a faster charge / discharge capability. The potential energy in the supercapacitor 226 may be stored in an electric field, while the battery 404 may store its potential energy in a chemical form.

[0050] In some implementations, the locking cap assembly 200 includes either (i) a battery 404, or (ii) a supercapacitor 226 and an inductive charging coil 224. In some implementations, the primary coil of a charging device (e.g., a mobile phone) induces a current in the NFC coil 224 of the locking cap assembly 200, thereby reverse wireless charging the locking cap assembly 200. Reverse wireless charging may be performed by placing the mobile phone and the locking cap assembly 200 together in close proximity. The NFC circuitry within the container may be configured to perform energy extraction to capture the NFC signal transmitted by the charging device, or it may utilize NFC-specific energy transfer to receive and / or transmit energy. Alternatively, energy may be received and / or transmitted using the Qi standard or a similar standard, which utilizes the reverse charging capability that allows a device (e.g., a telephone) to wirelessly power an accessory.

[0051] The energy transferred to the locking cap assembly 200 by the charging device over a short period (e.g., the time it takes to request access) is typically in the range of several hundred milliwatts. In this regard, the locking cap assembly 200 may be configured to draw energy from the charging device to operate a motor or actuator. The locking cap assembly 200 may include a small energy storage device (e.g., inside the cap) such as a battery or supercapacitor to enable storage of the drawn power and smooth power transfer over time. In some implementations, the locking cap assembly 200 may be configured to operate in standby mode until it receives a command to open from the charging device or another NFC device, in order to conserve energy. In standby mode, resource-consuming functions may be disabled or operated at low power.

[0052] The NFC coil 224 may also transmit or receive communication signals, which are transmitted to the NFC reader 406 for decoding. The communication signals may provide information for display on the display 206, or provide the lock status of the locking cap assembly 200 (e.g., whether the locking cap assembly 200 is locked or unlocked). The NFC reader 406 may relay the information to the microprocessor 408. If the microprocessor 408 determines that the locking cap assembly 200 is expected to be locked (based on the information received from the NFC coil 224), but is actually unlocked (based on the information from the latch position sensor 234), the microprocessor may transmit a control signal to trigger an alarm by activating the output device 414. Similar alerts regarding the locking status of the locking cap assembly 200 may also be transmitted and received using the BLE module 412. In addition to receiving sensor signals from the latch position sensor 234, the microprocessor 408 also controls the latch locking mechanism 416 via a MOSFET driver and isolation system 418. The isolation system 418 transmits control signals to drive the electrically actuated components 228.

[0053] In some implementations, the BLE module 412 can monitor whether a medicine bottle secured by the locking cap assembly 200 has moved from a particular location. The BLE module enables the locking cap assembly 200 to communicate with other BLE-enabled devices in its vicinity to indirectly provide location information about the locking cap assembly. Thus, the locking cap assembly 200 may additionally support a "Find My Container" function that allows a user to communicate with the locking cap assembly 200 via the BLE module. The locking cap assembly 200 may further include electronic equipment that enables an alarm to sound when activated by the "Find My Container" function. Alternatively or additionally, the BLE module 412 can communicate with a user device (e.g., a mobile phone) and provide the user device with location information about the locking cap assembly 200.

[0054] Figure 4B shows a functional flowchart of a locking cap assembly according to an embodiment of the present technology. Figure 4B shows a functional flowchart of the locking cap 420. The process begins with an NFC-capable telephone being placed near the locking cap assembly 200 (422). The locking cap assembly 200 receives an ID code or access code from the telephone via NFC communication (424).

[0055] The microprocessor 408 determines whether the ID code represents a valid access code (426). If the ID code is determined to be invalid, the display 206 displays an error message (428). For example, the display 206 may display the error message "Invalid code - authorization required to open". If the ID code is determined to be valid, the display 206 displays a confirmation message (430). For example, the display 206 may display the confirmation message "Valid code".

[0056] The microprocessor 408 determines whether it is time for the next dose of the medication (432). In accordance with the determination that it is not yet time for the next dose of the medication, the display 206 displays an error message (434). For example, the display 206 may display the error message "It is not yet time for the next dose." Such a function helps patients who may need assistance in safely self-administering medication by preventing accidental overdoses caused by the patient taking an additional dose prematurely. For example, the patient does not need to remember the exact time the last dose was taken and / or calculate when the next dose is scheduled. In accordance with the determination that it is time for the next dose, the locking cap assembly 200 is unlocked (436). Upon unlocking the locking cap assembly 200, the lock position sensor 234 detects that the locking cap assembly 200 has been released (438). After the locking cap assembly 200 has been released, the medication may be removed by the patient (440).

[0057] After the medication is removed, the cap may be returned to its original position and latched. The locking cap assembly 200 communicates with the telephone via NFC communication, and the telephone relays information to the caregiver confirming that the medication has been administered (442). Status information may also be sent to a cloud server via the phone app (446), and the time is reset locally (by the microprocessor 408) for the next dose (444). The microprocessor 408 calculates the time (T) corresponding to the remaining time until the next dose (448).

[0058] The microprocessor 408 determines whether T has decreased to zero, indicating that it is time for the next dose (450). Following the determination that it is not yet time for the next dose of the drug, the system simply loops through the function flowchart again. Following the determination that it is time for the next dose (i.e., T=0), the microprocessor 408 causes an alert message to be displayed on the display 206. For example, the alert message may read "It is time for the next dose." The microprocessor 408 may also trigger an output device 414 to notify the patient and / or caregiver that it is time for the next dose. The microprocessor 408 may also cause an alert to be sent to a telephone via the BLE module 412. After the alert has been sent, the process loops when the telephone is placed near the locking cap assembly 200 (422).

[0059] As used herein, “cap” may refer to a lid, cover, or other releaseable (e.g., lockable and unlockable) element that secures the opening of a container such as a bottle, tray, or jar. In some implementations, the lock vane or other actuarial locking element is described as being fixed “around the container.” In some implementations, the vane or other actuarial locking element may be fixed to a part of the container, such as a support or other projection attached to the container.

[0060] Figure 5A shows a system used to control a locking cap assembly according to an aspect of this technology. Figure 5A also shows a system 500 that enables portability of access to medication. Access to medication may be transferred by transferring an access code key to a designated caregiver. Relevant information and logs of medication administration (time and dose administered) may be stored on a cloud server and accessed via a telephone or other device.

[0061] System 500 includes a cloud server 502 that communicates data with a telephone 504. Data communication may be established using a WiFi signal. The telephone 504 is located near a locking cap assembly 200 that secures a medicine bottle 208. A physician or pharmacist using terminal 506 may establish a data connection to the cloud server 502, allowing terminal 506 to access and / or edit the patient's electronic health record (EHR).

[0062] The physician may send prescription data to the cloud server 502. The telephone 504 may provide information to log access to the medicine bottle 208 and the medication (e.g., tablets) taken from the medicine bottle 208. The telephone 504 may provide information to the cloud server 502, for example, according to step 446 of the exemplary flowchart 420. In some implementations, an application on the telephone coordinates (i) the exchange of information between the cloud server 502 and the telephone, and (ii) the communication between the telephone and the locking cap assembly. An application that controls unlocking may be maintained within the cloud server 502 and may be able to provide access keys (e.g., authorization codes) to the telephones of different authorized users. In such cases, the medicine container can be carried by the patient, and control or reminders are communicated to one or more caregivers. For example, the access key may be communicated to different caregivers in different locations who are responsible for caring for an immobile person being transported to different locations. Children may bring their medication to school, and an access key may be provided to the school nurse so that the nurse can administer the medication to the child. The cloud server 502 can maintain data logs regarding when the medication was administered, the identification of the person who administered the medication, and the remaining time until the next dose of the medication is administered. An application on the phone enables the exchange of information between the phone and the cloud server 502.

[0063] In some implementations, the user of telephone 504 is a patient with a prescription for medication contained in medicine bottle 208. The cloud server 502 may deliver a reminder message to telephone 504 to remind the patient to take the next dose of medication. In some implementations, the user of telephone 504 is a caregiver. The cloud server 502 may deliver a reminder message to telephone 504 to remind the caregiver to administer medication to the patient. In some implementations, the reminder sent to telephone 504 by the cloud server 502 may trigger a charging window, during which the locking cap assembly 200 may receive wireless power transmission in addition to receiving a communication signal from telephone 504 to unlock the locking cap assembly 200.

[0064] A first additional device 508 (e.g., a telephone) of a first caregiver at a first location may also be data-connected to the cloud server 502. A second additional device 510 (e.g., a telephone) of a second caregiver at a second location may also be data-connected to the cloud server 502. A third additional device 512 (e.g., a telephone) of a third caregiver at a third location may also be data-connected to the cloud server 502.

[0065] In some implementations, the first, second, and third locations are all the same location (e.g., a hospital). The first caregiver, second caregiver, and third caregiver may be nurses working different shifts. The cloud server 502 is configured to send an access code key to each nurse at the start of the nurses' shift, granting access to authorized users. After administering medication, one or more of the devices 508, 510, and 512 may provide information to log access to the medication bottle 208 and the medication (e.g., tablets) taken from the medication bottle 208. The devices 508, 510, and 512 may provide information to the cloud server 502, for example, according to step 446 of the exemplary flowchart 420.

[0066] Figure 5B shows an exemplary method for securing a drug container according to an aspect of the present technology. The locking cap assembly receives an authorization code wirelessly transmitted via the communication channel of the NFC module from a device placed near the locking assembly using a Near Field Communication (NFC) module (522). The microprocessor of the locking cap assembly determines whether the authorization is a valid authorization code. The microprocessor is configured to receive an NFC input from the NFC module and, in response to the microprocessor determining that the NFC input received by the NFC module corresponds to authorization to release the locking cap assembly 200 from the drug bottle 208, unlock the locking latch 232, allowing the upper housing 202 to rotate in a second direction relative to the lower housing 204, retracting the multiple locking vanes and releasing the lower housing 204 from the drug bottle 208.

[0067] In accordance with the determination that the authorization code is a valid authorization code, it is determined whether the current time is within the drug administration time interval (524). In accordance with the determination that the current time is within the drug administration time interval, if the input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, the locking latch of the locking cap assembly is released to allow the multiple locking vanes of the locking cap assembly to retract (526).

[0068] In some implementations, the first, second, and third locations are in different places. For example, the first, second, and third caregivers may be members of the patient's extended family and may reside in different locations. If the patient fails to take their medication, one or more of the first, second, and third caregivers may be notified by the cloud server 502 and can go to the patient's location to help administer the medication.

[0069] In some implementations, the locking cap assembly includes an upper housing, a lower housing rotatably connected to the upper housing and configured to mate into a container, an NFC module configured to wirelessly receive Near Field Communication (NFC) inputs, an inductive charging coil, a microprocessor, and a latching mechanism. The latching mechanism includes a locking latch configured to prevent the upper and lower housings from rotating relative to each other, and an electrically actuated component configured to lock and unlock the latch in response to signals received from the microprocessor and currents generated by the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, which are configured to variably define the inner diameter size of the lower housing in response to the rotation of the upper housing relative to the lower housing when the lower housing is mechanically engaged with the container. The locking cap assembly is configured to lock the container by retracting the plurality of vanes around the container in response to the rotation of the upper housing relative to the lower housing in a first direction. The microprocessor is configured to receive an NFC input from the NFC module and, in response to the microprocessor determining that the NFC input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, unlock the locking latch, allow the upper housing to rotate in a second direction relative to the lower housing, retract the multiple locking vanes, and release the lower housing from the container.

[0070] In some implementations, the locking cap assembly further includes a vane positioning ring in the lower housing, which is coupled to a plurality of locking vanes and the upper housing. When the vane positioning ring rotates relative to the lower housing together with the upper housing, the vane positioning ring extends or retracts the plurality of locking vanes. In some implementations, the locking cap assembly further includes a plurality of locking slots positioned within the lower housing. A locking latch is configured to engage with one of the plurality of locking slots from the upper housing.

[0071] In some implementations, a display is located within the upper housing and is configured to show a unique identifier associated with the medication in the container and the recipient of the medication. The locking cap assembly is configured to transmit the unique identifier to a device adjacent to it, and after the unique identifier is transmitted to and read by the device, it is authorized by the device adjacent to the locking cap assembly via an NFC module.

[0072] In some implementations, the locking cap assembly further includes electrical components for receiving wireless power charges from the device and supplying power to the electrically operated components of the locking cap assembly. The lower housing is positioned between the upper housing and the container.

[0073] In some implementations, the electrically operated component is coupled to a vane positioning ring and is configured to cause a motor-driven rotation of the upper housing relative to the lower housing in response to a signal received from a microprocessor, thereby locking or unlocking the locking cap assembly on the container.

[0074] In some implementations, the locking cap assembly further includes an optical sensor configured to determine the position of the locking latch and thus determine the locking state of the locking cap assembly.

[0075] In some implementations, the locking cap assembly further includes an output device (e.g., inside the cap) such as a buzzer, configured to emit a human-recognizable output (e.g., voice, sound, vibration) at a predetermined time prior to the scheduled administration of the drug in the container. An NFC module is configured to communicate information to a data network in response to a determination that the locking cap assembly is unlocked from the container.

[0076] In some implementations, the method for securing a drug container includes the step of receiving an authorization code wirelessly transmitted via the communication channel of a device placed near the locking cap assembly by a Near Field Communication (NFC) module in the locking cap assembly. According to the determination that the authorization code is a valid authorization code, it is determined whether the current time is within the drug administration time interval. According to the determination that the current time is within the drug administration time interval, if the input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, the locking latch of the locking cap assembly is released, allowing the multiple locking vanes of the locking cap assembly to retract. The multiple locking vanes variably define the size of the central opening, and the multiple locking vanes are configured to mechanically engage with the drug container in the locked state of the locking cap assembly. Power to release the locking latch is provided by wireless energy transfer from the device to the motor of the locking cap assembly via the communication channel.

[0077] In some implementations, the method further includes the step of receiving an authorization code transmitted by the device after the device has read a unique identifier associated with the locking cap assembly using the device's NFC module.

[0078] In some implementations, the method further includes the step of storing approval information for unlocking a drug container in a data network, such that the drug container is configured to be unlocked by multiple approved mobile devices that retrieve the approval information via the data network.

[0079] In some implementations, the method involves the device being a mobile phone, a valid authorization code being sent from the mobile phone as a cryptographic hash code to a locking cap assembly, and the locking cap assembly containing a decryption key for decrypting the valid authorization code.

[0080] In some implementations, the method further includes the steps of transmitting data to a data network via an NFC module in the locking cap assembly after the drug container has been unlocked, and maintaining a record in the data network of when the drug in the drug container was administered.

[0081] In some implementations, the method further includes the step of sounding an alarm in the locking cap assembly at a predetermined time prior to the scheduled subsequent administration of the drug in the drug container.

[0082] In some implementations, the method further includes the step of updating a display on the locking cap assembly after the drug container is unlocked in order to provide dosage or other information regarding the drug in the drug container. In some implementations, the method further includes the step of transmitting an access code for releasing the locking cap assembly from a first approved mobile device to a second approved mobile device. Figure 6 is a conceptual diagram showing an exemplary electronic system for controlling the locking cap assembly according to an aspect of the present technology. The electronic system 600 may include, but is not limited to, one or more parts or steps of the process or computing devices for executing components and process-related software provided in Figures 1 to 5B, including the server 130, computing hardware in the patient care device 12, or the terminal device 132. The electronic system 600 may be representative in combination with the present disclosure relating to Figures 1 to 5B. In this regard, the electronic system 600 may be a personal computer, or a mobile device such as a smartphone, tablet computer, laptop, PDA, augmented reality device, watch or band or glasses or other wearable device, or a combination thereof, or another touch screen or television incorporating or combined with one or more processors, or any other type of computer-related electronic device with network connectivity.

[0083] The electronic system 600 may include various types of computer-readable media and interfaces for various other types of computer-readable media. In the illustrated example, the electronic system 600 includes a bus 608, a processing unit 612, system memory 604, read-only memory (ROM) 610, persistent storage device 602, input device interface 614, output device interface 606, and one or more network interfaces 616. In some implementations, the electronic system 600 may include or be integrated with other computing devices or circuits for the operation of the various components and processes described above.

[0084] Bus 608 collectively represents all system buses, peripheral buses, and chipset buses that communicate with numerous internal devices of the electronic system 600. For example, bus 608 communicates with the processing unit 612, the ROM 610, the system memory 604, and the persistent storage device 602.

[0085] From these various memory units, the processing unit 612 retrieves instructions to be executed and data to be processed in order to carry out the process of this disclosure. In different implementations, the processing unit may be a single processor or a multi-core processor.

[0086] ROM 610 stores static data and instructions required by processing unit 612 and other modules of the electronic system. On the other hand, persistent storage device 602 is a read / write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 600 is off. Some implementations of this disclosure use a mass storage device (such as a magnetic disk or optical disk and its corresponding disk drive) as persistent storage device 602.

[0087] Other implementations use a removable storage device (such as a floppy disk, flash drive, and corresponding disk drive) as the persistent storage device 602. Similar to the persistent storage device 602, the system memory 604 is a read-write memory device. However, unlike the storage device 602, the system memory 604 is volatile read-write memory, such as random-access memory. The system memory 604 stores some of the instructions and data required by the processor at runtime. In some implementations, the process of this disclosure is stored in the system memory 604, the persistent storage device 602, and / or the ROM 610. From these various memory units, the processing unit 612 retrieves the instructions to be executed and the data to be processed in order to execute the process in some implementations.

[0088] Bus 608 also connects to an input device interface 614 and an output device interface 606. The input device interface 614 allows the user to communicate information and selected commands to the electronic system. Input devices used with the input device interface 614 include, for example, an alphanumeric keyboard and a pointing device (also called a "cursor control device"). The output device interface 606 allows, for example, the display of images generated by the electronic system 600. Output devices used with the output device interface 606 include, for example, a printer and a display device such as a cathode ray tube (CRT) or a liquid crystal display (LCD). Some implementations include devices such as touch screens that function as both input and output devices.

[0089] Furthermore, as shown in Figure 6, bus 608 also connects the electronic system 600 to a network (not shown) via a network interface 616. The network interface 616 may include, for example, a wireless access point (e.g., Bluetooth or WiFi) or a wireless circuit for connecting to a wireless access point (e.g., a transceiver, antenna, amplifier). The network interface 616 may also include hardware (e.g., Ethernet® hardware) for connecting a computer to a network of computers such as a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN, a personal area network ("PAN"), or an intranet, or a network of networks such as the Internet. Any or all components of the electronic system 600 can be used in conjunction with this disclosure.

[0090] These functions described above may be implemented in computer software, firmware, or hardware. The technique can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. Processes and logic flows can be executed by one or more programmable processors and one or more programmable logic circuits. General-purpose and dedicated computing and storage devices specifically configured for the described injection functions can be interconnected via a communication network.

[0091] Some implementations involve electronic components such as microprocessors, storage, and memory that store computer program instructions in machine-readable or computer-readable media (also called computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and / or solid-state hard drives, read-only and recordable Blu-ray® discs, ultra-high-density optical discs, and any other optical or magnetic media. Computer-readable media can store computer programs that are executable by at least one processing unit and contain instruction sets for performing various operations. Examples of computer programs or computer code include machine code, such as that generated by a compiler, and files containing high-level code that is executed by a computer, electronic component, or microprocessor using an interpreter.

[0092] The above description primarily refers to microprocessors or multicore processors that run software, but some implementations are performed by one or more integrated circuits, such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions stored within the circuit itself.

[0093] As used herein and in any of the claims, the terms “computer,” “server,” “processor,” and “memory” all refer to electronic devices or other technological devices. These terms exclude persons or groups of persons. For the purposes of this specification, the terms “display” or “displaying” mean displaying on an electronic device. As used herein and in any of the claims, the terms “computer-readable medium” and “computer-readable media” are strictly limited to tangible physical objects that store information in a format readable by a computer. These terms exclude wireless signals, wired download signals, and any other transient signals.

[0094] To provide user interaction, the implementations of the subject matter described herein may be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, and a keyboard and pointing device, such as a mouse or trackball, on which the user can provide input to the computer. Other types of devices may also be used to provide user interaction; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, and input from the user may be received in any form, including acoustic input, voice input, or tactile input. Furthermore, the computer may interact with the user by sending and receiving documents to and from devices used by the user, for example, by sending a web page to a web browser on the user's client device in response to a request received from a web browser.

[0095] The embodiments of the subject matter described herein may be implemented in a specially configured computing system that includes back-end components, such as a data server, or middleware components, such as an application server, or front-end components, such as a client computer having a graphical user interface or a web browser on which a user can interact with the implementation of the subject matter described herein, or any combination of one or more such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad-hoc peer-to-peer networks).

[0096] A computing system can include clients and servers. Clients and servers are generally geographically separated and may interact via a communication network. The client-server relationship arises from computer programs running on each computer that have a client-server relationship with each other. In some implementations, the server sends data (e.g., an HTML page) to the client device (for example, to display data to a user interacting with the client device and to receive user input from that user). Data generated on the client device (e.g., the results of user interaction) can be received by the server from the client device.

[0097] Those skilled in the art will understand that the various exemplary blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or a combination of both. To illustrate this compatibility between hardware and software, various exemplary blocks, modules, elements, components, methods, and algorithms have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. The described functionality may be implemented in various ways for each specific application. Without departing entirely from the scope of this art, various components and blocks may be configured differently (for example, they may be configured in different orders or divided in different ways).

[0098] It should be understood that the specific order or hierarchy of steps in the disclosed process is illustrative and describes an exemplary method. It should be understood that the specific order or hierarchy of steps in the process may be reconfigured based on design preferences. Some of the steps may be performed simultaneously. The attached method claims present elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0099] Examples of clauses in this technology: Various examples of the embodiments of this disclosure are described for convenience as numbered clauses (1, 2, 3, etc.). These are provided as examples and do not limit the technology. The identification of figures and reference numbers is provided below for illustrative purposes only and as examples, and the clauses are not limited by their identification.

[0100] Clause 1 The locking cap assembly includes an upper housing, a lower housing rotatably connected to the upper housing and configured to fit into a container, an NFC module configured to wirelessly receive near-field communication (NFC) inputs, an inductive charging coil, a microprocessor, and a latching mechanism comprising a locking latch configured to prevent the upper and lower housings from rotating relative to each other, and an electrically actuated component configured to lock and unlock the latch in response to signals received from the microprocessor and currents generated by the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, the locking vanes configured to variably define the inner diameter size of the lower housing in response to the rotation of the upper housing relative to the lower housing when the lower housing is mechanically engaged with the container. The locking cap assembly is configured to lock the container by retracting a plurality of vanes around the container in response to a first-direction rotation of the upper housing relative to the lower housing, and the microprocessor is configured to receive an NFC input from the NFC module and, in response to the microprocessor determining that the NFC input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, unlock the locking latch, allowing a second-direction rotation of the upper housing relative to the lower housing, thereby retracting the plurality of locking vanes and releasing the lower housing from the container.

[0101] The locking cap assembly according to Clause 2, further comprising a vane positioning ring in a lower housing, wherein the vane positioning ring is coupled to a plurality of locking vanes and an upper housing, and when the vane positioning ring rotates relative to the lower housing together with the upper housing, the vane positioning ring extends or retracts the plurality of locking vanes.

[0102] Clause 3: The locking cap assembly according to Clause 2, further comprising a plurality of locking slots located within the lower housing, wherein a locking latch is configured to engage with one of the plurality of locking slots from the upper housing.

[0103] Clause 4 The locking cap assembly according to Clause 2, further comprising a display located within the upper housing, wherein the display is configured to display a unique identifier associated with the drug in the container and the recipient of the drug.

[0104] Clause 5 The locking cap assembly as described in Clause 4, configured to transmit a unique identifier to a device adjacent to the locking cap assembly, and to receive authorization from the device adjacent to the locking cap assembly via an NFC module after the unique identifier has been transmitted to and read by the device.

[0105] Clause 6: The locking cap assembly as described in Clause 5, further comprising an electrical component for receiving wireless power charge from a device and supplying power to the electrically actuated components of the locking cap assembly.

[0106] Clause 7: The locking cap assembly described in Clause 2, wherein the lower housing is positioned between the upper housing and the container.

[0107] Clause 8: The locking cap assembly according to Clause 7, wherein an electrically actuated component is coupled to a vane positioning ring and configured to cause a motor-driven rotation of the upper housing relative to the lower housing in response to a signal received from a microprocessor, thereby locking or unlocking the locking cap assembly on the container.

[0108] Clause 9 A locking cap assembly according to any one of Clauses 1 to 8, further comprising an optical sensor configured to determine the position of the locking latch and to determine the locking state of the locking cap assembly.

[0109] Clause 10 A locking cap assembly according to any one of Clauses 1 to 9, further comprising a buzzer configured to emit a human-recognizable output at a predetermined time prior to the scheduled administration of the drug contained in the container.

[0110] Clause 11 The locking cap assembly described in Clause 10, wherein the human-perceivable output is at least one of sound or vibration.

[0111] Clause 12 A locking cap assembly as described in any one of Clauses 1 to 10, wherein the NFC module is configured to communicate information to a data network in response to a determination that the locking cap assembly is unlocked from its container.

[0112] Clause 13 A method for securing a drug container, comprising: receiving an authorization code wirelessly transmitted via a communication channel of a Near Field Communication (NFC) module in a locking cap assembly from a device placed near the locking cap assembly; determining, according to the determination that the authorization code is a valid authorization code, whether the current time is within a drug administration time interval; and, according to the determination that the current time is within a drug administration time interval, releasing the locking latch of the locking cap assembly so that a plurality of locking vanes of the locking cap assembly can retract, wherein the plurality of locking vanes variably define the size of the central opening, and the plurality of locking vanes are configured to mechanically engage with the drug container in the locked state of the locking cap assembly, and power for releasing the locking latch is provided by wireless energy transmission from a device via a communication channel to a motor of the locking cap assembly.

[0113] The method of Clause 13, further comprising the step of receiving an authorization code transmitted by the device after the device has read a unique identifier associated with the locking cap assembly using the device's NFC module.

[0114] The method according to Clause 15, further comprising the step of storing approval information for unlocking a drug container in a data network, such that the drug container is configured to be unlocked by multiple approved mobile devices that obtain approval information via a data network.

[0115] Clause 16 The method described in any one of Clauses 13 to 15, wherein the device includes a mobile phone, a valid authorization code is transmitted from the mobile phone to a locking cap assembly as a cryptographic hash code, and the locking cap assembly includes a decryption key for decrypting the valid authorization code.

[0116] Clause 17 The method of any one of Clauses 13 to 16, further comprising the steps of transmitting data to a data network via the NFC module of the locking cap assembly after the drug container has been unlocked, and maintaining a record in the data network regarding when the drug in the drug container was administered.

[0117] Clause 18 The method according to any one of Clauses 13 to 17, further comprising the step of sounding an alarm in the locking cap assembly at a predetermined time prior to the scheduled subsequent administration of the drug in the drug container.

[0118] Clause 19 The method of any one of Clauses 13 to 18, further comprising the step of updating the markings on the locking cap assembly after the drug container has been unlocked in order to provide dosage or other information relating to the drug in the drug container.

[0119] The method described in any one of the clauses 13 to 19, further comprising the step of transmitting an access code for releasing a locking cap assembly from a first approved mobile device to a second approved mobile device.

[0120] Further considerations: It should be understood that the specific order or hierarchy of steps in the disclosed process is illustrative and describes an exemplary method. It should be understood that the specific order or hierarchy of steps in the process may be reconfigured based on design preferences. Some of the steps may be performed simultaneously. The attached method claims present elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0121] The foregoing description is provided to enable those skilled in the art to practice the various embodiments described herein. The foregoing description provides various examples of the Art, and the Art is not limited to these examples. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may apply to other embodiments. Accordingly, the claims are not intended to be limited to the embodiments shown herein, but should be given an entire scope consistent with the claims in wording, and singular references to elements are not intended to mean "only" but rather "one or more" unless otherwise specified. Unless otherwise specified, the term "several" refers to one or more. Masculine pronouns (e.g., his) include feminine and neuter forms (e.g., her and its), and vice versa. Where headings and subheadings exist, they are used for convenience only and do not limit the inventions described herein.

[0122] As used herein, the term "website" may include any aspect of a website, including one or more web pages, one or more servers used to host or store web-related content, etc. Therefore, the term "website" may be used interchangeably with the terms "web page" and "server." The predicates "configured to," "operable to," and "programmed to" are not intended to imply any specific tangible or intangible modification of the subject, but rather to be interchangeable. For example, a processor configured to monitor and control operations or components may also mean that the processor is programmed to monitor and control operations, or that the processor is operable to monitor and control operations. Similarly, a processor configured to execute code may be interpreted as a processor programmed to execute code or operable to execute code.

[0123] As used herein, the term "automatic" may include performance by a computer or machine without user intervention, for example, by instructions in response to a predicate action by a computer or machine or other initiation mechanism. The word "example" is used herein to mean "to serve as an example or illustration." Any embodiment or design described herein as an "example" should not necessarily be construed as being preferable or advantageous to other embodiments or designs.

[0124] The terms "aspects" and similar phrases do not imply that such aspects are essential to the Technology, nor that such aspects apply to all configurations of the Technology. Disclosures relating to aspects may apply to all configurations or one or more configurations. Aspects may provide one or more examples. The terms "aspects" and similar phrases may refer to one or more aspects, and vice versa. The terms "examples" and similar phrases do not imply that such examples are essential to the Technology, nor that such examples apply to all configurations of the Technology. Disclosures relating to examples may apply to all implementations or one or more implementations. Examples may provide one or more examples. The terms "examples" and similar phrases may refer to one or more examples, and vice versa. The terms "configuration" and similar phrases do not imply that such configurations are essential to the Technology, nor that such configurations apply to all configurations of the Technology. Disclosures relating to configurations may apply to all configurations or one or more configurations. Configurations may provide one or more examples. The term "composition" can refer to one or more compositions, and vice versa.

[0125] As used herein, the terms “determine” or “decide” encompass a wide variety of actions. For example, “decide” may include, without user intervention, computing, processing, deriving, generating, obtaining, retrieving (e.g., searching within a table, database, or other data structure), confirming, etc., via hardware elements. Also, “decide” may include, without user intervention, receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. “Determine” may include, without user intervention, resolving, selecting, choosing, establishing, etc., via hardware elements.

[0126] As used herein, the terms “provide” or “to provide” encompass a wide variety of actions. For example, “provide” may include storing a value in a location on a storage device for later retrieval, directly transmitting a value to a recipient via at least one wired or wireless medium, or transmitting or storing a reference to a value. “Providing” may also include encoding, decrypting, encrypting, cracking, demonstrating, verifying, etc., via hardware elements.

[0127] As used herein, the term “message” encompasses a wide variety of formats for communicating information (e.g., sending or receiving). A message may include collections of machine-readable information such as XML documents, fixed-field messages, comma-separated messages, JSON, and custom protocols. In some embodiments, a message may include signals used to transmit one or more representations of information. Although stated in the singular, it should be understood that a message may be created, sent, stored, received, etc., in multiple parts.

[0128] As used herein, the terms “corresponding” or “corresponding” encompass structural, functional, quantitative, and / or qualitative correlations or relationships between two or more objects, data sets, or pieces of information, and the correspondence or relationship may preferably be used to translate one or more of the two or more objects, data sets, or pieces of information to appear identical or equivalent. The correspondence may be evaluated using one or more of the following: thresholds, value ranges, fuzzy logic, pattern matching, machine learning evaluation models, or a combination thereof.

[0129] In any embodiment, the generated or detected data may be transferred to a “remote” device or location, where “remote” means a location or device other than the location or device on which the program is run. For example, a remote location could be another location in the same city (e.g., an office, laboratory, etc.), another location in a different city, another location in a different state, or another location in a different country. Thus, when one item is indicated to be “remote” to another item, this means that the two items may be in the same room but separated or at least in different rooms or in different buildings, and that the two items may be at least 1.61 km (1 mile), 16.1 km (10 miles), or 161 km (100 miles) apart. To “communicate” information refers to transmitting data that represents that information as electrical signals over a suitable communication channel (e.g., a private or public network). To “transfer” an item means any means of moving the item from one place to another, whether by physical transport or by other means (if possible), and, at least in the case of data, includes physically transporting a medium carrying the data or communicating the data. Examples of communication media include wireless or infrared transmission channels, as well as network connections to another computer or networked device, and the Internet or cellular networks.

[0130] As used herein, “User Interface” (also called an interactive user interface, graphical user interface, or UI) may refer to a network-based interface that includes data fields and / or other control elements for receiving input signals or providing electronic information and / or providing information to a user in response to any received input signals. Control elements may include dials, buttons, icons, selectable areas, or other recognizable indicators presented through the UI that, when interacted with (e.g., click, touch, select, etc.), initiate data exchange for the device presenting the UI. The UI may be implemented in whole or in part using technologies such as hypertext markup language (HTML), FLASH®, JAVA®, .NET®, web services, or rich site summary (RSS). In some implementations, the UI may be contained within a standalone client (e.g., a thick client, a fat client) configured to communicate (e.g., send or receive data) according to one or more of the embodiments described. The communication may be between medical devices, diagnostic devices, monitoring devices, or servers that communicate with them.

Claims

1. Upper housing and A lower housing is rotatably connected to the upper housing and configured to fit into a container, An NFC module configured to wirelessly receive Near Field Communication (NFC) input, Induction charging coil and Microprocessor and A latching mechanism, wherein the latching mechanism is A locking latch configured to prevent the upper housing and the lower housing from rotating relative to each other, and An electrically operated component configured to lock and unlock the latch in response to a signal received from the microprocessor and a current generated by the inductive charging coil. A latching mechanism and A locking cap assembly equipped with, The lower housing includes a plurality of locking vanes within the lower housing, and the locking vanes are configured to variably define the inner diameter size of the lower housing in response to the rotation of the upper housing relative to the lower housing when the lower housing is mechanically engaged with the container. The locking cap assembly is configured to lock the container by contracting the plurality of locking vanes around the container in response to the rotation of the upper housing relative to the lower housing in a first direction, A locking cap assembly configured such that the microprocessor receives the NFC input from the NFC module, and in response to the microprocessor determining that the NFC input received by the NFC module corresponds to authorization to release the locking cap assembly from the container, the microprocessor unlocks the locking latch, allows the upper housing to rotate in a second direction relative to the lower housing, retracts the plurality of locking vanes, and releases the lower housing from the container.

2. The locking cap assembly according to claim 1, further comprising a vane positioning ring in the lower housing, wherein the vane positioning ring is coupled to the plurality of locking vanes and the upper housing, and when the vane positioning ring rotates with the upper housing relative to the lower housing, the vane positioning ring extends or retracts the plurality of locking vanes.

3. The locking cap assembly according to claim 2, further comprising a plurality of locking slots located within the lower housing, wherein the locking latch is configured to engage with one of the plurality of locking slots from the upper housing.

4. The locking cap assembly according to claim 2, further comprising a display disposed within the upper housing, wherein the display is configured to display a unique identifier associated with the drug in the container and the recipient of the drug.

5. The locking cap assembly according to claim 4, wherein the locking cap assembly is configured to transmit the unique identifier to a device adjacent to the locking cap assembly, and after the unique identifier has been transmitted to the device and read by the device, to receive the authorization from the device adjacent to the locking cap assembly via the NFC module.

6. The locking cap assembly according to claim 5, further comprising an electrical component for receiving wireless power charge from the device and supplying power to the electrically operated components of the locking cap assembly.

7. The locking cap assembly according to claim 2, wherein the lower housing is positioned between the upper housing and the container.

8. The locking cap assembly according to claim 7, wherein the electrically actuated component is coupled to the vane positioning ring and configured to cause a motor-driven rotation of the upper housing relative to the lower housing in response to the signal received from the microprocessor, thereby locking or unlocking the locking cap assembly on the container.

9. The locking cap assembly according to any one of claims 1 to 8, further comprising an optical sensor configured to determine the position of the locking latch and to determine the locking state of the locking cap assembly.

10. The locking cap assembly according to any one of claims 1 to 9, further comprising a buzzer configured to emit a human-recognizable output at a predetermined time prior to the scheduled administration of the drug in the container.

11. The locking cap assembly according to claim 10, wherein the human-recognizable output is at least one of sound or vibration.

12. The locking cap assembly according to any one of claims 1 to 10, wherein the NFC module is configured to communicate information to a data network in response to a determination that the locking cap assembly is unlocked from the container.

13. A method for securing a drug container, The steps include: receiving an authorization code wirelessly transmitted via the communication channel of a device placed near the locking cap assembly by a Near Field Communication (NFC) module in the locking cap assembly; The steps include determining whether the current time is within the drug administration time interval, based on the determination that the aforementioned approval code is a valid approval code, In accordance with the determination that the current time falls within the drug administration time interval, Steps include: when an input received by the NFC module corresponds to authorization to release the locking cap assembly from the drug container, releasing the locking latch of the locking cap assembly so that a plurality of locking vanes of the locking cap assembly retract, wherein the plurality of locking vanes variably define the size of the central opening, the plurality of locking vanes are configured to mechanically engage with the drug container in the locked state of the locking cap assembly, and power to release the locking latch is provided by wireless energy transmission from the device to the motor of the locking cap assembly via the communication channel; Methods that include...

14. The method according to claim 13, further comprising the step of receiving the authorization code transmitted by the device after the device has read a unique identifier associated with the locking cap assembly using the device's NFC module.

15. The method according to claim 13 or 14, further comprising the step of storing the approval information for unlocking the drug container in the data network, such that the drug container is configured to be unlocked by a plurality of approved mobile devices that obtain the approval information via the data network.

16. The method according to any one of claims 13 to 15, wherein the device includes a mobile phone, the valid authorization code is transmitted from the mobile phone to the locking cap assembly as a cryptographic hash code, and the locking cap assembly includes a decryption key for decrypting the valid authorization code.

17. After the drug container is unlocked, the data is transmitted to the data network via the NFC module of the locking cap assembly. The steps include maintaining a record in the data network regarding when the drug in the drug container was administered, and The method according to any one of claims 13 to 16, further comprising:

18. The method according to any one of claims 13 to 17, further comprising the step of sounding an alarm in the locking cap assembly at a predetermined time prior to the scheduled subsequent administration of the drug in the drug container.

19. The method according to any one of claims 13 to 18, further comprising the step of updating a marking on the locking cap assembly after the drug container is unlocked in order to provide information regarding the dosage or other information relating to the drug in the drug container.

20. The method according to any one of claims 13 to 19, further comprising the step of transmitting an access code for releasing the locking cap assembly from a first approved mobile device to a second approved mobile device.

Images