Systems, methods, and computer program products for providing a gateway for connecting fluid delivery systems and external systems

Abstract

Systems, methods, and computer program products are disclosed that provide a gateway device that enables communication between a fluid infusion system and one or more external systems. A system for enabling communication between a fluid injection system and at least one of a plurality of external systems is provided, including a gateway device including at least one processor programmed or configured to: provide a first communication interface between a hospital information system and the fluid injection system, provide a second communication interface between a fluid injection system service and control system associated with the fluid injection system and the fluid injection system, and provide a third communication interface between a medical imaging system and the fluid injection system.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 051,491, filed July 14, 2020, and U.S. Provisional Patent Application No. 63 / 145,607, filed May 17, 2021, the entire disclosures of which are incorporated herein by reference.

[0002] 1. Field The present disclosure relates generally to communication systems and / or devices associated with medical devices, and in some non-limiting embodiments, to systems, methods, and computer program products that provide a gateway to enable communication between a fluid injection system and one or more external systems. [Background technology]

[0003] 2.Technical considerations Fluid injection systems (e.g., medical fluid delivery systems) may be used by medical personnel, such as physicians, in medical diagnostic and / or therapeutic procedures. For example, medical personnel may use a fluid injection system to inject one or more medical fluids into a patient. Fluid injection systems may be used for pressurized injection of medical fluids, such as radiopaque contrast materials (e.g., contrast agents, radiocontrast media, etc.), and / or flushing agents, such as 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 injection systems are designed to deliver a preset amount of medical fluid at a preset flow rate.

[0004] In some cases, a fluid injection system may be part of a group of devices used in a medical treatment facility, such as a hospital. For example, the fluid injection system may be connected to a medical imaging system, such as a CT scanner and / or an MRI scanner, and an information system for the medical treatment facility. In some situations, the fluid injection system and the medical imaging system may communicate information related to the treatment performed on the patient to the information system via a communications network, and the information system may store the information in an appropriate database so that medical personnel can review the information. Summary of the Invention [Means for solving the problem]

[0005] Accordingly, systems, methods, and computer program products are disclosed that provide a gateway device that enables communication between a fluid infusion system and one or more external systems.

[0006] Further non-limiting embodiments or aspects are described in the following numbered clauses:

[0007] Item 1: A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: a gateway device, the gateway device comprising at least one processor programmed or configured to: provide a first communication interface between a hospital information system and the fluid injection system; provide a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and provide a third communication interface between a medical imaging system and the fluid injection system.

[0008] Item 2: The system described in Item 1, wherein at least one processor is further programmed or configured to transmit informatics-related data received from the hospital information system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0009] Clause 3: The system of clause 1 or clause 2, wherein at least one processor is further programmed or configured to receive informatics-related data from a hospital information system via a communications network in accordance with a communications protocol for communicating informatics-related data.

[0010] Clause 4: The system of any one of clauses 1 to 3, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to the patient's treatment from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0011] Clause 5: The system of any one of clauses 1 to 4, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to the operation of the fluid injection system from the hospital information system via the communications network based on the API call.

[0012] Clause 6: The system of any one of clauses 1 to 5, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to radiology images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0013] Clause 7: The system of any one of clauses 1 to 6, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive radiation treatment-related data from the hospital information system over the communications network in accordance with a Health Level Seven (HL7) standard communications protocol.

[0014] Clause 8: The system of any one of clauses 1 to 7, wherein upon receiving data related to informatics from the hospital information system, at least one processor is programmed or configured to receive data related to radiation dose during a radiological imaging examination from the hospital information system via a communications network based on an API call.

[0015] Clause 9: The system described in any one of clauses 1 to 8, wherein at least one processor is further programmed or configured to receive data related to service functions of the fluid injection system from the fluid injector service and control system via a communication network based on an API call.

[0016] Clause 10: A system described in any one of clauses 1 to 9, wherein at least one processor is further programmed or configured to receive data related to operation of the medical imaging system from the medical imaging system via a communications network based on an API call.

[0017] Clause 11: A system described in any one of clauses 1 to 10, wherein at least one processor is further programmed or configured to transmit data relating to service information received from the fluid injector service and control system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0018] Clause 12: A system described in any one of clauses 1 to 11, wherein at least one processor is further programmed or configured to transmit data related to images received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0019] Clause 13: The system of any one of clauses 1 to 12, wherein at least one processor is further programmed or configured to provide a graphical user interface to a user for receiving user input.

[0020] Clause 14: The system of any one of clauses 1 to 13, further comprising a memory device, the memory device storing a plurality of applications, the plurality of applications comprising: an informatics application associated with a first communication interface between a hospital information system and the fluid injection system; a remote service connectivity application associated with a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and an image connectivity system application associated with a third communication interface between a medical imaging system and the fluid injection system.

[0021] Clause 15: A system as described in any one of clauses 1 to 14, further comprising a display unit, wherein the plurality of applications comprises a fourth application associated with a graphical user interface provided to the user by the display unit for receiving user input.

[0022] Clause 16: The system of any one of clauses 1 to 15, wherein the gateway device comprises a universal gateway.

[0023] Clause 17: A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: the fluid injection system; and a gateway device, the gateway device comprising at least one processor programmed or configured to: provide a first communication interface between a hospital information system and the fluid injection system; provide a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and provide a third communication interface between a medical imaging system and the fluid injection system.

[0024] Clause 18: The system described in clause 17, wherein at least one processor is further programmed or configured to transmit informatics-related data received from the hospital information system to the fluid injection system via the communications network based on an API call from the fluid injection system.

[0025] Clause 19: The system of clause 17 or clause 18, wherein at least one processor is further programmed or configured to receive informatics-related data from a hospital information system via a communications network in accordance with a communications protocol for communicating informatics-related data.

[0026] Clause 20: The system of any one of clauses 17 to 19, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive patient treatment-related data from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0027] Clause 21: The system of any one of clauses 17 to 20, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to the operation of the fluid injection system from the hospital information system via the communications network based on the API call.

[0028] Clause 22: The system of any one of clauses 17 to 21, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to radiology images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0029] Clause 23: The system of any one of clauses 17 to 22, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive radiation treatment-related data from the hospital information system via a communications network in accordance with a Health Level Seven (HL7) standard communications protocol.

[0030] Clause 24: A system described in any one of clauses 17 to 23, wherein upon receiving data related to informatics from a hospital information system, at least one processor is programmed or configured to receive data related to radiation dose during a radiological imaging examination from the hospital information system via a communications network based on an API call.

[0031] Clause 25: The system described in any one of clauses 17 to 24, wherein at least one processor is further programmed or configured to receive data related to service functions of the fluid injection system from the fluid injector service and control system via a communication network based on an API call.

[0032] Clause 26: A system described in any one of clauses 17 to 25, wherein at least one processor is further programmed or configured to receive data related to operation of the medical imaging system from the medical imaging system via a communications network based on an API call.

[0033] Clause 27: A system described in any one of clauses 17 to 26, wherein at least one processor is further programmed or configured to transmit data relating to service information received from the fluid injector service and control system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0034] Clause 28: A system described in any one of clauses 17 to 27, wherein at least one processor is further programmed or configured to transmit data related to images received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0035] Clause 29: The system of any one of clauses 17 to 28, wherein at least one processor is further programmed or configured to provide a graphical user interface to a user for receiving user input.

[0036] Clause 30: The system of any one of clauses 17 to 29, further comprising a memory device, the memory device storing a plurality of applications, the plurality of applications comprising: an informatics application associated with a first communication interface between a hospital information system and the fluid injection system; a remote service connectivity application associated with a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and an image connectivity system application associated with a third communication interface between a medical imaging system and the fluid injection system.

[0037] Clause 31: A system as described in any one of clauses 17 to 30, further comprising a display unit, wherein the plurality of applications comprises a fourth application associated with a graphical user interface provided to the user by the display unit for receiving user input.

[0038] Clause 32: The system of any one of clauses 17 to 31, wherein the gateway device comprises a universal gateway.

[0039] Clause 33: A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: the fluid injection system; the fluid injection system comprising a gateway device; and at least one processor programmed or configured to: provide a first communication interface between a hospital information system and the fluid injection system; provide a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and provide a third communication interface between a medical imaging system and the fluid injection system.

[0040] Clause 34: The system described in clause 33, wherein at least one processor is further programmed or configured to transmit informatics-related data received from the hospital information system to the fluid injection system via the communications network based on an API call from the fluid injection system.

[0041] Clause 35: The system of clause 33 or clause 34, wherein at least one processor is further programmed or configured to receive informatics-related data from a hospital information system via a communications network in accordance with a communications protocol for communicating informatics-related data.

