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

Abstract

A system for operating a fluid infusion system may include at least one processor to receive patient data relating to a patient receiving a fluid infusion procedure, and to automatically generate at least one parameter of an infusion protocol for a fluid infusion procedure based on the patient data and independently of input relating to the dosage of the drug solution for the fluid infusion procedure received via a user interface relating to the fluid infusion system performing the fluid infusion procedure, wherein the at least one processor determines the dosage of the drug solution for the fluid infusion procedure when automatically generating at least one parameter and provides the at least one parameter of the infusion protocol to the fluid infusion system. Methods and computer program products are also disclosed.

Description

Technical Field

[0001] The present disclosure generally relates to control systems and / or devices related to medical devices, and in some non-limiting embodiments, to systems, methods, and computer program products for operating a fluid infusion system

Background Art

[0002] Infusion devices, such as fluid infusion devices (e.g., drug delivery devices), can be used by medical personnel, such as physicians, in medical diagnostic procedures and / or medical treatment procedures. For example, medical personnel may use a fluid infusion device to inject one or more drugs into a patient. Fluid infusion devices can be used for the pressure injection of drugs such as radiographic contrast materials (e.g., contrast agents, radiographic contrast agents, contrast media, etc.) and / or flushing agents such as physiological saline 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 certain amount of drug to a patient at one or more flow rates

Summary of the Invention

Problems to be Solved by the Invention

[0003] Therefore, there are provided systems, methods, and computer program products for operating a fluid infusion system that improve the efficiency and accuracy of infusion protocol generation for delivering drugs to a patient during a fluid infusion procedure

Means for Solving the Problems

[0004] Further non-limiting embodiments or aspects are described in the clauses numbered below

[0005] Clause 1: A system for operating a fluid infusion system, comprising at least one processor, which is programmed or configured to receive patient data relating to a patient receiving a fluid infusion procedure, the patient data including data relating to the patient's weight, and to automatically generate at least one parameter of an infusion protocol for a fluid infusion procedure, based on the patient data and independent of input relating to the dosage of a drug solution for the fluid infusion procedure received via a user interface relating to a fluid infusion system performing the fluid infusion procedure, the at least one processor being programmed or configured to determine the dosage of the drug solution for the fluid infusion procedure based on the patient's weight, the concentration of the drug solution, the anatomical region of the patient to which the fluid infusion procedure is to be performed, or any combination thereof, and to provide the at least one parameter of the infusion protocol to the fluid infusion system.

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

[0007] Clause 3: The system described in Clause 1 or 2, wherein upon receiving patient data, at least one processor is programmed or configured to receive patient data from user input via a user interface displayed on a display unit.

[0008] Clause 4: The system described in any one of Clauses 1 to 3, wherein patient data relating to a patient receiving a fluid infusion procedure corresponds to the patient's patient record stored in the hospital information system, and at least one processor is further programmed or configured to transmit a unique identifier relating to the patient's patient record to the hospital information system, and upon receiving patient data, at least one processor is programmed or configured to receive patient data from the hospital information system.

[0009] Clause 5: The system according to any one of Clauses 1 to 4, wherein when automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure, at least one processor is further programmed or configured to determine: a first dose of a drug solution for a first infusion stage of the fluid infusion procedure; a first flush stage of the fluid infusion procedure, wherein the first flush stage includes a first infusion of saline; a second dose of a drug solution for a second infusion stage of the fluid infusion procedure, based on at least one of the patient's body weight, the concentration of the drug solution, an anatomical region, or any combination thereof; and a second flush stage of the fluid infusion procedure, wherein the second flush stage includes a second infusion of saline.

[0010] Clause 6: The system according to any one of Clauses 1 to 5, wherein at least one processor is further programmed or configured to perform a fluid injection procedure in the order of a first injection step, a first flush step, a holding step, a second injection step, and a second flush step.

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

[0012] Clause 8: The system according to any one of Clauses 1 to 7, further comprising a display unit, wherein at least one processor is programmed or configured to display a plurality of anatomical region identifiers on a user interface on the display unit and to receive a selection of anatomical region identifiers of the plurality of anatomical region identifiers via the user interface, and when automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure, the at least one processor is programmed or configured to determine, based on the selection of anatomical region identifiers received via the user interface, the type of drug solution, the concentration of the drug solution, and the anatomical region of the patient to which the fluid infusion procedure should be performed.

[0013] Clause 9: A method for operating a fluid infusion system, comprising: receiving patient data relating to a patient receiving a fluid infusion procedure, the patient data including data relating to the patient's weight, using at least one processor; generating at least one parameter of an infusion protocol for a fluid infusion procedure, using at least one processor, independently of input relating to the dosage of a drug solution for the fluid infusion procedure, received via a user interface associated with the fluid infusion system that performs the fluid infusion procedure based on the patient data, wherein the step of automatically generating at least one parameter includes a step of determining the dosage of the drug solution for the fluid infusion procedure based on the patient's weight, the concentration of the drug solution, or the anatomical region of the patient to which the fluid infusion procedure is to be performed, or any combination thereof; and providing at least one parameter of an infusion protocol, using at least one processor.

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

[0015] Clause 11: The method according to Clause 9 or Clause 10, wherein patient data relating to a patient receiving a fluid infusion procedure corresponds to the patient's patient record stored in a hospital information system, and the method further includes the step of transmitting a unique identifier relating to the patient's patient record to the hospital information system, and the step of receiving patient data includes the step of receiving patient data from the hospital information system.

[0016] Clause 12: The method described in any one of Clauses 9 to 11, wherein the step of receiving patient data includes the step of receiving 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 the step of automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure further includes: determining a first dose of a drug solution for a first infusion stage of a fluid infusion procedure; determining a first flush stage of a fluid infusion procedure, which includes a first infusion of saline; determining a second dose of a drug solution for a second infusion stage of a fluid infusion procedure, which includes a second infusion of saline, based on at least one of the patient's body weight, the concentration of the drug solution, or an anatomical region; and determining a second flush stage, which includes a second infusion of saline.

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

[0019] Clause 15: The method according to any one of Clauses 9 to 14, wherein the step of automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure further includes the steps of determining a first flow rate of the drug solution for a first infusion stage based on the concentration of the drug solution and the anatomical region of the patient in which the fluid infusion procedure is to be performed, and determining a second flow rate of the drug solution for a second infusion stage based on the concentration of the drug solution and the anatomical region of the patient in which the fluid infusion procedure is to be performed.

[0020] Clause 16: The method according to any one of Clauses 9 to 15, comprising the steps of displaying a plurality of anatomical region identifiers on a user interface on a display unit, receiving a selection of the plurality of anatomical region identifiers via the user interface, and automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure, the steps of determining a drug solution, the concentration of the drug solution, and the anatomical region of the patient to which the fluid infusion procedure should be performed, based on the selection of anatomical region identifiers received via the user interface.

[0021] Clause 17: A computer program product for operating a fluid infusion system, the computer program product comprising at least one non-temporary computer-readable medium comprising one or more instructions that cause at least one processor to receive patient data relating to a patient undergoing a fluid infusion procedure, wherein the patient data includes data relating to the patient's weight, and to automatically generate at least one parameter of an infusion protocol for a fluid infusion procedure, based on the patient data and independent of input relating to the dosage of a drug solution for the fluid infusion procedure received via a user interface relating to a fluid infusion system performing the fluid infusion procedure, wherein one or more instructions that cause at least one processor to automatically generate at least one parameter is configured to cause at least one processor to determine the dosage of a drug solution for the fluid infusion procedure based on at least one of the patient's weight, the concentration of the drug solution, or at least one anatomical region of the patient to which the fluid infusion procedure is to be performed, and to provide at least one parameter of an infusion protocol to the fluid infusion system.

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

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

[0024] Clause 20: One or more instructions that cause at least one processor to automatically generate at least one parameter of an injection protocol for a fluid injection procedure cause the at least one processor to determine a first dosage of a medicament for a first injection stage of the fluid injection procedure and to determine a first flush stage of the fluid injection procedure, the first flush stage including a first injection of physiological saline, and to determine a second dosage of a medicament for a second injection stage of the fluid injection procedure based on at least one of the patient's weight, the concentration of the medicament, the anatomical region, or any combination thereof, and to determine a second flush stage of the fluid injection procedure, the second flush stage including a second injection of physiological saline, and 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 stage, the first flush stage, the hold stage, the second injection stage, and the second flush stage, a computer program product according to any one of Clauses 17 to 19.

[0025] These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of the structure, as well as the combinations of parts and the economics of manufacture, will become more apparent upon consideration of the following description and the appended claims, with reference to the accompanying drawings, all of which form a part of this specification, and like reference numerals indicate corresponding parts of various figures. However, it should be clearly understood that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the present disclosure. As used in this specification and the appended claims, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise.

[0026] Additional advantages and details of non-limiting embodiments or aspects are described in more detail below with reference to the exemplary embodiments shown in the accompanying schematic drawings.

Brief Description of the Drawings

[0027] [Figure 1A]FIG. 0 is a diagram of a non-limiting embodiment of an environment in which a system, apparatus, product, device, and / or method described herein can be implemented in accordance with the principles of the present disclosure. [Figure 1B] FIG. 3 is a diagram of a non-limiting embodiment of a system for automatically generating an infusion protocol for delivering a pharmaceutical solution to a patient during a fluid infusion procedure. [Figure 2] FIG. 6 is a diagram of a non-limiting embodiment of one or more components of the system of FIGS. 1A and 1B, or one or more devices. [Figure 3] FIG. 9 is a flowchart of a non-limiting embodiment of a process for operating a fluid infusion system. [Figure 4] FIG. 12 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 5] FIG. 15 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 6A] FIG. 18 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 6B] FIG. 21 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 7A] FIG. 24 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 7B] FIG. 27 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 7C] FIG. 30 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 7D] FIG. 33 is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid infusion system. [Figure 7E] This is a diagram of a non-limiting embodiment of a user interface on a display screen for use in a method for operating a fluid injection system. [Figure 8] This is a diagram of a non-limiting embodiment of an environment including a workstation device and a fluid injection system. [Figure 9] This is a diagram of a non-limiting embodiment of a fluid injection system. [Figure 10] This is a diagram of a non-limiting embodiment of an injector head unit of a fluid injection system. [Modes for carrying out the invention]

