Patent Description:
This application relates generally to a locking cap assembly.

Unauthorized access to medical containers or administering a medication prior to a scheduled time period for a subsequent dose may harm patient safety.

Patient safety can be enhanced by ensuring that authorized access to containers storing medication is granted only to authorized persons and at an authorized time. Some patients may not be able to adhere to a prescribed schedule for self-administering a medication. As a result, accidentally administering a subsequent dose of a medication before the intended time of that dose may harm patient safety. Sometimes, patients may not be able to recall when the last dose was administered, and thus cause uncertainty in when the next dose should be administered.

<CIT>) discloses a multi-piece, automated medication container having a first piece with an interactive label and a machine readable and writable electronic memory strip. The memory strip contains prescription information, medication information and program codes that are downloaded to a second piece having a computer processor. In one embodiment of the invention, the interactive label is affixed to a vial of a standard childproof container. The vial is sealed by an automated cap. The automated cap includes sensors for reading the information and codes on the memory strip and a memory for storing the information and codes. The automated cap also includes a display for visually or audibly indicating desired information to the patient, such as when to take the next dose of medication. A computer controlled locking assembly in the cap presents its removal before the prescribed time for taking the next dose of medication. The sensors also obtain actual medication consumption information based on when the container is opened. This actual consumption information is used to keep inventory information regarding the number of doses remaining in the container. The actual consumption information and inventory information is stored in the memory of the cap or sent to the interactive label to update the memory strip. The memory strip can also contain contraindication information for downloading to a personal home computer or a hospital or nursing home computer. In an other embodiment, the interactive label is affixed to a blister pack containing individual doses of medication. The blister pack is then placed in an automated dispenser.

<CIT>) a pill bottle cap providing access to authorized users using a biometric authentication feature. The pill bottle cap broadly includes: a shroud; a plurality of clamp members, each movably mounted to the shroud; a drive member interconnected with each of the clamp members to cause the clamp members to move in a first direction when the drive member is actuated in a first direction, and to cause the clamp members to move in a second direction when the drive member is actuated in a second direction; an actuator configured to actuate the drive member to selectively move in each of the first and second directions; and biometric identification module coupled to the actuator, and configured to activate the actuator to cause the selective movement upon identification of an authorized user. Each of the components are configured and positioned to minimize a height and a volume of the pill bottle cap.

<CIT>) discloses a pill container and dispenser including pill dispenser cap having a rotatable carousel with a pill-receiving chamber. The carousel is rotatable between a position in which the chamber receives pills from a storage component of the pill dispenser, and a position in which the pill can be dispensed from the chamber to a user. The pill dispenser includes systems for detecting the dispensing of the pill, and systems for recording and/or reporting pill dispensing events to a mobile device or remote server to allow compliance tacking. Some embodiments of the pill dispenser require a removal tool to remove a cap assembly from the storage compartment. Some embodiments including a locking ring that prevents the removal tool from removing the cap assembly. The locking ring must be damaged in some embodiments to remove the locking ring from the container.

<CIT>) discloses a attery powered, keyless locking container cap configured securing a bayonet filler neck or threaded filler neck remaining unlocked after attachment. A timer circuit powers off placing the invention into an energy saving, mode; a compression spring forces a coupler into engagement. While engaged, the cap can be removed and replaced. Cap rotation by an unauthorized user, locks the cap. A backup, rotary pin coded lock is in the interior inaccessible. Cap rotation enters a pin code to unlock or lock the cap. The invention supplied is with a transmitter configured as a key fob or a cigarette lighter power plug. the transmitter signals the cap not to lock thereby providing removal. rotational Comprising rotary frictional slippage prevents unauthorized removal by limiting both speed and the rotational force to a level insufficient to override the attachment torque.

Accordingly, there is a need for systems, devices, and methods that assist a patient in adhering to a prescribed schedule for administering a medication. By granting the patient and or caregivers authorized access to the medication only at an authorized time (e.g., the time of a subsequent dose) and automatically logging a time when the medication was accessed from the container, patient safety may be improved.

The systems, devices, and methods described herein provide an automated way to lock a medicine container and unlocking the medicine container only when a valid authorization code is provided to a locking cap assembly securing the medicine. According to various implementations, the medicine container is permitted to be unlocked only within a time window when a subsequent dose of the medicine is to be administered. The authorization code may be transferred between caregivers and/or the patient to allow additional or different authorized personnel access to the medicine container.

The disclosed devices and systems include a locking cap assembly having an upper housing, a lower housing rotatably connected to the upper housing and configured to be fitted onto a container, a near field communication (NFC) module configured to wirelessly receive a NFC input, an inductive charging coil, a microprocessor; and a latching mechanism. The latching mechanism includes: a locking latch configured to prevent the upper housing and the lower housing from rotating with respect to each other; and an electrical actuation component configured to lock and unlock the latch responsive to a signal received from the microprocessor and a current generated by the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, the locking vanes being configured to variably define an inner diameter size of the lower housing responsive to a rotation of the upper housing with respect to the lower housing when the lower housing is mechanically engaged with the container. When the locking cap assembly is configured to lock onto the container by contracting the plurality of vanes about the container responsive to a rotation of the upper housing with respect to the lower housing in a first direction. The microprocessor is configured to receive the NFC input from the NFC module and to unlock the locking latch and permit the rotation of upper housing with respect to the lower housing in a second direction to retract the plurality of locking vanes and release the lower housing from the container responsive to the microprocessor determining that the NFC input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container.

The disclosed subject matter also relates to a method of securing a medication container, the method includes receiving, by a near field communication (NFC) module in a locking cap assembly, an authorization code sent wirelessly from a device placed in proximity to the locking cap assembly via a communication channel of the NFC module. In accordance with a determination that the authorization code is a valid authorization code, determining if a current time is within a medication administration time interval. In accordance with a determination that the current time is within the medication administration time interval: releasing a locking latch of the locking cap assembly to permit a plurality of locking vanes of the locking cap assembly to retract when an input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container. The plurality of locking vanes variably defines a size of a central opening, and the central opening defined by the plurality of locking vanes is configured to be mechanically engaged with the medication container in a locked state of the locking cap assembly. Electrical power for releasing the locking latch is provided by a wireless energy transfer from the device via the communication channel to a motor of the locking cap assembly.

Other aspects include corresponding apparatus, and computer program products for implementation of the corresponding system and its features.

For a better understanding of the various described implementations, reference should be made to the Description below, in conjunction with the following drawings. Like reference numerals refer to corresponding parts throughout the figures and description.

Reference will now be made to implementations, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide an understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

