System and method for automated infusion of an infusion line

Abstract

The subject technology includes a pressure perfusion device configured such that in response to fluid flowing into the pressure perfusion device, a fluid input of the pressure perfusion device has a first fluid breakthrough back pressure, and the fluid output end of the pressure filling device is provided with a second fluid breakthrough back pressure which is greater than the first fluid breakthrough back pressure. A pump controller is configured to determine a perfusion pressure threshold greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure, and initiate perfusion of a fluid conduit connected to the fluid input of the pressure perfusion device with fluid. The pump controller automatically terminates perfusion of the fluid conduit when the perfusion pressure of the fluid satisfies the determined perfusion pressure threshold, and provides an indication that the fluid conduit is perfused in response to the fluid satisfying the determined perfusion pressure threshold.

Description

BACKGROUND OF THE INVENTION

[0001] There are various situations where fluids are infused into patients. Applications of fluid delivery systems include, but are not limited to, intravenous (IV) infusions, intra-arterial infusions, enteral infusions, drug infusions into the epidural space, and diagnostic infusions for determining vascular characteristics of the arterial, urinary, lymphatic, or cerebrospinal systems.

[0002] Fluid delivery systems for infusing fluids into patients typically include a fluid source of the fluid to be administered, an infusion needle or cannula, a delivery device connecting the fluid source to the cannula, and a flow control device such as a volumetric infusion pump. The delivery device typically includes a section of flexible tubing. The cannula is mounted at the distal end of the flexible tubing for insertion into a patient's blood vessel or other body part to deliver the infusion to the patient.

[0003] Some intravenous injection devices used with infusion pumps include an anti-siphon valve at the distal end to prevent accidental free flow and backflow. This also prevents perfusion of the device by gravity. Instead, perfusion is achieved by manually removing the sterile cap from the Luer fitting and pressing the perfusion button on the pump. The perfusion mechanism pushes a preset volume of fluid through the tubing (usually exceeding the air / dead space of the intravenous injection device). In many cases, the clinician must manually monitor the perfusion process and stop the pump once fluid starts flowing out of the distal end. This can be a cumbersome / messy / time-consuming process as another receptacle is needed to hold the excess fluid and / or there are risks in terms of sterile, hazardous / controlled drugs, etc. All of these increase the clinician's workload, inefficiency of the workflow, and potential clinical risks. SUMMARY OF THE INVENTION

[0004] In accordance with various aspects of the present subject technology, there is provided a system for automatically perfusing an infusion line. The system includes a pressure perfusion device configured such that in response to fluid flowing into the pressure perfusion device, a fluid input end of the pressure perfusion device has a first fluid breakthrough backpressure and a fluid output end of the pressure perfusion device has a second fluid breakthrough backpressure greater than the first fluid breakthrough backpressure; and a pump controller configured to: determine a perfusion pressure threshold greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure; initiate perfusion of a fluid line connected to the fluid input end of the pressure perfusion device with fluid; automatically terminate perfusion of the fluid line when the perfusion pressure of the fluid meets the determined perfusion pressure threshold; and provide an indication that the fluid line has been perfused in response to the fluid meeting the determined perfusion pressure threshold. Other aspects include corresponding devices, methods, and processes for corresponding system implementations.

[0005] A method for automatically perfusing an infusion line, the method comprising: providing a pressure perfusion device configured such that, in response to fluid flowing into the pressure perfusion device, a fluid input end of the pressure perfusion device has a first fluid breakthrough backpressure and a fluid output end of the pressure perfusion device has a second fluid breakthrough backpressure greater than the first fluid breakthrough backpressure; determining a perfusion pressure threshold greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure; initiating perfusion of a fluid line connected to the fluid input end of the pressure perfusion device with fluid; automatically terminating perfusion of the fluid line when the perfusion pressure of the fluid meets the determined perfusion pressure threshold; and providing an indication that the fluid line has been perfused in response to the fluid meeting the determined perfusion pressure threshold. Other aspects include corresponding devices, systems, and processes for corresponding method embodiments.

[0006] It should be understood that, from the following detailed description, those skilled in the art should readily understand other configurations of the subject technology, where various configurations of the subject technology are shown and described by way of illustration. As should be recognized, the subject technology is capable of having other and different configurations, and several details thereof can be modified in various other aspects, all without departing from the scope of the subject technology. Therefore, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To better understand the various embodiments described, reference should be made to the following description of the embodiments in conjunction with the following drawings. Throughout the drawings and the description, the same reference numerals represent corresponding parts.

[0008] Figure 1 An illustration shows a caregiver administering an infusion to a patient in a typical medical care environment.

[0009] Figure 2A A depiction shows an example infusion pump device shown in its intended environment according to various aspects of the subject technology.

[0010] Figure 2B A perspective view depicts an example infusion device according to various aspects of the subject technology, the perspective view showing an infusion device located within the infusion device.

[0011] Figure 3A and 3B An exploded view depicts an example pressure perfusion device according to various aspects of the subject technology.

[0012] Figure 4A 、 Figure 4B and Figure 4C An illustration depicts an example of perfusing an infusion line using a pressure perfusion system of the subject technology.

[0013] Figure 5 depicts an example process for automatically priming an infusion line according to various embodiments of the present subject matter technology.

[0014] Figure 6 is a conceptual diagram showing an example electronic system for automatically priming an infusion line according to aspects of the present subject matter technology. DETAILED DESCRIPTION

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

[0016] The present subject matter technology provides a system for automatically priming an infusion line. According to various embodiments, a pressure priming device includes a first part and a second part that are removably coupled together. When the pressure priming device is connected to a fluid conduit, the pressure priming device restricts the fluid by using two backpressure regulators at the input and output ends of the device, thereby forcing the fluid to flow directionally through the conduit and controlling the flow of fluid into the chamber of the priming device. In this regard, different backpressures are generated at the input and output ends, where the backpressure at the output end is greater than the backpressure at the input end of the pressure device. Accordingly, the pump controller initiates priming of the fluid conduit by pumping fluid through the conduit and into the chamber of the priming device until the pressure within the conduit is greater than the backpressure at the input end but less than the backpressure at the output end. For example, the pump system can pre-select a threshold backpressure value between the input backpressure and the output backpressure and determine the conduit to be primed when the internal fluid pressure within the conduit reaches the threshold backpressure.

[0017] As used herein, "fluid breakthrough backpressure" is the minimum required pressure that the fluid flowing through the conduit must flow against to flow through the conduit (overcome the breakthrough backpressure). As will be further described, the first part of the pressure priming device may also include a check valve located at the input end to control the directional flow of fluid. The valve can generate a first breakthrough backpressure as a function of the opening pressure of the valve (including part tolerances). The second part of the pressure priming device may include a hydrophobic filter (such as a hydrophobic membrane) located at its output end, which generates a second breakthrough backpressure based on the water pressure resistance of the hydrophobic filter (such as the liquid entry pressure, including tolerances).

[0018] The hydrophobic filter allows air to flow through the filter within the conduit but does not allow fluid to flow, thereby eliminating problems encountered in existing perfusion techniques. During the perfusion function, the pump monitors the downstream line pressure, and once a threshold backpressure (e.g., the pressure between a first and second breakthrough backpressure) is met, the pump automatically stops the perfusion action and notifies the user via a display that the perfusion is complete. According to various embodiments, the threshold backpressure is selected to be greater than the first breakthrough backpressure and less than the second breakthrough backpressure. Because the pressure is greater than the first breakthrough backpressure, the system ensures that the infusion line has been perfused and avoids a manual priming process, and because the pressure is less than the second breakthrough backpressure, the system eliminates or minimizes fluid spillage.