[0042] Clause 36: The system of any one of clauses 33 to 35, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to the patient's treatment from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0043] Clause 37: The system of any one of clauses 33 to 36, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to the operation of the fluid injection system from the hospital information system via the communications network based on the API call.

[0044] Clause 38: The system of any one of clauses 33 to 37, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive data related to radiology images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol.

[0045] Clause 39: The system of any one of clauses 33 to 38, wherein upon receiving informatics-related data from the hospital information system, at least one processor is programmed or configured to receive radiation treatment-related data from the hospital information system via a communications network in accordance with a Health Level Seven (HL7) standard communications protocol.

[0046] Clause 40: A system described in any one of clauses 33 to 39, wherein upon receiving data related to informatics from a hospital information system, at least one processor is programmed or configured to receive data related to radiation dose during a radiological imaging examination from the hospital information system via a communications network based on an API call.

[0047] Clause 41: The system described in any one of clauses 33 to 40, wherein at least one processor is further programmed or configured to receive data related to service functions of the fluid injection system from the fluid injector service and control system via a communication network based on an API call.

[0048] Clause 42: A system described in any one of clauses 33 to 41, wherein at least one processor is further programmed or configured to receive data related to operation of the medical imaging system from the medical imaging system via a communications network based on an API call.

[0049] Clause 43: A system described in any one of clauses 33 to 42, wherein at least one processor is further programmed or configured to transmit data relating to service information received from the fluid injector service and control system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0050] Clause 44: A system described in any one of clauses 33 to 43, wherein at least one processor is further programmed or configured to transmit data related to images received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system.

[0051] Clause 45: A system according to any one of clauses 33 to 44, wherein at least one processor is further programmed or configured to provide a graphical user interface to a user for receiving user input.

[0052] Clause 46: The system of any one of clauses 33 to 45, further comprising a memory device, the memory device storing a plurality of applications, the plurality of applications comprising: an informatics application associated with a first communication interface between a hospital information system and the fluid injection system; a remote service connectivity application associated with a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system; and an image connectivity system application associated with a third communication interface between a medical imaging system and the fluid injection system.

[0053] Clause 47: A system as described in any one of clauses 33 to 46, further comprising a display unit, wherein the plurality of applications comprises a fourth application associated with a graphical user interface provided to the user by the display unit for receiving user input.

[0054] Clause 48: The system of any one of clauses 33 to 47, wherein the gateway device comprises a universal gateway.

[0055] These and other features and characteristics of the present disclosure, as well as the method and function of operation of the associated elements of structure, and economies of combination of parts and manufacture, will become more apparent from a consideration of the following description and appended claims, taken in conjunction with the accompanying drawings, all of which form a part hereof, and in which like reference numerals indicate corresponding parts in the various views. It is to be expressly understood, however, 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 claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0056] Additional advantages and details of non-limiting embodiments or aspects are explained in detail below with reference to exemplary embodiments shown in the accompanying schematic drawings. [Brief explanation of the drawings]

[0057] [Figure 1] FIG. 1 illustrates a non-limiting embodiment of an environment in which the systems, methods, and / or computer program products described herein may be implemented in accordance with the present disclosure. [Figure 2] FIG. 2 is a diagram of a non-limiting embodiment of components of one or more devices and / or one or more systems of FIG. 1. [Figure 3] 1 is a diagram of a non-limiting embodiment of a system that enables communication between a fluid injection system and at least one of a plurality of external systems. [Figure 4]FIG. 1 is a diagram of a non-limiting embodiment of an application of a gateway device. [Figure 5] 1A-1C are diagrams of non-limiting embodiments of implementations of systems that enable communication between a fluid injection system and at least one of a plurality of external systems. [Figure 6] 1A-1C are diagrams of non-limiting embodiments of implementations of systems that enable communication between a fluid injection system and at least one of a plurality of external systems. [Figure 7] FIG. 1 is a diagram of a non-limiting embodiment of a gateway device. [Figure 8] 1A-1C illustrate exemplary CT image suites showing non-limiting embodiments of implementations of fluid injection systems and gateway devices. [Figure 9] FIG. 1 illustrates a non-limiting embodiment of a fluid injection system including a gateway device. [Figure 10] FIG. 1 illustrates a non-limiting embodiment of another fluid injection system including a gateway device. DETAILED DESCRIPTION OF THE INVENTION

[0058] For purposes of the following description, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "lateral," "longitudinal," and derivatives thereof, refer to the present disclosure as directions in the drawings. However, it should be understood that the present disclosure may contemplate various alternative modifications and step sequences unless expressly specified to the contrary. It should also be understood that the specific devices and processes illustrated in the accompanying drawings and described in the following specification are merely exemplary embodiments or aspects of the present disclosure. Accordingly, specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments disclosed herein are not to be considered limiting, unless expressly stated.

[0059] As used herein, aspects, components, elements, structures, operations, steps, functions, instructions, and the like should not be construed as critical or essential unless explicitly stated otherwise. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more" and "at least one." Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one." When only one item is intended, the term "one" or similar term is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified.

[0060] As used herein, the terms “communication” and “communicating” may refer to receiving, receiving, sending, transferring, providing, etc., information (e.g., data, signals, messages, instructions, commands, etc.). One unit (e.g., a device, a system, a component of a device or system, combinations thereof, etc.) communicating with another unit means that the one unit may receive information directly or indirectly from the other unit and / or transmit information to the other unit. This may refer to a direct or indirect connection that is wired and / or wireless in nature. 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, a first unit may communicate with a second unit even if the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may communicate with a second unit if at least one intermediate unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and transmits the processed information to the second unit. In some non-limiting embodiments, information may refer to network packets containing data (e.g., data packets, etc.).

[0061] In some non-limiting embodiments, the fluid injection system may be connected to a medical imaging system, which may itself be connected to an information system for a medical treatment facility, so that information related to the operation of the fluid injection system and / or the medical imaging system may be used by medical personnel during patient treatment.

[0062] However, to connect the fluid injection system to the medical imaging and information systems, the fluid injection system may require complex network communication equipment so that the fluid injection system can communicate with the medical imaging and information systems efficiently, securely, and without error. Additionally, the fluid injection system may require specially configured network equipment and / or reprogramming to communicate with the medical imaging and information systems based on the network communication configuration of the medical imaging and / or information systems.

[0063] Systems, methods, and computer program products are disclosed that provide solutions to the above-mentioned problems. For example, as disclosed herein, a system for enabling communication between a fluid injection system and at least one of a plurality of external systems includes a gateway device, the gateway device including at least one processor programmed or configured to provide a first communication interface between a hospital information system and the fluid injection system, a second communication interface between a fluid injector service and control system associated with the fluid injection system and the fluid injection system, and a third communication interface between a medical imaging system and the fluid injection system. In this manner, the system may eliminate the need for complex network communication equipment as part of or in addition to the fluid injection system. Furthermore, such a system may reduce the amount of network resources consumed by updating and / or configuring the fluid injection system to connect the fluid injection system with the medical imaging system and / or the hospital information system.

[0064] 1, which is a diagram of a non-limiting embodiment of an environment 100 in which the devices, systems, methods, and / or computer program products described herein may be implemented. As shown in FIG. 1, environment 100 includes a gateway device 102, a fluid injection system 104, and multiple external systems, such as a hospital information system 106, a medical imaging system 108, a fluid injection system service and control system 110, and a web server 112. Gateway device 102 may interconnect (e.g., establish connections for communication, etc.) fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112 via communications networks 114-1, 114-2, 114-3, 114-4, and 114-5 (individually referred to as communications networks 114 or in the plural as communications networks 114 unless otherwise noted). In some non-limiting embodiments, the gateway device 102 may interconnect (e.g., establish connections for communication, etc.) the fluid injection system 104, the hospital information system 106, the medical imaging system 108, the fluid injection system service and control system 110, and / or the web server 112 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0065] In some non-limiting embodiments, gateway device 102 may include one or more devices that may communicate with fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112 via communication network 114. For example, gateway device 102 may include devices such as a telecommunications gateway (e.g., a network gateway), a universal gateway, etc. Additionally or alternatively, gateway device 102 may include one or more computing devices such as one or more desktop computers, one or more mobile devices (e.g., one or more tablets, one or more smartphones, etc.), one or more servers, etc. In some non-limiting embodiments, gateway device 102 may include one or more applications (e.g., software applications) that implement a set of functions on an external application programming interface (API) through which fluid injection system 104 may send data to and receive data from external systems associated with the external API. In one example, the gateway device 102 may provide the ability to download applications, such as Bayer S / W applications, to the gateway device 102 (e.g., a mobile device of the gateway device 102 providing carry-your-own-device operation). In some non-limiting embodiments, applications may be supported by applications associated with the fluid injection system 104 where the gateway device 102 (e.g., a mobile device of the gateway device 102) may function as a control room display and may be the only device controlling the fluid injection system 104; in such examples, the gateway device 102 may provide authentication functionality.In some non-limiting embodiments, the gateway device 102 may access a network resource, such as a uniform resource locator (URL), to determine applications (e.g., application services) available to the gateway device 102, and the gateway device 102 and / or fluid injection system 104 may download one or more applications via the gateway device 102.