<FIG> depicts an example of an institutional patient care system <NUM> of a healthcare organization, according to aspects of the subject technology. In <FIG>, a patient care device (or "medical device" generally) <NUM> is connected to a hospital network <NUM>. The term patient care device (or "PCD") may be used interchangeably with the term patient care unit (or "PCU"), either which may include various ancillary medical devices such as an infusion pump, a vital signs monitor, a medication dispensing device (e.g., cabinet, tote), a medication preparation device, an automated dispensing device, a module coupled with one of the aforementioned (e.g., a syringe pump module configured to attach to an infusion pump), or other similar devices. Each patient care device <NUM> is connected to an internal healthcare network <NUM> by a transmission channel <NUM>. Transmission channel <NUM> is any wired or wireless transmission channel, for example an <NUM> wireless local area network (LAN). In some implementations, network <NUM> also includes computer systems located in various departments throughout a hospital. For example, network <NUM> of <FIG> optionally includes computer systems associated with an admissions department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers and/or a medical decision support system. As described further below, network <NUM> may include discrete subnetworks. In the depicted example, network <NUM> includes a device network <NUM> by which patient care devices <NUM> (and other devices) communicate in accordance with normal operations.

Additionally, institutional patient care system <NUM> may incorporate a separate information system server <NUM>, the function of which will be described in more detail below. Moreover, although the information system server <NUM> is shown as a separate server, the functions and programming of the information system server <NUM> may be incorporated into another computer, if such is desired by engineers designing the institution's information system. Institutional patient care system <NUM> may further include one or multiple device terminals <NUM> for connecting and communicating with information system server <NUM>. Device terminals <NUM> may include personal computers, personal data assistances, mobile devices such as laptops, tablet computers, augmented reality devices, or smartphones, configured with software for communications with information system server <NUM> via network <NUM>.

Patient care device <NUM> comprises a system for providing patient care, such as that described in Eggers et al. , Patient care device <NUM> may include or incorporate pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy devices, and other drug delivery devices may be utilized according to the teachings set forth herein. In the depicted example, patient care device <NUM> comprises a control module <NUM>, also referred to as interface unit <NUM>, connected to one or more functional modules <NUM>, <NUM>, <NUM>, <NUM>. Interface unit <NUM> includes a central processing unit (CPU) <NUM> connected to a memory, for example, random access memory (RAM) <NUM>, and one or more interface devices such as user interface device <NUM>, a coded data input device <NUM>, a network connection <NUM>, and an auxiliary interface <NUM> for communicating with additional modules or devices. Interface unit <NUM> also, although not necessarily, includes a main non-volatile storage unit <NUM>, such as a hard disk drive or non-volatile flash memory, for storing software and data and one or more internal buses <NUM> for interconnecting the aforementioned elements.

In various implementations, user interface device <NUM> is a touch screen for displaying information to a user and allowing a user to input information by touching defined areas of the screen. Additionally or in the alternative, user interface device <NUM> could include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, softkeys, a mouse, a track ball and/or a light pen. Data input device <NUM> may be a bar code reader capable of scanning and interpreting data printed in bar coded format. Additionally or in the alternative, data input device <NUM> can be any device for entering coded data into a computer, such as a device(s) for reading a magnetic strips, radio-frequency identification (RFID) devices whereby digital data encoded in RFID tags or smart labels (defined below) are captured by the reader <NUM> via radio waves, PCMCIA smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of data input device <NUM> include a voice activation or recognition device or a portable personal data assistant (PDA). Depending upon the types of interface devices used, user interface device <NUM> and data input device <NUM> may be the same device. Although data input device <NUM> is shown in <FIG> to be disposed within interface unit <NUM>, it is recognized that data input device <NUM> may be integral within pharmacy system <NUM> or located externally and communicating with pharmacy system <NUM> through an RS-<NUM> serial interface or any other appropriate communication means. Auxiliary interface <NUM> may be an RS-<NUM> communications interface, however any other means for communicating with a peripheral device such as a printer, patient monitor, infusion pump or other medical device may be used without departing from the subject technology. Additionally, data input device <NUM> may be a separate functional module, such as modules <NUM>, <NUM>, <NUM> and <NUM>, and configured to communicate with controller <NUM>, or any other system on the network, using suitable programming and communication protocols.

Network connection <NUM> may be a wired or wireless connection, such as by Ethernet, WiFi, BLUETOOTH, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem or a cable modem. Any direct or indirect network connection may be used, including, but not limited to a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link or a WLANS connection or other wireless connection.

Functional modules <NUM>, <NUM>, <NUM>, <NUM> are any devices for providing care to a patient or for monitoring patient condition. As shown in <FIG>, at least one of functional modules <NUM>, <NUM>, <NUM>, <NUM> may be an infusion pump module such as an intravenous infusion pump for delivering medication or other fluid to a patient. For the purposes of this discussion, functional module <NUM> is an infusion pump module. Each of functional modules <NUM>, <NUM>, <NUM> may be any patient treatment or monitoring device including, but not limited to, an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG monitor, an EEG monitor, a heart rate monitor or an intracranial pressure monitor or the like. Functional module <NUM>, <NUM> and/or <NUM> may be a printer, scanner, bar code reader or any other peripheral input, output or input/output device.

Each functional module <NUM>, <NUM>, <NUM>, <NUM> communicates directly or indirectly with interface unit <NUM>, with interface unit <NUM> providing overall monitoring and control of device <NUM>. Functional modules <NUM>, <NUM>, <NUM>, <NUM> may be connected physically and electronically in serial fashion to one or both ends of interface unit <NUM> as shown in <FIG>, or as detailed in Eggers et al. However, it is recognized that there are other means for connecting functional modules with the interface unit that may be utilized without departing from the subject technology. It will also be appreciated that devices such as pumps or patient monitoring devices that provide sufficient programmability and connectivity may be capable of operating as stand-alone devices and may communicate directly with the network without connected through a separate interface unit or control unit <NUM>. As described above, additional medical devices or peripheral devices may be connected to patient care device <NUM> through one or more auxiliary interfaces <NUM>.

Each functional module <NUM>, <NUM>, <NUM>, <NUM> may include module-specific components <NUM>, a microprocessor <NUM>, a volatile memory <NUM> and a nonvolatile memory <NUM> for storing information. It should be noted that while four functional modules are shown in <FIG>, any number of devices may be connected directly or indirectly to controller unit <NUM>. The number and type of functional modules described herein are intended to be illustrative, and in no way limit the scope of the subject technology. Module-specific components <NUM> include any components necessary for operation of a particular module, such as a pumping mechanism for infusion pump module <NUM>.

While each functional module may be capable of a least some level of independent operation, interface unit <NUM> monitors and controls overall operation of device <NUM>. For example, as will be described in more detail below, interface unit <NUM> provides programming instructions to the functional modules <NUM>, <NUM>, <NUM>, <NUM> and monitors the status of each module. The programming instructions may be based a volume or flow rate detected using at least some of the features described.

Patient care device <NUM> is capable of operating in several different modes, or personalities, with each personality defined by a configuration database. The configuration database may be a database <NUM> internal to patient care device, or an external database <NUM>. A particular configuration database is selected based, at least in part, by patient-specific information such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or a patient care device's <NUM> location in the hospital or hospital computer network. Patient care information may be entered through interface device <NUM>, <NUM>, <NUM> or <NUM>, and may originate from anywhere in network <NUM>, such as, for example, from a pharmacy server, admissions server, laboratory server, and the like.

