Systems, methods, and computer program products for operating fluid injection systems

Abstract

In some embodiments, a system for operating a fluid injection system may include at least one processor to receive patient data related to a patient undergoing a fluid injection procedure, in one embodiment, at least one parameter of an injection protocol for a fluid injection procedure is automatically generated based on patient data and independently of an input associated with a dose of a medical fluid for the fluid injection procedure received through a user interface associated with a fluid injection system performing the fluid injection procedure, when the at least one parameter is automatically generated, the at least one processor is configured to determine a dose of the medical fluid for the fluid injection procedure and provide the at least one parameter of the injection protocol to the fluid injection system. Methods and computer program products are also disclosed.

Description

Technical Field

[0001] This disclosure generally relates to control systems and / or devices associated with medical devices, and in some non-limiting embodiments, to systems, methods, and computer program products for operating fluid injection systems. Background Technology

[0002] Infusion devices, such as fluid infusion devices (e.g., medical fluid delivery devices), can be used by medical practitioners, such as physicians, in medical diagnostic and / or medical treatment procedures. For example, a medical practitioner may use a fluid infusion device to infuse one or more medical fluids into a patient. Fluid infusion devices can be used to pressurize and infuse medical fluids, such as contrast materials (e.g., contrast agents, radioactive contrast agents, contrast media, etc.) and / or irrigating agents (e.g., saline solution), in medical imaging procedures such as angiography, computed tomography (CT), ultrasound, magnetic resonance imaging (MRI), and positron emission tomography (PET)). In some cases, fluid infusion devices are designed to deliver a specific volume of medical fluid into a patient at one or more flow rates. Summary of the Invention

[0003] Therefore, systems, methods, and computer program products for operating fluid injection systems are provided, which improve the efficiency and accuracy of generating injection protocols for delivering medical fluids to patients during fluid injection procedures.

[0004] Further non-restrictive implementation agreements or aspects are set forth in the following numbered clauses:

[0005] Clause 1. A system for operating a fluid infusion system, comprising: at least one processor programmed or configured to: receive patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient's weight; automatically generate at least one parameter for an infusion protocol for the fluid infusion procedure based on the patient data and independently of input associated with a dose of a medical fluid for the fluid infusion procedure received via a user interface associated with the fluid infusion system performing the fluid infusion procedure, wherein, when the at least one parameter is automatically generated, the at least one processor is programmed or configured to: determine a dose of the medical fluid for the fluid infusion procedure based on: the patient's weight, the concentration of the medical fluid, the anatomical region of the patient in which the fluid infusion procedure will be performed, or any combination thereof; and provide at least one parameter of the infusion protocol to the fluid infusion system.

[0006] Clause 2. The system according to Clause 1 further includes a display unit, wherein the at least one processor is further programmed or configured to: display a plurality of patient identifiers in a user interface on the display unit; and receive a selection of a patient identifier among the plurality of patient identifiers via the user interface; wherein, when receiving the patient data, the at least one processor is programmed or configured to: receive the patient data based on the selection of the patient identifier received via the user interface.

[0007] Clause 3. The system according to Clause 1 or 2, wherein, when the patient data is received, the at least one processor is programmed or configured to receive the patient data from user input via a user interface displayed on a display unit.

[0008] Clause 4. The system according to any one of Clauses 1 to 3, wherein the patient data associated with the patient undergoing the fluid injection procedure corresponds to the patient's patient record stored in a hospital information system, and wherein the at least one processor is further programmed or configured to: transmit a unique identifier associated with the patient's patient record to the hospital information system; and wherein, when the patient data is received, the at least one processor is programmed or configured to: receive the patient data from the hospital information system.

[0009] Clause 5. The system according to any one of Clauses 1 to 4, wherein, when at least one parameter of the injection protocol for the fluid injection procedure is automatically generated, the at least one processor is further programmed or configured to: determine a first dose of medical fluid for a first injection phase of the fluid injection procedure; determine a first flushing phase of the fluid injection procedure, wherein the first flushing phase includes a first injection of saline fluid; determine a second dose of medical fluid for a second injection phase of the fluid injection procedure based on at least one of the following: the patient's weight, the concentration of the medical fluid, the anatomical region, or any combination thereof; and determine a second flushing phase of the fluid injection procedure, wherein the second flushing phase includes a second injection of saline fluid.

[0010] Clause 6. The system according to any one of Clauses 1 to 5, wherein the at least one processor is further programmed or configured to cause the fluid injection procedure to be executed in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

[0011] Clause 7. The system according to any one of Clauses 1 to 6, wherein, when at least one parameter of an injection protocol for the fluid injection procedure is automatically generated, the at least one processor is programmed or configured to: determine a first flow rate of the medical fluid for the first injection phase based on the concentration of the medical fluid and the anatomical region; and determine a second flow rate of the medical fluid for the second injection phase based on the concentration of the medical fluid and the anatomical region.

[0012] Clause 8. The system according to any one of Clauses 1 to 7 further includes a display unit, wherein the at least one processor is further programmed or configured to: display a plurality of anatomical region identifiers in a user interface on the display unit; and receive selection of an anatomical region identifier among the plurality of anatomical region identifiers via the user interface; wherein, when at least one parameter of an injection protocol for the fluid injection procedure is automatically generated, the at least one processor is programmed or configured to: determine the type of medical fluid, the concentration of the medical fluid, and the anatomical region of the patient in which the fluid injection procedure will be performed, based on the selection of the anatomical region identifier received via the user interface.

[0013] Clause 9. A method for operating a fluid infusion system, comprising: receiving, with at least one processor, patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient's weight; automatically generating, with at least one processor, at least one parameter of an infusion protocol for the fluid infusion procedure, and independently of input associated with a dose of a medical fluid for the fluid infusion procedure received via a user interface associated with the fluid infusion system, the fluid infusion system performing the fluid infusion procedure based on the patient data, wherein automatically generating the at least one parameter comprises: determining a dose of the medical fluid for the fluid infusion procedure based on: the patient's weight, the concentration of the medical fluid, or the anatomical region of the patient in which the fluid infusion procedure will be performed; or any combination thereof; and providing at least one parameter of the infusion protocol with at least one processor.

[0014] Clause 10. The method according to Clause 9 further includes: displaying a plurality of patient identifiers in a user interface on a display unit; and receiving a selection of a patient identifier among the plurality of patient identifiers via the user interface; wherein receiving the patient data includes: receiving the patient data based on the selection of the patient identifier received via the user interface.

[0015] Clause 11. The method according to Clause 9 or 10, wherein the patient data associated with the patient undergoing the fluid injection procedure corresponds to the patient's patient record stored in a hospital information system, and wherein the method further comprises: transmitting a unique identifier associated with the patient's patient record to the hospital information system; and wherein receiving the patient data comprises: receiving the patient data from the hospital information system.

[0016] Clause 12. The method according to any one of Clauses 9 to 11, wherein receiving patient data comprises: receiving the patient data from user input via a user interface displayed on a display unit.

[0017] Clause 13. The method according to any one of Clauses 9 to 12, wherein automatically generating at least one parameter of the injection protocol for the fluid injection procedure further comprises: determining a first dose of medical fluid for a first injection phase of the fluid injection procedure; determining a first flushing phase of the fluid injection procedure comprising a first injection of saline fluid; determining a second dose of medical fluid for a second injection phase of the fluid injection procedure based on at least one of the following: the patient's weight, the concentration of the medical fluid, or the anatomical region; and determining a second flushing phase comprising a second injection of the saline fluid.

[0018] Clause 14. The method according to any one of Clauses 9 to 13 further comprises: performing the fluid injection procedure in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

[0019] Clause 15. The method according to any one of Clauses 9 to 14, wherein automatically generating at least one parameter of the injection protocol for the fluid injection procedure further comprises: determining a first flow rate of the medical fluid for the first injection phase based on the concentration of the medical fluid and the anatomical region of the patient in which the fluid injection procedure will be performed; and determining a second flow rate of the medical fluid for the second injection phase based on the concentration of the medical fluid and the anatomical region of the patient in which the fluid injection procedure will be performed.

[0020] Clause 16. The method according to any one of Clauses 9 to 15, further comprising: displaying a plurality of anatomical region identifiers in a user interface on a display unit; and receiving, via the user interface, a selection of an anatomical region identifier among the plurality of anatomical region identifiers; wherein automatically generating at least one parameter of an injection protocol for the fluid injection procedure comprises: determining, based on the selection of the anatomical region identifier received via the user interface, the medical fluid, the concentration of the medical fluid, and the anatomical region of the patient in which the fluid injection procedure will be performed.

[0021] Clause 17. A computer program product for operating a fluid infusion system, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, which, when executed by at least one processor, cause the at least one processor to: receive patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient's weight; automatically generate at least one parameter for an infusion protocol for the fluid infusion procedure based on the patient data and independently of input associated with a dose of medical fluid for the fluid infusion procedure received via a user interface associated with the fluid infusion system performing the fluid infusion procedure, wherein the one or more instructions causing the at least one processor to automatically generate the at least one parameter cause the at least one processor to: determine the dose of medical fluid for the fluid infusion procedure based on at least one of: the patient's weight, the concentration of the medical fluid, or the anatomical region of the patient in which the fluid infusion procedure will be performed; and provide at least one parameter of the infusion protocol to the fluid infusion system.

[0022] Clause 18. The computer program product according to Clause 17, wherein the one or more instructions further cause the at least one processor to: display a plurality of patient identifiers in a user interface on a display unit; and receive a selection of a patient identifier among the plurality of patient identifiers via the user interface; wherein the one or more instructions causing the at least one processor to receive the patient data cause the at least one processor to: receive the patient data based on the selection of the patient identifier received via the user interface.

[0023] Clause 19. A computer program product according to Clause 17 or 18, wherein the patient data associated with the patient undergoing the fluid injection procedure corresponds to the patient's patient record stored in a hospital information system, and wherein the one or more instructions further cause the at least one processor to: transmit a unique identifier associated with the patient's patient record to the hospital information system; and wherein the one or more instructions causing the at least one processor to receive the patient data cause the at least one processor to: receive the patient data from the hospital information system.

[0024] 20. A computer program product according to any one of clauses 17 to 19, wherein the one or more instructions that cause the at least one processor to automatically generate at least one parameter of an injection protocol for the fluid injection procedure further cause the at least one processor to: determine a first dose of medical fluid for a first injection phase of the fluid injection procedure; determine a first flushing phase of the fluid injection procedure, wherein the first flushing phase includes a first injection of saline fluid; determine a second dose of medical fluid for a second injection phase of the fluid injection procedure based on at least one of the following: the patient's weight, the concentration of the medical fluid, the anatomical region, or any combination thereof; and determine a second flushing phase of the fluid injection procedure, wherein the second flushing phase includes a second injection of saline fluid; and wherein the one or more instructions further cause the at least one processor to: execute the fluid injection procedure in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

[0025] These and other features and characteristics of this disclosure, as well as the methods of operation and function of structurally related elements, and the economic efficiency of component assembly and manufacturing, will become more apparent upon consideration of the following description and appended claims with reference to the accompanying drawings, all of which form part of this specification, wherein similar reference numerals denote corresponding parts in the figures. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to be construed as limiting the scope of this disclosure. As used in the specification and claims, the singular forms “a,” “an,” and “the” include plural indicators unless the context clearly specifies otherwise. Attached Figure Description