[0028] For the purposes of the following description, the terms “end,” “top,” “bottom,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and their derivatives shall be relevant to the disclosure when oriented in the drawings. However, it should be understood that the disclosure may envision various alternative variations and step sequences unless expressly otherwise specified. It should also be understood that the particular apparatus and processes shown in the accompanying drawings and described in the following specification are merely exemplary embodiments of the disclosure. Accordingly, specific dimensions and other physical characteristics relating to embodiments or aspects of the embodiments disclosed herein should not be considered limiting unless otherwise indicated.

[0029] The aspects, components, elements, structures, actions, steps, functions, instructions, etc., used herein should not be construed as important or essential unless expressly stated otherwise. Furthermore, where 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, where used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items) and may be used interchangeably with “one or more” or “at least one.” When only one item is intended, the term “one” or a similar term is used. Furthermore, where used herein, terms such as “has,” “have,” and “having” are intended to be open-ended terms. Additionally, the phrase “based on” is intended to mean “at least partially based” unless otherwise specified.

[0030] As used herein, the terms “communicate” and “communicate” may refer to the reception, acceptance, transmission, transfer, provision, etc., of information (e.g., data, signals, messages, instructions, commands, etc.). Communication between one unit (e.g., a device, a system, a component of a device or system, a combination thereof, and / or similar) and another unit means that one unit can directly or indirectly receive information from and / or transmit information to the other unit. This may refer to direct or indirect connections that are essentially wired and / or wireless. Furthermore, two units may communicate with each other even if the transmitted information is modified, processed, relayed, and / or routed between the first and second units. For example, the first unit may communicate with the second unit even if the first unit passively receives information and does not actively transmit information to the second unit. As another example, the first unit may communicate with the 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 communicates the processed information to the second unit. In some non-limiting embodiments, the message may refer to a network packet containing data (e.g., a data packet). It will be understood that many other arrangements are possible.

[0031] As used herein, the term “system” may refer to one or more computing devices or combinations of computing devices, including, but not limited to, processors, servers, client devices, software applications, and / or other similar components. In addition, as used herein, references to “servers” or “processors” may refer to the previously listed servers and / or processors listed as performing the preceding step or function, different servers and / or processors, and / or combinations of servers and / or processors. For example, as used herein and in the claims, the first server and / or first processor listed as performing the first step or function may refer to the same or different servers, and / or processors listed as performing the second step or function.

[0032] In some cases, a fluid infusion system may be part of a group of devices used in medical treatment facilities such as hospitals during patient treatment, and / or in medical imaging facilities. A healthcare provider (e.g., personnel operating a magnetic resonance imaging (MRI) machine) may use a workstation device to provide parameters for an infusion protocol for a fluid infusion procedure to be administered by the fluid infusion system. The parameters may be provided as manually entered inputs by the user. However, the infusion protocol may need to be customized to the specific patient receiving the fluid infusion procedure so that the relevant medical and / or assessments are performed correctly, and / or the patient is not harmed by the infusion. For example, a particular drug solution to be infused in a fluid infusion procedure may need to be administered precisely on a patient basis and infused at a specific flow rate for best results.

[0033] The described systems, methods, and computer program products generate infusion protocols for fluid infusion systems and improve the accuracy and efficiency of operating fluid infusion procedures. In some non-limiting embodiments, the infusion protocol management system may receive patient data relating to a patient receiving a fluid infusion procedure, and may automatically generate at least one parameter of the infusion protocol for the fluid infusion procedure based on the patient data, and provide at least one parameter of the infusion protocol to the fluid infusion system. In some non-limiting embodiments, the patient data may include data relating to the patient's weight. In some non-limiting embodiments, when automatically generating at least one parameter, the infusion protocol management system may determine a first dose of the drug solution for the fluid infusion procedure based on at least one of the patient's weight, the concentration of the drug solution, or the anatomical region of the patient to which the fluid infusion procedure is to be performed.

[0034] In some non-limiting embodiments, the infusion protocol management system may include a display unit, which may display a plurality of patient identifiers on a user interface on the display unit, and then receive a selection of patient identifiers from among the plurality of patient identifiers via the user interface. In some non-limiting embodiments, the patient identifiers may include unique identifiers associated with patient records, and receiving patient data based on a selection of patient identifiers 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 identifiers may include identifiers not associated with patient records, and the infusion protocol management system may receive patient data based on a selection of patient identifiers received via the user interface. In some non-limiting embodiments, the infusion protocol management system may receive patient data from user input via the user interface.

[0035] In some non-limiting embodiments, when determining a first dose of a drug solution for a fluid infusion procedure, the infusion protocol management system may determine a first dose of a drug solution for a first infusion stage of the fluid infusion procedure; when automatically generating at least one parameter of the infusion protocol for a fluid infusion procedure, the infusion protocol management system may determine a first flush stage of the fluid infusion procedure, including a first infusion of saline; and based on at least one of the patient's body weight, the concentration of the drug solution, or an anatomical region, the infusion protocol management system may determine a second dose of a drug solution for a second infusion stage of the fluid infusion procedure, including a second infusion of saline. In some non-limiting embodiments, the infusion protocol management system may perform the fluid infusion procedure in the order of a first infusion stage, a first flush stage, a holding stage, a second infusion stage, and a second flush stage. In some non-limiting embodiments, when automatically generating at least one parameter of an injection protocol for a fluid injection procedure, the injection protocol management system may determine a first flow rate of the drug solution for a first injection stage and a second flow rate of the drug solution for a second injection stage, based on the drug solution concentration and anatomical region.

[0036] In some non-limiting embodiments, the infusion protocol management system may further include a display unit, which may display a plurality of anatomical region identifiers on a user interface on the display unit. In some non-limiting embodiments, the infusion protocol management system may receive a selection of a plurality of anatomical region identifiers via the user interface. In some non-limiting embodiments, when automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure, the infusion protocol management system may determine the type of drug (e.g., name, identifier, etc.), the concentration of the drug, and the anatomical region based on the selection of anatomical region identifiers received via the user interface.

[0037] In this way, non-limiting embodiments of the present disclosure provide faster generation of infusion protocols with fewer user steps, while also ensuring accurate parameters of the infusion protocol through the automatic generation of infusion protocol parameters based on patient data. Further computational improvements are provided by integrating the retrieval of patient data from hospital information systems, from which infusion protocol parameters can be automatically generated. (For example, this reduces network resources such as calls to devices that may be required to retrieve patient data in the process flow for generating the infusion protocol, rather than requiring the user to retrieve patient data using separate computing devices, applications, and / or process flows.) Furthermore, by automatically generating infusion protocol parameters based on patient data and / or selected anatomical regions, patient safety and the effectiveness of medical procedures are improved, thereby automatically determining parameters such as drug solution, drug concentration, flow rate, etc. This reduces the number of opportunities for human error to be introduced during the setup of infusion protocols for fluid infusion procedures.

[0038] Referring here to Figure 1A, Figure 1A is a diagram of a non-limiting embodiment of an environment 100A in which the apparatus, systems, methods, and / or computer program products described herein may be implemented. As shown in Figure 1A, the 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 (e.g., establish a connection for communication) via wired connections, wireless connections, or a combination of wired and wireless connections. Any apparatus or system in the environment 100A may communicate with each other within the same or a different communication network 110.

[0039] In some non-limiting embodiments, the infusion protocol management system 102 may include one or more devices that can communicate with the fluid injection system 104, the workstation device 106, and / or the hospital information system 108 via the communication network 110. For example, the infusion protocol management system 102 may include one or more computing devices such as one or more computers, one or more servers (e.g., a cloud server, a group of servers, etc.), one or more desktop computers, or one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.). In some non-limiting embodiments, the infusion 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 enables the infusion 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 applications may be supported by applications associated with the fluid injection system 104, enabling the infusion protocol management system 102, which may function as a control room display, to be the sole device controlling the fluid injection system 104, in which case the infusion 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.

[0040] 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, the workstation device 106, and / or the 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., a cloud server, a group of servers, etc.), one or more desktop computers, and 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 containing a contrast agent to the patient, and / or to administer an aqueous fluid such as saline to the patient before, during, and / or after the administration of the contrast fluid. For example, the fluid infusion system 104 can inject one or more prescribed doses of contrast fluid directly into the patient's bloodstream via a subcutaneous needle and syringe. In some non-limiting embodiments, the fluid infusion system 104 may be configured to continuously administer aqueous fluid to the patient through a peripheral venous line (PIV) and catheter, where one or more prescribed doses of contrast fluid are 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 inject a certain dose of contrast fluid, followed by the administration of a specific volume of aqueous fluid.In some non-limiting embodiments, the fluid injection system 104 includes one or more exemplary fluid injection devices, which include U.S. Patent Application No. 09 / 715,330, filed on 17 November 2000 and issued as U.S. Patent No. 6,643,537; U.S. Patent Application No. 09 / 982,518, filed on 18 October 2001 and issued as U.S. Patent No. 7,094,216; and U.S. Patent Application No. 1, filed on 16 April 2004 and issued as U.S. Patent No. 7,556,619. U.S. Patent Application No. 0 / 825,866, filed on 7 May 2009 and issued as U.S. Patent No. 8,337,456, U.S. Patent Application No. 12 / 476,513, filed on 2 June 2009 and issued as U.S. Patent No. 8,147,464, and U.S. Patent Application No. 11 / 004,670, filed on 3 December 2004 and issued as U.S. Patent No. 8,540,698, each of which disclosures are incorporated herein by reference in their entirety. In some non-limiting embodiments, the fluid injection system 104 may include the MEDRAD® Stellant CT Injection System, the MEDRAD® Stellant FLEX CT Injection System, the MEDRAD® MRXperion MR Injection System, the MEDRAD® Mark 7 Arterion Injection System, the MEDRAD® Intego PET Infusion System, or the MEDRAD® Centargo CT Injection System, all of which are supplied by Bayer Healthcare LLC.

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

[0042] In some non-limiting embodiments, the hospital information system 108 may include one or more devices capable of communicating with the infusion protocol management system 102, the fluid infusion 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, and one or more servers. 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 modality work lists, a system for providing patient demographic information for fluid infusion procedures and / or medical imaging procedures), a fluid infusion management system, an image archiving and communication system (e.g., an image archiving and communication system (PACS)), a radiology information system (RIS), and / or a radiology analysis system (e.g., Radimetrics® Enterprise Application, sold and distributed by Bayer HealthCare LLC). In some non-limiting embodiments, the hospital information system 108 may include one or more databases that store patient records (e.g., data file data objects containing patient data), which may be accessed (e.g., with read access permissions and / or write access permissions) by devices or systems within the environment 100A, such as the infusion protocol management system 102 and / or workstation device 106.