Medical devices incorporating aspects of the subject technology may be equipped with a Network Interface Module (NIM), allowing the medical device to participate as a node in a network. While for purposes of clarity the subject technology will be described as operating in an Ethernet network environment using the Internet Protocol (IP), it is understood that concepts of the subject technology are equally applicable in other network environments, and such environments are intended to be within the scope of the subject technology.

Data to and from the various data sources can be converted into network-compatible data with existing technology, and movement of the information between the medical device and network can be accomplished by a variety of means. For example, patient care device <NUM> and network <NUM> 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 occur through direct network connection <NUM> (as shown in <FIG>), or through RS232 links, MIB systems, RF links such as BLUETOOTH, IR links, WLANS, digital cable systems, telephone modems or other wired or wireless communication means. Manual interaction between patient care device <NUM> and network <NUM> involves physically transferring, intermittently or periodically, data between systems using, for example, user interface device <NUM>, coded data input device <NUM>, bar codes, computer disks, portable data assistants, memory cards, or any other media for storing data. The communication means in various aspects is bidirectional with access to data from as many points of the distributed data sources as possible. Decision-making can occur at a variety of places within network <NUM>. For example, and not by way of limitation, decisions can be made in health information server (HIS) <NUM>, decision support <NUM>, remote data server <NUM>, hospital department or unit stations <NUM>, or within patient care device <NUM> itself.

Direct communications with medical devices operating on a network in accordance with the subject technology may be performed through information system server <NUM>, also known as the remote data server (RDS). In accordance with aspects of the subject technology, network interface modules incorporated into medical devices such as, for example, infusion pumps or vital signs measurement devices, ignore all network traffic that does not originate from an authenticated RDS. The primary responsibilities of the RDS of the subject technology are to track the location and status of all networked medical devices that have NIMs, and maintain open communication.

<FIG> depicts an example of a locking cap assembly secured to a medicine container, according to aspects of the subject technology. <FIG> shows a locking cap assembly <NUM> securing a medicine bottle <NUM>. The locking cap assembly <NUM> includes an upper housing <NUM>, a lower housing <NUM>, and a display <NUM> positioned on the upper housing <NUM>. The lower housing <NUM> is rotatably connected to the upper housing and configured to be fitted onto the medicine bottle <NUM>. The lower housing <NUM> is positioned between the upper housing <NUM> and the medicine bottle <NUM>. Positioned within the upper housing <NUM> are electronic and communication components described in greater details in <FIG> and <FIG>.

According to various implementations, the locking cap assembly <NUM> may display and/or store a unique identifier that is associated to a patient, and medication contained in the medicine bottle <NUM>. The unique identifier may be wirelessly communicated to the locking cap assembly <NUM> and may be stored internally by the locking cap assembly <NUM>. The locking cap assembly <NUM> includes a communication module that allows other devices to read its unique identifier. The communication module may include a near field communication (NFC) module that is configured to wirelessly receive a NFC input. In some implementations, the unique identifier may be read by a NFC module of another device (e.g., a phone, a tablet). In some implementations, the locking cap assembly <NUM> is configured to transmit the unique identifier to a device proximate to the locking cap assembly <NUM>, and receive the authorization, via the NFC module, from the device proximate to the locking cap assembly after the unique identifier is transmitted to and read by the device.

In some implementations, the display <NUM> on the locking cap assembly <NUM> may display an optically scannable indicia (e.g., a 2D barcode) that can be scanned by a device (e.g., a phone, a tablet, a handheld optical scanner). When the device is placed in proximity to (e.g., within two inches, or in contact with) the locking cap assembly <NUM>, the NFC reader in the device may read the unique identifier of the locking cap assembly <NUM>. The device may then provide, to the locking cap assembly <NUM>, an authorization code specific to the locking cap assembly <NUM> in order to enable unlocking of the locking cap assembly <NUM>. In some implementations, the valid authorization code is transmitted as a cryptographic hash code from the device to the locking cap assembly, and the locking cap assembly is able to store a decryption key that allows a microprocessor on the locking cap assembly to decrypt the valid authorization code.

In some implementations, the authorization code is provided to an authorized device via an application installed on the device. For example, the authorization code is sent from a cloud server to the application installed on the device. The cloud server may use other methods to authenticate the identity of the user of the device, to confirm that the user granted access to the medication in the medicine bottle <NUM> is an authorized user. The scannable indicia displayed on the display <NUM> may allow the device to identify the medication stored in the medicine bottle, even for users who may not having access to the application that relays the authorization code from the cloud server. Such users, by scanning the scannable indicia, may be directed to a manufacturer of the drug to receiver further information such as side effects, recommended administration, or precautions associated with the medication. The user may also be provided with contact information to a doctor or caregiver in case of an emergency.

The locking cap assembly <NUM> may be used to lock single bottles of medications, and may be used also in situations where multiple bottles may need to be controlled and monitored, such as in a hospital, a school, an institution, or a doctor's office.

<FIG> depicts an example of a locking cap assembly having locking vanes in two different configurations, according to aspects of the subject technology. <FIG> shows locking vanes <NUM> in two different positions by rotating the upper housing <NUM> relative to the lower housing <NUM>. The locking cap assembly <NUM> is placed over a mouth or opening of the medicine bottle <NUM>. By rotating the upper housing <NUM> in a clockwise fashion as shown by an arrow <NUM>, the locking vanes <NUM> (originally in a retracted position and do not engage a corresponding protruding lip <NUM>, or locking rim, of the medicine bottle <NUM>) may start to extend and engage with the lip <NUM>. By rotating the upper housing <NUM> in a counterclockwise fashion as shown by an arrow <NUM>, the locking vanes <NUM> (originally in an extended position and engaged with the corresponding protruding lip <NUM> of the medicine bottle <NUM>) may start to retract, allowing the locking cap assembly <NUM> to be removed from the medicine bottle <NUM>. The locking vanes <NUM> are configured to variably define an inner diameter size of the lower housing <NUM> responsive to a rotation of the upper housing <NUM> with respect to the lower housing <NUM> when the lower housing <NUM> is mechanically engaged with the medicine bottle <NUM>. For example, the locking cap assembly <NUM> is configured to lock onto the medicine bottle <NUM> by contracting the locking vanes <NUM> about the medicine bottle <NUM> responsive to a rotation of the upper housing <NUM> with respect to the lower housing <NUM> in a first direction (e.g., a counter-clockwise direction).

The adjustable locking vanes <NUM> allow the locking cap assembly <NUM> to adapt to various bottle sizes that have mouths of different diameters. Such a feature allows the locking cap assembly <NUM> to accommodate multiple different bottle sizes. The locking cap assembly <NUM> is removed from the medicine bottle <NUM> by twisting the upper housing <NUM> relative to the lower housing <NUM> until the locking vanes <NUM> are in the retracted position and no longer engage the protruding lip <NUM> of the medicine bottle <NUM>.