[0019] Figure 1 Illustrated is a caregiver 2 administering an infusion to a patient 4 in a typical healthcare environment. The patient receives infusion fluid through an IV administration device 5 coupled to the patient's vascular system. The IV administration device 5 can include a drip chamber 6 coupled to an infusion fluid container 14, a conduit of an IV line 7 having a proximal end of the IV line 7 coupled to the drip chamber 6, and a distal end of the IV line 7 coupled to a catheter 22. A roller clamp 8 can be coupled to a section of the IV line 7 between the fluid container 14 and the catheter 22. In some embodiments, the IV line 7 can terminate at a luer fitting 9 having a perfusion cap (not shown) before a downstream portion 20 of the IV line 7 and the catheter 22 are coupled to the fluid container 14. In some embodiments, the IV perfusion cap can engage or be coupled to a portion of the IV line 7 such as the roller clamp 8.

[0020] The IV administration device can be gravity perfused through the distal end of the IV line 7 coupled to the IV perfusion cap, or the IV administration device can be perfused by separating a fluid connector from the IV perfusion cap. The perfusion cap can include a hydrophobic membrane to prevent fluid from flowing through the IV line while allowing air to flow through, thereby perfusing the IV administration device. Thus, the free flow of fluid through the IV line to the membrane is unobstructed. The clinician ensures that there is a head height difference between the end of the line 7 and the fluid container 14 and gravity fills the line. The perfusion cap with the hydrophobic membrane allows air to pass through but does not allow liquid to pass through.

[0021] The fluid moves freely through the tubing and the Luer connector 9, and gravity causes the fluid to push air through the hydrophobic membrane in the lid of the connector. Since there is not enough force to pass through the membrane, the fluid stays on the membrane. Then, the clinician can leave the fluid in the tubing while attending to other tasks. Then, the clinician can return to the patient and remove the perfusion cap. Then, the clinician can connect the downstream portion 20 of the tubing, and the infusion set is ready for use. In some embodiments, the clinician can use a pump to prime the tubing. However, the pump may push the fluid through the membrane, causing the fluid to spill out, which may be undesirable, especially when the fluid contains certain drugs (e.g., chemotherapy drugs).

[0022] Figure 2A An example infusion pump device 10 is depicted that illustrates its use in an intended environment in accordance with various aspects of the present subject technology. In particular, the infusion pump device 10 is shown mounted to an intravenous (IV) pole 12 on which a fluid source 14 containing an IV fluid is held. The fluid source 14 is fluidly connected to an upstream fluid tubing 16. The fluid tubing 16 is a conventional IV infusion type tubing commonly used in a hospital or medical setting and is made of any type of flexible tubing such as polyvinyl chloride (PVC) suitable for infusing a therapeutic fluid into a patient. A flexible pumping fluid tubing 18 is mounted to be operatively engaged with a peristaltic pumping device 19 for pushing the fluid through a downstream fluid tubing 20, e.g., to a patient's arm. A cannula 22 is mounted at the distal end of the flexible IV tubing 21 for insertion into a patient's blood vessel or other body part to deliver the fluid to the patient.

[0023] Those skilled in the art will understand that the upstream fluid tubing 16, the flexible tubing 18, and the downstream fluid tubing 20 can be part of a continuous length of flexible tubing, where the portion is defined by the location of the peristaltic pump 19. For convenience, the continuous length of the flexible tubing is denoted by the numeral 21. A roller clamp (e.g., configured to provide mechanical compression of the tubing to block flow) can be located on the downstream fluid tubing 20 between the pump 10 and the patient's arm 22. As used herein, the term "upstream" refers to the portion of the flexible tubing that extends between the fluid source and the peristaltic pump, and the term "downstream" refers to the portion of the flexible tubing that extends from the peristaltic pump to the patient.

[0024] Before connecting the downstream fluid tubing 20 to the flexible infusion device 18 and the medical container 14 above, a pressure priming device 25 can be installed at one end of the infusion tubing 21. As will be further described, the pressure priming device 25 uses two backpressure regulators to force the fluid to flow directionally through the tubing and into the chamber of the priming device, and to restrict the flow of fluid from the tubing 21 into the device 25. In this way, the tubing 21 connected to the tubing can be precisely primed with fluid controlled by the pump without fluid leakage occurring during the priming process.

[0025] Figure 2B FIG. depicts a perspective view of an exemplary infusion device in accordance with aspects of the present subject matter, the perspective view of the exemplary infusion device showing an infusion assembly located within the infusion device. An infusion system for parenterally infusing a medical fluid to a patient, the infusion system including a pump unit, a main portion of the pump unit including a housing that houses a cam system (not shown) of a plurality of fingers that control a pumping mechanism, a motor that drives the cam mechanism, and associated gearing, and further houses an electronic control and processing circuit for controlling such motor and processing signals from a pressure sensor, etc., disposed on the unit. As shown, the pump unit may also include an electronically operated display, an alarm light, an input keypad, or other manually operated controller, all in a manner known per se.

[0026] As Figure 2B shown, a perspective view shows an infusion pump 10 with its front door 50 open, showing an upstream fluid line portion 30 (e.g., a portion of the upstream infusion line 16) and a downstream fluid line 31 (e.g., a downstream portion of the infusion line 21) operatively engaged with the operation of the pump 10. The infusion pump 10 acts directly on a conduit 66 that connects the upstream fluid line 30 to the downstream fluid line 31 to form a continuous fluid conduit extending from a corresponding fluid source to the patient, through which the pump acts on the fluid to move the fluid downstream to the patient. Specifically, a pumping mechanism 70 acts as a flow control device of the pump to move fluid through the conduit. The depicted reference numerals 30, 31, 66 may be used herein to describe portions of a continuous fluid line 21, or in some embodiments, may separately describe portions that are fluidly connected together to form a continuous fluid line. The upstream and downstream fluid lines and / or conduits 30, 31, 66 may also be coupled to a pump cassette or barrel configured to be coupled to the pump 10, such as the type described in co-pending U.S. Patent No. 10,226,571, which is incorporated herein by reference.

[0027] The type of the pumping mechanism can vary and can be, for example, a multi-finger pumping mechanism. For example, the pumping mechanism can be of the "four-finger" type and includes an upstream blocking element or finger 72, a main pumping element or finger 74, a downstream blocking element or finger 76, and a secondary pumping element or finger 78. The "four-finger" pumping mechanism and the mechanisms used in other linear peristaltic pumps operate by successively pressing on a section of the fluid conduit by means of cam-follower pumping elements (e.g., pumping fingers and valve fingers) 72, 74, 76, and 78, which constitute the four-finger pump assembly. Pressure is applied at successive positions along the conduit, starting at the upstream end of the pumping mechanism and acting downstream. At least one finger is always pressed hard enough to block the conduit. As a practical matter, one finger does not retract from blocking the conduit until the next finger in the sequence has blocked the conduit; thus, there is never a direct fluid path from the fluid source to the patient. The operation of a peristaltic pump including four finger pumps is well known to those skilled in the art and no further operational details are provided here.

[0028] The pump 10 may also include an upstream pressure sensor 80. The upstream pressure sensor is assigned to the flow control device or the pumping mechanism 70 and, in this example, is also provided as an integral part of the pump 10. It is mounted on the flow control device 70 and is located near the upstream of the flow control device. The upstream pressure sensor is located upstream of the flow control device, that is, at a position between the fluid source and the flow control device, such that the correct connection of the fluid source to the correct pump can be verified before any fluid is pumped to the patient.

[0029] The pump 10 also includes a downstream pressure sensor 82, which is located at a downstream position relative to the pumping mechanism. The downstream pressure sensor 82 is mounted on the flow control device 70 and is located near the downstream of the flow control device. The downstream pressure sensor is located downstream of the flow control device, that is, at a position between the patient and the flow control device, so that when connected, the fluid pressure supplied to the downstream infusion line 31 and the pressure infusion device 25 can be determined to verify the perfusion of the fluid before the fluid is pumped to the patient.