[0043] 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 cellular networks (e.g., Long-Term Evolution (LTE®) networks, 3G networks, 4G networks, 5G networks, 6G networks, Code Division Multiple Access (CDMA) networks, etc.), public land mobile networks (PLMN), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks, ad hoc networks, intranets, the Internet, fiber optic-based 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.

[0044] The number and arrangement of systems and / or devices shown in Figure 1A are provided as an example. Additional systems and / or devices, fewer systems and / or devices, different systems and / or devices, or systems and / or devices in different arrangements than those shown in Figure 1A may exist. Furthermore, two or more systems and / or devices shown in Figure 1A may be implemented within a single system or single device, or a single system or single device shown in Figure 1A may be implemented as multiple distributed systems or devices. Additionally or alternatively, a set of systems or devices in environment 100A (e.g., one or more systems, one or more devices) may perform one or more functions that are described as being performed by another set of systems or another set of devices in environment 100A.

[0045] Referring here to Figure 1B, Figure 1B is a diagram of a non-limiting embodiment of System 100B for automatically generating infusion protocols for delivering medication to a patient during a fluid infusion procedure. In some non-limiting embodiments, one or more of the functions described herein with respect to System 100B may be performed (e.g., entirely, partially, and / or similarly) by the infusion protocol management system 102. In some non-limiting embodiments, one or more of the functions described herein with respect to System 100B may be performed (e.g., entirely, partially, and / or similarly) by another device or group of devices separate from and / or including the infusion protocol management system 102, such as a fluid infusion system 104, a workstation device 106 (e.g., including a display unit 106A), a hospital information system 108, and / or a medical imaging system 112.

[0046] As shown in Figure 1B, system 100B includes an injection protocol management system 102, a fluid injection system 104, a workstation device 106 including a display unit 106A, a hospital information system 108, and a medical imaging system 112. In some non-limiting embodiments, the injection protocol management system 102 may interconnect the fluid injection system 104, the workstation device 106, the hospital information system 108, and / or the medical imaging system 112 via wired connections, wireless connections, or a combination of wired and wireless connections (e.g., by establishing connections for communication and / or by similar means).

[0047] In some non-limiting embodiments, the medical imaging system 112 may include one or more devices capable of communicating with an injection protocol management system 102, a fluid injection system 104, a workstation device 106, and / or a 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 a CT scanner and / or an MRI scanner, capable of communicating via a communication network and performing medical imaging procedures, including the use of radiographic contrast materials.

[0048] As shown in Figure 1B, the infusion protocol management system 102 may include multiple applications, such as an informatics application 202A, a data management application 202B, and an imaging system connection application 202C. In some non-limiting embodiments, the multiple applications may be stored in the memory device of the infusion protocol management system 102. In some non-limiting embodiments, each of the multiple applications may be associated with an API that enables the fluid infusion system 104 to interface with the infusion protocol management system 102 (e.g., to communicate, to establish a communication interface, etc.), and / or enables the infusion protocol management system 102 to interface with the hospital information system 108 (e.g., individual subsystems of the hospital information system 108, such as a patient treatment tracking system 208A, a fluid injector management system 208B, an image archiving and communication system 208C, a radiology information system 208D, and / or a radiology analysis system 208E).

[0049] In some non-limiting embodiments, the injection protocol management system 102 may provide a user interface (e.g., via an application including a user interface such as a web-based user interface) that enables a user to control the fluid injection system 104. For example, a user may 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 enable a user to control aspects of an informatics application 202A, a data management application 202B, and / or an imaging system connection application 202C.

[0050] As further shown in Figure 1B, the workstation device 106 may include a display unit 106A. In some non-limiting embodiments, the display unit 106A may display a user interface (e.g., a web-based user interface) provided by the injection protocol management system 102. In some non-limiting embodiments, the display unit 106A may include a computing device such as a smart display unit, a portable computer such as a tablet, a laptop, etc. In some non-limiting embodiments, the display unit 106A may include a touchscreen for receiving user input. In some non-limiting embodiments, the display unit 106A may include a display device (e.g., a monitor, screen, and / or similar for displaying visual information).

[0051] In some non-limiting embodiments, the informatics application 202A, the data management application 202B, and / or the imaging system connection application 202C may be associated with a 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 the informatics application 202A, the data management application 202B, and / or the imaging system connection application 202C. In some non-limiting embodiments, the communication interface may include a set of communication settings (e.g., protocols, standards, etc.) that enable one device (e.g., one device in the system) to communicate (e.g., telecommunicate) with another device. In some non-limiting embodiments, the informatics application 202A may provide functionality for the fluid injection system 104 to interact with the hospital information system 108 (e.g., any of several subsystems of the hospital information system 108). Additionally or alternatively, the informatics application 202A may provide data storage for the fluid injection system 104 (e.g., data related to injection protocols for fluid injection procedures performed by the fluid injection system 104). In some non-limiting embodiments, the data management application 202B may provide functions associated with file system and database management for the injection protocol management system 102. Additionally or alternatively, the data management application 202B may provide operational controls for data storage for the fluid injection system 104. In some non-limiting embodiments, the imaging system connection application 202C may provide functions for the injection protocol management system 102 and / or the fluid injection system 104 to interact with the medical imaging system 112.In some non-limiting embodiments, the imaging system connection application 202C may abstract the interfaces of the medical imaging system 112 (e.g., ISI interface, ISI2 interface, and / or Connect CT interface) into a standard format for use by the injection protocol management system 102 and / or the fluid injection system 104.

[0052] In some non-limiting embodiments, the infusion protocol management system 102 may transmit data related to images received from the medical imaging system 112 to the fluid infusion system 104 via a communication network. For example, the infusion protocol management system 102 may transmit data related to images received from the medical imaging system 112 to the fluid infusion system 104 via a communication network based on API calls from the fluid infusion system 104 to the imaging system connection application 202C. In some non-limiting embodiments, the infusion protocol management system 102 may transmit data related to fluid infusion procedures received from the fluid infusion system 104 (e.g., data related to the amount of time to inject radiographic contrast material into the patient) to the medical imaging system 112 via a communication network. For example, the infusion protocol management system 102 may transmit data related to fluid infusion procedures received from the fluid infusion system 104 to the medical imaging system 112 via a communication network based on API calls from the medical imaging system 112 to the imaging system connection application 202C (e.g., API calls for the imaging system interface (ISI), API calls for the ISI2 interface, API calls for the Connect CT interface, etc.). In some non-limiting embodiments, the medical imaging system 112 may perform a medical imaging procedure on a patient based on data including an infusion protocol related to the fluid infusion procedure. In some non-limiting embodiments, the infusion protocol management system 102 may receive data related to the operation of the medical imaging system 112 from the medical imaging system 112 via a communication network based on an API call (e.g., an API call from the infusion protocol management system 102 to the medical imaging system 112).

[0053] In some non-limiting embodiments, the infusion protocol management system 102 may provide a communication interface between the hospital information system 108 and the fluid infusion system 104 so as to provide the ability for the fluid infusion system 104 to receive data based on API calls from the fluid infusion system 104 to the infusion protocol management system 102 by the informatics application 202A. In some non-limiting embodiments, the infusion protocol management system 102 may transmit informatics-related data received from the hospital information system 108 to the fluid infusion system 104 via a communication network (e.g., communication network 110). For example, the infusion protocol management system 102 may transmit informatics-related data received from the hospital information system 108 to the fluid infusion system 104 via a communication network based on API calls from the fluid infusion system 104 to the informatics application 202A. Informatics-related data may include data related to patient identification, data related to patient imaging procedures (e.g., fluid infusion procedures and / or medical imaging procedures performed on the patient), data related to contrast fluids provided during fluid infusion procedures, the gauge of the catheter used during fluid infusion procedures, and the fluid infusion protocol for the fluid infusion procedures. In some non-limiting embodiments, the infusion protocol management system 102 may store data related to patient examination procedures and / or data related to the configuration of the fluid infusion system 104 having an informatics application 202A.

[0054] As further shown in Figure 1B, the hospital information system 108 may include multiple subsystems. These subsystems may include a patient treatment 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 infusion protocol management system 102 may receive informatics-related data from the hospital information system 108 via a communication network (e.g., a communication network 110) according to a communication protocol for communicating informatics-related data. For example, the infusion protocol management system 102 may receive data related to patient procedures from the hospital information system 108 (e.g., from the patient procedure tracking system 208A) via a communication network in accordance with the Medical Digital Image Communication (DICOM) communication protocol, data related to the operation of the fluid infusion system from the hospital information system 108 (e.g., from the fluid infusion system management system 208B) via a communication network based on API calls (e.g., API calls from the infusion protocol management system 102 to the fluid infusion system management system 208B), data related to radiographic images from the hospital information system 108 (e.g., from the image archiving and communication system 208C) via a communication network in accordance with the DICOM communication protocol, data related to patient examination procedures from the hospital information system 108 (e.g., from the radiological information system 208D) via a communication network in accordance with the Health Level Seven Standard (HL7) communication protocol, and / or data related to radiation doses during medical imaging procedures from the hospital information system 108 (e.g., from the radiological analysis system 208E) via a communication network based on API calls (e.g., API calls from the infusion protocol management system 102 to the radiological analysis system 208E).

[0055] Referring now to Figure 2, which is a diagram of exemplary components of the apparatus 200. The apparatus 200 may correspond to one or more devices of the injection protocol management system 102, one or more devices of the fluid injection system 104, and / or a workstation device 106, a hospital information system 108, and / or a medical imaging system 112. In some non-limiting embodiments, the injection protocol management system 102, the fluid injection system 104, and / or the workstation device 106, the hospital information system 108, and / or the medical imaging system 112 may include at least one apparatus 200 and / or at least one component of apparatus 200. As shown in Figure 2, the apparatus 200 may include a bus 202, a processor 204, memory 206, a storage component 208, an input component 210, an output component 212, and a communication interface 214.

[0056] Bus 202 may include components that enable communication between components of the device 200. In some non-limiting embodiments, the processor 204 may be implemented in hardware, firmware, or a combination of hardware and software. For example, the processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerator processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.). Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the processor 204.

[0057] The storage component 208 may store information related to the operation and use of the device 200, as well as / or software. For example, the storage component 208 may include, together with a corresponding drive, a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, solid-state disk, etc.), a compact disc (CD), a digital multipurpose disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of computer-readable media.