<FIG> depicts locking vanes in two different configurations, according to aspects of the subject technology. <FIG> shows a view of the locking vanes <NUM> positioned within the lower housing <NUM> when the upper housing <NUM> is removed from the lower housing. The left portion of <FIG> shows the locking vane <NUM> in the retracted position. The right portion of <FIG> shows the locking vanes <NUM> in the extended position. A counterclockwise rotation of a vane positioning ring <NUM> retracts the locking vanes <NUM>. The vane positioning ring <NUM> is within the lower housing <NUM> and is coupled to the locking vanes <NUM> and to the upper housing <NUM>. The vane positing ring <NUM> extends or retracts the locking vanes <NUM> when the vane positioning ring <NUM> is rotated, together with the upper housing <NUM>, relative to the lower housing <NUM>. A clockwise rotation of a vane positioning ring <NUM> extends the locking vanes <NUM>. The vane positioning ring <NUM> is connected to the upper housing <NUM> and is rotated when the upper housing <NUM> is twisted. Twisting the upper housing <NUM> in a clockwise direction closes the locking vanes <NUM>, and twisting the upper housing <NUM> in a counterclockwise direction opens the locking vanes <NUM>.

<FIG> depicts a cross sectional view of the locking cap assembly and medicine bottle shown in <FIG>, according to aspects of the subject technology. <FIG> shows a cross-sectional view of the locking cap assembly <NUM> and the medicine bottle <NUM>. The upper housing <NUM> is entirely above the medicine bottle <NUM> (shown as being entirely to the right of the medicine bottle <NUM> in <FIG>). The lower housing <NUM> surrounds a neck or mouth region of the medicine bottle <NUM>. The vane positing ring is further away from the medicine bottle <NUM> (extended further to the right of <FIG>) compared to the locking vanes <NUM>. When the locking vanes <NUM> are in the extended position, they engage the protruding lip <NUM> in the neck region of the medicine bottle <NUM> to prevent the removal of the locking cap assembly <NUM> from the medicine bottle <NUM>. When the locking vanes <NUM> are in the retracted position, they no longer engage the protruding lip <NUM> of the medicine bottle <NUM> and the locking cap assembly <NUM> may be removed from the medicine bottle <NUM>. Some medicine containers include a lip at an opening of the container for engaging with a corresponding snap bottle cap. The locking vanes <NUM> may lock onto the lip of such a medicine containers. Some medicine container includes threads for engaging with a corresponding screw-type cap. The locking vanes <NUM> may also lock onto threads of such medicine containers. In other words, the locking cap assembly <NUM> is adapted to function together with a variety of existing medicine bottles.

<FIG> depicts an exploded view of the locking cap assembly, according to aspects of the subject technology. <FIG> shows an exploded view of various components of the locking cap assembly <NUM>. A top portion of the locking cap assembly <NUM> includes an upper housing cover <NUM> that surrounds the display <NUM>. A circuit board <NUM> and a near field communication (NFC) antenna or coil <NUM> are positioned behind the upper housing cover. A super capacitor <NUM> and an electrical actuation component <NUM> are housed within the upper housing <NUM>. The vane positioning ring <NUM> and the locking rings <NUM> are housed within the lower housing <NUM>.

<FIG> shows a detailed view of components of the locking cap assembly, according to aspects of the subject technology. <FIG> shows an exploded detail view of some components of the locking cap assembly <NUM>. Within the upper housing <NUM> are the electrical actuation component <NUM>, a locking latch <NUM>, a latch position sensor <NUM>, and a latch extension spring <NUM>. The latch position sensor <NUM> is configured to sense a position of the locking latch <NUM> to determine if the locking latch <NUM> is positioned in a locked (extended) state or an unlocked (retracted) state. The latch extension spring <NUM> may control a movement of the locking latch <NUM> between the locked state and the unlocked state. The locking latch <NUM> is configured to prevent the upper housing <NUM> and the lower housing <NUM> from rotating with respect to each other. The electrical actuation component <NUM> is configured to lock and unlock the locking latch <NUM> responsive to a signal received from a microprocessor of the locking cap assembly and a current generated by an inductive charging coil of the locking cap assembly.

Within the lower housing <NUM> are the locking vanes <NUM> and a plurality of latch locking slots <NUM>. The latch locking slots <NUM> are regularly spaced and each latch locking slot has a width that enables the slot to receive the locking latch <NUM> and to hold the locking latch <NUM> in an engaged position in the locked (extended) state. When one of the latch locking slots <NUM> is engaged by the locking latch <NUM>, rotation between the upper housing <NUM> and the lower housing <NUM> is blocked, preventing the retraction of the locking vanes <NUM>.

<FIG> shows a detailed view of a locking latch, according to aspects of the subject technology. <FIG> shows a detailed view of the locking latch <NUM> when the latch extension spring <NUM> is loaded. In some implementations, the spring <NUM> is loaded when it is compressed. When unlocked, the locking latch <NUM> is free to retract, allowing the locking cap assembly <NUM> to be turned (e.g., the upper housing <NUM> is twisted or rotated relative to the lower housing <NUM>) so that the medicine bottle <NUM> may be opened. When locked, the locking latch <NUM> is prevented from retracting, blocking the locking cap assembly <NUM> from turning (e.g., the upper housing <NUM> is locked relative to the lower housing <NUM> such that rotations are prevented) and the locking vanes are locked in place, preventing the medicine bottle <NUM> from being opened.

<FIG> shows a detailed view of a portion of the locking cap assembly in a locked state, according to aspects of the subject technology. <FIG> shows a detailed view of the locking cap assembly <NUM> in the locked state. In the locked state, a lock <NUM> is extended and prevents the locking latch <NUM> from retracting and prevents the locking cap assembly <NUM> from rotating. The lock <NUM> is extended when it moves to the right of the drawing, further away from the electrical actuation component <NUM>. The electrical actuation component <NUM> actuates the lock <NUM> to move from left (unlocked state, the lock <NUM> positioned closer to the electrical actuation component <NUM>) to right (locked state, the lock <NUM> positioned further from the electrical actuation component <NUM>). In some implementations, the electrical actuation component <NUM> includes a lock motor. In some implementations, the electrical actuation component <NUM> includes a solenoid. In some implementations, the electrical actuation component <NUM> does not rotate. For example, the electrical actuation component <NUM> may be a linear actuator that retracts a lock mechanism.

When the lock <NUM> is engaged, the locking cap assembly <NUM> is not removed from the medicine bottle <NUM>. In the locked state, the latch extension spring <NUM> is extended and the locking latch <NUM> extends/ protrudes into, and is held within, the latch locking slot <NUM>.

<FIG> shows a detailed view of a portion of the locking cap assembly in an unlocked state, according to aspects of the subject technology. <FIG> shows a detailed view of the locking cap assembly <NUM> in the unlocked state. In the unlocked state, the lock <NUM> is retracted (moves to the left of the drawing, closer to the electrical actuation component <NUM>) and the locking latch <NUM> is free to retract. Once the locking latch <NUM> is retracted, the locking cap assembly <NUM> is able to rotate to retract the locking vanes <NUM>, allowing the locking cap assembly <NUM> to be removed from the medicine bottle <NUM>. In the locked state, shown in <FIG>, a latch position flag <NUM> interrupts signal from the latch position sensor <NUM> to indicate that the mechanism is locked. In the unlocked state, the latch position flag <NUM> no longer obscures the latch position sensor <NUM> and the locking cap assembly <NUM> is indicated as being unlatched.

