All publications and patent applications mentioned in this specification are herein incorporated by reference for all intents and purposes to the same extent as if each individual publication or patent application was specifically and individually indicated to be incorporated by reference.
Embodiments of the disclosure relate generally to inhaler devices. Specifically, some implementations of the present disclosure relate to dry powder inhaler devices having multi-unit dose capabilities.
The present disclosure relates to inhaler devices, such as for inhaling dry powder medications to treat asthma. Inhaler devices for inhaling the contents of a capsule for medical uses are already known. Available inhalers, however, are not fully satisfactory from an operating standpoint and are susceptible to improvements.
U.S. Pat. No. 7,284,552 to Mauro Citterio, issued on Oct. 23, 2007 and entitled INHALER DEVICE, provides an example of a prior art inhaler device similar to those provided herein. The inhaler device includes an inhaler body defining a recess for a medicine capsule holding a substance to be inhaled, and a nosepiece/mouthpiece communicating with the capsule recess. The device also includes at least one perforating element coupled to the inhaler body and provided for perforating the capsule for allowing an outside airflow to be mixed with the capsule contents and inhaled through the nosepiece/mouthpiece.
U.S. Pat. No. 8,479,730 to Dominik Ziegler et al., issued on Jul. 9, 2013 and entitled INHALER DEVICE, provides another example of a prior art inhaler device. The inhaler device of the U.S. Pat. No. 8,479,730 patent is similar in construction and operation to that of the U.S. Pat. No. 7,284,552 patent, but has a mouthpiece that is pivotally attached to an edge of the inhaler body.
The above inhalers are single dose devices that require the user to perform many steps to administer each dose. What is needed and not provided by prior art inhalers are devices that require fewer steps and are easier to use.
A better understanding of the features and advantages of the present disclosure will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of the disclosure are utilized, and the accompanying drawings of which:
Referring to the reference numerals of the above-mentioned figures, an exemplary single dose inhaler device 1 is described below. As best seen in
The hole 6 is provided with a longitudinal slot (not shown), that can engage a cross tooth 8 of the peg 5, and a bottom ring-like recess, not specifically shown, in which the tooth 8 can slide.
Thus, it is possible to engage the peg 5 in the hole, by causing the tooth 8 to pass through the slot 7 and, upon achieving the bottom, it is possible to fully rotate the peg 5 in its hole 6, thereby also rotating the inhaler mouthpiece 3 with respect to the inhaler body 2.
The inhaler mouthpiece 3 can be locked in its closed condition, shown in
The inhaler body 2 is moreover provided with a recess for the capsule, the recess being upward opened and communicating with the outside through a perforated plate or grid 11, included in the inhaler mouthpiece 3 at the flange 4 and designed for separating the capsule recess 9 from the duct 12 of the mouthpiece.
A capsule 13 can be engaged in the recess 9, the capsule being of a per se known type and adapted to be perforated to allow the drug contents held therein to be easily accessed, the perforating operation being performed by any suitable perforating means.
In the disclosed embodiment, the perforating means comprise a pair of perforating needles 14 which can transversely slide as counter-urged by resilient elements comprising, in this embodiment, coil springs 15; each coil spring coaxially encompassing the perforating needle 14 and operating between a respective abutment element 16, rigid with the inhaler body 2, and a hollow push-button element 17. The perforating needles 14 may be similar to hollow hypodermic needles and have a single-side beveled tip, for facilitating the perforating needles 14 in perforating the coating of the capsule 13. In other implementations, the perforating needles 14 may be solid and or have other tip configurations.
The operation of the inhaler device according to the present disclosure is as follows. In the open condition, as shown in
Inhaler device 1 has a very simple construction. A further advantage of inhaler device 1 is the specifically designed configuration of the perforating needles that can be assimilated, as stated, to hypodermic needles. Since this type of needle presents a very small resistance against perforation and a very accurate operation, it is possible to use needles having a comparatively large diameter, without damaging the capsule, thereby providing a very simple perforating operation. The use of a small number of perforating needles, only two in some embodiments, allows reducing the contact surface between the needle and capsule (the perforated cross section being the same), with a consequent reduction of friction and of the problems affecting the prior inhalers.
Referring to
In this exemplary embodiment, inhaler device 50 is generally pear or teardrop shaped and has a main body formed by a front cover 52 and a rear cover 54. Covers 52 and 54 may be assembled with fasteners, plastic snap features, adhesives, ultrasonic welding, and/or other suitable assembly methods. A mouthpiece 56 may be provided above a capsule chamber portion 58. Mouthpiece 56 may be hingedly attached to capsule chamber portion 58 such that it pivots about a horizontal pivot axis between a closed position (as shown) and an open position (see
A pivoting mouthpiece cover 62 may be provided over mouthpiece 56. In this exemplary embodiment, mouthpiece cover 62 extends over mouthpiece 56 and includes a pair of downwardly depending arms that extend over a top portion of the front cover 52 and the rear cover 54. Mouthpiece cover 62 pivots about a horizontal axis that extends between its two arms and moves between a closed position (as shown) through about 90 degrees to an open position in which mouthpiece 56 is exposed (see
A dose count aperture 66 may be provided in front cover 52 for indicating to the user how many doses remain before device 50 is depleted, as shown in
Referring to
After mouthpiece cover 62 is rotated into the open position, the user places mouthpiece 56 against their mouth and inhales the dry powder released from the swirling capsule, as depicted in
Referring to
When device 50 is assembled, carousel 74 is rotatably received in a forward-facing lower cavity 90 of chassis 76. Carousel 74 is captivated in lower cavity 90 by front chassis cover 72, which may be secured to chassis 76 by four fasteners (not shown), or any means suitable for registration and attachment. A central hub of carousel 74 extends in a forward direction through a central aperture in front chassis cover 72 so that it can engage with dose count wheel 70. Dose count wheel 70 may be attached to carousel 74 with a single fastener through its center or any means suitable for registration and attachment so that it can rotate with carousel 74. A pair of forwardly protruding pegs or other registration features may be provided on the central hub of carousel 74 for engaging with mating recesses in the back side of dose count wheel 70 to ensure that the dose count wheel stays properly indexed with carousel 74. Sliding dose count window 68 is received within a mating slot on the inside/backside of front cover 52 which sandwiches sliding window 68 between cover 52 and wheel 70. This arrangement allows sliding window 68 to slide up and down, as will be subsequently described in more detail. Front cover 52 may be secured to the front side of chassis 76 with a single fastener (not shown), and or any other means suitable for registration and attachment.
Downfall wheel 82 is configured to be rotatably received in a rearward facing upper cavity 92 of chassis 76. Downfall wheel is captivated in upper cavity 92 by rear cover 54, which may be secured to the backside of chassis 76 by three fasteners (not shown), and or any other means suitable for registration and attachment.
Piercing hub 80 may be provided with two piercing pins or sharps 94 configured to pierce the same side of a medicine capsule on opposite hemispherical ends of the capsule (perpendicular to the longitudinal axis of the capsule), rather than piercing the capsule through its ends along the longitudinal axis as done by the previously described device 1. When device 50 is assembled, piercing hub 80 resides in the central bore of downfall wheel 82. Hub 80 has a forward extending axle that is received in mating bore 96 in upper cavity 92 of chassis 76, and a rearward extending axle that is received in mating bore 98 in the inside surface of rear cover 54. With this arrangement, piercing hub 80 is configured to pivot about a front to back horizontal axis allowing piercing pins to rotate between a lower position and an upper position, as will be subsequently described in more detail. Torsion hub spring 78 may be provided between hub 80 and chassis 76 to bias piercing pins 94 towards the lower position. In other embodiments (not shown), a four-bar mechanism may be used instead of a rotating piercing hub to move piercing pins 94 into the capsules.
Latch arm 84 may be configured to slide up and down in a vertical channel formed between the backside of chassis 76 and the inside of rear cover 54. Latch arm 84 serves to prevent mouthpiece cover 62 from returning to or staying in its upper position covering mouthpiece 56 until after mouthpiece 56 has been opened and closed, as previously described. Details of the construction and operation of latch arm 84 will be subsequently described.
Drive plate 88 may be configured to reside in a mating recess 100 in the rear arm of mouthpiece cover 62, such that drive plate 88 rotates with cover 62. Drive plate 88 includes a circumferentially extending flexure arm 102 and tooth 85 that extends through an arcuate slot in rear cover 54 to allow mouthpiece cover 62 to rotationally drive downfall wheel 82 ninety degrees at a time, as will be subsequently described in detail. Mouthpiece cover spring 86 may be provided between drive plate 88 and rear cover 54 to bias mouthpiece cover 62 towards its lower/open state. In some embodiments, features of drive plate 88 may be provided directly into mouthpiece cover 62 and the drive plate itself may be omitted.
Mouthpiece 56 may be provided with hinge features along its rear edge (not shown) for mating with hinge features 104 on the rear top edge of chassis 76. This arrangement allows mouthpiece 56 to pivot about a longitudinal horizontal axis between a closed position and an open position.
Rear cover 54 may be provided with an inwardly facing upper ramp 115, as shown. The function of ramp 115 is described below in the discussion of
Referring to
During operation, downfall wheel 82 rotates counterclockwise (as viewed from the rear of device 50) and carousel 74 rotates clockwise. Downfall wheel 82 indexes 90 degrees at a time and carousel 74 indexes 22.5 degrees. Drive plate 88 (
Referring to
Referring to
Referring to
Referring to
Downfall wheel 82 may be provided with solid surfaces 131 between the capsule spaces 128 for sealing off the bottom of the swirl chamber for use once a capsule has been loaded into the chamber so that air does not enter the chamber from the bottom, or airflow is at least reduced and any gap can be controlled to achieve a desired resistance as a system. As best seen in
Referring to
A spirally extending groove 136 may be provided on the front side of dose count wheel 70 as shown. A mating protrusion (not shown) may be provided on the back side of sliding dose count window 68 (shown in
Referring to
Referring to
Referring to
Starting with
In
In
In
In
Referring to
As best seen in
In some embodiments (not shown), inhaler device is configured without the above-described interlock features such that a mouthpiece cover may be opened and closed and another drug delivery cycle started without regard to whether the mouthpiece has been opened and closed first.
In the exemplary embodiment disclosed herein, inhaler device 50 is configured so that a user may hold the device and operate all of its functions with one hand, or may hold the device with one hand and operate it with the other hand. The cost of goods for device 50 is such that it can be recycled or otherwise disposed of after all its capsules have been depleted. In some implementations, device 50 may be reloaded with new capsules and reused after it has been cleaned and or sterilized. In some implementations, the inhaler device may be configured such that an empty carousel, cartridge or other capsule carrying device may be easily removed from the inhaler device by the end user or a provider of the inhaler device and replaced with a full capsule carrying device.
In some embodiments, “smart device” features may be incorporated into inhaler device 50. For example, device 50 may be configured to record the time, date, location, doses remaining and or user input(s) whenever a dose cycle has been started and or completed. Some or all of this data and or additional data may be stored on the device for later retrieval and or it may be transmitted by wire or wirelessly to another device, such as a smartphone, tablet, laptop computer, desktop computer, computer network or other device. A data recording and or transmitting event may be triggered by a mouthpiece cover being opened or closed, by a mouthpiece being opened or closed, by an automatic sensing of airflow through a mouthpiece, by a user input, by a preset time and or by one or more other triggers. These events may be referred to as “delivery signatures” triggered by “a deflection component” activating a “sensor component”, such as a cam surface actuating a microswitch. Each of these components is now further described in greater detail.
As reviewed above, aspects of the disclosure include systems and devices that comprise a sensor component. Sensor components in accordance with embodiments of the disclosure are configured to acquire one or more data inputs from the subject systems and devices, or from the immediate vicinity of the subject systems and devices, and to transmit a report comprising a drug dose completion signal when a delivery signature is detected. In certain embodiments, the report transmitted by the sensor component includes additional information, such as, e.g., one or more drug identification characteristics (described further herein).
In some embodiments, a sensor component may include a sound sensor (e.g. a microphone) or pressure sensor to detect data related to the quality of the inhalation (e.g. peak flow rate, average flowrate, peak pressure, inhaled volume, duration of inhalation, etc.)
In some embodiments, a sensor component comprises a circuit board component that is configured or adapted to mechanically support and electrically connect one or more electronic components of a subject sensor. Circuit board components in accordance with embodiments of the disclosure can include, without limitation, printed circuit boards, etched circuit boards, flexible circuit boards, or any combination thereof. In some embodiments, a circuit board component comprises a printed circuit board (PCB).
Circuit board components in accordance with embodiments of the disclosure can comprise conductive tracks, pads, or other features that are etched from conductive sheets (e.g., copper sheets) that are attached to a non-conductive substrate. In certain embodiments, standard circuit components, such as, e.g., capacitors, resistors, memory components, and the like, are electrically connected to a circuit board component (e.g., are soldered to a PCB). Connection of one or more electronic circuit components to a PCB results in a printed circuit assembly (PCA) or a printed circuit board assembly (PCBA), which terms are used interchangeably herein.
Aspects of the disclosure include switches that are configured to establish or break an electrical contact in a subject circuit board component in response to an external stimulus (e.g., in response to an external mechanical stimulus). In some embodiments, a circuit board component comprises a momentary contact switch that is configured to establish or break an electrical contact only while the momentary contact switch is in an activated state. In some embodiments, a circuit board component comprises a non-momentary contact switch that is configured to establish or break an electrical contact until the non-momentary switch is activated again.
In some embodiments, a sensor component comprises a position sensor that is configured or adapted to permit position measurement of one or more components of the subject drug delivery systems and devices. For example, in some embodiments, a position sensor is configured to detect and/or measure a position of an actuation component and/or a deflection component. In some embodiments, a position sensor is configured to detect an orientation of one or more components of a subject device. Position sensors in accordance with embodiments of the disclosure can be absolute position sensors or relative position sensors, and can be linear, angular or multi-axis position sensors. In some embodiments, a position sensor is configured to acquire a plurality of measurements over a defined time interval, or during execution of a drug delivery procedure, in order to measure a position of one or more components of the subject systems or devices, either as a function of time, or as a function of progression through the drug delivery procedure.
In some embodiments, a sensor component and/or a deflection component comprises a force sensor that is configured or adapted to detect and/or measure one or more forces in one or more components of the subject drug delivery systems and devices. Force sensors in accordance with embodiments of the disclosure can be absolute or relative force sensors. Non-limiting examples of force sensors include electrical resistance strain gauges, elastic strain gauges, foil strain gauges, semiconductor strain gauges, thin-film strain gauges, wire strain gauges, piezoelectric force transducers, strain gauge load cells, inductive sensors, and the like.
In some embodiments, a sensor component comprises a light sensor that is configured or adapted to detect and/or measure ambient light. For example, in some embodiments, a light sensor is configured to determine whether an amount of ambient light in the vicinity of a subject drug delivery system or device is above a predetermined threshold value. Light sensors in accordance with embodiments of the disclosure can be absolute or relative light sensors. In some embodiments, a light sensor is used to detect an increase in ambient light, thereby indicating that a subject device has been removed from its packaging, removed from a storage container, and/or removed from a dark location.
In some embodiments, a sensor component comprises a motion sensor that is configured or adapted to detect and/or measure motion of a subject drug delivery system or device. For example, in some embodiments, a motion sensor is configured to determine whether a device, or component thereof, moves more than a predetermined threshold value. Motion sensors in accordance with embodiments of the disclosure can be absolute or relative motion sensors. In some embodiments, a motion sensor is used to detect motion of a subject device, thereby indicating that a user has begun interacting with the device.
In some embodiments, a sensor component comprises a temperature sensor that is configured or adapted to detect and/or measure a temperature of one or more components of the subject systems or devices. For example, in some embodiments, a temperature sensor is configured to determine whether the temperature of a drug is above a predetermined threshold value or is within a predetermined temperature range. Temperature sensors in accordance with embodiments of the disclosure can be absolute or relative temperature sensors. In some embodiments, a temperature sensor is used to detect an increase in temperature, thereby indicating that a subject device has been removed from cold storage and has reached a temperature that is suitable for administration of the drug to a patient. In some embodiments, a temperature sensor is used to determine when a cold chain is broken (i.e., when the temperature of the device or a portion thereof rises above a predetermined threshold temperature) and to record this information. In some embodiments, a temperature sensor is used to track when the device or a portion thereof rises above a predetermined threshold temperature, and to wake up the device when the temperature reaches the predetermined threshold temperature to record an inhalation procedure. Any information relating to the cold chain of the device can be recorded and used for purposes of information tracking and/or for preparing the device for use. In some embodiments, the device is configured to wake up from a deep sleep, read the temperature from the sensor and go back to sleep. This process may be performed with low power levels once per minute or other frequency to allow long term storage of the device. In some embodiments, this process may be performed for up to 5 years on a single battery, due to fast action of the microprocessor and selective power up of only circuit components needed to read a temperature.
In some embodiments, a sensor component comprises a touch sensor that is configured or adapted to detect and/or measure contact by an object that is conductive, or that has a dielectric value that is different from air. In some embodiments, a touch sensor comprises one or more detection components (e.g., capacitive sensing components) that are placed in close proximity to, or on, the inside of an external surface of a subject drug delivery system or device and are electrically connected to the touch sensor. When a user touches a detection component, an electrical signal is sent to the touch sensor, indicating that the user has touched the device. In some embodiments, a touch sensor is used to determine that a user has made physical contact with a subject device (e.g., that a portion of a user's skin has made physical contact with a subject device), thereby indicating that the user has begun interacting with the device.
Aspects of the subject sensor components include a power component that is configured or adapted to provide electrical power to the sensor component. In some embodiments, a power component comprises a battery. In some embodiments, a power component comprises a rechargeable battery. In certain embodiments, such as, e.g., where one or more components are disposable, a power component does not include a rechargeable battery. In some embodiments, a power component comprises one or more standard electrical cords that are configured to supply electrical power to a sensor component by establishing electrical contact with an external power source (e.g., a standard electrical outlet). In some embodiments, a subject system or device comprises an on/off switch or button that can be used to turn power to the system or device on or off, as desired.
In some embodiments, a sensor component comprises a memory component that is configured or adapted to store one or more drug identification characteristics therein. Memory components in accordance with embodiments of the disclosure can be volatile or non-volatile memory components. In some embodiments, a memory component is encoded with one or more drug identification characteristics before it is connected to the sensor component (e.g., the memory component is encoded with one or more drug identification characteristics at the time the memory component is manufactured). In some embodiments, a memory component is encoded with one or more drug identification characteristics after the memory component has been connected to the sensor component. In certain embodiments, a sensor component comprises a data acquisition component that is configured to acquire the one or more drug identification characteristics that are stored in the memory component from an external source (e.g., from an external encoder, or from a memory component on a drug carousel or cartridge). In some embodiments, a memory component is configured to wirelessly receive encoded information (e.g., a data acquisition component is configured to wirelessly acquire the one or more drug identification characteristics). In some embodiments, a sensor component comprises a near-field communication (NFC) component and/or a radio frequency identification (RFID) component that are configured for data exchange.
Drug identification characteristics in accordance with embodiments of the disclosure broadly include any information relating to a drug's identity and/or its biochemical characteristics (including, but not limited to, a drug's name, concentration, dose, dosage, serial number, lot number, universal unique identifier (UUID), expiration date, manufacturing date, site of manufacture, or any combination thereof). In some embodiments, a memory component can further comprise one or more patient identification characteristics (including, but not limited to: a patient name, patient identification number, prescription number, demographic information, patient group or subgroup, or any combination thereof). In some embodiments, a memory component can further comprise one or more drug delivery device identification characteristics (including, but not limited to: a system or device name, type, model number, serial number, lot number, date of manufacture, place of manufacture, UUID, or any combination thereof). In some embodiments, a memory component is configured to be programmed (e.g., during manufacture of the device) using over-the-air transmission with a universal unique identifier (UUID).
Aspects of the subject sensor components include a wireless transmitter module that is configured to wirelessly transmit data to a networked device (e.g., a data management component). In some embodiments, a networked device is a secure networked device. In some embodiments, transmitted data can be encrypted. In some embodiments, a wireless transmitter module is configured to communicate with one or more networked devices using a wireless transmission component (e.g., a communication link that utilizes, e.g., infrared light, radiofrequency, optical or ultrasound waves, or any combination thereof). Networked devices in accordance with embodiments of the disclosure broadly include any device or component that communicates with at least one other device over a communication link. Non-limiting examples of networked devices include mobile computing devices (e.g., smart phones, laptop computers) that use, e.g., Bluetooth, Bluetooth low energy (BLE), or Wi-Fi connections. In some embodiments, a wireless transmitter module is configured to wirelessly communicate directly with a network or directly with a remote computing device (i.e., without first communicating with a mobile computing device). In certain embodiments, a wireless transmitter module comprises an antenna. Aspects of the disclosure broadly include any radio wave spectrum communication systems, including but not limited to those that can communicate to a central hub, and then into a cloud-based computing/data transmission environment.
Sensor components in accordance with embodiments of the disclosure are configured to transmit a report comprising a drug dose completion signal when the sensor component detects a delivery signature. In some embodiments, a drug dose completion signal comprises an indication that an actuation component has completed a delivery stroke. In some embodiments, a data management component is configured to determine a volume of drug that was delivered to the patient by identifying the drug delivery system or device and determining the volume of drug that is administered in a single delivery stroke of the identified system or device. In some embodiments, a data management component is encoded with information relating to, e.g., a volume of a drug that is administered in a single delivery cycle of a specified system or device.
In some embodiments, a subject sensor component is configured or adapted to determine one or more operational states of a drug delivery system or device. For example, in some embodiments, a sensor component is configured to determine a ready state, wherein the system or device is ready to administer a drug dose to the patient. In some embodiments, a sensor component is configured to determine an unready state, wherein the system or device is not ready to administer a drug dose to the patient. In some embodiments, a sensor component is configured to determine a dose-in-progress state, wherein the system or device is actively administering a drug dose to the patient. In some embodiments, a subject system or device can be configured to administer a drug dose to a patient over a time frame that ranges from about 1 second up to about 30 minutes, such as about 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, or 60 seconds, or about 1, 2, 3, 4, 5, 6, 7, 8, 9 or 10 minutes or more, such as about 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28 or 29 minutes or more. In some embodiments, a subject system or device is configured to remain in a dose-in-progress operational state for a period of time that is equal to the time frame for administering the drug to the patient.
In some embodiments, a sensor component is configured to determine a sleep mode state (e.g., a low power state), wherein the system or device is operating in reduced power mode and is not ready to administer a drug dose to the patient. In some embodiments, a sensor component is configured to determine a low battery state, wherein the battery charge is below a predetermined level.
Determination of any of the states described herein can be accomplished by analysis of one or more inputs from one or more of the subject sensor components. For example, in some embodiments, a ready state can be determined when a temperature value from a temperature sensor falls within a predetermined range (i.e., indicating that the drug is at a desired temperature range for administration) and a position sensor indicates that the system or device is in a desired position or orientation for administration (e.g., a position of an actuation component is determined to be correct for administration of the drug to the patient). This arrangement can also be used for training the user on correct ‘inhalation posture’ orientation. In some embodiments, this may be done in conjunction with the correct inhalation posture orientation being shown on the graphical user interface of the user's mobile device.
In some embodiments, a sensor component can communicate a determined operational state, as described above, to another component of the system or device (e.g., to a data management component). In certain embodiments, the data management component can then indicate the operational state to a user (e.g., on a GUI), thereby communicating the operational state to the user. In some embodiments, as described further herein, the subject systems and devices can comprise one or more indicator components that are configured to communicate an operational state of the system or device to a user (e.g., a “ready to inhale” operational state).
Sensor components in accordance with embodiments of the disclosure can be mounted in any suitable location on the subject systems or devices. For example, in some embodiments, a sensor component can be mounted in a housing that is positioned anywhere on the system or device. In certain embodiments, a sensor component is formed into a single unit. In certain embodiments, a sensor component comprises two or more individual units (e.g., two or more different PCBAs) that are electrically connected to one another, each of which is mounted in a suitable location on a subject drug delivery system or device.
Aspects of the disclosure include one or more deflection components that are configured to generate a delivery signature when a delivery stroke has been completed. The subject drug delivery systems and devices are configured to transmit a report comprising a drug dose completion signal only when a delivery signature has been generated and detected.
Deflection components in accordance with embodiments of the disclosure can be positioned in any suitable location on the subject systems or devices so that they can interact with one or more components of the subject systems and devices during the execution of a delivery cycle. In some embodiments, a deflection component is located along the length of an actuation component and is configured to be mechanically deflected by at least a portion of the system or device during a delivery cycle. In some embodiments, a deflection component comprises a force sensor that is configured to measure one or more forces applied to a portion of a subject system or device by a user. In some embodiments, a deflection component comprises one or more inductive sensor coils that are configured to move toward one or more detection targets in response to a force applied to one or more components of a subject system or device.
As reviewed above, in some embodiments, a deflection component comprises a force sensor. Force sensors in accordance with embodiments of the disclosure can be absolute or relative force sensors, and details of such sensors are generally known in the art.
In certain embodiments, a deflection component comprises one or more inductive sensor coils that are configured to move toward a detection target in response to a force that is applied to a portion of the subject systems and devices during a delivery stroke. Inductive sensor coils in accordance with embodiments of the disclosure generally operate by generating an alternating electrical field that can detect a conductive material within a certain proximity of the inductive sensor coil. As such, inductive sensor coils in accordance with embodiments of the disclosure generally operate in conjunction with one or more detection targets that comprise a conductive material (e.g., a conductive metal material). The configuration of an inductive sensor coil and its detection target can take on any suitable arrangement. For example, in some embodiments, a first inductive sensor coil is disposed on a base portion of a deflection component, and the base portion is configured to deflect towards the detection target when a force is applied to the base portion by a user during a delivery stroke. In some embodiments, an inductive sensor coil is disposed on an extension component that is configured to move through a portion of a subject device during a delivery stroke and is configured to pass one or more portions of a detection target during the delivery stroke.
Detection targets in accordance with embodiments of the disclosure can have any number of different geometries. For example, in some embodiments, a detection target has a uniform geometry that does not change significantly as function of position in a given direction. Non-limiting examples of uniform geometry detection targets include geometric shapes (e.g., rings, bands, rectangles, and squares). In some embodiments, a uniform geometry detection target can be placed on an internal or an external surface of a subject device and can be detected when an inductive sensor coil passes the detection target and/or moves towards it. In certain embodiments, a detection target with a uniform geometry is disposed over at least half of a surface of a subject system or device.
In some embodiments, a detection target has a repeating geometry, wherein two or more uniform geometry detection targets are disposed in a repeating manner in a given direction along a surface of a subject device. For example, in some embodiments, two or more circular or square detection targets can be disposed in series along the length of a device component. As an inductive sensor coil passes each uniform target, the progression of the delivery stroke can be determined.
In some embodiments, a detection target has a variable geometry, wherein one or more dimensions of the detection target change as a function of position in a given direction. For example, in some embodiments, a variable detection target comprises a conductive material that starts at a minimum width at a first end of a device component, and the width gradually increases along the length of the component to a final maximum width at the other end of the component. Any number of variations in the variable geometry can be introduced to generate a unique reading, or signature, that is obtained as an inductive sensor coil moves past the variable geometry detection target.
As reviewed above, aspects of the disclosure include detection of a delivery signature by a subject sensor and/or data management component. Delivery signatures in accordance with embodiments can comprise any of a variety of data components. For example, in embodiments where a deflection component comprises a plurality of trigger switches, a delivery signature can comprise data relating to a deflection order of the trigger switches, a deflection duration of each trigger switch, one or more time intervals corresponding to a time between a deflection of a first trigger switch and a deflection of a second trigger switch, or any combination thereof.
In embodiments where a deflection component comprises a first and second inductive sensor coil and a first and second detection target, a delivery signature can comprise a detection signal from the first and second inductive sensor coils, corresponding to detection of the first and second detection targets. In such embodiments, where the second detection target comprises a uniform geometry, a delivery signature can comprise detection of the uniform geometry of the second detection target by the second inductive sensor coil, which can be located on an extension component of the deflection component. Further, in such embodiments, where the second detection target comprises a repeating geometry, a delivery signature can comprise detection of the repeating geometry by the second inductive sensor coil, which can be located on an extension component of the deflection component. Additionally, in embodiments where a detection target comprises a variable geometry, a delivery signature can comprise a detection signal from one or more attributes of the variable geometry, such as a proportional signal.
Delivery signatures in accordance with embodiments of the disclosure can have a characteristic shape that is indicative of an inhalation profile. Aspects of the disclosure involve detecting all or a portion of a delivery signature in order to measure a progression of a delivery profile or a completion of a delivery profile. In some embodiments, a delivery signature is detected and/or analyzed by a sensor component. In some embodiments, a delivery signature is detected and/or analyzed by a data management component. In some embodiments, a delivery signature is compared to a reference signature, and if the delivery signature matches the reference signature within acceptable tolerance levels, a successful delivery profile is recorded. In some embodiments, a data management component is programmed with one or more algorithms that are adapted to apply a set of rules to determine whether a delivery signature sufficiently conforms to a predetermined reference signature.
In one embodiment, a delivery signature is generated when a plurality of trigger switches is deflected in a given direction for a specified period of time. For example, when all of the trigger switches in a trigger switch assembly are deflected in for a specified period of time (e.g., for 3 or more seconds, such as 4, 5, 6, 7, 8, 9, and 10 or more seconds), the data management component determines that the delivery signature conforms to a reference signature.
Aspects of the disclosure include actuation components that are configured to move, thereby causing a capsule to be dispensed from a capsule space into a swirl chamber. Actuation components in accordance with embodiments of the disclosure can generally be actuated by any suitable mechanism. In some embodiments, an actuation component is configured to be moved manually by a user. In some embodiments, an actuation component is configured to be moved automatically by one or more driver components (e.g., one or more mechanical, electrical, or electromechanical controllers).
In some embodiments, an actuation component can include a controller that is coupled to one or more assemblies or subassemblies of the subject systems or devices. The controller can be configured or adapted (e.g., programmed, if the controller comprises an electrical or electromechanical component) to move the actuation component in response to a user input or an activation signal.
In some embodiments, an actuation component can comprise one or more coupling components that are configured or adapted to mechanically connect the actuation component to one or more additional components of the subject systems or devices. Coupling components in accordance with embodiments of the disclosure broadly include threaded couplers, adhesive couplers, snap-fit couplers, magnetic couplers, or any combination thereof.
Aspects of the disclosure include indicator components that are configured or adapted to communicate one or more operational states of the subject drug delivery systems or devices to a user. In use, a given operational state of a subject drug delivery system or device can be assigned a specific indicator signal, and the subject indicator components can be used to communicate the specific indicator signal to a user, thereby indicating to the user that the system or device is in the indicated operational state. Indicator components in accordance with embodiments of the disclosure broadly include visual, haptic and auditory indicators, each of which is described in further detail herein.
Aspects of the disclosure include visual indicator components that are configured or adapted to display a visual signal regarding an operational state of a subject system or device to a user. In some embodiments, a visual indicator comprises a light-emitting component. Light emitting components in accordance with embodiments of the disclosure include, without limitation, light emitting diodes (LEDs) and organic light emitting diodes (OLEDs). In some embodiments, a visual indicator comprises a light pipe (also referred to as a light tube). In some embodiments, a light pipe comprises a hollow structure that is configured to contain light within the structure by utilizing a reflective lining. In some embodiments, a light pipe comprises a transparent solid material that is configured to contain light within the material by utilizing total internal reflection. In some embodiments, a visual indicator comprises a diffuser component (e.g., a light pipe diffuser) that is configured to uniformly spread a visual signal (e.g., light from an LED) over a defined area. In some embodiments, a visual indicator component comprises a light pipe and a light pipe diffuser. Visual indicator components in accordance with embodiments of the disclosure can be configured or adapted to generate visual signals having any color (e.g., red, orange, yellow, green, blue, purple) or any combination thereof. In some embodiments, an operational state of a subject system or device can be assigned a specific color. For example, in one embodiment, an unready operational state is assigned the color red, and when the system or device is in an unready state, a red color is displayed to a user using a visual indicator component. In some embodiments, a visual indicator component can be configured to flash a visual indicator on and off in a particular sequence (e.g., a series of three short flashes) or to remain constantly on to provide an indication of an operational state. Other indicator settings in accordance with embodiments of the disclosure include attempting to connect to a data management component (e.g., flashing yellow or blue indicator light), and connected to a data management component (e.g., flashing or solid green or blue indicator light). Any of a variety of “ready” or “unready” states can be indicated to a user. For example, in some embodiments, an indicator component is configured to indicate that a capsule storage component has reached a suitable temperature for use. In some embodiments, an indicator component is configured to indicate to a user that the device is attempting to connect to a wireless network or a data management component. In some embodiments, an indicator component is configured to indicate to a user that the device is connected to a wireless network or a data management component. In some embodiments, indicator component(s) can be located on a GUI of a mobile device.
Aspects of the disclosure include haptic indicator components that are configured or adapted to generate one or more vibration signals that are specific to an operational state of a subject system or device. In some embodiments, a haptic indicator comprises a vibration generator component. Vibration generator components in accordance with embodiments of the disclosure are configured or adapted to generate vibrations having any desired combination of amplitude, frequency and duration in order to generate a plurality of unique vibration signals. For example, in one embodiment, an unready operational state can be assigned a vibration signal that consists of a single, high amplitude vibration that has a duration of one second.
Aspects of the disclosure include auditory indicator components that are configured or adapted to generate one or more auditory signals that are specific to an operational state of a subject system or device. In some embodiments, an auditory indicator comprises a sound generator component. Sound generator components in accordance with embodiments of the disclosure are configured or adapted to generate a plurality of unique sounds having a plurality of different tones and/or volumes. For example, in one embodiment, an unready operational state can be assigned a sound that consists of a single, high-volume buzzer sound.
Indicator components in accordance with embodiments of the disclosure can be mounted in any suitable location on the subject systems or devices. For example, in some embodiments, an indicator component can be mounted in a housing that is positioned anywhere on the system or device. In some embodiments, an indicator component can comprise a plurality of individual components that work in concert to generate a desired indicator signal. For example, in one embodiment, a visual indicator component comprises an LED that generates a visible light signal, and also comprises a light pipe that transfers the visible light from the LED to one or more locations on the subject system or device. In some embodiments, a visual indicator further comprises a light pipe diffuser that evenly spreads the visible light signal over a desired location (e.g., over an entire indicator window).
Aspects of the disclosure include one or more housing components that are formed from suitable materials, such as, e.g., ceramic, plastic, metal, or any combination thereof. In some embodiments, one or more individual components of the subject drug delivery systems or devices can be located within a single housing and formed into a single unit. In some embodiments, one or more components of the subject systems or devices can be located in a first housing component, and one or more additional components of the subject systems or devices can be located in a second housing component, and the first and second housing components can be operably coupled to one another to form a single unit.
In some embodiments, a housing comprises one or more transparent or semitransparent windows that are made of a material that is at least partially transparent to light and is configured to allow ambient light to pass through the housing to reach a light sensor positioned therein. In some embodiments, a housing comprises one or more windows or openings that allow one or more components of the systems or devices to physically pass through.
Aspects of the disclosure include a data management component that is configured or adapted to communicate with the subject systems or devices and/or a user, e.g., to receive a report comprising a drug dose completion signal from a subject system or device, to send one or more commands to a subject system or device, or to send a reminder to a user that a drug dose is due to be administered at a certain time. In some embodiments, a data management component comprises a computer (e.g., a personal computer, a networked computer or a network server). In some embodiments, a data management device comprises a mobile computing device (e.g., a smart phone, or a laptop computer). In some embodiments, a data management component is an Internet-enabled device that is capable of sending and receiving information over the Internet. In some embodiments, a data management component comprises an application that is configured to manage one or more aspects relating to administration of a drug to a user (e.g., to record administration of individual drug doses to a patient, to remind a patient regarding upcoming drug dose administrations, to validate one or more drug identification characteristics by interacting with a remote database, etc.). In some embodiments, a data management component is configured to indicate to a user that one or more communication components are operational and/or are connected to one or more additional components of the subject drug delivery systems or devices. For example, in some embodiments, a data management component is configured to indicate to a user that the data management component is connected (e.g., via a Bluetooth or Wi-Fi connection) to a subject drug delivery system or device. In some embodiments, one or more indicator components on a subject drug delivery system or device, as described above, can further be used to indicate to a user that the data management component is connected to the system or device. Any suitable combination of indicator components on the data management component and/or the other components of the system or device can be used to indicate a connection status of the data management component to a user (e.g., connected, attempting to connect, not connected, disconnected, etc.).
In some embodiments, a data management component is configured or adapted to receive a report from a subject drug delivery system or device, and to record one or more aspects of the report for purposes of maintaining a patient's medical record/history. For example, in some embodiments, a data management component is configured to receive a report from a system or device that indicates a drug dose was administered to the patient, and the data management component records administration of the drug dose, including the date and time at which the drug dose was delivered. In some embodiments, a report can contain additional information relating to, e.g., the drug that was administered or the patient that received the drug. In some embodiments, a report can contain information relating to one or more operational states of the subject systems or devices. For example, in some embodiments, a report comprises information relating to, e.g., the temperature or temperature history of a system or device. In some embodiments, a report comprises information relating to a geographical location of the drug delivery system at the time of administration.
In some embodiments, a data management component is configured or adapted to receive one or more data inputs from a subject system or device, and to validate the one or more data inputs prior to proceeding with administration of the drug to the patient. For example, in some embodiments, a data management component is configured to receive a drug identification characteristic from a subject system or device and to verify that the drug identification characteristic is valid before proceeding with administration of the drug to the patient. In some embodiments, a data management component is configured to transmit one or more drug identification characteristics over the Internet to a remote database, and to receive an authentication signal in response, prior to administering the drug to the patient.
In some embodiments, a data management component is configured or adapted to receive one or more data inputs from a subject system of device, and to analyze the received data to determine whether a delivery stroke has been completed. For example, in some embodiments, a subject system or device is configured or adapted to transmit data from a deflection component and/or a sensor to a data management component, and to analyze the received data and compare the received data to one or more stored delivery signature parameters (e.g., a reference delivery signature) to determine whether the received data corresponds to a delivery signature for the device.
In some embodiments, a data management component is configured or adapted to determine whether a specific drug delivery system or device, or a component thereof is the result of an authorized sale from a manufacturer, and/or an authorized prescription of the drug from a prescribing health care provider (e.g., from a prescribing physician), in a specific geographical location (e.g., in a specific country). For example, in some embodiments, a data management component is configured to receive one or more drug identification characteristics from a subject drug delivery system or device (or a component thereof, e.g., a drug carousel or cartridge), and to transmit the one or more drug identification characteristics to a remote database. In some embodiments, a data management component is further configured or adapted to transmit a geographical location of the drug delivery system or device to the remote database as well. In some embodiments, a remote database is configured or adapted to compare the one or more drug identification characteristics with the geographical location received from the data management component to determine whether a specific drug delivery system or device, or component thereof (e.g., a drug capsule carousel or cartridge), is being used in the geographical location (e.g., the specific country) where it was sold.
In some embodiments, a data management component is configured to validate one or more operational states of the subject systems or devices prior to administration of the drug to the patient. For example, in one embodiment, a data management component is configured to determine whether a drug capsule is at a temperature that falls within a predetermined acceptable temperature range prior to administering the drug to the patient. In some embodiments, a data management component is configured to verify that a subject system or device is in a “ready” operational state prior to administering the drug to the patient.
Data management components in accordance with embodiments of the disclosure are configured to determine a date and time at which a drug is administered to a patient (e.g., a time stamp for the drug dose administration). In some embodiments, a data management component is configured to receive a drug dose completion signal from a subject system or device and is configured to determine the exact time of the drug administration based on additional information transmitted from the system or device. For example, in some situations, a subject system or device may not be operatively connected to a data management component at the specific date and time at which administration of the drug was carried out. In such instances, a subject system or device is configured to determine an elapsed time since completion of the drug administration procedure. When the system or device becomes connected to the data management component, a drug dose delivery signal as well as the elapsed time since the administration is transmitted to the data management component. The data management component then utilizes the transmitted information to back-calculate the specific date and time at which the drug administration procedure was completed and records this information in the patient's records.
In some embodiments, a subject system or device can comprise a controller, a processor, and a computer readable medium that are configured or adapted to control or operate one or more components of the subject systems or devices. In some embodiments, a system or device includes a controller that is in communication with one or more components of the subject systems of devices and is configured to control aspects of the systems or devices and/or execute one or more operations or functions of the subject systems or devices. In some embodiments, a system or device includes a processor and a computer-readable medium, which can include memory media and/or storage media. Applications and/or operating systems embodied as computer-readable instructions on the computer-readable memory can be executed by the processor to provide some or all of the functionalities described herein.
In some embodiments, a subject system or device includes a user interface, such as a graphical user interface (GUI), that is configured or adapted to receive an input from a user, and to execute one or more of the methods as described further herein. In some embodiments, a GUI is configured to display data or information to a user.
Aspects of the disclosure include energy harvesting systems coupled to a drug delivery device as disclosed herein. The use of an energy harvesting system allows the drug delivery device to harvest energy from its surrounding to power on-board communication electronics. This reduces or eliminates the need for a battery located on the device. In turn, this reduces challenges associated with environmentally friendly disposal of the devices, which are often disposable type devices. In some embodiments, mechanical energy is stored in a spring or similar means and this energy is recaptured at the time of use, such as at the end of inhalation or drug delivery cycle. In some embodiments, the spring or other storage mechanism supplies a generator with mechanical energy that is converted to electrical energy, rectified and regulated to power a wireless transmission from the drug delivery device to a mobile device or home-based receiver or hub. As previously described, this wireless transmission can provide drug delivery dose completed confirmation via smart device technology.
Various connection methods may be employed to wirelessly connect the self-powered drug delivery device to a user's smartphone. These may be segmented into direct and indirect methods:
Direct Methods—Communication Requiring No External Peripherals
Indirect Methods—Communication Requiring External Peripherals/Infrastructure
In some embodiments of energy harvesting, BLE (Bluetooth Low Energy) “non-connectable” may be chosen due to it being a widespread and mature technology. With this approach, a connection does not need to be initiated between the device and phone, thereby reducing power consumption. In some embodiments, at least 1.04mJ is required to be delivered to a BLE module to perform the types of communications described herein. Because of energy losses between a power generating device and a BLE module, in some embodiments it is desirable to have a generator output of approximately 10mJ.
According to aspects of the disclosure, the energy harvesting source may comprise:
In the magnetic inductive category, the energy harvesting source may be of one of the following design configurations:
Further details of the above-described “smart device” features may be found in co-pending published U.S. applications 2019/0321555 and 2021/0046247, incorporated herein by reference.
When a feature or element is herein referred to as being “on” another feature or element, it can be directly on the other feature or element or intervening features and/or elements may also be present. In contrast, when a feature or element is referred to as being “directly on” another feature or element, there are no intervening features or elements present. It will also be understood that, when a feature or element is referred to as being “connected”, “attached” or “coupled” to another feature or element, it can be directly connected, attached or coupled to the other feature or element or intervening features or elements may be present. In contrast, when a feature or element is referred to as being “directly connected”, “directly attached” or “directly coupled” to another feature or element, there are no intervening features or elements present. Although described or shown with respect to one embodiment, the features and elements so described or shown can apply to other embodiments. It will also be appreciated by those of skill in the art that references to a structure or feature that is disposed “adjacent” another feature may have portions that overlap or underlie the adjacent feature.
Terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. For example, as used herein, the singular forms “a” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items and may be abbreviated as “/”.
Spatially relative terms, such as “under”, “below”, “lower”, “over”, “upper” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if a device in the figures is inverted, elements described as “under” or “beneath” other elements or features would then be oriented “over” the other elements or features. Thus, the exemplary term “under” can encompass both an orientation of over and under. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly. Similarly, the terms “upwardly”, “downwardly”, “vertical”, “horizontal” and the like are used herein for the purpose of explanation only unless specifically indicated otherwise.
Although the terms “first” and “second” may be used herein to describe various features/elements (including steps), these features/elements should not be limited by these terms, unless the context indicates otherwise. These terms may be used to distinguish one feature/element from another feature/element. Thus, a first feature/element discussed below could be termed a second feature/element, and similarly, a second feature/element discussed below could be termed a first feature/element without departing from the teachings of the present disclosure.
Throughout this specification and the claims which follow, unless the context requires otherwise, the word “comprise”, and variations such as “comprises” and “comprising” means various components can be co-jointly employed in the methods and articles (e.g., compositions and apparatuses including device and methods). For example, the term “comprising” will be understood to imply the inclusion of any stated elements or steps but not the exclusion of any other elements or steps.
As used herein in the specification and claims, including as used in the examples and unless otherwise expressly specified, all numbers may be read as if prefaced by the word “about” or “approximately,” even if the term does not expressly appear. The phrase “about”, “approximately” or “generally” may be used when describing magnitude and/or position to indicate that the value and/or position described is within a reasonable expected range of values and/or positions. For example, a numeric value may have a value that is +/−0.1% of the stated value (or range of values), +/−1% of the stated value (or range of values), +/−2% of the stated value (or range of values), +/−5% of the stated value (or range of values), +/−10% of the stated value (or range of values), etc. Any numerical values given herein should also be understood to include about or approximately that value, unless the context indicates otherwise. For example, if the value “10” is disclosed, then “about 10” is also disclosed. Any numerical range recited herein is intended to include all sub-ranges subsumed therein. It is also understood that when a value is disclosed that “less than or equal to” the value, “greater than or equal to the value” and possible ranges between values are also disclosed, as appropriately understood by the skilled artisan. For example, if the value “X” is disclosed the “less than or equal to X” as well as “greater than or equal to X” (e.g., where X is a numerical value) is also disclosed. It is also understood that the throughout the application, data is provided in a number of different formats, and that this data, represents endpoints and starting points, and ranges for any combination of the data points. For example, if a particular data point “10” and a particular data point “15” are disclosed, it is understood that greater than, greater than or equal to, less than, less than or equal to, and equal to 10 and 15 are considered disclosed as well as between 10 and 15. It is also understood that each unit between two particular units are also disclosed. For example, if 10 and 15 are disclosed, then 11, 12, 13, and 14 are also disclosed.
Although various illustrative embodiments are described above, any of a number of changes may be made to various embodiments without departing from the scope of the disclosure as described by the claims. For example, the order in which various described method steps are performed may often be changed in alternative embodiments, and in other alternative embodiments one or more method steps may be skipped altogether. Optional features of various device and system embodiments may be included in some embodiments and not in others. Therefore, the foregoing description is provided primarily for exemplary purposes and should not be interpreted to limit the scope of the disclosure as it is set forth in the claims.
The examples and illustrations included herein show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. As mentioned, other embodiments may be utilized and derived there from, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Such embodiments of the inventive subject matter may be referred to herein individually or collectively by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept, if more than one is, in fact, disclosed. Thus, although specific embodiments have been illustrated and described herein, any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
This application is a continuation of PCT/US2023/023053, filed on May 22, 2023, which claims the benefit of priority to U.S. Provisional Application No. 63/365,229, filed on May 24, 2022, each of which are hereby incorporated by reference herein in their entirety and for all purposes
| Number | Date | Country | |
|---|---|---|---|
| 63365229 | May 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2023/023053 | May 2023 | WO |
| Child | 18954361 | US |