Systems to provide a gateway to connect a fluid supply system and external systems

Abstract

A system is provided to enable communication between a fluid injection system and at least one of several external systems. The system includes a gateway device, which includes at least one processor programmed or configured to provide a first communication interface between a hospital information system and a fluid injection system, a second communication interface between a control and service system associated with the fluid injection system and the fluid injection system itself, and a third communication interface between a medical imaging system and the fluid injection system.

Description

Systems to provide a gateway to connect a fluid supply system and external systems BACKGROUND Field This disclosure generally refers to communication systems and / or devices associated with medical devices and, in some non-limiting embodiments, to software systems, procedures, and products that provide a gateway enabling communication between a fluid injection system and one or more external systems. Technical considerations A fluid injection system (e.g., a medical fluid delivery system) may be used by a medical professional, such as a physician, in a diagnostic and / or therapeutic medical procedure. For example, the medical professional may use the fluid injection system to inject one or more medical fluids into a patient. The fluid injection system may be used for the pressurized injection of a medical fluid, such as a radiologic contrast material (e.g., a contrast agent, a radiocontrast agent, contrast media, etc.), and / or a flushing agent, such as saline solution, in medical imaging procedures, such as angiography, computed tomography (CT), ultrasound, magnetic resonance imaging (MRI), and positron emission tomography (PET).In some cases, the fluid injection system is designed to deliver a predetermined amount of a medical fluid at a predetermined flow rate. In some cases, the 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 to 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 a procedure performed on a patient to the information system via a communication network, and the information system may store the information in an appropriate database so that a medical professional can review it.For example, WO 2008 / 011401 A2 discloses a hospital information system control and coordination unit that controls both an injector and an image generator, but does not provide an interface that allows a user to manage a gateway device configuration. Summary Consequently, systems, procedures, and software products that provide a gateway device enabling communication between a fluid injection system and one or more external systems are disclosed. The object of the present invention is a system that allows communication between a fluid injection system and at least one of a plurality of external systems, according to claim 1. These and other features and characteristics of this disclosure, as well as the operating procedures and functions of the related structural elements and the combination of parts and manufacturing economies, will become more apparent upon consideration of the following description and the accompanying claims with reference to the accompanying drawings, all of which form part of this specification, in which similar reference numbers designate corresponding parts in the various figures. It should be expressly understood, however, that the drawings are for illustrative and descriptive purposes only and are not intended to define the limits of this disclosure. As used in the specification and in the claims, the singular forms of "a" and "an" include references to plurals unless the context clearly dictates otherwise. Brief description of the drawings Additional advantages and details of embodiments or non-limiting aspects are explained in greater detail below with reference to the exemplary embodiments illustrated in the accompanying schematic figures, in which: FIG.1 is a diagram of a non-limiting embodiment of an environment in which systems, procedures and / or computer program products described in this document may be implemented in accordance with this disclosure; 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; FIG.3 is a diagram of a non-limiting embodiment of a system for enabling communication between a fluid injection system and at least one of a plurality of external systems; FIG.4 is a diagram of a non-limiting embodiment of a gateway device; FIG.5 is a diagram of a non-limiting embodiment of a system implementation for enabling communication between a fluid injection system and at least one of a plurality of external systems; FIG.6 is a diagram of a non-limiting embodiment of an implementation of a system to allow communication between a fluid injection system and at least one of a plurality of external systems; FIG.7 is a diagram of a non-limiting embodiment of a gateway device; FIG. 8 illustrates an exemplary CT imaging suite illustrating a non-limiting embodiment of a fluid injection system and gateway device; FIG. 9 illustrates a non-limiting embodiment of a fluid injection system including a gateway device; and FIG. 10 illustrates a non-limiting embodiment of another fluid injection system that includes a gateway device. Description For the purposes of the description herein, the terms "end," "top," "bottom," "right," "left," "vertical," "horizontal," "top," "bottom," "side," "longitudinal," and derivatives thereof shall refer to the disclosure as oriented in the accompanying drawings. However, it should be understood that the disclosure may assume various alternative variations and step sequences, except where specifically stated otherwise. It should also be understood that the specific devices and procedures illustrated in the accompanying drawings and described herein are merely exemplary embodiments or aspects of the disclosure. Therefore, specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments disclosed herein should not be considered limiting unless otherwise indicated. No aspect, component, element, structure, act, step, function, instruction, and / or the like used in this report should be construed as critical or essential unless explicitly described as such. Likewise, as used in this report, the terms "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 in this report, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and / or the like) and may be used interchangeably with "one or more" or "at least one." When referring to a single item, the term "one" or similar language is used. Additionally, as used in this report, the terms "has," "have," "having," and the like are intended to be open-ended terms.Furthermore, the expression "based on" means "based at least partially on," unless explicitly stated otherwise. As used herein, the terms "communication" and "communicate" may refer to the reception, transmission, transfer, provision, and / or similar actions of information (e.g., data, signals, messages, instructions, commands, and / or similar actions). That a unit (e.g., a system, a component of a device or system, combinations thereof, and / or similar actions) is in communication with another unit means that the unit is capable of receiving information directly or indirectly from and / or transmitting information to the other unit. This may refer to a direct or indirect connection, which may be wired and / or wireless.Additionally, two units or components can communicate with each other even if the transmitted information is modified, processed, retransmitted, and / or routed between the first and second units. For example, a first unit can communicate with a second unit even if the first unit passively receives information and does not actively send information to the second unit. As another example, a first unit can communicate with a second unit if at least one intermediary unit (for example, a third unit located between the first and second units) processes the information received from the first unit and sends the processed information to the second unit. In some non-limiting embodiments, the information may refer to a network packet (for example, a data packet and / or similar) that includes data.In some non-limiting embodiments, a fluid injection system can be connected to a medical imaging system, which, in turn, can be connected to an information system for a medical treatment center, so that information associated with operations of the fluid injection system and / or the medical imaging system can be used by a medical professional during the treatment of a patient. However, in order to connect the fluid injection system to the medical imaging system and the information system, the fluid injection system may require complex network communication equipment so that it can communicate with the medical imaging system and the information system efficiently, securely, and without error. Furthermore, the fluid injection system may require specially configured network equipment and / or reprogramming to communicate with the medical imaging system and the information system based on the network communication configuration of the medical imaging system and / or the information system. Systems, procedures, and software products that provide solutions to the challenges mentioned above are disclosed. 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 may include a gateway device that includes at least one processor programmed or configured to provide a first communication interface between a hospital information system and a 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.In this way, the system can eliminate the need for complex network communication equipment as part of, or in addition to, the fluid injection system. Furthermore, such a system can reduce the amount of network resources consumed by upgrading and / or configuring the fluid injection system to connect it to the medical imaging system and / or the hospital information system. Referring now to FIG. 1, FIG. 1 is a diagram of a non-limiting embodiment of an environment 100 in which the devices, systems, procedures, and / or software products described herein may be implemented. As shown in FIG. 1, the environment 100 includes a gateway device 102, a fluid injection system 104, and a plurality of external systems, such as the hospital information system 106, the medical imaging system 108, the fluid injection system service and control system 110, and the web server 112.Gateway device 102 can interconnect (e.g., establish a connection to communicate with and / or the like) 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 communication networks 114-1, 114-2, 114-3, 114-4, and 114-5 (individually referred to as communication network 114 or collectively as communication networks 114, unless otherwise specified).In some non-limiting embodiments, the gateway device 102 can be interconnected (e.g., establishing a connection to communicate with and / or similar) 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. In some non-limiting embodiments, the gateway device 102 may include one or more devices capable of communicating with 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 the communication network 114. For example, the gateway device 102 may include a telecommunications gateway (e.g., a network gateway), a universal gateway, and / or any other similar devices. Additionally or alternatively, the 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, and / or the like.In some non-limiting embodiments, gateway device 102 may include one or more (for example, a plurality of) applications (for example, software applications) that perform a set of functionalities on an external application programming interface (API) that enables fluid injection system 104 to send data to an external system associated with the external API and to receive data from the external system associated with the external API. In one example, gateway device 102 may provide the ability to download an application, such as a Bayer S / W application, to gateway device 102 (for example, a mobile device of gateway device 102, providing Bring Your Own Device operability).In some non-limiting embodiments, the application may be supported by an application associated with the fluid injection system 104, which would allow the gateway device 102 (for example, a mobile device of the gateway device 102), which may function as a control room display, to be the sole device controlling the fluid injection system 104. In such an example, the gateway device 102 may provide an authentication function. In some non-limiting embodiments, the gateway device 102 may be able to access a network resource, such as a Uniform Resource Locator (URL), to determine which applications (for example, application services) are available to the gateway device 102. The gateway device 102 and / or the fluid injection system 104 may then download one or more applications through the gateway device 102. In some non-limiting embodiments, the fluid injection system 104 may include one or more devices capable of communicating with the gateway device 102, 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 the communication network 114, and capable of performing fluid injection procedures. For example, the fluid injection system 104 may include one or more fluid injectors capable of communicating via the communication network 114 and capable of performing fluid injection procedures involving a radiologic contrast material (e.g., a contrast agent, a radiocontrast agent, contrast media, etc.), such as iodine-based contrast media and / or gadolinium-based contrast media. 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, deliver, etc.) contrast fluid, including a contrast agent, to a patient, and / or administer an aqueous fluid, such as saline solution, to a patient before, during, and / or after administering the contrast fluid. For example, the Fluid Injection System 104 may inject one or more prescribed doses of contrast fluid directly into a patient's bloodstream through a hypodermic needle and syringe.In some non-limiting embodiments, the fluid injection system 104 may be configured to continuously administer aqueous fluid to a patient via a peripheral intravenous (PIV) line and catheter, and one or more prescribed doses of contrast fluid may be introduced into the PIV and administered via the catheter to the patient. In some non-limiting embodiments, the fluid injection system 104 is configured to inject a dose of contrast fluid followed by the administration of a particular volume of aqueous fluid. In some non-limiting embodiments, the fluid injection system 104 may include one or more exemplary injection systems or injectors disclosed in: U.S. Patent Application Serial No. 09 / 715,330, filed November 17, 2000, granted as U.S. Patent No. 6,643,537; U.S. Patent Application No.of serial number 09 / 982, 518, filed on October 18, 2001, granted as U.S. Patent No. 7,094,216; U.S. Patent Application with serial number 10 / 825,866, filed on April 16, 2004, granted as U.S. Patent No. 7,556,619; U.S. Patent Application Serial No. 12 / 437,011, filed May 7, 2009, granted U.S. Patent No. 8,337,456; U.S. Patent Application Serial No. 12 / 476,513, filed June 2, 2009, granted U.S. Patent No. 8,147,464; and U.S. Patent Application Serial No. 11 / 004,670, filed December 3, 2004, granted as U.S. 8,540,698. In some non-limiting embodiments, the 104 fluid injection system may include the MEDRAD® Stellant CT injection system, the MEDRAD® Stellant Flex CT injection system, the MEDRAD® MRXperion MR injection system, the MEDRAD® Mark 7 Arterion injection system, the MEDRAD® Intego PET infusion system, or the MEDRAD® Centargo CT injection system, all of which are supplied by Bayer Healthcare LLC. In some non-limiting embodiments, the hospital information system 106 may include one or more devices capable of communicating with the gateway device 102, the fluid injection system 104, the medical imaging system 108, and the fluid injection system service and control system 110 via the communication network 114. For example, the 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, and / or the like.In some non-limiting embodiments, the 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., an Image 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). In some non-limiting embodiments, the medical imaging system 108 may include one or more devices capable of communicating with the gateway device 102, the fluid injection system 104, the hospital information system 106, the fluid injection system service and control system 110, and / or the web server 112 via the communication network 114. For example, the medical imaging system 108 may include one or more scanners, such as a CT scanner and / or an MRI scanner, capable of communicating via the communication network 114 and capable of performing imaging procedures involving the use of a radiologic contrast material. In some non-limiting embodiments, the service and control system for the fluid injection system 110 may include one or more devices capable of communicating with the gateway device 102, the fluid injection system 104, the hospital information system 106, the medical imaging system 108, and / or the web server 112 via the communication network 114. For example, the service and control system for the fluid injection 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, and / or the like. In some non-limiting embodiments, the service and control system for the fluid injection system 110 may provide functionality for a user (for example, a service representative) to interact with the fluid injection system 104 and / or the gateway device 102 for maintenance purposes.For example, the fluid injection system 110 service and control system may provide functionality for the user to perform updates, restore operations, log operations, data backup operations, and / or similar operations. In some non-limiting embodiments, the fluid injection system 110 service and control system may be a subsystem of the hospital information system 106, and the fluid injection system 110 service and control system may communicate with the gateway device 102 via the communication network 114-4. In some non-limiting embodiments, the service and control system for fluid injection system 110 may include a back-end system associated with gateway device 102 and / or fluid injection system 104. In some non-limiting embodiments, the service and control system for fluid injection system 110 may include a cloud computing system that stores data in an associated database. In some non-limiting embodiments, the service and control system for fluid injection system 110 may be able to interface with fluid injection system 104 to provide functionality such as remote equipment servicing for fluid injection system 104 (for example, the VirtualCARE® remote support service for injection systems and devices provided by Bayer HealthCare LLC).In some non-limiting embodiments, the service and control system of the fluid injection system 110 may be operated by or on behalf of an original equipment manufacturer (OEM) of the fluid injection system 104 (e.g., an OEM of one or more components or devices of the fluid injection system 104), a supplier of the fluid injection system 104, an imaging site or hospital in which the fluid injection system 104 is operated, a service technician assigned to the fluid injection system 104, and / or the like. In some non-limiting embodiments, the web server 112 may include one or more devices capable of communicating with the gateway device 102, the fluid injection system 104, the hospital information system 106, the medical imaging system 108, and / or the fluid injection system's service and control system 110 via the communication network 114. For example, the web server 112 may include one or more computing devices, such as one or more servers and / or the like. In some non-limiting embodiments, the web server 112 may provide a web-based user interface to the gateway device 102 that enables control of and / or access to the functionality of the fluid injection system 104. In some non-limiting embodiments, the web server 112 may receive requests via a network protocol (e.g., HTTP, HTTPS, etc.).) for a network resource and transmit the content of the network resource and / or a message relating to the network resource (for example, an error message). In some non-limiting embodiments, the 114 communication network (for example, one or more of the 114-1, 114-2, 114-3, 114-4, and 114-5 communication networks) may include one or more wired and / or wireless networks. For example, the 114 communication network 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, and / or similar), 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, a fiber-optic-based network, an Ethernet network, a universal serial bus (USB) network, a cloud computing network, and / or similar, and / or a combination of some or all of these or other types of networks. The number and arrangement of systems and / or devices shown in FIG. 1 are provided as an example. There may be additional systems and / or devices, fewer systems and / or devices, different systems and / or devices, or systems and / or devices arranged differently than those shown in FIG. 1. Furthermore, two or more systems and / or devices shown in FIG. 1 may be implemented within a single system or device, or a single system or device shown in FIG. 1 may be implemented as multiple distributed systems or devices. Additionally or alternatively, a set of systems or a set of devices (e.g., one or more systems, one or more devices) in environment 100 may perform one or more functions described as being performed by another set of systems or another set of devices in environment 100. Referring now to FIG. 2, FIG. 2 is a diagram of exemplary components of device 200. Device 200 may correspond to gateway device 102, fluid injection system 104, hospital information system 106, medical image generation 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 image generation 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 bus 202, processor 204, memory 206, storage component 208, input component 210, output component 212, and communication component 214. The 202 bus may include a component that enables communication between the components of device 200. In some embodiments or non-limiting aspects, the 204 processor may be implemented in hardware, software, or a combination of hardware and software. For example, the 204 processor may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), and / or the like), a microprocessor, a digital signal processor (DSP), and / or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and / or the like) that can be programmed to perform a function.Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory, and / or similar) that store information and / or instructions for use by the processor 204. Storage component 208 can store information and / or software related to the operation and use of device 200. For example, storage component 208 can include a hard disk (for example, a magnetic disk, an optical disk, a magneto-optical disk, a solid-state disk, and / or the like), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or other computer-readable media, together with a corresponding drive. Input component 210 may include a component that enables device 200 to receive information, for example, through user input (e.g., a touchscreen, keyboard, numeric keypad, mouse, button, switch, microphone, camera, and / or the like). Alternatively, input component 210 may include a sensor for detecting information (e.g., a global positioning system (GPS) component, accelerometer, gyroscope, actuator, and / or the like). Output component 212 may include a component that provides output information from device 200 (e.g., a display, speaker, one or more light-emitting diodes (LEDs), and / or the like). Communication component 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, and / or the like) that enables device 200 to communicate with other devices, such as through a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication component 214 may enable device 200 to receive information from another device and / or send information to another device. For example, communication 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 (BSU) interface, a Wi-Fi® interface, a cellular network interface, and / or the like. Device 200 can perform one or more of the procedures described herein. Device 200 can perform these procedures based on processor 204 executing software instructions stored on a computer-readable medium, such as memory 206 and / or storage component 208. A computer-readable medium (for example, a non-transient computer-readable medium) is defined herein as a non-transient memory device. A non-transient memory device includes memory space located within a single physical storage device or memory space extended across multiple physical storage devices. Software instructions can be read into memory 206 and / or storage component 208 from another computer-readable medium or from another device via communication component 214.When executed, the software instructions stored in memory 206 and / or storage component 208 can cause the processor 204 to perform one or more of the procedures described herein. Additionally or alternatively, hardwired circuitry can be used instead of or in combination with software instructions to perform one or more of the procedures described herein. Therefore, the implementations or aspects described herein are not limited to any specific combination of hardware and software circuitry. Memory 206 and / or storage component 208 may include data storage or one or more data structures (for example, a database and / or the like). Device 200 may be able to retrieve information from, store information in, or search for information stored in data storage or one or more data structures in memory 206 and / or storage component 208. The number and arrangement of components shown in FIG. 2 are provided as an example. In some embodiments or non-limiting aspects, the device 200 may include additional components, fewer components, different components, or components arranged differently than those shown in FIG. 2. Additionally or alternatively, a set of components (for example, one or more components) of the device 200 may perform one or more functions described herein as performed by another set of components of the device 200. Referring now to Figures 3 and 4, Figure 3 is a diagram of a non-limiting embodiment of a system 300 for enabling 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 (for example, completely, partially, and / or similarly) by the gateway device 102.In some non-limiting embodiments, one or more of the functions described with respect to system 300 may be performed (for example, completely, partially, and / or similarly) by another device or a group of devices separate from and / or including the gateway device 102, such as 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 display unit 308. FIG. 4 is a diagram of a non-limiting embodiment of applications of the gateway device 102. As shown in FIGS. 3 and 4, the gateway device 102 can include a plurality of applications, such as the system management application 202-A, the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, and the image generation system connectivity application 202-E. In some non-limiting embodiments, the plurality of applications can be stored in a memory device of the gateway device 102. In some non-limiting embodiments, each of the plurality of applications can be associated with an API associated with a respective application (e.g., a first API associated with a first application, a second API associated with a second application, a third API associated with a third application, etc.).) enabling the fluid injection system 104 to establish an interface (e.g., communicate, establish a communication interface, etc.) with the gateway device 102 and / or enabling the gateway device 102 to establish an interface 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 radiological information system 206-D, and / or the radiological analysis system 206-E). In some non-limiting embodiments, each application within the plurality of applications may include a common software platform application that provides common features and functionalities shared by all fluid injection system modalities. Thus, the gateway device 102 may be able to connect to a fluid injection system regardless of the specific fluid injection system manufacturer. In some non-limiting embodiments, the system management application 202-A may provide operational control of aspects of the gateway device 102. For example, the system management application 202-A may provide operational control management of the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, and / or the imaging system connectivity application 202-E. In some non-limiting embodiments, the system management application 202-A may provide a user interface (for example, a web-based user interface) that allows a user to control the fluid injection system 104. For example, a user may initiate medical imaging, fluid injection, and / or other additional procedures to be performed by the fluid injection system 104 through the user interface.Additionally or alternatively, the user interface may allow the user to control aspects of the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, and / or the image generation system connectivity application 202-E. As further shown in FIG. 3, the 300 system may include a display unit 308. In some non-limiting embodiments, the display unit 308 may be capable of displaying the user interface (for example, the web-based user interface) provided by the 202-A system management application. In some non-limiting embodiments, the display unit 308 may include a computing device, such as a smart display, a handheld computer, a tablet, a laptop, or similar. In some non-limiting embodiments, the display unit 308 may include a touchscreen for receiving input from a user. In some non-limiting embodiments, the software application 202-B may be associated with a first communication interface of the gateway device 102 between the hospital information system 106 and the fluid injection system 104. For example, the gateway device 102 may provide the first communication interface between the hospital information system 106 and the fluid injection system 104 based on the software application 202-B. In some non-limiting embodiments, a communication interface may include a set of communication configurations (e.g., protocols, standards, etc.) that enables one device (e.g., a device in a system) to telecommunicate with another device.In some non-limiting embodiments, the software application 202-B may provide functionality for the fluid injection system 104 to interact with the hospital information system 106 (for example, with any of the plurality of subsystems of the hospital information system 106). Additionally or alternatively, the software application 202-B may provide data storage for the fluid injection system 104. In some non-limiting embodiments, the fluid injection system service application 202-C may be associated with a second communication interface of gateway device 102 between the fluid injector service and control system 110 and the fluid injection system 104. For example, gateway device 102 may provide the second communication interface between the fluid injection service and control system 110 associated with fluid injection system 104 and the fluid injection system 104. In some non-limiting embodiments, the fluid injection system service application 202-C may provide functionality for a user (for example, a service representative) to interact with fluid injection system 104 and / or gateway device 102 to perform maintenance operations. In some non-limiting embodiments, the data management application 202-D may be associated with a third communication interface of the gateway device 102 between the hospital information system 106 and the fluid injection system 104. For example, the gateway device 102 may provide the third communication interface between the hospital information system 106 and the fluid injection 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 the hospital information system 106 and the fluid injection system 104. In some non-limiting embodiments, the data management application 202-D may provide functionalities associated with file system and database management for the gateway device 102.Additionally or alternatively, the 202-D data management application can provide operational control with respect to data storage for the 104 fluid injection system. In some non-limiting embodiments, the connectivity application of the imaging system 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 the 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 the 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 connectivity application of the imaging system 202-E can provide functionality for the fluid injection system 104 to interact with the medical imaging system 108. In some non-limiting embodiments, the connectivity application of the imaging system 202-E can abstract an interface of the medical imaging system 108 (for example, an ISI interface, an ISI2 interface, or a Connect CT interface) into a standard format for use by the fluid injection system 104. In some non-limiting embodiments, gateway device 102 can provide the first communication interface between hospital information system 106 and fluid injection system 104, such that computer application 202-B provides the ability for fluid injection system 104 to receive data based on an API call from fluid injection system 104 to gateway device 102. In some non-limiting embodiments, gateway device 102 can transmit data associated with information received from hospital information system 106 to fluid injection system 104 via a communication network 114.For example, gateway device 102 can transmit data associated with information received from the hospital information system 106 to the fluid injection system 104 via the communication network 114 based on an API call to the computer application 202-B from the fluid injection system. The computer-related data may include data associated with a patient's identification, data associated with a patient examination procedure (e.g., a fluid injection procedure and an imaging procedure performed on a patient), such as data associated with a contrast fluid administered during a fluid injection procedure, the gauge of a catheter used during a fluid injection procedure, and a fluid injection protocol for a fluid injection procedure.In some non-limiting embodiments, the gateway device 102 can store data associated with a patient examination procedure and / or data associated with a fluid injection system configuration 104 with the computer application 202-B. As further shown in FIG. 3, the hospital information system 106 may include a plurality of subsystems. These subsystems may include 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 the radiology analysis system 206-E. In some non-limiting embodiments, gateway device 102 can receive computer-related data from hospital information system 106 via communication network 114, in accordance with a communication protocol for transmitting computer-related data. For example, gateway device 102 can receive data related to a patient procedure from hospital information system 106 (e.g., from patient procedure tracking system 206-A) via communication network 114 (e.g., communication network 114-2) in accordance with a DICOM (Image Generation and Communications in Medicine) protocol, and data related to a fluid injection system operation from hospital information system 106 (e.g.,from the fluid injector management system 206-B) via the communication network 114 based on an API call (e.g., an API call from gateway device 102 to fluid injector management system 206-B), data associated with a radiological image from the hospital information system 106 (e.g., from the image archiving and communication system 206-C) via the communication network 114 in accordance with a DICOM communication protocol, data associated with a patient scan procedure from the hospital information system 106 (e.g., from the radiological information system 206-D) via the communication network 114 in accordance with a Health Level Seven (HL7) standard communication protocol, and / or data associated with radiation dosage during a medical imaging procedure from the hospital information system 106 (e.g.,from the radiological analysis system 206-E) through the communication network 114 based on an API call (for example, an API call from gateway device 102 to the radiological analysis system 206-E). In some non-limiting embodiments, gateway device 102 can provide the second communication interface between the fluid injection system 110 service and control system and the fluid injection system 104, such that the fluid injection system 202-C service application provides the ability for the fluid injection system 104 to receive data based on an API call from the fluid injection system 104 to gateway device 102. In some non-limiting embodiments, gateway device 102 can transmit data associated with service information received from the fluid injection system 110 service and control system to the fluid injection system 104 via the communication network 114.For example, gateway device 102 can transmit data associated with service information received from the fluid injection system service and control system 110 to fluid injection system 104 via communication network 114 based on an API call to the fluid injection system service application 202-C from fluid injection system 104. In some non-limiting embodiments, gateway device 102 can receive data associated with a service function of fluid injection system 104 from the 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 the fluid injection system service and control system 110). In some non-limiting embodiments, the gateway device 102 can provide the third communication interface between the medical imaging system 108 and the fluid injection system 104, such that the connectivity application of the imaging system 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 can transmit data associated with an image received from the medical imaging system 108 to the fluid injection system 104 via the communication network 114.For example, gateway device 102 can transmit image-related data received from medical imaging system 108 to fluid injection system 104 via communication network 114, based on an API call to the connectivity application of imaging system 202-E from fluid injection system 104. In some non-limiting embodiments, gateway device 102 can transmit data associated with a fluid injection procedure (e.g., data associated with a time amount for injecting radiologic contrast material into a patient) received from fluid injection system 104 to medical imaging system 108 via communication network 114.For example, gateway device 102 can transmit data associated with the fluid injection procedure received from fluid injection system 104 to medical imaging system 108 via communication network 114 based on an API call (e.g., an API call for an imaging system (ISI) interface, an API call for an ISI2 interface, an API call for a Connect CT interface, etc.) to the imaging system connectivity application 202-E from medical imaging system 108. In some non-limiting embodiments, medical imaging system 108 can perform a medical imaging procedure on a patient based on the data associated with the fluid injection procedure.In some non-limiting embodiments, gateway device 102 can receive data associated with the operation of medical imaging system 108 from medical imaging system 108 via communication network 114 (e.g., communication network 114-3) based on an API call (e.g., an API call from gateway device 102 to medical imaging system 108). In some non-limiting embodiments, gateway device 102 may provide a fourth interface to a user for receiving user input, such that system management application 202-A may provide the capability for gateway device 102 to receive user input. In some non-limiting embodiments, the fourth interface is a graphical user interface. In some non-limiting embodiments, gateway device 102 may provide the fourth interface to the user (for example, an administrator) for configuring communication networks 114, the plurality of applications stored on gateway device 102, and / or the operating system of gateway device 102.In some non-limiting embodiments, gateway device 102 may provide a fourth interface to allow the user to manage a configuration (for example, providing control functions, adjusting communication settings such as device addresses, communication protocols, etc.) of an API associated with an application stored on gateway device 102. In some non-limiting embodiments, system management application 202-A provides an API that allows fluid injection system 104 to interact with high-level functions of gateway device 102. For example, gateway device 102 may provide access to high-level functionality of gateway device 102 based on a call to the API of system management application 202-A from fluid injection system 104.In some non-limiting embodiments, the 202-A system management application may provide a GUI for a user (for example, an administrator) to configure one or more of the 114 communication networks, manage gateway device 102 users, control updates for the gateway device 102 OS and applications, and / or monitor gateway device 102 applications. As further shown in FIG. 4, each application within the plurality of applications on gateway device 102 can provide services (e.g., additional software or hardware functionality, such as microservices, features, etc.) associated with each application. In some non-limiting embodiments, the system management application 202-A may include the network management service 4022-A, the update management service 4022-B, the security management service 4022-C, and / or the container management service 4022-D. In some non-limiting embodiments, the network management service 4022-A may provide functionalities associated with controlling communications across the communication network 114. For example, the network management service 4022-A may provide control over network addresses, communication protocols, and / or the like.In some non-limiting embodiments, the update management service 4022-B may provide functionality associated with controlling updates to be performed on applications and / or services of gateway device 102. For example, the update management service 4022-B may provide control over updates to be performed on services of computer application 202-B. In some non-limiting embodiments, the security management service 4022-C may provide functionality associated with controlling access to gateway device 102. For example, the security management service 4022-C may provide control over users who are able to access gateway device 102, authentication procedures for access to gateway device 102, and / or similar functions.In some non-limiting embodiments, the 4022-D container management service may provide functionalities associated with the control of services, which may be structured as containers, provided by the 202-B software application. In some non-limiting embodiments, the software application 202-B may include the patient procedure tracking service 4024-A, the 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 knowledge service 4024-F. In some non-limiting embodiments, the patient procedure tracking service 4024-A may provide functionalities associated with tracking the patient procedures to be performed by the fluid injection system 104 (for example, functionalities associated with patient demographic information for fluid injection procedures and / or medical image generation procedures).For example, the Patient Procedure Tracking Service 4024-A may provide reports, alerts, messaging, and / or similar functionality 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 (e.g., images provided by medical imaging techniques, scans, scanned images, etc.) received during a fluid injection procedure or a medical imaging procedure. For example, the Image Archiving and Communication Service 4024-B may provide reception, storage, access, transmission, and / or similar functionality with respect to images. In some non-limiting embodiments, the Radiology Information Service 4024-C may provide functionality associated with records of medical imaging procedures.In some non-limiting implementations, the Radiology Information Service 4024-C may provide patient scheduling, resource management, scan tracking, reporting, results distribution, and / or procedure billing with respect to medical imaging procedures. In some non-limiting implementations, the Radiology Analysis Service 4024-D may provide functionalities associated with metrics for medical imaging procedures (e.g., a radiological medical imaging procedure or a radiological medical imaging study).For example, the Radiology Analysis Service 4024-D may provide reporting, tracking, alerts, messaging, and / or similar services regarding information associated with a medical imaging procedure, such as data related to radiation and / or contrast fluid dosage, information regarding procedure protocol management, and / or information regarding benchmarking. In some non-limiting embodiments, the Fluid Injector Management Service 4024-E may provide functionalities associated with the control and / or management of injection protocols for fluid injection systems. For example, the Fluid Injector Management Service 4024-E may provide reception, storage, transmission, and / or otherwise manage fluid injection systems and / or fluid injection protocols used by fluid injection systems.In some non-limiting embodiments, the 4024-F data knowledge service may provide functionality associated with knowledge derived from data related to fluid injection and / or medical imaging procedures. For example, the 4024-F data knowledge service may provide reports, tracking, alerts, messaging, and / or similar services regarding equipment (e.g., medical supplies used during procedures, including contrast fluid, intravenous catheters, etc.) and / or services used during medical imaging procedures. In some non-limiting embodiments, the gateway device 102's software application 202-B can provide cloud-based network storage of data associated with (e.g., received through, stored through, transmitted through, 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 knowledge service 4024-F. In this way, the gateway device 102 can provide the collection, storage, and access of data associated with the software application 202-B, reducing the need for resources (e.g., memory resources, network resources, etc.) to be available on the fluid injection system 104.In some non-limiting embodiments, machine learning techniques can be applied to data associated with 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 analysis service 4024-F, which are collected and stored in a cloud network storage.For example, machine learning techniques can be applied to data associated with patients (e.g., patient demographics), data associated with a fluid injection system, data associated with a medical imaging system, data associated with a contrast fluid, data associated with a catheter used during a fluid injection procedure, and / or the like, and the result of the machine learning techniques may include recommendations for fluid injection procedure protocols. In some non-limiting embodiments, the services of the 202-B software application may be subscription-based and require users to register for the terms and conditions. In some non-limiting embodiments, service levels may be provided on a subscription basis associated with the 4024-A Patient Procedure Tracking Service, the 4024-B Image Archiving and Communication Service, the 4024-C Radiology Information Service, the 4024-D Radiology Analysis Service, the 4024-E Fluid Injector Management Service, and / or the 4024-F Data Knowledge Service.For example, the gateway device 102 can provide access to one or more of 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 the Data Knowledge Service 4024-F based on a service level to which a user subscribes. In some non-limiting embodiments, the Fluid Injection System 202-C service application may include the Remote Service Connectivity Service 4026-A, the Update Repository Service 4026-B, the License Management Service 4026-C, and / or the Periodic Data Management Service 4026-D. In some non-limiting embodiments, the Remote Service Connectivity Service 4026-A may provide functionality associated with 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 Update Repository Service 4026-B may provide functionality associated with updates (for example, executable files associated with updates) for the Gateway Device 102 and / or Fluid Injection System 104 services. For example, the Update Repository Service 4026-B may provide the receipt, storage, access, and / or similar functions with respect to records relating to updates for the Gateway Device 102 and / or Fluid Injection System 104 services. In some non-limiting embodiments, the License Management Service 4026-C may provide functionality associated with licensing for the Gateway Device 102 and / or Fluid Injection System 104 services.For example, the license management service 4026-C may provide the receipt, storage, access, and / or similar functions with respect to records relating to licenses for the gateway device 102 and fluid injection system 104 services. In some non-limiting embodiments, the periodic data management service 4026-D may provide functionalities associated with the management of time-sensitive data associated with the gateway device 102 and / or fluid injection system 104. For example, the periodic data management service 4026-D may provide reporting, tracking, alerting, messaging, and / or similar functions with respect to time-sensitive data associated with the gateway device 102 and / or fluid injection system 104.In some non-limiting embodiments, time-sensitive data associated with gateway device 102 and / or fluid injection system 104 may include backups of data associated with procedure protocols, data associated with scan logs, data associated with configuration files and / or the like. In some non-limiting embodiments, the 202-D data management application may include the 4028-A file system management service and / or the 4028-B database management service. In some non-limiting embodiments, the 4028-A file system management service may provide functionality associated with managing a file system on the 102 gateway device. In some non-limiting embodiments, the 4028-B database management service may provide functionality associated with managing one or more databases associated with the 102 gateway device. In some non-limiting embodiments, the application of the 202-E imaging connectivity system may include the 4030-A imaging system interface service and / or the 4030-B imaging system communication protocol service. In some non-limiting embodiments, the 4030-A imaging system interface service may provide functionality associated with communication (e.g., communication based on Controller Area Network (CAN) technology) between the 108 medical imaging system and the 104 fluid injection system. For example, the 4030-A imaging system interface service may provide that a user interface of the 108 medical imaging system (e.g., an ISI interface, an ISI2 interface, a Connect CT interface, etc.) is generated in a standard format for use by the 104 fluid injection system.In some non-limiting embodiments, the communication protocol service of the imaging system 4030-B may provide functionalities associated with communication between the medical imaging system 108 and the fluid injection system 104, in addition to (for example, complementarily to) or independently of (for example, separately from, instead of) the interface service of the imaging system 4030-A. For example, the communication protocol service of the imaging system 4030-B may provide communication between the medical imaging system 108 and the fluid injection system 104 based on a different communication protocol than the one used by the interface service of the imaging system 4030-A. In some non-limiting embodiments, the gateway device 102 can 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 way, the gateway device 102 can eliminate the need for separate control units (e.g., separate computing devices that are specifically designed for controlling the fluid injection system 104 and the medical imaging system 108, such as separate workstations) for each of the fluid injection system 104 and the medical imaging system 108. Referring now to FIG. 5, FIG. 5 is a diagram of a non-limiting embodiment of a system 500 for enabling 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 (for example, completely, partially, and / or similarly) by the gateway device 102.In some non-limiting embodiments, one or more of the functions described herein with respect to system 500 may be performed (for example, completely, partially and / or similarly) by another device or group of devices separate from and / or including the gateway device 102, such as the fluid injection system 104, the hospital information system 106, the medical image generation system 108, the fluid injection system service and control system 110, and / or the web server 112. As shown in FIG. 5, the first application 502-A (for example, one of the system management application 202-A, the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, or the imaging system connectivity application 202-E) and the second application 502-B (for example, another of the system management application 202-A, the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, or the imaging system connectivity application 202-E) can be stored on the gateway device 102. As further shown in FIG. 5, the first application 502-A may correspond to the first external system 506-A (for example, one of the hospital information systems 106, one of a plurality of 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, the radiology analysis system 206-E, the medical image generation system 108, or the fluid injection system service and control system 110) and the second application 502-B may correspond to the second external system 506-B (for example, another of the hospital information system 106, one of a plurality of 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, the radiology analysis system 206-E, the system of medical image generation 108,or the service and control system of the fluid injection system 110) ., In some non-limiting embodiments, the fluid injection system 104 may interact with the gateway device 102 based on the first application 502-A and the second application 502-B, and the gateway device 102 may interact with the first external system 506-A and / or the 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 interact with 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 interact with the second application 502-B, and the second application 502-B may interact with the fluid injection system 104.For example, the second external system 506-B can provide data to the second application 502-B, and the second application 502-B can receive data from the first application 502-A based on the API call from the second application 502-B to the first application 502-A. The fluid injection system 104 can receive data from the second application 502-B (for example, based on an API call from the fluid injection system 104 to the second application 502-B) that includes data from the second external system 506-B and data from the first application 502-A (for example, data that is 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, gateway device 102 can reduce the amount of network resources consumed when obtaining data from an external system and data from an application stored on gateway device 102 and providing the data to fluid injection system 104 compared to a situation where fluid injection system 104 would obtain separate data from two external systems. Referring now to FIG. 6, FIG. 6 is a diagram of a non-limiting embodiment of a system 600 for enabling 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 (for example, completely, partially, and / or similarly) by the gateway device 102.In some non-limiting embodiments, one or more of the functions described herein with respect to system 600 may be performed (for example, completely, partially and / or similarly) by another device or group of devices separate from and / or including the gateway device 102, such as the fluid injection system 104, the hospital information system 106, the medical image generation system 108, the fluid injection system service and control system 110, and / or the web server 112. As shown in FIG. 6, the first application 502-A (for example, a first application of the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, or the imaging system connectivity application 202-E), the second application 502-B (for example, a second application of the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, or the imaging system connectivity application 202-E), and the third application 502-C (for example, a third application of the computer application 202-B, the fluid injection system service application 202-C, the data management application 202-D, or the imaging system connectivity application 202-E) can be stored on the gateway device 102. As also shown in FIG.6. The system manager application 202-A can provide a selection of the first application 502-A, the second application 502-B, or the third application 502-C based on the web-based user interface 608 (for example, based on the web-based user interface 608 displayed on the display unit 308) that is provided by the system manager application 202-A. In some non-limiting embodiments, the web-based user interface 608 can be served by the web server 112 based on an API call to the web server 112 from the gateway device 102. As further shown in FIG. 6, the gateway device 102 will provide a communication interface between the selected application and the fluid injection system 104. Referring now to FIG. 7, FIG. 7 is a diagram of gateway device 102. As shown in FIG. 7, gateway device 102 includes display unit 708, display unit 710, and concentrator 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 laptop computer, a mobile device, and / or a touchscreen device. In some non-limiting embodiments, concentrator device 704 may include a telecommunications gateway, such as a universal gateway.In some non-limiting embodiments, the display unit 708 and / or the display unit 710 can be wirelessly connected to the concentrator device 704. In some non-limiting embodiments, the concentrator device 704 may include hardware components that enable the concentrator device 704 to interconnect with 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. For example, the concentrator device 704 may include one or more cellular modem modules, one or more Wi-Fi modules, one or more Bluetooth devices, and / or the like, to enable wireless interconnections.Additionally or alternatively, the 704 concentrator device may include one or more Ethernet cards, one or more Ethernet switches, one or more universal serial bus (USB) ports, and / or similar, to allow wired interconnections. Referring now to FIG. 8, FIG. 8 illustrates a non-limiting embodiment of an implementation 800 of the fluid injector system 804, specifically 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 the computed tomography (CT) imaging room 812. In some non-limiting embodiments, the fluid injector 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 gateway device 102, and the display unit 808 may be the same as or similar to display unit 308 and / or display unit 708. As shown in FIG. 8, the gateway device 802 may eliminate the need for a bifurcated fluid injection system that includes a scan room unit and a control room unit located in scan room 814 and control room 816, respectively, of the CT imaging room 812. In some non-limiting embodiments, 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 injection system 804 and the medical imaging system 806.In this way, the gateway device 802 can eliminate the need for separate computing devices that are specifically designed for control of the fluid injector system 804 and the medical imaging system 806. Referring now to FIG. 9, FIG. 9 illustrates a non-limiting embodiment of the fluid injector system 900, specifically a multi-fluid delivery system such as the MEDRAD® Centargo CT injection system, with a gateway device 932 and a display unit 938. As shown in FIG. 9, the fluid injector system 900 can be configured to (for example, adapted to) provide feedback on compliance with the instructions for use. In some non-limiting embodiments, the fluid injector system 900 includes a motorized fluid injector 901 connected to a fluid delivery assembly intended to be associated with an injector device to deliver fluids from one or more single- or multi-dose containers and pressurized fluid pathway assemblies into a patient.In some non-limiting embodiments, the motorized fluid injector 901 includes the injector housing 902 with opposing side sides 904, distal or upper end 906, and proximal or lower end 908. The injector housing 902 encloses the various mechanical drive components, electrical and power components necessary to drive the mechanical drive components, and control components, such as electronic memory and electronic control devices (hereafter referred to in this document as electronic control device(s)), used to control the operation of reciprocally movable drive members, such as drive members associated with the fluid injector system 900.Such drive members may be reciprocally operable by electromechanical drive components, such as a motor-driven ball screw shaft, a moving coil drive, a rack and pinion gear drive, a linear motor, and the like. In some non-limiting embodiments, the fluid injector system 900 may include at least one bulk fluid connector 918 for connection to at least one bulk fluid source 920. Alternatively, the fluid source could be a single-dose vial instead of a bulk source. In some examples or aspects, a plurality of bulk fluid connectors 918 may be provided. In some non-limiting embodiments, three bulk fluid connectors 918 may be provided in a side-by-side or other arrangement. In some non-limiting embodiments, at least one bulk fluid connector 918 may be a punch configured to removably connect to the 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 via tubing to the disposable multi-patient assembly, as described herein. The at least one bulk fluid source 920 may be configured to receive a medical fluid, such as saline solution, an imaging contrast solution, or another medical fluid, for delivery to the fluid injector system 900. The injector housing 902 may have at least one support member 922 to support the at least one bulk fluid source 920 once it is connected to the fluid injector system 900. In some non-limiting embodiments, the fluid injector system 900 may include the connection port 928. 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 injection system 900. For example, gateway device 932 may include a printed circuit board (PCB) that is installed within fluid injection system 900. Referring now to FIG. 10, FIG. 10 illustrates a non-limiting embodiment of the injector head unit 1001 of a fluid injection system, such as the MEDRAD® Stellant Flex CT injection system, with a gateway device 1022. As shown in FIG. 10, the injector head unit 1001 may include the housing 1002 and at least one fluid reservoir 1004, such as a syringe or a fluid pump container. In some non-limiting embodiments, the fluid injection system may include an actuating component for controlling fluid flow into or out of a fluid reservoir, such as a piston associated with each of the fluid reservoirs 1004 that actuates plungers 1006 within a cylinder of the fluid reservoir 1004. In some non-limiting embodiments, each of the fluid reservoirs 1004 is adapted to releasably interact with the housing 1002 at 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 imaging contrast media, saline solution, or any desired medical fluid. Each fluid reservoir 1004 may be filled with a different medical fluid F. In some non-limiting embodiments, the fluid injection system may be a multi-syringe injector, as shown, wherein two fluid reservoirs 1004 may be oriented side by side or in another spatial relationship and are actuated separately by respective pistons associated with the fluid injection system. The fluid injection system can be used during a medical procedure to inject at least one medical fluid F into a patient's vasculature by actuating plungers 1006 associated with the fluid reservoir 1004 with an actuating component. The actuating component can move the plunger 1006 toward the distal end 1010 of the fluid reservoir 1004 to expel fluid F from the fluid reservoir 1004 into and through the fluid pathway assembly 1012 during a priming, purging, and / or fluid delivery step.In some non-limiting embodiments, the fluid pathway assembly 1012 may include at least one tube or set of tubes configured to be in fluid communication with each fluid reservoir 1004 to put each fluid reservoir 1004 into fluid communication with a flexible delivery tube and associated catheter to deliver fluid F from each fluid reservoir 1004 to a patient at a vascular access site. As shown in FIG. 10, the gateway device 1022 can be a component of the injector head unit 1001 of the fluid injector system. For example, the gateway device 1022 can include a PCB that is installed inside the injector head unit 1001. Although the systems, procedures, and products of the above computer programs have been described in detail for illustrative purposes based on what are currently considered to be the most practical and preferred realizations or aspects, it should be understood that such detail is solely for that purpose and that the present disclosure is not limited to the realizations or aspects described.