<FIG> shows a perspective view of a portion of the locking cap assembly in an unlocked state, according to aspects of the subject technology. <FIG> shows a detailed perspective view of the unlocked state. The lock <NUM> is retracted, and the latch position flag <NUM> is displaced from the latch position sensor <NUM>. The locking latch <NUM> is also retracted, and is not engaged within a latch locking slot <NUM>. Each pair of latch locking slot <NUM> is separated by a latch locking protrusion <NUM>. The latch locking protrusion <NUM> is able to push the locking latch <NUM> and compress the latch extension spring <NUM> in the unlocked state.

<FIG> shows a perspective view of a portion of the locking cap assembly in a locked state, according to aspects of the subject technology. <FIG> shows a detailed cross-sectional perspective view of the locked state. The locking latch <NUM> in the extended position, and is engaged within a latch locking slot <NUM>. The latch extension spring <NUM> is extended in the locked state. The latch position flag <NUM> is underneath the latch position sensor <NUM> and interrupts a signal between a top portion <NUM> of the latch position sensor <NUM> and a bottom portion <NUM> of the latch position sensor. The interrupted signal indicates that the mechanism is locked.

<FIG> shows a perspective view of a portion of the locking cap assembly in a locked state, according to aspects of the subject technology. <FIG> shows a detailed cross-sectional perspective view of the locked state. The electrical actuation component <NUM> has not fully retracted the lock <NUM> and a portion <NUM> of the lock <NUM> remains in contact with the latch position flag <NUM>, preventing the latch <NUM> from retracting. In some implementations, the lock <NUM> includes a series of teeth that engages a corresponding part of the electrical actuation component <NUM> to cause the lock <NUM> to be actuated.

In some implementations, the electrical actuation component is coupled to the vane positioning ring or to the lower housing <NUM> and configured to cause a motor-driven rotation of the upper housing <NUM> with respect to the lower housing <NUM> to lock or unlock the locking cap assembly <NUM> onto the medicine bottle <NUM> responsive to a signal received from the microprocessor. Such implementations may use a larger motor and more power to actuate or cause the rotations. A separate lock may additionally be provided to prevent turning the larger motor, which would be connected to the locking cap assembly cap. A size of the locking cap assembly cap may be increased, and more power, in addition to that provided by the NFC coil, may be used.

In some implementations, the locking cap assembly may include a solenoid that disengages the lock.

<FIG> depicts a system architecture of the locking cap assembly, according to aspects of the subject technology. <FIG> shows a system architecture <NUM> of the hardware components of the locking cap assembly <NUM>. A microprocessor <NUM> positioned on the circuit board <NUM> controls various components of the locking cap assembly <NUM>. The microprocessor <NUM> having associated firmware <NUM> controls the display <NUM>, a power management system <NUM>, a NFC reader <NUM>, an output device <NUM> such as a buzzer, a Bluetooth communication module <NUM>. The output device <NUM> may emit a human perceivable output such as audio or vibration. The microprocessor <NUM> also controls a latch locking mechanism <NUM> which includes the latch position sensor <NUM>, a MOSFET driver and isolation system <NUM>, and the electrical actuation component <NUM>.

The power management system <NUM> controls one or more energy sources: a battery <NUM>, the super capacitor <NUM>, and charging by the inductive charging coil <NUM>. The battery <NUM> may provide higher energy density for storage, while the super capacitor <NUM> may have more rapid charge and discharge capabilities. The potential energy in the super capacitor <NUM> may be stored in an electric field, whereas the battery <NUM> may store its potential energy in a chemical form.

In some implementations, the locking cap assembly <NUM> includes either (i) the battery <NUM>, or (ii) the super capacitor <NUM> and the inductive charging coil <NUM>. In some implementations, a primary coil in a charging device (e.g., a cell phone) induces a current in the NFC coil <NUM> coil of the locking cap assembly <NUM> to reverse wireless charge the locking cap assembly <NUM>. The reverse wireless charge may be carried out by placing the cell phone and the locking cap assembly <NUM> together in close proximity. The NFC circuit in the container may be configured to conduct energy harvesting to harvest the NFC signal transmitted by the charging device, or may utilize NFC specific energy transfer to receive and/or transmit energy. Energy may also be received and/or transmitted using Qi standard, or similar standard, using reverse charging capability where a device (e.g., phone) can wirelessly power an accessory.

The energy transferred by a charging device to the locking cap assembly <NUM> over a short period of time (e.g., the time to request access) is typically on the order of a couple hundred milliwatts. In this regard, the locking cap assembly <NUM> may be configured to harvest energy from the charging device to cause the motor or actuator to operate. The locking cap assembly <NUM> may include (e.g., within the cap) a small storage device such as a battery or super capacitor to allow storage of harvested power and a smooth transfer of the power over time. In some implementations, the locking cap assembly <NUM> may be configured to operate in standby mode until a command to open is received from the charging device or other NFC device in order to conserve energy. In standby mode, resource consuming functions may be disabled or operated in a low power state.

The NFC coil <NUM> may also send or receive communication signals that are sent to the NFC reader <NUM> to be decoded. The communication signals may provide information for displaying on the display <NUM>, or may provide a locking status of the locking cap assembly <NUM> (e.g., whether it is in the locked or unlocked state). The NFC reader <NUM> may relay the information to the microprocessor <NUM>. In cases where the locking cap assembly <NUM> is expected to be in a locked state (based on information received from the NFC coil <NUM>) but the microprocessor <NUM> determines that it is in fact in an unlocked state (based on information from the latch position sensor <NUM>), the microprocessor can send control signals to trigger an alarm by activating the output device <NUM>. Similar alerts about the locking state of the locking cap assembly <NUM> may also be sent and received using the BLE module <NUM>. In addition to receiving the sensor signals from the latch position sensor <NUM>, the microprocessor <NUM> also controls the latch locking mechanism <NUM> via the MOSFET driver and isolation system <NUM>. The isolation system <NUM> sends control signals to drive the electrical actuation component <NUM>.

In some implementations, the BLE module <NUM> is able to monitor if a medicine bottle secured by the locking cap assembly <NUM> is removed from a particular location. The BLE module allows the locking cap assembly <NUM> to communicate with other BLE-enabled device(s) in a vicinity of the locking cap assembly, to indirectly provide location information about the locking cap assembly. The locking cap assembly <NUM> may thus additionally support a "Find my container" functionality that allows a user to communicate with the locking cap assembly <NUM>, via BLE module. The locking cap assembly <NUM> can further include electronics that allows it to sound an alarm when triggered by the "Find my container" functionality. Alternatively, or in addition, the BLE module <NUM> can communicate with a user device (e.g., cell phone) and provide location information of the locking cap assembly <NUM> to the user device.

<FIG> depicts a locking cap assembly functional flowchart, according to aspects of the subject technology. <FIG> shows a locking cap functional flowchart <NUM>. The process starts with a phone having NFC capability being placed near the locking cap assembly <NUM> (<NUM>). The locking cap assembly <NUM> receives an ID code or access code via NFC communication from the phone (<NUM>).