[0026] Additional advantages and details of non-limiting embodiments or aspects will be explained in more detail below with reference to exemplary embodiments shown in the accompanying diagrams, wherein:

[0027] Figure 1A Schematic diagrams of non-limiting embodiments of environments in which the systems, devices, products, apparatuses and / or methods described herein can be implemented based on the principles of this disclosure;

[0028] Figure 1B A diagram of a non-limiting embodiment of a system for automatically generating an injection protocol for delivering medical fluid to a patient during a fluid infusion procedure;

[0029] Figure 2 for Figure 1A and 1B A diagram of a non-limiting embodiment of a component of one or more systems or devices;

[0030] Figure 3 A flowchart of a non-limiting embodiment of the process for operating a fluid injection system;

[0031] Figure 4 The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0032] Figure 5 The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0033] Figure 6A The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0034] Figure 6B The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0035] Figure 7A The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0036] Figure 7B The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0037] Figure 7C The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0038] Figure 7D The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0039] Figure 7E The illustration is a non-limiting embodiment of a user interface on a display screen, illustrating a method for operating a fluid injection system;

[0040] Figure 8 Figures for a non-limiting embodiment of an environment including workstation equipment and a fluid injection system;

[0041] Figure 9 Figures showing a non-limiting embodiment of the fluid injection system; and

[0042] Figure 10 A diagram showing a non-limiting embodiment of an injector head unit for a fluid injection system. Detailed Implementation

[0043] For the purposes described below, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and their derivatives should be used in connection with this disclosure, as they are oriented in the accompanying drawings. However, it should be understood that this disclosure may take various alternative variations and sequences of steps unless expressly stated to the contrary. It should also be understood that the specific devices and processes shown in the accompanying drawings and described in the following specification are merely exemplary embodiments of this disclosure. Therefore, unless otherwise stated, specific dimensions and other physical features relating to the embodiments or aspects of the embodiments disclosed herein should not be considered limiting.

[0044] No aspect, component, element, structure, action, step, function, instruction, etc., used herein should be construed as critical or essential unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more” and “at least one.” Additionally, as used herein, the term “collection” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with “one or more” or “at least one.” The term “an” or similar language is used when only one item is intended. Furthermore, as used herein, the terms “have,” “possess,” “contain,” etc., are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise.

[0045] As used herein, the terms "communication" and "transmission" can refer to the receipt, transmission, transfer, provision, etc., of information (e.g., data, signals, messages, instructions, commands, etc.). Communication between one unit (e.g., a device, system, component of a device or system, combination thereof, etc.) and another unit means that one unit is able to receive information directly or indirectly from and / or transmit information to the other unit. This can refer to a direct or indirect connection that is essentially wired and / or wireless. Furthermore, two units can communicate with each other even if the transmitted information can be modified, processed, relayed, and / or routed between the first and second units. For example, a first unit can communicate with a second unit even if it passively receives information and does not actively transmit information to the second unit. As another example, a first unit can communicate with a second unit if at least one intermediate unit (e.g., a third unit located between the first and second units) processes information received from the first unit and transmits the processed information to the second unit. In some non-limiting embodiments, a message can refer to a network packet (e.g., a data packet, etc.) that includes data. It should be understood that many other arrangements are also possible.

[0046] As used herein, the term "system" may refer to one or more computing devices or a combination of computing devices, such as, but not limited to, processors, servers, client devices, software applications, and / or other similar components. Furthermore, as used herein, references to "server" or "processor" may refer to the previously described server and / or processor responsibly performing the preceding steps or functions, different servers and / or processors, and / or combinations of servers and / or processors. For example, as used in the specification and claims, a first server and / or a first processor responsibly performing a first step or function may refer to the same or different servers and / or processors responsibly performing a second step or function.

[0047] In some instances, a fluid infusion system may be part of a set of devices used in medical facilities such as hospitals during patient treatment and / or in medical imaging facilities. Individuals, such as healthcare providers (e.g., personnel operating magnetic resonance imaging (MRI) equipment), may use workstation devices to provide parameters for the infusion protocol of a fluid infusion procedure that will be managed by the fluid infusion system. Parameters may be provided as input manually provided by the user. However, the infusion protocol may need to be tailored to the specific patient undergoing the fluid infusion procedure in order to correctly perform the relevant medical care and / or assessment, and / or to ensure that the patient is not harmed by the infusion. For example, certain medical fluids to be infused in a fluid infusion procedure may need to be administered based on the patient's correct dosing and injected at a specific flow rate for optimal results.

[0048] The described systems, methods, and computer program products improve the accuracy and efficiency of fluid injection procedures for generating injection protocols and operating fluid injection systems. In some non-limiting embodiments, the injection protocol management system may receive patient data associated with a patient undergoing a fluid injection procedure, automatically generate at least one parameter of the injection protocol for the fluid injection procedure based on the patient data, and provide at least one parameter of the injection protocol to the fluid injection system. In some non-limiting embodiments, the patient data may include data associated with the patient's weight. In some non-limiting embodiments, when automatically generating at least one parameter, the injection protocol management system may determine a first dose of medical fluid for the fluid injection procedure based on at least one of the following: the patient's weight, the concentration of the medical fluid, or the anatomical region of the patient in which the fluid injection procedure will be performed.

[0049] In some non-limiting embodiments, the injection protocol management system may include a display unit, and the system may display multiple patient identifiers on a user interface of the display unit, and then receive a selection of a patient identifier from among the multiple patient identifiers via the user interface. In some non-limiting embodiments, the patient identifier may include a unique identifier associated with a patient record, and receiving patient data based on the selection of a patient identifier received via the user interface may include retrieving patient data from patient records stored in a hospital information system. In some non-limiting embodiments, the patient identifier may include an identifier unrelated to a patient record, and the injection protocol management system may receive patient data based on the selection of a patient identifier received via the user interface. In some non-limiting embodiments, the injection protocol management system may receive patient data from user input via a user interface.

[0050] In some non-limiting embodiments, when determining a first dose of medical fluid for a fluid infusion procedure, the infusion protocol management system may determine a first dose of medical fluid for a first injection phase of the fluid infusion procedure, and when automatically generating at least one parameter of the infusion protocol for the fluid infusion procedure, the infusion protocol management system may determine a first flushing phase of the fluid infusion procedure including a first injection of saline fluid, and determine a second dose of medical fluid for a second injection phase of the fluid infusion procedure based on at least one of the following: patient weight, concentration of medical fluid, or anatomical region, and the infusion protocol management system may determine a second flushing phase including a second injection of saline fluid. In some non-limiting embodiments, the infusion protocol management system may execute the fluid infusion procedure in the order of first injection phase, first flushing phase, holding phase, second injection phase, and second flushing phase. In some non-limiting embodiments, when automatically generating at least one parameter of the infusion protocol for the fluid infusion procedure, the infusion protocol management system may determine a first flow rate of medical fluid for the first injection phase and a second flow rate of medical fluid for the second injection phase based on the concentration of medical fluid and the anatomical region.

[0051] In some non-limiting embodiments, the injection protocol management system may further include a display unit, and the injection protocol management system may display multiple anatomical region identifiers in a user interface on the display unit. In some non-limiting embodiments, the injection protocol management system may receive a selection of anatomical region identifiers from among the multiple anatomical region identifiers via the user interface. In some non-limiting embodiments, when at least one parameter of the injection protocol for the fluid injection procedure is automatically generated, the injection protocol management system may determine the type of medical fluid (e.g., name, identifier, etc.), the concentration of the medical fluid, and the anatomical region based on the selection of the anatomical region identifiers received via the user interface.

[0052] In this way, non-limiting embodiments of this disclosure can generate injection protocols more quickly with fewer user steps, while ensuring the accuracy of injection protocol parameters by automatically generating them based on patient data. Additional computational improvements are provided by integrating patient data retrieved from hospital information systems, from which injection protocol parameters can be automatically generated (e.g., reducing network resources, such as calling devices that might otherwise require retrieving patient data within a process to generate the injection protocol, rather than requiring the user to use separate computing devices, applications, and / or processes to retrieve patient data). Furthermore, by automatically generating injection protocol parameters based on patient data and / or selected anatomical regions, patient safety and the efficiency of medical procedures are improved, through which parameters such as the medical fluid, its concentration, and flow rate can be automatically determined. This reduces the chance of introducing human error during the setup of the injection protocol in the fluid injection procedure.

[0053] For reference Figure 1A , Figure 1A A diagram illustrating a non-limiting embodiment of an environment 100A in which the apparatus, system, method, and / or computer program product described herein may be implemented. (See diagram for reference.) Figure 1A As shown, environment 100A includes an injection protocol management system 102, a fluid injection system 104, a workstation device 106, a hospital information system 108, and a communication network 110. In some non-limiting embodiments, the injection protocol management system 102, the fluid injection system 104, the workstation device 106, and / or the hospital information system 108 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections (e.g., establishing connections for communication). Any device or system in environment 100A may communicate with each other in the same or different communication network 110 as other devices or systems.

[0054] In some non-limiting embodiments, the injection protocol management system 102 may include one or more devices capable of communicating with the fluid injection system 104, workstation device 106, and / or hospital information system 108 via the communication network 110. For example, the injection protocol management system 102 may include one or more computing devices, such as one or more computers, one or more servers (e.g., cloud servers, a set of servers, etc.), one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In some non-limiting embodiments, the injection protocol management system 102 may include one or more (e.g., multiple) applications (e.g., software applications) that perform a set of functions on an external application programming interface (API) that allows the injection protocol management system 102 to send data to and receive data from external systems associated with the external API. In some non-limiting embodiments, the application may be supported by an application associated with the fluid injection system 104 that would allow the injection protocol management system 102, which can be used as a control room display, to be the sole device controlling the fluid injection system 104, and in such an example, the injection protocol management system 102 may provide authentication functionality. In some non-limiting embodiments, the injection protocol management system 102 may be a component of the fluid injection system 104 and / or the workstation device 106.

[0055] In some non-limiting embodiments, the fluid infusion system 104 may include one or more devices capable of communicating with the infusion protocol management system 102, workstation device 106, and / or hospital information system 108 via the communication network 110. For example, the fluid infusion system 104 may include one or more computing devices, such as one or more computers, one or more servers (e.g., cloud servers, a set of servers, etc.), one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In some non-limiting embodiments, the fluid infusion system 104 may include one or more infusion devices (e.g., one or more fluid infusion devices, one or more fluid injectors). In some non-limiting embodiments, the fluid infusion system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid comprising a contrast agent to a patient, and / or administer an aqueous fluid (e.g., saline) to the patient before, during, and / or after the administration of the contrast fluid. For example, the fluid infusion system 104 may directly infuse one or more prescription doses of contrast fluid into the patient's bloodstream via a subcutaneous injection needle and syringe. In some non-limiting embodiments, the fluid infusion system 104 may be configured to continuously administer an aqueous fluid to a patient via a peripheral venous line (PIV) and catheter, and one or more prescription doses of contrast fluid may be introduced into the PIV and administered to the patient via the catheter. In some non-limiting embodiments, the fluid infusion system 104 is configured to infuse a dose of contrast fluid, followed by administration of a specific volume of aqueous fluid. In some non-limiting embodiments, the fluid infusion system 104 may include one or more exemplary fluid infusion devices disclosed in: U.S. Patent Application Serial No. 09 / 715,330, filed November 17, 2000, granted U.S. Patent No. 6,643,537; U.S. Patent Application Serial No. 09 / 982,518, filed October 18, 2001, granted U.S. Patent No. 7,094,216; and U.S. Patent Application Serial No. 10 / 825,866, filed April 16, 2004, granted U.S. Patent No. 6,643,537. U.S. Patent No. 7,556,619; U.S. Patent Application Serial No. 12 / 437,011, filed May 7, 2009, granted U.S. Patent No. 8,337,456; U.S. Patent Application Serial No. 12 / 476,513, filed June 2, 2009, granted U.S. Patent No. 8,147,464; and U.S. Patent Application Serial No. 11 / 004,670, filed December 3, 2004, granted U.S. Patent No. 8,540,698, the disclosure of each of which is incorporated herein by reference in its entirety. In some non-limiting embodiments, the fluid injection system 104 may include MEDRAD. ® Stellant CT Injection System, MEDRAD ®Stellant FLEX CT Injection System, MEDRAD ® MRXperion MR Injection System, MEDRAD ® Mark 7 Arterion Injection System, MEDRAD ® Intego PET infusion system or MEDRAD ® Centargo CT injection system, all of which are provided by Bayer Healthcare LLC.