Claims

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,comprising the gateway device: 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 service system of a fluid injection system and the 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; provide an interface that allows the user to manage a configuration of the gateway device and that allows the fluid injection system to interact with high-level functionality of the gateway device based on a call to the application programming interface (API),from the fluid injection system; transmit the computer-associated data received from the hospital information system to a fluid injection system via a communication network based on an API call from the fluid injection system; and receive the computer-associated data from the hospital information system via the communication network in accordance with a communications protocol for communicating computer-associated data, wherein, when receiving computer-associated data from the hospital information system, at least one processor is programmed or configured to: receive data associated with a patient procedure or data associated with a radiological image from the hospital information system via the communication network in accordance with a Digital Imaging and Communications in Medicine (DICOM) communications protocol.or receive data associated with a radiological procedure from the hospital information system via the communication network in accordance with a standard Health Level Seven (HL7) communications protocol.

2. The system of claim 1, wherein, when receiving data associated with the computer from the hospital information system, at least one processor is programmed or configured to: receive data associated with a fluid injection system operation from the hospital information system via the communication network based on an API call.

3. The system of claim 1, wherein, when receiving data associated with the computer from the hospital information system,1. The system of claim 1, wherein at least one processor is programmed or configured to: receive data associated with radiation dosage during a radiological imaging study from the hospital information system via the communication network based on an API call.