The microprocessor <NUM> determines whether the ID code represents a valid access code (<NUM>). In accordance with a determination that the ID code is not valid, the display <NUM> shows an error message (<NUM>). For example, the display <NUM> may show an error message stating: "invalid code - seek authorization to open". In accordance with a determination that the ID code is valid, the display <NUM> shows a confirmation message (<NUM>). For example, the display <NUM> may show a confirmation message stating: "Valid code".

The microprocessor <NUM> determines whether it is time for a next dose of medication (<NUM>). In accordance with a determination that it is not yet time for the next dose of medication, the display <NUM> shows an error message (<NUM>). For example, the display <NUM> may show an error message stating: "not time yet for the next dose. " Such a feature helps patients who may require help with safely self-administering medicine by preventing accidental overdose caused by the patient prematurely taking an additional dose. For example, the patient is no longer required to remember the exact time the last dose was taken and/or calculate when the next dose is due. In accordance with a determination that it is time for the next dose, the locking cap assembly <NUM> unlocks (<NUM>). Due to the unlocking of the locking cap assembly <NUM>, the lock position sensor <NUM> detects the locking cap assembly <NUM> is unlatched (<NUM>). Medication may be retrieved by a patient after the locking cap assembly <NUM> is unlatched (<NUM>).

After the medication has been retrieved, the cap may be replaced and latched. The locking cap assembly <NUM> communications via NFC communication to the phone, and the phone relays information to a caregiver confirming that the medication has been administered (<NUM>). The status information may be sent to a cloud server via a phone app (<NUM>), and the time is reset locally (by the microprocessor <NUM>) for the next dose (<NUM>). The microprocessor <NUM> calculates a time (T) which corresponds to the time remaining until next dose (<NUM>).

The microprocessor <NUM> determines if T has decreased to zero, indicating that it is time for the next dose (<NUM>). In accordance with a determination that it is not yet time for the next dose of medication, the system simply loops through the functional flowchart again. In accordance with a determination that it is time for the next dose (i.e., T=<NUM>), the microprocessor <NUM> causes an alert message to be displayed on the display <NUM>. For example, the alert message may state: "Time for the next dose. " The microprocessor <NUM> may additionally trigger the output device <NUM> to notify the patient and/or the caregiver that it is time for the next dose. The microprocessor <NUM> may also cause an alert to the sent to the phone via the BLE module <NUM>. After the alerts are sent out, the process is looped through when the phone is placed near the locking cap assembly <NUM> (<NUM>).

As used herein, a "cap" may refer to a lid, a cover, or other releasable (e.g., lockable and unlockable) element that secures an opening for a container such as a bottle, tray, or bin. In some implementation, the locking vane or other actuated locking element is described as being secured "about the container. " Some implementations may secure the vane or other actuated locking element to a portion of the container such as a post or other protrusion affixed to the container.

<FIG> depicts a system used to control a locking cap assembly, according to aspects of the subject technology. <FIG> shows a system <NUM> that allows portability of access to medication. The access to medication may be transferred by transferring the access code key to selected caregivers. Pertinent information and logs of medication administration (time and dose administered) may be stored in the cloud server, and accessed via phones or other devices.

The system <NUM> includes a cloud server <NUM> that is in data communication with a phone <NUM>. The data communication may be established using WiFi signals. The phone <NUM> is in close proximity to the locking cap assembly <NUM> securing the medicine bottle <NUM>. A doctor or pharmacist using a terminal <NUM> may establish a data connection to the cloud server <NUM>, allowing the terminal <NUM> to access and/or edit a patient's electronic health record (EHR).

A doctor may send prescription data to the cloud server <NUM>. The phone <NUM> may provide information that logs the access to the medicine bottle <NUM> and the medication (e.g., pills) that are taken from the medicine bottle <NUM>. The phone <NUM> may provide the information, for example, according to step <NUM> of the example flowchart <NUM>, to the cloud server <NUM>. In some implementations, an application on the phone coordinates (i) the exchange of information between the cloud server <NUM> and the phone, and (ii) the communication between the phone and the locking cap assembly. The application that controls the unlocking may be maintained in the cloud server <NUM>, and may allow an access key (e.g., the authorization code) to be provided to phones of different authorized users. For such cases, the medication container can be carried by the patient, and control or reminders are transferred to one or more caretakers. For example, the access key may be transferred to different caregivers at different locations responsible for the care of an incapacitated person who is being transferred to the different locations. A child may also carry her medication with her to school, and the access key may be provided to a school nurse so the school nurse can administer the medication to the child. The cloud server <NUM> can keep a data log record of when the medication was administered, and an identity of the person administering the medication, and the time remaining until the next dose of the medication is to be administration. The application on the phone enables exchange of information between the phone and the cloud server <NUM>.

In some implementations, the user of the phone <NUM> is the patient who has a prescription to the medication contained in the medicine bottle <NUM>. The cloud server <NUM> may deliver reminder messages to the phone <NUM> to remind the patient to take a next dose of the medication. In some implementations, the user of the phone <NUM> is a caretaker. The cloud server <NUM> may deliver reminder messages to the phone <NUM> to remind a caretaker to administer the medication to the patient. In some implementations, the reminder sent by the cloud server <NUM> to the phone <NUM> may trigger a charging window during which wireless power transmission may be received by the locking cap assembly <NUM>, in additional to receiving a communication signal from the phone <NUM> to unlock the locking cap assembly <NUM>.

A first additional device <NUM> (e.g., a phone) of a first caretaker at a first location may also be in data connection to the cloud server <NUM>. A second additional device <NUM> (e.g., a phone) of a second caretaker at a second location may also be in data connection to the cloud server <NUM>. A third additional device <NUM> (e.g., a phone) of a third caretaker at a third location may also be in data connection to the cloud server <NUM>.

In some implementations, the first location, the second location and the third location are all at the same location (e.g., a hospital). The first, second, and third caretakers may be nurses working different shifts. The cloud server <NUM> is configured to send an access code key granting access to authorized users to each of the nurses at the beginning of their shifts. After administering the medication, one or more of the devices <NUM>, <NUM>, and <NUM> may provide information that logs the access to the medicine bottle <NUM> and the medication (e.g., pills) that are taken from the medicine bottle <NUM>. The devices <NUM>, <NUM>, and <NUM> may provide the information, for example, according to step <NUM> of the example flowchart <NUM>, to the cloud server <NUM>.

<FIG> depicts an example method for securing a medication container, according to aspects of the subject technology. A locking cap assembly receives, using a near field communication (NFC) module, an authorization code sent wireless from a device placed in proximity to the locking assembly via a communication channel of the NFC module (<NUM>). A microprocessor of the locking cap assembly determines if the authorization is a valid authorization code. The microprocessor is configured to receive the NFC input from the NFC module and to unlock the locking latch <NUM> and permit the rotation of upper housing <NUM> with respect to the lower housing <NUM> in a second direction to retract the plurality of locking vanes and release the lower housing <NUM> from the medicine bottle <NUM> responsive to the microprocessor determining that the NFC input received by the NFC module corresponds to an authorization to release the locking cap assembly <NUM> from the medicine bottle <NUM>.