[0058] The input component 210 may include components that enable the device 200 to receive information via user input (e.g., a touchscreen display, keyboard, keypad, mouse, buttons, switches, microphone, etc.). Additionally or alternatively, the input component 210 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, accelerometer, gyroscope, actuator, etc.). The output component 212 may include components that provide output information from the device 200 (e.g., a display, speaker, one or more light-emitting diodes (LEDs), etc.).

[0059] The communication interface 214 may include transceiver-like components (e.g., transceivers, separate receivers and transmitters) that enable the device 200 to communicate with other devices via wired connections, wireless connections, or a combination of wired and wireless connections. The communication interface 214 can enable the device 200 to receive information from and / or provide information to other devices. For example, the communication interface 214 may include Ethernet interfaces, optical interfaces, coaxial interfaces, infrared interfaces, radio frequency (RF) interfaces, Universal Serial Bus (USB) interfaces, Wi-Fi® interfaces, cellular network interfaces, and the like.

[0060] The apparatus 200 may perform one or more processes described herein. The apparatus 200 may perform these processes based on a processor 204 that executes software instructions stored in a computer-readable medium such as memory 206 and / or storage component 208. A computer-readable medium (e.g., non-temporary computer-readable medium) is defined herein as a non-temporary memory device. A memory device may include a memory space located inside a single physical storage device or a memory space that extends across multiple physical storage devices.

[0061] Software instructions may be read into memory 206 and / or storage component 208 from another computer-readable medium or from another device via the communication interface 214. When executed, the software instructions stored in memory 206 and / or storage component 208 may cause the processor 204 to execute one or more processes described herein. In addition, or instead, hardwired circuits may be used instead of, or in combination with, software instructions to execute one or more processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuits and software.

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

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

[0064] As shown in Figure 3, in step 302, process 300 may include displaying a plurality of patient identifiers. For example, the infusion protocol management system 102 may display a plurality of patient identifiers on a user interface on a display unit (e.g., display unit 106A) of the workstation device 106. In some non-limiting embodiments, the plurality of 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 treatment tracking system 208A of the hospital information system 108). In some non-limiting embodiments, the plurality of patient identifiers may be displayed in a list of rows associated with a patient (e.g., as shown in Figure 5). In some non-limiting embodiments, the plurality of patient identifiers may include identifiers not associated with a patient record, such as an identifier for an unknown or unnamed patient. In some non-limiting embodiments, the plurality of 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.

[0065] As shown in Figure 3, in step 304, process 300 may include receiving a selection of a patient identifier. For example, the infusion protocol management system 102 may receive a selection of a patient identifier from among several patient identifiers via the user interface. In some non-limiting embodiments, the infusion protocol management system 102 may receive a selection of a patient identifier based on user input. For example, the user may select an identifier associated with a patient record (e.g., a patient identifier including a unique identifier) ​​by selecting an identifier within the user interface (e.g., touch, click, press, etc.). In some non-limiting embodiments, the user may select an identifier not associated with a patient record by selecting a button indicating that the patient is unknown, unnamed, etc. In the above example, the infusion protocol management system 102 may receive a selection of an identifier via the user interface based on the user selecting an identifier within the user interface.

[0066] As shown in Figure 3, in step 306, process 300 may include displaying a plurality of anatomical region identifiers. For example, the infusion protocol management system 102 may display a plurality of anatomical region identifiers on a user interface on a display unit (e.g., display unit 106A of the workstation device 106). In some non-limiting embodiments, the anatomical region identifier may include an identifier (e.g., a short description, a unique code, an image, etc.) that represents the anatomical region (e.g., the patient's anatomical region) to which the fluid infusion procedure is to be performed. For example, the fluid infusion procedure may involve injecting a drug solution, such as a contrast agent, so that an MRI scan of the patient's breast can be taken. In such an example, the anatomical region identifier may include a short description, such as the text "breast". In a further example, the anatomical region identifier may include a unique code (e.g., a collaborative magnetic imaging (CPT) code), such as "77059".

[0067] As shown in Figure 3, in step 308, process 300 may include receiving a selection of anatomical region identifiers. For example, the infusion protocol management system 102 may receive a selection of anatomical region identifiers of a plurality of anatomical region identifiers via a user interface. In some non-limiting embodiments, the user may select anatomical region identifiers by selecting anatomical region identifiers within the user interface. In some non-limiting embodiments, the infusion protocol management system 102 may receive a selection of anatomical region identifiers based on user input. For example, the user may select anatomical region identifiers related to the anatomical region of the patient to which the fluid infusion procedure is to be performed by selecting anatomical region identifiers within the user interface. In such an example, the infusion protocol management system 102 may receive a selection of anatomical region identifiers via the user interface based on the user selecting anatomical region identifiers in the user interface. In some non-limiting embodiments, the selection of anatomical region identifiers may be performed automatically by a patient selection on the workstation device 106, for example, via a trigger communicated electronically from the workstation device 106.

[0068] As shown in Figure 3, in step 310, process 300 includes receiving patient data. For example, the infusion protocol management system 102 may receive patient data related to a patient receiving a fluid infusion procedure. In some non-limiting embodiments, the patient data may include the patient's name, height, weight, age, estimated glomerular filtration rate (eGFR), sex, patient identifier (e.g., social security number, global unique code), patient acceptance number (e.g., a unique number assigned to the patient by the hospital information system 108 that 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 infusion procedure), etc. In some non-limiting embodiments, the patient data related to the patient may correspond to the patient's patient record (e.g., an existing patient record) stored in the hospital information system 108.

[0069] In some non-limiting embodiments, the infusion protocol management system 102 may transmit identifiers (e.g., unique identifiers) associated with patient records for patients receiving fluid infusion procedures to the hospital information system 108, and the infusion protocol management system 102 may also receive patient data from the hospital information system 108. In some non-limiting embodiments, the hospital information system 108 may receive identifiers associated with patient records, retrieve the patient's patient record based on the identifiers, and transmit the patient record to the infusion protocol management system 102.

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

[0071] As shown in Figure 3, in step 312, process 300 includes automatically generating at least one parameter of the infusion protocol. For example, the infusion protocol management system 102 may automatically generate at least one parameter of the infusion protocol for a fluid infusion procedure based on patient data related to the patient receiving the fluid infusion procedure. In some non-limiting embodiments, the infusion protocol management system 102 may automatically generate at least one parameter of the infusion protocol by determining the dosage (e.g., ml / kg) of the drug solution (e.g., contrast fluid) for the fluid infusion procedure. In some non-limiting embodiments, the infusion protocol management system 102 may determine the dosage based on the patient's weight (e.g., in kilograms, which may be converted from pounds), the concentration of the drug solution (e.g., mmol / ml) used in the fluid infusion procedure, the patient's anatomical region (e.g., breast, heart, central nervous system (CNS), suprarenal aorta, liver, head, neck, chest, abdomen, limbs, etc.), etc.

[0072] In some non-limiting embodiments, the fluid infusion procedure may comprise multiple stages. For example, the fluid infusion procedure may comprise an infusion stage, a flush stage, and / or a holding stage. In some non-limiting embodiments, the infusion stage of the fluid infusion procedure may be a stage characterized by a volume of drug solution infused at a certain flow rate (e.g., volume of fluid over time), which may be determined by the overall duration of the infusion stage. In some non-limiting embodiments, the flush stage of the fluid infusion procedure may be a stage characterized by a volume of drug solution acting as a flushing agent infused at a flow rate which may be determined by the overall duration of the flush stage. In some non-limiting embodiments, the holding stage of the fluid infusion procedure may be a stage characterized by a certain duration during which no fluid is infused into the patient. In some non-limiting embodiments, the infusion protocol management system 102 may determine the dosage of drug solution for the infusion stage and / or flush stage of the fluid infusion procedure. In some non-limiting embodiments, the operating parameters of the injection protocol for a fluid injection procedure performed by the fluid injection system 104 may include one or more exemplary data types disclosed in U.S. Patent Application No. 10 / 143,562, filed on 10 May 2002 and issued as U.S. Patent No. 7,457,804; U.S. Patent Application No. 12 / 254,318, filed on 20 October 2008 and issued as U.S. Patent No. 7,996,381; and U.S. Patent Application No. 13 / 180,175, filed on 11 July 2011 and issued as U.S. Patent No. 8,521,716, each of which disclosures are incorporated herein by reference in their entirety.

[0073] In some non-limiting embodiments, the fluid injection procedure may include injection, flushing, and / or holding stages in any order as needed. In some non-limiting embodiments, parameters of the injection protocol for the fluid injection procedure may include the duration of the fluid injection procedure (e.g., with respect to each stage), the type of drug solution in the fluid injection procedure (e.g., with respect to each stage), the concentration of the type of drug solution in the fluid injection procedure (e.g., with respect to each stage), the amount of drug solution administered in the fluid injection procedure (e.g., with respect to each stage), the flow rate of the drug solution in the fluid injection procedure (e.g., with respect to each stage), and so on.

[0074] In some non-limiting embodiments, the infusion protocol management system 102 may determine at least one parameter of the infusion protocol for a fluid infusion procedure. For example, the infusion protocol management system 102 may retrieve data related to at least one parameter from a data structure based on data related to the fluid infusion procedure (e.g., patient data related to the patient receiving the fluid infusion procedure, data related to the anatomical region of the patient to which the fluid infusion procedure should be performed, etc.). In some non-limiting embodiments, the infusion protocol management system 102 may configure at least one parameter of the infusion protocol for a fluid infusion procedure. For example, the infusion protocol management system 102 may configure the fluid infusion system 104 (e.g., the fluid infusion device of the fluid infusion system 104) such that the fluid infusion procedure is performed according to at least one parameter of the infusion protocol.

[0075] In some non-limiting embodiments, the fluid infusion procedure may include multiple infusion stages, flush stages, and / or holding stages. For example, the fluid infusion procedure may include two infusion stages. In some non-limiting embodiments, the infusion protocol management system 102 may determine a first flow rate of the drug solution for a first infusion stage and a second flow rate of the drug solution for a second infusion stage. For example, the infusion protocol management system 102 may determine the first and / or second flow rates based on the concentration of the drug solution (e.g., a mixture / ratio of contrast agent and saline) and / or the anatomical region of the patient to which the fluid infusion procedure is to be performed.

[0076] 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. For example, the injection protocol management system 102 may automatically generate at least one parameter of the injection protocol based on the receipt of a selection of an anatomical region identifier.

[0077] In another example, the infusion protocol management system 102 may automatically generate an infusion protocol for a fluid infusion procedure having two stages, such as an infusion stage and a flush stage, and the infusion protocol management system 102 may determine the type of drug solution and the dosage of the drug solution for the infusion stage based on the patient's weight and anatomical region identifier.

[0078] In yet another example, the infusion protocol management system 102 may automatically generate the parameters of the infusion protocol by determining a first dose of the drug solution, determining the parameters for a first flush stage, determining a second dose of the drug solution, and determining the parameters for a second flush stage. In some non-limiting embodiments, the infusion protocol management system 102 may determine a first dose of the drug solution and configure a first flush stage of a fluid infusion procedure, including a first infusion of saline (for example, by configuring the volume and flow rate of saline to be used by the fluid infusion system 104). The infusion protocol management system 102 may further determine a second dose of the drug solution for a second infusion stage of the fluid infusion procedure based on at least one of the patient's weight, the concentration of the drug solution, or an anatomical region. The infusion protocol management system 102 may further configure a second flush stage, including a second infusion of saline (for example, by configuring the same or different volume and flow rate of saline). The infusion protocol management system 102 may be configured to perform the fluid infusion procedure in the following order: a first infusion stage, a first flush stage, a holding stage, a second infusion stage, and a second flush stage (for example, by communicating commands to the fluid infusion system 104). For example, such a configuration may be used for a fluid infusion procedure associated with an MRI scan of the patient's cardiac region.

[0079] In some non-limiting embodiments, the infusion protocol management system 102 may automatically generate at least one parameter of the infusion protocol for a fluid infusion procedure based on the patient's patient data and independently of user input related to at least one parameter (e.g., without input). For example, the infusion protocol management system 102 may automatically generate at least one parameter of the infusion protocol for a fluid infusion procedure based on patient data and independently of user input related to the dosage of the drug solution for the fluid infusion procedure received via a user interface associated with the fluid infusion system performing the fluid infusion procedure.

[0080] As shown in Figure 3, in step 314, process 300 includes providing at least one parameter. For example, the infusion protocol management system 102 may provide at least one parameter of the infusion protocol to the fluid infusion system 104 (e.g., the fluid infusion device of the fluid infusion system 104). In some non-limiting embodiments, at least one parameter of the infusion protocol may be provided to the fluid infusion system 104 to perform a fluid infusion procedure. In one example, the fluid infusion system 104 may, based on receiving data related to at least one parameter of the infusion protocol from the infusion protocol management system 102, infuse the drug solution to the patient via the fluid infusion device as part of a fluid infusion procedure. The fluid infusion system 104 may perform a fluid infusion procedure according to at least one parameter of the infusion protocol, such as the dosage of the drug solution. In some non-limiting embodiments, the infusion protocol management system 102 may automatically provide at least one parameter to the fluid infusion system 104 based on user input (e.g., selection of the start button). In some non-limiting embodiments, the injection protocol management system 102 may provide at least one parameter in the user interface so that it is indicated as an instruction that a fluid injection procedure should be performed before the fluid injection procedure is initiated. In some non-limiting embodiments, the injection protocol management system 102 may cause the fluid injection system 104 to perform the fluid injection procedure. For example, the injection protocol management system 102 may cause the fluid injection system 104 to perform the fluid injection procedure based on the injection protocol management system 102 receiving user input (e.g., selection of a start button).

[0081] In some non-limiting embodiments, the injection protocol management system 102 may cause the fluid injection system 104 to perform the fluid injection procedure. For example, the injection protocol management system 102 may send a command signal to the fluid injection system 104 to perform the fluid injection procedure according to the injection protocol of the fluid injection procedure (for example, based on the fluid injection system 104 receiving a command signal). In some non-limiting embodiments, the injection protocol management system 102 may cause the fluid injection procedure to be performed in a sequence of multiple stages. For example, the injection protocol management system 102 may cause the fluid injection procedure to be performed in the order of injection stage, flush stage, and hold stage, or in any combination as needed. In one example, the injection protocol management system 102 may cause the fluid injection procedure to be performed in the order of first injection stage, first flush stage, hold stage, second injection stage, and second flush stage.

[0082] 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 for the fluid injection procedure, data related to at least one parameter of the injection protocol for the fluid injection procedure, data related to the complete injection protocol for the fluid injection procedure, etc.). For example, the injection protocol management system 102 may transmit data related to the fluid injection procedure to the fluid injection system 104 before the fluid injection procedure is performed.

