Fluid infusion systems are configured to inject a fluid, such as therapeutic fluid, into a patient. Such systems are sometimes manually controlled by a user based upon the user's review or interaction with anatomical images obtained by an imaging modality. This can result in an inexact or ineffective dose of the therapeutic to the patient. In view of this, there is a need for systems and methods for controlling the infusion of fluids to a patient based on imaging data.
Disclosed are systems and methods for controlling or managing an injection of fluid into the brain such as using imaging data. A fluid injection device or delivery device, such as a catheter, is coupled to a patient's brain such that the fluid injection device forms a fluid pathway (such as via transcranial pathway) to at least one target location within the brain. The fluid injection device is connected to a fluid transfer device, such a syringe, containing a therapeutic fluid. The syringe is further connected to a fluid pump that is configured to cause fluid to be forcibly injected into the brain via the syringe and the catheter.
The disclosed systems and methods enable the pump to be controlled manually or automatically based on imaging data. Such a configuration simplifies the workflow relative to existing systems and provides more consistent clinical results. This can result in a reduction in dosing time and can increase coverage amount, and further decrease a volume of therapeutic needed to properly treat the patient.
The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.
Before the present subject matter is further described, it is to be understood that this subject matter described herein is not limited to particular embodiments described, as such may of course vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. Unless defined otherwise, all technical terms used herein have the same meaning as commonly understood by one skilled in the art to which this subject matter belongs.
In the illustrated embodiment, the pump assembly 110 includes a screen for display any of a variety of information as well as one or more actuators, such as buttons, configured to permit the user to input predetermined dosing parameters (i.e. volume and flow rate) or manually start/stop the flow of therapeutic. The screen is configured to present a user interface for interaction by the user. In an implementation, the user interface may be disabled when the pump is being automatically controlled via the closed loop system described below with reference to
With reference still to
The closed loop control configuration may operate in real time. Alternatively, the closed loop control configuration may be delayed based wherein changes to control of the pump assembly may be delayed for a period of time after relevant data is received. The delay may be based on hardware and software limitations or may be intentionally introduced for safety or other reasons. Moreover, the system may incorporate safety limits and parameters. Such limits and parameters may be entered manually by a user or may be automatically derived from drug libraries, volume calculations or other parameters. Safety limits based on the ability of the software to detect leaked infusate, catheter backflow, and other limits may be specified by the user before infusions. For example, the system is configured to inhibit, change, stop, increase or otherwise adjust fluid flow to the patient based on whether safety limits thresholds are reached.
In
The computer 235 includes software configured to cause the pump assembly 210 or any other aspect of the system to manually or automatically identify an anatomical volume of interest in the brain based upon the image data. For example, a specific area of the brain may be identified for monitoring infusion of fluid thereto. The software is further configured to generate an image and create boundary lines on the image around at least one anatomical region or structure of interest and present an image of such boundary lines such as on a display or on a hard copy of the image. The boundary lines may be automatically generated by the software or a user can manually provide data related to the boundary lines such as by drawing boundary lines on an image. The software may also manually or automatically detect the location, amount, flow rate or other feature of therapeutic (such as a fluid therapeutic) in the brain.
The software is further configured to cause the system, such as via an instruction via software to the computer, to calculate infused volume of therapeutic and proportion of therapeutic coverage. This information can be used to control the pump assembly 210, such as to manually (via a user command) or automatically turn the pump on, turn the pump off, or adjust the flowrate of fluid infused by the pump.
The software is further configured to identify other aspects of the anatomy, such as for example porosity, hydraulic conductivity, and other physical characteristics of the anatomy (e.g., in or around the region of interest) and the therapeutic. Patient-specific physical characteristics of targeted anatomy may be computed from multi-modal imaging (such as DWI, fMRI, PET) registered and fused in the space of the structural data. This information can be used to identify and modify the flow rate to provide optimized coverage, infused volume, dosing time, etc. The software is configured to cause the pump to optimize a flow rate based on imaging data, infused volume, backflow, target location or an aspect of the anatomy (such as porosity).
The software is further configured to identify optimum or enhanced dosing location of the anatomy for delivery of the therapeutic. This can be determined using physics-based simulation or geometric parameters (e.g. centroid or centroids), diffusion characteristics (e.g. porosity, viscosity) and a combination of other factors. The system can then automatically cause the catheter 120 to be positioned (such as via electromechanical components) to coincide with one or more optimum infusion locations.
If multiple target locations for delivery of therapeutic are used, then they may or may not be collinear. The system may incorporate a drive mechanism that allows for automatic adjustment of the position of the catheter in the anatomy. The dosing may be performed only at discrete points or dosing may continue concurrent to catheter movement.
The catheter 120 may vary in structure. For example, the catheter may include a single lumen opening or multiple lumen openings. The catheter may include a single lumen or multiple lumens. If the catheter includes multiple lumens then they may all be controlled together or may include individual controls per lumen.
As shown in
The memory 920 is a computer readable medium such as volatile or non-volatile that stores information within the computing system 900. The memory 920 can store data structures representing configuration object databases, for example. The storage device 930 is capable of providing persistent storage for the computing system 900. The storage device 930 can be a floppy disk device, a digital cloud, a hard disk device, an optical disk device, or a tape device, or other suitable persistent storage means. The input/output device 940 provides input/output operations for the computing system 900. In some implementations of the current subject matter, the input/output device 940 includes a keyboard and/or pointing device. In various implementations, the input/output device 940 includes a display unit for displaying graphical user interfaces.
According to some implementations of the current subject matter, the input/output device 940 can provide input/output operations for a network device. For example, the input/output device 940 can include Ethernet ports or other networking ports to communicate with one or more wired and/or wireless networks, Bluetooth or digital cloud system (e.g., a local area network (LAN), a wide area network (WAN), the Internet).
In some implementations of the current subject matter, the computing system 900 can be used to execute various interactive computer software applications that can be used for organization, analysis and/or storage of data in various (e.g., tabular) format (e.g., Microsoft Excel®, and/or any other type of software). Alternatively, the computing system 900 can be used to execute any type of software application. These applications can be used to perform various functionalities, e.g., planning functionalities (e.g., generating, managing, editing of spreadsheet documents, word processing documents, and/or any other objects, etc.), computing functionalities, communications functionalities, etc. The applications can include various add-in functionalities, plug ins, or can be standalone computing products and/or functionalities. Upon activation within the applications, the functionalities can be used to generate the user interface provided via the input/output device 940. The user interface can be generated and presented to a user by the computing system 900 (e.g., on a computer screen monitor, etc.). The user interface can be integrated with other devices or virtual ecosystems.
One or more aspects or features of the subject matter described herein can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs, field programmable gate arrays (FPGAs) computer hardware, firmware, software, and/or combinations thereof. These various aspects or features can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. The programmable system or computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
These computer programs, which can also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid-state memory or a magnetic hard drive or any equivalent storage medium. The machine-readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example, as would a processor cache or other random-access memory associated with one or more physical processor cores.
To provide for interaction with a user, one or more aspects or features of the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) or a light emitting diode (LED) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, speech, or tactile input. Other possible input or output devices include touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive track pads, joy sticks, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, image scanners including computer topography and magnetic resonance (MR) imaging systems and the like.
In the descriptions above and in the claims, phrases such as “at least one of” or “one or more of” may occur followed by a conjunctive list of elements or features. The term “and/or” may also occur in a list of two or more elements or features. Unless otherwise implicitly or explicitly contradicted by the context in which it used, such a phrase is intended to mean any of the listed elements or features individually or any of the recited elements or features in combination with any of the other recited elements or features. For example, the phrases “at least one of A and B;” “one or more of A and B;” and “A and/or B” are each intended to mean “A alone, B alone, or A and B together.” A similar interpretation is also intended for lists including three or more items. For example, the phrases “at least one of A, B, and C;” “one or more of A, B, and C;” and “A, B, and/or C” are each intended to mean “A alone, B alone, C alone, A and B together, A and C together, B and C together, or A and B and C together.” Use of the term “based on,” above and in the claims is intended to mean, “based at least in part on,” such that an unrecited feature or element is also permissible.
While this specification contains many specifics, these should not be construed as limitations on the scope of an invention that is claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Only a few examples and implementations are disclosed. Variations, modifications and enhancements to the described examples and implementations and other implementations may be made based on what is disclosed.
The present application claims priority to U.S. Provisional Application No. 63/583,360, filed on Sep. 18, 2023, and entitled “CLOSED LOOP INFUSION PUMP CONTROL,” the entirety of which is incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
63583360 | Sep 2023 | US |