In accordance with a determination that the authorization code is a valid authorization code, determine if a current time is within a medication administration time interval (<NUM>). In accordance with a determination that the current time is within the medication administration time interval: release a locking latch of the locking cap assembly to permit a plurality of locking vanes of the locking cap assembly to retract when an input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container (<NUM>).

In some implementations, the first location, the second location and the third location are at different locations. For example, the first, second, and third caretakers may be extended family members of the patient and may live at different places. When a patient has failed to take a medication, one or more of the first, second, and third caretaker may be notified by the cloud server <NUM>, and they may go to the location of the patient to help with administering the medication.

In some implementations, a locking cap assembly includes an upper housing, a lower housing rotatably connected to the upper housing and configured to be fitted onto a container, a near field communication (NFC) module configured to wirelessly receive a NFC input, an inductive charging coil, a microprocessor; and a latching mechanism. The latching mechanism includes: a locking latch configured to prevent the upper housing and the lower housing from rotating with respect to each other; and an electrical actuation component configured to lock and unlock the latch responsive to a signal received from the microprocessor and a current generated by the inductive charging coil. The lower housing includes a plurality of locking vanes within the lower housing, the locking vanes being configured to variably define an inner diameter size of the lower housing responsive to a rotation of the upper housing with respect to the lower housing when the lower housing is mechanically engaged with the container. When the locking cap assembly is configured to lock onto the container by contracting the plurality of vanes about the container responsive to a rotation of the upper housing with respect to the lower housing in a first direction. The microprocessor is configured to receive the NFC input from the NFC module and to unlock the locking latch and permit the rotation of upper housing with respect to the lower housing in a second direction to retract the plurality of locking vanes and release the lower housing from the container responsive to the microprocessor determining that the NFC input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container.

In some implementations, the locking cap assembly further includes a vane positioning ring within the lower housing, the vane positioning ring being coupled to the plurality of locking vanes and to the upper housing. The vane positing ring extends or retracts the plurality of locking vanes when the vane positioning ring is rotated, together with the upper housing, relative to the lower housing. In some implementations, the locking cap assembly further includes a plurality of locking slots positioned within the lower housing. The locking latch is configured to engage one of the plurality of locking slots from the upper housing.

In some implementations, a display disposed is in the upper housing, the display is configured to present a unique identifier associated with a medication in the container and a recipient of the medication. The locking cap assembly is configured to transmit the unique identifier to a device proximate to the locking cap assembly, and receive the authorization, via the NFC module, from the device proximate to the locking cap assembly after the unique identifier is transmitted to and read by the device.

In some implementations, the locking cap assembly further includes electrical components to receive wireless power charging from the device to power an electrical actuation component of the locking cap assembly. The lower housing is positioned between the upper housing and the container.

In some implementations, the electrical actuation component is coupled to the vane positioning ring and configured to cause a motor-driven rotation of the upper housing with respect to the lower housing to lock or unlock the locking cap assembly onto the container responsive to the signal received from the microprocessor.

In some implementations, the locking cap assembly further includes an optical sensor configured to determine a position of the locking latch for determining a locking state of the locking cap assembly.

In some implementations, the locking cap assembly further includes an output device (e.g., within the cap), such as a buzzer, configured to emit a human perceivable output (e.g., audio, a sound, vibration) at a predetermined time prior to a scheduled administration of a medication in the container. The NFC module is configured to communicate information to a data network responsive to a determination that the locking cap assembly is unlocked from the container.

In some implementations, a method of securing a medication container, the method includes receiving, by a near field communication (NFC) module in a locking cap assembly, an authorization code sent wirelessly from a device placed in proximity to the locking cap assembly via a communication channel of the NFC module. In accordance with a determination that the authorization code is a valid authorization code, determining if a current time is within a medication administration time interval. In accordance with a determination that the current time is within the medication administration time interval: releasing a locking latch of the locking cap assembly to permit a plurality of locking vanes of the locking cap assembly to retract when an input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container. The plurality of locking vanes variably defines a size of a central opening, and the plurality of locking vanes is configured to be mechanically engaged with the medication container in a locked state of the locking cap assembly. The electrical power for releasing the locking latch is provided by a wireless energy transfer from the device via the communication channel to a motor of the locking cap assembly.

In some implementations, the method further includes receiving the authorization code sent by a device after the device reads, using an NFC module of the device, a unique identifier associated with the locking cap assembly.

In some implementations, the method further includes storing, in a data network, authorization information for unlocking the medication container so that the medication container is configured to be unlocked by a plurality of authorized mobile terminals that retrieves the authorization information over the data network.

In some implementations, the method further includes the device being a cell phone, and the valid authorization code is transmitted as a cryptographic hash code from the cell phone to the locking cap assembly, and the locking cap assembly includes a decryption key for decrypting the valid authorization code.

In some implementations, the method further includes sending, via the NFC module of the locking cap assembly, data to a data network after the medication container has been unlocked; and maintaining, at the data network, a record of when medication in the medication container is administered.

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

In some implementations, the method further includes updating a display on the locking cap assembly after the medication container has been unlocked to provide dosage or other information relating to medication in the medication container. In some implementations, the method further includes transferring an access code for releasing the locking cap assembly from a first authorized mobile device to a second authorized mobile device. <FIG> is a conceptual diagram illustrating an example electronic system for controlling a locking cap assembly, according to aspects of the subject technology. Electronic system <NUM> may be a computing device for execution of software associated with one or more portions or steps of process, or components and processes provided by <FIG>, including but not limited to server <NUM>, computing hardware within patient care device <NUM>, or terminal device <NUM>. Electronic system <NUM> may be representative, in combination with the disclosure regarding <FIG>. In this regard, electronic system <NUM> may be a personal computer or a mobile device such as a smartphone, tablet computer, laptop, PDA, an augmented reality device, a wearable such as a watch or band or glasses, or combination thereof, or other touch screen or television with one or more processors embedded therein or coupled thereto, or any other sort of computer-related electronic device having network connectivity.

Electronic system <NUM> may include various types of computer readable media and interfaces for various other types of computer readable media. In the depicted example, electronic system <NUM> includes a bus <NUM>, processing unit(s) <NUM>, a system memory <NUM>, a read-only memory (ROM) <NUM>, a permanent storage device <NUM>, an input device interface <NUM>, an output device interface <NUM>, and one or more network interfaces <NUM>. In some implementations, electronic system <NUM> may include or be integrated with other computing devices or circuitry for operation of the various components and processes previously described.

Bus <NUM> collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of electronic system <NUM>. For instance, bus <NUM> communicatively connects processing unit(s) <NUM> with ROM <NUM>, system memory <NUM>, and permanent storage device <NUM>.

From these various memory units, processing unit(s) <NUM> retrieves instructions to execute and data to process in order to execute the processes of the subject disclosure. The processing unit(s) can be a single processor or a multi-core processor in different implementations.