[0066] In some non-limiting embodiments, fluid injection system 104 may include one or more devices that communicate with gateway device 102, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112 via communications network 114 and may perform fluid injection procedures. For example, fluid injection system 104 may include one or more fluid injectors that communicate via communications network 114 and may perform fluid injection procedures including radiopaque contrast materials (e.g., contrast agents, radiocontrast agents, contrast media, etc.), such as iodine-based contrast agents and / or gadolinium-based contrast agents.

[0067] In some non-limiting embodiments, the fluid injection system 104 includes one or more injection devices (e.g., one or more fluid injection devices). In some non-limiting embodiments, the fluid injection system 104 is configured to administer (e.g., inject, feed, etc.) a contrast fluid containing a contrast agent to the patient and / or administer an aqueous fluid, such as saline, to the patient before, during, and / or after administration of the contrast fluid. For example, the fluid injection system 104 may inject one or more prescribed doses of contrast fluid directly into the patient's bloodstream via a hypodermic needle and syringe. In some non-limiting embodiments, the fluid injection system 104 may be configured to continuously administer an aqueous fluid to the patient through a peripheral intravenous line (PIV) and catheter, where one or more prescribed doses of contrast fluid may be introduced into the PIV and administered to the patient via the catheter. In some non-limiting embodiments, the fluid injection system 104 is configured to inject a given dose of contrast fluid followed by a specific volume of aqueous fluid. In some non-limiting embodiments, the fluid injection system 104 may be configured as a fluid injection system, such as those disclosed in U.S. patent application Ser. No. 09 / 715,330, filed Nov. 17, 2000, issued as U.S. Patent No. 6,643,537; U.S. patent application Ser. No. 09 / 982,518, filed Oct. 18, 2001, issued as U.S. Patent No. 7,094,216; U.S. patent application Ser. No. 10 / 825,866, filed Apr. 16, 2004, issued as U.S. Patent No. 7,556,619; U.S. patent application Ser. No. 10 / 825,866, filed May 7, 2009, issued as U.S. Patent No. This may include one or more exemplary injection systems or injectors disclosed in U.S. patent application Ser. No. 12 / 437,011, issued as U.S. Patent No. 8,337,456, U.S. patent application Ser. No. 12 / 476,513, filed June 2, 2009, issued as U.S. Patent No. 8,147,464, and U.S. patent application Ser. No. 11 / 004,670, filed December 3, 2004, issued as U.S. Patent No. 8,540,698, the disclosures of each of which are incorporated herein by reference in their entirety.In some non-limiting embodiments, the fluid injection system 104 may include a MEDRAD® Stellant CT injection system, a MEDRAD® Stellant Flex CT injection system, a MEDRAD® MRXperion MR injection system, a MEDRAD® Mark 7 Arterion injection system, a MEDRAD® Intego PET injection system, or a MEDRAD® Centargo CT injection system, all of which are provided by Bayer Healthcare LLC.

[0068] In some non-limiting embodiments, hospital information system 106 may include one or more devices that may communicate with gateway device 102, fluid injection system 104, medical imaging system 108, and fluid injection system service and control system 110 via communication network 114. For example, hospital information system 106 may include one or more computing devices, such as one or more desktop computers, one or more mobile devices, one or more servers, etc. In some non-limiting embodiments, hospital information system 106 may include one or more subsystems, such as a patient procedure tracking system (e.g., a system that operates a modality worklist, a system that provides patient demographic information for fluid injection procedures and / or medical imaging procedures, etc.), a fluid injector management system, an image archiving and communication system (e.g., a Picture Archiving and Communication System (PACS)), a radiology information system, and / or a radiology analysis system (e.g., Radimetrics Enterprise Application, marketed and sold by Bayer HealthCare LLC).

[0069] In some non-limiting embodiments, medical imaging system 108 may include one or more devices that may communicate with gateway device 102, fluid injection system 104, hospital information system 106, fluid injection system service and control system 110, and / or web server 112 via communications network 114. For example, medical imaging system 108 may include one or more scanners, such as a CT scanner and / or an MRI scanner, that communicate via communications network 114 and that may perform medical imaging procedures that include the use of radiopaque contrast materials.

[0070] In some non-limiting embodiments, fluid injection system service and control system 110 may include one or more devices that may communicate with gateway device 102, fluid injection system 104, hospital information system 106, medical imaging system 108, and / or web server 112 via communication network 114. For example, fluid injection system service and control system 110 may include one or more computing devices, such as one or more desktop computers, one or more mobile devices, one or more servers, etc. In some non-limiting embodiments, fluid injection system service and control system 110 may provide functionality for a user (e.g., service personnel) to interact with fluid injection system 104 and / or gateway device 102 for maintenance purposes. For example, fluid injection system service and control system 110 may provide functionality for a user to perform upgrades, perform restore operations, logging operations, data backup operations, etc. In some non-limiting embodiments, the fluid injection system service and control system 110 may be a subsystem of the hospital information system 106, and the fluid injection system service and control system 110 may communicate with the gateway device 102 via a communication network 114-4.

[0071] In some non-limiting embodiments, the fluid infusion system service and control system 110 may include back-end systems associated with the gateway device 102 and / or the fluid infusion system 104. In some non-limiting embodiments, the fluid infusion system service and control system 110 may include a cloud computing system that stores data in an associated database. In some non-limiting embodiments, the fluid infusion system service and control system 110 may interact with the fluid infusion system 104 to provide functionality such as remote equipment services for the fluid infusion system 104 (e.g., VirtualCARE® Remote Support services for infusion systems and devices offered by Bayer HealthCare LLC). In some non-limiting embodiments, the fluid infusion system service and control system 110 may be operated by or on behalf of the OEM of the fluid infusion system 104 (e.g., the original equipment manufacturer (OEM) of one or more components or devices of the fluid infusion system 104), the provider of the fluid infusion system 104, the imaging site or hospital where the fluid infusion system 104 operates, a service technician assigned to the fluid infusion system 104, etc.

[0072] In some non-limiting embodiments, web server 112 may include one or more devices that may communicate with gateway device 102, fluid injection system 104, hospital information system 106, medical imaging system 108, and / or fluid injection system service and control system 110 via communication network 114. For example, web server 112 may include one or more computing devices, such as one or more servers. In some non-limiting embodiments, web server 112 may provide a web-based user interface to gateway device 102 that enables control and / or access to functionality of fluid injection system 104. In some non-limiting embodiments, web server 112 may receive requests for network resources and transmit content of network resources and / or messages (e.g., error messages) related to network resources via network protocols (e.g., HTTP, HTTPS, etc.).

[0073] In some non-limiting embodiments, communication network 114 (e.g., one or more of communication networks 114-1, 114-2, 114-3, 114-4, and 114-5) may include one or more wired and / or wireless networks. For example, communication network 114 may include a cellular network (e.g., a Long Term Evolution (LTE) network, a third-generation (3G) network, a fourth-generation (4G) network, a fifth-generation (5G) network, a code division multiple access (CDMA) network, etc.), a local area network (LAN), a wide area network (WAN), a wireless LAN (WLAN), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, an Ethernet network, a universal serial bus (USB) network, a cloud computing network, etc., and / or a combination of some or all of these or other types of networks.

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

[0075] 2, which is a diagram of example components of device 200. Device 200 may correspond to gateway device 102, fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112. In some non-limiting aspects or embodiments, gateway device 102, fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112 may include at least one device 200 and / or at least one component of device 200. As shown in FIG. 2, device 200 may include a bus 202, a processor 204, a memory 206, a storage component 208, an input component 210, an output component 212, and a communication component 214.

[0076] Bus 202 may include components that enable communication between components of device 200. In some non-limiting embodiments or aspects, processor 204 may be implemented in hardware, software, or a combination of hardware and software. For example, processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated 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 processor 204.

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

[0078] Input components 210 may include components through which device 200 may receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, a microphone, a camera, etc.). Additionally or alternatively, input components 210 may include sensors that detect information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output components 212 may include components that provide output information from device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

[0079] Communications component 214 may include transceiver-like components (e.g., a walkie-talkie, a separate receiver and transmitter, etc.) that enable device 200 to communicate with other devices via wired connections, wireless connections, a combination of wired and wireless connections, etc. Communications component 214 may enable device 200 to receive information from and / or provide information to another device. For example, communications component 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

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