[0030] Figure 3AA exploded view of an example pressure infusion device in accordance with various aspects of the present subject matter technology is depicted. The pressure infusion device 25 of the present subject matter technology includes a fluid input end 52 configured to have a first fluid breakthrough backpressure and a fluid output end 54 configured to have a second fluid breakthrough backpressure. The fluid breakthrough backpressure is a fluid pressure at which the fluid flowing through the IV tubing coupled to the pressure infusion device must reach before the fluid will flow through the corresponding input or output end of the pressure infusion device. Although the depicted example is shown as two separate parts, in some embodiments, the pressure infusion device can be a single device.

[0031] According to various embodiments, the pressure infusion device 25 includes two parts: a first part 90 and a second part 100 detachably coupled to the first part. In the depicted example, the first part includes a luer fitting and the second part is an infusion cap whose output is sealed (e.g., embedded therein) with a hydrophobic membrane. The depicted first part 90 is configured to receive and fluidly seal with the second part 100. For example, the first part 90 can include a threaded shaft 92 configured to engage and screw into a threaded receiving cavity 110 of the second part 100 of the pressure infusion device 25. In this regard, when the infusion is complete, the threaded infusion cap 100 can be removed from the first part 90 and disposed of (e.g., thrown away), and replaced with the downstream portion 20 of the infusion device 21 by coupling the threaded connector at the input end of the infusion device 21 to the threaded shaft 92. Although a threaded luer-type connector is shown, it should be understood that the two parts can be coupled and fluidly sealed using other connection mechanisms.

[0032] In some embodiments, the first part 90 includes a one-way check valve 94 that restricts the flow of fluid in one direction 96. The check valve can also create a first fluid breakthrough backpressure such that when the fluid pressure meets the first fluid breakthrough backpressure (e.g., greater than or equal to 30 kPa ± tolerance), the fluid will flow only in the indicated direction 96. In some embodiments, the first part 90 can include an anti-siphon valve having these characteristics.

[0033] The IV infusion cap 100 includes a body 102 having a proximal section 112 and a distal section 114. The lumen 110 of the proximal section 112 is defined to extend into the body 102 at the proximal end 104 and is configured to receive a fluid connector therein. The lumen may extend from the proximal end 104 of the body 102 toward the distal end 106. The longitudinal connector lumen axis 1A is shown to extend between the proximal and distal ends of the body and, when the first and second parts are connected, may extend the entire length of the pressure infusion device 25. The lumen 110 may include a helical ridge 134 formed as threads along the inner surface of the lumen at the proximal section 112. The threads may extend out from or into the inner surface 110 of the cap body. The threads may have a pitch configured to engage the threads of a fluid connector coupled to the IV infusion cap. The ridge 134 may be formed as either a helical ridge or a longitudinal ridge. In some embodiments, the ridge 134 may be any shape configured to engage the fluid connector. In this way, the second part 100 may be fluid-sealed to the first part 90 (e.g., the threaded shaft 92).

[0034] Referring Figure 3B , the second part 100 may include an infusion channel 122 that extends the length of the part 100 from the lumen 110 to the fluid outlet at the distal end 54. At the distal end 54, the second part 100 may include a filter 128 that is embedded in and / or seals the fluid outlet. In some embodiments, the second part 100 may include a groove 130 to receive the filter 128 therein. The groove 130 may extend to the distal end of the cap body 102, and the distal portion 126 of the infusion channel 122 intersects the groove 130. In some embodiments, the IV infusion cap does not include a filter. According to various embodiments, the filter 128 is a hydrophobic filter (or hydrophobic membrane). In some examples, the filter 128 includes a polyethylene material or includes a membrane coated with polyethylene. The filter 128 may be configured to allow gas to move through the filter while preventing liquid from moving through the filter. For example, the filter 128 may be positioned within the infusion channels 122, 126 or coupled to the tip portion of the cap body 102.

[0035] The hydrophobic filter (and / or the infusion channels 122, 126) may be configured such that when the filter is not wetted, the resistance of the filter to air is low (e.g., less than or equal to 1 kPa ± tolerance), while when wetted, the resistance increases (e.g., greater than or equal to 60 kPa ± tolerance). According to various embodiments, the second fluid breakthrough backpressure generated by the second part 100 is greater than the first fluid breakthrough backpressure generated by the first part 90.

[0036] Although the present disclosure describes embodiments of coupling a second portion 100 to a male Luer-type fluid connector 70, it should be understood that the V-perfusion cap can be coupled to other fluid connectors. However, for clarity and conciseness, the present disclosure may primarily refer to male Luer fluid connectors. Additionally, although the present disclosure describes a pressure perfusion device 25 in relation to an IV administration device, it should be understood that the pressure perfusion device 25 can be coupled to other IV fluid delivery devices and systems. However, for clarity and conciseness, the present disclosure will primarily relate to an IV administration device.

[0037] Figure 4A 、 Figure 4B and Figure 4C depicts an example of perfusing an infusion line using a pressure perfusion system of the subject technology. In the depicted example, a large volume infusion pump (LVP) 10 initiates perfusion of a conduit 21 connected to an input end of the disclosed pressure perfusion device 25. In Figure 4A , the pump 10 is activated and presents a user interface that prompts a clinician to begin perfusion. As shown, the user interface 11 displayed on a display screen associated with the pump 10 can provide an alert or warning to disconnect the conduit from the patient and / or downstream venous line or catheter. The clinician ensures that the conduit is disconnected from the patient, and the pressure perfusion device 25 is connected to the distal end of the infusion line, and then activates the controller to begin the infusion. As will be further described, the pump 10 can be configured to begin perfusing the conduit 21 at a first flow rate and then decrease the flow rate as the pressure increases.

[0038] In the depicted example, a first portion 90 of the device 25 (oriented at the top) includes an anti-siphon valve, and a second portion 100 includes a perfusion cap with a hydrophobic membrane 128 that is coupled to a Luer interface of the first portion 90. At this time, gravitational flow of fluid within the conduit may occur; however, no fluid will pass through the first portion 90 of the device 25 due to a first breakthrough backpressure generated by the first portion.

[0039] In Figure 4B , the pump perfuses the conduit 21 at a given flow rate until a perfusion pressure threshold is reached. As previously described, the perfusion pressure threshold is selected to be greater than a first fluid breakthrough backpressure at an input end 52 of the device 25 and less than a second fluid breakthrough backpressure at an output end of the device 25. Before or during the perfusion operation, a downstream pressure sensor 82 of the pump 10 is activated to measure the pressure within the conduit 21. The perfusion operation is initiated, and the user interface 11 indicates that the pump is perfusing and allows the pressure in the conduit to increase beyond the first breakthrough backpressure such that fluid begins to enter a chamber within the device 25, as shown. The pressure can be continuously monitored so that the fluid is not allowed to overcome the second fluid breakthrough backpressure and spill out of the output end 54 of the device 25.

[0040] According to various embodiments, the pump 10 is programmed to perfuse the fluid conduit 21 at a first flow rate during a first time period (e.g., before the pressure reaches a selected threshold), and then perfuse the fluid conduit 21 at a second flow rate until the threshold is met. In some embodiments, when the downstream sensor 82 measures a pressure approaching the selected perfusion pressure threshold, the pump 10 can initiate a faster perfusion (e.g., 300 mL / hr), and then slow down to a slower perfusion (e.g., 100 mL / hr). For example, multiple pressure thresholds can be provided; a first threshold for reducing the perfusion rate (e.g., equal to or just above the first breakthrough backpressure), and a (second) perfusion pressure threshold for terminating the perfusion operation. In some embodiments, the perfusion pressure threshold can be selected as an intermediate value between the first breakthrough backpressure and the second breakthrough backpressure. If the first breakthrough backpressure is 30 kPa and the second breakthrough backpressure is 60 kPa, the perfusion pressure threshold can be selected as 45 kPa.