2. The system of claim 1, wherein at least one processor is further programmed or configured to: receive data associated with a service function of the fluid injection system from the fluid injection system's service and control system via the communication network based on an API call.

3. The system of claim 1, wherein at least one processor is further programmed or configured to: receive data associated with an operation of the medical imaging system from the medical imaging system via the communication network based on an API call.

4. The system of claim 1,wherein the at least one processor is further programmed or configured to: transmit data associated with service information received from the fluid injection system's service and control system to the fluid injection system via a communication network based on an API call from the fluid injection system.

7. The system of claim 1, wherein the at least one processor is further programmed or configured to: transmit data associated with an image received from the medical imaging system to the fluid injection system via a communication network based on an API call from the fluid injection system.

8. The system of claim 1, wherein the at least one processor is further programmed or configured to: provide a graphical user interface to a user for receiving user input.

9. The system of claim 1,further comprising a memory device, and wherein the memory device stores a plurality of applications,and wherein the plurality of applications comprises: a computer application associated with the first communication interface between the hospital information system and the fluid injection system for storing data associated with a patient examination procedure and / or data associated with a configuration of the fluid injection system 104; a remote service connectivity application associated with the second communication interface between the fluid injection system's service and control system and the fluid injection system; and an image generation connectivity system application associated with the third communication interface between the medical image generation system and the fluid injection system.

10. The system of claim 9,further comprising: a display unit; wherein the plurality of applications comprises: a fourth application associated with a graphical user interface provided to a user by the display unit to receive user input.

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

Images