[0081] Software instructions may be read into memory 206 and / or storage component 208 from another computer-readable medium or from another device via communication component 214. Software instructions stored in memory 206 and / or storage component 208, when executed, may cause processor 204 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement one or more processes described herein. Thus, embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software.

[0082] The memory 206 and / or storage component 208 may include a data store or one or more data structures (e.g., databases, etc.) The device 200 may retrieve information from, store information in, or retrieve stored information in the data store or one or more data structures in the memory 206 and / or storage component 208.

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

[0084] 3 and 4, FIG. 3 is a diagram of a non-limiting embodiment of a system 300 that enables communication between a fluid injection system and at least one of a plurality of external systems. In some non-limiting embodiments or aspects, one or more of the functions described herein with respect to system 300 may be performed (e.g., fully, partially, etc.) by gateway device 102. In some non-limiting embodiments, one or more of the functions described with respect to system 300 may be performed (e.g., fully, partially, etc.) by another device or group of devices that are separate from and / or include gateway device 102, such as fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or display unit 308. FIG. 4 is a diagram of a non-limiting embodiment of an application of gateway device 102.

[0085] 3 and 4, gateway device 102 may include multiple applications, such as a system management application 202-A, an informatics application 202-B, a fluid injection system service application 202-C, a data management application 202-D, and an imaging system connectivity application 202-E. In some non-limiting embodiments, the multiple applications may be stored in a memory device of gateway device 102. In some non-limiting embodiments, each of the multiple applications may be associated with an API (e.g., a first API associated with the first application, a second API associated with the second application, a third API associated with the third application, etc.) associated with the respective application through which the fluid injection system 104 may connect (e.g., communicate, establish a communication interface, etc.) with the gateway device 102 and / or through which the gateway device 102 may connect with the hospital information system 106 (e.g., individual subsystems of the hospital information system 106, such as the patient procedure tracking system 206-A, the fluid injector management system 206-B, the image archiving and communication system 206-C, the radiology information system 206-D, and / or the radiology analysis system 206-E).

[0086] In some non-limiting embodiments, each application of the plurality of applications may comprise a common software platform application that provides common features and functionality common to all fluid infusion system modalities. In this manner, the gateway device 102 may interface with fluid infusion systems regardless of the particular manufacturer of the fluid infusion system.

[0087] In some non-limiting embodiments, system management application 202-A may provide operational control of aspects of gateway device 102. For example, system management application 202-A may provide management of operational control of informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, and / or imaging system connectivity application 202-E. In some non-limiting embodiments, system management application 202-A may provide a user interface (e.g., a web-based user interface) through which a user may control fluid injection system 104. For example, a user may initiate medical imaging, fluid injection, and / or other additional procedures performed by fluid injection system 104 via the user interface. Additionally or alternatively, the user interface may allow a user to control aspects of informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, and / or imaging system connectivity application 202-E.

[0088] 3, system 300 may include a display unit 308. In some non-limiting embodiments, display unit 308 may display a user interface (e.g., a web-based user interface) provided by system management application 202-A. In some non-limiting embodiments, display unit 308 may include a computing device such as a smart display unit, a portable computer such as a tablet or laptop, or the like. In some non-limiting embodiments, display unit 308 may include a touch screen for receiving input by a user.

[0089] In some non-limiting embodiments, informatics application 202-B may be associated with a first communication interface of gateway device 102 between hospital information system 106 and fluid infusion system 104. For example, gateway device 102 may provide a first communication interface between hospital information system 106 and fluid infusion system 104 based on informatics application 202-B. In some non-limiting embodiments, the communication interface may include a set of communication settings (e.g., protocols, standards, etc.) by which one device (e.g., one device of the system) may electrically communicate with another device. In some non-limiting embodiments, informatics application 202-B may provide functionality for fluid infusion system 104 to interact with hospital information system 106 (e.g., any of multiple subsystems of hospital information system 106). Additionally or alternatively, informatics application 202-B may provide storage of data for fluid infusion system 104.

[0090] In some non-limiting embodiments, fluid injection system service application 202-C may be associated with a second communication interface of gateway device 102 between fluid injector service and control system 110 and fluid injection system 104. For example, gateway device 102 may provide a second communication interface between fluid injection system 104 and fluid injector service and control system 110 associated with fluid injection system 104. In some non-limiting embodiments, fluid injection system service application 202-C may provide functionality for a user (e.g., service personnel) to communicate with fluid injection system 104 and / or gateway device 102 to perform maintenance operations.

[0091] In some non-limiting embodiments, data management application 202-D may be associated with a third communication interface of gateway device 102 between hospital information system 106 and fluid infusion system 104. For example, gateway device 102 may provide a third communication interface between hospital information system 106 and fluid infusion system 104. In some non-limiting embodiments, the third communication interface may be, or may be the same as, or similar to, the first communication interface between hospital information system 106 and fluid infusion system 104. In some non-limiting embodiments, data management application 202-D may provide functionality related to file system and database management for gateway device 102. Additionally or alternatively, data management application 202-D may provide operational control over the storage of data for fluid infusion system 104.

[0092] In some non-limiting embodiments, the imaging system connection application 202-E may be associated with a fourth communication interface of the gateway device 102 between the medical imaging system 108 and the fluid injection system 104. For example, the gateway device 102 may provide a fourth communication interface between the medical imaging system 108 and the fluid injection system 104. In some non-limiting embodiments, the system management application 202-A may be associated with a fourth interface of the gateway device 102 between a user and the fluid injection system 104 and / or the gateway device 102. In some non-limiting embodiments, the imaging system connection application 202-E may provide functionality for the fluid injection system 104 to interact with the medical imaging system 108. In some non-limiting embodiments, the imaging system connection application 202-E may abstract the interface of the medical imaging system 108 (e.g., an ISI interface, an ISI2 interface, and / or a Connect CT interface) into a standard format for utilization by the fluid injection system 104.

[0093] In some non-limiting embodiments, gateway device 102 may provide a first communications interface between hospital information system 106 and fluid injection system 104 such that informatics application 202-B provides the ability for fluid injection system 104 to receive data based on API calls from fluid injection system 104 to gateway device 102. In some non-limiting embodiments, gateway device 102 may transmit informatics-related data received from hospital information system 106 to fluid injection system 104 via communications network 114. For example, gateway device 102 may transmit informatics-related data received from hospital information system 106 to fluid injection system 104 based on API calls from the fluid injection system to informatics application 202-B via communications network 114. The informatics-related data may include data related to patient identification and data related to a patient examination procedure (e.g., a fluid injection procedure and a medical imaging procedure to be performed on a patient), such as data related to contrast fluid provided during the fluid injection procedure, the gauge of a catheter used during the fluid injection procedure, and a fluid injection protocol for the fluid injection procedure. In some non-limiting embodiments, the gateway device 102 may store data related to patient testing procedures and / or data related to the configuration of the fluid injection system 104 with the informatics application 202-B.

[0094] 3, the hospital information system 106 may include multiple subsystems, which may include a patient procedure tracking system 206-A, a fluid infuser management system 206-B, an image archiving and communication system 206-C, a radiology information system 206-D, and a radiology analysis system 206-E.

[0095] In some non-limiting embodiments, gateway device 102 may receive informatics-related data from hospital information system 106 via communications network 114 according to a communications protocol for communicating informatics-related data. For example, gateway device 102 may receive data regarding patient treatment from hospital information system 106 (e.g., from patient treatment tracking system 206-A) via communications network 114 (e.g., communications network 114-2) according to the Digital Imaging and Communications in Medicine (DICOM) communications protocol, and data regarding the operation of a fluid injection system from hospital information system 106 (e.g., from fluid injector management system 206-B) via communications network 114 based on an API call (e.g., an API call from gateway device 102 to fluid injector management system 206-B) according to the DICOM communications protocol. The gateway device 102 may receive data regarding radiology images from the hospital information system 106 (e.g., from image archiving and communication system 206-C) via the communication network 114, data regarding patient examination procedures from the hospital information system 106 (e.g., from radiology information system 206-D) via the communication network 114 according to a Health Level Seven (HL7) standard communication protocol, and / or data regarding radiation dosage during medical imaging procedures from the hospital information system 106 (e.g., from radiology analysis system 206-E) via the communication network 114 based on an API call (e.g., an API call from the gateway device 102 to the radiology analysis system 206-E).