[0041] In some embodiments, the flow rate can be reduced based on the volume of the chamber within the pressure perfusion device 25. The pump can deliver a first portion of the chamber volume at a higher rate and then a second portion or the remaining portion at a lower rate. For example, if the chamber volume is 7 mL, the pump 10 can deliver the first 4 mL into the chamber at a high flow rate (e.g., 300 mL / hr), and then switch to a lower flow rate (e.g., 100 mL / hr) for the remaining 3 mL. In some embodiments, the rate can be continuously reduced based on the difference between the pressure measured by the sensor 82 and the perfusion pressure threshold.

[0042] In Figure 4C which, when the downstream pressure sensor 82 of the pump 10 detects a pressure that meets the perfusion pressure threshold, the perfusion operation terminates. A notification indicating the completion of the start operation can be displayed on the user interface 11. In the depicted example, when the pressure sensor 82 detects a pressure of 45 kPa, which is the intermediate value between the first breakthrough backpressure of 45 kPa and the second breakthrough backpressure of 60 kPa, the perfusion operation terminates. The pump 10 can dynamically identify the perfusion pressure threshold. For example, the pump 10 can receive information identifying the pressure perfusion device 25. Based on this information, the pump 10 can determine (e.g., look-up table, query service, data storage, etc.) the pressure threshold or range of the pressure perfusion device 25. This ensures that the appropriate perfusion is safely performed, at least in part, by dynamically adjusting the process of the pressure perfusion device 25. Additionally, these features ensure that the resistance from the pressure perfusion device 25 does not inadvertently cause blockages or other pressure-related alarms or errors.

[0043] Thus, priming is automatically accomplished using pump 10. The clinician does not have to estimate the priming volume, nor sit and wait, nor manually start and stop the pump to fill the fluid in the tubing; the fluid automatically stops when the pump senses that the fluid has reached the correct pressure and there is no leakage, for example, at the hydrophobic membrane.

[0044] Figure 5 An example process for automatically priming an infusion line in accordance with various embodiments of the present subject matter is depicted. For purposes of explanation, various blocks of example process 500 are described herein with reference to Figure 1 FIGS. 1 to 4 and the components and / or processes described herein. In some embodiments, one or more of these blocks may be implemented separately from other blocks and by one or more different devices. Additionally, for purposes of explanation, the blocks of example process 500 are described as occurring serially or linearly. However, multiple blocks of example process 500 may occur in parallel. Additionally, the blocks of example process 500 need not be executed in the order shown, and / or one or more of the blocks in example process 500 need not be executed.

[0045] In the depicted example, a pressure priming device 25 (502) is provided. The pressure priming device 25 is configured such that in response to fluid flowing into the pressure priming device, the fluid input end 52 of the pressure priming device has a first fluid breakthrough backpressure, and the fluid output end 54 of the pressure priming device has a second fluid breakthrough backpressure greater than the first fluid breakthrough backpressure. In other words, the fluid input end 52 can permeate fluid at the first fluid breakthrough backpressure, while the fluid output end can permeate fluid at the second fluid breakthrough backpressure. According to various embodiments, the pressure priming device includes a first portion 90 and a second portion 100 coupled together. The first portion 90 includes the fluid input end 52, while the second portion 100 includes the fluid output end 54.

[0046] In some embodiments, the first portion 90 of the pressure priming device 25 may include a one-way valve at the input end to control the directional flow of fluid. For example, the first portion may include an anti-siphon valve, and the second portion may include a priming cap coupled to the Luer fitting of the anti-siphon valve. In this regard, the clinician can utilize an anti-siphon valve and a priming cap having pre-determined backpressure characteristics known to the pump controller or an associated system, as further described below.

[0047] The pump controller (optionally) determines a priming pressure threshold (504) that is greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure. The pump controller may include a microprocessor of pump 10, or a control unit or other computing device associated with pump 10 (e.g., see Figure 6)。In some embodiments, the pump controller determines the perfusion pressure threshold and / or the back pressure by obtaining the perfusion pressure threshold and / or the value of the back pressure from a memory (e.g., on-vehicle or off-vehicle memories 604, 610, or via a network connection 616). In this regard, the back pressure characteristics of the first and second portions can be pre-determined and stored for determining the perfusion pressure threshold. In some embodiments, the perfusion pressure threshold and / or the back pressure can be manually input by a clinician via the user interface of the pump 10 or an associated computing device. In some embodiments, the perfusion pressure threshold can be a pre-determined value obtained from a storage system. In some embodiments, the pump controller can obtain the first and second breakthrough back pressures and then determine the perfusion pressure threshold based on the back pressure. For example, the pump controller can select a perfusion pressure threshold between the first fluid breakthrough back pressure and the second fluid breakthrough back pressure.

[0048] In some embodiments, an identifier associated with the pressure perfusion device is received by the pump controller or a computing device associated with the pump controller. The identifier can be scanned, for example, from a barcode or an electronic identification device pasted or embedded within the pressure perfusion device. A clinician can use a scanning device to scan the identifier, and the controller and / or the computing device can query a server for the first fluid breakthrough back pressure and the second fluid breakthrough back pressure and then obtain them from the results.

[0049] The pump controller initiates perfusion (506) of a fluid conduit connected to the fluid input end of the perfusion pressure device 25. In some embodiments, the pump 10 initiates perfusion by pumping fluid through the conduit at a pre-determined flow rate and allowing the pressure to increase beyond the first fluid breakthrough back pressure until the determined perfusion pressure threshold is reached.

[0050] In some embodiments, the flow rate of perfusion is adjusted (e.g., decreased) according to the difference between the current pressure of the fluid and the perfusion pressure threshold. In some embodiments, before the fluid pressure reaches the perfusion pressure threshold, the pump controller perfuses the fluid conduit at a first flow rate (e.g., 300 mL / hr) for a first time period and then perfuses the fluid conduit at a second flow rate (e.g., 100 mL / hr) lower than the first flow rate for a second time period until the pressure meets the perfusion pressure threshold.

[0051] Then, when the perfusion pressure of the fluid meets the determined perfusion pressure threshold, the pump controller automatically terminates the perfusion of the fluid conduit (508). As described previously, the pump controller can use the downstream pressure sensor 82 to monitor the pressure within the conduit and can monitor more frequently when the pressure becomes greater than a predetermined threshold. When the pressure reaches the determined perfusion pressure threshold, the pump controller can terminate the perfusion operation. According to various embodiments, a user interface 11 generated on a display screen associated with the pump 10 or an associated computing device graphically indicates that perfusion is complete when the fluid pressure of the fluid meets the perfusion pressure threshold (510).

[0052] In some embodiments, the pump controller initiates the perfusion of the fluid conduit at a first flow rate during a first time period before the fluid pressure reaches the perfusion pressure threshold and determines that the fluid pressure does not reach the perfusion pressure threshold within a predetermined time. In response to determining that the fluid pressure does not reach the perfusion pressure threshold within the predetermined time period, a notification indicating perfusion failure can be provided. After completing the perfusion operation, the clinician can remove the second portion 100 of the pressure perfusion device from the first portion 90 of the device 25 and connect the infusion device 20 to begin infusing the fluid to the patient.