[0083] Referring here to Figure 4, which shows a non-limiting embodiment of a first GUI 400a for use in the described method for operating a fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the first GUI 400a are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the first GUI 400a, and one or more elements of the first GUI 400a may be included in other GUIs to provide the features of the described method for operating a fluid injection system. The GUIs related to Figures 4 to 7E may be described using sequential terms such as “first,” “second,” “third,” etc., but it will be understood that these terms, unless otherwise specified, are for distinguishing exemplary views (e.g., graphically displayed windows) rather than defining a sequence of operations. The user interfaces described herein may include one or more of the GUIs 400a to 400i described herein.

[0084] The first GUI 400a displays an exemplary welcome screen (e.g., a startup screen, a home screen, etc.) for display to the user of the workstation device 106. The first GUI 400a may include settings or menu icons (e.g., shown as a gear symbol or a three-line symbol) that allow the user to configure settings for the GUI in the described manner (e.g., units of the measurement system, default settings for the dosage calculator, etc.), and / or display settings (e.g., brightness, light / dark mode, font size, etc.). The first GUI 400a may further include an exit control button (e.g., an "X" that may be accompanied by the word "Exit") for closing the GUI in the described manner. The first GUI 400a may further include a set of text that describes the GUI to be displayed, such as a welcome message with information about getting started. The first GUI 400a may further include a graphic button for starting a fluid infusion procedure with a new patient (e.g., a button labeled "New Patient"), and a graphic button for starting a fluid infusion procedure with the last patient the system was used with (e.g., a button labeled "Same Patient"). When a new patient button is selected, the user may be navigated to a second GUI400b, as shown in Figure 5. When the same patient button is selected, the system may navigate the user to a third GUI400c, based on the previously used patient, as shown in Figure 6A.

[0085] Referring here to Figure 5, Figure 5 shows a non-limiting embodiment of the second GUI400b for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the second GUI400b are for illustrative purposes only and should not be construed as limiting the present disclosure. To provide the features of the described method for operating the fluid injection system, one or more elements of other GUIs described herein may be combined with those of the second GUI400b, or one or more elements of the second GUI400b may be included in other GUIs.

[0086] The second GUI 400b shows an exemplary patient work list screen that provides the user with a list of patients (including at least several patient identifiers, such as unique identifiers associated with patient records). The second GUI 400b may provide, at least partially, a list of patients for whom one or more fluid infusion procedures are scheduled. The workstation device 106 may communicate with the hospital information system 108 to determine which list of patients to display based on the time (e.g., date, time, etc.) at which the patient procedures are scheduled to be performed. For example, the workstation device 106 may receive a list of patients scheduled for the time closest to the workstation device 106's current operating time. In the illustrated example, for a user operating the workstation device 106 at 7:00 AM on July 8, 2022, the second GUI 400b may display a list of patients for whom procedures are scheduled over at least the next 48 hours (e.g., July 8, 2022, and July 9, 2022). It will be understood that patients scheduled over a wider or narrower period may also be displayed in the second GUI 400b. It should also be understood that if a patient is scheduled for multiple procedures, a particular patient may be shown multiple times in the second GUI400b.

[0087] In some non-limiting embodiments, the second GUI400b may provide a list of patients in a series of rows, each row representing a different patient and the patient's scheduled treatment. Each column of the illustrated data may represent a different part of the patient data. For example, there may be multiple columns showing, but not limited to, patient name (e.g., titled "Name"), date of birth (e.g., titled "Date of Birth"), patient identifier (e.g., titled "ID"), treatment time (e.g., titled "Time"), treatment date (e.g., titled "Date"), acceptance number (e.g., titled "ACC", a unique number assigned to the patient by the registrar, which may be used to determine when the patient was first identified by the registrar), and a description of the treatment to be performed (e.g., titled "Treatment Description", which may include a treatment identifier and / or a short text description of the treatment). Rows may be configured in a second GUI400b to be sortable based on a selected column (for example, if "Name" is selected, patients may be organized alphabetically by last name, inversely alphabetically by last name, and / or similar). Each row may further include icons that the user can select to view more information about the patient and / or the patient's treatment (for example, icons indicating profile symbols).

[0088] In some non-limiting embodiments, the second GUI400b may include a refresh button that can update the list of patients with the most recent data based on the current time. Additionally or alternatively, the second GUI400b may automatically refresh based on a predetermined time interval (e.g., once every minute, once every five minutes). The second GUI400b may further include a search field to enable the user to search for and find a specific patient scheduled for treatment. The second GUI400b may further include a filter control to provide the user with one or more filters for reorganizing the displayed patient data. If the number of patients exceeds the amount of display space available for the second GUI400b, the second GUI400b may include a scroll bar and / or be scrollable to view further patients. The second GUI400b may also include a button that allows the user to continue the process for patients that have not been identified or associated with a patient record (e.g., an unnamed patient, an unknown patient, etc.). The button may be associated with an identifier that is not associated with a patient record.

[0089] In some non-limiting embodiments, the second GUI400b may include setting or menu icons (e.g., shown as a gear symbol or a three-line symbol) that allow the user to configure settings and / or display settings for the GUI in the described manner. The second GUI400b may further include a navigation bar that indicates where the user is in the process (e.g., which part of the process for configuring a fluid injection procedure). The navigation bar may include tabs having text and / or icons representing parts of the setup process for a fluid infusion procedure, which may include, but are not limited to, viewing a patient's worklist (e.g., "Patient" tab), viewing pre-configurations for an infusion protocol (e.g., "Protocol" tab), viewing patient data and parameters for an infusion protocol (e.g., "Fluid" tab), viewing parameters generated for an infusion protocol for a fluid infusion procedure (e.g., "Examination Information" tab), confirming and starting a fluid infusion procedure (e.g., "Infusion" tab), and waiting while the fluid infusion procedure is in progress (e.g., a "Lock" tab to indicate that the parameters for the infusion protocol for a fluid infusion procedure have been configured and provided to the fluid infusion system 104 and cannot be changed while the procedure is being performed).

[0090] Referring here to Figure 6A, Figure 6A shows a non-limiting embodiment of the third GUI400c for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the third GUI400c are for illustrative purposes only and should not be construed as limiting the present disclosure. To provide the features of the described method for operating the fluid injection system, one or more elements of other GUIs described herein may be combined with those of the third GUI400c, and one or more elements of the third GUI400c may be included in other GUIs.