[0096] In some non-limiting embodiments, the gateway device 102 may provide a second communication interface between the fluid injection system service and control system 110 and the fluid injection system 104 such that the fluid injection system service application 202-C provides the ability for the fluid injection system 104 to receive data based on an API call from the fluid injection system 104 to the gateway device 102. In some non-limiting embodiments, the gateway device 102 may transmit data related to service information received from the fluid injection system service and control system 110 to the fluid injection system 104 via the communication network 114. For example, the gateway device 102 may transmit data related to service information received from the fluid injection system service and control system 110 to the fluid injection system 104 based on an API call from the fluid injection system 104 to the fluid injection system service application 202-C via the communication network 114. In some non-limiting embodiments, gateway device 102 may receive data related to the service functions of fluid injection system 104 from fluid injection system service and control system 110 via communication network 114 (e.g., communication network 114-4 or communication network 114-2) based on an API call (e.g., an API call from gateway device 102 to fluid injection system service and control system 110).

[0097] In some non-limiting embodiments, the gateway device 102 may provide a third communication interface between the medical imaging system 108 and the fluid injection system 104 such that the imaging system connectivity application 202-E provides the ability for the fluid injection system 104 to receive data based on an API call from the fluid injection system 104 to the gateway device 102. In some non-limiting embodiments, the gateway device 102 may transmit data related to images received from the medical imaging system 108 to the fluid injection system 104 via the communications network 114. For example, the gateway device 102 may transmit data related to images received from the medical imaging system 108 to the fluid injection system 104 based on an API call from the fluid injection system 104 to the imaging system connectivity application 202-E via the communications network 114. In some non-limiting embodiments, the gateway device 102 may transmit data related to a fluid injection procedure received from the fluid injection system 104 (e.g., data related to the length of time for injecting radiographic contrast material into a patient) to the medical imaging system 108 via the communications network 114. For example, the gateway device 102 may transmit data related to a fluid injection procedure received from the fluid injection system 104 to the medical imaging system 108 based on an API call from the medical imaging system 108 to the imaging system connectivity application 202-E (e.g., an API call for the Imaging System Interface (ISI), an API call for the ISI2 interface, an API call for the Connect CT interface, etc.) via the communications network 114. In some non-limiting embodiments, the medical imaging system 108 may perform a medical imaging procedure on the patient based on the data related to the fluid injection procedure. In some non-limiting embodiments, the gateway device 102 may receive data related to the operation of the medical imaging system 108 from the medical imaging system 108 based on an API call (e.g., an API call from the gateway device 102 to the medical imaging system 108) via the communications network 114 (e.g., communications network 114-3).

[0098] In some non-limiting embodiments, the gateway device 102 may provide a fourth interface to a user to receive user input, such that the system management application 202-A may provide the gateway device 102 with the ability to receive user input from a user. In some non-limiting embodiments, the fourth interface is a graphical user interface. In some non-limiting embodiments, the gateway device 102 may provide a fourth interface to a user (e.g., an administrator) to configure the communications network 114, the applications stored on the gateway device 102, and / or the operating system of the gateway device 102. In some non-limiting embodiments, the gateway device 102 may provide a fourth interface to enable a user to manage the configuration of APIs associated with applications stored on the gateway device 102 (e.g., to provide control functions and adjust settings for communications, such as device addresses, communication protocols, etc.). In some non-limiting embodiments, the system management application 202-A provides APIs through which the fluid infusion system 104 may interface with high-level functionality of the gateway device 102. For example, the gateway device 102 may provide access to high-level functionality of the gateway device 102 based on API calls from the fluid infusion system 104 to the system management application 202-A. In some non-limiting embodiments, the system management application 202-A may provide a GUI to a user (e.g., an administrator) to configure one or more communication networks 114, manage users of the gateway device 102, control OS and application updates of the gateway device 102, and / or monitor applications of the gateway device 102.

[0099] As further shown in FIG. 4 , each of the multiple applications of gateway device 102 may provide services (e.g., additional software or hardware functionality, such as microservices, features, etc.) associated with each application. In some non-limiting embodiments, system management application 202-A may include network management services 4022-A, upgrade management services 4022-B, security management services 4022-C, and / or container management services 4022-D. In some non-limiting embodiments, network management services 4022-A may provide functionality related to controlling communications over communications network 114. For example, network management services 4022-A may provide control over network addresses, communications protocols, etc. In some non-limiting embodiments, upgrade management services 4022-B may provide functionality related to controlling upgrades made to applications and / or services of gateway device 102. For example, upgrade management services 4022-B may provide control over upgrades made to services of informatics application 202-B. In some non-limiting embodiments, security management services 4022-C may provide functionality related to controlling access to gateway device 102. For example, security management services 4022-C may provide control over which users may access gateway device 102, authentication methods for accessing gateway device 102, etc. In some non-limiting embodiments, container management services 4022-D may provide functionality related to controlling services provided by informatics application 202-B, which may be structured as containers.

[0100] In some non-limiting embodiments, informatics applications 202-B may include a patient procedure tracking service 4024-A, an image archiving and communication service 4024-B, a radiology information service 4024-C, a radiology analysis service 4024-D, a fluid injector management service 4024-E, and / or a data insights service 4024-F. In some non-limiting embodiments, the patient procedure tracking service 4024-A may provide functionality related to tracking of patient procedures performed by the fluid injection system 104 (e.g., functionality related to patient demographic information for fluid injection procedures and / or medical imaging procedures). For example, the patient procedure tracking service 4024-A may provide reporting, alerts, messaging, etc. regarding the timing of patient procedures. In some non-limiting embodiments, the image archiving and communication service 4024-B may provide functionality related to images received during fluid injection procedures and / or medical imaging procedures (e.g., images provided by medical imaging techniques, scans, scanned images, etc.). For example, image archiving and communication services 4024-B may provide reception, storage, access, transmission, etc., for images. In some non-limiting embodiments, radiology information services 4024-C may provide functionality related to recording of medical imaging procedures. In some non-limiting embodiments, radiology information services 4024-C may provide patient scheduling, resource management, exam performance tracking, reporting, results distribution, and / or procedure billing for medical imaging procedures. In some non-limiting embodiments, radiology analysis services 4024-D may provide functionality related to metrics for medical imaging procedures (e.g., radiology imaging procedures, radiology imaging exams). For example, radiology analysis services 4024-D may provide reporting, tracking, alerts, messaging, etc., regarding information related to medical imaging procedures, such as data related to radiation and / or contrast fluid volumes, information regarding treatment protocol management, and / or information regarding benchmarking. In some non-limiting embodiments, fluid injector management services 4024-E may provide functionality related to control and / or management of injection protocols for fluid injection systems.For example, the fluid injector management service 4024-E may provide for receiving, storing, transmitting, and / or managing fluid injection systems and / or fluid injection protocols used by the fluid injection systems. In some non-limiting embodiments, the data insights service 4024-F may provide functionality related to insights gained from data related to fluid injection and / or medical imaging procedures. For example, the data insights service 4024-F may provide reporting, tracking, alerts, messaging, etc. regarding equipment (e.g., medical supplies used during the procedure, including contrast fluids, intravenous catheters, etc.) and / or services used during medical imaging procedures.

[0101] In some non-limiting embodiments, the informatics application 202-B of the gateway device 102 may provide cloud network storage of data related to (e.g., received via, stored via, transmitted via, etc.) the patient procedure tracking service 4024-A, the image archiving and communication service 4024-B, the radiology information service 4024-C, the radiology analysis service 4024-D, the fluid injector management service 4024-E, and / or the data insights service 4024-F. In this manner, the gateway device 102 may provide collection, storage, and access of data related to the informatics application 202-B that reduces the need for resources (e.g., memory resources, network resources, etc.) available on the fluid injection system 104. In some non-limiting embodiments, machine learning techniques may be applied to data related to the patient procedure tracking service 4024-A, image archiving and communication service 4024-B, radiology information service 4024-C, radiology analysis service 4024-D, fluid injector management service 4024-E, and / or data insights service 4024-F that is collected and stored in cloud network storage. For example, machine learning techniques may be applied to data related to patients (e.g., patient demographics), data related to fluid injection systems, data related to medical imaging systems, data related to contrast fluids, data related to catheters used during fluid injection procedures, etc., and the output of the machine learning techniques may include recommendations for fluid injection procedure protocols.

[0102] In some non-limiting embodiments, the informatics application 202-B services may be subscription-based and may require users to sign up for terms and conditions. In some non-limiting embodiments, levels of service may be provided based on subscriptions associated with the patient procedure tracking service 4024-A, image archiving and communication service 4024-B, radiology information service 4024-C, radiology analysis service 4024-D, fluid infuser management service 4024-E, and / or data insights service 4024-F. For example, the gateway device 102 may provide access to one or more of the patient procedure tracking service 4024-A, image archiving and communication service 4024-B, radiology information service 4024-C, radiology analysis service 4024-D, fluid infuser management service 4024-E, and data insights service 4024-F based on the level of service to which the user subscribes.

