Patent Grant
11135416
This invention relates generally to medical fluid transfer systems, methods, and components; and specifically to electronically controlled medical fluid transfer systems, methods, and components.
Many types of medical fluids are routinely used to treat patients, including chemotherapy drugs, antibiotics, immunosuppressive drugs, antiviral drugs, hydrating fluids, nourishing fluids, anticoagulants, pain management drugs, contrast fluids for medical imaging, etc. All of these fluids, in turn, come in many different varieties with advantages and disadvantages for various types of diseases, conditions, injuries, or therapies. Moreover, particular patients require optimized dosages, concentrations, and combinations of these drugs or other medical fluids to address their specific medical needs. As a result, medical facilities are required to provide many different types of customized medical fluids on a continual basis to meet individual patient needs.
In some embodiments, a medical fluid transfer module is configured to be removably coupled to an electronic medical fluid transfer device to facilitate the transfer of medical fluids from a source container to a destination container. The medical fluid transfer module can comprise a first closeable, resealable medical connector and a second closeable, resealable medical connector, a multidirectional flow-control valve with a driving interface configured to interface with an electromechanical driver of an electronic medical fluid transfer device, and an intermediate container. The multidirectional flow-control valve can comprise a plurality of functional positions to enable a selection among a plurality of different fluid pathways within the medical fluid transfer module. The plurality of different fluid pathways can be configured to contain liquid within the medical fluid transfer module in a closed system when the medical fluid transfer module is not attached to the electronic medical fluid transfer device.
In some embodiments, a method of enabling medical fluid transfer between a source container and a destination container can comprise the steps of providing a closed-system fluid transfer module comprising a first closeable, resealable medical connector and a second closeable, resealable medical connector, a multidirectional fluid control valve with a driving interface configured to interface with an electromechanical driver of an electronic medical fluid transfer device, and an intermediate container or an intermediate pumping region; and instructing a user to couple the closed-system fluid transfer module to the electronic medical fluid transfer device.
In some embodiments, an electronic medical fluid transfer device can comprise one or more supports configured to receive a fluid transfer module comprising a first inlet fluid connector, a second outlet fluid connector, a multidirectional flow control valve, and an intermediate container or pumping region; a gas sensor configured to detect whether gas is present in the fluid transfer module; a first electromechanical driver configured to interface with and control the multidirectional flow control valve on the fluid transfer module; a second electromechanical driver configured to be mechanically linked to the intermediate container or pumping region; and a computer processor or processors configured to communicate electronically with the sensor and the first and second electromechanical drivers to prime or purge the fluid transfer module with liquid and purge gas from the fluid transfer module.
In some embodiments, the priming of the fluid transfer module can comprise the steps of opening a fluid pathway between the second fluid connector and the intermediate container or pumping region and closing a fluid pathway to the first fluid connector; lowering the pressure in the intermediate container or pumping region; opening a fluid pathway between the inlet fluid connector and the intermediate container or pumping region and closing the fluid pathway to the second fluid connector; pushing fluid from the intermediate container or pumping region toward the first fluid connector; opening the fluid pathway between the first fluid connector and the second fluid connector and closing the fluid pathway to the intermediate container or pumping region; and opening the fluid pathway between the first fluid connector and the intermediate container or pumping region.
Embodiments will now be described with reference to the following drawings, which are provided by way of example, and not limitation. Like reference numerals indicate identical or functionally similar elements.
i is a front perspective view of an example of an electromechanical system for transferring medical fluid.
i is a rear view of an example of a fluid transfer device.
i is a front perspective view of the electromechanical system for transferring medical fluid of
i is a magnified partial front view of the electromechanical system of
ii is a front perspective view of an example of an electromechanical system for transferring medical fluid according to another embodiment.
ii is a rear view of an example of a fluid transfer device according to another embodiment.
ii is a front perspective view of the electromechanical system for transferring medical fluid of
ii is a magnified partial front view of the electromechanical system of
ii is a rear perspective cross-sectional view of the electromechanical system and fluid transfer device shown
Various systems, methods, and components can be used in different embodiments of the inventions. Some embodiments are illustrated in the accompanying figures; however, the figures are provided for convenience of illustration only, and should not be interpreted to limit the inventions to the particular combinations of features shown. Rather, any feature, structure, material, step, or component of any embodiment described and/or illustrated in this specification can be used by itself, or with or instead of any other feature, structure, material, step, or component of any other embodiment described and/or illustrated in this specification. Nothing in this specification is essential or indispensable.
The fluid transfer module 31 can comprise a multidirectional flow-control valve 41 and an intermediate container or pumping region 40, as well as any connector(s) and/or conduit(s) that may extend between or among these or any other components of the fluid transfer module 31, and/or any connectors and/or conduits that may extend between or among the fluid transfer module 31 and the source container 39 and/or the destination container 44. For example, the fluid transfer module 31 can comprise an inlet fluid connector 32 and tubing that can be configured to removably attach the multidirectional flow-control valve to the source container 39; and/or the fluid transfer module 31 can comprise an outlet fluid connector 42 and tubing that can be configured to removably attach the multidirectional flow control valve to the destination container 44.
As shown in
The multidirectional flow-control valve 41 can be configured to mechanically attach to or interface with the electromechanical controller 36. For example, in some embodiments, the multidirectional flow-control valve 41 can comprise a driving interface 33 that is configured to attach with and/or interface with a corresponding electromechanical driver (see, e.g.,
In some embodiments, the multidirectional flow-control valve 41 can comprise a stopcock with a plurality of functional positions, such as a first position that enables fluid communication between the outlet fluid connector 42 and the intermediate container or pumping region 40 (but not the inlet fluid connector 32, in some embodiments); a second position that enables fluid communication between the inlet fluid connector 32 and the intermediate container or pumping region 40 (but not the outlet fluid connector 42, in some embodiments); and a third position that enables fluid communication between the outlet fluid connector 42 and the inlet fluid connector 32 (but not the intermediate container or pumping region 40, in some embodiments). For example, in some embodiments, when the stopcock is in the first position, fluid can flow from the intermediate container or pumping region 40 to the destination container 44 or vice versa; when the stopcock is in the second position, fluid can flow from the source container 39 to the intermediate container or pumping region 40 or vice versa; and when the stopcock is in the third position, fluid can flow from the source container 39 to the destination container 44 or vice versa. Further, in some embodiments, when the stopcock is in the first position, the intermediate fluid connector 38, the stopcock, and the outlet fluid connector 42 can comprise at least a portion of a flow path between the intermediate container or pumping region 40 and the destination container 44; when the stopcock is in the second or fourth position, the inlet fluid connector 32, the stopcock, and the intermediate fluid connector 38 can comprise at least a portion of a flow path between the source container 39 and the intermediate container or pumping region 40; and when the stopcock is in the third position, the inlet fluid connector 32, the stopcock, and the outlet fluid connector 42 can comprise at least a portion of a flow path between the source container 39 and the destination container 44. In some embodiments, the stopcock can comprise at least a portion of one or more flow paths between or among two or more containers (e.g., the source container 39, the intermediate container or pumping region 40, and/or the destination container 44) without the use of any connectors (e.g., the inlet fluid connector 32, the intermediate fluid connector 38, and/or the outlet fluid connector 42) when in the first, second, third, and/or fourth position. Other arrangements can be used are also appreciated and contemplated herein, including, for example, stopcocks configured to have more or less than three positions (e.g., stopcocks configured to have 2, 4, 5, or more positions).
In some embodiments, the fluid transfer module 31 can be a single-use or limited-use, disposable device that is configured to be periodically removed from and replaced within the fluid transfer device 30, such as after a single dosage of medication for a particular patient has been transferred and/or after one particular type of medication has passed through the fluid transfer module 31 (e.g., to avoid mixing of medications when not desired).
The various components of the fluid transfer system 86 can communicate between or among themselves in any suitable manner. For example, as illustrated, the one or more patient and/or drug information storage device(s) or network(s) 70 can electronically communicate with the fluid transfer management system 74, or any components thereof, by way of an electronic communication link 72, formed by any suitable electronic communication device, such as a wired connection, a local area network, a wide area network, the Internet, and/or a wireless connection (including, e.g., Wi-Fi, Bluetooth, Ant+, ZigBee, cellular, etc.), or any other electronic communication device (collectively referred to as “electronic communicators”). As shown in
The user interface 78 can communicate with one or more fluid transfer devices 30 and/or with one or more patient and/or drug information storage device(s) or network(s) 70 by way of any suitable electronic communication device 76, including by way of any wireless device or by way of any other of the electronic communicators. In some embodiments of the fluid transfer management system 74 in which there are multiple fluid transfer devices 30, a single user interface 78 can electronically communicate with a plurality of fluid transfer devices 30 to control and/or monitor multiple fluid transfers operating generally simultaneously or generally in parallel. In some embodiments of the fluid transfer management system 74 in which there are multiple fluid transfer devices 30, one or more user interfaces 78 can electronically communicate with a plurality of fluid transfer devices 30 to control and/or monitor multiple fluid transfers operating generally simultaneously or generally in parallel. The user interface 78, like the fluid transfer device 30, can electronically communicate with or include a memory 84 by way of a wired connector 80 or any other of the electronic communicators. The memory 84 of the user interface 78 can be part of the user interface 78 in that a common housing can be provided for containing or supporting both. Each of the components of the fluid transfer management system 74 as shown in
i-2Di illustrate various features, components, and arrangements that can be included in some embodiments of the fluid transfer device 30 and fluid transfer module 31 shown in
Turning to
In some embodiments, at least one or more portions of the housing 202, such as the one or more receptacles 218 (e.g., the recess 218 illustrated in
The volume sensor can be used, for example, to control and/or to provide a record of the volume and/or type of fluid transferred to a patient, such as, for example, by sensing and/or recording the volume and/or one or more other characteristics (e.g., color, viscosity, concentration, lot number, expiration date, etc.) of the liquid in a container (e.g., the intermediate container, or pumping region 40, and/or the source container 39 and/or the destination container 44) before, during, and/or after it is transferred to a patient. For example, in some embodiments, a camera can be used to capture an image of the intermediate container or pumping region 40 to confirm or measure the volume therein. A data file can then be created and stored in a memory 84 which has one of more items of information, such as patient identifying information, the date and time the liquid was transferred and/or the volume or other characteristic(s) of the liquid was or were confirmed and recorded, the type (name, brand, and/or concentration, etc.) of medical fluid transferred, the volume of medical fluid transferred, and/or one or more images of the intermediate container or pumping region 40 with liquid inside, etc. The same or a similar data file can be created for any one of the suitable volume sensors described above. In some embodiments, the fluid transfer unit 200, the fluid transfer device 30, and/or the fluid transfer system 86 can include one or more measuring instruments, such as one or more volume sensors. In some embodiments, the one or more measuring instruments or volume sensors can be internal and/or external to the fluid transfer unit 220, or partially external and partially internal, such as when a portion of the instrument or sensor is inside of the housing 212 and a portion of the sensor protrudes from the housing 212.
i illustrates a rear view of an example of a fluid transfer module 31 of
A multidirectional flow-control valve 41, such as a fluid stopcock 230, can be particularly useful in some embodiments because it can permit variability and control of the direction and/or orientation of the fluid pathway within the fluid transfer module 31. In some embodiments, the flow-control valve 41 can be configured, as illustrated throughout this specification, to selectively enable a plurality of discrete settings, each setting enabling fluid connections within the fluid pathway of the fluid transfer module 31 among two or more different components of the fluid transfer module 31, and closing-off or isolating one or more other fluid connections of one or more other components from the fluid pathway of the fluid transfer module 31. The flow-control valve 41 can be configured to change between the plurality of discrete settings.
In some embodiments, as illustrated, such change or changes of settings or connections within the flow-control valve 41 can be accomplished electronically and independently of changes to fluid pressure within the fluid transfer module 31. For example, in some embodiments, a pressure differential can arise between two or more parts or components of the fluid transfer module 31 without causing any change of connections within the fluid transfer module 31 and/or without enabling fluid communication between different portions of the fluid transfer module 31 that, before such pressure differential, were not previously in fluid communication with each other.
In some embodiments, the multidirectional flow-control valve 41 is not a one-way valve or a series of one-way valves; rather, the multidirectional flow-control valve 41, in each particular electronically selectable setting, can provide a full two-way fluid pathway between two or more components of the fluid transfer module 31. For example, in some embodiments, in one or a plurality of discrete, electronically selectable settings, the flow-control valve 41 can provide a two-way fluid pathway between the inlet fluid connector 226 and the outlet fluid connector 234; and/or a two-way fluid pathway between the inlet fluid connector 226 and the intermediate container 40 or syringe pump 240; and/or a two-way fluid pathway between the intermediate container 40 or syringe pump 240 and the outlet fluid connector 234. In some embodiments, the multidirectional flow-control valve 41 can enable fluid withdrawn from a source container 39 to be partially or fully returned to a source container 39, in some situations, which can be particularly advantageous, such as, for example, during priming and/or purging of a fluid transfer module 31, although other situations in which this type of fluid flow are also contemplated and can be used.
In some embodiments, either or both of the fluid connectors 226, 234 can be industry standard medical connectors (e.g., luer connectors complaint with ISO 594 or compliant with any other industry standard) that are resealable and fluid-tight, such as the Clave® female medical connector or the Spiros® male medical connector or either of the male or female sides of a Chemolock® medical connector system, all sold by ICU Medical, Inc. Examples of embodiments of these and other devices, among many others, that can be used as fluid connectors 226, 234, or as any portions thereof, are included in U.S. Pat. Nos. 5,873,862; 7,998,134; and U.S. Published Patent Application No. 2014/0246616, all of which are incorporate by reference in this specification in their entireties. Any feature, structure, material, step, or component described and/or illustrated in any of the foregoing patents or published application can be used with or instead of any feature, structure, material, step, or component described and/or illustrated in any other portion of this specification.
In some embodiments, the fluid stopcock 230 can comprise a device that selectively permits fluid communication between and/or among multiple apertures and/or channels in the stopcock 230. For example, as shown in
i is a magnified partial front view of the fluid transfer unit 200 of
Returning to
In some embodiments, as shown, for example, in
As illustrated, in some embodiments, the fluid transfer module 31 (such as the fluid pump assembly 224) can form part of or constitute a closed system, in that: (i) liquid, or fluid, and/or vapors contained or sealed within the fluid transfer module 31 are prevented from exiting or escaping from the fluid transfer module 31, and/or (ii) the exiting or escaping of liquid, or fluid, and/or vapors is resisted in a clinically significant manner to diminish or avoid one or more clinical risks or negative outcomes, when the fluid transfer module 31 is disconnected from other components of the fluid transfer device 30. As shown, in some embodiments, the entire fluid pathway within the fluid transfer device 30 can constitute a closed system or a seal system. As used in this specification, the term “closed system” or “sealed” or any similar terms are used in accordance with their customary meanings in the field of medical infusion, and these terms include the requirement that fluids stay inside of the fluid transfer module 31 or the fluid transfer device 30 (or components thereof) under normal conditions or use such that any small amount of escaping fluid or vapors would not have any significant adverse clinical effects under normal conditions or use. In some embodiments, as shown in
i is a front perspective view of another type of fluid transfer module 31 that is removably attached to the fluid transfer unit 200 of
When the fluid transfer module 31 (e.g., the fluid pump assembly 224) is removably attached to the fluid transfer unit 200, a fluid-observation region on the conduit 238 of the fluid transfer device 30 can be positioned adjacent to or within an appropriate sensing distance from the one or more sensors 215. In the illustrated example, the fluid-observation region of the fluid transfer device 30 is at least a portion of the conduit 238 positioned between the multidirectional flow-control valve 41 (e.g., the fluid stopcock 230) and/or the intermediate container or pumping region 40 (e.g., the syringe pump 240). In some embodiments, the fluid-observation region of the fluid transfer device 30 can comprise a portion of the conduit 238 positioned between the multidirectional flow-control valve 41 (e.g., the fluid stopcock 230) and/or the intermediate container or pumping region 40 (e.g., the syringe pump 240). In some embodiments, the fluid-observation region can be positioned in another position on the fluid transfer device 30, or there can be multiple fluid-observation regions 30 located at a plurality of positions on the fluid transfer device 30.
In some embodiments, the one or more sensors 215 can be configured to determine whether there is liquid, gas (e.g., one or more bubbles), and/or a vacuum or partial vacuum, within a particular region or regions of the fluid transfer module 31 (e.g., fluid pump assembly 224). For example, as illustrated in the figures, the one or more sensors 215 can be configured to determine whether there is a medical fluid within at least a portion of the conduit 238 or whether there is a gas (e.g., ambient air or air bubbles) or a vacuum or partial vacuum within the conduit 238. In some embodiments, the one or more sensors 215 can determine whether there is a medical fluid within a portion of the conduit 238 or whether there is a gas (e.g., ambient air) or a vacuum or partial vacuum within a portion of the conduit 238. The one or more sensors 215 can be any suitable type of sensor, including but not limited to one or more acoustic sensors (e.g., ultrasonic sensors), infrared sensors, laser sensors, visual-spectrum optical sensors, motion flow sensors, or any other suitable sensors. One or more indicators 216, such as an indicator light or indicator speaker or other indicator, can be positioned on the sensor device 214 to indicate when the sensor device 214 is sensing a particular condition, such as when liquid is present in the fluid observation-region.
i also illustrates a fluid source container 39 in the form in this example of an inverted vial 246 attached to a vial adaptor 248 that is in turn attached to an inlet connector 32 in the form in this example of a male fluid connector 226a with a longitudinal locking mechanism. In some embodiments, the vial adaptor 248 comprises a filtered fluid inlet and/or outlet 250 and securing arms that are configured to securely receive the vial.
ii-2Dii illustrate various features, components, and arrangements that can be included in some embodiments of the fluid transfer device 30 shown in
As another example,
In some embodiments, the stopcock handle 245 can be removably attached to the stopcock 230. In some embodiments, the handle is configured to be manipulated (e.g., rotated, slid, pushed, and/or pulled) to manually actuate the stopcock into the various positions described above with reference to, for example,
ii is a rear perspective cross-sectional view of the fluid transfer unit 200 and the fluid pump assembly 224 shown in
The fluid transfer unit 200 may comprise one or more computer processors 297, 298, which can form part of or be in electronic communication with any or all of the electro-mechanical controller 36 of
In some embodiments, the fluid transfer unit 200 may comprise one or more presence sensors 294a, 294b, 294c. The one or more sensors 294a, 294b, 294c can be positioned within and/or on the housing 202 and can determine the presence or absence of one or more structures. In some embodiments, one or more of the sensors 294a, 294b, 294c can be infrared sensors or any other suitable sensor. One or more of the sensors 294a, 294b can determine whether the fluid source container 39 (such as vial 246), the source adapter 250, and/or the source fluid connector are present and/or connected to the fluid transfer unit 200. In some embodiments, sensor 294a may determine if a source container 246 connector, such as a male or female side of a Chemolock® medical connector system, is properly engaged with a corresponding connector on the fluid transfer unit 200, such as a Chemolock® connector 226a. The sensor 294b may determine if an intermediate container 40, such as fluid pump assembly 224, and/or connector 226a, such as a male or female side of a Chemolock® connector, is present and/or properly engaged with the housing 202 and/or a corresponding connector on a source container 246. The sensor 294c may determine whether the destination container 44, such as IV bag 244, and/or destination fluid connector are present and/or connected to the fluid transfer unit 200. In some embodiments, sensor 294c may determine if a destination container 44 connector, such as a male or female side of a Chemolock® medical connector system, is properly engaged with a corresponding connector on the fluid transfer unit 200, such as a Chemolock® connector 234a. In some embodiments, if any of sensor 294a, 294b, 294c determine that a component of the fluid transfer unit 200 is not present, the sensor 294a, 294b, 294c may send a signal to the controller 36 to prevent initiation of the fluid transfer process and/or terminate an ongoing fluid transfer. The sensor 294a, 294b, 294c may trigger an indicator signaling to a user that not all components are present or properly engaged with the fluid transfer unit 200.
As shown in
In some embodiments, one or more of the sensors 294a, 294b, 294c can be configured to detect the presence or absence of at least a portion of a fluid transfer module attached to the electronic fluid transfer device, such as a connector on the fluid transfer device. In some embodiments, one or more of the sensors (e.g., 294a, 294b) can be configured to additionally or alternatively detect the presence or absence of or connection with at least a portion of a fluid source system, such as a connector or vial adaptor or vial or bag or conduit that forms part of or is connected to a fluid source system. In some embodiments, one or more of the sensors (e.g., 294c) can be configured to additionally or alternatively detect the presence or absence of or connection with at least a portion of a fluid destination system, such as a connector or bag or conduit that forms part of or is connected to a fluid destination system. In some embodiments, the detection of one or more of the fluid transfer module 31, the detection of the connection to the fluid source system, and/or the detection to the connection to the fluid destination system can be a gating step or a required step for the computer processor or other component of the electro-mechanical controller to permit fluid transfer to begin or continue.
The user interface 78 can display or convey various items of information between a user and an electronic storage medium and/or can convey one or more executable instructions to a computer processor in the fluid transfer unit 200, or to electromechanical hardware in the fluid transfer unit 200, to perform one or more actions relating to fluid transfer. For example, the user interface 78 can receive and/or store (e.g., by user input or electronic transmission) the identity of the pharmacist or technician who is performing the fluid transfer, the identity of the patient, the name of the medical fluid, the volume of medical fluid to be transferred, the lot number, the expiration date of the medical fluid, and/or the date and time on which the fluid transfer was performed, etc. Also, as other examples, the user interface 78 can assist in controlling the fluid transfer by receiving and conveying commands from the user via the user interface 78 and/or displaying messages from the fluid transfer unit 200 regarding the progress and/or status of the fluid transfer, such as commands initiating the fluid transfer and/or halting the fluid transfer, and/or one or more messages demonstrating the amount of fluid transferred at any given moment, or the history of fluid transfers for a particular patient or pharmacist over a particular period, or one or more error messages indicating that the fluid transfer was not completed or that the fluid source container 39 is not connected or is empty, or the fluid destination container 44 is not connected or is full, or any other useful message.
A second channel of the stopcock 230 can be attached to an intermediate or measuring region 268 by way of a first conduit segment 260, a positive displacement conduit segment 270, and a second conduit segment 264. One or more coupling regions 262, 266 can be provided between the first conduit segment 260 and the positive displacement conduit segment 270, and between the positive displacement conduit segment 270 and the second conduit segment 264, and/or between the second conduit segment 264 and the intermediate or measuring region 268, as illustrated in
A source container 39 is illustrated in
As shown in
A positive displacement pump 1350 can be configured to receive the intermediate container or pumping region 40 in the form in this example of a positive displacement segment 270 of the positive displacement system 275. In some embodiments, the positive displacement pump 1350 is a peristaltic pump or another type of pump that includes one or more advancing fluid-pushing structures comprising one or more rotating or sliding or otherwise moving arms or wipers or rollers or kneaders or rotors that can be configured during use to constrict, pinch, occlude, squeeze, and/or compress a portion of the positive displacement segment 270 in a progressive or linear manner along the positive displacement segment 270 to forcefully advance or express an amount of fluid contained within the positive displacement segment 270 either upstream (toward the source container 39) or downstream (toward the destination container 44). Many other types of pumps can be used to move fluid forward or backward within the positive displacement segment 270.
In some embodiments, the fluid transfer unit 1318 can include a volume sensor 225 that is configured to provide information to help calculate the volume of liquid in the intermediate or measuring region 268. The volume sensor 225 can include any appropriate sensor or combination of sensors to provide information about the volume of the liquid, such as an optical sensor (such as a camera or a break-beam sensor), an infrared sensor, an acoustic sensor (e.g., an ultrasonic sensor), and/or a mass or weight sensor, etc. In some embodiments, the volume sensor can be internal and/or external to the fluid transfer unit 1318. In any embodiments in this specification, the tray 280, 56 or the support arm 242 or the pole stand 204 or any other support structure that holds or supports or contains any form of the destination container 44 and/or any form of the intermediate container or pumping region 40 can include any one of, or any combination of, any such sensors to help provide information about any characteristic of the liquid that has been transferred into the destination container 44, such as information about the volume, mass, weight, and/or any other characteristic of the transferred liquid. The computer processor can comprise one or more algorithms, subroutines, hardware, and/or program instructions configured to process one or more signals received from one or more of such sensors to calculate information regarding one or more of the liquid characteristics.
As illustrated, the fluid transfer module need not include an intermediate container and/or the fluid transfer module need not include a multidirectional flow-control valve; rather, the liquid from the source container 39 or vial 246 can be pumped or transferred directly into the destination container 44 or IV bag 248 (e.g., via the associated tubing and connectors of the fluid transfer module) by the positive displacement motion of the positive displacement pump 1350. The gas sensing region 231 of the fluid transfer module can be coupled with a gas sensor assembly 265 that is configured to sense whether gas (such as air) in a bubble or otherwise has entered into the fluid transfer module.
The fluid transfer process 600 begins at the start block 602. If a fluid transfer module 31 in the form in this example of a connector assembly (e.g., a multi-stroke pump assembly 224 or a positive displacement system 275, etc.) has not already been attached to a source container 39, then the source container 39 is attached to the connector assembly at block 604. If the connector assembly has already been attached to a source container 39 (or if it will be attached later), then the connector assembly is attached to a fluid transfer management system 74 in the form in this example of an electronic fluid-delivery device, such any of the fluid transfer units 50, 200, 1318, 1318a, or any other type of fluid transfer unit, at block 605.
In some situations, the connector assembly has previously been in use, such as when only a portion of the fluid in a source container 39 of a first connector assembly has been withdrawn but the connector assembly is temporarily disconnected or removed from the fluid transfer management system 74 to permit a second connector assembly attached to a source container 39 with a different type of therapeutic liquid to be coupled with the fluid transfer management system 74 for another type of fluid transfer. After the second connector assembly is used in the fluid transfer management system 74, the first connector assembly can be reattached in its original position in order to withdraw all or a portion of the remaining contents of the source container 39. Thus, in this example, among others, the first connector assembly has previously been in use.
If the connector assembly has not already been used, then in some instances the connector assembly can be “primed” at block 100 by filling the connector assembly with liquid and by removing gas, such as air, from the connector assembly. Priming may comprise filling the interior cavity of connector 234 and/or connecter 226 prior to transferring of fluid to a destination container 44. In some situations, gas needs to be removed from the connector assembly to avoid transferring air into a destination container 44 that will be transferred entirely into a patient's blood vessel. For example, priming may be useful where it is desirable to remove any clinically significant amount of air prior to transferring of fluid to a destination container 44, such as a syringe containing liquid that will be injected directly into a patient or into a patient's fluid line. In some situations, such as when an IV bag 248 is used, the concern of harming the patient 44 is not as severe, since an IV bag 248 is typically gravity-fed and the gas migrates to the top of the bag without entering the patient's blood vessel anyway. In some instances, the main concern is that a transfer of gas from the connector assembly into the destination container 44 might be mistakenly counted as a transfer of therapeutic liquid into the destination container 44, which may result in an undercount of the amount of therapeutic liquid provided to the patient, or it may lower the concentration of therapeutic liquid provided to the patient. In some embodiments, any one and/or all of the concerns may be resolved through various methods described in further detail below. An example of the priming process is illustrated and described more fully in
If the connector assembly has already been used, then the connector assembly does not need to be filled with liquid or primed. However, the connector assembly may have acquired air bubbles inside of it, such as during the disconnection process, or from partial vaporization of the liquid within the connector assembly, or by partial external spillage. The air bubbles can be substantially or entirely removed during a purging step in block 608, which is explained more fully in connection with block 123 of
After the source container 39 and the destination container 44 are attached to the fluid transfer module 31 (or connector assembly), the fluid transfer device 30 can proceed to transfer fluid from the source container 39, through the fluid transfer module 31, to the destination container 44, which is illustrated and explained more fully in
An example of the process of priming and purging is illustrated more fully in
As previously discussed, priming sequences detailed in
At block 110, the intermediate container 40 can be actuated (such as by exerting a pulling force on the actuating stem 241 of a syringe pump 240) to expand or increase the volume within the intermediate container 40, thereby lowering the pressure or creating at least a partial vacuum within the intermediate container 40, which can also lower the pressure or create at least a partial vacuum within the fluid control valve 41 and the outlet connector 42. The intermediate container 40 can be actuated by an electronic signal or series of signals sent from the computer processor of the fluid transfer management system 74 to an electromechanical driver in the fluid transfer management system 74 that is configured to be removably linked to or mechanically connected (either directly or indirectly) with the intermediate container 40 by way of a moveable actuator. For example, the electromechanical driver can be a motor, such as a stepper motor, that is mechanically linked to a moveable actuator in the form in this example of the movable platform 222 of the fluid transfer unit 200. As illustrated in
At block 114, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the multidirectional flow-control valve 41 to close an outlet port on the fluid-control valve 41 (e.g., an outlet port directly connected to an outlet conduit 236 that is configured to be placed in fluid communication with the destination container 44), and to open simultaneously or generally concurrently a fluid pathway between the inlet port on the fluid-control valve 41 and the intermediate outlet port on the fluid-control valve 41. The closing of the outlet port seals off and preserves the lower pressure or partial vacuum within the outlet conduit 236 and the outlet fluid connector 42 or outlet male fluid connector 234. The inlet connector 32 (and source container 39), fluid-control valve 41, and intermediate container 40 can then be positioned in fluid communication with each other, while the outlet connector 42 can be isolated or not in fluid communication with these components. An example of this configuration 116 shows an inverted vial 246 attached to a stopcock 230 by way of a male fluid connector 226 that is in fluid communication with the stopcock 230 and the syringe pump 240, while the male fluid connector 234 attached to the outlet port and outlet conduit 236 is blocked from fluid communication with the stopcock 230 and other components.
As illustrated, when the fluid-control valve 41 or stopcock 230 is actuated as illustrated in block 114, fluid from the source container 39 rapidly flows into the multi-directional flow control valve 41 or stopcock 230 and the intermediate container 40 or syringe pump 240, since the pressure in the source container 39 is higher than the pressure of the partial vacuum within the flow control valve 41 and the intermediate container 40. In some embodiments, after the migration of fluid from the source container 39 to the flow-control valve 41 and intermediate container 40, only a small amount of air bubbles or a small air region is present in the intermediate container 40. The air region or air bubbles generally migrate upward within the syringe pump 240, since the air is less dense than the fluid transferred from the source container 39, which is typically liquid. Additional air may still be present within the flow control valve 41.
At block 118, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the electromechanical driver. In some embodiments, as illustrated, the actuation of the electromechanical driver can upwardly move the movable platform 222 and push the actuating stem 241 into the syringe pump 240, thereby decreasing the volume and increasing the pressure within the intermediate container 40 or syringe pump 240 to urge or push liquid and any accompanying air within the intermediate container 40 or syringe pump 240 backward or in reverse from the intermediate container 40 or syringe pump 240 into the flow-control valve 41, the inlet connector 226, and the source container. This reverse or backward flow of liquid can help to “prime” the fluid pathway between the source container 39, the flow control valve 41, and the intermediate container 40, to remove all or a portion of the air within or between these components to enable it to later be replaced with liquid. For example, when the air is pushed into or returned to the source container 39 by the reverse or backward flow, the air migrates to the top of the inside of the source container 39, since its density is lower than that of the surrounding liquid, and when the intermediate container 40 is actuated to pull fluid back into it, the liquid at the bottom of the source container 39 moves through the inlet connector 226 and associated structures into the intermediate container 40, rather than the air.
At block 120, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the multidirectional flow-control valve 41 to close an outlet port on the fluid-control valve 41 (e.g., an outlet port directly connected to an outlet conduit 238 in fluid communication with the intermediate container 40), and to open simultaneously or generally concurrently a fluid pathway between the inlet port on the fluid-control valve 41 (in fluid communication with the source container 39) and the outlet port on the fluid-control valve 41 that is in fluid communication with the outlet fluid connector 42. An example of this configuration 122 shows the inverted vial 246 in fluid communication with the stopcock and the outlet fluid connector 42, but not the syringe pump 240.
In some embodiments, in one or more previous steps such as at blocks 110 and 114, the air within the outlet port and outlet fluid connector 42, and the associated conduit(s), has been evacuated or the pressure within these components has been diminished, and then the interior regions of these components has been sealed off or isolated by actuating the flow-control valve 41, in order to close the fluid pathway inside of these components from one or more or all of the other components of the fluid transfer module 31. When the multidirectional flow-control valve 41 is actuated at block 120 to open the outlet port, the outlet fluid connector 42, and/or the associated tubing, to be in fluid communication with the flow-control valve 41 and the source container 39, then liquid from the source container 39 rapidly flows through the flow-control valve 41 or stopcock 230 and into the outlet fluid connector 42, since the pressure in the source container 39 and the flow-control valve 41 is much higher than the pressure of the partial vacuum within the outlet fluid connector 42 and there is very little air to block the entering liquid. This process can prime the outlet fluid connector 42 and its associated tubing (such as conduit 238), without producing air bubbles or without producing an unduly or unmanageably large amount of air bubbles in the fluid pathway.
At this point, the fluid transfer module 31 is usually primed, in that all or substantially all of the gas or air has been removed from the fluid transfer module 31 and replaced with liquid from the source container 39. In this context, “substantially” all of the gas or air or any similar phrase should be understood to mean that enough gas or air has been removed that no clinically significant imprecise measurements or other adverse results would be caused by any remaining gas or air. Referring back to
At block 123, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the multidirectional flow-control valve 41 to close the outlet port on the fluid-control valve 41 that is in fluid communication with the outlet connector 234, and to open simultaneously or generally concurrently a fluid pathway between the inlet port on the fluid-control valve 41 that is in fluid communication with the source container 39 and the outlet port on the fluid-control valve 41 that is in fluid communication with the intermediate container 40. An example of this configuration 123 shows the inverted vial 246 in fluid communication with the stopcock and the syringe pump 240 but not the outlet fluid connector 42. At this point, the computer processor can send a signal or series of signals to the electromechanical movable platform 222 to actuate the syringe pump 240 to draw in the proper amount of therapeutic fluid to be transferred to the destination container 44.
In some embodiments, when the fluid-control valve 41 or stopcock 230 is actuated, the fluid transfer management system 74 at block 118′ may actively transfer fluid into the intermediate container 40 or syringe pump 240. The computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the electromechanical driver. In some embodiments, as illustrated in 116′, the actuation of the electromechanical driver can downwardly move the movable platform 222 and pull the actuating stem 241 out of the syringe pump 240, thereby increasing the volume and decreasing the pressure within the intermediate container 40 or syringe pump 240 to urge or pull liquid within the source container 39 into the intermediate container 40 or syringe pump 240. In some embodiments, after the migration of fluid from the source container 39 to the flow-control valve 41 and intermediate container 40, a small amount of air bubbles or a small air region may be present in the intermediate container 40. The air region or air bubbles generally migrate upward within the syringe pump 240, since the air is less dense than the fluid transferred from the source container 39, which is typically liquid. Additional air may still be present within the flow control valve 41.
At block 118″, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the electromechanical driver. In some embodiments, as illustrated, the actuation of the electromechanical driver can upwardly move the movable platform 222 and push the actuating stem 241 into the syringe pump 240, thereby decreasing the volume and increasing the pressure within the intermediate container 40 or syringe pump 240 to urge or push liquid and any accompanying air within the intermediate container 40 or syringe pump 240 backward or in reverse from the intermediate container 40 or syringe pump 240 into the flow-control valve 41, and the inlet connector 226. This reverse or backward flow of liquid can “prime” the fluid pathway between the source container 39, the flow control valve 41, and the intermediate container 40, to remove all or a portion of the air within these components and replace it with liquid. The backward flow of liquid may remove any air present in the syringe pump 240, thereby preventing the later transfer of air to the outlet port, outlet conduit 236, and/or outlet container. The movable platform 222 may be positioned to inject sufficient flow of fluid into the source container 39 to prime the fluid pathway between the source container 39, the flow control valve 41, and the inlet connector 226, while maintaining an amount of fluid within the intermediate container 40 sufficient to prime the outlet connector 42. The amount of liquid to prime the outlet connector 42 may include a volume of liquid about at least equal to the volume of the interior cavity of the outlet connector 42.
At the beginning in block 106′, the multidirectional flow-control valve 41 can be mechanically actuated by the electromechanical controller 36 of the fluid transfer device 30 to close an inlet port on the fluid-control valve 41 and open simultaneously or generally concurrently a fluid pathway between an outlet port on the fluid-control valve 41 and an intermediate outlet port on the fluid-control valve 41. The outlet connector 42, fluid-control valve 41, and intermediate container 40 can then be positioned in fluid communication with each other, while the source container 39 can be isolated or not in fluid communication with these components. An example of this configuration 108′ shows an inverted vial 246 attached to a stopcock 230 by way of a male fluid connector 226 that is blocked from fluid communication with the stopcock 230 and other components, while a syringe pump 240 attached to the stopcock 230 is in fluid communication through the stopcock 230 with the outlet fluid connector 234.
Block 106′ and 106″ may evacuate any air within the outlet port and outlet fluid connector 42 or diminish the pressure within these components. The computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the electromechanical driver. In some embodiments, the actuation of the electromechanical driver can downwardly move the movable platform 222 and pull the actuating stem 241 out of the syringe pump 240, thereby increasing the volume and decreasing the pressure within the intermediate container 40 or syringe pump 240 to urge or pull liquid and any accompanying air within the outlet port and outlet fluid connector 42 into the intermediate container 40 or syringe pump 240. This reverse or backward flow of liquid can “prime” the fluid pathway between the destination container, the outlet port, and the outlet fluid connector 42, to remove all or a portion of the air within these components and replace it with liquid. In some embodiments, as illustrated in block 106″, the actuation of the electromechanical driver can upwardly move the movable platform 222 and push the actuating stem 241 into the syringe pump 240, thereby decreasing the volume and increasing the pressure within the intermediate container 40 or syringe pump 240 to urge or push liquid within the intermediate container 40 or syringe pump 240 into the outlet port and outlet fluid connector 42. This flow of liquid can prime the fluid pathway between the destination container, the outlet port, and the outlet fluid connector 42, to remove all or a portion of the air within these components and replace it with liquid.
At block 123′, the computer processor of the fluid transfer management system 74 can send an electronic signal to the electromechanical controller 36 of the fluid transfer device 30 to mechanically actuate the multidirectional flow-control valve 41 to close the outlet port on the fluid-control valve 41 that is in fluid communication with the outlet connector 234, and to open simultaneously or generally concurrently a fluid pathway between the inlet port on the fluid-control valve 41 that is in fluid communication with the source container 39 and the outlet port on the fluid-control valve 41 that is in fluid communication with the intermediate container 40. An example of this configuration 123′ shows the inverted vial 246 in fluid communication with the stopcock and the syringe pump 240 but not the outlet fluid connector 42. At this point, the computer processor can send a signal or series of signals to the electromechanical movable platform 222 to actuate the syringe pump 240 to draw in the proper amount of therapeutic fluid to be transferred to the destination container 44.
If, at any other stage of
This back-and-forth or drawing-and-expelling movement of liquid between the source container 39 and the intermediate container 40 can help to purge air from the fluid transfer module 31 because any air present will normally rise to the top of the central chamber of the intermediate container 40, or the top of the conduit 238, or the top of the fluid-control valve 41, and/or the top of the conduit 232 (since the gas or air is less dense than the liquid surrounding it), and then the gas or air can be returned or moved into the source container 39 during the return stroke before the liquid in the central chamber of the intermediate container 40 is returned or moved into the source container 39. If a first iteration of the back-and-forth or drawing-and-expelling movement does not sufficiently purge any significant amount of air from the fluid transfer module 31, then a second iteration or a plurality of additional iterations of the back-and-forth or drawing-and-expelling movement can be performed.
Any single step or grouping of steps of
As illustrated in the example of
After or during the transfer of fluid at block 506, the sensor 215 can constantly or intermittently monitor one or more regions of the fluid transfer module 31, such as a fluid-observation region on the conduit 238, to determine whether a gas, such as air, is present or has migrated into the fluid transfer module 31, as represented at block 510. If a significant gas bubble is detected (e.g., a gas bubble that is approximately equal to or greater than 0.1 mL, or approximately equal to or greater than 0.25 mL, or approximately equal to or greater than 0.5 mL, etc.), then the computer processor can query a memory 84 in the fluid transfer management system 74 at block 508 to determine whether a purge of such gas bubble (or a predetermined plurality of purges, such as two purges or three purges, or more) has already been performed during this particular stage in the fluid transfer process. If a purge or a predetermined plurality of purges has not yet been performed at this stage in the fluid transfer, then a gas purge can be performed at block 504. The gas purge can be performed according to any or a portion of the procedures or steps described in this specification, or according to one or more additional or alternative procedures or steps. After the gas purge is completed, the computer processor can return to block 506 by sending an electronic signal or a series of electronic signals to the electromagnetic driver to transfer a quantity of liquid from the source container 39 to the intermediate container 40. If a purge or a predetermine plurality of purges has been performed at this stage in the fluid transfer, then the computer processor proceeds to block 514 and stops the transfer of liquid and displays an error message to the user.
The error message can communicate to a user than the vial is presumed to be empty and should be replaced with a full vial since no liquid is passing from the source container 39 into the intermediate container 40 and/or the error message can communicate one or more other messages, such as a message encouraging the user to check the fluid couplings in the fluid transfer device 30.
If the vial is replaced, then the computer processor can proceed to block 605 of
In some embodiments, the electromagnetic driver may comprise a stepper motor that transfers a particular volume of fluid in discrete “steps” made by the stepper motor. Each “step” of the stepper motor may correspond to a set volume of fluid being transferred. The computer processor may determine the total volume of fluid transferred corresponding to the number of “steps” the syringe pump 240 is moved. During each “step” of the stepper motor, the sensor 215 may determine whether an air bubble is present in the volume of fluid transferred. If the sensor 215 detects an air bubble during a “step,” the computer processor may identify the step as no volume of liquid being transferred to the destination chamber 44. If the sensor 215 does not detect an air bubble during a “step,” the computer processor may identify the step as a discrete volume of liquid being transferred to the destination chamber 44. If multiple quantities of liquid have been transferred by multiple “steps,” then the computer processor can store in the memory 84 a sum of all the liquid quantities transferred during each “step” identified as liquid being transferred. Upon termination of the fluid transfer sequence, the computer processor may calculate the total sum of all liquid quantities transferred to determine the rate of flow of the fluid transfer and the total volume of liquid transferred.
In some embodiments, the electromagnetic driver may comprise a continuous motor. The computer processor may utilize any one or more structures, components, or steps in the method and systems as described above to calculate the rate of flow and total volume of fluid transferred to the destination chamber 44. The continuous motor may be used in combination with the sensor 215 to measure discrete volume transfers in the continuous motion. The motion of the continuous motor may be identified in discrete “steps” with the motor transferring a set volume of fluid within each “step.” The sensor 215 may determine whether the discrete “steps” of fluid transferred by the continuous motor comprise air or liquid. Upon termination of the fluid transfer sequence, the computer processor may calculate the total sum of all liquid quantities transferred to determine the rate of flow of the fluid transfer and the total volume of liquid transferred.
As previously discussed, the sensor 215 may comprise any suitable type of sensor. In some embodiments, the sensor 215 may comprise an acoustic sensor. The acoustic sensor may be used as a sonic device to determine whether a discrete volume of transferred comprises a liquid or air transfer. In some embodiments, the acoustic sensor may comprise a sonic emitter, such as a speaker, and a sonic receiver, such as a microphone. The sonic emitter may produce a sound wave that travels through at least a portion of the fluid transfer module 31 and/or fluid within the fluid transfer module 31 that is being transferred by the electromagnetic driver. The sonic receiver may detect the sound wave after travelling through the fluid, and the sound wave may vary based on whether the wave travelled through a liquid medium or a gaseous medium (e.g., the amplitude, wavelength, pitch, and/or frequency, etc. of the sound wave may vary). The acoustic sensor may use any variations in the received sound wave to determine the presence of air or liquid within an amount of fluid through which the emitted sound wave has passed that is going to be transferred or is being transferred by the electromagnetic driver.
In some embodiments, the acoustic sensor can provide decreased processing requirements, thus increasing response speed, as compared to some other sensor types. The decreased processing requirements and increased response speed can permit the computer processor to increase sampling rates and/or fluid flow rates. The sampling rate may be sufficiently high to provide for generally real-time resolution since the processing requirements of some acoustic sensors are much less than some other types of sensors. The sampling rate can be at least about 30 KHz and/or less than or equal to about 70 KHz. The sensor 125 may comprise an optical sensor. The optical sensor may comprise an optical encoder located in the sensor device 214.
In some embodiments, the electromagnetic driver may be used in combination with sensor 225 to function as a flowmeter similar. While the flowmeter functionality is discussed in terms of transferring fluid from the intermediate container 40 or the syringe pump 240 to the destination container 44 or IV bag 244, it is to be understood that the functionality may apply in any type or combination of fluid transfer devices or otherwise. For example, the electromagnetic driver and the sensor 215 may be used as a flow meter to measure the rate of flow of fluid between the source container 39 or inverted vial 246 and the intermediate container 40 or the syringe pump 240. The application of a flowmeter may apply to fluid transfer from the destination container 44 to the intermediate container 40 or syringe pump 240.
With regard to
In some embodiments, the memory 84 can store the maximum volume of the particular intermediate container 40 utilized in the fluid transfer module 31. If the sum of fluid transfers during a particular fluid transfer procedure is sufficiently large that another transfer of a quantity of liquid at block 506 will exceed the maximum volume of the intermediate container 40, then the computer processor can actuate the flow-control valve 41 to close off the fluid pathway to the source container 39 and open the fluid pathway between the intermediate container 40 and the destination container 44, and the computer processor can actuate the moveable platform 222 to force the fluid in the intermediate container 40 into the destination container 44. The computer processor can then actuate the flow-control valve 41 to close off the fluid pathway to the destination container 44 and again open the fluid pathway between the source container 39 and the intermediate container 40, and the computer processor can return to block 506 and proceed with the algorithm of
In some embodiments, the electronic fluid transfer management system 74 can comprise a compliance or verification system with a recorder for capturing and storing information relating to one or more parameters of a particular fluid transfer procedure. For example, in some embodiments, the electronic fluid transfer management system 74 can comprise one or more cameras for capturing one or more images of various components or stages in the transfer of fluid and one or more memories 84 for storing such one or more images. Examples of one or more of such images include an image of the source container 39 (e.g., including the product label on the source container 39), an image of the intermediate container or pumping region 40 when filled with liquid immediately before transferring the liquid into the destination container 44, and/or an image of the destination container 44 when containing or filled with the transferred liquid (e.g., including the patient-information label on the destination container 44). The compliance or verification system can record and store information relating to the patient's identity, the healthcare worker in control of the electronic fluid transfer management system 74 during a particular fluid transfer, the healthcare worker who requested the medical fluid for the patient, the date and time, and/or the type of medical fluid transferred into the destination container, etc. Any or all of this information can be transmitted to and/or retrieved from the patient and/or drug information storage device or network 70.
The fluid transfer module 31 can be manufactured in a series of steps that include providing any or all of the components illustrated and/or described in this specification and/or assembling such components as illustrated and/or described in this specification. In a method of enabling the use of a fluid transfer module 31, a fluid transfer module 31 can be provided to a user and instructions can be provided (e.g., in written form, as part of a display on a screen of a user interface, on a website, in printed directions-for-use, on product packaging, in spoken form, or otherwise) to attach or couple the fluid transfer module 31 to a fluid transfer device 30 that is configured to transfer fluid in any manner disclosed in this specification. For example, any embodiment of a fluid transfer module 31 can be provided to a user, such as the multi-stroke fluid pump assembly 224 of
As shown in
Although this invention has been disclosed in the context of certain embodiments and examples, it will be understood by those skilled in the art that the present invention extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses of the invention and obvious modifications and equivalents thereof. In addition, while several variations of the invention have been shown and described in detail, other modifications, which are within the scope of this invention, will be readily apparent to those of skill in the art based upon this disclosure. It is also contemplated that various combinations or sub-combinations of the specific features and aspects of the embodiments may be made and still fall within the scope of the invention. It should be understood that various features and aspects of the disclosed embodiments can be combined with, or substituted for, one another in order to form varying modes of the disclosed invention. Thus, it is intended that the scope of the present invention herein disclosed should not be limited by the particular disclosed embodiments described above, but should be determined only by a fair reading of the claims that follow.
This application is a continuation of U.S. patent application Ser. No. 16/182,503, filed Nov. 6, 2018 and issued as U.S. Pat. No. 10,420,927 on Sep. 24, 2019, titled “SYSTEMS, METHODS, AND COMPONENTS FOR TRANSFERRING MEDICAL FLUIDS,” which is a divisional of U.S. patent application Ser. No. 15/991,385, filed May 29, 2018 and issued as U.S. Pat. No. 10,188,849 on Jan. 29, 2019, titled “SYSTEMS, METHODS, AND COMPONENTS FOR TRANSFERRING MEDICAL FLUIDS,” which claims the benefit under 35 U.S.C. § 120 and 35 U.S.C. § 365(c) as a continuation of International Application No. PCT/US2016/064467, designating the United States, with an international filing date of Dec. 1, 2016, titled “SYSTEMS, METHODS, AND COMPONENTS FOR TRANSFERRING MEDICAL FLUIDS,” which claims priority to U.S. application Ser. No. 62/263,541, filed Dec. 4, 2015, titled “SYSTEMS, METHODS, AND COMPONENTS FOR TRANSFERRING MEDICAL FLUIDS” and claims priority to U.S. application Ser. No. 62/360,900, filed Jul. 11, 2016, titled “SYSTEMS, METHODS, AND COMPONENTS FOR TRANSFERRING MEDICAL FLUIDS,” the entire contents of each of which are incorporated by reference herein and made a part of this specification.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1923501 | Perry | Aug 1933 | A |
| 3157201 | Littmann | Nov 1964 | A |
| 3344785 | Hamilton | Oct 1967 | A |
| D222956 | Sato | Feb 1972 | S |
| D222957 | Sato | Feb 1972 | S |
| D236163 | Manno | Jul 1975 | S |
| 4005710 | Zeddies et al. | Feb 1977 | A |
| 4084606 | Mittleman | Apr 1978 | A |
| 4187890 | Stach et al. | Feb 1980 | A |
| 4190048 | Sampson | Feb 1980 | A |
| 4262671 | Kersten | Apr 1981 | A |
| 4306705 | Svensson | Dec 1981 | A |
| 4336802 | Stone et al. | Jun 1982 | A |
| 4367736 | Gupton | Jan 1983 | A |
| D268206 | Kosako | Mar 1983 | S |
| D268284 | Manno et al. | Mar 1983 | S |
| 4397335 | Doblar et al. | Aug 1983 | A |
| 4410321 | Pearson et al. | Oct 1983 | A |
| 4423741 | Levy | Jan 1984 | A |
| 4519792 | Dawe | May 1985 | A |
| 4534758 | Akers et al. | Aug 1985 | A |
| 4559043 | Whitehouse et al. | Dec 1985 | A |
| 4561856 | Cochran | Dec 1985 | A |
| 4666429 | Stone | May 1987 | A |
| 4670007 | Wheeldon et al. | Jun 1987 | A |
| 4683916 | Raines | Aug 1987 | A |
| 4755172 | Baldwin | Jul 1988 | A |
| 4759756 | Forman et al. | Jul 1988 | A |
| 4768568 | Fournier et al. | Sep 1988 | A |
| 4778450 | Kamen | Oct 1988 | A |
| 4819684 | Zaugg et al. | Apr 1989 | A |
| 4863429 | Baldwin | Sep 1989 | A |
| D305165 | Rudolph et al. | Dec 1989 | S |
| 4922975 | Polaschegg | May 1990 | A |
| 4936841 | Aoki et al. | Jun 1990 | A |
| 4969874 | Michel et al. | Nov 1990 | A |
| 4972876 | Kabata et al. | Nov 1990 | A |
| 4976590 | Baldwin | Dec 1990 | A |
| 4995268 | Ash et al. | Feb 1991 | A |
| 5024347 | Baldwin | Jun 1991 | A |
| 5037390 | Raines et al. | Aug 1991 | A |
| 5114580 | Ahmad et al. | May 1992 | A |
| D328952 | Arioka | Aug 1992 | S |
| 5176658 | Ranford | Jan 1993 | A |
| 5224937 | van der Heiden et al. | Jul 1993 | A |
| 5254096 | Rondelet et al. | Oct 1993 | A |
| 5256155 | Yerlikaya et al. | Oct 1993 | A |
| 5288290 | Brody | Feb 1994 | A |
| 5300044 | Classey et al. | Apr 1994 | A |
| D348101 | Poli et al. | Jun 1994 | S |
| 5334211 | Shiber | Aug 1994 | A |
| 5336201 | von der Decken | Aug 1994 | A |
| D352778 | Irvin | Nov 1994 | S |
| 5378231 | Johnson et al. | Jan 1995 | A |
| 5405333 | Richmond | Apr 1995 | A |
| 5423791 | Bartlett | Jun 1995 | A |
| 5431201 | Torchia et al. | Jun 1995 | A |
| 5439451 | Collinson et al. | Aug 1995 | A |
| 5466220 | Brenneman | Nov 1995 | A |
| 5609572 | Lang | Mar 1997 | A |
| 5645538 | Richmond | Jul 1997 | A |
| 5647845 | Haber et al. | Jul 1997 | A |
| 5676346 | Leinsing | Oct 1997 | A |
| 5685866 | Lopez | Nov 1997 | A |
| 5776345 | Truitt et al. | Jul 1998 | A |
| 5782816 | Werschmidt et al. | Jul 1998 | A |
| 5807312 | Dzwonkiewicz | Sep 1998 | A |
| 5810792 | Fangrow, Jr. et al. | Sep 1998 | A |
| 5871110 | Grimard et al. | Feb 1999 | A |
| 5871500 | Jepson et al. | Feb 1999 | A |
| D408079 | Ellis | Apr 1999 | S |
| 5897526 | Vaillancourt | Apr 1999 | A |
| 5904666 | DeDecker et al. | May 1999 | A |
| 5910252 | Truitt et al. | Jun 1999 | A |
| 5935106 | Olsen | Aug 1999 | A |
| 5947951 | Ortiz et al. | Sep 1999 | A |
| 5968014 | Neftel et al. | Oct 1999 | A |
| 5989237 | Fowles et al. | Nov 1999 | A |
| 6059747 | Bruggeman et al. | May 2000 | A |
| 6110153 | Davis et al. | Aug 2000 | A |
| RE36871 | Epstein et al. | Sep 2000 | E |
| 6123685 | Reynolds | Sep 2000 | A |
| 6132404 | Lopez | Oct 2000 | A |
| 6152900 | Mayer | Nov 2000 | A |
| 6171484 | Schnell et al. | Jan 2001 | B1 |
| 6179823 | Niedospial, Jr. | Jan 2001 | B1 |
| 6193675 | Kraus et al. | Feb 2001 | B1 |
| 6193689 | Woodard | Feb 2001 | B1 |
| 6202708 | Bynum | Mar 2001 | B1 |
| 6221041 | Russo | Apr 2001 | B1 |
| 6245048 | Fangrow, Jr. et al. | Jun 2001 | B1 |
| 6287289 | Niedospial, Jr. | Sep 2001 | B1 |
| 6302864 | Nowosielski | Oct 2001 | B1 |
| 6425497 | Chu et al. | Jul 2002 | B1 |
| 6474375 | Spero et al. | Nov 2002 | B2 |
| 6485472 | Richmond | Nov 2002 | B1 |
| 6551299 | Miyoshi et al. | Apr 2003 | B2 |
| 6558365 | Zinger et al. | May 2003 | B2 |
| 6572256 | Seaton et al. | Jun 2003 | B2 |
| 6585229 | Cote, Sr. et al. | Jul 2003 | B2 |
| 6590167 | Clare | Jul 2003 | B2 |
| 6599273 | Lopez | Jul 2003 | B1 |
| 6623455 | Small et al. | Sep 2003 | B2 |
| 6629956 | Polidoro et al. | Oct 2003 | B1 |
| 6651956 | Miller | Nov 2003 | B2 |
| 6663586 | Verkaart et al. | Dec 2003 | B2 |
| 6689108 | Lavi et al. | Feb 2004 | B2 |
| 6699230 | Jaafar et al. | Mar 2004 | B2 |
| 6711460 | Reese | Mar 2004 | B1 |
| 6726672 | Hanly et al. | Apr 2004 | B1 |
| 6793651 | Bennett et al. | Sep 2004 | B1 |
| 6813868 | Baldwin et al. | Nov 2004 | B2 |
| 6854620 | Ramet | Feb 2005 | B2 |
| 6908459 | Harding et al. | Jun 2005 | B2 |
| 6915823 | Osborne et al. | Jul 2005 | B2 |
| 6948522 | Newbrough et al. | Sep 2005 | B2 |
| 6953450 | Baldwin et al. | Oct 2005 | B2 |
| 6985870 | Martucci et al. | Jan 2006 | B2 |
| 6991002 | Osborne et al. | Jan 2006 | B2 |
| 6994315 | Ryan et al. | Feb 2006 | B2 |
| 6997917 | Niedospial, Jr. et al. | Feb 2006 | B2 |
| 7006894 | De La Huerga | Feb 2006 | B2 |
| 7017623 | Tribble et al. | Mar 2006 | B2 |
| 7086431 | D'Antonio et al. | Aug 2006 | B2 |
| 7108024 | Navarro | Sep 2006 | B2 |
| 7117901 | Martinell Gisper-Sauch | Oct 2006 | B2 |
| 7117902 | Osborne | Oct 2006 | B2 |
| 7128105 | Tribble et al. | Oct 2006 | B2 |
| 7163031 | Graves et al. | Jan 2007 | B2 |
| 7163035 | Khan et al. | Jan 2007 | B2 |
| 7175615 | Hanly et al. | Feb 2007 | B2 |
| 7194336 | DiGianfilippo et al. | Mar 2007 | B2 |
| 7260447 | Osborne | Aug 2007 | B2 |
| 7317967 | DiGianfilippo et al. | Jan 2008 | B2 |
| 7343224 | DiGianfilippo et al. | Mar 2008 | B2 |
| 7343943 | Khan et al. | Mar 2008 | B2 |
| 7351226 | Herskowitz | Apr 2008 | B1 |
| 7354426 | Young | Apr 2008 | B2 |
| 7392638 | Baldwin et al. | Jul 2008 | B2 |
| 7396051 | Baldwin et al. | Jul 2008 | B2 |
| 7398183 | Holland et al. | Jul 2008 | B2 |
| 7398802 | Baker | Jul 2008 | B2 |
| 7418981 | Baker et al. | Sep 2008 | B2 |
| 7442186 | Blomquist | Oct 2008 | B2 |
| 7454314 | Holland et al. | Nov 2008 | B2 |
| 7488311 | Domkowski et al. | Feb 2009 | B2 |
| 7499581 | Tribble et al. | Mar 2009 | B2 |
| 7527619 | Domkowski et al. | May 2009 | B2 |
| 7530211 | McErlean et al. | May 2009 | B2 |
| 7530974 | Domkowski et al. | May 2009 | B2 |
| 7538858 | Mackey | May 2009 | B2 |
| D594120 | Berberich et al. | Jun 2009 | S |
| D596291 | Berberich et al. | Jul 2009 | S |
| 7566326 | Duchon et al. | Jul 2009 | B2 |
| 7590021 | Michalak et al. | Sep 2009 | B2 |
| 7610115 | Rob et al. | Oct 2009 | B2 |
| 7630788 | Reese | Dec 2009 | B1 |
| 7630789 | Broadfield et al. | Dec 2009 | B2 |
| 7632261 | Zinger et al. | Dec 2009 | B2 |
| 7654976 | Peterson et al. | Feb 2010 | B2 |
| 7681606 | Khan et al. | Mar 2010 | B2 |
| 7685026 | McGrady et al. | Mar 2010 | B1 |
| D616092 | Domkowski et al. | May 2010 | S |
| 7717897 | Burg et al. | May 2010 | B2 |
| D620108 | Eitenmueller et al. | Jul 2010 | S |
| 7753085 | Tribble et al. | Jul 2010 | B2 |
| 7758560 | Connell et al. | Jul 2010 | B2 |
| 7789850 | Roger | Sep 2010 | B2 |
| 7814731 | Bender et al. | Oct 2010 | B2 |
| 7850051 | Py et al. | Dec 2010 | B2 |
| 7867215 | Akerlund et al. | Jan 2011 | B2 |
| 7882863 | Pestotnik | Feb 2011 | B2 |
| 7895053 | Holland et al. | Feb 2011 | B2 |
| 7900658 | Osborne et al. | Mar 2011 | B2 |
| 7913720 | Tribble et al. | Mar 2011 | B2 |
| 7963201 | Willoughby et al. | Jun 2011 | B2 |
| 7963954 | Kavazov | Jun 2011 | B2 |
| 7967202 | Durrell et al. | Jun 2011 | B2 |
| 7981381 | Lurvey et al. | Jul 2011 | B2 |
| 7997304 | Ranalletta | Aug 2011 | B2 |
| 8034041 | Domkowski et al. | Oct 2011 | B2 |
| 8037659 | Osborne et al. | Oct 2011 | B2 |
| 8065161 | Howard et al. | Nov 2011 | B2 |
| 8075545 | Moy et al. | Dec 2011 | B2 |
| 8091727 | Domkowski | Jan 2012 | B2 |
| 8091860 | Thompson et al. | Jan 2012 | B2 |
| 8104644 | Py et al. | Jan 2012 | B2 |
| 8117809 | McErlean et al. | Feb 2012 | B2 |
| 8140351 | Tribble et al. | Mar 2012 | B2 |
| 8141601 | Fehr et al. | Mar 2012 | B2 |
| 8151835 | Khan et al. | Apr 2012 | B2 |
| 8162903 | Reilly et al. | Apr 2012 | B2 |
| 8162914 | Kraushaar et al. | Apr 2012 | B2 |
| 8162915 | Brandenburger et al. | Apr 2012 | B2 |
| D660423 | Hermle | May 2012 | S |
| 8172823 | Rondeau et al. | May 2012 | B2 |
| 8182744 | Mlodzinski et al. | May 2012 | B2 |
| 8197459 | Jansen et al. | Jun 2012 | B2 |
| 8206367 | Warren et al. | Jun 2012 | B2 |
| D664647 | Becker | Jul 2012 | S |
| D664648 | Becker | Jul 2012 | S |
| D664649 | Becker | Jul 2012 | S |
| 8209941 | Osborne et al. | Jul 2012 | B2 |
| 8216207 | Moy et al. | Jul 2012 | B2 |
| 8220503 | Tribble et al. | Jul 2012 | B2 |
| 8220504 | Hartman et al. | Jul 2012 | B2 |
| 8221382 | Moy et al. | Jul 2012 | B2 |
| 8225824 | Eliuk et al. | Jul 2012 | B2 |
| 8225826 | Horppu et al. | Jul 2012 | B2 |
| 8231567 | Tennican et al. | Jul 2012 | B2 |
| 8231749 | Dent et al. | Jul 2012 | B2 |
| 8241265 | Moy et al. | Aug 2012 | B2 |
| 8267129 | Doherty et al. | Sep 2012 | B2 |
| 8267912 | Ferris | Sep 2012 | B2 |
| 8287513 | Ellstrom et al. | Oct 2012 | B2 |
| 8328082 | Bochenko et al. | Dec 2012 | B1 |
| 8336587 | Rosenquist et al. | Dec 2012 | B2 |
| 8353318 | Ranalletta et al. | Jan 2013 | B2 |
| 8356644 | Chong et al. | Jan 2013 | B2 |
| 8356645 | Chong et al. | Jan 2013 | B2 |
| 8357137 | Yandell | Jan 2013 | B2 |
| 8374887 | Alexander | Feb 2013 | B1 |
| 8380536 | Howard et al. | Feb 2013 | B2 |
| 8381776 | Horppu | Feb 2013 | B2 |
| 8382696 | Beiriger et al. | Feb 2013 | B2 |
| 8386070 | Eliuk et al. | Feb 2013 | B2 |
| 8403905 | Yow | Mar 2013 | B2 |
| 8409165 | Niedospial, Jr. et al. | Apr 2013 | B2 |
| 8414556 | Garfield et al. | Apr 2013 | B2 |
| 8425487 | Beiriger et al. | Apr 2013 | B2 |
| 8430859 | McConnell | Apr 2013 | B2 |
| 8449521 | Thorne, Jr. et al. | May 2013 | B2 |
| 8506548 | Okiyama | Aug 2013 | B2 |
| 8522832 | Lopez | Sep 2013 | B2 |
| 8543416 | Palmroos et al. | Sep 2013 | B2 |
| 8551037 | Suchecki et al. | Oct 2013 | B2 |
| 8562583 | Akerlund et al. | Oct 2013 | B2 |
| 8567235 | Bojan et al. | Oct 2013 | B2 |
| 8571708 | Rob et al. | Oct 2013 | B2 |
| 8562584 | Beiriger et al. | Nov 2013 | B2 |
| 8602067 | Kuhni et al. | Dec 2013 | B2 |
| 8608723 | Lev et al. | Dec 2013 | B2 |
| 8622985 | Ellstrom | Jan 2014 | B2 |
| 8636720 | Truitt et al. | Jan 2014 | B2 |
| 8639525 | Levine et al. | Jan 2014 | B2 |
| 8660860 | Wehba et al. | Feb 2014 | B2 |
| 8679075 | Lurvey et al. | Mar 2014 | B2 |
| 8684994 | Lev et al. | Apr 2014 | B2 |
| 8700421 | Feng et al. | Apr 2014 | B2 |
| 8701696 | Guala | Apr 2014 | B2 |
| 8702675 | Imai | Apr 2014 | B2 |
| 8720496 | Huwiler et al. | May 2014 | B2 |
| 8721612 | Domkowski et al. | May 2014 | B2 |
| 8721614 | Takemoto et al. | May 2014 | B2 |
| 8721627 | Alpert | May 2014 | B2 |
| 8753325 | Lev et al. | Jun 2014 | B2 |
| 8763798 | Paul | Jul 2014 | B2 |
| 8795231 | Chong | Aug 2014 | B2 |
| 8801689 | Moy et al. | Aug 2014 | B2 |
| 8821436 | Mosler et al. | Sep 2014 | B2 |
| 8834444 | Domkowski | Sep 2014 | B2 |
| 8852147 | Callan et al. | Oct 2014 | B2 |
| 8863788 | Ranalletta et al. | Oct 2014 | B2 |
| 8864725 | Ranalletta et al. | Oct 2014 | B2 |
| 8864737 | Hasegawa et al. | Oct 2014 | B2 |
| 8870832 | Raday et al. | Oct 2014 | B2 |
| 8882739 | Domkowski et al. | Nov 2014 | B2 |
| 8894627 | Garfield et al. | Nov 2014 | B2 |
| 8911421 | Domkowski et al. | Dec 2014 | B2 |
| D721803 | Dubach | Jan 2015 | S |
| 8926554 | Okuda et al. | Jan 2015 | B2 |
| 8958112 | Matsui et al. | Feb 2015 | B2 |
| D724198 | Oostman et al. | Mar 2015 | S |
| 8973622 | Lopez et al. | Mar 2015 | B2 |
| 8979792 | Lev et al. | Mar 2015 | B2 |
| 9033006 | Perazzo et al. | May 2015 | B2 |
| 9043019 | Eliuk et al. | May 2015 | B2 |
| 9056164 | Tate et al. | Jun 2015 | B2 |
| 9057363 | Capone | Jun 2015 | B2 |
| 9057370 | Mundt et al. | Jun 2015 | B2 |
| 9060923 | Hossainy | Jun 2015 | B2 |
| 9061130 | Truitt et al. | Jun 2015 | B2 |
| 9076115 | Utech et al. | Jul 2015 | B2 |
| 9079686 | Domkowski et al. | Jul 2015 | B2 |
| 9089474 | Cederschiöld | Jul 2015 | B2 |
| 9089647 | Haenggi et al. | Jul 2015 | B2 |
| 9101717 | Mansour et al. | Aug 2015 | B2 |
| 9114242 | Fangrow, Jr. et al. | Aug 2015 | B2 |
| 9123077 | Silkaitis et al. | Sep 2015 | B2 |
| 9132062 | Fangrow | Sep 2015 | B2 |
| 9132063 | Lev et al. | Sep 2015 | B2 |
| 9139316 | Husnu et al. | Sep 2015 | B2 |
| 9144646 | Barron, III et al. | Sep 2015 | B2 |
| 9149576 | Bullington et al. | Oct 2015 | B2 |
| 9198832 | Moy et al. | Dec 2015 | B2 |
| 9211231 | Mansour et al. | Dec 2015 | B2 |
| 9212762 | Duncan | Dec 2015 | B2 |
| 9220661 | Garfield et al. | Dec 2015 | B2 |
| 9227048 | Frattini | Jan 2016 | B2 |
| 9241875 | Davis et al. | Jan 2016 | B2 |
| 9242039 | Valk et al. | Jan 2016 | B2 |
| 9270890 | Okuma et al. | Feb 2016 | B2 |
| 9345640 | Mosler et al. | May 2016 | B2 |
| 9345641 | Kraus et al. | May 2016 | B2 |
| 9345643 | Okiyama | May 2016 | B2 |
| 9381135 | Reynolds et al. | Jul 2016 | B2 |
| 9381137 | Garfield et al. | Jul 2016 | B2 |
| 9381296 | Arrizza et al. | Jul 2016 | B2 |
| 9382021 | Tribble et al. | Jul 2016 | B2 |
| 9393362 | Cozmi et al. | Jul 2016 | B2 |
| 9402786 | Petrone | Aug 2016 | B2 |
| 9408966 | Kamen | Aug 2016 | B2 |
| 9466088 | Perazzo et al. | Oct 2016 | B2 |
| 9474690 | Ranalletta et al. | Oct 2016 | B2 |
| 9475019 | Kaucky et al. | Oct 2016 | B2 |
| 9481477 | Kjar | Nov 2016 | B2 |
| D774192 | Fuchs | Dec 2016 | S |
| D775325 | Larson et al. | Dec 2016 | S |
| 9511989 | Lopez et al. | Dec 2016 | B2 |
| 9561893 | Root et al. | Feb 2017 | B2 |
| 9572923 | Howard et al. | Feb 2017 | B2 |
| 9579255 | Eliuk et al. | Feb 2017 | B2 |
| 9615997 | Fangrow | Apr 2017 | B2 |
| 9629955 | Bresina et al. | Apr 2017 | B2 |
| 9744102 | Kubo | Aug 2017 | B2 |
| 9770388 | Noike et al. | Sep 2017 | B2 |
| 9775778 | Qiu et al. | Oct 2017 | B2 |
| 9801787 | Py | Oct 2017 | B2 |
| 9802171 | Konrad, Jr. et al. | Oct 2017 | B2 |
| 9802172 | Konrad, Jr. et al. | Oct 2017 | B2 |
| D803396 | Oberkircher et al. | Nov 2017 | S |
| 9827163 | Lopez | Nov 2017 | B2 |
| 9827680 | Davey et al. | Nov 2017 | B2 |
| D804651 | Loonan | Dec 2017 | S |
| 9849236 | Hachey | Dec 2017 | B2 |
| 9883987 | Lopez | Feb 2018 | B2 |
| 9930297 | Alexander et al. | Mar 2018 | B2 |
| 9931276 | Lopez et al. | Apr 2018 | B2 |
| 10106278 | Chang | Oct 2018 | B2 |
| 10143985 | Brown et al. | Dec 2018 | B2 |
| D837983 | Fangrow | Jan 2019 | S |
| 10181186 | Kriheli et al. | Jan 2019 | B2 |
| 10188849 | Fangrow | Jan 2019 | B2 |
| 10189616 | Kraft | Jan 2019 | B2 |
| D846146 | Amos et al. | Apr 2019 | S |
| 10259608 | Fianchini et al. | Apr 2019 | B2 |
| D851745 | Shauver et al. | Jun 2019 | S |
| 10307338 | Hellenbrand | Jun 2019 | B2 |
| 10314764 | Lopez et al. | Jun 2019 | B2 |
| 10314765 | Lopez et al. | Jun 2019 | B2 |
| 10315174 | Konrad, Jr. et al. | Jun 2019 | B2 |
| 10327987 | Bochenko et al. | Jun 2019 | B1 |
| 10327988 | Tribble et al. | Jun 2019 | B2 |
| 10336477 | Perazzo et al. | Jul 2019 | B2 |
| 10417758 | Alexander | Sep 2019 | B1 |
| 10420927 | Fangrow | Sep 2019 | B2 |
| 10494126 | Joplin | Dec 2019 | B2 |
| 10503873 | Prince et al. | Dec 2019 | B2 |
| 10512885 | Janders et al. | Dec 2019 | B2 |
| D874644 | Shauver et al. | Feb 2020 | S |
| 10554937 | Alexander et al. | Feb 2020 | B2 |
| 10556062 | Simpson et al. | Feb 2020 | B2 |
| 10576211 | Hang et al. | Mar 2020 | B2 |
| D905228 | Shauver | Dec 2020 | S |
| 11007119 | Lopez et al. | May 2021 | B2 |
| 20020017328 | Loo | Feb 2002 | A1 |
| 20020085952 | Ellingboe et al. | Jul 2002 | A1 |
| 20020095121 | Norton et al. | Jul 2002 | A1 |
| 20020179544 | Johnson et al. | Dec 2002 | A1 |
| 20020189712 | Safabash | Dec 2002 | A1 |
| 20030023226 | Lopez | Jan 2003 | A1 |
| 20030153895 | Leinsing | Aug 2003 | A1 |
| 20030236500 | Scheu | Dec 2003 | A1 |
| 20040031756 | Suzuki et al. | Feb 2004 | A1 |
| 20040035743 | Tighe et al. | Feb 2004 | A1 |
| 20040073161 | Tachibana | Apr 2004 | A1 |
| 20040087888 | Digianfilippo et al. | May 2004 | A1 |
| 20040116891 | Curutcharry | Jun 2004 | A1 |
| 20040118477 | Desmond | Jun 2004 | A1 |
| 20040225274 | Jansen et al. | Nov 2004 | A1 |
| 20040249341 | Newbrough et al. | Dec 2004 | A1 |
| 20050033260 | Kubo et al. | Feb 2005 | A1 |
| 20050059952 | Giuliano et al. | Mar 2005 | A1 |
| 20050096627 | Howard | May 2005 | A1 |
| 20050131357 | Denton et al. | Jun 2005 | A1 |
| 20050230575 | Zelenski et al. | Oct 2005 | A1 |
| 20050252572 | Khan et al. | Nov 2005 | A1 |
| 20050252574 | Khan et al. | Nov 2005 | A1 |
| 20050278194 | Holland et al. | Dec 2005 | A1 |
| 20060048844 | Merrill | Mar 2006 | A1 |
| 20060064053 | Bollish et al. | Mar 2006 | A1 |
| 20060089854 | Holland et al. | Apr 2006 | A1 |
| 20060089855 | Holland et al. | Apr 2006 | A1 |
| 20060100907 | Holland et al. | May 2006 | A1 |
| 20060169348 | Yigal | Aug 2006 | A1 |
| 20060259195 | Eliuk et al. | Nov 2006 | A1 |
| 20070007478 | Leinsing et al. | Jan 2007 | A1 |
| 20070017583 | Fangrow | Jan 2007 | A1 |
| 20070088252 | Pestotnik et al. | Apr 2007 | A1 |
| 20070088313 | Zinger et al. | Apr 2007 | A1 |
| 20070106244 | Mosler et al. | May 2007 | A1 |
| 20070151984 | Baker et al. | Jul 2007 | A1 |
| 20070169836 | Djurle et al. | Jul 2007 | A1 |
| 20070214003 | Holland et al. | Sep 2007 | A1 |
| 20070244447 | Capitaine et al. | Oct 2007 | A1 |
| 20070287953 | Ziv et al. | Dec 2007 | A1 |
| 20080059228 | Bossi et al. | Mar 2008 | A1 |
| 20080065006 | Roger et al. | Mar 2008 | A1 |
| 20080077116 | Dailey et al. | Mar 2008 | A1 |
| 20080086094 | Peters | Apr 2008 | A1 |
| 20080114328 | Doherty | May 2008 | A1 |
| 20080125897 | DiGianfilippo et al. | May 2008 | A1 |
| 20080169043 | Osborne et al. | Jul 2008 | A1 |
| 20080169044 | Osborne et al. | Jul 2008 | A1 |
| 20080177222 | De Marco et al. | Jul 2008 | A1 |
| 20080195416 | Tribble et al. | Aug 2008 | A1 |
| 20080199353 | Mlodzinski et al. | Aug 2008 | A1 |
| 20080269680 | Ibranyan et al. | Oct 2008 | A1 |
| 20080287920 | Fangrow et al. | Nov 2008 | A1 |
| 20090012449 | Lee et al. | Jan 2009 | A1 |
| 20090050216 | Trocki et al. | Feb 2009 | A1 |
| 20090067973 | Eliuk et al. | Mar 2009 | A1 |
| 20090069743 | Krishnamoorthy et al. | Mar 2009 | A1 |
| 20090082649 | Muller et al. | Mar 2009 | A1 |
| 20090088687 | Yardimci et al. | Apr 2009 | A1 |
| 20090099547 | Radmer | Apr 2009 | A1 |
| 20090101576 | Rohde et al. | Apr 2009 | A1 |
| 20090126825 | Eliuk et al. | May 2009 | A1 |
| 20090135196 | Holland et al. | May 2009 | A1 |
| 20090145509 | Baker et al. | Jun 2009 | A1 |
| 20090149743 | Barron | Jun 2009 | A1 |
| 20090154764 | Khan et al. | Jun 2009 | A1 |
| 20090163860 | Patrick et al. | Jun 2009 | A1 |
| 20090177149 | Childers et al. | Jul 2009 | A1 |
| 20090198215 | Chong et al. | Aug 2009 | A1 |
| 20090223592 | Procyshyn et al. | Sep 2009 | A1 |
| 20090223990 | Bailey et al. | Sep 2009 | A1 |
| 20090254031 | Lee | Oct 2009 | A1 |
| 20090270832 | Vancaillie et al. | Oct 2009 | A1 |
| 20090306621 | Thome, Jr. | Dec 2009 | A1 |
| 20100049157 | Fangrow | Feb 2010 | A1 |
| 20100121246 | Peters et al. | May 2010 | A1 |
| 20100130933 | Holland et al. | May 2010 | A1 |
| 20100245056 | Braun et al. | Sep 2010 | A1 |
| 20100276034 | Gonnelli et al. | Nov 2010 | A1 |
| 20100280430 | Caleffi et al. | Nov 2010 | A1 |
| 20100286606 | Ding | Nov 2010 | A1 |
| 20110004143 | Beiriger et al. | Jan 2011 | A1 |
| 20110062703 | Lopez et al. | Mar 2011 | A1 |
| 20110067781 | Osborne | Mar 2011 | A1 |
| 20110087164 | Mosler | Apr 2011 | A1 |
| 20110152757 | Beck et al. | Jun 2011 | A1 |
| 20110175347 | Okiyama | Jul 2011 | A1 |
| 20110178493 | Okiyama | Jul 2011 | A1 |
| 20110196304 | Kramer et al. | Aug 2011 | A1 |
| 20110204144 | Waugh et al. | Aug 2011 | A1 |
| 20110229517 | Strahlendorf et al. | Sep 2011 | A1 |
| 20110276031 | Hoang et al. | Nov 2011 | A1 |
| 20110305545 | Davis et al. | Dec 2011 | A1 |
| 20120157914 | Stroup | Jan 2012 | A1 |
| 20120067429 | Mosler et al. | Mar 2012 | A1 |
| 20120109077 | Ryan | May 2012 | A1 |
| 20120123298 | Mendels | May 2012 | A1 |
| 20120302986 | Brem et al. | Nov 2012 | A1 |
| 20130006214 | Garfield et al. | Jan 2013 | A1 |
| 20130018356 | Prince et al. | Jan 2013 | A1 |
| 20130053815 | Mucientes et al. | Feb 2013 | A1 |
| 20130085439 | Sansoucy et al. | Apr 2013 | A1 |
| 20130102772 | Eshima et al. | Apr 2013 | A1 |
| 20130180618 | Py | Jul 2013 | A1 |
| 20130211332 | Beiriger et al. | Aug 2013 | A1 |
| 20130218121 | Waller et al. | Aug 2013 | A1 |
| 20130220484 | De Marco | Aug 2013 | A1 |
| 20130292004 | Ducret et al. | Nov 2013 | A1 |
| 20140020790 | Yuyama et al. | Jan 2014 | A1 |
| 20140039392 | Geipel et al. | Feb 2014 | A1 |
| 20140124087 | Anderson et al. | May 2014 | A1 |
| 20140135732 | Spronken et al. | May 2014 | A1 |
| 20140136229 | Levine et al. | May 2014 | A1 |
| 20140150925 | Sjogren et al. | Jun 2014 | A1 |
| 20140261727 | Mansour et al. | Sep 2014 | A1 |
| 20140261860 | Heath | Sep 2014 | A1 |
| 20140261877 | Ivosevic et al. | Sep 2014 | A1 |
| 20140263614 | Keefe et al. | Sep 2014 | A1 |
| 20140276386 | Mansour et al. | Sep 2014 | A1 |
| 20140276649 | Ivosevic et al. | Sep 2014 | A1 |
| 20140299221 | Lopez | Oct 2014 | A1 |
| 20140323970 | Duncan | Oct 2014 | A1 |
| 20140350949 | Utech et al. | Nov 2014 | A1 |
| 20150000784 | Jamaledine | Jan 2015 | A1 |
| 20150008664 | Tachizaki | Jan 2015 | A1 |
| 20150025453 | Ledford et al. | Jan 2015 | A1 |
| 20150040987 | Reichert et al. | Feb 2015 | A1 |
| 20150040988 | Reichert et al. | Feb 2015 | A1 |
| 20150041531 | Vavala et al. | Feb 2015 | A1 |
| 20150045772 | Reichert et al. | Feb 2015 | A1 |
| 20150051751 | Kirschbaum et al. | Feb 2015 | A1 |
| 20150082746 | Ivosevic et al. | Mar 2015 | A1 |
| 20150101707 | Ranalletta et al. | Apr 2015 | A1 |
| 20150119820 | Kanamoto | Apr 2015 | A1 |
| 20150123398 | Sanders et al. | May 2015 | A1 |
| 20150126958 | Sanders et al. | May 2015 | A1 |
| 20150133879 | Kanamoto et al. | May 2015 | A1 |
| 20150151041 | Yodfat et al. | Jun 2015 | A1 |
| 20150157536 | Qiu et al. | Jun 2015 | A1 |
| 20150161354 | Blomquist | Jun 2015 | A1 |
| 20150202382 | Juretich et al. | Jul 2015 | A1 |
| 20150202383 | Juretich et al. | Jul 2015 | A1 |
| 20150202384 | Juretich et al. | Jul 2015 | A1 |
| 20150202385 | Juretich et al. | Jul 2015 | A1 |
| 20150209230 | Lev et al. | Jul 2015 | A1 |
| 20150209233 | Fukuoka | Jul 2015 | A1 |
| 20150209495 | Biset et al. | Jul 2015 | A1 |
| 20150209510 | Burkholz et al. | Jul 2015 | A1 |
| 20150209572 | Garfield et al. | Jul 2015 | A1 |
| 20150250680 | Browka et al. | Sep 2015 | A1 |
| 20150250681 | Lev et al. | Sep 2015 | A1 |
| 20150257977 | Bochenko et al. | Sep 2015 | A1 |
| 20150265500 | Russo et al. | Sep 2015 | A1 |
| 20150297451 | Mariei et al. | Oct 2015 | A1 |
| 20150297453 | Kim et al. | Oct 2015 | A1 |
| 20150297454 | Sanders et al. | Oct 2015 | A1 |
| 20150297456 | Mariei et al. | Oct 2015 | A1 |
| 20150297459 | Sanders et al. | Oct 2015 | A1 |
| 20150297460 | Mansour et al. | Oct 2015 | A1 |
| 20150297839 | Sanders et al. | Oct 2015 | A1 |
| 20150297881 | Sanders et al. | Oct 2015 | A1 |
| 20150314066 | Shimizu | Nov 2015 | A1 |
| 20150320992 | Bonnet et al. | Nov 2015 | A1 |
| 20150346013 | Feng et al. | Dec 2015 | A1 |
| 20150359709 | Kriheli et al. | Dec 2015 | A1 |
| 20150366758 | Noguchi et al. | Dec 2015 | A1 |
| 20160000653 | Kramer | Jan 2016 | A1 |
| 20160001003 | Perazzo et al. | Jan 2016 | A1 |
| 20160038373 | Ohlin | Feb 2016 | A1 |
| 20160038374 | Merhold et al. | Feb 2016 | A1 |
| 20160051446 | Lev et al. | Feb 2016 | A1 |
| 20160058666 | Strahlendorf et al. | Mar 2016 | A1 |
| 20160058667 | Kriheli | Mar 2016 | A1 |
| 20160081878 | Marks et al. | Mar 2016 | A1 |
| 20160081879 | Garfield et al. | Mar 2016 | A1 |
| 20160101020 | Guala | Apr 2016 | A1 |
| 20160114922 | Bonhora et al. | Apr 2016 | A1 |
| 20160136051 | Lavi | May 2016 | A1 |
| 20160136412 | McKinnon et al. | May 2016 | A1 |
| 20160140315 | Diaz et al. | May 2016 | A1 |
| 20160158104 | Ali et al. | Jun 2016 | A1 |
| 20160158437 | Biasi et al. | Jun 2016 | A1 |
| 20160206511 | Garfield et al. | Jul 2016 | A1 |
| 20160213568 | Mansour et al. | Jul 2016 | A1 |
| 20160213861 | Whitaker et al. | Jul 2016 | A1 |
| 20160213862 | Whitaker et al. | Jul 2016 | A1 |
| 20160250102 | Garfield et al. | Sep 2016 | A1 |
| 20160256632 | Fangrow | Sep 2016 | A1 |
| 20160262981 | Carrez et al. | Sep 2016 | A1 |
| 20160310362 | Lane et al. | Oct 2016 | A1 |
| 20160331893 | Yeh et al. | Nov 2016 | A1 |
| 20160354281 | O'Neill et al. | Dec 2016 | A1 |
| 20170007501 | Schuldt-Lieb et al. | Jan 2017 | A1 |
| 20170020428 | Rogers et al. | Jan 2017 | A1 |
| 20170081168 | Seay et al. | Mar 2017 | A1 |
| 20170128666 | Davis | May 2017 | A1 |
| 20170129763 | Fangrow, Jr. | May 2017 | A1 |
| 20170146381 | Eckel et al. | May 2017 | A1 |
| 20170165435 | Green | Jun 2017 | A1 |
| 20170165436 | Haddad et al. | Jun 2017 | A1 |
| 20170255760 | Lee et al. | Sep 2017 | A1 |
| 20170274140 | Howard et al. | Sep 2017 | A1 |
| 20170312716 | Konrad, Jr. et al. | Nov 2017 | A1 |
| 20170354571 | David et al. | Dec 2017 | A1 |
| 20180043323 | Janders et al. | Feb 2018 | A1 |
| 20180055735 | Lopez | Mar 2018 | A1 |
| 20180055738 | Chen et al. | Mar 2018 | A1 |
| 20180065097 | Konrad, Jr. et al. | Mar 2018 | A1 |
| 20180133667 | Lee et al. | May 2018 | A1 |
| 20180161244 | Lopez | Jun 2018 | A1 |
| 20180168930 | Tunesi | Jun 2018 | A1 |
| 20180168935 | Chen et al. | Jun 2018 | A1 |
| 20180177940 | Hachey | Jun 2018 | A1 |
| 20180194505 | Amano et al. | Jul 2018 | A1 |
| 20180207063 | Lopez | Jul 2018 | A1 |
| 20180232497 | Hoffman et al. | Aug 2018 | A1 |
| 20180263850 | Schneider et al. | Sep 2018 | A1 |
| 20180272117 | Fangrow | Sep 2018 | A1 |
| 20180344572 | Zollinger et al. | Dec 2018 | A1 |
| 20180353381 | Pak et al. | Dec 2018 | A1 |
| 20180353382 | Zollinger et al. | Dec 2018 | A1 |
| 20180354662 | Feith et al. | Dec 2018 | A1 |
| 20180357476 | Klumph | Dec 2018 | A1 |
| 20180360689 | Zollinger et al. | Dec 2018 | A1 |
| 20190019576 | DeCiccio et al. | Jan 2019 | A1 |
| 20190021947 | Bomgaars et al. | Jan 2019 | A1 |
| 20190056419 | Procyshyn et al. | Feb 2019 | A1 |
| 20190091639 | Brown et al. | Mar 2019 | A1 |
| 20190105619 | Wilson et al. | Apr 2019 | A1 |
| 20190151569 | Fangrow | May 2019 | A1 |
| 20190152663 | Kraft | May 2019 | A1 |
| 20190163876 | Remme et al. | May 2019 | A1 |
| 20190170663 | Pirkle et al. | Jun 2019 | A1 |
| 20190216683 | Yaegashi | Jul 2019 | A1 |
| 20190244466 | Berg et al. | Aug 2019 | A1 |
| 20190247280 | Hellenbrand | Aug 2019 | A1 |
| 20190262790 | Konrad, Jr. et al. | Aug 2019 | A1 |
| 20190275243 | Deck et al. | Sep 2019 | A1 |
| 20190307643 | Tribble et al. | Oct 2019 | A1 |
| 20190388302 | Schobel et al. | Dec 2019 | A1 |
| 20200016037 | Oda et al. | Jan 2020 | A1 |
| 20200066389 | Prince et al. | Feb 2020 | A1 |
| 20200093699 | Oda et al. | Mar 2020 | A1 |
| 20200113784 | Lopez | Apr 2020 | A1 |
| 20200113785 | Lopez | Apr 2020 | A1 |
| 20200289370 | Lopez | Sep 2020 | A1 |
| 20200297581 | Lopez | Sep 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1707379 | Dec 2005 | CN |
| 101244297 | Aug 2008 | CN |
| 106860003 | Jun 2017 | CN |
| 107198658 | Sep 2017 | CN |
| 108210332 | Jun 2018 | CN |
| 202 16 791 | Feb 2003 | DE |
| 20 2004 014 868 | Nov 2004 | DE |
| 0 521 460 | Sep 1995 | EP |
| 0 974 330 | Jan 2000 | EP |
| 1 533 597 | May 2005 | EP |
| 1 563 819 | Aug 2005 | EP |
| 1 997 471 | Dec 2008 | EP |
| 3 375 427 | Sep 2018 | EP |
| S55-156750 | Nov 1980 | JP |
| 55-173339 | Dec 1980 | JP |
| 56-95247 | Aug 1981 | JP |
| 62-189072 | Aug 1987 | JP |
| 06-343706 | Dec 1994 | JP |
| 10-118158 | May 1998 | JP |
| 2001-190689 | Jul 2001 | JP |
| 2002-238979 | Aug 2002 | JP |
| 2002-355318 | Dec 2002 | JP |
| 2003-144546 | May 2003 | JP |
| 2003-199823 | Jul 2003 | JP |
| 2003-225305 | Aug 2003 | JP |
| 2004-49497 | Feb 2004 | JP |
| 2007-14618 | Jan 2007 | JP |
| 2007-215775 | Aug 2007 | JP |
| 2011-0019800 | Mar 2011 | KR |
| 10-1095961 | Dec 2011 | KR |
| 10-1574194 | Dec 2015 | KR |
| WO 199714493 | Apr 1997 | WO |
| WO 199823353 | Jun 1998 | WO |
| WO 199919012 | Apr 1999 | WO |
| WO 199963547 | Dec 1999 | WO |
| WO 200041751 | Jul 2000 | WO |
| WO 200103757 | Jan 2001 | WO |
| WO 2001039874 | Jun 2001 | WO |
| WO 2005041846 | May 2005 | WO |
| WO 2005110007 | Nov 2005 | WO |
| WO 2005123162 | Dec 2005 | WO |
| WO 2007033013 | Mar 2007 | WO |
| WO 2007061424 | May 2007 | WO |
| WO 2007062315 | May 2007 | WO |
| WO 2007079305 | Jul 2007 | WO |
| WO 2007148708 | Dec 2007 | WO |
| WO 2008051998 | May 2008 | WO |
| WO 2008128074 | Oct 2008 | WO |
| WO 2009060419 | May 2009 | WO |
| WO 2009130147 | Oct 2009 | WO |
| WO 2011002853 | Jan 2011 | WO |
| WO 2011012313 | Feb 2011 | WO |
| WO 2011058545 | May 2011 | WO |
| WO 2011058548 | May 2011 | WO |
| WO 2011091542 | Aug 2011 | WO |
| WO 2011091543 | Aug 2011 | WO |
| WO 2011104711 | Sep 2011 | WO |
| WO 2011104712 | Sep 2011 | WO |
| WO 2011150037 | Dec 2011 | WO |
| WO 2012119225 | Sep 2012 | WO |
| WO 2014122643 | Aug 2014 | WO |
| WO 2014126473 | Aug 2014 | WO |
| WO 2014177347 | Nov 2014 | WO |
| WO 2014181320 | Nov 2014 | WO |
| WO 2015029020 | Mar 2015 | WO |
| WO 2018009996 | Jan 2018 | WO |
| WO 2019018195 | Jan 2019 | WO |
| Entry |
|---|
| U.S. Appl. No. 15/933,954, filed Mar. 23, 2018, Lopez et al. |
| U.S. Appl. No. 29/571,547, filed Jul. 19, 2016, Shauver et al. |
| U.S. Appl. No. 29/586,575, filed Dec. 5, 2016, Fangrow. |
| Abbott Laboratories, “Abbott MedNet Software,” Installation and User Guide in 156 pages, Copyright 2006. (Part 1—pp. 1-78). |
| Abbott Laboratories, “Abbott MedNet Software,” Installation and User Guide in 156 pages, Copyright 2006. (Part 2—pp. 79-156). |
| Autoyec 50, from KRZ, Dec. 6, 2007. |
| B. Braun Medical Inc. Two-Bag Irrigation Set, Two Non-vented Spikes, dated Jul. 2012, in 1 page. |
| BioExpert International Inc., Company overview, credentials for Rabih Jamaleddine, Nabil Kereknawi, and Danica Robillard Corso, copyright 2010 BioExpert International Inc. in 3 pages [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://bioexpert.ca/about.html. |
| Cato (Computer Aided Therapy for Oncology)—Reference Manual—Vienna, May 2005, 255 pgs. |
| Clearlink Needleless IV Access System, dated Aug. 2007, in 2 pages. |
| CytoCare, by Health Robotics, Brochure, Date Unknown, downloaded on May 25, 2012 from http://www.health-robotics.com/smartedit/downloads/en/cytocare7.pdf, 6 pages. |
| Exacta-Mix 2400, from Baxa, which appears to have a date of 2007, 2 pages. |
| Flickinger, Bruce, “Misperceptions Cloud the Issue of Sterile Drug Compounding,” Jun. 2007. |
| Fox Brent I., “Pharmacy Automation and Technology: Automated Intravenous Preparation: Robots for the Pharmacy,” Hospital Pharmacy, vol. 44, Mar. 2009, pp. 255-257. |
| Grifols International, S.A., “PHOCUS Rx, Remote IV Compounding Validation” product brochure and “Product Description Sheet” in 13 pages [Publication Date unknown but may be May 29, 2013]. |
| Healthmark, “Hospital Medication Preparation, Packaging and Dispensing” in 1 page [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/2-en-Hospital-Medication-Preparation-Packaging-and-Dispensing.html. |
| Healthmark, “Hospital Medication Preparation, Packaging and Dispensing,” Chemo Drug Preparation/Administration in 2 pages [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/2-36-88-Chemo-Drug-Preparation-Administration_en.html. |
| Healthmark, “Hospital Medication Preparation, Packaging and Dispensing,” Chemosphere, Sterile Chemo Compounding (Isolator) in 1 page [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/2-36-10-ChemoSphere_en.html?ProduitID=244. |
| Healthmark, “Hospital Medication Preparation, Packaging and Dispensing,” Oncology Preparation and Administration in 1 page [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/2-36-10-COMPANY-PROFILEHospital-en.html. |
| Healthmark, “Hospital Medication Preparation, Packaging and Dispensing,”Phocus RX (Camera Verification System), Remote Rx Checking of admixtures in 2 pages [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/2-36-10-PHOCUS-Rx-Camera-Verification-System-_en.html?ProduitID=229. |
| Healthmark, “New Product Items” in 1 page [retrieved on Jan. 6, 2015; Publication Date Unknown]; accessed on the world wide web at http://www.healthmark.ca/home.html. |
| Healthmark, “Introducing the Precifill Dispensing Pump” product brochure in 2 pages [Publication Date Unknown]. |
| Hospira, “Hospira MedNet Software Suite,” IT Implementation Training Guide in 143 pages, Copyright 2006. |
| Hospira, “LifeCare PCA with Hospira MedNet Software,” LifeCare PCA Technical Service Manual in 208 pages, Published 2007. (Part 1—pp. 1-104). |
| Hospira, “LifeCare PCA with Hospira MedNet Software,” LifeCare PCA Technical Service Manual in 208 pages, Published 2007. (Part 2—pp. 105-208). |
| Integra Brochure, from Eurospital, Brochure acquired in Mar. 2012. |
| International Invitation to Pay Additional Fees (with cited art), re PCT Application No. PCT/US 16/64467, dated Jan. 25, 2017. |
| International Preliminary Report on Patentability, re PCT Application No. PCT/US 16/64467, dated Jun. 5, 2018. |
| International Search Report and Written Opinion, re PCT Application No. PCT/US 16/64467, dated Apr. 5, 2017. |
| ISO/Tech Design, QC, Canada, “Chemosphere,” product brochure, in 2 pages [Publication Date Unknown]. |
| Machine transcription generated by YouTube taken from a video titled, “RIVA Robotic IV Automation,” available at https://www.youtube.com/watch?v-GbLIBNMPv9Y, as allegedly published on Sep. 11, 2006. |
| Neo Care Medical Products: Product Catalog, dated Jun. 2008, in 38 pages. |
| Pinnacle TPN Management System, from B Braun, downloaded May 5, 2009 from http://www.bbraunusa.com/index. cfm?uuid=7386ADF065B05CD0D22AF700339AA4092, 1 page. |
| “Precifill,” Trademark search (TESS) in 1 page, [retrieved on Jan. 6, 2015; Application Filing Date of Sep. 30, 2011]; accessed on the world wide web at http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4807:gz67gx.3.1. |
| Product detail for “NAMIC® Closed Fluid Systems” from Navilyst Medical, downloaded on May 11, 2010 from http://www.navilystmedical.com/Products/index.cfm/19, 2 pages. |
| Product detail for “RapidFill™Automated Syringe Filler,” from Baxa, downloaded on Mar. 31, 2010 from http://www.baxa/com/PharmacyProducts/AutomatedFillingSystems/ProductDetail/?id=B1, 2 pages. |
| Product detail for “Summit Medical DirectFlow” micro infusion extension set from Summit Medical Technologies, downloaded on May 10, 2010 from http://summitmedtech.com/p6line.php, 1 page. |
| Richard Anders, “RIVA Robotic IV Automation,” available at https://www.youtube.com/watch?v=GbLIBNMPv9Y, as allegedly published Sep. 11, 2006. |
| Riva, downloaded in Apr. 2009 from http://www.rivasystem.com, 6 pages. |
| SmartSite Safety Disposables, with copyright notice dated 2004. |
| Smith, “Lifesaving Cancer Drugs May Put Workers′ Lives at Risk,” downloaded on Jul. 12, 2010 from http://www.msnbc.msn.com/id/38114586/ns/health-cancer, 7 pages. |
| Spiros—Closed Male Connector, published Jan. 22, 2008. |
| Technical Data sheet for Analog Amplifiers Type VA, models V8-C and V8-D, STM Sensors dated Dec. 2007, 4 pages. |
| Technical Data sheet for Through Beam Sensors Type G2, 1480 nm, STM Sensors dated Dec. 2009, 2 pages. |
| Technical Data sheet for Through Beam Sensors Type G2, 645 nm, STM Sensors dated Sep. 2008, 2 pages. |
| User Guide for medOC 1xx Basic, Neo Care Medical Products GmbH, Version Jun. 2008, 23 pages. |
| User Manual for medOC 3xx /6xx /8xx, Neo Care Medical Products GmbH, Version May 2008, 44 pages. |
| Abbott “Plum A+,” System Operating Manual (for use with List 11971-04) in 85 pages, May 2001. |
| Baxa Corp. v. McGaw Inc. 981 F. Supp. 1348 (1997), Memorandum Opinion and Order, 14 pages. |
| Burrows, et al., “Intravenous (IV) Fluidmaker IV. A Disposable Device for Preparation of Sterile Water for Injection In a Field Setting,” Fort Detrick, US Army Biomedical Research & Development Laboratory, Sep. 1991. https://apps.dtc.mil/dtic/tr/fulltest/u2/a247385.pdf. |
| Number | Date | Country | |
|---|---|---|---|
| 20200206492 A1 | Jul 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62263541 | Dec 2015 | US | |
| 62360900 | Jul 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15991385 | May 2018 | US |
| Child | 16182503 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16182503 | Nov 2018 | US |
| Child | 16564575 | US | |
| Parent | PCT/US2016/064467 | Dec 2016 | US |
| Child | 15991385 | US |
