Fluid transfer devices and methods of use

Abstract

Systems and methods for the transfer of medical fluid are provided. A medical fluid transfer system may comprise a pump configured to transfer fluid through a tube assembly having a first connector configured to couple to a source container and a second connector configured to couple to a target container. The medical fluid transfer system may also comprise a destination sensor configured to output information about the target container. The medical fluid transfer system may further comprise a control system configured to operate the pump based on an operational setting associated with fluid volume; receive measurement data representing a measurement of the target container by the destination sensor, and adjust the operational setting based on an observed volume of fluid transferred to the target container.

Description

INCORPORATION BY REFERENCE

U.S. Pat. No. 8,522,832 (the “'832 Patent”), titled “FLUID TRANSFER DEVICES AND METHODS OF USE,” filed on Jul. 28, 2010 as U.S. patent application Ser. No. 12/845,548, and granted on Sep. 3, 2013, is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Pat. No. 5,685,866 (the “'866 Patent”), titled “MEDICAL VALVE AND METHOD OF USE,” filed on Nov. 4, 1994 as U.S. patent application Ser. No. 08/334,846, and granted on Nov. 11, 1997, is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Pat. No. 7,998,134 (the “'134 Patent”), titled “MEDICAL CONNECTOR WITH CLOSEABLE MALE LUER,” filed on May 8, 2008 as U.S. patent application Ser. No. 12/117,568, and granted on Aug. 16, 2011, is incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Pat. No. 8,409,164 (the “'164 Patent”), titled “ANTI-REFLUX VIAL ADAPTORS,” filed on Aug. 19, 2009 as U.S. patent application Ser. No. 12/543,776, and granted on Apr. 2, 2013, is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Provisional Patent Application No. 61/557,793 (the “'793 application”), filed Nov. 9, 2011, and titled “MEDICAL CONNECTORS WITH FLUID-RESISTANT MATING INTERFACES,” is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

PCT Patent Application No. PCT/US2012/054289, filed Sep. 7, 2012, and titled “MEDICAL CONNECTORS WITH FLUID-RESISTANT MATING INTERFACES,” is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Pat. No. 8,758,306 (the “'306 Patent”), titled “MEDICAL CONNECTORS AND METHODS OF USE,” filed on May 12, 2011 as U.S. patent application Ser. No. 13/106,781, and granted on Jun. 24, 2014, is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

U.S. Pat. No. 9,883,987 (the “'987 Patent”), titled “FLUID TRANSFER DEVICES AND METHODS OF USE,” filed on Jun. 20, 2014 as U.S. patent application Ser. No. 14/310,942, and granted on Feb. 6, 2018, is hereby incorporated by reference in its entirety and made a part of this specification for all that it discloses.

BACKGROUND

Field of the Disclosure

Some embodiments of the invention relate generally to devices and methods for transferring fluid and specifically to devices and methods for transferring medical fluids.

Description of the Related Art

In some circumstances it can be desirable to transfer one or more fluids between containers. In the medical field, it is often desirable to dispense fluids in precise amounts and to store and to transport potentially dangerous fluids. Current fluid transfer devices and methods in the medical field suffer from various drawbacks, including high cost, low efficiency, intensive labor demands, and excessive fluid or vapor leakage. Some embodiments disclosed herein overcome one or more of these disadvantages.

SUMMARY OF SOME EMBODIMENTS

Some embodiments disclosed herein relate to systems and methods for transferring fluid from source containers to target containers.

In some embodiments a medical fluid transfer system is provided. The medical fluid transfer system may comprise a pump configured to transfer fluid through a tube assembly having a first connector configured to couple to a source container and a second connector configured to couple to a target container. The medical fluid transfer system may also comprise a destination sensor configured to output information about the target container. The medical fluid transfer system may further comprise a control system. The control system may be configured to: receive an instruction to transfer a desired volume of a medical fluid to the target container; operate the pump based on the instruction and an operational setting associated with fluid volume; receive measurement data representing a measurement of the target container by the destination sensor (e.g., the weight of the target container after transfer of medical fluid to the target container); determine a difference between a transferred volume of the medical fluid and the desired volume of the medical fluid based at least partly on the measurement data and a fluid property of the medical fluid (e.g., specific gravity of the medical fluid); adjust the operational setting based on the difference; and operate the pump based on the operational setting that has been adjusted.

In some embodiments, the control system comprises a user interface, and the measurement data is received by the control system via the user interface. In some embodiments, the control system comprises a first communication interface, the destination sensor comprises a second communication interface, the destination sensor transmits the measurement data via the second interface, and the measurement data is received by the control system via the first communication interface. In some embodiments, the control system determines the transferred volume of medical fluid based on the specific gravity of the medical fluid and the weight of the target container. In some embodiments, the pump is a peristaltic pump comprising a rotor with one or more lobes. In some embodiments, the operational setting indicates a quantity of rotations that the rotor is to be rotated for transfer of one or more volumetric units of the medical fluid. In some embodiments, a plane of rotation of the rotor is substantially orthogonal to a direction of gravity during operation of the peristaltic pump. In some embodiments, the control system is further configured to manage a batch transfer operation in which the control system operates the pump to transfer the desired volume of the medical fluid to each of a plurality of target containers. In some embodiments, the control system is further configured to delay a subsequent segment of the batch transfer operation for a predetermined time interval after completion of a prior segment of the batch transfer operation.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain embodiments of the invention will now be discussed in detail with reference to the following figures. These figures are provided for illustrative purposes only, and the embodiments are not limited to the subject matter illustrated in the figures.

FIG. 1A schematically shows an example embodiment of an automated system for transferring fluid.

FIG. 1B schematically shows another example embodiment of an automated system for transferring fluid.

FIG. 2 is a view of an example embodiment of an automated system for transferring fluid.

FIG. 3 is a front view of the system of FIG. 2.

FIG. 4 is a back view of the system of FIG. 2.

FIG. 5 is a perspective view of an example embodiment of a fluidics assembly that can be used to transfer fluid.

FIG. 6 is an exploded view of the fluidics assembly of FIG. 5.

FIGS. 7, 8, and 9 illustrate usage of an embodiment of a peristaltic pump.

FIG. 10 is a flow diagram of an example embodiment of a method for using an automated system for transferring fluid.

FIG. 11 is a view of another example embodiment of an automated system for transferring fluid.

FIG. 12 is a top view of the system of FIG. 11 during installation of a fluidics assembly.

FIG. 13 schematically shows components of the system of FIG. 11.

FIG. 14 is a view of user interfaces for managing the transfer of fluid using the system of FIG. 11.

FIG. 15 is a flow diagram of an example embodiment of a method for calibrating an automated system for transferring fluid.

FIG. 16 is a view of user interfaces for managing the calibration of the system of FIG. 11.

FIG. 17 is a flow diagram of an example embodiment of batch fluid transfer method with periodic verification.

FIG. 18 is a view of user interfaces for managing the batch transfer of fluid with period verification using the system of FIG. 11.

DETAILED DESCRIPTION OF SOME EXAMPLE EMBODIMENTS

The following detailed description is now directed to certain specific example embodiments of the disclosure. In this description, reference is made to the drawings wherein like parts are designated with like numerals throughout the description and the drawings.

In many circumstances fluid is transferred from a source container to a target container. In some instances, it can be desirable to transfer precise amounts of a fluid, such as a medication, into the target container. For example, in some embodiments a medication can be stored in a vial or other container, and a precise dosage amount of the medication can be extracted and transferred to a target device so that the dosage amount can be delivered to a patient. In some embodiments, fluid from multiple source containers can be combined, or compounded, into a single target container. For example, in some embodiments a mixture of medications can be created in the target container, or a concentrated medication can be combined with a diluent in the target container. To achieve the desired proportions of fluids, it can be desirable to precisely measure the amounts of fluids transferred into the target container. Also, precisely measuring the amount of fluid transferred from the source container to the target container can reduce the amount of fluid wasted (e.g., when more fluid than necessary is withdrawn from the source container). Reduction of waste is desirable because, for example, in some instances the fluid being transferred can be expensive.

Some embodiments disclosed herein provide fluid transfer devices for transferring precise amounts of fluid from one or more source containers into one or more target containers.

In some embodiments, it can be desirable to transfer fluids from a source container to a target container using a sealed system. In some embodiments, exposing the fluid to ambient air can allow contaminants to enter the fluid or cause an undesirable reaction with the fluid. Some medications (e.g., chemotherapy medications) can be harmful to an unintended recipient. Therefore, it can be desirable to prevent or reduce exposure of the fluid being transferred to the ambient air or area outside the fluid transfer system. In some embodiments, a fluid transfer system that prevents or reduces exposure of the fluid to the area outside the fluid transfer system can render other expensive equipment (e.g., a clean room) unnecessary, thereby reducing the cost associated with transferring the fluids.

Some embodiments disclosed herein provide a fluid transfer device for transferring fluid while preventing, reducing, or minimizing the amount of contact the fluid has with the ambient air or area outside the fluid transfer system.

FIG. 1A schematically shows an embodiment of an automated fluid transfer system 1200. The system 1200 comprises one or more fluid transfer stations 1218a-b, a destination sensor, such as an end volume sensor or a weight sensor 1222, and a controller 1204. Although in the embodiment shown, the components are all contained within the housing 1202, a variety of other configurations are possible. For example, the system 1200 can include one or more housings 1202 enclosing components of the various systems. In some embodiments, each component grouping can have a separate housing (as illustrated by the dashed lines within the housing 1202). In some embodiments the controller 1204 can be contained within the same housing as the first fluid transfer station 1218a. In some embodiments there is a single fluid transfer station 1218a. In some embodiments there can be a plurality (e.g., a first and a second) of fluid transfer stations 1218a-b. In some embodiments the destination sensor 1222 can be in a different housing than the fluid transfer stations 1218a-b and the controller 1204. In some embodiments, the controller 1204 can be external to the housing 1202, and can be, for example contained within a second housing, which may also contain the user interface 1208.

The system 1200 has a controller 1204 and a memory module 1206. The controller 1204 can be configured to control the operation and functions of the fluid transfer stations 1218a-b and the destination sensor 1222. The system 1200 can also include a user interface 1208, which can be, for example, external to the housing 1202. The user interface 1208 can also be integrated into the housing 1202 in some cases. The user interface 1208 can include, for example, a display, a keypad, and/or a touch screen display. The user interface 1208 can be configured to receive instructions from the user, for example, regarding the amounts of fluid to be transferred and the types of fluids to be transferred. The user interface can also be configured to provide information to the user, such as error messages, alerts, or instructions (e.g., to replace an empty vial). In some embodiments, the system 1200 can include a communication interface 1210 configured to receive information (e.g., instructions) from a remote source such as an external controller 1212, a terminal (such as a computer) 1214, or an automated management system (such as a hospital information system (HIS)) 1216, etc. In some embodiments, the communication interface can also send information (e.g., results or alerts) to the remote source. The communication interface can include one or more connection types and can be configured to allow connectivity to multiple remote sources at once. In some embodiments, the system 1200 does not include a communication interface 1210 and does not communicate with a remote source.

The destination sensor 1222 can include a communication interface 1221 that can communicate with the controller 1204. In some embodiments a weight sensor 1222 can communicate with the controller using wireless communication. In some embodiments a weight sensor 1222 can be physically connected to the controller 1204 using a standard communication interface (e.g., RS232, USB, etc.). The controller 1204 can receive information (e.g., measurements, current state of operation, etc.) and provide commands (e.g., zeroing the weight sensor) to the weight sensor 1220 through the communication interface 1221. In some embodiments the weight sensor 1222 can include a user interface 1223. The user interface can provide a visual indication of weight, and other information. In some embodiments the weight sensor 1222 can receive commands or instructions through the user interface 1223 from a user.

The destination sensor 1222 is used to determine the amount of fluid transferred from the source container 1220a-b to the target container 1224. The destination sensor 1222 outputs the weight of the fluid transferred to the target container to the controller 1204. Prior to transferring fluid, the scale can be programmatically zeroed in order to compensate for the weight of the target container 1224. For example, a base weight can be assigned as “zero” fluid weight (i.e., equivalent to the weight of the inherent scale weight and/or equivalent to the inherent scale weight plus a first fluid weight, and/or equivalent to the weight of the target container). The scale can then determine the relative weight of the fluid transferred to the target container 1224 beyond the base weight.

In some embodiments, the destination sensor 1222 is a scale that is capable of receiving weight information and electronically providing the information to the controller 1204. The scale can be located in a separate housing 1202. In some embodiments, the scale can have a substantially flat weighing surface for the target container. In some embodiments (not illustrated) the scale can be a hanging scale.

In some embodiments, the fluid transfer station can include a positive displacement pump, such as a peristaltic pump, 1240a-b, a motor 1242a-b and a fluidics assembly. The positive displacement pump 1240a-b can be used to pump fluid from a source container 1220a-b to a target container 1224. The fluid is transferred via a hose 1228a-b fitted inside a pump mounting interface 1244a-b. A rotor with a number of lobes rotates and compresses the hose 1228a-b progressively along an advancing portion of the hose. As the lobe passes a particular portion of hose, such portion of hose rebounds to substantially its original shape and internal volume. As the rotor turns, the part of hose 1228a-b under compression is pinched, thus, displacing fluid and forcing the fluid to move forward through the tube. The speed of the rotation of the rotor, the number of lobes, and the material properties of the hose influence the flow rate of the fluid through the system. The flow rate of the fluid transfer can be controlled by varying the speed of the pump 1240a-b. The motor 1242a-b operating the pump 1240a-b can run at variable speeds. The peristaltic pump 1240a-b can be configured to operate at a low pressure. The pressure generated by the pump 1240a-b can be sufficiently low, such that it is below a threshold at which the connector 1230a-b will not leak if the pump is operating and the connector 1230a-b is not connected to the target container.

The operations of the pump can be controlled by the controller 1204. In some embodiments, the housing 1202 incorporating the pump can have a touch screen that allows commands to be provided to the controller 1204. For example, a user can instruct the pump to transfer a specific amount of fluid to the target container. In some embodiments the commands can be received from an external source such as a network computer. The controller 1204 can operate the pump at variable speeds by controlling the speed of the motor. The controller 1204 can control that rate at which the rotor is spinning, which, in turn, controls the fluid flow rate. In some embodiments, the computer can use an algorithm to reduce the speed of the motor as the amount of fluid approaches the desired amount of fluid in the target container in order to increase accuracy.

Each fluid transfer station 1218a-b can have a fluidics assembly that includes a first connector 1226a-b, a hose 1228a-b, and a second connector 1230a-b. The hose 1228a-b can be formed from a compressible material (e.g., silicone rubber, and other elastomeric materials). The hose 1228a-b is configured to be inserted within the mounting interface 1244a-b of the peristaltic pump 1240a-b (as illustrated by the dashed line) in order to facilitate the transfer of fluid between the source container 1220a-b and the target container 1224. Some embodiments can be assembled from different types or portions of hose. In some embodiments, the hose 1228a-b can be formed from a single material. In some embodiments, the hose is formed with an elastomeric portion and other portions formed from polymeric materials. The first and second connectors 1226a-b, 1230a-b are fixedly coupled to the hose 1228a-b at opposite ends and are not configured to be removable from the hose. The first connector 1226a-b is configured to connect to the source container 1220a-b. In some embodiments, one or more pairs of male and female fluid connectors configured to be attached to each other to selectively permit the passage of fluid between the source container 1220a-b and the target container 1224. The connectors can be detached or disconnected, for example, so that the target container 1224 can be removed once the fluid has been transferred. In some embodiments, the connectors can be configured to automatically close when disconnected from a corresponding connector, thereby preventing fluid from escaping when the connectors are detached. Thus, the fluid transfer system 1200 can be used to transfer fluid while retaining substantially entirely, or entirely, all of the fluid within the system, permitting the fluid transfer to occur in a substantially entirely, or entirely, closed system. The fluid transfer system 1200 can thereby reduce or eliminate the risk of injury, waste, or damage caused by liquid or vapor leakage when connecting and disconnecting the components of the fluid transfer system 1200.

Each transfer station 1218a-b can include a fluid source container 1220a-b, which can be, for example, a medical vial or other suitable container such as a bag, a bottle, or a vat, etc. Although many embodiments disclosed herein discuss using a vial as the source container, it will be understood the other containers can be used even when not specifically mentioned. In some embodiments, each of the source containers 1220a-b can contain a unique fluid, providing a variety of fluids that the user can select for transfer. In other embodiments, two or more of the source containers 1220a-b can contain the same fluid. In some embodiments, the source containers 1220a-b include bar codes that identify the types of fluid contained therein. The bar codes can be scanned by a bar code scanner 1205 that is in communication with the controller 1204 and/or the memory 1206 (e.g., via the communication interface 1210) so that the identities of the fluids contained by source containers 1220a-b can be stored within the memory module 1206. In some embodiments, the fluid transfer stations 1218a-b are configured to transfer precise amounts of fluid from source containers 1220a-b to a target container 1224, which can be, for example an IV bag. It will be understood that in various embodiments described herein, a different type of target container or destination container can be used instead of an IV bag (e.g., a syringe, a bottle, a vial, an elastomeric pump, etc.) even when not specifically mentioned.

In some embodiments, the system 1200 can include source adapters 1236a-b configured to receive the source containers 1220a-b and removably connect to the connectors 1226a-b. Thus, when a source container 1220a-c runs out of fluid, the empty source container 1220a-b and its corresponding adapter 1236a-b can be removed and replaced without requiring disengagement of the associated connector 1226a-b from the housing 1202. In some embodiments, source adapters 1236a-b can be omitted, and the source containers 1220a-b can be directly received by the connectors 1226a-b.

In some embodiments using two or more fluid transfer stations 1218a-b, the fluid transfer system 1200 can be used to transfer and combine individual fluids from the source containers 1220a-b to the target container 1224. The system 1200 can be used for compounding mixtures of fluids. For example, the system 1200 can be used to combine multiple medications together or to combine feeding fluids (e.g., water, dextrose, lipids, vitamins, minerals). The system 1200 can also be used to dilute a medication or other fluid to a desired concentration level. In some embodiments, a first fluid transfer station 1218a can include a concentrated medication or other fluid, and a second fluid transfer station 1218b can include saline or other diluent. The system 1200 can be configured to receive input (e.g., from a user or from a hospital information system) indicating a desired amount and concentration of medication, and the system 1200 can be configured to transfer the precise amounts of the concentrated medication and the diluent required to fill the source container 1224a with the desired amount and concentration of the medication. The system can calculate the amount that needs to be transferred from each fluid transfer station 1218. The operation can then be done serially by transferring a first fluid from the first transfer station 1218a and then separately transferring a second fluid from the second transfer station 1218b. In some embodiments, a technician can manually connect the first fluid transfer station 1218a, via connector 1230a, to the target container 1224. After the first fluid is transferred the connector 1230a is disconnected and second fluid transfer station is connected, via connector 1230b, to the target container 1224 to transfer the second fluid. In some embodiments, the system 1200 can include an actuator that is capable of automatically switching the connection of the target container 1224 between the fluid transfer stations 1218a-b. In some embodiments, the actuator can switch between different fluid sources at the same fluid transfer station. For example, the first fluid source can be a concentrated medication or other fluid, and a second fluid source can be saline or some other diluent.

In some embodiments, the system 1200 can include compatibility modules 1232a-b for permitting connections with approved connectors 1226a-b, and for preventing connectors other than approved connectors 1226a-b from being placed in communication with the system 1200. The compatibility modules can be, for example, a specifically shaped mounting feature (e.g., on the housing of the fluid transfer station) that is configured to interface with a corresponding portion of the connector 1226a-b, 1230a-b. In some embodiments, the compatibility modules 1232a-b can be one or more sensors configured to detect the presence of an approved connector 1226a-b or to align with a specific portion of the connector 1226a-b during operation.

In some embodiments the system 1200 can include sensors 1234a-b for detecting the presence of the target container 1224. Sensors 1234a-b can be in communication with the controller 1204 so as to prevent the system 1200 from attempting to transfer fluid when no target container 1224 is connected. A variety of sensor types can be used for sensors 1234a-b. For example, sensors 1234a-b can be weight sensors, sensor pads, infrared sensors, or other forms of electronic sensors. In some embodiments, the sensor 1234a-b can align with a substantially transparent portion of the connector 1226a-b to detect whether a valve on the connector 1226a-b leading to target container 1224a-b is open. If open, the sensor 1234a-b can send a signal to the controller 1204 so that fluid transfer is permitted. The sensors 1234a-b can be configured to align properly with only approved connectors 1226a-b so that the sensors 1234a-b do not allow fluid transfer if an unapproved connector is used. Thus, the sensors 1234a-b can be used as the compatibility modules 1232a-b in some embodiments.

The fluid transfer system 1200 can have many different configurations. For example, in some embodiments there is only a single fluid transfer station. In some embodiments, certain features shown in FIG. 1A can be omitted for some or all of the transfer stations. For example, in some embodiments, a fluid transfer station can have the sensors omitted because, for example, a particular peristaltic pump does not generate sufficient pressure to cause fluid to leak out the connector when a target container is not connected and the pump is running.

FIG. 1B illustrates an example embodiment of a fluid transfer system 1250 in a configuration that can have features similar to, or the same as, the example fluid transfer system 1200 shown in FIG. 1A. For example, the system 1250 may include one or more fluid transfer stations that each comprise a peristaltic pump 1240 and a motor 1242 to transfer fluid from a source container to a target container, as described in greater detail herein. The system 1250 has a controller 1204 that can be configured to control the operation and functions of one or more fluid transfer stations. The fluid transfer system 1250 can include one or more circuit boards, such as boards 1252 and 1254. The circuit boards 1252, 1254 may support the controller 1204 any of a variety of electronic components, such as any or all of the electronic components of the fluid transfer system 1200 shown in FIG. 1A, by providing power, communications, and the like.

The system 1250 can also include a user interface 1208, such as a display, a keypad, and/or a touch screen display. The user interface 1208 can be configured to receive instructions from the user, for example, regarding the amounts of fluid to be transferred and the types of fluids to be transferred. The user interface can also be configured to provide information to the user, such as error messages, alerts, or instructions (e.g., to replace an empty vial).

In some embodiments, the system 1250 can include a communication interface 1210 configured to receive information (e.g., instructions) from a remote source such as an external controller, a terminal (such as a computer), or an automated management system (such as an HIS), etc. In some embodiments, the communication interface 1210 can also send information (e.g., results or alerts) to the remote source. The communication interface 1210 can include one or more connection types and can be configured to allow connectivity to multiple remote sources at once. In some embodiments, the system 1250 does not include a communication interface 1210 and does not communicate with a remote source.

The fluid transfer system 1250 may also include a weight sensor 1222 to assist in evaluating the transfer of fluid to and/or from a container, such as a source container or target container. The fluid transfer system 1250 may also include a bar code scanner 1205 for input of data from medication containers, patient charts, or the like.

The fluid transfer system 1250 may include one or more components in addition to, or instead of, those of the fluid transfer system 1200. In some embodiments, as shown, the fluid transfer system 1250 may include a battery 1260 to provide primary power, or to provide backup power in the event of disconnection from—or otherwise loss of power from—a primary power source. The fluid transfer system 1250 may include a speaker 1262 to provide audible feedback, alerts, etc. The fluid transfer system 1250 may include a printer 1264 to print hard copies of information, such as labels for medication, barcodes, and the like. The fluid transfer system 1250 may include a pedal 1266 to provide input, such as start or stop commands. These components may be coupled to or otherwise in electronic communication with one or more circuit boards 1252, 1254.

The fluid transfer system 1250 can have many different configurations. For example, in some embodiments there is only a single fluid transfer station. In some embodiments, certain features shown in FIG. 1B can be omitted for some or all of the transfer stations.

FIG. 2 is an example embodiment of a fluid transfer system 1300, which can have features similar to, or the same as, the systems 1200 and/or 1250 described above or any other fluid transfer system described herein. FIG. 3 is a front view of the fluid transfer system 1300 and FIG. 4 is a back view of the fluid transfer system 1300. In FIGS. 3 and 4, certain features (i.e., the fluidics assembly) are omitted from view. The system 1300 can include a fluid transfer station 1318 and a weight sensor 1322.

The fluid transfer station 1318 includes a housing 1302, a peristaltic pump 1350, a motor (not shown), a user interface 1308, and a pole assembly 1342. The user interface 1308 can be incorporated into the housing. The user interface 1308 can include a touchscreen, a keypad, a display, or other suitable interface devices for providing information to a user and/or for providing input from the user to a controller (not shown).

As can be seen in FIG. 4, the fluid transfer station 1318 and the weight sensor 1322 can have communication interfaces 1310a-b. The communications interfaces 1310a-b can include one or more connection points to receive cables from one or more remote sources such as a remote terminal (e.g., a computer) or an automated management system (e.g., a hospital information system (HIS)). The fluid transfer station 1318 and the weight sensor 1322 have a communication link established between them, such as by cable 1312. In some embodiments the weight sensor 1322 and the fluid transfer station can establish a communication using wireless signal.

In some embodiments, the communication interfaces 1310a-b can be configured to provide a communication link between the system 1300 (i.e., the fluid transfer station and the weight sensor) and a remote location. The communication link can be provided by a wireless signal (e.g., using an antenna) or by one or more cables or a combination thereof. The communication link can make use of a network such as a WAN, a LAN, or the internet. In some embodiments, the communication interfaces 1310a-b can be configured to receive input (e.g., fluid transfer commands) from the remote location and/or can provide information (e.g., results or alerts) from the system to the remote location.

The fluid transfer station 1318 can be configured to transfer fluid from a vial 1320 to an IV bag 1324 using a peristaltic pump 1350. The fluid is transferred from the vial 1320 through a connector 1326, and into a hose assembly 1330. The peristaltic pump 1350 moves the fluid from the hose assembly 1330 through the connector 1328 and into the IV bag 1324. The operation of the peristaltic pump 1350 is controlled by the controller based on commands or information received from a user. An example of the fluidics assembly is described in additional detail below with additional reference to FIGS. 5 and 6. Operation of an embodiment of a peristaltic pump is described in additional detail below with reference to FIGS. 7 through 9.

The fluid transfer station 1318 can include a pole assembly 1342, which can be configured to hold fluid containers such as vials and fluid bags. A pole 1344 can extend upward from the housing 1302, and in some embodiments, the pole 1344 can be height adjustable and a thumb screw 1346 can be tightened to hold the pole 1344 in place. The thumb screw 1346 can be loosened to enable adjustment of the height of the pole 1344, and in some embodiments, the pole 1344 can be lowered into a recess formed in the housing 1302 that is configured to receive the pole 1344. the pole 1344 can be entirely, substantially entirely, or mostly withdrawn into the housing 1302 when the pole 1344 is not in use (e.g., during storage or transportation or when not needed to support fluid containers). One or more support modules 1348 can be attached to the pole 1344 and can be configured to support fluid containers. The support modules 1348 can include thumb screws so that the positions of the support modules 1348 on the pole 1344 can be adjustable, and/or so that the support modules 1348 can be removable from the pole 1344. In the illustrated embodiment, the support module 1348 can have one or more curved arms for supporting a fluid container such as vial 1320.

In some embodiments, the weight sensor can include a housing 1316, a user interface, and a weighing surface 1321. The user interface 1308 can be incorporated in the housing 1316. The user interface 1308 can provide a visual indication of weight, and other information. In some embodiments the weight sensor 1322 can receive commands or instructions through the user interface 1308 from a user. In some embodiments the weight sensor 1322 does not include a user interface 1308. The weighing surface 1321 is configured to provide a surface for the IV bag. The weighing surface 1321 can be sized so that the IV bag 1324 or other target container can be properly balanced and positioned on the weight sensor.

The weight sensor 1322 can provide information to (e.g., measurements, current state of operation, etc.) and receive commands (e.g., zeroing the weight sensor) from the fluid transfer station 1318 through the communication interface 1310b. The weight sensor 1322 is used to determine the amount of fluid transferred from the vial 1320 to the IV bag 1324.

FIG. 5 is a perspective view of a fluidics assembly 1339 that can be used with the fluid transfer station 1318. FIG. 6 is a perspective exploded view of the fluidics assembly 1339 shown in FIG. 5. The fluid assembly 1339 can be used to transfer precise amounts of fluid from a vial 1320 to an IV bag 1324. The fluidics assembly 1339 includes a vial 1320, a vial adapter 1352 configured to provide fluid communication with the fluid (e.g., chemotherapy drug or other medication) contained within the vial 1320 to a connector 1326, a tubing assembly 1330, a connector 1328, and the IV bag assembly 1324. In some embodiments, the fluidics assembly 1339 can be configured to allow the vial 1320 and vial adapter 1352 to be replaced (e.g., when the vial runs out of fluid) without replacing the connector 1326 or the tubing assembly 1330. In some embodiments, the vial adapter 1352 can be configured to allow air to enter the vial 1320 via the vial adapter 1352, thereby substantially equalizing pressure in the vial 1320 as fluid is drawn out.

A tubing or hose assembly 1330 can extend between the connector 1326 and the connector 1328. The tubing assembly includes first tube portions 1334, a second tube portion 1332, and tubing connectors 1336. The second tube portion 1332 is configured to be inserted within the peristaltic pump 1350. In some embodiments the second portion 1332 can be configured to be more flexible than the first portion 1334. In some embodiments the second tube portion 1332 can be configured to have a lower durometer value than the first portions 1334. In some embodiments, the second portion 1332 can be more compressible than the first portion 1334 at a given force. In some embodiments, the tube 1332 can be formed from silicone rubber, or other appropriately formed elastomeric materials. The tube portions 1334 are positioned between the connectors 1326, 1328 and the tubing connectors 1336. In some embodiments the first tube portions 1334 can be smaller diameter tubing than is used for the second tube portion 1332. The tubing connectors 1336 are configured to create a fluid tight seal between the second tube portion 1332 and the first tube portions 1334. In some embodiments, there are no first tube portions 1334 or tubing connectors 1336 and the second tube portion 1332 is coupled to the connector 1326 and the connector 1328.

A connector 1326 (e.g., a Spiros® closeable male connector or a first Chemolock™ connector manufactured by ICU Medical, Inc., of San Clemente, California) can be located at the end of the tubing assembly 1330 and can be used to connect to a corresponding connector 1338 (e.g., a Clave® connector or a second Chemolock™ connector manufactured by ICU Medical, Inc., of San Clemente, California) that is attached to the fluid source container 1320. Additional details relating to Clave® connectors and some variations are disclosed in the '866 Patent. In various embodiments disclosed herein, other types of connectors can also be used, such as a MicroCLAVE® connector (manufactured by ICU Medical, Inc., of San Clemente, California), or any other connector disclosed or described herein, including those in the '306 Patent, including, for example, clear connectors. When the connectors 1326 and 1338 are engaged, a fluid connection exists between the fluid source container 1320 and the connector 1326. A tube 1330 can extend from an outlet of the connector 1326 to a connector 1328 (e.g., a Spiros® closable male connector) which can be positioned at the opposite end of the tubing assembly 1330. A corresponding connector 1338 (e.g., a Clave® connector) can engage the connector 1328. The IV bag 1324 may have a supplemental line of tubing 1325 that can be configured to engage the connector 1338 to provide a fluid connection between the connector 1328 and the IV bag 1324.

FIGS. 7 through 9 illustrate an embodiment of a peristaltic pump 1350 used by the fluid transfer station 1318. The peristaltic pump has a cover (not shown), a mounting interface 1354, a plurality of lobes 1356, a rotor 1358, and a motor (not shown). The peristaltic pump is a positive displacement pump used for pumping fluid from the vial 1320 to the IV bag 1324. The fluid is transferred via a compressible tube 1332 fitted inside the mounting interface 1354. The rotor 1358 has a plurality of lobes 1356 attached to the external circumference of the rotor compresses the flexible tube. In some embodiments the lobes can be rollers, shoes, wipers, or other members that facilitate the operation of the pump. As the rotor 1358 turns, the part of tube under compression is compressed, or occludes, thus forcing the fluid to be pumped to move through the tube. As the tube 1332 opens to its natural state after the passing of the lobes 1356 fluid flow is induced.

In some embodiments, the motor may rotate the rotor 1358 in a single direction (e.g., only clockwise, or only counterclockwise). Thus, the fluid may be pumped through the tube in a single direction, from a first end that is always coupled to a source container (e.g., a vial, medical fluid bag, or other suitable container) to a second end that is always coupled to a target container (e.g., an IV bag, an elastomeric pump, a syringe, or other suitable container).

In some embodiments, the motor may be configured to rotate the rotor 1358 in both a clockwise and counterclockwise direction. Thus, a first end of the tube may be coupled to a source container when the rotor 1358 is rotating in one direction (e.g., clockwise) and coupled to a target container when the rotor 1358 is rotating in a different direction (e.g., counterclockwise). For example, the motor may rotate the rotor 1358 in a first direction to move fluid from a source container to a target container. When the transfer is substantially complete, the motor may reverse directions and rotate the rotor 1358 in the second direction for a short time to depressurize or decompress the tube such that the pressure is sufficiently low and fluid is not urged outside of the tube upon disconnection of the target container. As another example, the source container may serve initially as a target container, such as when the source container includes lyophilized medication. The container with lyophilized medication may be coupled to a first end of the tube, and a container with a diluent (e.g., saline or sterile water) may be coupled to a second end of the tube. The motor may initially rotate the rotor 1358 in the first direction to move diluent into the container with the lyophilized medication. After the lyophilized medication is sufficiently hydrated, the motor may be stopped, and a new target container may be coupled to the end of the tube to which the diluent container was coupled (or the diluent container may remain coupled to the tube to now serve as a target container). The motor may then begin rotating the rotor in the second direction to move hydrated medication into the new target container.

In some embodiments of the pump 1350, the cover (if present) is opened, the tube 1332 is positioned within the mounting interface 1354 (see FIG. 8), and the cover is closed. FIG. 9 illustrates the tubing 1332 mounted within the pump 1350 during operation. As shown the peristaltic pump lobes pinch the tube and compress the tubing, thereby moving fluid through the tube 1332.

The flow rate of the fluid through the pump 1350 can be controlled by the speed of the pump motor. The motor can be a variable speed motor and the fluid flow rate can be precisely controlled by varying the speed of the motor.

The peristaltic pump can operate at low pressures, and can avoid building up high pressures if the tubing is not connected to the IV bag. The pressures can be sufficiently low that the connector 1328 does not leak when it is closed and the pump is operating and connected to a fluid source, such as the vial 1320. In some embodiments, the system does not include sensors for detecting the presence of a target container.

Additionally, the system does not include sensors, in some embodiments, for detecting air bubbles because the system uses the weight of the target container to determine when the correct amount of fluid is transferred. The pump can continue to operate until the desired amount of fluid has been transferred to the target container.

FIG. 10 is an example of a flowchart for a method of using a fluid transfer system to transfer fluid from a source container to a target container 1360. The fluid transfer system can use the same or similar components as the fluid transfer systems 1200, 1250, and 1300 described herein. At block 1362, source container (e.g., a medical vial or other suitable container such as a bag, a bottle, or a vat, etc.) is coupled to a fluid transfer station. The source container contains fluid (e.g., chemotherapy drug or other medical fluid). The source container can have a compatible adapter device. The source container is in fluid communication with a tubing assembly. The tubing assembly is in fluid communication with a target container (e.g., an IV bag, an elastomeric pump, a syringe, or other suitable container). The tubing assembly can be a closed system that retains substantially entirely, or entirely, all of the fluid within the assembly, permitting the fluid transfer to occur in a substantially entirely, or entirely, closed system. A closed system can reduce or eliminate the risk of injury, waste, or damage caused by liquid or vapor leakage when connecting and disconnecting the components of the fluidics system. The source container can be mounted on a fluid transfer station. The fluid transfer station can include a housing that incorporates a peristaltic pump, controller, user interface, and communication interface. The tubing assembly has a portion of tubing mounted within a peristaltic pump.

At block 1364 a target container (such as an IV bag, an elastomeric pump, a syringe, or other appropriate target container) is coupled to the opposite end of the tubing assembly. In some embodiments, the target container may be positioned on a weight sensor. The weight sensor is configured to weigh the target container to determine the amount of fluid that is transferred into the target container. The weight sensor can be incorporated in a separate housing from the fluid transfer station. The weight sensor can have a communication interface and can be in communication with the controller. The weight sensor can provide information to the controller and receive instructions from the controller.

At block 1366, the fluid transfer station receives a command to transfer a specific amount of fluid from the source container to the target container. A user can provide commands through the user interface on the fluid transfer station. In some embodiments the commands can be received by a remote source. The user can identify a specific amount of fluid that is to be transferred (e.g., 10 ml, 30, ml, 100 ml, etc.) to the target container. After determining the amount of fluid to be transferred, the user can instruct the fluid transfer system to proceed with the transfer. In some embodiments the fluid transfer system can verify that the user has entered in the correct amount of fluid to be transferred.

At block 1368, the fluid transfer station processes the commands and prepares the system to transfer the fluid to the target container. The controller zeros the weight sensor to compensate for other masses in the system, such as the weight of the target container assembly. This allows the scale to determine the amount of fluid that will be transferred to the target container. After the scale has been zeroed the controller can initiate the transfer of fluid to the target container.

At block 1370, the controller instructs the motor of the peristaltic pump to operate pumping until the weight of the scale meets the specified weight of transferred fluid in the target container. The motor can vary the speed of the peristaltic pump based on the amount of fluid to transfer to the target container. As the amount of fluid approaches the specified amount, the speed of the motor can slow down, thereby reducing the flow rate of fluid into the target container, in order to increase accuracy. The controller can use an algorithm to determine the appropriate speeds at which to operate the pump. In some embodiments the controller can determine the flow rate associated with different speeds of the motor. The controller will continue to operate the motor until the specified amount has been transferred to the target container.

At block 1372 additional source containers can be coupled to the fluid transfer station. The source containers can continue to be replaced until the specified amount of fluid has been transferred to the target container. In some embodiments the motor can stop when the controller detects that the source is disconnected. In other embodiments the pump continues to operate until the specified weight is achieved regardless of whether the source container is disconnected. In some embodiments the controller can determine that fluid is not being transferred from the source container to the target container. In some embodiments the controller can receive input from a sensor to determine whether the source container is empty. In some embodiments the controller can determine that fluid is not being transferred from the source container because the motor is operating but fluid is not being transferred. In such instances, the controller can provide an audible alarm to the user, stop the operation of the motor, and/or perform other appropriate actions. A reservoir container can be used to transfer the contents of multiple source containers to the reservoir container prior to transferring the fluid to the target container.

FIG. 11 is an example embodiment of a fluid transfer system 1500, which can have features similar to, or the same as, the systems 1200, 1250, or 1300 described above or any other fluid transfer system described herein. The system 1500 can include a fluid transfer station 1502 and various auxiliary devices. For example, the system 1500 may include a destination sensor, such as a weight sensor 1504. As another example, the system 1500 may include a foot pedal (not shown). The fluid transfer station 1502 may communicate with the weight sensor 1504 and/or foot pedal via communication interfaces (not shown) in the respective devices. In some embodiments, the communication interfaces may be wired communication interfaces configured to be coupled to—and communicate via—a cable or other physical transmission medium between devices. In some embodiments, the communication interfaces may be wireless communication interfaces configured to transmit and receive wireless signals. In some embodiments, communication between components of the system 1500 and/or to external systems (other fluid transfer systems, a hospital information system, etc.) may be provided using any of the communication interfaces or features described above with respect to the fluid transfer system 1300.

As shown, the fluid transfer station 1502 may include a housing 1510, a peristaltic pump 1512 to effectuate the transfer of fluid from a source container to a target container, and a user interface 1514. The user interface 1514 can include a touchscreen, a keypad, a display, a microphone, a speaker, and/or other suitable interface devices for providing information to a user and/or for providing input from the user to a controller (not shown). Examples of user interface displays to manage various operations of the system 1500 are described in greater detail below. The user interface 1514 can be incorporated into the housing 1510. The fluid transfer station 1502 may also include various internal components as shown in FIG. 13 and described in greater detail below.

The weight sensor 1504 may have features similar to, or the same as, the weight sensor 1322. In some embodiments, the weight sensor 1504 can include a user interface (not shown) and a weighing surface 1540. The user interface can provide a visual indication of weight, and other information. In some embodiments the weight sensor 1504 can receive commands or instructions through the user interface from a user. In some embodiments the weight sensor 1504 does not include a user interface. The weighing surface 1540 is configured to provide a surface for a target container, such as an IV bag. The weighing surface 1540 can be sized so that an IV bag or other target container can be properly balanced and positioned on the weight sensor 1504 such that the weight sensor 1504 is configured to obtain an accurate measure of the weight of the IV bag or other target container. The weight sensor 1504 may provide information (e.g., weight measurements, current state of operation, etc.) to and receive commands from (e.g., zeroing the weight sensor) the fluid transfer station 1502 through a wired or wireless communication interface (not shown). As described in greater detail below, the weight sensor 1504 may be used to determine the amount of fluid transferred from the source container to the target container. These measurements can be used to calibrate the operation of the fluid transfer station 1502, to verify fluid transfer operations, and the like.

A foot pedal can be configured to provide user input to the system 1500 in addition to, or instead of, input provided through the user interface 1514. The foot pedal can allow the user to have both hands free (e.g., to replace IV bags after each fluid transfer of a multiple-IV bag order). In some embodiments, the foot pedal can issue a repeat command that causes the system 1500 to perform a fluid transfer of the same amount as the previous fluid transfer. In some embodiments, the foot pedal may provide an emergency stop command, such as when the foot pedal is activated during an active fluid transfer. The foot pedal can provide various other signals to the controller, such as an accept command, a pause command, a start command, a cancel command, etc.

In some embodiments, the system 1500 can include a printer that can be configured to automatically print labels for use with the fluid transfer station 1502 or other components. For example, when a fluid transfer is performed, the printer can print a label automatically to be placed on the target container (e.g., IV bag). The label can include information such as the fluid type, the concentration, the amount of fluid, the intended patient, the requesting doctor, etc. In some embodiments, the printer can be directly attached to the fluid transfer station 1502, such as by a wire or cable extending from a port on the fluid transfer station 1502. In some embodiments, the printer can communicate with the fluid transfer station 1502 by a wireless data connection. The controller of the fluid transfer station 1502 can be configured to generate the printer instructions for printing the labels. In some embodiments, some or all of the aspects of the printer may be incorporated into the fluid transfer station 1502 (e.g., located within a housing of the fluid transfer station 1502).

The fluid transfer station 1502 can be configured to transfer medical fluid from a source container (e.g., a vial, bag, or the like) to a target container (e.g., an IV bag) using the peristaltic pump 1512 and a fluidics assembly, such as the fluidics assembly 1530 shown in FIG. 12. The peristaltic pump 1512 is a positive displacement pump used for pumping fluid from a source container to a target container. The peristaltic pump 1512 may include a cover 1520 that shields components of the peristaltic pump 1512 and/or fluidics assembly 1530 during use, and prevents injury to users of the pump 1512. The peristaltic pump 1512 may also include a mounting interface 1522 configured to receive the fluidics assembly 1530. Fluid is transferred via a compressible tube 1532 of the fluidics assembly 1530 fitted inside the mounting interface 1522.

A rotor 1524 may be coupled to a motor of the peristaltic pump 1512, and the motor may cause the rotor 1524 to rotate around a central axis. One or more lobes 1526 may be attached to an external circumference of the rotor 1524 to compress the flexible tube 1532, which may be positioned substantially adjacent to the external circumference of the rotor 1524. In some embodiments the lobes 1526 can be rollers, shoes, wipers, or other members that facilitate the operation of the pump 1512. In some embodiments, the peristaltic pump 1512 may have the same number or a different number of lobes as the peristaltic pump 1350 described above. For example, while the peristaltic pump 1350 shown in FIG. 9 has four lobes 1356, the peristaltic pump 1512 shown in FIG. 12 has three lobes 1526. During operation, a plurality of lobes 1526 (e.g., at least two out of three lobes) may be in contact with the tube 1532 simultaneously, and the particular lobes 1526 that contact the tube 1532 vary over the course of operation as the rotor 1524 turns. As the rotor 1524 is turned by the motor of the peristaltic pump 1512, at least a portion of the tube 1532 is compressed, or occludes, thus forcing the fluid to move through the tangentially-oriented tube 1532 towards the target container. The tube 1532 may be resilient such that after the passing of the lobes 1526 over a portion of the tube 1532, the portion of the tube 1532 expands to its natural state and fluid flow is induced from the source container. This process of tube 1532 compression and expansion may be repeated for as long as the rotor 1524 rotates and the lobes 1526 contact and pass over the tube 1532. The volume of fluid transferred through the tube 1532 for each rotation (or fractional rotation) of the rotor 1524 may be determinable, as described in greater detail below, and may be used during operation of the peristaltic pump 1512 to accurately transfer a desired total volume of fluid to a target container.

The fluidics assembly 1530 may be similar to, or the same as, the fluidics assembly 1339 shown in FIGS. 5-6. In some embodiments, as shown in FIG. 12, the fluidics assembly 1530 may include a positioning member 1534 that is configured to fit within the mounting interface 1522 in a single or limited number of orientations, thereby ensuring proper installation for use of the fluidics assembly 1530. To install the fluidics assembly 1530, the cover 1520 is opened, the compressible tube 1532 and optional positioning member 1534 are positioned within the mounting interface 1522, and the cover 1520 is closed.

In some embodiments, as shown in FIGS. 11 and 12, the peristaltic pump 1512 is located on top of the housing 1510. In this configuration, the plane in which the rotor 1524 rotates is parallel (or substantially parallel) to the plane of the surface upon which the fluid transfer station 1502 is positioned, and is orthogonal (or substantially orthogonal) to the direction of gravity. Thus, gravity does not aid or impede the flow of fluid through the portion of the compressible tube 1532 that is installed into the mounting interface 1522, because the entire portion of the tube 1532 installed into the mounting interface 1522 is also positioned such that the path of fluid flow is substantially orthogonal to the direction of gravity at all points within the mounting interface 1522. Moreover, the source container and target container (not shown) may be positioned such that they are also coplanar with the rotor 1524, or are both above the plane of the rotor 1524, or are both below the plane of the rotor 1524. Therefore, any effect of gravity on one portion of the fluidics assembly 1530 are negated by the opposite effect of gravity on another portion of the fluidics assembly 1530. In contrast, if the plane in which the rotor 1524 rotates is parallel to (or is otherwise not orthogonal to) the direction of gravity, then gravity may aid or impede the flow of fluid at certain points within the compressible tube, which may cause inefficiencies and inconsistencies (e.g., due to backflow or free flow immediately before or after a lobe 1526 compresses and/or decompresses the tube).

FIG. 13 shows example internal components of the fluid transfer station 1502 to facilitate various features described herein. As shown, the fluid transfer station 1502 may include: one or more computer processors 1550, such as central processing units (“CPUs”); one or more communication interfaces 1552, such as a network interface cards (“NICs”), wireless communication antenna and related circuitry, etc.; one or more input/output device interfaces 1554; one or more motors 1556; one or more motor controller units (“MCUs”) 1558 to control the operation of the motor(s) 1556; and one or more computer readable memories 1560, such as random access memory (“RAM”) and/or other non-transitory computer-readable media. The computer readable memory 1560 may include data storage and/or computer program instructions that the computer processor(s) 1550 execute in order to implement one or more embodiments. For example, the computer readable memory 1560 can store an operating system 1562 that provides computer program instructions for use by the computer processor(s) 1550 in the general administration and operation of the fluid transfer station 1502. The computer readable memory 1560 may also include fluid transfer instructions 1564 for initiating and managing the transfer of fluid. The computer readable memory 1560 may also include an operational settings data store 1568 to store fluid transfer parameters and other operational settings of the fluid transfer station 1502. The computer readable memory 1560 may also include a drug library 1570—also referred to as a medication database—to store data regarding the medical fluids transferred via the fluid transfer station 1502.

FIG. 14 shows example user interface (“UI”) displays 400, 420, and 440 for setting up and managing a fluid transfer operation using the fluid transfer system 1500. During a particular transfer operation, the peristaltic pump 1512 moves the fluid from the source container through the fluidics assembly 1530 and into the target container. An example of operation of an embodiment of a peristaltic pump is described in greater detail above with reference to FIG. 10. A user may initiate such a fluid transfer operation by selecting a medication via UI display 400. The user may enter or search for a medication profile using a medication entry control 402. In some embodiments, commonly-used or recently-used medication profiles may be available for faster selection using a quick select control 404. Upon selection of a medication profile, information may be loaded from a drug library and displayed on the UI display 400. For example, medication profile information may be loaded from the drug library 1570 of the fluid transfer station 1502 or obtained from another data store via a network, such as from a HIS. The UI display 400 may be updated to show aspects of the medication profile, such as the name of the fluid, an identifier, a lot number, an expiration, and the like.

In addition to—or instead of—such descriptive properties of the medication profile, the fluid transfer station 1502 may present fluid properties of the medication profile. For example, fluid properties may include the specific gravity 406 of the fluid (also referred to as the relative density), and the source container volume 408. As described in greater detail below, such fluid properties may affect the operation of the fluid transfer station 1502 in performing a fluid transfer operation, including the calibration of the fluid transfer station 1502 and/or verification of the fluid transfer operation. In some embodiments, the UI controls used to display the specific gravity 406, source container volume 408, or other fluid properties of the medication profile may allow editing of the displayed data. For example, a user may be permitted to modify the specific gravity of the fluid that is the subject of the displayed medication profile. Once a property has been edited, the UI display 400 may indicate that the property has been edited, such as by displaying an icon, changing a font characteristic, and/or preventing additional edits. In some embodiments, editing of medication profile data may be restricted to only authorized users (e.g., only authorized users may be permitted to change the specific gravities associated with medication profiles).

Once a medication profile has been selected (and optionally edited), the user may move to the next step of fluid transfer setup by selecting or providing transfer parameters. In some embodiments, UI display 420 may provide editable controls for setting transfer parameters. As shown, volume control 422 may allow selection or entry of a volume of fluid to be transferred from a source container to a target container. A speed control 424 may allow selection or entry of a speed at which the volume of fluid is to be transferred. The speed—or flow rate—at which fluid moves through the fluidics assembly 1530 can be controlled by the speed at which the MCU 1558 operates the motor 1556, which in turn controls the speed at which the rotor 1524 rotates. Users may wish to control the fluid flow rate based on one or more factors such as the viscosity of the fluid being transferred, the volume of fluid being transferred, and the like. A direction control 426 may allow selection or entry of a direction at which the fluid is to be transferred. For example, the options may be “forward” in which fluid is transferred from the source container to the target container, and “reverse” in which fluid is transferred back to the source container from the target container, or back to the source container from the fluidics system, which fills with air to replace the fluid. The “reverse” direction may be desirable when the fluid is expensive and preserving all unused fluid for future operations is preferable rather than to disposing of fluid along with a disposable fluidics assembly.

In some embodiments, the user may select a fluid transfer mode. For example, UI display 420 may include selectable controls for initiating a single transfer 428 (e.g., filling a single target container to a specified volume) or a batch transfer 430 (e.g., repeatedly transferring the desired volume of fluid to a configurable number of target containers). Batch transfer mode is described in greater detail below with respect to FIGS. 17 and 18.

Once a single fluid transfer operation has been initiated, UI display 440 may present the status of the transfer operation. For example, UI display 440 may include a transferred volume portion 442 that dynamically updates to display the volume of fluid that has been transferred from the start of the operation to the present time. UI display 440 may include a specified volume portion 444 that displays the total volume originally selected (e.g., via UI display 420) to be transferred to the target container.

UI display 440 may also include a specified weight portion 446 that displays the total weight of the fluid to be transferred to the target container. The fluid transfer station 1502 may determine the value to be displayed in the specified weight portion 446 based on one or more fluid properties and/or other aspects of the fluid transfer configuration. For example, the fluid transfer station 1502 may multiply the specific gravity—e.g., obtained from the selected medication profile or inputted by the user or sensed by a sensor—by the specified volume to be transferred to the target container in order to determine the specified weight according to the following equation:

$w=\mathrm{sg}\times v$ where w=weight of the fluid in a given unit of weight (such as grams), sg=specific gravity of the fluid in the given unit of weight per a given unit of volume (such as grams per milliliter), and v=volume of the fluid in the given unit of volume (milliliters in this example).

The peristaltic pump 1512 may be configured to rotate the rotor 1524 a particular quantity of revolutions (or a particular fraction of a revolution) per volume unit of fluid to be transferred. For a transfer operation, the fluid transfer station 1502 may determine the quantity of revolutions that the rotor 1524 is to be rotated in order to cause transfer of the desired volume of fluid. The fluid transfer station 1502 may load an operation setting, such as a setting stored in the pump settings data store 1568, indicating the quantity of revolutions per unit of fluid to be transferred.

In some embodiments, multiple settings may be stored in the pump data store 1568, and individual settings may indicate a quantity of revolutions that the rotor 1524 is to be rotated per unit of fluid to be transferred, when the transfer operation is associated with different fluid properties and/or transfer parameters. For example, a first setting may be associated with fluid transfer operations occurring at a first speed (in terms of rotor revolutions per minute, units of fluid per minute, etc.), and a second setting may be associated with fluid transfer operations occurring at a second speed that is different than the first speed. As another example, a first setting may be associated with fluid transfer operations of fluids with a first specific gravity, while a second setting may be associated with fluid transfer operations of fluids with a second specific gravity that is different than the first specific gravity. As a further example, a first setting may be associated with fluid transfer operations of fluids with a first viscosity, while a second setting may be associated with fluid transfer operations of fluids with a second viscosity that is different than the first viscosity. In some embodiments, settings may be associated with combinations of fluid properties and/or fluid transfer parameters. For example, a first setting may be associated with fluid transfer operations of fluid with a first viscosity, where the transfer operations occur at a first speed, and so on.

The peristaltic pump 1512 may drift out of proper calibration for a number of reasons. For example, different fluidics assemblies may have subtle variances due to manufacturing tolerances that cause different volumes of fluid to be pumped through different assemblies for the same quantity of rotor rotations. As another example, as the motor is used its operational performance and specifications may gradually change due to wear. In some cases, environmental factors such as volume, humidity, altitude, barometric pressure, or the like may affect the calibration of the peristaltic pump 1512. To address these and other calibration issues, a calibration process may be performed on a periodic and/or on-demand basis.

FIG. 15 is a flowchart of an example process 500 that may be used to calibrate the fluid transfer station 1502 such that the volume of fluid transferred to a target container matches, or comes within a threshold amount or percentage of matching, the volume that was directed to be transferred. As described in greater detail below, the calibration process 500 involves transferring a desired volume of fluid using a current set of operational settings, measuring the volume that was actually transferred, determining an offset between the desired volume and the transferred volume, and adjusting the operational settings as needed so that future transfer operations result in the amount of volume transferred being the same as—or within an acceptable degree of accuracy of—the desired volume. Advantageously, in some embodiments the calibration process 500 can use the weight sensor 1504 and fluid properties in medication profiles to determine whether to modify operational settings—and if so, the degree to which the operational settings are to be modified—without requiring any specialized target container for the transferred fluid, and without requiring the transferred fluid to be removed from the target container for a volume measurement. Rather, the measurements during the calibration process 500 may be taken after transferring fluid to the same standard target containers used in routine transfer operations, including target containers from which the fluid will eventually be administered to patients. In this way, calibration may be performed more easily, and more often if needed, than alternative calibration methods.

The process 500 begins at block 502. The process may begin in response to an event, such as when the fluid transfer station 1502 is powered on, at recommended intervals, or on-demand. In some embodiments, calibration may be recommended or required periodically or in response to an event. For example, calibration may be recommended or required after each change of fluidics assembly, each change of desired volume, each change of target container type, or when the fluid transfer station 1502 has transferred a threshold volume of fluid since the last calibration (e.g., every 10,000, 30,000, or 100,000 milliliters of fluid transferred).

When the process 500 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device. For example, FIG. 13 shows an example fluid transfer station 1502 in which calibration instructions 1566 may be loaded into memory 1560, and executed by a processor 1550.

At decision block 504, the fluid transfer station 1502 can determine whether a fluidics assembly has been installed and primed. For example, the fluid transfer station 1502 may prompt a user via user interface 1514 to indicate whether the fluidics assembly is primed. If the fluidics assembly has not been primed, the process 500 may proceed to block 506 to prime the assembly. Otherwise, if the assembly has been primed, the process 500 may proceed to block 508.

At block 508, the fluid transfer station 1502 can obtain fluid properties for the fluid that is to be used during the calibration operation. In some embodiments, a user interface display with features that are similar to—or the same as—UI display 400 may be used to select the fluid that is to be used during the calibration operation. For example, determining fluid properties can include determining the specific gravity of the fluid to be transferred. The fluid transfer station 1502 may load the specific gravity from the drug library 1570 after selection of the particular fluid to be transferred. In some embodiments, other fluid properties may be determined, such as the viscosity of the fluid to be transferred.

At block 510, the fluid transfer station 1502 can obtain transfer parameters for the calibration operation. In some embodiments, a user interface display with features that are similar to—or the same as—UI display 420 may be used to select the volume of fluid that is to be transferred during the calibration operation. In some embodiments, other fluid transfer parameters properties may be determined, such as the speed at which fluid is to be transferred. The fluid transfer station 1502 may also obtain the current operational settings in order to manage the transfer of fluid. For example, the fluid transfer station 1502 may load a setting, stored in the pump settings data store 1568, indicating the quantity of revolutions per unit of fluid to be transferred. The operational setting may be a universal setting that applies to all fluids and transfer operations, or it may be an operational setting that applies to transfer of fluids with specific fluid properties (e.g., viscosity, specific gravity, etc.) and/or using specific transfer parameters (e.g., speed, type of fluidics assembly, etc.).

At block 512, the weight sensor 1504 can be initialized. Initialization of the weight sensor 1504 may be performed to ensure that weight measurements generated by the weight sensor 1504 are accurate. In some embodiments, the weight sensor may be initialized to account for tare. For example, the weight sensor 1504 may be initialized such that it produces a weight measure of 0.0 units when an empty target container is on the weight sensor 1504. Accordingly, when fluid is transferred into the target container, the weight sensor 1504 will indicate the weight of the fluid only, and not the target container.

At block 514, the fluid transfer station 1502 can initiate transfer of the indicated volume of fluid to the target container. Transfer of the volume of fluid may proceed in a manner similar to—or the same as—transfer of fluid in a non-calibration-related transfer operation as described in greater detail above. In some embodiments, a user interface display with features that are similar to—or the same as—UI display 440 may be used to present the status of the fluid transfer operation.

At block 516, a measurement of the transferred volume of fluid can be determined. The measurement may be a weight measurement of the transferred fluid, as measured by the weight sensor 1504. The measurement may be provided from the weight sensor 1504 to the fluid transfer station 1502 via wired or wireless transmission. For example, after the fluid transfer station 1502 completes transfer of the volume of fluid using the operational settings, the fluid transfer station 1502 may request, read, receive, or otherwise obtain a measurement from the weight sensor 1504. In some embodiments, rather than obtaining the weight via transmission from the weight sensor 1504, the weight may be provided to the fluid transfer station 1502 by a user via a user interface. For example, UI display 600 shown in FIG. 6 may provide an interactive control 602 for entering, selecting, or otherwise providing a weight measurement. The user may review a user interface of the weight sensor 1504 to determine the weight measured by the weight sensor 1504, and then provide the determined weight measurement to the fluid transfer station 1502 via the UI display 600.

At block 518, the fluid transfer station 1502 can determine an observed volume of fluid transferred to the target container based on the weight measurement obtained in block 516 above, and a property of the fluid such as the specific gravity of the fluid. For example, the fluid transfer station 1502 may divide the measured weight of the transferred fluid by the specific gravity from the selected medication profile to arrive at the observed volume transferred to the target container, according to the following equation:

$v=w/\mathrm{sg}$ where w=weight of the fluid in a given unit of weight (such as grams), sg=specific gravity of the fluid in the given unit of weight per a given unit of volume (such as grams per milliliter), and v=volume of the fluid in the given unit of volume (such as milliliters).

At block 520, the fluid transfer station 1502 can determine an adjustment to address any difference between the observed volume and the desired volume. The fluid transfer station 1502 may first analyze the observed volume with respect to the desired volume to determine whether there is a difference or “offset.” If there is an offset, the fluid transfer station 1502 may adjust an operational setting to address the offset. For example, the fluid transfer station 1502 may determine that the number of rotor revolutions previously used to transfer the desired volume is now associated with the observed volume, which is different than the desired volume. A modification to the operational setting that represents the number of rotor revolutions may be made to ensure that use of the operational setting produces the desired volume. In some embodiments, adjusting the setting may be based on the magnitude and direction of the offset. For example, the offset may be based on the percentage of the observed volume in terms of the desired volume: a positive value indicates greater than 100% of the desired volume has been transferred, and a negative value indicates less than 100% of the desired volume has been transferred. The operational setting may be adjusted by the offset value: reducing the setting by a percentage corresponding to the offset value if the sign of the offset is positive (indicating an overfill), and increasing the setting by a percentage corresponding to the offset value if the sign of the offset is negative (indicating an underfill).

At decision block 522, the fluid transfer station 1502 can determine whether the offset determined above at block 520 is within a calibration threshold. An offset exceeding a calibration threshold may indicate that a relatively large change to the operational setting was made. A large offset may have been anomalous, or a large change to the operational setting may be associated with less than desired precision. In such cases, the calibration process 500 may return to block 504 and be performed again to verify that the change made to the operational setting indeed results in the desired volume of fluid being transferred. The re-performance of the calibration process may be automatic or required. For example, in response to determining that the offset is outside of the calibration threshold, use of the fluid transfer station 1502 may not be permitted until the calibration process 500 is performed again. In some embodiments, re-performance of the calibration process 500 may be optional or manually initiated. For example, a user interface such as UI display 620 shown in FIG. 6 may provide a warning or other indication 622 that the offset exceeds a calibration threshold. A user may accept the calibration change (e.g., by activating an acceptance control 624), or choose to perform another calibration process (e.g., by activating a re-calibration control 626) to verify that the change has brought the fluid transfer station 1502 within the desired level of calibration.

At block 524, the process 500 may terminate.

In addition to being performed on-demand or in response to particular recommendations, calibration may be incorporated into a batch process at regular intervals. In some embodiments, a user may configure the fluid transfer station 1502 to transfer a same volume of fluid to a predetermined number of target containers without requiring reconfiguration of the fluid transfer station 1502 between target containers. For example, a same volume of saline (e.g., 100 ml) may be transferred from a large source container to multiple individual target containers (e.g., 5, 10, 50, or more individual target containers) after a single setup operation, without requiring a corresponding number of setup operations (e.g., without requiring 5, 10, 50, or more setup operations using the UI displays 400, 420, 440). In order to detect and address any calibration issues that may arise during the batch operation, periodic calibration checks may be performed during the batch process.

FIG. 17 is a flowchart of an example process 700 that may be used to perform a batch transfer of fluid to multiple target containers while periodically checking the calibration of the fluid transfer station 1502. As described in greater detail below, the batch transfer process 700 involves iteratively transferring a desired volume of fluid using a current set of operational settings, periodically measuring the volume that was actually transferred, and adjusting the operational settings as needed. Advantageously, the batch transfer process 700 uses the weight sensor 1504 and fluid properties in medication profiles to verify the calibration of the fluid transfer station 1502.

The process 700 begins at block 702. The process may begin in response to an event, such as when a user accesses a user interface to initiate a batch transfer process. When the process 700 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device. For example, FIG. 13 shows an example fluid transfer station 1502 in which fluid transfer instructions 1564 may be loaded into memory 1560, and executed by a processor 1550.

At block decision block 704, the fluid transfer station 1502 can determine whether a fluidics assembly has been installed and primed. For example, the fluid transfer station 1502 may prompt a user via user interface 1514 to indicate whether the fluidics assembly is primed. If the fluidics assembly has not been primed, the process 700 may proceed to block 706 to prime the assembly. Otherwise, if the assembly has been primed, the process 700 may proceed to block 708.

At block 708, the fluid transfer station 1502 can obtain fluid properties for the fluid that is to be used during the batch transfer operation. In some embodiments, a user interface display with features that are similar to—or the same as—UI display 400 may be used to select the fluid that is to be used during the batch transfer operation. For example, determining fluid properties can include determining the specific gravity of the fluid to be transferred. The fluid transfer station 1502 may load the specific gravity from the drug library 1570 after selection of the particular fluid to be transferred. In some embodiments, other fluid properties may be determined, such as the viscosity of the fluid to be transferred.

At block 710, the fluid transfer station 1502 can obtain transfer parameters for the batch transfer operation. In some embodiments, a user interface display with features that are similar to—or the same as—UI display 420 may be used to select the volume to be transferred in each segment of the batch transfer operation, and the speed at which the desired volume is to be transferred in each segment. In addition to these transfer parameters, additional parameters may be set for the batch transfer operation. A user interface display, such as UI display 800 in FIG. 18, may be presented to facilitate the configuration of additional parameters of batch transfer operation. For example, the UI display 800 may include an interactive segment entry control 802 for selecting or entering a desired quantity of target containers into which the desired volume of fluid is to be transferred. The batch transfer operation will include a segment for each target container. The UI display 800 may also include an interactive interval time control 804 for selecting or entering the desired length of time to be used as the interval between each segment of the batch transfer operation. The interval provides time for the user of the fluid transfer station 1502 to perform various tasks related to completion of a segment and/or preparation for a next segment, such as disconnecting a target container—filled during the most-recently-completed segment of the batch transfer operation—from the fluidics system, connecting a new empty target container to the fluidics system for the next segment of the batch transfer operation, etc.

At block 712, a segment of the batch transfer process may be performed. The fluid transfer performed in each individual segment of the batch transfer process may proceed in a manner similar to—or the same as—transfer of fluid in a non-batch transfer operation as described in greater detail above. In some embodiments, a user interface display such as UI display 820 may be used to present the status and results of the current segment. UI display 820 may include a segment indicator portion 822 to indicate which segment of the batch transfer operation is currently in progress, a transferred volume portion 824 to indicate the volume transferred the far during the current segment of the batch transfer process, a desired volume portion 826 to indicate the desired volume to be transferred during the current segment, and an interval indicator portion 828 to indicate the length of the interval between segments (e.g. a quantity of units of time, such as seconds).

At decision block 714, after the current segment of the batch transfer process has completed, the fluid transfer station 1502 can determine whether a number of segments transferred since the last calibration check—or since the beginning of the process 700—has reached a verification threshold. If so, the process proceeds to block 716 to verify the calibration based on the most recently completed segment of the batch transfer process. Otherwise, the process may continue at decision block 718. The verification threshold may be a predetermined value, such as an operational setting of the fluid transfer station 1502. For example, the threshold may be set to a value (e.g., 10, 50, 100) when the fluid transfer station 1502 is manufactured, maintained by an administrator, or the like. In some embodiments, the verification threshold may be configurable for a given batch transfer process. For example, a UI display such as UI display 800 may include an interactive control for selecting or entering the verification threshold to be used for the current batch transfer process,

At block 716, the calibration of the fluid transfer station 1502 can be verified based on the most recently completed segment of the fluid transfer process. The calibration may be verified based on the weight of the filled target container. In some embodiments, a process that is the same—or similar to—the calibration process 500 described in greater detail above may be used. For example, a user may place the filled target container on the weight sensor 1504. The weight measured by the weight sensor 1504 may be provided to the fluid transfer station 1502 automatically (e.g., via wired or wireless communication between the weight sensor 1504 and the fluid transfer station 1502), or manually (e.g., the user may enter the weight measurement in a user interface of the fluid transfer station 1502). The fluid transfer station 1502 may determine the observed volume of fluid transferred to the target container based on the weight using a fluid property, such as the specific gravity of the fluid, as described in greater detail above. The fluid transfer station may further determine an offset between the observed volume of fluid and the desired volume fluid, as also described in greater detail above. An operational setting may be automatically changed based on the offset, or the user may be prompted as to whether to update the operational setting.

At decision block 718, the fluid transfer station 1502 can determine whether there are any additional segments of the batch transfer process to be completed. If so, the process 700 can proceed to block 720. Otherwise, the process may terminate at block 722.

At block 720, there are one or more additional segments of the batch transfer process to be completed, and the fluid transfer station 1502 can wait for the designated interval between segments before returning to block 712 for the next segment. The interval provides time for the user of the fluid transfer station 1502 to perform various tasks related to completion of a segment and/or preparation for a next segment, such as disconnecting a target container—filled during the most-recently-completed segment of the batch transfer operation—from the fluidics system, connecting a new empty target container to the fluidics system for the next segment of the batch transfer operation, etc. In some embodiments, a UI display (such as UI display 820) may include a dynamic interval time indicator (not shown) that indicates the amount of time remaining in the interval before the next segment of the batch transfer process is to begin. If the user requires additional time between segments or otherwise wishes to pause or stop the batch transfer process, the user may activate a control on a UI display, activate the pedal, or use other input method.

Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, operations or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of electronic hardware and computer software. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, or as software that runs on hardware, depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as programmable computer central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. For example, some or all of the algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. When a method, process, routine, or algorithm is to be executed, executable instructions may be loaded to or accessed at a storage medium and executed by one or more processors. In some embodiments, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal.

Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A medical fluid transfer system comprising: a pump comprising a rotor with one or more lobes, wherein the pump is configured to transfer fluid through a tube assembly having a first connector configured to couple to a source container and a second connector configured to couple to a target container;a destination sensor configured to output information about the target container; anda control system configured to: receive an instruction to transfer a desired volume of a medical fluid to the target container;operate the pump based on the instruction and an operational setting associated with a first quantity of rotations that the rotor is to be rotated for transfer of a fluid volume of the medical fluid;receive measurement data representing a measurement of the target container by the destination sensor;determine a difference between a transferred volume of the medical fluid and the desired volume of the medical fluid based at least partly on the measurement data and a fluid property of the medical fluid;adjust the operational setting based on the difference to a second quantity of rotations that the rotor is to be rotated for transfer of the fluid volume of the medical fluid; andoperate the pump based on the operational setting that has been adjusted.

2. The medical fluid transfer system of claim 1, further comprising the tube assembly.

3. The medical fluid transfer system of claim 1, wherein the destination sensor comprises a weight sensor, and wherein the measurement data represents a weight of the target container after operation of the pump.

4. The medical fluid transfer system of claim 1, wherein the control system comprises a user interface, and wherein the measurement data is received by the control system via the user interface.

5. The medical fluid transfer system of claim 1, wherein the control system comprises a first communication interface, wherein the destination sensor comprises a second communication interface, wherein the destination sensor transmits the measurement data via the second communication interface, and wherein the measurement data is received by the control system via the first communication interface.

6. The medical fluid transfer system of claim 1, wherein the fluid property comprises a specific gravity of the medical fluid, and wherein the control system is further configured to determine the transferred volume of medical fluid based on the specific gravity and a weight of the target container represented by the measurement data.

7. The medical fluid transfer system of claim 1, wherein the control system is further configured to determine an adjustment to the operational setting based on a magnitude of the difference.

8. The medical fluid transfer system of claim 1, wherein the pump is a peristaltic pump.

9. The medical fluid transfer system of claim 8, further comprising a housing, wherein the housing is configured to support the peristaltic pump in a position in which a plane of rotation of the rotor is substantially orthogonal to a direction of gravity during operation of the peristaltic pump.

10. The medical fluid transfer system of claim 8, wherein the peristaltic pump is configured to operate at a plurality of speed settings.

11. The medical fluid transfer system of claim 1, wherein the control system is further configured to manage a batch transfer operation in which the control system operates the pump to transfer the desired volume of the medical fluid to each of a plurality of target containers.

12. The medical fluid transfer system of claim 11, wherein the control system is further configured to delay a subsequent segment of the batch transfer operation for a predetermined time interval after completion of a prior segment of the batch transfer operation.

13. The medical fluid transfer system of claim 11, wherein the control system is further configured to determine that the medical fluid has been transferred to a threshold quantity of target containers during the batch transfer operation, wherein the measurement data is received in response to the control system determining that the medical fluid has been transferred to the threshold quantity of target containers.

14. A method for calibrating a medical fluid transfer system, the method comprising: under control of a control system of the medical fluid transfer system, the control system comprising one or more computer processors configured to execute specific instructions: receiving an instruction to transfer a desired volume of a medical fluid to a target container;operating a pump of the medical fluid transfer system based on the instruction and an operational setting, wherein the pump comprises a rotor and one or more lobes, and wherein the operational setting is associated with a first quantity of rotations that the rotor is to be rotated for transfer of a fluid volume of the medical fluid;receiving measurement data representing a measurement of the target container by a destination sensor;determining a difference between a transferred volume of the medical fluid and the desired volume of the medical fluid based at least partly on the measurement data and a fluid property of the medical fluid; andadjusting the operational setting based on the difference to a second quantity of rotations that the rotor is to be rotated for transfer of the fluid volume of the medical fluid.

15. The method of claim 14, further comprising operating the pump using the operational setting that has been adjusted.

16. The method of claim 14, further comprising determining the transferred volume of the medical fluid based on the fluid property and the measurement data, wherein the fluid property comprises a specific gravity of the medical fluid, and wherein the measurement data represents a weight of the target container.

17. The method of claim 14, further comprising determining an adjustment to the operational setting based on a magnitude of the difference.

18. The method of claim 14, further comprising loading the operational setting from a data store, wherein the operational setting indicates a quantity of rotations that a rotor of the pump is to be rotated for transfer of one or more volumetric units of the medical fluid.

19. The method of claim 14, further comprising: managing a batch transfer operation in which the desired volume of the medical fluid is transferred to each of a plurality of target containers; anddelaying a segment of the batch transfer operation for a predetermined time interval after completion of a prior segment of the batch transfer operation.