[0103] In some non-limiting embodiments, the fluid injection system service application 202-C may include a remote service connectivity service 4026-A, an upgrade repository service 4026-B, a license management service 4026-C, and / or a periodic data management service 4026-D. In some non-limiting embodiments, the remote service connectivity service 4026-A may provide functionality related to connectivity for maintenance and / or repair of the fluid injection system 104. For example, the remote service connectivity service 4026-A may provide access to and / or control of diagnostic operations of the fluid injection system 104 by a remote service technician. In some non-limiting embodiments, the upgrade repository service 4026-B may provide functionality related to upgrades to services of the gateway device 102 and / or the fluid injection system 104 (e.g., executable files associated with the upgrades). For example, the upgrade repository service 4026-B may provide for receiving, storing, accessing, etc., records related to upgrades to services of the gateway device 102 and / or the fluid injection system 104. In some non-limiting embodiments, the license management service 4026-C may provide functionality related to licenses for services of the gateway device 102 and / or the fluid injection system 104. For example, the license management service 4026-C may provide receiving, storing, accessing, etc., records related to licenses for services of the gateway device 102 and / or the fluid injection system 104. In some non-limiting embodiments, the periodic data management service 4026-D may provide functionality related to managing time-sensitive data related to the gateway device 102 and / or the fluid injection system 104. For example, the periodic data management service 4026-D may provide reporting, tracking, alerts, messaging, etc., related to time-sensitive data related to the gateway device 102 and / or the fluid injection system 104.In some non-limiting embodiments, time-sensitive data associated with the gateway device 102 and / or fluid injection system 104 may include backups of data related to treatment protocols, data related to test records, data related to configuration files, and the like.

[0104] In some non-limiting embodiments, data management application 202-D may include file system management services 4028-A and / or database management services 4028-B. In some non-limiting embodiments, file system management services 4028-A may provide functionality related to managing a file system of gateway device 102. In some non-limiting embodiments, database management services 4028-B may provide functionality related to managing one or more databases associated with gateway device 102.

[0105] In some non-limiting embodiments, the image connectivity system application 202-E may include an image system interface service 4030-A and / or an image system communication protocol service 4030-B. In some non-limiting embodiments, the image system interface service 4030-A may provide functionality related to communication between the medical imaging system 108 and the fluid injection system 104 (e.g., communication based on controller area network (CAN) technology). For example, the image system interface service 4030-A may provide a user interface for the medical imaging system 108 generated in a standard format for use by the fluid injection system 104 (e.g., an ISI interface, an ISI2 interface, a Connect CT interface, etc.). In some non-limiting embodiments, the image system communication protocol service 4030-B may provide functionality related to communication between the medical imaging system 108 and the fluid injection system 104 in addition to (e.g., complimentary to) or independently of (e.g., separately from, instead of) the image system interface service 4030-A. For example, the imaging system communication protocol service 4030-B may provide communication between the medical imaging system 108 and the fluid injection system 104 based on a communication protocol that is different from the communication protocol used by the imaging system interface service 4030-A.

[0106] In some non-limiting embodiments, the gateway device 102 may provide a user interface (e.g., a web-based user interface) for controlling the fluid injection system 104 and the medical imaging system 108. In this manner, the gateway device 102 may eliminate the need for a separate control unit (e.g., a separate computing device specifically designed for control of the fluid injection system 104 and the medical imaging system 108, such as a separate workstation) for each fluid injection system 104 and medical imaging system 108 to control the fluid injection system 104 and the medical imaging system 108.

[0107] 5, which is a diagram of a non-limiting embodiment of a system 500 that enables communication between a fluid injection system and at least one of a plurality of external systems. In some non-limiting embodiments or aspects, one or more of the functions described herein with respect to system 500 may be performed (e.g., fully, partially, etc.) by gateway device 102. In some non-limiting embodiments, one or more of the functions described herein with respect to system 500 may be performed (e.g., fully, partially, etc.) by another device or group of devices that are separate from and / or include gateway device 102, such as fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112.

[0108] As shown in FIG. 5, a first application 502-A (e.g., one of system management application 202-A, informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, or imaging system connectivity application 202-E) and a second application 502-B (e.g., another one of system management application 202-A, informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, or imaging system connectivity application 202-E) may be stored on gateway device 102. As further shown in FIG. 5, the first application 502-A may correspond to a first external system 506-A (e.g., one of the hospital information systems 106, one of multiple subsystems of the hospital information system 106, such as the patient treatment tracking system 206-A, the fluid injector management system 206-B, the image archive and communication system 206-C, the radiology information system 206-D, the radiology analysis system 206-E, the medical imaging system 108, or the fluid injection system service and control system 110), and the second application 502-B may correspond to a second external system 506-B (e.g., another of the hospital information systems 106, one of multiple subsystems of the hospital information system 106, such as the patient treatment tracking system 206-A, the fluid injector management system 206-B, the image archive and communication system 206-C, the radiology information system 206-D, the radiology analysis system 206-E, the medical imaging system 108, or the fluid injection system service and control system 110).

[0109] In some non-limiting embodiments, the fluid infusion system 104 may interact with the gateway device 102 based on a first application 502-A and a second application 502-B, and the gateway device 102 may interact with a first external system 506-A and / or a second external system 506-B as described herein. In some non-limiting embodiments, the first application 502-A and the second application 502-B may interact. For example, the second application 502-B may connect to the first application 502-A based on an API call from the second application 502-B to the first application 502-A. In some non-limiting embodiments, the second external system 506-B may connect to the second application 502-B, and the second application 502-B may connect to the fluid infusion system 104. For example, the second external system 506-B may provide data to the second application 502-B, and the second application 502-B may receive data from the first application 502-A based on an API call from the second application 502-B to the first application 502-A. The fluid infusion system 104 may receive data from the second application 502-B (e.g., based on an API call from the fluid infusion system 104 to the second application 502-B), including data from the second external system 506-B and data from the first application 502-A (e.g., data aggregated from the data from the second external system 506-B and the data from the first application 502-A), based on the API call from the second application 502-B to the first application 502-A. In this way, compared to a situation where the fluid infusion system 104 obtains separate data from two external systems, the gateway device 102 may reduce the amount of network resources consumed when obtaining data from the external systems and data from applications stored on the gateway device 102 and providing that data to the fluid infusion system 104.

[0110] 6, which is a diagram of a non-limiting embodiment of a system 600 that enables communication between a fluid injection system and at least one of a plurality of external systems. In some non-limiting embodiments or aspects, one or more of the functions described herein with respect to system 600 may be performed (e.g., fully, partially, etc.) by gateway device 102. In some non-limiting embodiments, one or more of the functions described herein with respect to system 600 may be performed (e.g., fully, partially, etc.) by another device or group of devices that are separate from and / or include gateway device 102, such as fluid injection system 104, hospital information system 106, medical imaging system 108, fluid injection system service and control system 110, and / or web server 112.

[0111] As shown in FIG. 6, a first application 502-A (e.g., a first application of informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, or imaging system connection application 202-E), a second application 502-B (e.g., a second application of informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, or imaging system connection application 202-E), and a third application 502-C (e.g., a third application of informatics application 202-B, fluid injection system service application 202-C, data management application 202-D, or imaging system connection application 202-E) may be stored in gateway device 102. 6, the system management application 202-A may provide selection of the first application 502-A, the second application 502-B, or the third application 502-C based on a web-based user interface 608 provided by the system management application 202-A (e.g., based on the web-based user interface 608 displayed on the display unit 308). In some non-limiting embodiments, the web-based user interface 608 may be served by the web server 112 based on an API call from the gateway device 102 to the web server 112. As further shown in FIG. 6, the gateway device 102 provides a communication interface between the selected application and the fluid infusion system 104.

[0112] Referring now to FIG. 7, FIG. 7 is a diagram of gateway device 102. As shown in FIG. 7, gateway device 102 includes a display unit 708, a display unit 710, and a hub device 704. In some non-limiting embodiments, display unit 708 and / or display unit 710 may be the same as or similar to display unit 308. In some non-limiting embodiments, display unit 708 and / or display unit 710 may include a computing device such as a portable computer (e.g., a laptop), a mobile device, and / or a touchscreen device (e.g., a computer with a touchscreen). In some non-limiting embodiments, hub device 704 may include a telecommunications gateway such as a universal gateway. In some non-limiting embodiments, display unit 708 and / or display unit 710 may wirelessly interconnect with hub device 704. In some non-limiting embodiments, hub device 704 may include hardware components that enable it to interconnect with fluid infusion system 104, hospital information system 106, medical imaging system 108, fluid infusion system service and control system 110, and / or web server 112. For example, hub device 704 may include one or more cellular modem modules, one or more Wi-Fi modules, one or more Bluetooth devices, etc. to enable wireless interconnections. Additionally or alternatively, hub device 704 may include one or more Ethernet cards, one or more Ethernet switches, one or more universal serial bus (USB) ports, etc. to enable wired interconnections.