[0053] In some embodiments, process 550 can include the pump 10 or the pump controller or an associated computing device, requesting user confirmation that the second portion is coupled to the first portion, initiating the perfusion of process 500 in response to receiving the user confirmation, prompting (e.g., on the user interface 11) the user to remove the second portion after perfusion termination, and causing the pump 10 to pump the fluid through the fluid conduit in response to receiving an indication that the second portion has been removed from the first portion. In some embodiments, the pump 10 or the pump controller or an associated computing device can detect the activation (e.g., selection) of a control element (e.g., a menu item) via the user interface 11 and identify the first and / or second portions 90, 100 based on the activation of the control element (e.g., selecting the portion from a menu), or scan information from a portion of one or more of the first and / or second portions and decode the information to identify the one or more first and / or second portions. In this regard, the perfusion pressure can be determined based on a lookup (e.g., in a database) of the perfusion pressure based on the identified one or more first and / or second portions.

[0054] Many of the example processes 500 and related features and applications described above can also be implemented as a software process that is specified as a set of instructions recorded on a computer-readable storage medium (also referred to as a computer-readable medium) and can be executed automatically (e.g., without user intervention). When these instructions are executed by one or more processing units (e.g., one or more processors, processor cores, or other processing units), they cause the one or more processing units to perform the actions indicated in the instructions. Examples of computer-readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard disk drives, EPROMs, etc. Computer-readable media do not include carrier waves and electronic signals transmitted through wireless or wired connections.

[0055] The term "software" means, in appropriate circumstances, including firmware residing in read-only memory or an application stored in magnetic memory, which can be read into memory for processing by a processor. Additionally, in some embodiments, multiple software aspects of the present subject matter disclosure can be implemented as sub-parts of a larger program while retaining the different software aspects of the present subject matter disclosure. In some embodiments, multiple software aspects can also be implemented as separate programs. Finally, any combination of separate programs that co-implement the software aspects described herein is within the scope of the present subject matter disclosure. In some embodiments, when a software program is installed to run on one or more electronic systems, the software program defines one or more specific machine implementations that implement and execute the operations of the software program.

[0056] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language (including compiled or interpreted languages, declarative or procedural languages) and can be deployed in any form (including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for a computing environment). A computer program can, but does not need to, correspond to a file in a file system. The program can be stored as part of a file that holds other programs or data (e.g., one or more scripts in a markup language document), in a single file dedicated to the program being discussed, or in multiple cooperating files (e.g., files that store one or more modules, subroutines, or portions of code). A computer program can be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0057] Figure 6 is a conceptual diagram showing an example electronic system for automatically priming an infusion line according to various aspects of the present subject matter technology. The electronic system 600 can be used to perform operations related to Figures 1 - 5A computing device associated with software related to one or more parts or steps or components of 500, including but not limited to computing hardware within pump 10 or associated computing devices or associated modules or terminals. The electronic system 600 can be a personal computer or a mobile device, such as a smart phone, a tablet computer, a laptop computer, a PDA, an augmented reality device, a wearable device such as a watch or a wristband or glasses or a combination thereof, or any other touch screen or television with one or more processors embedded therein or coupled thereto, or any other type of computer-related electronic device having a network connection.

[0058] The electronic system 600 can include various types of computer-readable media and interfaces for various other types of computer-readable media. In the depicted example, the electronic system 600 includes a bus 608, one or more processing units 612, a system memory 604, a read-only memory (ROM) 610, a permanent storage device 602, an input device interface 614, an output device interface 606, and one or more network interfaces 616. In some embodiments, the electronic system 600 can include or integrate other computing devices or circuits for the operation of the various components and methods described above.

[0059] The bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 600. For example, the bus 608 communicatively connects one or more processing units 612 with the ROM 610, the system memory 604, and the permanent storage device 602.

[0060] One or more processing units 612 obtain the instructions to be executed and the data to be processed from these different storage units to execute the processes disclosed in this subject matter. In different embodiments, the one or more processing units can be a single processor or a multi-core processor.

[0061] The ROM 610 stores static data and instructions required by one or more processing units 612 of the electronic system and other modules. On the other hand, the permanent storage device 602 is a read-write memory device. This device is a non-volatile storage unit that stores instructions and data even when the electronic system 600 is turned off. Some embodiments of this subject matter use a mass storage device (such as a magnetic disk or an optical disk and its corresponding disk drive) as the permanent storage device 602.

[0062] Other embodiments use a removable storage device (such as a floppy disk, flash drive, and their corresponding disk drives) as the permanent storage device 602. Like the permanent storage device 602, the system memory 604 is a read-write storage device. However, different from the storage device 602, the system memory 604 is a volatile read-write memory such as random access memory. The system memory 604 stores some instructions and data that the processor needs during operation. In some embodiments, the processes disclosed in this subject matter are stored in the system memory 604, the permanent storage device 602, and / or the ROM 610. One or more processing units 612 obtain the instructions to be executed and the data to be processed from these various memory units in order to execute the processes of some embodiments.

[0063] The bus 608 is also connected to the input and output device interfaces 614 and 606. The input device interface 614 enables a user to transfer information to and select commands for the electronic system. Input devices used in conjunction with the input device interface 614 include, for example, an alphanumeric keyboard and a pointing device (also known as a "cursor control device"). The output device interface 606 can display, for example, images generated by the electronic system 600. Output devices used in conjunction with the output device interface 606 include, for example, a printer and a display device such as a cathode ray tube (CRT) or a liquid crystal display (LCD). Some embodiments include a device such as a touch screen that serves as both an input device and an output device.

[0064] In addition, as Figure 6 shown, the bus 608 also couples the electronic system 600 to a network (not shown) through the network interface 616. The network interface 616 can include, for example, a wireless access point (such as Bluetooth or WiFi) or radio circuitry for connecting to a wireless access point. The network interface 616 can also include hardware for connecting a computer to a portion of a computer network, such as a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN, or an intranet, or a network of networks such as the Internet. Any or all components of the electronic system 600 can be used in conjunction with the disclosed subject matter.

[0065] The functions described above can be implemented in computer software, firmware, or hardware. These techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as a mobile device. Processes and logical flows can be executed by one or more programmable processors and one or more programmable logic circuits. General and special purpose computing devices and storage devices can be interconnected through a communication network.

[0066] Some embodiments include electronic components such as microprocessors, memories, and storage, which store computer program instructions in a machine-readable or computer-readable medium (also referred to as a computer-readable storage medium, machine-readable medium, or machine-readable storage medium). Some examples of such computer-readable media include RAM, ROM, read-only optical discs (CD-ROMs), recordable optical discs (CD-Rs), rewritable optical discs (CD-RWs), read-only digital versatile discs (e.g., DVD-ROMs, dual-layer DVD-ROMs), various recordable / rewritable DVDs (e.g., DVD-RAMs, DVD-RWs, DVD+RWs, etc.), flash memories (e.g., SD cards, mini SD cards, micro SD cards, etc.), magnetic and / or solid state drives, read-only and recordable optical discs, holographic discs, any other optical or magnetic medium, and floppy discs. The computer-readable medium can store a computer program executable by at least one one or more processing units and includes an instruction set for performing various operations. Examples of computer programs or computer code include machine code, such as that generated by a compiler, and files that include high-level code executed by a computer, an electronic component, or a microprocessor using an interpreter.

[0067] Although the foregoing discussion has mainly related to microprocessors or multi-core processors that execute software, some embodiments are executed by one or more integrated circuits such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions stored on the circuit itself.

[0068] As used in this specification and any claims of this application, the terms "computer", "server", "processor", and "memory" refer to electronic or other technological devices. These terms do not include a person or a group. For the purposes of this specification, the term "display" or "displaying" means displaying on an electronic device. As used in this specification and any claims of this application, the terms "computer-readable medium" and "computer-readable media" are entirely limited to tangible physical objects that store information in a computer-readable form. These terms do not include any wireless signals, wired download signals, and any other transient signals.