[0056] In some non-limiting embodiments, workstation device 106 may include one or more devices capable of communicating with injection protocol management system 102, fluid injection system 104, and / or hospital information system 108 via communication network 110. For example, workstation device 106 may include computing devices, such as one or more computers, including desktop computers, laptop computers, tablets, etc. At least a portion of the process executed at workstation device 106 may be executed at a remote server (e.g., a cloud computing server). In some non-limiting embodiments, workstation device 106 may provide a user interface for controlling the operation of fluid injection system 104, including generating instructions for and / or providing instructions to fluid injection system 104. Additionally or alternatively, workstation device 106 may display operating parameters of fluid injection system 104 during operation of fluid injection system 104 (e.g., during real-time operation). In some non-limiting embodiments, workstation device 106 may provide interconnection between fluid injection system 104 and other devices or systems such as scanner devices (not shown). In some non-limiting embodiments, workstation device 106 may include Certegra provided by Bayer. ® Workstation. In some non-limiting embodiments, workstation device 106 may include a display unit (e.g., a display device, display screen, etc.), such as a computer monitor, touchscreen, head-up display, etc., which can be used to display a user interface (e.g., a graphical user interface (GUI) of a software application) through which a user can interact with workstation device 106 to view parameters and / or control the operation of fluid injection system 104. For example, a user of workstation device 106 may provide input to workstation device 106 using one or more hardware or software components of workstation device 106, along with a touchscreen, mouse, touchpad, keyboard, stylus, gesture-sensing camera, microphone for receiving voice commands, etc.

[0057] In some non-limiting embodiments, the hospital information system 108 may include one or more devices capable of communicating with the injection protocol management system 102, the fluid injection system 104, and / or the workstation device 106 via the communication network 110. For example, the hospital information system 108 may include one or more computing devices, such as one or more desktop computers, one or more mobile devices, one or more servers, etc. In some non-limiting embodiments, the hospital information system 108 may include one or more subsystems, such as a patient procedure tracking system (e.g., a system for operating modal work lists, a system for providing patient demographic information for fluid injection procedures and / or medical imaging procedures, etc.), a fluid injection management system, an image archiving and communication system (e.g., a picture archiving and communication system (PACS)), a radiology information system (RIS), and / or a radiology analysis system (e.g., Radimetrics, marketed and sold by Bayer HealthCare LLC). ® (Enterprise applications). In some non-limiting embodiments, the hospital information system 108 may include one or more databases in which patient records (e.g., data files or data objects including patient data) are stored, which may be accessible by devices or systems in environment 100A (e.g., with read access permissions and / or write access permissions), such as injection protocol management system 102 and / or workstation device 106.

[0058] In some non-limiting embodiments, the communication network 110 may include one or more wired and / or wireless networks. For example, the communication network 110 may include a cellular network (e.g., Long Term Evolution (LTE)). ® Networks including third-generation (3G), fourth-generation (4G), fifth-generation (5G), sixth-generation (6G), code division multiple access (CDMA), etc., public land mobile networks (PLMN), local area networks (LAN), wide area networks (WAN), metropolitan area networks (MAN), telephone networks (e.g., public switched telephone network (PSTN)), private networks, self-organizing networks, intranets, the Internet, fiber-optic networks, cloud computing networks, short-range wireless communication networks (e.g., Bluetooth networks, near field communication (NFC) networks), etc., and / or combinations of these or other types of networks.

[0059] Figure 1A The number and arrangement of systems and / or equipment shown are provided as examples. Figure 1A Compared to the systems and / or equipment shown, there may be additional systems and / or equipment, fewer systems and / or equipment, different systems and / or equipment, or systems and / or equipment with different arrangements. Furthermore, Figure 1A The two or more systems and / or devices shown can be implemented within a single system or a single device, or Figure 1AThe single system or single device shown can be implemented as multiple distributed systems or devices. Additionally or alternatively, a group of systems or a group of devices in environment 100A (e.g., one or more systems, one or more devices) can perform one or more functions described as being performed by another group of systems or another group of devices in environment 100A.

[0060] For reference Figure 1B , Figure 1B This diagram illustrates a non-limiting embodiment of system 100B, which is used to automatically generate an injection protocol for delivering medical fluids to a patient during a fluid injection procedure. In some non-limiting embodiments, one or more functions described herein with respect to system 100B may be performed by an injection protocol management system 102 (e.g., entirely, partially, etc.). In some non-limiting embodiments, one or more functions described with respect to system 100B may be performed by another device or set of devices separate from and / or including the injection protocol management system 102 (e.g., entirely, partially, etc.), such as fluid injection system 104, workstation device 106 (e.g., which includes display unit 106A), hospital information system 108, and / or medical imaging system 112.

[0061] like Figure 1B As shown, system 100B includes an injection protocol management system 102, a fluid injection system 104, a workstation device 106, a hospital information system 108, and a medical imaging system 112. The workstation device 106 includes a display unit 106A. In some non-limiting embodiments, the injection protocol management system 102 may be interconnected with the fluid injection system 104, the workstation device 106, the hospital information system 108, and / or the medical imaging system 112 via a wired connection, a wireless connection, or a combination of wired and wireless connections (e.g., establishing a connection for communication, etc.).

[0062] In some non-limiting embodiments, the medical imaging system 112 may include one or more devices capable of communicating with the injection protocol management system 102, the fluid injection system 104, the workstation device 106, and / or the hospital information system 108 via a communication network (e.g., communication network 114). In some non-limiting embodiments, the medical imaging system 112 may include one or more scanners, such as CT scanners and / or MRI scanners, capable of communicating via a communication network and capable of performing medical imaging procedures involving the use of radiographic materials.

[0063] like Figure 1BAs shown, the injection protocol management system 102 may include multiple applications, such as an informatics application 202A, a data management application 202B, and an imaging system connectivity application 202C. In some non-limiting embodiments, the multiple applications may be stored in the storage device of the injection protocol management system 102. In some non-limiting embodiments, each of the multiple applications may be associated with an API associated with the corresponding application (e.g., a first API associated with a first application, a second API associated with a second application, a third API associated with a third application, etc.), which allows the fluid injection system 104 to interface with the injection protocol management system 102 (e.g., communicate, establish communication interfaces, etc.) and / or allows the injection protocol management system 102 to interface with the hospital information system 108 (e.g., various subsystems of the hospital information system 108, such as the patient procedure tracking system 208A, the fluid injector management system 208B, the image archiving and communication system 208C, the radiology information system 208D, and / or the radiology analysis system 208E).

[0064] In some non-limiting embodiments, the injection protocol management system 102 may provide a user interface (e.g., through an application that includes a user interface, such as a web-based user interface) that allows a user to control the fluid injection system 104. For example, a user may be able to initiate medical imaging, fluid injection, and / or other additional procedures performed by the fluid injection system 104 via the user interface. Additionally or alternatively, the user interface may allow the user to control aspects of the informatics application 202A, the data management application 202B, and / or the imaging system connectivity application 202C.

[0065] like Figure 1B As further shown, workstation device 106 may include display unit 106A. In some non-limiting embodiments, display unit 106A is capable of displaying a user interface (e.g., a web-based user interface) provided by injection protocol management system 102. In some non-limiting embodiments, display unit 106A may include computing devices, such as smart display units, portable computers such as tablets, laptops, etc. In some non-limiting embodiments, display unit 106A may include a touchscreen for receiving user input. In some non-limiting embodiments, display unit 106A may include display devices (e.g., monitors, screens, and / or similar devices for displaying visual information).

[0066] In some non-limiting embodiments, informatics application 202A, data management application 202B, and / or imaging system connectivity application 202C may be associated with the communication interface of the injection protocol management system 102 between the fluid injection system 104 and the hospital information system 108. For example, the injection protocol management system 102 may provide a communication interface between the fluid injection system 104 and the hospital information system 108 based on informatics application 202A, data management application 202B, and / or imaging system connectivity application 202C. In some non-limiting embodiments, the communication interface may include a set of communication settings (e.g., protocols, standards, etc.) enabling one device (e.g., a device of the system) to communicate with another device (e.g., remote communication). In some non-limiting embodiments, informatics application 202A may provide the fluid injection system 104 with the ability to interact with the hospital information system 108 (e.g., any of the multiple subsystems of the hospital information system 108). Additionally or alternatively, informatics application 202A may provide data storage for fluid injection system 104 (e.g., data associated with the injection protocol of the fluid injection procedure to be performed by fluid injection system 104). In some non-limiting embodiments, data management application 202B may provide functionality associated with file system and database management for injection protocol management system 102. Additionally or alternatively, data management application 202B may provide operational control over the data storage of fluid injection system 104. In some non-limiting embodiments, imaging system connectivity application 202C may provide functionality for interaction with medical imaging system 112 for injection protocol management system 102 and / or fluid injection system 104. In some non-limiting embodiments, imaging system connectivity application 202C may abstract the interfaces of medical imaging system 112 (e.g., ISI interface, ISI2 interface, and / or Connect CT interface) into a standard format for use by injection protocol management system 102 and / or fluid injection system 104.

[0067] In some non-limiting embodiments, the injection protocol management system 102 can transmit data associated with images received from the medical imaging system 112 to the fluid injection system 104 via a communication network. For example, the injection protocol management system 102 can transmit data associated with images received from the medical imaging system 112 to the fluid injection system 104 via a communication network based on an API call from the fluid injection system 104 to the imaging system connection application 202C. In some non-limiting embodiments, the injection protocol management system 102 can transmit data associated with the fluid injection procedure (e.g., data associated with the amount of time for injecting radioactive contrast material into the patient) received from the fluid injection system 104 to the medical imaging system 112 via a communication network. For example, the injection protocol management system 102 can transmit data associated with the fluid injection procedure received from the fluid injection system 104 to the medical imaging system 112 via a communication network based on API calls (e.g., API calls for the Imaging System Interface (ISI), API calls for the ISI2 interface, API calls for the Connect CT interface, etc.), and then from the medical imaging system 112 to the imaging system connection application 202C. In some non-limiting embodiments, the medical imaging system 112 may perform a medical imaging procedure on a patient based on data associated with a fluid injection procedure, including an injection protocol. In some non-limiting embodiments, the injection protocol management system 102 may receive data associated with the operation of the medical imaging system 112 via a communication network based on API calls (e.g., API calls from the injection protocol management system 102 to the medical imaging system 112).