[0113] 8 , which illustrates a non-limiting embodiment of an implementation 800 of a fluid injector system 804, i.e., a multi-fluid delivery system such as the MEDRAD® Centargo CT Injection System, a medical imaging system 806, and a gateway device 802 including a display unit 808 located in a computed tomography (CT) imaging suite 812. In some non-limiting embodiments, the fluid injector system 804 may be the same as or similar to the fluid injection system 104, and the medical imaging system 806 may be the same as or similar to the medical imaging system 108. In some non-limiting embodiments, the gateway device 802 may be the same as or similar to the gateway device 102, and the display unit 808 may be the same as or similar to the display unit 308 and / or the display unit 708. As shown in FIG. 8 , the gateway device 802 may eliminate the need for a branched fluid injection system including a scanning room unit and a control room unit located in a scanning room 814 and a control room 816, respectively, of the CT imaging suite 812. In a non-limiting embodiment, the gateway device 802 may provide a user interface (e.g., a web-based user interface) on the display unit 808 for controlling the fluid injector system 804 and the medical imaging system 806. In this manner, the gateway device 802 may eliminate the need for separate computing devices specifically designed for control of the fluid injector system 804 and the medical imaging system 806.

[0114] Referring now to FIG. 9 , FIG. 9 illustrates a non-limiting embodiment of a fluid injector system 900, i.e., a multi-fluid delivery system such as the MEDRAD® Centargo CT Injection System, having a gateway device 932 and a display unit 938. As shown in FIG. 9 , the fluid injector system 900 may be configured (e.g., adapted) to provide feedback regarding compliance with instructions for use. In some non-limiting embodiments, the fluid injector system 900 includes a powered fluid injector 901 connected to a fluid delivery set intended to be associated with the injector device to deliver fluid under pressure from one or more single-dose or multi-dose containers and a fluid pathway set to a patient. In some non-limiting embodiments, the powered fluid injector 901 includes an injector housing 902 having opposing sides 904, a distal or upper end 906, and a proximal or lower end 908. The injector housing 902 encloses various mechanical drive components, the electrical and power components necessary to drive the mechanical drive components, and control components such as electronic memory and electronic control devices (hereinafter, electronic control devices) used to control the operation of reciprocable drive members, such as the drive members associated with the fluid injector system 900. Such drive members may be reciprocable via electromechanical drive components, such as ball screw shafts driven by motors, voice coil actuators, rack and pinion gear drive devices, linear motors, and the like.

[0115] In some non-limiting embodiments, the fluid infuser system 900 may include at least one bulk fluid connector 918 for connecting to at least one bulk fluid source 920. Alternatively, the fluid source may be a single-dose vial rather than a bulk source. In some examples or aspects, multiple bulk fluid connectors 918 may be provided. In some non-limiting embodiments, the three bulk fluid connectors 918 may be arranged side-by-side or in other configurations. In some non-limiting embodiments, the at least one bulk fluid connector 918 may be a spike configured to removably connect to at least one bulk fluid source 920, such as a vial, bottle, or bag. The at least one bulk fluid connector 918 may have a reusable or non-reusable interface with each new bulk fluid source 920. The at least one bulk fluid connector 918 may be formed on or attached by tubing with a multi-patient disposable set, as described herein. At least one bulk fluid source 920 may be configured to receive a medical fluid, such as saline, imaging contrast solution, or other medical fluid, for supply to the fluid injector system 900. The injector housing 902 may have at least one support member 922 for supporting the at least one bulk fluid source 920 when connected to the fluid injector system 900. In some non-limiting embodiments, the fluid injector system 900 may include a connection port 928.

[0116] In some non-limiting embodiments, gateway device 932 may be the same as or similar to gateway device 102 and / or gateway device 802. In some non-limiting embodiments, display unit 938 may be the same as or similar to display unit 308, display unit 708, and / or display unit 808. As shown in FIG. 9 , gateway device 932 and display unit 938 may be components of fluid injector system 900. For example, gateway device 932 may include a printed circuit board (PCB) that is installed within fluid injector system 900.

[0117] 10 , which illustrates a non-limiting embodiment of an injector head unit 1001 of a fluid injector system, such as a MEDRAD® Stellant Flex CT injection system having a gateway device 1022. As shown in FIG. 10 , the injector head unit 1001 may include a housing 1002 and at least one fluid reservoir 1004, such as a syringe or fluid pump container. In some non-limiting embodiments, the fluid injection system may include a drive component to control the flow of fluid into and out of the fluid reservoirs, such as a piston associated with each of the fluid reservoirs 1004 that drives a plunger 1006 within the barrel of the fluid reservoir 1004. In some non-limiting embodiments, each of the fluid reservoirs 1004 is adapted to releasably connect with the housing 1002 at a port 1008. Each fluid reservoir 1004 of the fluid injection system is configured to be filled with at least one medical fluid F, such as an imaging contrast agent, saline, or any desired medical fluid. Each fluid reservoir 1004 can be filled with a different medical fluid F. In some non-limiting embodiments, the fluid injection system can be a multi-syringe injector, as shown, and the two fluid reservoirs 1004 can be positioned side-by-side or in another spatial relationship and are separately actuated by respective pistons associated with the fluid injection system.

[0118] In some non-limiting embodiments, the fluid injection system may be used during a medical procedure to inject at least one medical fluid F into a patient's blood vessel by driving a plunger 1006 associated with a fluid reservoir 1004 with a drive component. The drive component may move the plunger 1006 toward the distal end 1010 of the fluid reservoir 1004 to expel the fluid F from the fluid reservoir 1004 into and through the fluid pathway set 1012 during priming, purging, and / or fluid delivery steps. In some non-limiting embodiments, the fluid pathway set 1012 may include at least one tube or tubing set configured in fluid communication with each fluid reservoir 1004, and may be positioned in fluid communication with each fluid reservoir 1004 and a flexible administration tubing and associated catheter for delivering the fluid F from each fluid reservoir 1004 to a patient at a vascular access site.

[0119] 10, the gateway device 1022 may be a component of the injector head unit 1001 of the fluid injector system. For example, the gateway device 1022 may include a PCB installed within the injector head unit 1001.

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

[0121] 100 Environment 102 Gateway Device 104 Fluid Injection System 106 Hospital Information System 108 Medical Imaging Systems 110 Fluid injection system service and control system, fluid injector service and control system 112 Web Server 114-1 Communication Network 114-2 Communication Networks 114-3 Communication Networks 114-4 Communication Networks 114-5 Communication Networks 200 devices 202 Bus 202-A System Management Application 202-B Information Science Applications 202-C Fluid Injection System Service Applications 202-D Data Management Applications 202-E Image System Connection Application 204 processors 206 memory 206-A Patient Procedure Tracking System 206-B Fluid Injector Management System 206-C Image Archive and Communications System 206-D Radiology Information System 206-E Radiation Analysis System 208 Memory Components 210 Input Components 212 Output Components 214 Communication Components 300 System 308 Display Unit 500 Systems 502-A First Application 502-B Secondary Application 502-C Third Application 506-A First External System 506-B Second External System 600 System 608 Web-based User Interface 704 Hub Device 708 Display Unit 710 Display Unit 800 Implementation 802 Gateway Device 804 Fluid Injector System 806 Medical Imaging Systems 808 Display Unit 812 Computed Tomography (CT) Image Suite, CT Image Suite 814 Scanning Room 816 Control Room 900 Fluid Injector System 901 Electric fluid injector 902 Injector Housing 904 Opposite side 906 Distal or upper end 908 Proximal or lower end 918 Bulk Fluid Connector 920 Bulk Fluid Source 922 Support member 928 connection port 932 Gateway Device 938 Display Unit 1001 Injector Head Unit 1002 Housing 1004 fluid reservoir 1006 Plunger Port 1008 1010 distal end 1012 Fluid Path Set 1022 Gateway Device 4022-A Network Management Services 4022-B Upgrade Management Services 4022-C Security Management Services 4022-D Container Management Services 4024-A Patient Procedure Tracking Service 4024-B Image Archive and Communications Services 4024-C Radiation Information Services 4024-D Radiation Analysis Services 4024-E Fluid Injector Management Services 4024-F Data Insight Services 4026-A Remote Service Connection Service 4026-B Upgrade Repository Service 4026-C License Management Services 4026-D Periodic Data Management Service 4028-A File System Management Services 4028-B Database Management Services 4030-A Imaging Systems Interface Services 4030-B Imaging System Communication Protocol Service