[0069] To provide for interaction with a user, embodiments of the subject matter described in this specification may be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, and a keyboard and a pointing device by which the user may provide input to the computer, such as a mouse or a trackball. Other types of devices may also be used to provide for interaction with the user; for example, feedback provided to the user may be any form of sensory feedback (such as visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input. Additionally, the computer may interact with the user by sending documents to and receiving documents from the device used by the user; for example, by sending a web page to a web browser on a client device of the user in response to a request received from the web browser.

[0070] Embodiments of the subject matter described in this specification may be implemented in a computing system that includes a back-end component, such as a data server, or includes a middleware component, such as an application server, or includes a front-end component, such as a client computer having a graphical user interface or a web browser, by which the user may interact with embodiments of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (such as a communication network). Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), the Internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network).

[0071] The computing system may include a client and a server. The client and the server are typically remote from each other and may interact through a communication network. The relationship of the client and the server arises from computer programs running on respective computers and has a client-server relationship with each other. In some embodiments, the server transmits data (e.g., an HTML page) to the client device (e.g., to display data to and receive user input from a user interacting with the client device). Data generated at the client device (e.g., the result of a user interaction) may be received at the server from the client device.

[0072] Those skilled in the art should understand that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein can be implemented as electronic hardware, computer software, or a combination of both. To illustrate this interchangeability of hardware and software, the various illustrative blocks, modules, elements, components, methods, and algorithms have been described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. The described functionality can be implemented in different ways for each particular application. The various components and blocks can be arranged differently (e.g., arranged in a different order or divided in a different way) without departing from the scope of the claimed subject matter.

[0073] It should be understood that the particular order or hierarchy of steps in the disclosed processes is an illustration of example methods. Based on design preferences, it is understood that the particular order or hierarchy of steps in the processes can be rearranged. Some of the steps can be performed simultaneously. The appended method claims present the elements of the various steps in an example order and are not meant to be limited to the particular order or hierarchy presented.

[0074] The claimed subject matter is illustrated as clauses:

[0075] For convenience, various examples of aspects of this disclosure are described as numbered clauses (1, 2, 3, etc.). These are provided only as examples and do not limit the claimed subject matter. The identification of numbers and reference numerals provided below is for example and illustrative purposes only, and the clauses are not limited by these identifications.

[0076] Clause 1. A system for automatically priming an infusion line, the system comprising: a pressure priming device including: a fluid input end permeable to fluid under a first fluid breakthrough backpressure; a fluid chamber; and a fluid output end permeable to fluid under a second fluid breakthrough backpressure greater than the first fluid breakthrough backpressure; and a pump controller configured to: determine a priming pressure threshold greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure; initiate priming of a fluid line connected to the fluid input end of the pressure priming device with fluid; automatically terminate priming of the fluid line when the priming pressure of the fluid meets the priming pressure threshold; and provide an indication that the fluid line has been primed in response to the fluid meeting the priming pressure threshold.

[0077] Clause 2. The system according to clause 1, wherein the pressure priming device includes a first part and a second part coupled together, the first part including the fluid input end and the second part including the fluid output end.

[0078] Clause 3. The system according to Clause 2, wherein the fluid output end is sealed with a hydrophobic membrane, and wherein the second fluid breakthrough back pressure is based on the characteristics of the hydrophobic membrane.

[0079] Clause 4. The system according to any one of Clauses 1 to 3, wherein the pump controller is further configured to: request confirmation that the second part is coupled to the first part via a user interface; initiate the perfusion in response to receiving the confirmation; after the perfusion terminates, present a prompt to remove the second part via the user interface; detect the removal of the second part after the perfusion terminates; and in response to detecting the removal of the second part, cause the pump to pump fluid through the fluid conduit.

[0080] Clause 5. The system according to Clause 4, wherein the pump controller is further configured to: detect the activation of a control element via the user interface and identify the second part based on the activation of the control element; or scan information from a portion of the second part and decode the information to identify the second part, wherein the pump controller is configured to determine the perfusion pressure including the pump controller being configured to look up the perfusion pressure based on identifying the second part.

[0081] Clause 6. The system according to any one of Clauses 1 to 5, wherein the pump controller is further configured to: receive an identifier associated with the pressure perfusion device; obtain the first fluid breakthrough back pressure and the second fluid breakthrough back pressure from a data store based on the received identifier; and wherein the pump controller is configured to determine the perfusion pressure in response to obtaining the first fluid breakthrough back pressure and the second fluid breakthrough back pressure.

[0082] Clause 7. The system according to any one of Clauses 1 to 6, wherein the pump controller is further configured to: perfuse the fluid conduit at a first flow rate for a first time period before the fluid pressure reaches a determined perfusion pressure threshold; and perfuse the fluid conduit at a second flow rate lower than the first flow rate for a second time period until the pressure meets the determined perfusion pressure threshold.

[0083] Clause 8. The system according to any one of Clauses 1 to 7, wherein the pump controller is further configured to: reduce the flow rate of the perfusion according to the difference between the current pressure of the fluid and the determined perfusion pressure threshold.

[0084] Clause 9. The system according to any one of Clauses 1 to 8, wherein the pump controller is further configured to: initiate perfusion of the fluid pipeline at a first flow rate within a first time period before the fluid pressure reaches the determined perfusion pressure threshold; determine that the fluid pressure does not reach the determined perfusion pressure threshold within a predetermined time period; and in response to determining that the fluid pressure does not reach the determined perfusion pressure threshold within the predetermined time period, provide a notification indicating perfusion failure.

[0085] Clause 10. The system according to any one of Clauses 1 to 9, wherein the pump controller is further configured to: graphically indicate the completion of the perfusion on a display screen when the fluid pressure of the fluid meets the determined perfusion pressure threshold.

[0086] Clause 11. A method for automatically perfusing an infusion line, the method comprising: providing a pressure perfusion device comprising: a fluid input end permeable to fluid under a first fluid breakthrough back pressure; a fluid chamber; and a fluid output end permeable to fluid under a second fluid breakthrough back pressure greater than the first fluid breakthrough back pressure; determining a perfusion pressure threshold greater than the first fluid breakthrough back pressure and less than the second fluid breakthrough back pressure; initiating perfusion of a fluid pipeline connected to the fluid input end of the pressure perfusion device with fluid; automatically terminating perfusion of the fluid pipeline when the perfusion pressure of the fluid meets the determined perfusion pressure threshold; and in response to the fluid meeting the determined perfusion pressure threshold, providing an indication that the fluid pipeline has been perfused.

[0087] Clause 12. The method according to Clause 11, wherein the pressure perfusion device comprises a first part and a second part coupled together, the first part comprising the fluid input end, the second part comprising the fluid output end, and the method further comprises: requesting user confirmation that the second part is coupled to the first part; initiating the perfusion in response to receiving the user confirmation; prompting the user to remove the second part after the perfusion is terminated; and in response to receiving an indication that the second part has been removed from the first part, causing the pump to pump fluid through the fluid pipeline.

[0088] Clause 13. The method according to claim 12, the method further comprising: detecting activation of a control element via a user interface and identifying the second part based on the activation of the control element; or scanning information from a portion of the second part and decoding the information to identify the second part, wherein determining the perfusion pressure comprises looking up the perfusion pressure based on identifying the second part.

[0089] Clause 14. The method according to any one of Clauses 11 to 13 further includes: receiving an identifier associated with the pressure perfusion device; determining the first fluid breakthrough back pressure and the second fluid breakthrough back pressure based on the received identifier; and wherein the pump controller is configured to determine the perfusion pressure in response to obtaining the first fluid breakthrough back pressure and the second fluid breakthrough back pressure.