[0068] In some non-limiting embodiments, the injection protocol management system 102 may provide a communication interface between the hospital information system 108 and the fluid injection system 104, enabling the informatics application 202A to provide the fluid injection system 104 with the ability to receive data based on API calls from the fluid injection system 104 to the injection protocol management system 102. In some non-limiting embodiments, the injection protocol management system 102 may transmit informatics-related data received from the hospital information system 108 to the fluid injection system 104 via a communication network (e.g., communication network 110). For example, the injection protocol management system 102 may transmit informatics-related data received from the hospital information system 108 to the fluid injection system 104 via a communication network based on API calls from the fluid injection system 104 to the informatics application 202A. Informatics-related data may include data associated with the patient's identity, data associated with patient examination procedures (e.g., fluid injection procedures and / or medical imaging procedures performed on the patient), such as data associated with the contrast fluid provided during the fluid injection procedure, the specifications of the catheter used during the fluid injection procedure, and the fluid injection protocol used for the fluid injection procedure. In some non-limiting embodiments, the injection protocol management system 102 may store data associated with patient examination procedures and / or data associated with the configuration of the fluid injection system 104 having informatics application 202A.

[0069] like Figure 1BAs further shown, the hospital information system 108 may include multiple subsystems. These subsystems may include a patient procedure tracking system 208A, a fluid injector management system 208B, an image archiving and communication system 208C, a radiology information system 208D, and a radiology analysis system 208E. In some non-limiting embodiments, the injection protocol management system 102 may receive informatics-related data from the hospital information system 108 via a communication network (e.g., communication network 110) according to a communication protocol for transmitting informatics-related data. For example, the injection protocol management system 102 may receive patient procedure-related data from the hospital information system 108 (e.g., from the patient procedure tracking system 208A) via the communication network according to the Medical Digital Imaging and Communication (DICOM) communication protocol, receive operation-related data of the fluid injection system from the hospital information system 108 (e.g., from the fluid injector management system 208B) via the communication network according to API calls (e.g., from the injection protocol management system 102 to the fluid injector management system 208B), and receive data related to the operation of the fluid injection system from the hospital information system 108 (e.g., from the fluid injector management system 208B) via the communication network according to the DICOM communication protocol. System 108 (e.g., from image archive and communication system 208C) receives data related to radiographic images, receives data related to patient examination procedures from hospital information system 108 (e.g., from radiology information system 208D) via a communication network according to the Health Level 7 (HL7) standard communication protocol, and / or receives data related to radiation dose during medical imaging procedures from hospital information system 108 (e.g., from radiology analysis system 208E) via a communication network based on API calls (e.g., API calls from injection protocol management system 102 to radiology analysis system 208E).

[0070] For reference Figure 2 , Figure 2 This diagram illustrates example components of device 200. Device 200 may correspond to one or more devices of injection protocol management system 102, one or more devices of fluid injection system 104 and / or workstation device 106, hospital information system 108 and / or medical imaging system 112. In some non-limiting embodiments, injection protocol management system 102, fluid injection system 104 and / or workstation device 106, hospital information system 108 and / or medical imaging system 112 may include at least one device 200 and / or at least one component of device 200. Figure 2 As shown, device 200 may include bus 202, processor 204, memory 206, storage unit 208, input unit 210, output unit 212 and communication interface 214.

[0071] Bus 202 may include components that allow communication between parts of device 200. In some non-limiting embodiments, processor 204 may be implemented using hardware, firmware, or a combination of hardware and software. For example, processor 204 may include a processor (e.g., a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), etc.), microprocessor, digital signal processor (DSP), and / or any processing unit that can programmably perform functions (e.g., a field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), etc.). Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory, etc.) that store information and / or instructions for use by processor 204.

[0072] Storage component 208 may store information and / or software related to the operation and use of device 200. For example, storage component 208 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, solid-state disks, etc.), optical disks (CDs), digital versatile optical disks (DVDs), floppy disks, cassette tapes, magnetic tapes, and / or other types of computer-readable media, and corresponding drives.

[0073] Input component 210 may include components that allow device 200 to receive information, such as through user input (e.g., touchscreen display, keyboard, keypad, mouse, button, switch, microphone, etc.). Additionally or alternatively, input component 210 may include sensors for sensing information (e.g., Global Positioning System (GPS) components, accelerometers, gyroscopes, actuators, etc.). Output component 212 may include components that provide output information from device 200 (e.g., display, speaker, one or more light-emitting diodes (LEDs), etc.).

[0074] Communication interface 214 may include transceiver-like components (e.g., transceiver, standalone receiver and transmitter, etc.) that enable device 200 to communicate with other devices, for example, via wired connection, wireless connection, or a combination of wired and wireless connection. Communication interface 214 may allow device 200 to receive information from and / or provide information to another device. For example, communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, or a Wi-Fi interface. ® Interfaces, cellular network interfaces, etc.

[0075] Device 200 can perform one or more processes described herein. Device 200 can perform these processes based on processor 204 executing software instructions stored on a computer-readable medium such as memory 206 and / or storage unit 208. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device may include memory space located within a single physical storage device or memory space distributed across multiple physical storage devices.

[0076] Software instructions can be read into memory 206 and / or storage unit 208 from another computer-readable medium or another device via communication interface 214. When executed, the software instructions stored in memory 206 and / or storage unit 208 can cause processor 204 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.

[0077] Figure 2 The number and arrangement of components shown are provided as an example. In some non-limiting embodiments, device 200 may include more than Figure 2 The more components, fewer components, different components, or components arranged differently shown. Additionally or alternatively, a set of components of device 200 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 200.

[0078] For reference Figure 3 , Figure 3 A flowchart illustrating a non-limiting embodiment of a process 300 for operating a fluid injection system. In some non-limiting embodiments, one or more steps of process 300 are performed by an injection protocol management system 102 (e.g., entirely, partially, etc.). In some non-limiting embodiments, one or more steps of process 300 are performed by another device or group of devices separate from or including the injection protocol management system 102 (e.g., entirely, partially, etc.), such as fluid injection system 104 (e.g., one or more devices of fluid injection system 104), workstation device 106, and / or hospital information system 108 (e.g., one or more devices of hospital information system 108).

[0079] like Figure 3As shown, in step 302, process 300 may include displaying multiple patient identifiers. For example, the injection protocol management system 102 may display multiple patient identifiers in a user interface on a display unit (e.g., display unit 106A) of workstation device 106. In some non-limiting embodiments, the multiple patient identifiers may include one or more unique identifiers. Each identifier may be associated with a patient's patient record (e.g., a patient's patient record stored in the patient procedure tracking system 208A of hospital information system 108). In some non-limiting embodiments, the multiple patient identifiers may be displayed in a list of rows associated with the patient (e.g., such as...). Figure 5 (As shown). In some non-limiting embodiments, the multiple patient identifiers may include identifiers not associated with a patient record, such as identifiers of unknown or anonymous patients. In some non-limiting embodiments, the multiple patient identifiers may include one or more patient identifiers associated with a patient record and one or more identifiers not associated with a patient record.

[0080] like Figure 3 As shown, in step 304, process 300 may include receiving a selection of a patient identifier. For example, the injection protocol management system 102 may receive a selection of a patient identifier from a plurality of patient identifiers via a user interface. In some non-limiting embodiments, the injection protocol management system 102 may receive a selection of a patient identifier based on user input. For example, a user may select an identifier associated with a patient record (e.g., a patient identifier including a unique identifier) ​​by selecting (e.g., touching, clicking, pressing, etc.) an identifier in the user interface. In some non-limiting embodiments, a user may select an identifier unrelated to a patient record by selecting a button indicating that the patient's identity is unknown, anonymous, etc. In the above examples, the injection protocol management system 102 may receive the selection of an identifier via the user interface based on the user's selection of an identifier in the user interface.