ROM <NUM> stores static data and instructions that are needed by processing unit(s) <NUM> and other modules of the electronic system. Permanent storage device <NUM>, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when electronic system <NUM> is off. Some implementations of the subject disclosure use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as permanent storage device <NUM>.

Other implementations use a removable storage device (such as a floppy disk, flash drive, and its corresponding disk drive) as permanent storage device <NUM>. Like permanent storage device <NUM>, system memory <NUM> is a read-and-write memory device. However, unlike storage device <NUM>, system memory <NUM> is a volatile read-and-write memory, such a random access memory. System memory <NUM> stores some of the instructions and data that the processor needs at runtime. In some implementations, the processes of the subject disclosure are stored in system memory <NUM>, permanent storage device <NUM>, and/or ROM <NUM>. From these various memory units, processing unit(s) <NUM> retrieves instructions to execute and data to process in order to execute the processes of some implementations.

Bus <NUM> also connects to input and output device interfaces <NUM> and <NUM>. Input device interface <NUM> enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface <NUM> include, e.g., alphanumeric keyboards and pointing devices (also called "cursor control devices"). Output device interfaces <NUM> enables, e.g., the display of images generated by the electronic system <NUM>. Output devices used with output device interface <NUM> include, e.g., printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some implementations include devices such as a touchscreen that functions as both input and output devices.

Also, as shown in <FIG>, bus <NUM> also couples electronic system <NUM> to a network (not shown) through network interfaces <NUM>. Network interfaces <NUM> may include, e.g., a wireless access point (e.g., Bluetooth or WiFi) or radio circuitry (e.g., transceiver, antenna, amplifier) for connecting to a wireless access point. Network interfaces <NUM> may also include hardware (e.g., Ethernet hardware) for connecting the computer to a part of a network of computers such as a local area network ("LAN"), a wide area network ("WAN"), wireless LAN, personal area network ("PAN"), or an Intranet, or a network of networks, such as the Internet. Any or all components of electronic system <NUM> can be used in conjunction with the subject disclosure.

These functions described above can be implemented in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. The processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuitry. General and special purpose computing devices and storage devices specifically configured for the infusion features described can be interconnected through communication networks.

Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (also referred to as 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), a variety of recordable/rewritable DVDs (e.g., 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 density optical discs, and any other optical or magnetic media. The computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

While the above discussion primarily refers to microprocessor or multi-core processors that execute software, 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 that are stored on the circuit itself.

To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; e.g., feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; e.g., by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

Embodiments of the subject matter described in this specification can be implemented in a specifically configured computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components.

A client and server are generally remote from each other and may interact through a communication network. In some implementations, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device).

The described functionality may be implemented in varying ways for each particular application.

It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description provides various examples of the subject technology, and the subject technology is not limited to these examples. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

The term website, as used herein, 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. Accordingly, the term website may be used interchangeably with the terms web page and server. For example, a processor configured to monitor and control an operation or a component may also mean the processor being programmed to monitor and control the operation or the processor being operable to monitor and control the operation.

The term automatic, as used herein, may include performance by a computer or machine without user intervention; for example, by instructions responsive to a predicate action by the computer or machine or other initiation mechanism. The word "example" is used herein to mean "serving as an example or illustration. " Any aspect or design described herein as "example" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

A disclosure relating to an embodiment may apply to all implementations, or one or more implementations. A phrase such as an "embodiment" may refer to one or more embodiments and vice versa. A phrase such as a "configuration" may refer to one or more configurations and vice versa.

As used herein, the terms "determine" or "determining" encompass a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like via a hardware element without user intervention. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like via a hardware element without user intervention. "Determining" may include resolving, selecting, choosing, establishing, and the like via a hardware element without user intervention.

As used herein, the terms "provide" or "providing" encompass a wide variety of actions. For example, "providing" may include storing a value in a location of a storage device for subsequent retrieval, transmitting a value directly to the recipient via at least one wired or wireless communication medium, transmitting or storing a reference to a value, and the like. "Providing" may also include encoding, decoding, encrypting, decrypting, validating, verifying, and the like via a hardware element.

As used herein, the term "message" encompasses a wide variety of formats for communicating (e.g., transmitting or receiving) information. A message may include a machine readable aggregation of information such as an XML document, fixed field message, comma separated message, JSON, a custom protocol, or the like. A message may, in some embodiments, include a signal utilized to transmit one or more representations of the information. While recited in the singular, it will be understood that a message may be composed, transmitted, stored, received, etc. in multiple parts.

As used herein, the terms "correspond" or "corresponding" encompasses a structural, functional, quantitative and/or qualitative correlation or relationship between two or more objects, data sets, information and/or the like, preferably where the correspondence or relationship may be used to translate one or more of the two or more objects, data sets, information and/or the like so to appear to be the same or equal. Correspondence may be assessed using one or more of a threshold, a value range, fuzzy logic, pattern matching, a machine learning assessment model, or combinations thereof.

In any embodiment, data generated or detected can be forwarded to a "remote" device or location, where "remote," means a location or device other than the location or device at which the program is executed. For example, a remote location could be another location (e.g., office, lab, etc.) in the same city, another location in a different city, another location in a different state, another location in a different country, etc. As such, when one item is indicated as being "remote" from another, what is meant is that the two items can be in the same room but separated, or at least in different rooms or different buildings, and can be at least one mile, ten miles, or at least one hundred miles apart. "Communicating" information references transmitting the data representing that information as electrical signals over a suitable communication channel (e.g., a private or public network). "Forwarding" an item refers to any means of getting that item from one location to the next, whether by physically transporting that item or otherwise (where that is possible) and includes, at least in the case of data, physically transporting a medium carrying the data or communicating the data. Examples of communicating media include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the internet or cellular networks.

Claim 1:
A locking cap assembly (<NUM>), the locking cap assembly comprising:
an upper housing (<NUM>);
a lower housing (<NUM>) rotatably connected to the upper housing and configured to be fitted onto a container;
a near field communication (NFC) (<NUM>) module configured to wirelessly receive a NFC input;
an inductive charging coil (<NUM>);
a microprocessor (<NUM>); and
a latching mechanism, the latching mechanism includes:
a locking latch (<NUM>) configured to prevent the upper housing and the lower housing from rotating with respect to each other; and
an electrical actuation component (<NUM>) configured to lock and unlock the locking latch responsive to a signal received from the microprocessor and a current generated by the inductive charging coil;
wherein the lower housing includes a plurality of locking vanes (<NUM>) within the lower housing, the locking vanes being configured to variably define an inner diameter size of the lower housing responsive to a rotation of the upper housing with respect to the lower housing when the lower housing is mechanically engaged with the container,
wherein when the locking cap assembly is configured to lock onto the container by contracting the plurality of locking vanes about the container responsive to a rotation of the upper housing with respect to the lower housing in a first direction, and
wherein the microprocessor is configured to receive the NFC input from the NFC module and to unlock the locking latch and permit the rotation of upper housing with respect to the lower housing in a second direction to retract the plurality of locking vanes and release the lower housing from the container responsive to the microprocessor determining that the NFC input received by the NFC module corresponds to an authorization to release the locking cap assembly from the container.