[0090] Clause 15. The method according to any one of Clauses 11 to 14 further includes: perfusing the fluid pipeline at a first flow rate within a first time period before the fluid pressure reaches the determined perfusion pressure threshold; and perfusing the fluid pipeline at a second flow rate lower than the first flow rate within a second time period until the pressure meets the determined perfusion pressure threshold.

[0091] Clause 16. The method according to any one of Clauses 11 to 15 further includes: reducing the flow rate of the perfusion according to the difference between the current pressure of the fluid and the determined perfusion pressure threshold.

[0092] Clause 17. The method according to any one of Clauses 11 to 16 further includes: starting to perfuse the fluid pipeline at a first flow rate within a first time period before the fluid pressure reaches the determined perfusion pressure threshold; determining that the fluid pressure does not reach the determined perfusion pressure threshold within a predetermined time period; and in response to determining that the fluid pressure does not reach the determined perfusion pressure threshold within the predetermined time period, providing a notification indicating that the perfusion has failed.

[0093] Clause 18. The method according to any one of Clauses 11 to 17 further includes: when the fluid pressure of the fluid meets the determined perfusion pressure threshold, graphically indicating on the display screen that the perfusion is completed.

[0094] Clause 19. The method according to any one of Clauses 11 to 18, wherein providing the pressure perfusion device includes: coupling a first part of the pressure perfusion device and a second part of the pressure perfusion device together, the first part including a fluid input end and the second part including a fluid output end.

[0095] Clause 20. A non-transitory computer-readable medium storing instructions which, when executed, perform operations including: identifying a pressure perfusion device including a fluid input end permeable to fluid under a first fluid breakthrough back pressure and a fluid output end permeable to fluid under a second fluid breakthrough back pressure greater than the first fluid breakthrough back pressure; determining a perfusion pressure threshold greater than the first fluid breakthrough back pressure and less than the second fluid breakthrough back pressure; initiating perfusion of a fluid conduit connected to the fluid input end of the pressure perfusion device with fluid; automatically terminating perfusion of the fluid conduit when the perfusion pressure of the fluid meets the determined perfusion pressure threshold; and providing an indication that the fluid conduit has been perfused in response to the fluid meeting the determined perfusion pressure threshold.

[0096] Further consider:

[0097] It should be understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of example methods. Based on design preferences, it is understood that the specific order or hierarchy of steps in the process can be rearranged. Some of the steps can be performed simultaneously. The appended method claims present the elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0098] The foregoing description is provided to enable a person skilled in the art to practice the various aspects described herein. The foregoing description provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, where the elements in the singular form are not meant to mean "one and only one" unless specifically stated otherwise, but rather are meant to mean "one or more". Unless otherwise stated, the term "some" means one or more. Masculine pronouns (such as "his") include feminine and neuter (such as "her" and "its"), and vice versa. Headings and subheadings (if any) are used for convenience only and do not limit the invention described herein.

[0099] The predicate words "configured to", "operable to", and "programmed to" do not imply any specific tangible or intangible modification to the subject matter but are intended to be used interchangeably. For example, a processor or component configured to monitor and control an operation may also mean a processor programmed to monitor and control the operation, or a processor operable to monitor and control the operation. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute code or a processor operable to execute code.

[0100] As used herein, the term "automatically" can include the performance of a computer or machine without user intervention; e.g., by instructions or other initiation mechanisms responsive to a predicate action of the computer or machine. The term "example" is used herein to mean "serving as an example or illustration". Any aspect or design described herein as an "instance" is not necessarily to be construed as superior or better than other aspects or designs.

[0101] Phrases such as "aspect" do not mean that the aspect is essential to the claimed subject matter nor that the aspect is applicable to all configurations of the claimed subject matter. Disclosure related to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. Phrases such as "aspect" may refer to one or more aspects, and vice versa. Phrases such as "embodiment" do not mean that such an embodiment is essential to the claimed subject matter nor that such an embodiment is applicable to all configurations of the claimed subject matter. Disclosure related to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. Phrases such as "embodiment" may refer to one or more embodiments, and vice versa. Phrases such as "configuration" do not mean that such a configuration is essential to the claimed subject matter nor that such a configuration is applicable to all configurations of the claimed subject matter. Disclosure related to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. Phrases such as "configuration" may refer to one or more configurations, and vice versa.

[0102] As used herein, a "user interface" (also referred to as an interactive user interface, graphical user interface, or UI) may refer to a web-based interface that includes data fields and / or other control elements for receiving input signals or providing electronic information and / or for providing information to a user in response to any received input signal. The control elements may include dials, buttons, icons, selectable areas, or other perceivable markers presented via the UI that initiate a data exchange of the device presenting the UI when interacted with (e.g., clicked, touched, selected, etc.). The UI may be implemented in whole or in part using technologies such as HyperText Markup Language (HTML), FLASH TM , JAVA TM , NET TM , C, C++, web services, or Rich Site Summary (RSS), etc. In some embodiments, the UI may be included in a stand-alone client (e.g., thick client, fat client) that is configured to communicate (e.g., send or receive data) according to one or more of the aspects described. The communication may be to or from a medical device or server with which it communicates.

[0103] As used herein, the terms "determine" or "determining" include a variety of actions. For example, "determining" can include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. via a hardware component without user intervention. Additionally, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. via a hardware component without user intervention. "Determining" can include parsing, selecting, picking, establishing, etc. via a hardware component without user intervention.

[0104] As used herein, the terms "supply" or "providing" encompass a variety of actions. For example, "providing" may include storing a value at a location in a storage device for subsequent retrieval, directly sending the value to a recipient via at least one wired or wireless communication medium, sending or storing a reference to the value, and so on. "Providing" can also include encoding, decoding, encrypting, decrypting, validating, verifying, etc. via a hardware component.

[0105] As used herein, the term "message" includes various formats for conveying (e.g., sending or receiving) information. Messages can include machine-readable aggregations of information, such as XML documents, fixed-field messages, comma-separated messages, JSON, custom protocols, etc. In some embodiments, a message can include a signal for transmitting one or more representations of information. Although recited in the singular, it is understood that messages can be written, sent, stored, received, etc. in multiple parts.

[0106] As used herein, the terms "selectively" or "selective" can include a variety of actions. For example, a "selective" process can include determining one option from multiple options. A "selective" process can include one or more of the following: dynamically determined input, pre-configured input, or user-initiated input for making a determination. In some embodiments, n input switches can be included to provide a selective function, where n is the number of inputs for making a selection.

[0107] As a user herein, the terms "correspond to" or "corresponding" include a structural, functional, quantitative, and / or qualitative correlation or relationship between two or more objects, data sets, information, etc., preferably where the corresponding relationship or relationship can be used to interpret one or more of the two or more objects, data sets, information, and / or the like to make it appear the same or equal. One or more of a threshold, range of values, fuzzy logic, pattern matching, machine learning evaluation model, or a combination thereof can be used to evaluate the corresponding relationship.

[0108] In any embodiment, the data generated or detected can be forwarded to a "remote" device or location, where "remote" refers to a location or device other than the location or device where the program is executed. For example, a remote location can be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Thus, when an object is indicated as "remote" from another object, this means that the two objects can be in the same room but separated, or at least in different rooms or different buildings, and can be at least one mile, ten miles, or at least one hundred miles apart. "Transmitting" information means transmitting the data representing the information as an electrical signal through a suitable communication channel (e.g., a private or public network). "Forwarding" an object means any means of moving the object from one location to the next, whether by physically transporting the object or otherwise (where possible), and in the case of data at least, includes physically transporting the medium carrying the data or transmitting the data. Examples of communication media include radio or infrared transmission channels and network connections to another computer or networked device, as well as the Internet or including email transmissions and information recorded on websites, etc.