[0081] like Figure 3As shown, in step 306, process 300 may include displaying multiple anatomical region identifiers. For example, the injection protocol management system 102 may display multiple anatomical region identifiers in a user interface on a display unit (e.g., display unit 106A of workstation device 106). In some non-limiting embodiments, the anatomical region identifier may contain an identifier (e.g., a brief description, a unique code, an image, etc.) that represents the anatomical region (e.g., a patient's anatomical region) in which a fluid injection procedure will be performed. For example, the fluid injection procedure may require the injection of a medical fluid (e.g., a contrast agent) to perform an MRI scan of a patient's breast. In such an example, the anatomical region identifier may contain a brief description, such as the text "breast". As a further example, the anatomical region identifier may contain a unique code (e.g., a co-magnetic imaging (CPT) code), such as "77059".

[0082] like Figure 3 As shown, in step 308, process 300 may include receiving a selection of an anatomical region identifier. For example, the injection protocol management system 102 may receive a selection of an anatomical region identifier from a plurality of anatomical region identifiers via a user interface. In some non-limiting embodiments, a user may select an anatomical region identifier by selecting it in the user interface. In some non-limiting embodiments, the injection protocol management system 102 may receive a selection of an anatomical region identifier based on user input. For example, a user may select an anatomical region identifier associated with a patient's anatomical region where a fluid injection procedure will be performed by selecting it in the user interface. In such an example, the injection protocol management system 102 may receive a selection of an anatomical region identifier via the user interface based on the user's selection of the anatomical region identifier in the user interface. In some non-limiting embodiments, the selection of an anatomical region identifier may be performed automatically by means of a selection by the patient on workstation device 106, triggered by, for example, electronic communication from workstation device 106.

[0083] like Figure 3As shown, in step 310, process 300 includes receiving patient data. For example, the injection protocol management system 102 may receive patient data associated with a patient undergoing a fluid injection procedure. In some non-limiting embodiments, patient data may include the patient's name, height, weight, age, estimated glomerular filtration rate (eGFR), gender, patient identifier (e.g., Social Security number, globally unique code, etc.), patient registration number (e.g., a unique number assigned to the patient by the hospital information system 108, which can be used to determine when the patient was first identified), patient procedure identifier (e.g., a unique identifier for identifying the type of procedure to be performed, such as a medical procedure, including a fluid injection procedure), etc. In some non-limiting embodiments, the patient data associated with the patient may correspond to the patient's patient record (e.g., an existing patient record) stored in the hospital information system 108.

[0084] In some non-limiting embodiments, the injection protocol management system 102 may transmit an identifier (e.g., a unique identifier) ​​associated with a patient's record of a patient undergoing a fluid injection procedure to the hospital information system 108, and the injection protocol management system 102 may receive patient data from the hospital information system 108. In some non-limiting embodiments, the hospital information system 108 may receive an identifier associated with a patient record, retrieve the patient's record based on the identifier, and transmit the patient record to the injection protocol management system 102.

[0085] In some non-limiting embodiments, the injection protocol management system 102 may receive patient data based on the selection of a patient identifier. In some non-limiting embodiments, the injection protocol management system 102 may receive patient data by retrieving patient data from patient records stored in the hospital information system 108 based on a patient identifier. In some non-limiting embodiments, the injection protocol management system 102 may retrieve patient data from the hospital information system 108 and, based on the selection of the receiving patient identifier, store the patient data in temporary local storage on the injection protocol management system 102. In some non-limiting embodiments, the injection protocol management system 102 may display the patient data in a user interface. In some non-limiting embodiments, when the selected patient identifier is an identifier unrelated to a patient record, the injection protocol management system 102 may receive patient data from user input via a user interface. For example, the injection protocol management system 102 may display one or more input fields (e.g., graphical user interface elements displayed in the user interface, such as text fields, numeric sliders, drop-down menus, date pickers, etc.) to receive user input including patient data (e.g., receiving weight in pounds when the user enters the patient's weight into the corresponding patient weight input field for an unknown patient).

[0086] like Figure 3 As shown, in step 312, process 300 includes automatically generating at least one parameter of the injection protocol. For example, the injection protocol management system 102 may automatically generate at least one parameter of the injection protocol for a fluid injection procedure based on patient data associated with a patient undergoing a fluid injection procedure. In some non-limiting embodiments, the injection protocol management system 102 may automatically generate at least one parameter of the injection protocol by determining the dose (e.g., ml / kg) of the medical fluid (e.g., contrast fluid) used in the fluid injection procedure. In some non-limiting embodiments, the injection protocol management system 102 may determine the dose based on the patient's weight (e.g., in kilograms, which can be converted from pounds), the concentration of the medical fluid to be used in the fluid injection procedure (e.g., mmol / ml), the anatomical region (e.g., breast, heart, central nervous system (CNS), supra-aortic renal region, liver, head, neck, chest, abdomen, limbs, etc.).

[0087] In some non-limiting embodiments, the fluid infusion procedure may include multiple phases. For example, the fluid infusion procedure may include an infusion phase, a flushing phase, and / or a holding phase. In some non-limiting embodiments, the infusion phase of the fluid infusion procedure may be a phase characterized by a volume of medical fluid (e.g., a fluid volume that varies over time) infused at a certain flow rate, which may be determined by the total duration of the infusion phase. In some non-limiting embodiments, the flushing phase of the fluid infusion procedure may be a phase characterized by a volume of medical fluid acting as a flushing agent infused at a certain flow rate, which may be determined by the total duration of the flushing phase. In some non-limiting embodiments, the holding phase of the fluid infusion procedure may be a phase characterized by no fluid being infused into the patient for a period of time. In some non-limiting embodiments, the infusion protocol management system 102 may determine the dosage of medical fluid used in the infusion phase and / or flushing phase of the fluid infusion procedure. In some non-limiting embodiments, the operational parameters of the injection protocol of the fluid injection procedure performed by the fluid injection system 104 may include one or more exemplary data types disclosed in the following patents: U.S. Patent Application No. 10 / 143,562 (filed May 10, 2002, U.S. Patent No. 7,457,804); U.S. Patent Application No. 12 / 254,318 (filed October 20, 2008, U.S. Patent No. 7,996,381); and U.S. Patent Application No. 13 / 180,175 (filed July 11, 2011, U.S. Patent No. 8,521,716), the disclosure of each of which is incorporated herein by reference in its entirety.

[0088] In some non-limiting embodiments, the fluid infusion procedure may include an infusion phase, a flushing phase, and / or a holding phase, in the order specified. In some non-limiting embodiments, parameters of the infusion protocol for the fluid infusion procedure may include the amount of time for the fluid infusion procedure (e.g., for each phase), the type of medical fluid used in the fluid infusion procedure (e.g., for each phase), the concentration of the medical fluid used in the fluid infusion procedure (e.g., for each phase), the dose of the medical fluid used in the fluid infusion procedure (e.g., for each phase), the flow rate of the medical fluid used in the fluid infusion procedure (e.g., for each phase), etc.

[0089] In some non-limiting embodiments, the injection protocol management system 102 may determine at least one parameter of the injection protocol for a fluid injection procedure. For example, the injection protocol management system 102 may retrieve data associated with at least one parameter from a data structure based on data associated with the fluid injection procedure (e.g., patient data associated with a patient who will undergo the fluid injection procedure, data associated with the anatomical region of the patient in which the fluid injection procedure will be performed, etc.). In some non-limiting embodiments, the injection protocol management system 102 may configure at least one parameter of the injection protocol for the fluid injection procedure. For example, the injection protocol management system 102 may configure the fluid injection system 104 (e.g., the fluid injection device of the fluid injection system 104) such that the fluid injection procedure is executed according to at least one parameter of the injection protocol.

[0090] In some non-limiting embodiments, the fluid infusion process may include multiple phases of each of an infusion phase, a flushing phase, and / or a holding phase. For example, a fluid infusion procedure may include two infusion phases. In some non-limiting embodiments, the infusion protocol management system 102 may determine a first flow rate of the medical fluid for a first infusion phase and a second flow rate of the medical fluid for a second infusion phase. For example, the infusion protocol management system 102 may determine the first and / or second flow rates based on the concentration of the medical fluid (e.g., a mixture / ratio of contrast agent to saline) and / or the anatomical region of the patient in which the fluid infusion procedure will be performed.

[0091] In some non-limiting embodiments, the injection protocol management system 102 may automatically generate at least one parameter of the injection protocol based on an anatomical region identifier. In one example, the injection protocol management system 102 may automatically generate at least one parameter of the injection protocol based on receiving a selection of an anatomical region identifier.

[0092] In another example, the injection protocol management system 102 can automatically generate an injection protocol for a fluid injection procedure with two phases, such as an injection phase and a flushing phase, and the injection protocol management system 102 can determine the type of medical fluid and the dosage of the medical fluid in the injection phase based on the patient's weight and anatomical region identifier.

[0093] In another example, the infusion protocol management system 102 can automatically generate parameters for the infusion protocol by determining a first dose of medical fluid, determining parameters for a first flushing phase, determining a second dose of medical fluid, and determining parameters for a second flushing phase. In some non-limiting embodiments, the infusion protocol management system 102 can determine the first dose of medical fluid and configure a first flushing phase of a fluid infusion procedure including a first injection of saline fluid (e.g., by configuring the volume and flow rate of the saline fluid to be used by the fluid infusion system 104). The infusion protocol management system 102 can also determine a second dose of medical fluid for the second injection phase of the fluid infusion procedure based on at least one of the following: the patient's weight, the concentration of the medical fluid, or the anatomical region. The infusion protocol management system 102 can further configure a second flushing phase including a second injection of saline fluid (e.g., by configuring the volume and flow rate of the same or different saline fluid). The infusion protocol management system 102 can be configured to execute the fluid infusion procedure in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase (e.g., by transmitting instructions to the fluid infusion system 104). For example, this configuration can be used for fluid injection procedures accompanying MRI scans of the patient's cardiac region.

[0094] In some non-limiting embodiments, the injection protocol management system 102 can automatically generate at least one parameter of the injection protocol for a fluid injection procedure based on the patient's patient data and independently of (e.g., without) user input associated with at least one parameter. For example, the injection protocol management system 102 can automatically generate at least one parameter of the injection protocol for a fluid injection procedure based on patient data and independently of user input associated with the dose of the medical fluid used in the fluid injection procedure, received through a user interface associated with the fluid injection system to which the fluid injection procedure is to be performed.

[0095] like Figure 3As shown, in step 314, process 300 includes providing at least one parameter. For example, the injection protocol management system 102 may provide at least one parameter of the injection protocol to the fluid injection system 104 (e.g., the fluid injection device of the fluid injection system 104). In some non-limiting embodiments, at least one parameter of the injection protocol may be provided to the fluid injection system 104 for performing a fluid injection procedure. In one example, the fluid injection system 104 may, as part of a fluid injection procedure, inject medical fluid into a patient via the fluid injection device based on data associated with at least one parameter of the injection protocol received from the injection protocol management system 102. The fluid injection system 104 may perform the fluid injection procedure according to at least one parameter of the injection protocol, such as the dose of the medical fluid. In some non-limiting embodiments, the injection protocol management system 102 may automatically provide at least one parameter to the fluid injection system 104 based on user input (e.g., selection of a start button). In some non-limiting embodiments, the injection protocol management system 102 may provide at least one parameter in a user interface to indicate that the fluid injection procedure will occur before the fluid injection procedure begins. In some non-limiting embodiments, the injection protocol management system 102 can cause the fluid injection system 104 to execute a fluid injection procedure. For example, the injection protocol management system 102 can cause the fluid injection system 104 to execute a fluid injection procedure based on user input (e.g., selection of a start button) received by the injection protocol management system 102.

[0096] In some non-limiting embodiments, the injection protocol management system 102 can cause the fluid injection system 104 to execute a fluid injection procedure. For example, the injection protocol management system 102 can transmit a command signal that causes the fluid injection system 104 to execute the fluid injection procedure according to an injection protocol of the fluid injection procedure (e.g., based on the fluid injection system 104 receiving a command signal). In some non-limiting embodiments, the injection protocol management system 102 can cause the fluid injection procedure to be executed in a sequence of multiple phases. For example, the injection protocol management system 102 can cause the fluid injection procedure to be executed in the order of an injection phase, a flushing phase, and a holding phase, or any suitable combination thereof. In one example, the injection protocol management system 102 can cause the fluid injection procedure to be executed in the order of a first injection phase, a first flushing phase, a holding phase, a second injection phase, and a second flushing phase.

[0097] In some non-limiting embodiments, the injection protocol management system 102 may transmit data related to the fluid injection procedure (e.g., data related to multiple parameters of the injection protocol of the fluid injection procedure, data related to at least one parameter of the injection protocol of the fluid injection procedure, data related to the complete injection protocol of the fluid injection procedure, etc.). For example, the injection protocol management system 102 may transmit data associated with the fluid injection procedure to the fluid injection system 104 before executing the fluid injection procedure.

[0098] For reference Figure 4 , Figure 4 A non-limiting embodiment of a first GUI 400a for operating a fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the first GUI 400a are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the first GUI 400a, and one or more elements of the first GUI 400a may be included in other GUIs to provide features of the method for operating a fluid injection system. Although ordinal numbers such as "first," "second," and "third" may be used in conjunction... Figures 4 to 7E The GUI is described herein, but it should be understood that these terms are for distinguishing exemplary views (e.g., windows displaying graphics) and not for specifying the order of operations, unless otherwise stated. The user interfaces described in this disclosure may include one or more GUIs 400a-400i described herein.

[0099] The first GUI 400a depicts an illustrative welcome screen (e.g., start screen, main screen, etc.) displayed to the user of workstation device 106. The first GUI 400a may include settings or menu icons (e.g., depicted as a gear symbol or a three-line symbol) to allow the user to configure the GUI preferences of the method (e.g., system units of measurement, default settings for the dosimeter, etc.) and / or display settings (e.g., brightness, light or dark mode, font size, etc.). The first GUI 400a may also include an exit control button (e.g., an "X" that may be accompanied by the word "exit") to close the GUI of the method. The first GUI 400a may also include a set of text describing the GUI to be displayed, such as a welcome message with information about starting. The first GUI 400a may also include graphical buttons for starting a fluid infusion procedure for a new patient (e.g., a button labeled "New Patient") and graphical buttons for starting a fluid infusion procedure for the previous patient used by the system (e.g., a button labeled "Same Patient"). Selecting the New Patient button will navigate the user to the second GUI 400b, such as... Figure 5 As shown. Selecting the same patient button will navigate the user to the third GUI 400c, as... Figure 6A As shown, however, this is based on patients previously used with this system.

[0100] For reference Figure 5 , Figure 5 A non-limiting embodiment of a second GUI 400b for operating the described method of a fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the second GUI 400b are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the second GUI 400b, and one or more elements of the second GUI 400b may be included in other GUIs to provide the characteristics of the described method for operating the fluid injection system.

[0101] The second GUI 400b depicts an illustrative patient worklist screen (e.g., including at least several patient identifiers, such as unique identifiers associated with patient records) that provides a list of patients to the user. The second GUI 400b can provide a list of patients who have at least partially scheduled one or more fluid infusion procedures. Workstation device 106 can communicate with hospital information system 108 to determine the patient list to display based on the time when the patient procedure was scheduled (e.g., date, time of day, etc.). For example, workstation device 106 can receive a list of patients scheduled for the time closest to the current operation time of workstation device 106. In the example shown, for a user operating workstation device 106 at 07:00 AM on July 8, 2022, the second GUI 400b can display a list of patients scheduled for surgery at least within the next forty-eight hours (e.g., July 8, 2022 and July 9, 2022). It should be understood that patients scheduled for wider or narrower time periods can be displayed in the second GUI 400b. It should also be understood that if a patient is scheduled for more than one procedure, a particular patient may be displayed more than once in the second GUI 400b.

[0102] In some non-limiting embodiments, the second graphical user interface 400b may provide a list of patients in a series of rows, where each row represents a different patient and the procedures scheduled for that patient. Each column of the depicted data may represent a different portion of the patient data. For example, multiple columns may be provided that non-limitingly describe the patient's name (e.g., titled "Name"), date of birth (e.g., titled "DOB"), patient identifier (e.g., titled "ID"), procedure time (e.g., titled "Time"), procedure date (e.g., titled "Date"), access number (e.g., titled "ACC," a unique number assigned to the patient by the registrar that may be used to determine when the registrar first identified the patient), and a description of the procedure to be performed (e.g., titled "Study Description," which may include the procedure identifier and / or a brief textual description of the procedure). The rows in the second GUI 400b may be configured to be sorted based on the selected column (e.g., when "Name" is selected, patients may be sorted alphabetically by last name, in reverse alphabetical order, etc.). Each row may also contain an icon (e.g., an icon depicting a profile symbol) that users can select to view more information about the patient and / or patient procedures.

[0103] In some non-limiting embodiments, the second GUI 400b may include a refresh button that updates the patient list with the latest data based on the current time. Additionally or alternatively, the second GUI 400b may refresh automatically based on predetermined time intervals (e.g., once per minute, once every five minutes, etc.). The second GUI 400b may also include a search field to allow users to search for and find specific patients scheduled for the program. The second GUI 400b may also include filter controls to provide users with one or more filters to reconfigure the displayed patient data. If the number of patients exceeds the display space in the second GUI 400b, the second GUI 400b may include scrollbars and / or scrollable scrollable elements to view additional patients. The second GUI 400b may also include buttons to allow users to continue the method for unidentified or irrelevant patients (e.g., anonymous patients, unknown patients, etc.). These buttons may be associated with identifiers unrelated to patient records.

[0104] In some non-limiting embodiments, the second GUI 400b may include settings or menu icons (e.g., depicted as a gear symbol or a three-line symbol) to allow a user to configure preferences and / or display settings for the GUI of the method. The second GUI 400b may also include a navigation bar to depict the user's position in the process (e.g., which part of the process for setting up a fluid injection procedure). The navigation bar may include labels with text and / or icons to indicate parts of the fluid injection procedure setup process, which may include, but are not limited to: viewing the patient work list (e.g., the "Patient" label); viewing injection protocol presets (e.g., the "Protocol" label); viewing patient data and parameters of the injection protocol (e.g., the "Fluid" label); viewing parameters generated for the injection protocol of the fluid injection procedure (e.g., the "Check Information" label); confirming and starting the fluid injection procedure (e.g., the "Injection" label); and waiting while the fluid injection procedure is in progress (e.g., the "Lock" label, indicating that the parameters of the injection protocol for the fluid injection procedure have been configured and provided to the fluid injection system 104 and cannot be changed while the procedure is in progress).

[0105] For reference Figure 6A , Figure 6A A non-limiting embodiment of a third GUI 400c for operating the described method of a fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the third GUI 400c are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the third GUI 400c, and one or more elements of the third GUI 400c may be included in other GUIs to provide the characteristics of the described method for operating the fluid injection system.

[0106] The third GUI 400c depicts an illustrative injection protocol selection screen through which the user can view various types of preset injection protocols (e.g., including at least multiple anatomical region identifiers). The arrangement of the displayed injection protocols can be predetermined based on a specific set of medical fluids planned for use in the relevant fluid injection system. For example, multiple preset injection protocols can be displayed for fluid injection procedures for multiple anatomical regions, such as, but not limited to: breast, heart, central nervous system (CNS), superior renal aorta (e.g., via magnetic resonance angiography (MRA)), and liver. While the term "preset" can be used to indicate a predetermined or preferred injection protocol to be displayed, it should be understood that all parameters of the injection protocol can only be configured later in the method, when the parameters can be automatically generated by the workstation device 106 based on patient data of patients undergoing the procedure. In addition to the corresponding anatomical region, the preset injection protocol button can also identify the dosage parameters (e.g., ml / kg) of the medical fluid to be used and the identifier of the medical fluid, such as, Figure 6A The examples shown are Gadovist and Primovist.

[0107] In some non-limiting embodiments, the third GUI 400c may include multiple additional injection protocol selection options besides the preset injection protocol options for workstation device 106. In response to a user's selection of a corresponding button, other groups of injection protocols may be presented, such as patient priors (e.g., displaying previous injection protocols for the patient based on their patient record), commonly used injection protocols (e.g., displaying commonly used injection protocols on workstation device 106), and additional injection protocol templates for various groups of anatomical regions (e.g., head, neck, chest, abdomen, limbs, etc.). The third GUI 400c may further allow users to create their own preset injection protocols. The third GUI 400c may also include an event notification window accessible by collapsible control buttons, which may present alerts or notifications to the user of workstation device 106. The third GUI 400c may also display patient data (if applicable) for the selected patient in a drop-down field, which may provide some advanced patient data for reference, including but not limited to patient name, patient access number, patient gender, and patient age. In this way, the user is always informed of the patient information for the fluid injection procedure to be performed.

[0108] In some non-limiting embodiments, the third GUI 400c may include a program reset button to discard the current fluid injection program's settings and return to the home and / or start screen, for example... Figure 4 The first GUI 400a Figure 5 The second GUI 400b or Figure 6AThe third GUI 400c. Before resetting the procedure, confirmation from the user may be required to avoid unintentional selection of a reset procedure. The third GUI 400c may also include a preview of the fluid injection procedure based on the injection protocol selected and configured during setup. Since the exemplary third GUI 400c displays multiple preset injection protocols, and the user has not yet selected any of them, the injection protocol preview section of the third GUI 400c is depicted as mostly empty / unfilled. For example, the preview may include fields displaying the total contrast agent volume, total saline volume, and total duration of the fluid injection procedure. Each of these fields in the third GUI 400c is displayed as undefined or zero because no injection protocol has been selected or configured. Similarly, a dropdown list depicting the maximum injection pressure limit for the injection protocol (e.g., in pounds per square inch (PSI)) remains undefined. In contrast, the duration of the keep-open vein (KVO) time is depicted based on the patient's expected medical procedure. Once the user has selected an injection protocol for further setup, the user can select a button (e.g., a "Select and Edit" button) to view the protocol's parameters and confirm them before starting the program. Furthermore, like the second GUI 400b, the third GUI 400c may include a navigation bar to describe the user's location during the setup process.

[0109] For reference Figure 6B , Figure 6B A non-limiting embodiment of a fourth GUI 400d for operating the method of a fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the fourth GUI 400d are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the fourth GUI 400d, and one or more elements of the fourth GUI 400d may be included in other GUIs to provide the characteristics of the method for operating the fluid injection system.

[0110] The fourth GUI 400d depicts a GUI essentially the same as the third GUI 400c, but in a configuration where the user views different groups of injection protocols. Instead of displaying preset injection protocols, the user has selected a "Breast UAA Hospital" template (e.g., based on guidelines from an exemplary hospital) for breast-based injection protocols, which is listed under the injection protocols in the "Breast" group for injection protocols. Further (e.g., by selecting the "Select and Edit" button), the user can view specific parameters of the selected injection protocol (see...). Figure 7A ).

[0111] For reference Figure 7A , Figure 7AA non-limiting embodiment of a fifth GUI 400e for operating the fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the fifth GUI 400e are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the fifth GUI 400e, and one or more elements of the fifth GUI 400e may be included in other GUIs to provide the characteristics of the described method for operating the fluid injection system.

[0112] The fifth GUI 400e depicts an illustrative window (e.g., titled "Fluid" or "Fluid Information," referring to the fluid used in the fluid injection procedure) for viewing and modifying parameters of a selected injection protocol. As shown in the figure, this example is a selected "Breast UAA Hospital" template for the injection protocol, which may have been modified by the user in... Figure 6B The patient data can be selected in the fourth GUI 400d. In some non-limiting embodiments, based on the selection of a patient identifier in the second GUI 400b, patient data can be retrieved from the hospital information system 108 and displayed in the fifth GUI 400e. Additionally or alternatively, patient data can be preloaded from the hospital information system 108 and selectively displayed on the workstation device 106 based on the selection of the patient identifier. In the depicted example, patient data can be displayed in the fifth GUI 400e, including but not limited to patient weight, patient height, and patient eGFR. Patient information controls (e.g., drop-down menus), program reset buttons, event controls, and / or navigation bars can continue to be displayed in the fifth GUI 400e as they are in the third GUI 400c and the fourth GUI 400d.

[0113] In some non-limiting embodiments, the window for viewing and modifying selected injection protocol parameters may include information about the fluids used in the fluid injection procedure. For example, the window may display a medical fluid selector (e.g., a drop-down menu describing and allowing modification of the contrast fluid), a batch / volume field for the medical fluid, and an expiration date field for the medical fluid. As a further example, the window may display a saline fluid selector (e.g., a drop-down menu describing and allowing modification of the saline fluid), a batch / volume field for the saline fluid, and an expiration date field for the saline fluid. The window may also include a "Load Defaults" button to load predetermined medical fluid and saline fluid data for the injection protocol.

[0114] Specifically, Figure 7AThe fifth graphical user interface 400e depicts an illustrative window that initially disables the dose calculator function. The dose calculator of this disclosure includes a tool that automatically determines the dose of medical fluids for a patient based on patient data, without requiring the user to consult an external tool. Because the dose calculator is disabled in the fifth GUI 400e, the infusion protocol preview of the fifth GUI 400e is based on a default dose volume, which does not need to be customized for the patient based on patient data. For example, the infusion protocol preview depicts a total medical fluid volume of 10.0 ml, a total saline fluid volume of 10.0 ml, and a total infusion procedure duration of 10 seconds. The pressure limit for the infusion is set (e.g., configured and / or stored in memory) to 325 psi (above this threshold, the infusion procedure can be configured to abort). The infusion protocol preview also includes a description of the infusion procedure stages based on the current parameter settings. These stages are displayed in a series of lines, one stage per line. Each stage includes a fluid identifier (e.g., an icon describing the fluid type or lack of fluid), flow rate, volume, and infusion duration. As illustrated in the example described, the current infusion protocol specifies an infusion phase with a flow rate of 2 ml / sec, a contrast agent volume of 10.0 ml, and a contrast agent infusion duration of 5 seconds, followed by a flushing phase with a flow rate of 2 ml / sec, a saline volume of 10.0 ml, and a saline infusion duration of 5 seconds.

[0115] For reference Figure 7B , Figure 7B A non-limiting embodiment of a sixth GUI 400f for operating the method of the fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the sixth GUI 400f are for illustrative purposes only and should not be considered as a limitation of this disclosure. One or more elements of another GUI described herein may be combined with elements of the sixth GUI 400f, and one or more elements of the sixth GUI 400f may be included in other GUIs to provide the characteristics of the method for operating the fluid injection system.

[0116] The sixth GUI 400f depicts the... Figure 7AThe fifth GUI 400e has a substantially similar explanatory window, but with the dose calculator enabled. Users can select a button (e.g., a toggle switch) to activate the dose calculator. Once enabled, certain parameters of the infusion protocol can be updated and determined based on patient data. For example, workstation device 106 can identify from a programmed data sheet (e.g., a contrast fluid with a concentration of 1 mmol / ml), a default dose (e.g., 0.1 ml / kg, also from a programmed data sheet), a patient dose based on patient data (in ml / kg) (e.g., from a programmed data sheet based on the patient's age and / or weight), and a total dose volume calculated based on patient data (in ml) (e.g., determining the patient's weight by converting 187 pounds to 85 kg and multiplying the patient's weight by the dose or patient dose to determine a total volume of 8.5 ml). With the dose calculator enabled, the infusion protocol preview is updated to a more precise set of custom parameters for the infusion protocol of the fluid infusion procedure. For example, the injection protocol preview depicts a total medical fluid volume of 8.5 ml, a total saline volume of 10.0 ml, and a total injection procedure duration of 9 seconds. These phases have been updated to an injection phase with a flow rate of 2 ml / s, a contrast agent volume of 8.5 ml, and a contrast agent injection duration of 4 seconds, followed by a flushing phase with a flow rate of 2 ml / s, a saline volume of 10.0 ml, and a saline injection duration of 5 seconds. In this way, the parameters of the injection protocol are automatically generated without the user needing to consult external tools / manuals. From this point, the user can check and confirm the final parameters of the injection protocol, which can be used to execute the fluid injection procedure by instructing the fluid injection system.

[0117] For reference Figure 7C , Figure 7C A non-limiting embodiment of a seventh GUI 400g for operating the method of the fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the seventh GUI 400g are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the seventh GUI 400g, and one or more elements of the seventh GUI 400g may be included in other GUIs to provide the characteristics of the method for operating the fluid injection system.

[0118] The seventh GUI 400g depicts... Figure 7B The sixth GUI 400f has a basically the same explanatory window, but the dose calculator feature is fully integrated as part of the preset injection protocol. In particular, the seventh GUI 400g can respond to user selections in... Figure 6AThe preset "breast" injection protocol shown in the third GUI 400c is displayed. Patient data can be automatically retrieved from the patient records of the hospital information system 108 and displayed in the seventh GUI 400g. Furthermore, the parameters of the injection protocol can be automatically calculated based on patient data (e.g., patient weight) and are also displayed in the seventh GUI 400g. For this purpose, the recommended medical fluid and the recommended saline fluid are displayed. The injection and flushing phases are configured based on the selected anatomical region identifier "breast". Additionally, the workstation device 106 can identify the total dose volume (ml) calculated based on the patient data (e.g., 8.5 ml derived from the dose and patient weight). As shown, the injection protocol preview depicts the automatically generated total medical fluid volume of 8.5 ml, the total saline fluid volume of 20.0 ml, and the total injection procedure duration of 14 seconds. The planned fluid infusion procedure was also divided into phases, including an infusion phase with a flow rate of 2 ml / sec, a contrast agent volume of 8.5 ml, and an infusion duration of 4 seconds, followed by a flushing phase with a flow rate of 2 ml / sec, a saline volume of 20.0 ml, and an infusion duration of 10 seconds. In this way, the parameters of the infusion protocol are automatically generated without the user needing to consult external tools / manuals. From this point, the user can check and confirm the final parameters of the infusion protocol, which can be used to execute the fluid infusion procedure by instructing the fluid infusion system.

[0119] For reference Figure 7D , Figure 7D A non-limiting embodiment of an eighth GUI 400h for operating the described method of a fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the eighth GUI 400h are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the eighth GUI 400h, and one or more elements of the eighth GUI 400h may be included in other GUIs to provide the characteristics of the described method for operating the fluid injection system.

[0120] The eighth GUI 400h describes the relationship with Figure 7C The seventh GUI 400g has essentially the same explanatory window, but is designed for different patients undergoing fluid injection procedures based on their cardiac anatomy. Specifically, the eighth GUI 400h can respond to user input... Figure 5 In the second GUI 400b, the patient "Wei Zhang" is selected and displayed, followed by... Figure 6AThe third GUI 400c shows the preset "heart" injection protocol. Patient data can be automatically retrieved from the patient records of the hospital information system 108 and displayed in the eighth GUI 400h. Furthermore, the parameters of the injection protocol can be automatically calculated based on patient data (e.g., patient weight) and also displayed in the eighth GUI 400h. For this purpose, the recommended medical fluid and the recommended saline fluid are displayed. Because the preset injection protocol for the "heart" anatomical region requires two injection phases and two saline phases separated by a holding phase, the workstation device 106 has automatically generated the phases of the corresponding fluid injection procedure. As shown, the injection protocol preview depicts the automatically generated total medical fluid volume of 8.4 ml, the total saline fluid volume of 40.0 ml, and the total injection procedure duration of 10 minutes and 12 seconds. The planned fluid infusion procedure has been broken down into stages, including: a first infusion stage with a flow rate of 4 mL / s, a contrast agent volume of 4.2 mL, and an infusion duration of 1 second; followed by a first flushing stage with a flow rate of 4 mL / s, a saline volume of 20.0 mL, and a saline infusion duration of 5 seconds; then a hold stage (e.g., in which no fluid is infused) lasting 10 minutes; followed by a second infusion stage with the same parameters as the first infusion stage; and then a second flushing stage with the same parameters as the first flushing stage. In this way, the parameters of the infusion protocol are automatically generated without the user needing to consult external tools / manuals. At this point, the user can view and confirm the final parameters of the infusion protocol and execute the fluid infusion procedure by instructing the fluid infusion system.

[0121] For reference Figure 7E , Figure 7E A non-limiting embodiment of the ninth GUI 400i for operating the fluid injection system is shown. It should be understood that the precise style, arrangement, and configuration of the interface components of the ninth GUI 400i are for illustrative purposes only and should not be considered as limiting this disclosure. One or more elements of another GUI described herein may be combined with elements of the ninth GUI 400i, and one or more elements of the ninth GUI 400i may be included in other GUIs to provide the characteristics of the method for operating the fluid injection system.

[0122] The ninth GUI 400i depicts... Figure 7C The seventh GUI 400g has essentially the same explanatory window, but is used for unidentified (e.g., anonymous, unknown) patients. Specifically, the ninth GUI 400i can respond to user selections. Figure 5 The second GUI400b shows the "Unknown Patient" button, followed by... Figure 6AThe third GUI 400c displays the "Breast" preset injection protocol. Because the "Unknown Patient" button is associated with an identifier unrelated to patient records, patient data is not automatically retrieved from the patient records of the hospital information system 108. Instead, the ninth GUI 400i notifies the user that patient data, specifically patient weight, is required. Once the user has entered the patient weight data, the workstation device 106 can automatically generate parameters for the injection protocol based on the entered patient data. The automatically generated parameters can be populated in the injection protocol preview window, very similar to that in the seventh GUI 400g. From then on, the user can check and confirm the final parameters of the injection protocol, which can be used to execute the fluid injection procedure by instructing the fluid injection system.

[0123] Now for reference Figure 8 , Figure 8 A non-limiting embodiment of a medical imaging kit 800 is illustrated. The medical imaging kit 800 may be located in a hospital and / or imaging center for performing imaging procedures on a patient for the purpose of diagnosing diseases and / or other abnormalities. The medical imaging kit 800 may include a scanning room 814 and a control room 816, with a fluid infusion system 804 and a medical imaging system 806 located in the scanning room 814. An individual (e.g., a radiologist, technician, or other medical personnel) can monitor the patient from the control room 816 via one or more workstation devices 802 associated with the fluid infusion system 804 and / or the medical imaging system 806. The fluid infusion system 804 may include a multi-fluid delivery system, such as MEDRAD provided by Bayer HealthCare LLC. ® MR injection system of MRXperion. In some non-limiting embodiments, fluid injection system 804 may be the same as or similar to fluid injection system 104. In some non-limiting embodiments, workstation device 802 including display unit 808 may be the same as or similar to workstation device 106. In some non-limiting embodiments, injection protocol management system 102 may be a component of workstation device 802. Figure 8 As shown, workstation device 802 can be used (e.g., by medical personnel) to set up and / or perform fluid injection procedures for a patient. In some non-limiting embodiments, workstation device 802 may provide a user interface (e.g., an application-based user interface, a web-based user interface, etc.) on display unit 808 for controlling fluid injection system 804 and medical imaging system 806. Parameters of the injection protocol for the fluid injection procedure may be automatically generated by injection protocol management system 102 and, in some non-limiting embodiments, displayed on workstation device 802 and / or transmitted to fluid injection system 804 to execute the fluid injection procedure.

[0124] For reference Figure 9 , Figure 9 It shows Figure 8 An enlarged partial view of the fluid injection system 804 shown, particularly the scanning chamber unit 805 (e.g., MEDRAD). ® Non-limiting embodiments of the MRXperion MR injection system. In some non-limiting embodiments, the scanning chamber unit 805 includes a base 811 mounted to a base 813, with lockable casters 817 secured at the bottom to the base 813 for moving the scanning chamber unit 805 within the scanning chamber 814 as needed during imaging procedures. While primarily used to support the injector head 850 of the scanning chamber unit 805, the base 811 also includes an integrated IV rod 818, which includes one or more hooks 819 for suspending minimally heavy IV-related accessories. In some non-limiting embodiments, the base 813 houses various electronic and communication components as well as the power supply for the scanning chamber unit 805. In other connections, such as Figure 8 As shown, the scanning chamber unit 805 has a power cable 821 for transmitting power to a power source through a through panel 807 and an optical fiber link 822 for communicating with a workstation device 802 in a control room 816 via the optical fiber link 822 to control the operation of the fluid injection system 804.

[0125] Now for reference Figure 10 , Figure 10 It shows Figure 9 The scanning chamber unit 805 shown (e.g., MEDRAD) ® A non-limiting embodiment of the injector head 850 of the MRXperion MR injection system. (e.g.) Figure 10 As shown, the injector head 850 may include a housing 851 and at least one fluid reservoir 860a / 860b, such as a syringe. In some non-limiting embodiments, the fluid injection system may include a drive component for controlling the inflow or outflow of fluid into the fluid reservoir, such as a piston associated with each fluid reservoir 860a / 860b that drives an associated plunger within the cylinder of the fluid reservoir 860a / 860b. In some non-limiting embodiments, each fluid reservoir 860a / 860b is adapted to be releasably engaged with the housing 851 at a port 855. Each fluid reservoir 860a / 860b of the fluid injection system is configured to be filled with at least one medical fluid F, such as an imaging contrast medium, a saline solution, and / or any desired medical fluid. In some non-limiting embodiments, the fluid injection system 804 may be a multi-syringe injector, as shown, wherein two fluid reservoirs 860a / 860b may be oriented side-by-side or in another spatial relationship and are individually actuated by a corresponding piston associated with the fluid injection system.

[0126] In some non-limiting embodiments, the fluid infusion system 804 can be used during a medical procedure to infuse at least one medical fluid F into a patient's vascular system by selectively actuating a plunger associated with each fluid reservoir 860a / 860b and its respective actuation component. For each fluid reservoir, during perfusion, purging, and / or fluid delivery steps, the actuation component can move the plunger toward the distal end 861 of the fluid reservoir to expel fluid F from the fluid reservoir into and through the fluid pathway kit 1000. In some non-limiting embodiments, the fluid pathway kit 1000 may include at least one tube or tube assembly configured to be in fluid communication with each fluid reservoir 860a / 860b, such that each fluid reservoir is in fluid communication with a flexible drug delivery tubing and an associated catheter for delivering fluid F from each or both fluid reservoirs 860a / 860b to the patient's vascular access site.

[0127] In some non-limiting embodiments, the injector head 850 may include a variety of control buttons and indicators that monitor and influence the operation of the fluid infusion system 804. For example, an operator may use manual knobs 861a / 861b to assist in the infusion of the tubing(s) kit and to help ensure proper placement of the catheter in the patient and to check the patency of the fluid connection to the patient. The injector head 850 may also include an infusion button 870 that, when pressed, initiates the infusion function and illuminates to indicate to the operator that infusion can begin. The injector head 850 may also include a start / hold button 871 and an abort button 872, wherein the start / hold button 871, when pressed, initiates the infusion procedure when the fluid infusion system 804 is ready, and the abort button 872, when pressed, terminates the ongoing infusion procedure, thereby deactivating the fluid infusion system 804. The injector head 850 may also have forward and backward piston control buttons 873 and 874, and an actuation piston control button 875 to activate buttons 873 and 874, thereby enabling them to be used to advance and retract the piston. In some non-limiting embodiments, the injector head 850 may include a variety of other control buttons and indicators, such as those described in MEDRAD published by Bayer Medical Care Inc. in January 2021. ® The descriptions in the MRXperion MR Injection System Operation Manual are incorporated herein by reference.

[0128] Although the above-described systems, methods, and computer program products have been described in detail based on embodiments currently considered most practical and preferred, it should be understood that such detailed description is for this purpose only, and this disclosure is not limited to the described embodiments or aspects, but rather is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that this disclosure contemplates that, to the extent possible, at least one feature of any embodiment or aspect may be combined with at least one feature of any other embodiment.

Claims

1. A system for operating a fluid injection system, comprising: At least one processor is programmed or configured to: Receive patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient's weight; Based on the patient data and independently of inputs associated with the dose of the medical fluid used in the fluid infusion procedure, at least one parameter for the infusion protocol of the fluid infusion procedure is automatically generated, the input being received via a user interface associated with the fluid infusion system performing the fluid infusion procedure, wherein, when the at least one parameter is automatically generated, the at least one processor is programmed or configured to: The dosage of the medical fluid used in the fluid infusion procedure is determined based on the following: The patient's weight, The concentration of the medical fluid, The anatomical area of ​​the patient in which the fluid injection procedure is performed, or Any combination of them; and Provide the fluid injection system with at least one parameter of the injection protocol.

2. The system of claim 1, further comprising a display unit, wherein the at least one processor is further programmed or configured to: Displaying multiple patient identifiers in the user interface on the display unit; and Receive selection of a patient identifier from the plurality of patient identifiers via the user interface; in, When the patient data is received, the at least one processor is programmed or configured to: The patient data is received based on the selection of the patient identifier received via the user interface.

3. The system according to claim 1, wherein, When the patient data is received, the at least one processor is programmed or configured to: The patient data is received from user input via a user interface displayed on the display unit.

4. The system according to claim 1, wherein, The patient data associated with the patient undergoing the fluid injection procedure corresponds to the patient's patient record stored in a hospital information system, and wherein the at least one processor is further programmed or configured to: Transmit the unique identifier associated with the patient's patient record to the hospital information system; and When receiving the patient data, the at least one processor is programmed or configured to: Receive the patient data from the hospital information system.

5. The system according to claim 1, wherein, When at least one parameter of the injection protocol for the fluid injection procedure is automatically generated, the at least one processor is further programmed or configured to: Determine a first dose of the medical fluid for the first injection phase of the fluid injection procedure; Determine a first flushing phase of the fluid injection procedure, wherein the first flushing phase includes the first injection of physiological saline fluid; The second dose of the medical fluid for the second injection phase of the fluid injection procedure is determined based on at least one of the following: The patient's weight, The concentration of the medical fluid, The anatomical region, or Any combination of them; and A second flushing phase is defined in the fluid injection procedure, wherein the second flushing phase includes a second injection of physiological saline fluid.

6. The system according to claim 5, wherein, The at least one processor is further programmed or configured to: The fluid injection procedure is executed in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

7. The system according to claim 5, wherein, When at least one parameter of the injection protocol for the fluid injection procedure is automatically generated, the at least one processor is programmed or configured to: A first flow rate of the medical fluid for the first injection phase is determined based on the concentration of the medical fluid and the anatomical region. as well as A second flow rate of the medical fluid for the second injection phase is determined based on the concentration of the medical fluid and the anatomical region.

8. The system according to claim 1, further comprising a display unit, wherein, The at least one processor is further programmed or configured to: Display multiple anatomical region identifiers in the user interface on the display unit; and The user interface receives a selection of an anatomical region identifier from the plurality of anatomical region identifiers. Wherein, when at least one parameter of the injection protocol for the fluid injection procedure is automatically generated, the at least one processor is programmed or configured to: Based on the selection of the anatomical region identifier received via the user interface, the type of medical fluid, the concentration of the medical fluid, and the anatomical region of the patient in which the fluid injection procedure will be performed are determined.

9. A method for operating a fluid injection system, comprising: At least one processor receives patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient’s weight; At least one parameter of the injection protocol for the fluid injection procedure is automatically generated using at least one processor, and independently of inputs related to the dose of the medical fluid for the fluid injection procedure received via a user interface associated with the fluid injection system, the fluid injection system performing the fluid injection procedure based on the patient data, wherein automatically generating the at least one parameter includes: The dosage of the medical fluid used in the fluid infusion procedure is determined based on the following: The patient's weight, The concentration of the medical fluid, or The anatomical area of ​​the patient in which the fluid injection procedure will be performed; or Any combination of them; and At least one parameter of the injection protocol is provided by at least one processor.

10. The method of claim 9, further comprising: Display multiple patient identifiers in the user interface on the display unit; and Receive selection of a patient identifier from the plurality of patient identifiers via the user interface; Receiving the patient data includes: The patient data is received based on the selection of the patient identifier received via the user interface.

11. The method according to claim 10, wherein, The patient data associated with the patient undergoing the fluid infusion procedure corresponds to the patient's patient record stored in a hospital information system, and the method further includes: Transmit the unique identifier associated with the patient's patient record to the hospital information system; and Receiving the patient data includes: Receive the patient data from the hospital information system.

12. The method according to claim 9, wherein, Receive patient data, including: The patient data is received from user input via a user interface displayed on the display unit.

13. The method according to claim 9, wherein, Automatically generating at least one parameter of the injection protocol for the fluid injection procedure, further comprising: Determine a first dose of the medical fluid for the first injection phase of the fluid injection procedure; The first flushing phase of the fluid injection procedure, which includes the first injection of physiological saline fluid, is determined. A second dose of the medical fluid for the second injection phase of the fluid infusion procedure is determined based on at least one of the following: the patient's weight, the concentration of the medical fluid, or the anatomical region; and A second flushing phase is defined, which includes a second injection of the saline fluid.

14. The method of claim 13, further comprising: The fluid injection procedure is performed in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

15. The method according to claim 13, wherein, Automatically generating at least one parameter of the injection protocol for the fluid injection procedure, further comprising: Based on the concentration of the medical fluid and the anatomical region of the patient in which the fluid injection procedure will be performed, a first flow rate of the medical fluid for the first injection phase is determined; and A second flow rate of the medical fluid for the second injection phase is determined based on the concentration of the medical fluid and the anatomical region of the patient in which the fluid injection procedure will be performed.

16. The method of claim 9, further comprising: Display multiple anatomical region identifiers in the user interface on the display unit; and The user interface receives a selection of an anatomical region identifier from the plurality of anatomical region identifiers. The automatic generation of at least one parameter for the injection protocol used in the fluid injection procedure includes: Based on the selection of the anatomical region identifier received via the user interface, the medical fluid, the concentration of the medical fluid, and the anatomical region of the patient in which the fluid injection procedure will be performed are determined.

17. A computer program product for operating a fluid injection system, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, which, when executed by at least one processor, cause the at least one processor to: Receive patient data associated with a patient undergoing a fluid infusion procedure, wherein the patient data includes data associated with the patient's weight; Based on the patient data and independently of inputs associated with the dosage of the medical fluid used in the fluid injection procedure, at least one parameter for the injection protocol of the fluid injection procedure is automatically generated, the inputs being received via a user interface associated with the fluid injection system performing the fluid injection procedure. The one or more instructions that cause the at least one processor to automatically generate the at least one parameter cause the at least one processor to: The dosage of the medical fluid used in the fluid infusion procedure is determined based on at least one of the following: The patient's weight, The concentration of the medical fluid, or The anatomical area of ​​the patient in which the fluid injection procedure will be performed; and Provide the fluid injection system with at least one parameter of the injection protocol.

18. The computer program product according to claim 17, wherein, The one or more instructions also cause the at least one processor to: Displaying multiple patient identifiers in the user interface on the display unit; and Receive selection of a patient identifier from the plurality of patient identifiers via the user interface; Wherein, the one or more instructions that cause the at least one processor to receive the patient data cause the at least one processor to: The patient data is received based on the selection of the patient identifier received via the user interface.

19. The computer program product according to claim 17, wherein, The patient data associated with the patient undergoing the fluid injection procedure corresponds to the patient's patient record stored in a hospital information system, and wherein the one or more instructions further cause the at least one processor to: Transmit the unique identifier associated with the patient's patient record to the hospital information system; and Wherein, the one or more instructions that cause the at least one processor to receive the patient data cause the at least one processor to: Receive the patient data from the hospital information system.

20. The computer program product according to claim 17, wherein, The one or more instructions that cause the at least one processor to automatically generate at least one parameter of the injection protocol for the fluid injection procedure also cause the at least one processor to: Determine a first dose of the medical fluid for the first injection phase of the fluid injection procedure; Determine a first flushing phase of the fluid injection procedure, wherein the first flushing phase includes the first injection of physiological saline fluid; The second dose of the medical fluid for the second injection phase of the fluid injection procedure is determined based on at least one of the following: The patient's weight, The concentration of the medical fluid, The anatomical region, or Any combination of them; and Determine a second flushing phase of the fluid injection procedure, wherein the second flushing phase includes a second injection of physiological saline fluid; and Wherein, the one or more instructions further cause the at least one processor to: The fluid injection procedure is executed in the order of the first injection phase, the first flushing phase, the holding phase, the second injection phase, and the second flushing phase.

Images