Patent Application
20230122652
Many conventional automatic drug delivery systems are well known, including, for example, wearable drug delivery devices of the type shown in
An exemplary prior art pump mechanism 400 is shown in perspective view in
One limitation of this design is that the total footprint of the reservoir 302 and drive mechanism 402 is greater than the length of reservoir 302 by as much as 2 times. This is due to the fact that the leadscrew 404 needs to reach all the way into reservoir 302 when reservoir 302 is in the empty state (i.e., it must be approximately equal to the length of reservoir 302 minus the space taken by plunger 304). When reservoir 302 is full, leadscrew 404 will necessarily extend behind reservoir 302 to occupy space 408 at a length up to the length of the reservoir.
In wearable, on-body devices, it is desirable to keep the pump mechanism 400, as well as the overall drug delivery device 102, as small as possible to minimize the impact to the wearer. Therefore, it would be desirable to replace the prior art pump mechanism 400 with a positive displacement pump mechanism having a different method of driving the plunger 304 within the reservoir 302 that does not require the large footprint of the prior art pump mechanism 400. This would reduce the size footprint of pump mechanism 400, thereby improving the size impact of the overall drug delivery system 102 while maintaining the benefits of the pumping methodology. Further, a smaller pump mechanism would enable the use of a larger reservoir capable of holding larger quantities of the liquid drug.
As used herein, the term “liquid drug” should be interpreted to include any drug in liquid form capable of being administered by a drug delivery device via a subcutaneous cannula, including, for example, insulin or co-formulations of two or more of GLP-1, pramlintide, and insulin.
Embodiments of the invention disclosed herein include a size-optimized pump mechanism having a flexible linkage between a drive mechanism and a plunger disposed in a reservoir, wherein the flexible linkage comprises, in a preferred embodiment, a coiled metal tape that unrolls and pushes on the plunger, causing a longitudinal translation of the plunger within the reservoir to dispense a liquid drug from the reservoir. The flexible linkage has one end attached to the plunger through an open end of the reservoir with the remainder of the flexible linkage being initially coiled around a reel. As the flexible linkage is uncoiled from the reel, it passes through a pair of rollers shaped to provide the flexible linkage with a curved cross-sectional shape to increase the structural integrity and the buckling force of the flexible linkage, thus allowing it to impart force on the plunger required to cause the longitudinal translation of the plunger through the reservoir to force the liquid drug in the reservoir to a patient interface. At least one roller of the pair of rollers is driven by a drive mechanism and the flexible linkage is uncoiled by virtue of a frictional engagement with the rollers.
This disclosure presents various systems, components and methods for moving a liquid drug, from a reservoir 302 in a wearable drug delivery device 102 to a patient interface, typically a needle or cannula. The embodiments described herein provide one or more advantages over conventional, prior art systems, components and methods.
Various embodiments of the present invention include systems and methods for delivering a medication to a user using a drug delivery device (sometimes referred to herein as a “pod”), either autonomously, or in accordance with a wireless signal received from an electronic device. In various embodiments, the electronic device may be a user device comprising a smartphone, a smart watch, a smart necklace, a module attached to the drug delivery device, or any other type or sort of electronic device that may be carried by the user or worn on the body of the user and that executes an algorithm that computes the times and dosages of delivery of the medication.
For example, the user device may execute an “artificial-pancreas” algorithm that computes the times and dosages of delivery of insulin. The user device may also be in communication with a sensor, such as a glucose sensor, that collects data on a physical attribute or condition of the user, such as a glucose level. The sensor may be disposed in or on the body of the user and may be part of the drug delivery device or may be a separate device.
Alternatively, the drug delivery device may be in communication with the sensor in lieu of or in addition to the communication between the sensor and the user device. The communication may be direct (if, e.g., the sensor is integrated with or otherwise a part of the drug delivery device) or remote/wireless (if, e.g., the sensor is disposed in a different housing than the drug delivery device). In these embodiments, the drug delivery device contains computing hardware (e.g., a processor, memory, firmware, etc.) that executes some or all of the algorithm that computes the times and dosages of delivery of the medication.
Drug delivery system 100, in an optional example, may also include an accessory device 106, such as a smartwatch, a personal assistant device, or the like, which may communicate with the other components of system 100 via either a wired or wireless communication links 191-193.
The user device 105 may be a computing device such as a smartphone, a tablet, a personal diabetes management (PDM) device, a dedicated diabetes therapy management device, or the like. In an example, user device 105 may include a processor 151, device memory 153, a user interface 158, and a communication interface 154. The user device 105 may also contain analog and/or digital circuitry that may be implemented as a processor 151 for executing processes based on programming code stored in device memory 153, such as user application 160 to manage a user's blood glucose levels and for controlling the delivery of the drug, medication, or therapeutic agent to the user, as well for providing other functions, such as calculating carbohydrate-compensation dosage, a correction bolus dosage and the like as discussed below. The user device 105 may be used to program, adjust settings, and/or control operation of drug delivery device 102 and/or the analyte sensor 103 as well as the optional smart accessory device 106.
The processor 151 may also be configured to execute programming code stored in device memory 153, such as the user app 160. The user app 160 may be a computer application that is operable to deliver a drug based on information received from the analyte sensor 103, the cloud-based services 111 and/or the user device 105 or optional accessory device 106. The memory 153 may also store programming code to, for example, operate the user interface 158 (e.g., a touchscreen device, a camera or the like), the communication interface 154 and the like. The processor 151, when executing user app 160, may be configured to implement indications and notifications related to meal ingestion, blood glucose measurements, and the like. The user interface 158 may be under the control of the processor 151 and be configured to present a graphical user interface that enables the input of a meal announcement, adjust setting selections and the like as described herein.
In a specific example, when the user app 160 is an AP application, the processor 151 is also configured to execute a diabetes treatment plan (which may be stored in a memory) that is managed by user app 160. In addition to the functions mentioned above, when user app 160 is an AP application, it may further provide functionality to determine a carbohydrate-compensation dosage, a correction bolus dosage and determine a basal dosage according to a diabetes treatment plan. In addition, as an AP application, user app 160 provides functionality to output signals to the drug delivery device 102 via communications interface 154 to deliver the determined bolus and basal dosages.
The communication interface 154 may include one or more transceivers that operate according to one or more radio-frequency protocols. In one embodiment, the transceivers may comprise a cellular transceiver and a Bluetooth® transceiver. The communication interface 154 may be configured to receive and transmit signals containing information usable by user app 160.
User device 105 may be further provided with one or more output devices 155 which may be, for example, a speaker or a vibration transducer, to provide various signals to the user.
In various exemplary embodiments, drug delivery device 102 may include a reservoir 124 and drive mechanism 125, which are controllable by controller 121, executing a medication delivery algorithm (MDA) 129 stored in memory 123. Alternatively, controller 121 may act to control reservoir 124 and drive mechanism 125 based on signals received from user app 160 executing on a user device 105 and communicated to drug delivery device 102 via communication link 194. Drive mechanism 125 operates to longitudinally translate a plunger through the reservoir, such as to force the liquid drug through an outlet fluid port to needle/cannula 186.
In an alternate embodiment, drug delivery device 102 may also include an optional second reservoir 124-2 and second drive mechanism 125-2 which enables the independent delivery of two different liquid drugs. As an example, reservoir 124 may be filled with insulin, while reservoir 124-2 may be filled with Pramlintide or GLP-1. In some embodiments, each of reservoirs 124, 124-2 may be configured with a separate drive mechanism 125, 125-2, respectively, which may be separately controllable by controller 121 under the direction of MDA 129. Both reservoirs 124, 124-2 may be connected to a common needle/cannula 186.
Drug delivery device 102 may be optionally configured with a user interface 127 providing a means for receiving input from the user and a means for outputting information to the user. User interface 127 may include, for example, light-emitting diodes, buttons on a housing of drug delivery device 102, a sound transducer, a micro-display, a microphone, an accelerometer for detecting motions of the device or user gestures (e.g., tapping on a housing of the device) or any other type of interface device that is configured to allow a user to enter information and/or allow drug delivery device 102 to output information for presentation to the user (e.g., alarm signals or the like).
Drug delivery device 102 includes a patient interface 186 for interfacing with the user to deliver the liquid drug. Patient interface may be, for example, a needle or cannula for delivering the drug into the body of the user (which may be done subcutaneously, intraperitoneally, or intravenously). Drug delivery device 102 further includes a mechanism for inserting the needle/cannula 186 into the body of the user, which may be integral with or attachable to drug delivery device 102. The insertion mechanism may comprise, in one embodiment, an actuator that inserts the needle/cannula 186 under the skin of the user and thereafter retracts the needle, leaving the cannula in place.
In one embodiment, drug delivery device 102 includes a communication interface 126, which may be a transceiver that operates according to one or more radio-frequency protocols, such as Bluetooth®, Wi-Fi, near-field communication, cellular, or the like. The controller 121 may, for example, communicate with user device 105 and an analyte sensor 108 via the communication interface 126.
In some embodiments, drug delivery device 102 may be provided with one or more sensors 184. The sensors 184 may include one or more of a pressure sensor, a power sensor, or the like that are communicatively coupled to the controller 121 and provide various signals. For example, a pressure sensor may be configured to provide an indication of the fluid pressure detected in a fluid pathway between the patient interface 186 and reservoir 124. The pressure sensor may be coupled to or integral with the actuator for inserting the patient interface 186 into the user. In an example, the controller 121 may be operable to determine a rate of drug infusion based on the indication of the fluid pressure. The rate of drug infusion may be compared to an infusion rate threshold, and the comparison result may be usable in determining an amount of insulin onboard (IOB) or a total daily insulin (TDI) amount. In one embodiment, analyte sensor 108 may be integral with drug delivery device 102.
Drug delivery device 102 further includes a power source 128, such as a battery, a piezoelectric device, an energy harvesting device, or the like, for supplying electrical power to controller 121, memory 123, drive mechanisms 125 and/or other components of drug delivery device 102.
Drug delivery device 102 may be configured to perform and execute processes required to deliver doses of the medication to the user without input from the user device 105 or the optional accessory device 106. As explained in more detail, MDA 129 may be operable, for example, to determine an amount of insulin to be delivered, JOB, insulin remaining, and the like and to cause controller 121 to activate drive mechanism 125 to deliver the medication from reservoir 124. MDA 129 may take as input data received from the analyte sensor 108 or from user app 160.
The reservoirs 124, 124-2 may be configured to store drugs, medications or therapeutic agents suitable for automated delivery, such as insulin, Pramlintide, GLP-1, co-formulations of insulin and GLP-1, morphine, blood pressure medicines, chemotherapy drugs, fertility drugs or the like.
Drug delivery device 102 may be a wearable device and may be attached to the body of a user, such as a patient or diabetic, at an attachment location and may deliver any therapeutic agent, including any drug or medicine, such as insulin or the like, to a user at or around the attachment location. A surface of drug delivery device 102 may include an adhesive to facilitate attachment to the skin of a user.
When configured to communicate with an external device, such as the user device 105 or the analyte sensor 108, drug delivery device 102 may receive signals over the wired or wireless link 194 from the user device 105 or from the analyte sensor 108. The controller 121 of drug delivery device 102 may receive and process the signals from the respective external devices as well as implementing delivery of a drug to the user according to a diabetes treatment plan or other drug delivery regimen.
Optional accessory device 107 may be, a wearable smart device, for example, a smart watch (e.g., an Apple Watch®), smart eyeglasses, smart jewelry, a global positioning system-enabled wearable, a wearable fitness device, smart clothing, or the like. Similar to user device 105, the accessory device 107 may also be configured to perform various functions including controlling drug delivery device 102. For example, the accessory device 107 may include a communication interface 174, a processor 171, a user interface 178 and a memory 173. The user interface 178 may be a graphical user interface presented on a touchscreen display of the smart accessory device 107. The memory 173 may store programming code to operate different functions of the smart accessory device 107 as well as an instance of the user app 160, or a pared-down version of user app 160 with reduced functionality. In some instances, accessory device 107 may also include sensors of various types.
The analyte sensor 108 may include a controller 131, a memory 132, a sensing/measuring device 133, an optional user interface 137, a power source/energy harvesting circuitry 134, and a communication interface 135. The analyte sensor 108 may be communicatively coupled to the processor 151 of the management device 105 or controller 121 of drug delivery device 102. The memory 132 may be configured to store information and programming code 136.
The analyte sensor 108 may be configured to detect multiple different analytes, such as glucose, lactate, ketones, uric acid, sodium, potassium, alcohol levels or the like, and output results of the detections, such as measurement values or the like. The analyte sensor 108 may, in an exemplary embodiment, be configured to measure a blood glucose value at a predetermined time interval, such as every 5 minutes, every 1 minute, or the like. The communication interface 135 of analyte sensor 108 may have circuitry that operates as a transceiver for communicating the measured blood glucose values to the user device 105 over a wireless link 195 or with drug delivery device 102 over the wireless communication link 108. While referred to herein as an analyte sensor 108, the sensing/measuring device 133 of the analyte sensor 108 may include one or more additional sensing elements, such as a glucose measurement element, a heart rate monitor, a pressure sensor, or the like. The controller 131 may include discrete, specialized logic and/or components, an application-specific integrated circuit, a microcontroller or processor that executes software instructions, firmware, programming instructions stored in memory (such as memory 132), or any combination thereof.
Similar to the controller 121 of drug delivery device 102, the controller 131 of the analyte sensor 108 may be operable to perform many functions. For example, the controller 131 may be configured by programming code 136 to manage the collection and analysis of data detected by the sensing and measuring device 133.
Although the analyte sensor 108 is depicted in
Drug delivery system 100 may communicate with or receive services from cloud-based services 111. Services provided by cloud-based services 111 may include data storage that stores personal or anonymized data, such as blood glucose measurement values, historical IOB or TDI, prior carbohydrate-compensation dosage, and other forms of data. In addition, the cloud-based services 111 may process anonymized data from multiple users to provide generalized information related to TDI, insulin sensitivity, IOB and the like. The communication link 115 that couples the cloud-based services 111 to the respective devices 102, 105, 106, 108 of system 100 may be a cellular link, a Wi-Fi link, a Bluetooth® link, or a combination thereof.
The wireless communication links 115 and 191-196 may be any type of wireless link operating using known wireless communication standards or proprietary standards. As an example, the wireless communication links 191-196 may provide communication links based on Bluetooth®, Zigbee®, Wi-Fi, a near-field communication standard, a cellular standard, or any other wireless protocol via the respective communication interfaces 126, 135, 154 and 174.
In an operational example, user application 160 implements a graphical user interface that is the primary interface with the user and is used to start and stop drug delivery device 102, program basal and bolus calculator settings for manual mode as well as program settings specific for automated mode (hybrid closed-loop or closed-loop).
User app 160, provides a graphical user interface 158 that allows for the use of large text, graphics, and on-screen instructions to prompt the user through the set-up processes and the use of system 100. It will also be used to program the user's custom basal insulin delivery profile, check the status, of drug delivery device 102, initiate bolus doses of insulin, make changes to a patient's insulin delivery profile, handle system alerts and alarms, and allow the user to switch between automated mode and manual mode.
User app 160 may configured to operate in a manual mode in which user app 160 will deliver insulin at programmed basal rates and bolus amounts with the option to set temporary basal profiles. The controller 121 will also have the ability to function as a sensor-augmented pump in manual mode, using sensor glucose data provided by the analyte sensor 108 to populate the bolus calculator.
User app 160 may configured to operate in an automated mode in which user app 160 supports the use of multiple target blood glucose values. For example, in one embodiment, target blood glucose values can range from 110-150 mg/dL, in 10 mg/dL increments, in 5 mg/dL increments, or other increments, but preferably 10 mg/dL increments. The experience for the user will reflect current setup flows whereby the healthcare provider assists the user to program basal rates, glucose targets and bolus calculator settings. These in turn will inform the user app 160 for insulin dosing parameters. The insulin dosing parameters will be adapted over time based on the total daily insulin (TDI) delivered during each use of drug delivery device 102. A temporary hypoglycemia protection mode may be implemented by the user for various time durations in automated mode. With hypoglycemia protection mode, the algorithm reduces insulin delivery and is intended for use over temporary durations when insulin sensitivity is expected to be higher, such as during exercise.
The user app 160 (or MDA 129) may provide periodic insulin micro-boluses based upon past glucose measurements and/or a predicted glucose over a prediction horizon (e.g., 60 minutes). Optimal post-prandial control may require the user to give meal boluses in the same manner as current pump therapy, but normal operation of the user app 160 will compensate for missed meal boluses and mitigate prolonged hyperglycemia. The user app 160 uses a control-to-target strategy that attempts to achieve and maintain a set target glucose value, thereby reducing the duration of prolonged hyperglycemia and hypoglycemia.
In some embodiments, user device 105 and the analyte sensor 108 may not communicate directly with one another. Instead, data (e.g., blood glucose readings) from analyte sensor may be communicated to drug delivery device 102 via link 196 and then relayed to user device 105 via link 194. In some embodiments, to enable communication between analyte sensor 108 and user device 105, the serial number of the analyte sensor must be entered into user app 160.
User app 160 may provide the ability to calculate a suggested bolus dose through the use of a bolus calculator. The bolus calculator is provided as a convenience to the user to aid in determining the suggested bolus dose based on ingested carbohydrates, most-recent blood glucose readings (or a blood glucose reading if using fingerstick), programmable correction factor, insulin to carbohydrate ratio, target glucose value and insulin on board (IOB). IOB is estimated by user app 160 taking into account any manual bolus and insulin delivered by the algorithm.
In primary embodiments of the invention, the reservoir and pump are integrated into a single component (referred to herein as a “pump mechanism”) and the linkage between the drive mechanism of the prior art pump mechanism and the reservoir of the prior art pump mechanism is replaced by a novel flexible linkage as described herein which reduces the overall size of the footprint of the pump mechanism, or, alternatively, allows for the use of a larger reservoir.
Embodiments of the pump mechanism 500 described herein are shown in
The reservoir 302 may, in various embodiments of the invention, be composed of polyethylene or an injection-molded plastic, but, in other embodiments, may be composed of any material impermeable to the liquid drug disposed therein. The plunger 304 may be composed of any material and may be configured with one or more O-rings along one or more circumferential surfaces thereof such as to create a seal between the plunger 304 and the interior wall of reservoir 302 when the plunger 304 is disposed within reservoir 302. The cross-sectional area of the reservoir 302 and plunger 304 may be of any convenient shape, such as to be able to take advantage of all available space within one or more housings of drug delivery device 102, which, as shown in
A primary embodiment of the invention is shown in a perspective view in
Reservoir 302 stores the liquid drug prior to delivery to the user. In some embodiments, the drug delivery device 102 may come with a prefilled reservoir containing the liquid drug. In other embodiments, the reservoir 302 may be filled by or refillable by the user. Reservoir 302 may be fitted with a plunger 304 which is longitudinally translatable through the interior length of reservoir 302 in direction “A” as shown in
Longitudinal translation of plunger 304 toward the distal end of reservoir 308 will force the liquid drug from area 308 via a fluid port (not shown) to a patient interface, typically a subcutaneous needle or cannula (not shown). The fluid port may be provided with a one-way valve that prevents fluids from the user from entering area 308 of reservoir 302. The fluid port may be located at any point such as to be in fluid communication with space 308 within reservoir 302, however, in preferred embodiments, the fluid port is located as close to the distal end of reservoir 302 as possible to avoid wasting any holdup volume of the liquid drug that would otherwise get trapped at the distal end of the reservoir 302. Preferably, reservoir 302 is rigidly attached to the body of the drug delivery device.
The longitudinal translation of the plunger 304 in direction “A” toward the distal end of reservoir 302, in the preferred embodiments, is accomplished via a flexible linkage 402 between a drive mechanism 410 and plunger 304. As flexible linkage 502 is uncoiled from reel 504, it passes through a pair of rollers comprising a roller 506 having a convex circumferential surface and a roller 508 having a concave circumferential surface, which impart flexible linkage 502 with a curved cross-sectional shape as it is passed therethrough, to add structural strength and to prevent buckling of flexible linkage 502 as it pushes plunger 504 toward the distal end of reservoir 302. Flexible linkage 502 may be uncoiled from reel 504 by virtue of a frictional engagement between flexible linkage 502 and rollers 506, 508. Alternatively, a motor or drive mechanism (such as drive mechanism 510) may be directly coupled to reel 504 to uncoil flexible linkage 502 therefrom. In one embodiment of the invention, flexible linkage 502 is composed of steel; however, other materials may be used.
In preferred embodiments of the invention, convex roller 506 may be driven by drive mechanism 510 in a clockwise direction “B” as shown in
In preferred embodiments of the invention, convex-surfaced roller 506 is driven by drive mechanism 510, which may comprise, in one embodiment, a ratchet mechanism and a set of reduction gears. The gear reduction would ensure that each pulse of the ratchet mechanism would dispense the required volume of the liquid drug. In one embodiment of the invention, drive mechanism 510 may include a planetary gear assembly; however, any arrangement of gears may be used.
In certain embodiments, drive mechanism 510 may be provided with a clutch mechanism (not shown) such as to be able to disengage drive mechanism 510 from driven roller 506 or 508 to allow rollers 506, 508 to move in a reverse direction. This is useful in embodiments of drug delivery device 102 wherein reservoir 302 may be filled by the user via injection of the liquid drug through a fill port, thus causing plunger 304 to move in a direction opposite direction “A” in
In alternate embodiments of the invention, as would be realized by one of skill in the art, roller 506 may be provided with the concave circumferential surface and roller 508 may be provided with the convex circumferential surface. Also, in alternative embodiments, roller 508 may be driven by drive mechanism 510 and roller 506 may be spring-loaded against flexible linkage 502.
In various aspects of the primary embodiment, either or both of rollers 506, 508 could be provided with rubber coatings on the circumferential surfaces thereof to aid in the provision of the frictional engagement with flexible linkage 502.
In an alternate embodiment shown in
In yet another alternative embodiment, a light sensor (not shown) could be provided to add the capability to tally the holes 702 in flexible linkage 502 as they pass over the light sensor, thereby providing a measurement of how much of the flexible linkage 502 has been uncoiled from reel 504. This may serve as an indication of how far the plunger has translated longitudinally toward the distal end of reservoir 302. Additionally, the quantity of the liquid drug deposited into or dispensed from reservoir 302 may be calculated as a function of the tally of the holes 702 in flexible linkage 502 passing over the light sensor.
Drive mechanism 510 may be actuated by a motor or, alternatively, by the expansion and contraction of a wire composed of a shape memory alloy, such as Nitinol. Additionally, drive mechanism 510 may be located in alternative positions with respect to reservoir 302 to those shown in
In yet another embodiment of the invention, flexible linkage 502, instead of being coiled around reel 504, could be coiled around either driven roller 506 or spring-loaded roller 508. In such cases, as the flexible linkage 502 unrolls from the coil, the radius of the coil would change. The change in the linear travel of flexible linkage 502 could be calculated based on the reducing radius of the coil and the motion of drive mechanism 510 adjusted accordingly.
The following examples pertain to various embodiments of the pump mechanism suitable for use in a wearable drug delivery device:
Example 1 is a first embodiment of a pump mechanism comprising a reservoir, a plunger disposed in the reservoir, a drive mechanism and a flexible linkage coupling the drive mechanism and the plunger.
Example 2 is an extension of Example 1, or any other example disclosed herein, wherein the flexible linkage extends through the open end of the reservoir and is coupled to a rear surface of the plunger.
Example 3 is an extension of Example 2, or any other example disclosed herein, wherein the flexible linkage is coiled around a reel and uncoiled by motion of the drive mechanism.
Example 4 is an extension of Example 3, or any other example disclosed herein, further comprising a pair of rollers, at least one of which is rotationally driven by the drive mechanism.
Example 5 is an extension of Example 4, or any other example disclosed herein, when one of the rollers is spring-loaded against the other roller and wherein the flexible linkage is disposed between the rollers such that rotation of the rollers by the drive mechanism imparts a linear translation of the flexible linkage by virtue of a frictional engagement between the rollers and the flexible linkage.
Example 6 is an extension of Example 5, or any other example disclosed herein, wherein one of the rollers is configured with a concavely-shaped circumference and the other roller is configured with a convexly-shaped circumference such as to impart a curved cross-sectional shape to the flexible linkage.
Example 7 is an extension of Example 6, or any other example disclosed herein, wherein the linear translation of the flexible linkage through the rollers causes a linear translation of the plunger toward the closed end of the reservoir.
Example 8 is an extension of Example 7, or any other example disclosed herein, wherein one or both of the rollers is configured with a rubber-coated circumference such as to improve the frictional engagement between the rollers and the flexible linkage.
Example 9 is an extension of Example 4, or any other example disclosed herein, further comprising a series of holes defined in the flexible linkage and a series of protrusions defined on the circumference of one or both of the rollers wherein the protrusions engage the series of holes in the flexible linkage as the rollers are rotationally driven by the drive mechanism.
Example 10 is an extension of Example 9, or any other example disclosed herein, further comprising a light sensor configured to sense light passing through the holes defined in the flexible linkage.
Example 11 is an extension of Example 4, or any other example disclosed herein, wherein the flexible linkage is coiled around one of the rollers.
Example 12 is an extension of Example 4, or any other example disclosed herein, wherein the flexible linkage is coiled around a reel separate from the rollers.
Example 13 is an extension of Example 4, or any other example disclosed herein, wherein the drive mechanism comprises a ratchet wheel, a planetary gear driven by the ratchet wheel and a gear train coupled to the planetary gear for engaging the driven roller.
Example 14 is extension of Example 13, or any other example disclosed herein, wherein the ratchet wheel is rotated by an expansion and contraction of a wire composed of a shape memory alloy.
Example 15 is an extension of Example 13, or any other example disclosed herein, wherein the ratchet wheel is rotated by a motor.
Example 16 is an extension of Example 4, or any other example disclosed herein, wherein pump mechanism further comprises a clutch mechanism disposed between the drive mechanism and the driven roller.
Example 17 is an extension of Example 16, or any other example disclosed herein, wherein the position of the plunger within the reservoir can be calculated as a function of the number of rotations or partial rotations of the rollers in either direction.
Example 18 is a method for operating a positive displacement pump mechanism comprising uncoiling a flexible linkage from a reel, wherein the flexible linkage is attached to a plunger disposed in the reservoir of the positive displacement pump and wherein a linear translation of the uncoiled portion of the flexible linkage causes a linear translation of the plunger within the reservoir.
Example 19 is an extension of Example 18, or any other example disclosed herein, the method further comprising passing the uncoiled portion of the flexible linkage between a pair of rollers, one roller having a convex circumferential surface and the other roller having a concave circumferential surface wherein the rollers impart a curved cross-sectional shape of the flexible linkage.
Example 20 is an extension of Example 19, or any other example disclosed herein, the method further comprising rotating one or both of the rollers using a drive mechanism, wherein a frictional engagement between the rollers and the flexible linkage causes the flexible linkage to uncoil.
Software related implementations of the techniques described herein may include, but are not limited to, firmware, application specific software, or any other type of computer readable instructions that may be executed by one or more processors. The computer readable instructions may be provided via non-transitory computer-readable media. Hardware related implementations of the techniques described herein may include, but are not limited to, integrated circuits (ICs), application specific ICs (ASICs), field programmable arrays (FPGAs), and/or programmable logic devices (PLDs). In some examples, the techniques described herein, and/or any system or constituent component described herein may be implemented with a processor executing computer readable instructions stored on one or more memory components.
To those skilled in the art to which the invention relates, many modifications and adaptations of the invention may be realized. Implementations provided herein, including sizes, shapes, ratings and specifications of various components or arrangements of components, and descriptions of specific manufacturing processes, should be considered exemplary only and are not meant to limit the invention in any way. As one of skill in the art would realize, many variations on implementations discussed herein which fall within the scope of the invention are possible. Moreover, it is to be understood that the features of the various embodiments described herein were not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the invention. Accordingly, the method and apparatus disclosed herein are not to be taken as limitations on the invention but as an illustration thereof. The scope of the invention is defined by the claims which follow.
This application claims the benefit of U.S. Provisional Patent Application No. 63/256,712, filed Oct. 18, 2021, the contents of which are incorporated herein by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63256712 | Oct 2021 | US |