Claims

1. 1. A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: a gateway device, the gateway device comprising: providing a first communication interface between the hospital information system and the fluid infusion system; providing a second communication interface between the fluid injection system and a fluid injection system service and control system associated with the fluid injection system; providing a third communication interface between a medical imaging system and the fluid injection system; at least one processor programmed or configured to A system comprising:

2. the at least one processor: transmitting informatics-related data received from the hospital information system to the fluid infusion system via a communications network based on an application programming interface (API) call from the fluid infusion system. The system of claim 1 further programmed or configured to:

3. the at least one processor: receiving the informatics-related data from the hospital information system via the communications network in accordance with a communications protocol for communicating the informatics-related data; The system of claim 2 further programmed or configured to:

4. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to a patient's treatment from the hospital information system via the communication network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communication protocol; The system of claim 3, programmed or configured to:

5. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to operation of the fluid injection system from the hospital information system via the communications network based on an API call; The system of claim 3, programmed or configured to:

6. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data relating to radiological images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol; The system of claim 3, programmed or configured to:

7. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to the radiation treatment from the hospital information system via the communication network in accordance with a Health Level Seven (HL7) standard communication protocol; The system of claim 3, programmed or configured to:

8. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to radiation dose during a radiological imaging examination from the hospital information system via the communication network based on an API call; The system of claim 3, programmed or configured to:

9. the at least one processor: receiving data related to service functions of the fluid injection system from the fluid injector service and control system via the communication network based on API calls; The system of claim 3 further programmed or configured to:

10. the at least one processor: receiving data related to operation of the medical imaging system from the medical imaging system via the communications network based on the API call; The system of claim 3 further programmed or configured to:

11. the at least one processor: transmitting data related to the service information received from the fluid injector service and control system to the fluid injection system via a communications network based on an API call from the fluid injection system; The system of claim 1 further programmed or configured to:

12. the at least one processor: transmitting data related to the image received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system; The system of claim 1 further programmed or configured to:

13. the at least one processor: Providing a graphical user interface to a user for receiving user input The system of claim 1 further programmed or configured to:

14. The computer further includes a memory device, the memory device storing a plurality of applications, the plurality of applications including: an informatics application associated with the first communication interface between the hospital information system and the fluid injection system; a remote service connectivity application associated with the second communication interface between the fluid injector service and control system associated with the fluid injection system and the fluid injection system; an image connection system application associated with the third communication interface between the medical imaging system and the fluid injection system; and The system of claim 1 , comprising:

15. Display Unit Further provided with the plurality of applications a fourth application associated with a graphical user interface provided to a user by said display unit for receiving user input; The system of claim 14, comprising:

16. The system of claim 1 , wherein the gateway device comprises a universal gateway.

17. 1. A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: a fluid injection system; a gateway device, wherein the gateway device: providing a first communication interface between a hospital information system and the fluid infusion system; providing a second communication interface between the fluid injection system and a fluid injection system service and control system associated with the fluid injection system; providing a third communication interface between a medical imaging system and the fluid injection system; at least one processor programmed or configured to A system comprising:

18. the at least one processor: transmitting informatics-related data received from the hospital information system to the fluid infusion system via a communications network based on an application programming interface (API) call from the fluid infusion system.

20. The system of claim 17, further programmed or configured to:

19. the at least one processor: receiving the informatics-related data from the hospital information system via the communications network in accordance with a communications protocol for communicating the informatics-related data; 20. The system of claim 18, further programmed or configured to:

20. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to a patient's treatment from the hospital information system via the communication network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communication protocol; 20. The system of claim 19, programmed or configured to:

21. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to operation of the fluid injection system from the hospital information system via the communications network based on an API call; 20. The system of claim 19, programmed or configured to:

22. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data relating to radiological images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol; 20. The system of claim 19, programmed or configured to:

23. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to the radiation treatment from the hospital information system via the communication network in accordance with a Health Level Seven (HL7) standard communication protocol; 20. The system of claim 19, programmed or configured to:

24. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to radiation dose during a radiological imaging examination from the hospital information system via the communication network based on an API call; 20. The system of claim 19, programmed or configured to:

25. the at least one processor: receiving data related to service functions of the fluid injection system from the fluid injector service and control system via the communication network based on API calls; 20. The system of claim 19, further programmed or configured to:

26. the at least one processor: receiving data related to operation of the medical imaging system from the medical imaging system via the communications network based on the API call; 20. The system of claim 19, further programmed or configured to:

27. the at least one processor: transmitting data related to the fluid injection system service and service information received from the control system to the fluid injection system via a communications network based on an API call from the fluid injection system; 20. The system of claim 17, further programmed or configured to:

28. the at least one processor: transmitting data related to the image received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system; 20. The system of claim 17, further programmed or configured to:

29. the at least one processor: Providing a graphical user interface to a user for receiving user input 20. The system of claim 17, further programmed or configured to:

30. The computer further includes a memory device, the memory device storing a plurality of applications, the plurality of applications including: an informatics application associated with the first communication interface between the hospital information system and the fluid injection system; a remote service connectivity application associated with the second communication interface between the fluid injector service and control system associated with the fluid injection system and the fluid injection system; an image connection system application associated with the third communication interface between the medical imaging system and the fluid injection system; and 18. The system of claim 17, comprising:

31. Display Unit Further provided with the plurality of applications a fourth application associated with a graphical user interface provided to a user by said display unit for receiving user input; 31. The system of claim 30, comprising:

32. The system of claim 17 , wherein the gateway device comprises a universal gateway.

33. 1. A system for enabling communication between a fluid injection system and at least one of a plurality of external systems, comprising: a fluid injection system, the fluid injection system comprising: a gateway device, the gateway device comprising: providing a first communication interface between a hospital information system and the fluid infusion system; providing a second communication interface between the fluid injection system and a fluid injection system service and control system associated with the fluid injection system; providing a third communication interface between a medical imaging system and the fluid injection system; at least one processor programmed or configured to Equipped with system.

34. the at least one processor: transmitting informatics-related data received from the hospital information system to the fluid infusion system via a communications network based on an application programming interface (API) call from the fluid infusion system.

34. The system of claim 33, further programmed or configured to:

35. the at least one processor: receiving the informatics-related data from the hospital information system via the communications network in accordance with a communications protocol for communicating the informatics-related data; 35. The system of claim 34, further programmed or configured to:

36. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to a patient's treatment from the hospital information system via the communication network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communication protocol; 36. The system of claim 35, programmed or configured to:

37. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to operation of the fluid injection system from the hospital information system via the communications network based on an API call; 36. The system of claim 35, programmed or configured to:

38. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data relating to radiological images from the hospital information system via the communications network in accordance with the Digital Imaging and Communications in Medicine (DICOM) communications protocol; 36. The system of claim 35, programmed or configured to:

39. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to the radiation treatment from the hospital information system via the communication network in accordance with a Health Level Seven (HL7) standard communication protocol; 36. The system of claim 35, programmed or configured to:

40. Upon receiving the data related to informatics from the hospital information system, the at least one processor: receiving data related to radiation dose during a radiological imaging examination from the hospital information system via the communication network based on an API call; 36. The system of claim 35, programmed or configured to:

41. the at least one processor: receiving data related to service functions of the fluid injection system from the fluid injection system service and control system via the communication network based on API calls; 36. The system of claim 35, further programmed or configured to:

42. the at least one processor: receiving data related to operation of the medical imaging system from the medical imaging system via the communications network based on the API call; 36. The system of claim 35, further programmed or configured to:

43. the at least one processor: transmitting data related to the fluid injection system service and service information received from the control system to the fluid injection system via a communications network based on an API call from the fluid injection system; 34. The system of claim 33, further programmed or configured to:

44. the at least one processor: transmitting data related to the image received from the medical imaging system to the fluid injection system via a communications network based on an API call from the fluid injection system; 34. The system of claim 33, further programmed or configured to:

45. the at least one processor: Providing a graphical user interface to a user for receiving user input 34. The system of claim 33, further programmed or configured to:

46. The computer further includes a memory device, the memory device storing a plurality of applications, the plurality of applications including: an informatics application associated with the first communication interface between the hospital information system and the fluid injection system; a remote service connectivity application associated with the second communication interface between the fluid injection system and the fluid injection system service and control system associated with the fluid injection system; an image connection system application associated with the third communication interface between the medical imaging system and the fluid injection system; and 34. The system of claim 33, comprising:

47. Display Unit Further provided with the plurality of applications a fourth application associated with a graphical user interface provided to a user by said display unit for receiving user input; 47. The system of claim 46, comprising:

48. The system of claim 17 , wherein the gateway device comprises a universal gateway.

Images