Claims

1. A system for automatically perfusing an infusion line, the system comprising: A pressure perfusion device, the pressure perfusion device comprising: A fluid input end that is permeable to fluid under a first fluid breakthrough backpressure; A fluid chamber; and A fluid output end that is permeable to fluid under a second fluid breakthrough backpressure greater than the first fluid breakthrough backpressure; and A pump controller configured to: Determine a perfusion pressure threshold greater than the first fluid breakthrough backpressure and less than the second fluid breakthrough backpressure; Initiate perfusion of a fluid pipeline connected to the fluid input end of the pressure perfusion device with fluid; Automatically terminate perfusion of the fluid pipeline when the perfusion pressure of the fluid meets the perfusion pressure threshold; and In response to the fluid meeting the perfusion pressure threshold, provide an indication that the fluid pipeline has been perfused.

2. The system according to claim 1, wherein The pressure perfusion device includes a first part and a second part coupled together, the first part includes the fluid input end, and the second part includes the fluid output end.

3. The system according to claim 2, wherein, The fluid output end is sealed with a hydrophobic membrane, and wherein the second fluid breakthrough backpressure is based on the characteristics of the hydrophobic membrane.

4. The system according to claim 2 or claim 3, wherein The pump controller is further configured to: Request confirmation via a user interface that the second part is coupled to the first part; Initiate the perfusion in response to receiving the confirmation; After the perfusion is terminated, present a prompt to remove the second part via the user interface; Detect the removal of the second part after the perfusion is terminated; And In response to detecting the removal of the second part, cause the pump to pump fluid through the fluid pipeline.

5. The system according to any one of claims 2 to 4, wherein The pump controller is further configured to: Detect activation of a control element via the user interface and identify the second part based on the activation of the control element; or Scan information from a part of the second part and decode the information to identify the second part, Wherein the pump controller is configured to determine the perfusion pressure including the pump controller being configured to look up the perfusion pressure based on identifying the second part.

6. The system according to any one of claims 1 to 5, wherein, The pump controller is further configured to: Receive an identifier associated with the pressure perfusion device; Obtain the first fluid breakthrough backpressure and the second fluid breakthrough backpressure from a data store based on the received identifier; And Wherein the pump controller is configured to determine the perfusion pressure in response to obtaining the first fluid breakthrough backpressure and the second fluid breakthrough backpressure.

7. The system according to any one of claims 1 to 6, wherein The pump controller is further configured to: Perfuse the fluid pipeline at a first flow rate within a first time period before the fluid pressure reaches the determined perfusion pressure threshold; and Perfuse the fluid pipeline at a second flow rate lower than the first flow rate within a second time period until the pressure meets the determined perfusion pressure threshold.

8. The system according to any one of claims 1 to 7, wherein, The pump controller is further configured to: Reduce the flow rate of the perfusion according to the difference between the current pressure of the fluid and the determined perfusion pressure threshold.

9. The system according to any one of claims 1 to 8, wherein, The pump controller is further configured to: Initiate perfusion of the fluid pipeline at a first flow rate within a first time period before the fluid pressure reaches the determined perfusion pressure threshold; Determine that the fluid pressure does not reach the determined perfusion pressure threshold within a predetermined period of time; And In response to determining that the fluid pressure does not reach the determined perfusion pressure threshold within the predetermined period of time, provide a notification indicating perfusion failure.

10. The system according to any one of claims 1 to 9, wherein The pump controller is further configured to: When the fluid pressure of the fluid meets the determined perfusion pressure threshold, graphically indicate the completion of the perfusion on the display screen.

11. A method for automatically perfusing an infusion line, the method comprising: Provide a pressure perfusion device, the pressure perfusion device comprising: A fluid input end permeable to fluid under a first fluid breakthrough back pressure; A fluid chamber; and A fluid output end permeable to fluid under a second fluid breakthrough back pressure greater than the first fluid breakthrough back pressure; Determine a perfusion pressure threshold greater than the first fluid breakthrough back pressure and less than the second fluid breakthrough back pressure; Initiate perfusion of a fluid conduit connected to the fluid input end of the pressure perfusion device with fluid; Automatically terminate perfusion of the fluid conduit when the perfusion pressure of the fluid meets the determined perfusion pressure threshold; and In response to the fluid meeting the determined perfusion pressure threshold, provide an indication that the fluid conduit has been perfused.

12. The method according to claim 11, wherein, The pressure perfusion device includes a first part and a second part coupled together, the first part includes the fluid input end, the second part includes the fluid output end, the method further comprising: Request user confirmation that the second part is coupled to the first part; Initiate the perfusion in response to receiving the user confirmation; Prompt the user to remove the second part after the perfusion is terminated; and In response to receiving an indication that the second part has been removed from the first part, cause the pump to pump fluid through the fluid conduit.

13. The method according to claim 12, the method further comprising: Detect activation of a control element via the user interface and identify the second part based on the activation of the control element; Or Scan information from a part of the second part and decode the information to identify the second part, Wherein determining the perfusion pressure includes looking up the perfusion pressure based on identifying the second part.

14. The method according to any one of claims 11 to 13, further comprising: Receive an identifier associated with the pressure perfusion device; Determine the first fluid breakthrough back pressure and the second fluid breakthrough back pressure based on the received identifier; And Wherein the pump controller is configured to determine the perfusion pressure in response to obtaining the first fluid breakthrough back pressure and the second fluid breakthrough back pressure.

15. The method according to any one of claims 11 to 14, further comprising: Perfuse the fluid conduit at a first flow rate within a first period of time before the fluid pressure reaches the determined perfusion pressure threshold; And Perfuse the fluid conduit at a second flow rate lower than the first flow rate within a second period of time until the pressure meets the determined perfusion pressure threshold.

16. The method according to any one of claims 11 to 15, further comprising: Reduce the flow rate of the perfusion based on the difference between the current pressure of the fluid and the determined perfusion pressure threshold.

17. The method according to any one of claims 11 to 16, further comprising: Before the fluid pressure reaches the determined perfusion pressure threshold, initiate perfusion of the fluid conduit at a first flow rate during a first time period; Determine that the fluid pressure does not reach the determined perfusion pressure threshold within a predetermined time period; And In response to determining that the fluid pressure does not reach the determined perfusion pressure threshold within the predetermined time period, provide a notification indicating perfusion failure.

18. The method according to any one of claims 11 to 17, further comprising: When the fluid pressure of the fluid satisfies the determined perfusion pressure threshold, graphically indicate on a display screen that the perfusion is complete.

19. The method according to any one of claims 11 to 18, wherein providing the pressure perfusion device comprises: Couple a first portion of the pressure perfusion device and a second portion of the pressure perfusion device together, the first portion including the fluid input end and the second portion including the fluid output end.

20. A non-transitory computer-readable medium having instructions stored thereon, the instructions when executed perform operations, the operations including: Identify a pressure perfusion device, the pressure perfusion device including: A fluid input end permeable to fluid under a first fluid breakthrough back pressure; and A fluid output end permeable to fluid under a second fluid breakthrough back pressure greater than the first fluid breakthrough back pressure; Determine a perfusion pressure threshold greater than the first fluid breakthrough back pressure and less than the second fluid breakthrough back pressure; Initiate perfusion of a fluid conduit connected to the fluid input end of the pressure perfusion device with fluid; Automatically terminate perfusion of the fluid conduit when the perfusion pressure of the fluid satisfies the determined perfusion pressure threshold; and In response to the fluid satisfying the determined perfusion pressure threshold, provide an indication that the fluid conduit has been perfused.

Images