[0091] A third GUI400c displays an exemplary infusion protocol selection screen through which the user can browse various types of pre-configured infusion protocols (e.g., including at least several anatomical region identifiers). The arrangement of the displayed infusion protocols may be predetermined according to a specific set of drug solutions planned for use in the associated fluid infusion system. For example, but not limited to, several pre-configured infusion protocols may be displayed for fluid infusion procedures in several anatomical regions such as the breast, heart, central nervous system (CNS), supra-renal aorta (e.g., via magnetic resonance angiography (MRA)), and liver. The term “pre-configured” may be used to indicate a predetermined or preferred infusion protocol to be displayed, but it will be understood that not all parameters of an infusion protocol may be configured until later in the described method if the parameters can be automatically generated by the workstation device 106 based on patient data of the patient receiving the procedure. The pre-configured infusion protocol buttons may identify, in addition to the corresponding anatomical region, the dosage parameters of the drug solution to be used (e.g., ml / kg), and drug solution identifiers such as Gadovist and Primovist, as shown in Figure 6A.

[0092] In some non-limiting embodiments, the third GUI 400c may include several other infusion protocol selection options other than those pre-configured on the workstation device 106. Other sets of infusion protocols may be presented in response to user selections of corresponding buttons, such as patient prior information (e.g., showing previous infusion protocols used on the patient based on the patient's patient record), frequently used (e.g., showing infusion protocols commonly used on the workstation device 106), and other templates for infusion protocols for various groups of anatomical regions (e.g., head, neck, chest, abdomen, limbs, etc.). The third GUI 400c may further allow the user to create their own pre-configured infusion protocols. The third GUI 400c may also include an event notification window accessible by collapsible control buttons, which may present warnings or notifications to the user of the workstation device 106. The third GUI 400c may further display patient data (if applicable) for the selected patient in a dropdown field, which may provide some high-level patient data for easy reference, including but not limited to patient name, patient acceptance number, patient gender, and patient age. In this way, the user is consistently notified of patient information on which fluid injection procedures are being performed.

[0093] In some non-limiting embodiments, the third GUI400c may include a procedure reset button to abandon the setup process for the current fluid infusion procedure and return to the home and / or start screen, such as the first GUI400a in Figure 4, the second GUI400b in Figure 5, or the third GUI400c in Figure 6A. To avoid scenarios in which the user inadvertently selects the option to reset the procedure, confirmation from the user may be required before resetting the procedure. The third GUI400c may also include a preview of the fluid infusion procedure based on the infusion protocols selected and configured up to that point in the setup process. In an exemplary third GUI400c, several pre-configured infusion protocols are shown, and since none of them have yet been selected by the user, the preview portion of the infusion protocols in the third GUI400c is shown mostly empty / unfilled. For example, the preview may include fields showing the total contrast agent volume, total saline volume, and total duration of the fluid infusion procedure. Each of these fields in the third GUI400c is shown as undefined or zero, since no infusion protocol has yet been selected or configured. Similarly, the dropdown shown for the maximum infusion pressure limit of the infusion protocol (e.g., in pounds per square inch (PSI) units) remains undefined. In contrast, the duration of the venous access (KVO) time is indicated based on the patient's expected medical procedure. Once the user selects an infusion protocol for further setup, the user may browse the protocol parameters before initiating the procedure and select a button (e.g., a "Select and Edit" button) to review the parameters. Furthermore, similar to the second GUI400b, the third GUI400c may include a navigation bar to indicate where the user is in the setup process.

[0094] Referring here to Figure 6B, Figure 6B shows a non-limiting embodiment of the fourth GUI400d for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the fourth GUI400d are for illustrative purposes only and should not be construed as limiting the present disclosure. To provide the features of the described method for operating the fluid injection system, one or more elements of other GUIs described herein may be combined with those of the fourth GUI400d, and one or more elements of the fourth GUI400d may be included in other GUIs.

[0095] The fourth GUI400d presents substantially the same GUI as the third GUI400c, but is configured so that the user is browsing a different set of infusion protocols. Instead of pre-configured infusion protocols being displayed, the user selects the “Breast UAA Hospital” template for breast-based infusion protocols (e.g., based on guidelines from an exemplary hospital), which is listed under infusion protocols for the “Chest” grouping of infusion protocols. Further on (e.g., by selecting the “Select and Edit” button), the user can browse specific parameters of the selected infusion protocol (see Figure 7A).

[0096] Referring here to Figure 7A, Figure 7A shows a non-limiting embodiment of the fifth GUI400e for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the fifth GUI400e are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the fifth GUI400e, and one or more elements of the fifth GUI400e may be included in other GUIs to provide the features of the described method for operating the fluid injection system.

[0097] The fifth GUI400e displays an exemplary window for viewing and modifying the parameters of the selected infusion protocol (for example, titled “Fluid” or “Fluid Information” in relation to the fluid used in the fluid infusion procedure). As shown, this example is for the selected “Breast UAA Hospital” template of an infusion protocol that may have been selected by the user in the fourth GUI400d in Figure 6B. In some non-limiting embodiments, patient data may be retrieved from the hospital information system 108 based on the selection of a patient identifier in the second GUI400b and displayed in the fifth GUI400e. Additionally or alternatively, patient data may be preloaded from the hospital information system 108 and selectively displayed on the workstation device 106 based on the selection of a patient identifier. In the illustrated example, patient data including, but not limited to, patient weight, patient height, and patient eGFR may be displayed in the fifth GUI400e. Patient information controls (e.g., dropdowns), procedure reset buttons, event controls, and / or navigation bars may continue to be displayed in the fifth GUI400e, as they were in the third GUI400c and fourth GUI400d.

[0098] In some non-limiting embodiments, the window for viewing and modifying the parameters of the selected infusion protocol may include information about the fluids used in the fluid infusion procedure. For example, the window may display a drug selector (e.g., a dropdown indicating and allowing modification of contrast fluids), a drug batch / lot field, and a drug expiration date field. As a further example, the window may display a saline selector (e.g., a dropdown indicating and allowing modification of saline), a saline batch / lot field, and a saline expiration date field. The window may also include a "Load Defaults" button for loading predetermined drug and saline data for the infusion protocol.

[0099] Figure 7A shows an exemplary window of the fifth GUI400e, in particular, where the dose calculation function is initially disabled. The dose calculator of this disclosure includes a tool for automatically determining the patient's drug dose based on patient data without requiring the user to refer to an external tool. Since the dose calculator is disabled in the fifth GUI400e, the infusion protocol preview in the fifth GUI400e is based on the patient data and is based on default dose volumes that are not necessarily customized for the patient. For example, the infusion protocol preview shows a total drug fluid volume of 10.0 ml, a total saline volume of 10.0 ml, and a total infusion procedure duration of 10 seconds. The pressure limit for the infusion is set to 325 psi (which may be configured to terminate the infusion procedure if this threshold is exceeded) (e.g., configured and / or stored in memory). The infusion protocol preview further includes a depiction of the stages of the infusion procedure based on the current parameter settings. The stages are shown in a series of rows, with one row for each stage. Each stage includes a fluid identifier (e.g., an icon indicating the type of fluid or fluid shortage), flow rate, volume, and duration of injection. As shown in the illustrated example, the current injection protocol specifies an injection stage with a flow rate of 2 ml / second, a contrast agent volume of 10.0 ml, and a contrast agent injection duration of 5 seconds, followed by a flush stage with a flow rate of 2 ml / second, a saline volume of 10.0 ml, and a saline injection duration of 5 seconds.

[0100] Referring here to Figure 7B, Figure 7B shows a non-limiting embodiment of the sixth GUI400f for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the sixth GUI400f are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the sixth GUI400f, and one or more elements of the sixth GUI400f may be included in other GUIs to provide the features of the described method for operating the fluid injection system.

[0101] The sixth GUI400f displays substantially the same exemplary window as the fifth GUI400e in Figure 7A, but with the dose calculation function enabled. The user may enable the dose calculator by selecting a button (e.g., a toggle switch). Once the dose calculator is available, certain parameters of the infusion protocol may be updated and determined based on patient data. For example, the workstation device 106 may identify the concentration of a drug solution (e.g., a contrast fluid with a concentration of 1 mmol / ml) selected from a programmed data table (e.g., a hardcoded chart), a default dose (e.g., 0.1 ml / kg, also from a programmed data table), a patient dose (in units ml / kg) based on patient data (e.g., from a programmed data table based on the patient's age and / or weight), and a total dose volume (in units ml) calculated based on patient data (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 dosage calculation function enabled, the infusion protocol preview has been updated with a more accurate and now customized set of parameters for the fluid infusion procedure's infusion protocol. For example, the infusion protocol preview now shows a total drug fluid volume of 8.5 ml, a total saline volume of 10.0 ml, and a total infusion procedure duration of 9 seconds. The stages have also been updated to an infusion stage with a flow rate of 2 ml / second, a contrast agent volume of 8.5 ml, and a contrast agent infusion duration of 4 seconds, followed by a flush stage with a flow rate of 2 ml / second, a saline volume of 10.0 ml, and a saline infusion duration of 5 seconds. In this way, the parameters of the infusion protocol are automatically generated without the user having to refer to external tools / manuals. From this point of view, the user may review and confirm the final parameters of the infusion protocol, which can then be used to perform the fluid infusion procedure by instructing the fluid infusion system.

[0102] Referring here to Figure 7C, Figure 7C shows a non-limiting embodiment of the seventh GUI400g for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the seventh GUI400g are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the seventh GUI400g, and one or more elements of the seventh GUI400g may be included in other GUIs to provide the features of the described method for operating the fluid injection system.

[0103] The seventh GUI400g shows substantially the same exemplary window as the sixth GUI400f in Figure 7B, but the dosage calculation function is fully integrated as part of a pre-configured infusion protocol. In particular, the seventh GUI400g may be displayed in response to the user selecting the pre-configured “breast” infusion protocol shown in the third GUI400c in Figure 6A. Patient data may be automatically retrieved from the patient record in the hospital information system 108 and displayed in the seventh GUI400g. Furthermore, the parameters of the infusion protocol may be automatically calculated based on patient data (e.g., patient weight) and thus displayed in the seventh GUI400g. For this purpose, the recommended drug solution is displayed along with the recommended saline solution. The infusion and flushing stages are configured based on the selected anatomical region identifier, “breast”. Furthermore, the workstation device 106 may identify the total dose volume (ml) calculated based on patient data (e.g., 8.5 ml derived from the dose and patient weight). The preview of the infusion protocol shows, as indicated, an automatically generated total drug fluid volume of 8.5 ml, a total saline fluid volume of 20.0 ml, and a total infusion procedure duration of 14 seconds. The planned fluid infusion procedure is also divided into stages, including an infusion stage with a flow rate of 2 ml / second, a contrast agent volume of 8.5 ml, and a contrast agent infusion duration of 4 seconds, followed by a flush stage with a flow rate of 2 ml / second, a saline fluid volume of 20.0 ml, and a saline infusion duration of 10 seconds. In this way, the parameters of the infusion protocol are automatically generated without the user having to refer to external tools / manuals. From this point of view, the user may review and confirm the final parameters of the infusion protocol, which can be used to perform the fluid infusion procedure by instructing the fluid infusion system.

[0104] Referring here to Figure 7D, Figure 7D shows a non-limiting embodiment of the eighth GUI400h for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the eighth GUI400h are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the eighth GUI400h, and one or more elements of the eighth GUI400h may be included in other GUIs to provide the features of the described method for operating the fluid injection system.

[0105] The eighth GUI400h displays substantially the same exemplary window as the seventh GUI400g in Figure 7C, but for a different patient receiving a fluid infusion procedure based on cardiac anatomical region. In particular, the eighth GUI400h may appear in response to the user selecting patient "Wei Zhang" in the second GUI400b in Figure 5, and subsequently selecting the pre-configured "cardiac" infusion protocol shown in the third GUI400c in Figure 6A. Patient data may be automatically retrieved from the patient record in the hospital information system 108 and displayed in the eighth GUI400h. Furthermore, the parameters of the infusion protocol may be automatically calculated based on patient data (e.g., patient weight) and thus displayed in the eighth GUI400h. For this purpose, the recommended medication is displayed along with the recommended saline solution. Since the pre-configured infusion protocol for the "cardiac" anatomical region requires two infusion stages and two saline stages separated by a holding stage, the workstation device 106 automatically generates the corresponding stages of the fluid infusion procedure. The preview of the infusion protocol shows, as indicated, an automatically generated total drug fluid volume of 8.4 ml, a total saline fluid volume of 40.0 ml, and a total infusion procedure duration of 10 minutes and 12 seconds. The planned fluid infusion procedure also includes a first infusion stage with a flow rate of 4 ml / second, a contrast agent volume of 4.2 ml, and a contrast agent infusion duration of 1 second; a subsequent first flush stage with a flow rate of 4 ml / second, a saline fluid volume of 20.0 ml, and a saline infusion duration of 5 seconds; a subsequent hold stage with a duration of 10 minutes (e.g., no fluid is injected); a subsequent second infusion stage with the same parameters as the first infusion stage; and a subsequent second flush stage with the same parameters as the first flush stage. In this way, the parameters of the infusion protocol are automatically generated without the user having to refer to external tools / manuals. From this point of view, the user may review and confirm the final parameters of the infusion protocol, which can be used to perform the fluid infusion procedure by instructing the fluid infusion system.

[0106] Referring here to Figure 7E, which shows a non-limiting embodiment of the 9th GUI400i for use in the described method for operating the fluid injection system. It will be understood that the exact style, arrangement, and configuration of the interface components of the 9th GUI400i are for illustrative purposes only and should not be construed as limiting this disclosure. One or more elements of other GUIs described herein may be combined with those of the 9th GUI400i, and one or more elements of the 9th GUI400i may be included in other GUIs to provide the features of the described method for operating the fluid injection system.

[0107] The ninth GUI400i displays substantially the same exemplary window as the seventh GUI400g in Figure 7C, but is for unidentified (e.g., unnamed, unknown) patients. In particular, the ninth GUI400i may appear in response to the user selecting the “Unknown Patient” button shown in the second GUI400b in Figure 5, followed by the “Breast” pre-configured infusion protocol shown in the third GUI400c in Figure 6A. Since the “Unknown Patient” button is associated with an identifier not linked to a patient record, patient data is not automatically retrieved from the patient record in the hospital information system 108. Instead, the ninth GUI400i notifies the user that patient data input is required, in particular, including the patient's weight. Once the patient's weight data is entered by the user, the workstation device 106 may automatically generate the parameters for the infusion protocol based on the entered patient data. The automatically generated parameters may be entered into the preview window for the infusion protocol, much like in the seventh GUI400g. From this perspective, the user may review and confirm the final parameters of the injection protocol, which can be used to perform the fluid injection procedure by instructing the fluid injection system.

[0108] Referring here to Figure 8, which illustrates a non-limiting embodiment of the medical imaging suite 800. The medical imaging suite 800 may be located in a hospital and / or imaging center for use when performing imaging procedures on a patient for the purpose of diagnosing disease and / or other abnormalities. The medical imaging suite 800 may include a scanning room 814 in which a fluid infusion system 804 and a medical imaging system 806 are located, and a control room 816 in which an individual (e.g., a radiologist, technician, or other healthcare professional) can monitor the patient 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 multifluid delivery system such as the MEDRAD® MRXperion MR infusion system provided by Bayer HealthCare LLC. In some non-limiting embodiments, the fluid infusion system 804 may be the same as or similar to the fluid infusion system 104. In some non-limiting embodiments, the workstation device 802 including a display unit 808 may be the same as or similar to the workstation device 106. In some non-limiting embodiments, the infusion protocol management system 102 may be a component of the workstation device 802. As shown in Figure 8, the workstation device 802 may be used (e.g., by a medical professional) to set up and / or perform a fluid infusion procedure for a patient. In some non-limiting embodiments, the workstation device 802 may provide a user interface (e.g., an application-based user interface, a web-based user interface, etc.) for controlling the fluid infusion system 804 and the medical imaging system 806 to the display unit 808. Parameters of the infusion protocol for the fluid infusion procedure may be automatically generated by the infusion protocol management system 102 and, in some non-limiting embodiments, displayed on the workstation device 802 and / or communicated to the fluid infusion system 804 to perform the fluid infusion procedure.

[0109] Referring here to Figure 9, which shows an enlarged sub-view of the fluid injection system 804 shown in Figure 8, specifically an unrestricted embodiment of the scanning chamber unit 805 (e.g., the MEDRAD® MRXperion MR injection system). In some unrestricted embodiments, the scanning chamber unit 805 includes a pedestal 811 mounted on a base 813, which has lockable casters 817 attached to its bottom, for use when moving the scanning chamber unit 805 within the scanning chamber 814 as needed during imaging procedures. Primarily intended to support the injector head 850 of the scanning chamber unit 805, the pedestal 811 also includes an integrated IV pole 818 with one or more hooks 819 for suspending minimal IV-related accessories. In some unrestricted embodiments, the base 813 houses various electronic and communication components, as well as a power supply for the scanning chamber unit 805. Among other connections, the scanning chamber unit 805 has a power cable 821 for supplying power to the power supply via a through panel 807, as shown in Figure 8, and an optical fiber link 822 for communicating with a workstation device 802 in the control chamber 816 to enable control of the operation of the fluid injection system 804.

[0110] Referring here to Figure 10, Figure 10 shows a non-limiting embodiment of the injector head 850 of the scanning chamber unit 805 shown in Figure 9 (e.g., the MEDRAD® MRXperion MR injection system). As shown in Figure 10, 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 drive components for controlling the flow of fluid into and out of the fluid reservoirs, such as pistons associated with each of the fluid reservoirs 860a / 860b that drive associated plungers in the barrels of the fluid reservoirs 860a / 860b. In some non-limiting embodiments, each of the fluid reservoirs 860a / 860b is adapted to interface with the housing 851 in a releasable manner with a port 855 therefor. Each fluid reservoir 860a / 860b of the fluid injection system is configured to be filled with at least one drug solution F, such as imaging contrast agent, saline solution, and / or any desired drug solution. Each fluid reservoir 860a / 860b may be filled with a different drug solution F. In some non-limiting embodiments, the fluid injection system 804 may be a multi-syringe injector as shown, and the two fluid reservoirs 860a / 860b may be oriented side by side or in a different spatial relationship and actuated separately by their respective pistons associated with the fluid injection system.

[0111] In some non-limiting embodiments, the fluid infusion system 804 may be used during a medical procedure to infuse at least one drug solution F into the patient's vascular system by selectively driving plungers associated with each fluid reservoir 860a / 860b with their respective drive components. For each fluid reservoir, the drive component may move the plunger toward the distal end 861 of the fluid reservoir to drain the fluid F from the fluid reservoir into a fluid pathway set and through the fluid pathway set 1000 during priming, purging, and / or fluid delivery steps. In some non-limiting embodiments, the fluid pathway set 1000 may include at least one tube or set of tubes configured to fluidize each fluid reservoir 860a / 860b, and each fluid reservoir may be arranged to fluidize with a flexible dosing tube and associated catheter to deliver the fluid F from each or both fluid reservoirs 860a / 860b to the patient at a vascular access site.

[0112] In some non-limiting embodiments, the injector head 850 may include a variety of control buttons and indicators for monitoring and influencing the operation of the fluid infusion system 804 through it. For example, a manual knob 861a / 861b may be used by the operator to assist in priming one or more sets of tubing, to help ensure accurate placement of the catheter to the patient, and to check the patency of the fluid connection with the patient. The injector head 850 may also include a prime button 870 that, when pressed, lights up to indicate to the operator that the priming function can be activated and priming can be initiated. The injector head 850 may also include a start / hold button 871 that, when pressed, starts the infusion procedure when the fluid infusion system 804 is ready, and a stop button 872 that, when pressed, ends the infusion procedure in progress and thereby releases the fluid infusion system 804. The injector head 850 may also feature forward and backward piston control buttons 873 and 874, as well as a piston control enable button 875, to activate buttons 873 and 874, thereby allowing their use to advance and retract the piston. In some non-limiting embodiments, the injector head 850 may include various other control buttons and indicators, such as those described in the MEDRAD® MRXperion MR Injection System Operation Manual published by Bayer Medical Care Inc. in January 2021, which are incorporated herein by reference.

[0113] The systems, methods, and computer program products described above are described in detail for illustrative purposes based on what is considered to be the most practical and preferred embodiments at present; however, such details are for that purpose only, and it should be understood that this disclosure is not limited to the embodiments or aspects described, but rather intended to cover modifications and equivalent configurations that fall within the spirit and scope of the appended claims. For example, it should be understood that this disclosure is intended to allow, wherever possible, at least one feature of any embodiment or aspect to be combined with at least one feature of any other embodiment. [Explanation of Symbols]

[0114] 100A environment 100B System 102 Injection Protocol Management System 104 Fluid injection system 106 Workstation equipment 106A Display Unit 108 Hospital Information System 110 Communication Network 112 Medical Imaging Systems 114 Communication Networks 200 equipment Bus 202 202A Informatics Applications 202B Data Management Application 202C Imaging System Connection Application 204 Processors 206 memory 208 Memory Components 208A Patient Treatment Tracking System 208B Fluid Injector Management System 208C Communication System 208D Radiation Information System 208E Radiation Analysis System 210 Input Components 212 Output Components 214 Communication Interface 300 processes 800 Medical Imaging Suite 802 Workstation equipment 804 Fluid Injection System 805 Scanning Room Unit 806 Medical Imaging System 807 Through-panel 808 Display Unit 811 Pedestal 813 Base 814 Scanning Room 816 Control Room 817 Caster 818 Integrated IV Pole 819 Hook 821 Power Cable 822 Fiber Optic Link 850 Injector Heads 851 Housing Port 855 860a Fluid reservoir 860b Fluid reservoir 861 Distal end 870 Prime Button 871 Hold button 872 Cancel button 873 Forward Piston Control Button 874 Reverse piston control button 875 Piston control enable button 1000 Fluid Path Sets

Claims

1. A system for operating a fluid injection system, At least one processor, Receiving patient data relating to a patient undergoing a fluid injection procedure, wherein the patient data includes data relating to the patient's weight. To automatically generate at least one parameter of an infusion protocol for a fluid infusion procedure based on the patient data and independently of inputs related to the dosage of the drug solution for the fluid infusion procedure received via a user interface associated with the fluid infusion system that performs the fluid infusion procedure, wherein when the at least one parameter is automatically generated, the at least one processor The amount of the drug solution to be administered for the fluid injection treatment is The aforementioned patient’s weight, The concentration of the aforementioned chemical solution, The anatomical region of the patient in which the fluid injection procedure is to be performed, Any combination of those, To generate, which is programmed or configured to determine based on, To provide the fluid injection system with at least one parameter of the injection protocol, At least one processor, programmed or configured to perform Equipped with, system.

2. The system further comprises a display unit, and the at least one processor is: Displaying multiple patient identifiers on the user interface of the display unit, The selection of a patient identifier from the plurality of patient identifiers is received via the user interface, Programmed or configured to do so, Upon receiving the patient data, the at least one processor, The system is programmed or configured to receive patient data based on the selection of the patient identifier received via the user interface. The system according to claim 1.

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

4. The patient data relating to the patient receiving the fluid injection procedure corresponds to the patient's patient record stored in the hospital information system, and the at least one processor, Further programmed or configured to transmit a unique identifier associated with the patient's patient record to the hospital information system, Upon receiving the patient data, the at least one processor: Programmed or configured to receive patient data from the hospital information system, The system according to claim 1.

5. When automatically generating the at least one parameter of the injection protocol for the fluid injection procedure, the at least one processor: Determining a first dose of the drug solution for the first injection stage of the fluid injection procedure, Determining a first flush stage of the fluid injection procedure, wherein the first flush stage includes a first injection of physiological saline solution. The second dose of the drug solution for the second injection step of the fluid injection procedure is The aforementioned patient’s weight, The concentration of the aforementioned chemical solution, The aforementioned anatomical region, or Any combination of them The decision will be based on at least one of the following: Determining a second flushing stage of the fluid injection procedure, wherein the second flushing stage includes a second injection of physiological saline solution. Further programmed or configured to do so, The system according to claim 1.

6. The aforementioned at least one processor is The fluid injection procedure is further programmed or configured to be performed in the following order: the first injection step, the first flush step, the holding step, the second injection step, and the second flush step. The system according to claim 5.

7. When automatically generating the at least one parameter of the injection protocol for the fluid injection procedure, the at least one processor: Based on the concentration of the drug solution and the anatomical region, a first flow rate of the drug solution for the first injection step is determined. Based on the concentration of the drug solution and the anatomical region, a second flow rate of the drug solution for the second injection step is determined. Programmed or configured to do, The system according to claim 5.

8. The system further comprises a display unit, and the at least one processor is: Displaying multiple anatomical region identifiers on the user interface of the display unit, The selection of the anatomical region identifiers of the plurality of anatomical region identifiers is received via the user interface, Further programmed or configured to do so, When automatically generating the at least one parameter of the injection protocol for the fluid injection procedure, the at least one processor: Based on the selection of the anatomical region identifier received via the user interface, the type of drug solution, the concentration of the drug solution, and the anatomical region of the patient to which the fluid infusion procedure should be performed are determined. To be programmed or configured The system according to claim 1.

9. A method for operating a fluid injection system, A step of receiving patient data relating to a patient undergoing a fluid infusion procedure using at least one processor, wherein the patient data includes data relating to the patient's weight. A step of automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure using at least one processor, independently of inputs related to the dosage of the drug solution for the fluid infusion procedure received via a user interface associated with a fluid infusion system that performs the fluid infusion procedure based on patient data, wherein the step of automatically generating at least one parameter is The amount of the drug solution to be administered for the fluid injection treatment is The aforementioned patient’s weight, The concentration of the aforementioned chemical solution, or The anatomical region of the patient in which the fluid injection procedure is to be performed, Any combination of those, Based on this, including the step of making a decision, The steps to generate, A step of providing the at least one parameter of the injection protocol using at least one processor, Methods that include...

10. The steps include displaying multiple patient identifiers on the user interface of the display unit, The method further includes the step of receiving a selection of a patient identifier from among the plurality of patient identifiers via the user interface, The step of receiving the patient data is: The step of receiving patient data based on the selection of the patient identifier received via the user interface, The method according to claim 9.

11. The patient data relating to the patient receiving the fluid injection treatment corresponds to the patient's patient record stored in the hospital information system, and the method is, The step further includes transmitting a unique identifier associated with the patient's patient record to the hospital information system, The step of receiving the patient data is, The step includes receiving the patient data from the hospital information system, The method according to claim 10.

12. The step of receiving the patient data is: The step of receiving the patient data from user input via a user interface displayed on a display unit includes: The method according to claim 9.

13. The step of automatically generating the at least one parameter of the injection protocol for the fluid injection procedure is: A step of determining a first dose of the drug solution for the first injection stage of the fluid injection procedure, A step of determining a first flush stage of the fluid injection procedure, which includes a first injection of physiological saline solution, A step of determining a second dose of the drug solution for a second infusion stage of the fluid infusion procedure, based on the patient's body weight, the concentration of the drug solution, or at least one of the anatomical regions. A step of determining a second flushing stage, which includes a second injection of the physiological saline solution, The method according to claim 9, further comprising:

14. The steps of performing the fluid injection procedure in the following order: the first injection step, the first flush step, the holding step, the second injection step, and the second flush step, The method according to claim 13, further comprising:

15. The step of automatically generating the at least one parameter of the injection protocol for the fluid injection procedure is: A step of determining a first flow rate of the drug solution for the first infusion step, based on the concentration of the drug solution and the anatomical region of the patient to which the fluid injection procedure is to be performed. A step of determining a second flow rate of the drug solution for the second infusion stage, based on the concentration of the drug solution and the anatomical region of the patient to which the fluid infusion procedure is to be performed. The method according to claim 13, further comprising:

16. The steps include displaying multiple anatomical region identifiers on the user interface of the display unit, The method further includes the step of receiving a selection of anatomical region identifiers of the plurality of anatomical region identifiers via the user interface, The step of automatically generating the at least one parameter of the injection protocol for the fluid injection procedure is: The steps include determining the drug solution, the concentration of the drug solution, and the anatomical region of the patient to which the fluid infusion treatment should be performed, based on the selection of the anatomical region identifier received via the user interface. The method according to claim 9.

17. A computer program product for operating a fluid injection system, wherein the computer program product, when executed by at least one processor, provides to the at least one processor: Receiving patient data relating to a patient undergoing a fluid injection procedure, wherein the patient data includes data relating to the patient's weight. The method for automatically generating at least one parameter of an infusion protocol for a fluid infusion procedure, based on the patient data and independent of inputs related to the dosage of the drug solution for the fluid infusion procedure received via a user interface associated with the fluid infusion system that performs the fluid infusion procedure, wherein one or more instructions causing the at least one processor to automatically generate the at least one parameter are provided to the at least one processor. The amount of the drug solution to be administered for the fluid injection treatment is The aforementioned patient’s weight, The concentration of the aforementioned chemical solution, or The anatomical region of the patient in which the fluid injection procedure is to be performed, Based on at least one of the following, To generate, To provide the fluid injection system with at least one parameter of the injection protocol, To have them do it, A computer program product comprising at least one non-temporary computer-readable medium containing the aforementioned one or more instructions.

18. The one or more instructions further provide to the at least one processor: Displaying multiple patient identifiers on the user interface of the display unit, The system receives the selection of a patient identifier from among the multiple patient identifiers via the user interface, and further allows the system to perform this action. The one or more instructions that cause the at least one processor to receive the patient data are, The system is made to receive patient data based on the selection of the patient identifier received via the user interface. The computer program product according to claim 17.

19. The patient data relating to the patient receiving the fluid injection procedure corresponds to the patient's patient record stored in the hospital information system, and the one or more instructions are sent to the at least one processor. Further, the unique identifier associated with the patient's patient record is transmitted to the hospital information system. The one or more instructions that cause the at least one processor to receive the patient data are, The system is made to receive the patient data from the hospital information system. The computer program product according to claim 17.

20. The one or more instructions that cause the at least one processor to automatically generate the at least one parameter of the injection protocol for the fluid injection procedure, Determining a first dose of the drug solution for the first injection stage of the fluid injection procedure, Determining a first flush stage of the fluid injection procedure, wherein the first flush stage includes a first injection of physiological saline solution. The second dose of the drug solution for the second injection step of the fluid injection procedure is The aforementioned patient’s weight, The concentration of the aforementioned chemical solution, The aforementioned anatomical region, or, Any combination of them The decision will be based on at least one of the following: Determining a second flushing stage of the fluid injection procedure, wherein the second flushing stage includes a second injection of physiological saline solution. Let them do it further, The one or more instructions further cause the at least one processor to The fluid injection procedure is performed in the following order: the first injection step, the first flush step, the holding step, the second injection step, and the second flush step. The computer program product according to claim 17.

Images