Systems, methods, and computer program products for providing access to fluid injection systems

Abstract

This invention provides a system and method for safely accessing a fluid injection system. [Solution] The method includes at least one processor programmed or configured to authenticate a user for access to a fluid injection system (302), provide data identifying one or more functions of a software application for accessing the fluid injection system (304), receive data identifying selected functions of a software application for accessing the fluid injection system (306), and provide access to selected functions of a software application for accessing the fluid injection system (308).

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit of U.S. Provisional Application No. 63 / 088,343, filed on October 6, 2020, the entire disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure generally relates to systems, devices, products, apparatuses, and methods for providing access to an electronic device, and in one particular embodiment, to systems, products, and methods for safely accessing a fluid injection system.

Background Art

[0003] Infusion devices, such as fluid infusion devices (e.g., medical fluid delivery devices), can be used by practicing physicians, such as internists, in medical diagnostic procedures and / or medical treatment procedures. For example, a practicing physician can use a fluid infusion device to inject one or more medical fluids into a patient. Fluid infusion devices can be used for the pressure infusion of medical fluids, such as radiographic contrast materials (e.g., contrast agents, radiographic contrast agents, contrast agents, etc.) and / or flushing agents 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, fluid infusion devices are designed to deliver a preset amount of medical fluid at a preset flow rate.

[0004] In some cases, access to the software of the injection device may be provided via a hardware key (e.g., a dongle, a software protection dongle, a software protection key, etc.), such as a Software Copyright Infringement Prevention Hardware (HASP) key. The hardware key may also be an electronic copy and software content protection device. When connected to the injection device, the hardware key can be used to unlock software functions and / or decrypt content. The hardware key may include a product key (e.g., a software key) and / or other cryptographic protection mechanisms (e.g., may be programmed with them), and may enable access to the software of the injection device when the hardware key is connected to an electrical connector, such as a Universal Serial Bus (USB) connector, on the injection device. [Overview of the project] [Means for solving the problem]

[0005] Therefore, systems, devices, products, apparatus, and / or methods are provided for safely accessing a fluid injection system, which improve the availability and / or accessibility of information regarding the software environment of the fluid injection system.

[0006] Further non-limiting embodiments are described in the following numbered clauses.

[0007] Clause 1: A system for accessing a fluid injection system, comprising at least one processor programmed or configured to authenticate a user for access to the fluid injection system, provide data identifying one or more functions of a software application for accessing the fluid injection system, receive data identifying selected functions of a software application for accessing the fluid injection system, and provide access to the selected functions of the software application for accessing the fluid injection system.

[0008] Clause 2: The system as described in Clause 1, wherein at least one processor is further programmed or configured to display data relating to selected functions of a software application for accessing the fluid injection system via a graphical user interface (GUI) of a mobile application on a user device.

[0009] Clause 3: The system described in Clause 1 or 2, wherein at least one processor is further programmed or configured to determine whether a user is authorized to access selected functions of a software application for accessing the fluid injection system, based on authenticating the user for access to the fluid injection system.

[0010] Clause 4: In determining whether a user is authorized to access selected functions of a software application for accessing a fluid injection system, at least one processor in the system described in any one of Clauses 1 to 3 is further programmed or configured to determine whether the user has an access level that authorizes the user to access selected functions of a software application for accessing a fluid injection system.

[0011] Clause 5: The fluid injection system includes a display screen, and at least one processor is further programmed or configured to display data related to the fluid injection system on the display screen of the fluid injection system, as described in any one of Clauses 1 to 4.

[0012] Clause 6: The system according to any one of Clauses 1 to 5, wherein at least one processor is further programmed or configured to access selected functions of the software application of the fluid injection system to provide data relating to the fluid injection system, and the data relating to the fluid injection system includes data relating to one or more operations of the fluid injection system, and at least one processor is further programmed or configured to record data relating to one or more operations of the fluid injection system.

[0013] Clause 7: In the case of providing access to selected functions of a software application for accessing a fluid injection system, at least one processor is programmed or configured to provide access to selected functions of a software application for accessing a fluid injection system, based on determining that the user is authorized to access selected functions of the software application, as described in any one of Clauses 1 to 6.

[0014] Clause 8: A computer program product for accessing a fluid injection system, the computer program product comprising at least one non-temporary computer-readable medium which, when executed by at least one processor, causes at least one processor to authenticate a user for access to the fluid injection system, provide data identifying one or more functions of a software application for accessing the fluid injection system, receive data identifying selected functions of the software application for the fluid injection system, and provide access to selected functions of the software application for the fluid injection system.

[0015] Clause 9: The computer program product described in Clause 8, wherein one or more instructions further cause at least one processor to display data relating to a selected function of a software application for a fluid injection system via a graphical user interface (GUI) of a mobile application on a user device.

[0016] Clause 10: The computer program product described in Clause 8 or 9, further comprising one or more instructions causing at least one processor to determine whether a user is authorized to access selected functions of the software application for the fluid injection system, based on authenticating the user for access to the fluid injection system.

[0017] Clause 11: A computer program product as described in any one of Clauses 8 to 10, wherein one or more instructions causing at least one processor to determine whether a user is authorized to access selected functions of a software application for accessing a fluid injection system, further causing at least one processor to determine whether a user has an access level that authenticates the user's access to selected functions of a software application for accessing a fluid injection system.

[0018] Clause 12: A computer program product according to any one of Clauses 8 to 11, wherein the fluid injection system includes a display screen, and one or more instructions further cause at least one processor to display data related to the fluid injection system on the display screen of the fluid injection system.

[0019] Clause 13: A computer program product as described in any one of Clauses 8 to 12, wherein one or more instructions further cause at least one processor to access selected functions of a software application for accessing a fluid injection system in order to provide data relating to the fluid injection system, the data relating to the fluid injection system includes data relating to one or more operations of the fluid injection system, and one or more instructions further cause at least one processor to record data relating to one or more operations of the fluid injection system.

[0020] Clause 14: A computer program product as described in any one of Clauses 8 to 13, wherein one or more instructions causing at least one processor to provide access to selected functions of a software application for accessing a fluid injection system, further causing at least one processor to provide access to selected functions of a software application for accessing a fluid injection system, based on determining that the user is authorized to access selected functions of a software application for accessing a fluid injection system.

[0021] Clause 15: A method for accessing a fluid injection system, comprising: using at least one processor to authenticate a user for access to the fluid injection system; using at least one processor to provide data identifying one or more functions of a software application for accessing the fluid injection system; using at least one processor to receive data identifying selected functions of a software application for accessing the fluid injection system; and using at least one processor to provide access to selected functions of a software application for accessing the fluid injection system.

[0022] Clause 16: The method of Clause 15, further comprising the step of displaying data relating to a selected function of a software application for a fluid injection system via a graphical user interface (GUI) of a mobile application on a user device.

[0023] Clause 17: The method of Clause 15 or 16, further comprising a step of determining whether the user is authorized to access selected functions of the software application for accessing the fluid injection system, based on a step of authenticating the user for access to the fluid injection system.

[0024] Clause 18: The method of any one of Clauses 15 to 17, wherein the step of determining whether a user is authorized to access selected functions of a software application for accessing a fluid injection system includes the step of determining whether the user has an access level that authorizes the user to access selected functions of a software application for accessing a fluid injection system.

[0025] Clause 19: The method according to any one of Clauses 15 to 18, wherein the fluid injection system includes a display screen, and the method further includes the step of displaying data related to the fluid injection system on the display screen of the fluid injection system.

[0026] Clause 20: The method according to any one of Clauses 15 to 19, further comprising the step of accessing selected functions of a software application for accessing a fluid injection system in order to provide data relating to the fluid injection system, wherein the data relating to the fluid injection system includes data relating to one or more operations of the fluid injection system, and the method further comprising the step of recording the data relating to one or more operations of the fluid injection system.

[0027] Clause 21: The step of providing access to a selected function of a software application for accessing a fluid injection system includes the step of providing access to a selected function of a software application for accessing a fluid injection system based on the step of determining that the user is authorized to access the selected function of the software application, the method according to any one of Clauses 15 to 20.

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

[0029] Further advantages and details of the present disclosure are described in more detail below with reference to the exemplary embodiments shown in the accompanying schematic drawings.

Brief Description of the Drawings

[0030] [Figure 1] FIG. is a diagram of a non-limiting embodiment of an environment in which the systems, devices, products, apparatuses, and / or methods described herein may be implemented in accordance with the principles of the present disclosure. [Figure 2] FIG. is a diagram of a non-limiting embodiment of the components of one or more systems or one or more devices of FIG. 1. [Figure 3] FIG. is a flowchart of a non-limiting embodiment of a process for safely accessing a fluid injection system. [Figure 4A] FIG. is a diagram showing a non-limiting example of an imaging suite and a non-limiting embodiment of a fluid injection system therein. [Figure 4B] Figure 4A shows the injector head unit of the fluid injection system. [Figure 4C] This figure shows another non-limiting embodiment of the fluid injection system. [Figure 5A] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5B] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5C] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5D] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5E] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5F] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5G] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5H] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5I] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5J]This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5K] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5L] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5M] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5N] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5O] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5P] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5Q] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5R] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5S] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5T]This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5U] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5V] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Figure 5W] This is a diagram of a non-limiting embodiment of a graphical user interface (GUI) displayed during the process of securely accessing a fluid injection system. [Modes for carrying out the invention]

[0031] For the purposes of the following description, the terms “end,” “top,” “bottom,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” and “longitudinal,” and their derivatives, are used in relation to this disclosure as oriented in the drawings. However, it should be understood that this disclosure may assume various alternative variations and step sequences unless expressly otherwise specified. It should also be understood that certain devices and processes shown in the accompanying drawings and described in the following specification are merely exemplary embodiments of this disclosure. Accordingly, certain dimensions and other physical characteristics relating to embodiments of the embodiments disclosed herein should not be considered limiting unless otherwise indicated.

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

[0033] As used herein, the terms “communicate” and “communicate” may mean receiving, taking, transmitting, forwarding, and / or providing information (e.g., data, signals, messages, instructions, commands, etc.). When one unit (e.g., a device, a system, a component of a device or system, a combination thereof, and / or something similar) communicates with another unit, it means that one unit can directly or indirectly receive information from and / or transmit information to the other unit. This may mean a direct or indirect connection that is essentially wired and / or wireless. Furthermore, two units can communicate with each other even if the transmitted information is modified, processed, relayed, and / or routed between the first and second units. For example, the first unit can communicate with the second unit without the first unit passively receiving information and actively transmitting information to the second unit. As another example, if at least one intermediate unit (e.g., a third unit located between the first and second units) processes information received from the first unit and communicates the processed information to the second unit, then the first unit can communicate with the second unit. In some non-limiting embodiments, a message can refer to a network packet containing data (e.g., a data packet). It will be understood that many other configurations are possible.

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

[0035] In some cases, a fluid injection device may be part of a group of devices used in a medical treatment facility, such as a hospital, during patient treatment. Individuals such as technicians (e.g., on-site service engineers), administrators, or others properly trained in the operation of the fluid injection device may access the fluid injection device's software via a hardware key. In some examples, individuals may access service-related software tools via a hardware key. For example, a fluid injection device may malfunction during fluid injection operation, and an individual may obtain information about the malfunction by connecting a hardware key to the fluid injection device and downloading a report containing the information. Furthermore, individuals may install software updates on the fluid injection device, including product enhancements, operating system updates, and / or security updates (e.g., security patches), for example, by using a hardware key.

[0036] However, individuals may need to possess a hardware key to access fluid injection devices, and the physical nature of hardware keys can be problematic due to the possibility of loss, damage, and / or theft. Furthermore, multiple hardware keys may be associated with a particular fluid injection device, and two or more keys may be required to access all the software functions of that device. In addition, product keys associated with hardware keys may expire following the term of the user license, and as part of the user license renewal process, the operator of the fluid injection device may need to obtain and provide the identification information of the fluid injection device. The process of obtaining and providing the identification information of the fluid injection device may be resource- and labor-intensive on behalf of the operator. Similarly, when components of a fluid injection device are maintained and / or replaced, the product key may need to be updated on the hardware key before the hardware key can access the software functions of the fluid injection device.

[0037] Non-limiting embodiments of this disclosure relate to systems, devices, products, apparatus, and / or methods for securely accessing a fluid injection system. In some non-limiting embodiments, the access management system may include at least one processor programmed or configured to authenticate a user for access to the fluid injection system, provide data identifying one or more functions of a software application for accessing the fluid injection system, receive data identifying selected functions of the software application for accessing the fluid injection system, and provide access to the selected functions of the software application for accessing the fluid injection system. In some non-limiting embodiments, the at least one processor is further programmed or configured to display data relating to the selected functions of the software application for accessing the fluid injection system via a graphical user interface (GUI) of a mobile application on a user device. In some non-limiting embodiments, the at least one processor is further programmed or configured to determine, based on authenticating the user for access to the fluid injection system, whether the user is authorized to access the selected functions of the software application for accessing the fluid injection system. In some non-limiting embodiments, when determining whether the user is authorized to access the selected functions of the software application for accessing the fluid injection system, the at least one processor is further programmed or configured to determine whether the user has an access level that authorizes the user to access the selected functions of the software application for accessing the fluid injection system.

[0038] In some non-limiting embodiments, the fluid injection system includes a display screen, and at least one processor is further programmed or configured to display data related to the fluid injection system on the display screen of the fluid injection system. In some non-limiting embodiments, at least one processor is further programmed or configured to access selected functions of a software application for the fluid injection system to provide data related to the fluid injection system, and the data related to the fluid injection system includes data related to one or more operations of the fluid injection system, and at least one processor is further programmed or configured to record data related to one or more operations of the fluid injection system. In some non-limiting embodiments, if access to selected functions of a software application for accessing the fluid injection system is provided, at least one processor is programmed or configured to provide access to selected functions of the software application for accessing the fluid injection system based on determining that the user is authorized to access selected functions of the software application.

[0039] In this way, non-limiting embodiments of the present disclosure provide readily available access to a fluid injection system and information related to the fluid injection system. Furthermore, non-limiting embodiments of the present disclosure eliminate the need for a hardware key used to access the fluid injection system. In this way, non-limiting embodiments of the present disclosure also eliminate the need to update information stored in a hardware key, including a product key for accessing the software functions of the fluid injection device.

[0040] Referring here to Figure 1, Figure 1 is a diagram of an exemplary environment 100 in which the devices, systems, and / or methods described herein may be implemented. As shown in Figure 1, the environment 100 includes an access management system 102, a fluid injection system 104, a workstation device 106, a support system 108, a user device 110, and a communication network 112. In some non-limiting embodiments, the access management system 102, the fluid injection system 104, the workstation device 106, the support system 108, and / or the user device 110 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections (e.g., to establish connections for communication).

[0041] In some non-limiting embodiments, the access management system 102 includes one or more devices that can communicate with the fluid injection system 104, the workstation device 106, the support system 108, and / or the user device 110 via the communication network 112. For example, the access management system 102 may include computing devices such as a computer, a server, a group of servers, and / or other similar devices. In some non-limiting embodiments, the access management system 102 may be a component of the fluid injection system 104 and / or the workstation device 106.

[0042] In some non-limiting embodiments, the fluid infusion system 104 includes one or more devices that can communicate with an access management system 102, a workstation device 106, a support system 108, and / or a user device 110 via a communication network 112. For example, the fluid infusion system 104 may include computing devices such as one or more computers, servers, groups of servers, and / or other similar devices. In some non-limiting embodiments, the fluid infusion system 104 includes one or more infusion devices (e.g., one or more fluid infusion devices). In some non-limiting embodiments, the fluid infusion system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid containing a contrast agent to a patient, and / or to administer an aqueous fluid such as saline to the patient before, during, and / or after administration of the contrast fluid. For example, the fluid infusion system 104 may inject one or more prescribed doses of contrast fluid directly into the patient's bloodstream via a subcutaneous needle and syringe. In some non-limiting embodiments, the fluid infusion system 104 may be configured to continuously administer aqueous fluid to the patient through a peripheral venous line (PIV) and catheter, and 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 infusion system 104 may be configured to infuse a certain dose of contrast fluid, followed by the administration of a specific volume of aqueous fluid. In some non-limiting embodiments, the fluid infusion system 104 may include a device capable of reading (e.g., scanning) barcodes such as Quick Response (QR) Codes®.

[0043] In some non-limiting embodiments, the fluid injection system 104 may include one or more exemplary injection systems or injectors, which include U.S. Patent Application No. 09 / 715,330, filed on 17 November 2000 and issued as U.S. Patent No. 6,643,537; U.S. Patent Application No. 09 / 982,518, filed on 18 October 2001 and issued as U.S. Patent No. 7,094,216; and U.S. Patent Application No. 7,556,619, filed on 16 April 2004. This information is disclosed in U.S. Patent Application No. 12 / 437,011, filed on 7 May 2009 and issued as U.S. Patent No. 8,337,456, U.S. Patent Application No. 12 / 476,513, filed on 2 June 2009 and issued as U.S. Patent No. 8,147,464, and U.S. Patent Application No. 11 / 004,670, filed on 3 December 2004 and issued as U.S. Patent No. 8,540,698, each of which is incorporated herein by reference in its entirety. In some non-limiting embodiments, the fluid injection system 104 may include the MEDRAD® Stellant CT injection system, the MEDRAD® Stellant FLEX CT injection system, the MEDRAD® Spectris Solaris EP MR injection system, the MEDRAD® MRXperion MR injection system, the MEDRAD® Salient contrast agent injection system, the MEDRAD® Mark 7 Arterion injection system, the MEDRAD® Avanta fluid management injection system, the MEDRAD® Intego PET injection system, or the MEDRAD® Centargo CT injection system, all of which are supplied by Bayer.

[0044] In some non-limiting embodiments, the workstation device 106 includes one or more devices that can communicate with the access management system 102, the fluid injection system 104, the support system 108, and / or the user device 110 via the communication network 112. For example, the workstation device 106 may include one or more computing devices such as computers, including desktop computers, laptops, and / or tablets. In some non-limiting embodiments, the workstation device 106 may provide a control interface for controlling the operation of the fluid injection system 104, including providing input to the fluid injection system 104. Additionally or alternatively, the workstation device 106 may display the operating parameters of the fluid injection system 104 while the fluid injection system 104 is operating (e.g., during real-time operation). In some non-limiting embodiments, the workstation device 106 may provide interconnectivity between the fluid injection system 104 and other devices or systems, such as a scanner device (not shown). In some non-limiting embodiments, the workstation device 106 may include a Certegra® workstation provided by Bayer.

[0045] In some non-limiting embodiments, the support system 108 may include one or more devices that can communicate with the access management system 102, the fluid injection system 104, the workstation device 106, and / or the user device 110 via the communication network 112. For example, the support system 108 may include computing devices such as computers, servers (e.g., web servers), groups of servers, and / or other similar devices. In some non-limiting embodiments, the support system 108 may include backend systems associated with the access management system 102, the fluid injection system 104, and / or the workstation device 106. In some non-limiting embodiments, the support system 108 may include a cloud computing system that stores data in an associated database. In some non-limiting embodiments, the support system 108 may interact with the fluid injection system 104 to provide functions such as remote equipment services for the fluid injection system 104 (for example, the VirtualCARE® remote equipment support service targets injection systems and devices provided by Bayer). In some non-limiting embodiments, the support system 108 may be operated by, or on behalf of, the 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), the provider of the fluid injection system 104, the imaging site or hospital where the fluid injection system 104 operates, and / or service technicians assigned to the fluid injection system 104. In some non-limiting embodiments, the support system 108 may include a hospital information system (HIS) and / or a radiology information system (RIS). In some non-limiting embodiments, the support system 108 may include a customer relationship management (CRM) system.

[0046] In some non-limiting embodiments, the user device 110 may include one or more devices that can communicate with the access management system 102, the fluid injection system 104, the workstation device 106, and / or the support system 108 via the communication network 112. For example, the user device 110 may include a computing device such as a computer (e.g., a desktop, laptop, etc.) or a mobile device (e.g., a smartphone, tablet, etc.). In some non-limiting embodiments, the user device 110 may be able to read (e.g., scan) barcodes such as Quick Response (QR) Codes®. In some non-limiting embodiments, the user device 110 may be configured to transmit and / or receive data to and from another device or system (e.g., the fluid injection system 104, the workstation device 106) via a short-range wireless communication connection (e.g., NFC communication connection, RFID communication connection, Bluetooth® communication connection, and / or similar). In some non-limiting embodiments, the user device 110 may be configured to transmit and / or receive data via Radio Frequency Identification (RFID). For example, the user device 110 may include an RFID reader. In some non-limiting embodiments, the user device 110 may be associated with a user (e.g., an individual operating the device). In some non-limiting embodiments, one or more software (e.g., mobile) applications may be associated with the user device 110 (e.g., applications stored on the user device 110, such as a mobile device application, a native application for a mobile device, or a mobile cloud application for a mobile device) (e.g., they may be installed and / or run).

[0047] In some non-limiting embodiments, the communication network 112 may include one or more wired and / or wireless networks. For example, the communication network 112 may include cellular networks (e.g., Long-Term Evolution (LTE) networks, 3G networks, 4G networks, 5G networks, Code Division Multiple Access (CDMA) networks, etc.), public land mobile networks (PLMN), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), telephone networks (e.g., public switched telephone networks (PSTNs)), private networks, ad hoc networks, intranets, the Internet, fiber optic-based networks, cloud computing networks, short-range wireless communication networks (e.g., Bluetooth® networks, near-field communication (NFC) networks, etc.), and / or combinations of these or other types of networks.

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

[0049] Referring now to Figure 2, Figure 2 is a diagram of exemplary components of device 200. Device 200 may correspond to one or more devices of the access management system 102, one or more devices of the fluid injection system 104, a workstation device 106, one or more devices of the support system 108, and / or a user device 110. In some non-limiting embodiments, the access management system 102, the fluid injection system 104, the workstation device 106, the support system 108, and / or the user device 110 may include at least one device 200 and / or at least one component of device 200. As shown in Figure 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 interface 214.

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

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

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

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

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

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

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

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

[0058] Aspects of non-limiting embodiments of this specification (e.g., one or more steps of process 300) may be performed with respect to a software application, such as a mobile application, having client-side components stored on a user device 110 associated with a server-side component of the access management system 102. In some non-limiting embodiments, the software application may be operated by (e.g., controlled by) the access management system 102 to access one or more functions of the software environment of the fluid injection system 104 (e.g., one or more software applications of the software environment, one or more software services of the software environment, one or more software tools of the software environment, etc.). Additionally or alternatively, one or more aspects of the software application may be stored in the fluid injection system 104 and / or the workstation device 106. In some non-limiting embodiments, one or more functions of the software application can provide access to one or more functions of the software environment of the fluid injection system 104.

[0059] In some non-limiting embodiments, one or more functions of the software environment of the fluid injection system 104 may include functions related to a patient procedure tracking system (e.g., a system for operating modality worklists, a system for providing patient demographic information for fluid injection procedures and / or medical imaging procedures), functions related to a fluid injector management system, functions related to an image archiving and communication system (e.g., a picture archiving and communication system (PACS)), functions related to a radiology information system (RIS), and / or functions related to a radiology analysis system (e.g., Radimetrics® Enterprise Application, commercially available from Bayer HealthCare LLC).

[0060] As shown in Figure 3, in step 302, process 300 includes a step of authenticating the user for access to the fluid injection system. For example, the access management system 102 may authenticate the user for access to the fluid injection system 104 via a software application for accessing the fluid injection system 104 stored on the user device 110. The access management system 102 may authenticate the user for access to the fluid injection system 104 via a software application independent of (e.g., without using a hardware key). In some non-limiting embodiments, the access management system 102 may receive user identification data from the user via the user device 110 (e.g., a software application for accessing the fluid injection system 104 stored on the user device 110) during the login process, and the access management system 102 may use the user identification data for authenticating the user for access to the fluid injection system 104 (e.g., access to one or more functions of the software application for accessing the fluid injection system 104). In some non-limiting embodiments, the access management system 102 may generate a graphical user interface (GUI) and provide a GUI for display on the user device 110 to receive user input as part of the login process. User input may include login credentials. In some non-limiting embodiments, login credentials may include user identification data, such as a username, password, employee identification number, device identifier (e.g., Internet Protocol (IP) address, Media Access Control (MAC) address), telephone number, office location, and / or office address. In some non-limiting embodiments, login credentials may include user biometric data (e.g., fingerprints, iris scan, images of body parts of the user).In some non-limiting embodiments, the access management system 102 can authenticate a user for access to a software application for accessing the fluid injection system 104, and based on the user authentication, the access management system 102 can determine whether the user is authorized to access one or more functions of the software application.

[0061] In some non-limiting embodiments, the access management system 102 can generate login credentials to provide to the fluid injection system 104 to authenticate a user for access to the fluid injection system 104. For example, the access management system 102 can generate login credentials (e.g., a password, passcode, etc.) based on a clock (e.g., the internal clock of the user device 110). In some non-limiting embodiments, the access management system 102 can provide a GUI to the fluid injection system 104 or workstation device 106 (e.g., on the display screen of the fluid injection system 104 or workstation device 106) to display indicators, and the access management system 102 can receive login credentials associated with the indicators from the user device 110 via a software application. For example, the access management system 102 can provide a GUI on the display screen of the fluid injection system 104 or workstation device 106 to display an image (e.g., an image of a QR code®), and the user device 110 can scan the image. The user device 110 can determine the login credentials associated with the image, and the user device 110 can provide the login credentials to access the management system 102 via a software application. The access management system 102 can authenticate a user for access to the fluid injection system 104 based on receiving login authentication information via a software application. In some non-limiting embodiments, the access management system 102 can provide a GUI for displaying indicators to a user device 110, and the access management system 102 can receive login credentials related to the indicators from the fluid injection system 104 via a software application. For example, the access management system 102 can provide a GUI on the display screen of the user device 110 that displays an image (e.g., an image of a QR code®), and the fluid injection system 104 can scan the image.The fluid injection system 104 can determine login credentials associated with an image, and can provide login credentials to access the management system 102 via a software application. The access management system 102 can authenticate a user for access to the fluid injection system 104 based on receiving login authentication information via the software application.

[0062] In some non-limiting embodiments, the access management system 102 may receive login credentials from the fluid injection system 104 to authenticate a user for access to the fluid injection system 104. For example, the access management system 102 may provide login credentials to a user (e.g., via a user device), and the user may enter the login credentials into the fluid injection system 104. The fluid injection system may transmit the login credentials to the access management system 102, and the access management system 102 may authenticate a user for access to the fluid injection system 104 based on the receipt of the login credentials.

[0063] In some non-limiting embodiments, features of a software application for accessing the fluid injection system 104 (e.g., services, tools, etc.) may include one or more functions related to providing data related to the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may communicate with a web application (e.g., communicating with a web application operated by a web server) to retrieve data related to the fluid injection system 104 via the software application. For example, the access management system 102 may communicate with the web application to retrieve data related to user profiles and / or data related to user licenses (e.g., software licenses for users), etc.

[0064] In some examples, data related to the fluid injection system 104 may include data related to the identifier of the fluid injection system 104 (e.g., device identifier of the fluid injection system 104, model number of the fluid injection system 104, serial number of the fluid injection system 104, etc.), data related to the software or hardware of the fluid injection system 104 (e.g., software configuration of the fluid injection system 104, hardware configuration of the fluid injection system 104, software version of the fluid injection system 104 such as the software version of the operating system of the fluid injection system 104, revision number of the software of the fluid injection system 104, identifier of one or more software patches applied to the fluid injection system 104, etc.), and / or data related to the network connectivity of the fluid injection system 104 (e.g., MAC address of the network interface controller (NIC) of the fluid injection system 104, IP address of the fluid injection system 104, etc.). In some non-limiting embodiments, data related to the fluid injection system 104 may include data related to one or more operations of the fluid injection system 104. Data relating to one or more operations of the fluid injection system 104 may include data relating to operations performed by the fluid injection system 104 (e.g., the number of fluid injection operations performed by the fluid injection system 104, the duration of the fluid injection operations performed by the fluid injection system 104, the operation parameters of the fluid injection operations performed by the fluid injection system 104, data relating to patient demographics of patients to whom the fluid injection operation was performed by the fluid injection system 104, etc.), data relating to the configuration of the fluid injection system 104 (e.g., the configuration of the fluid delivery components of the fluid injection system 104, the cybersecurity component list (CBOM) of the fluid injection system 104, the software component list (SBOM) of the fluid injection system 104, etc.), and / or data relating to malfunctions encountered during one or more operations of the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may log (e.g., store in a data log) data relating to the fluid injection system 104.For example, the access management system 102 may record data relating to one or more operations of the fluid infusion system 104. It should be noted that, because embodiments of this disclosure comply with all legal requirements, such as the Health Insurance Portability and Accountability Act (HIPAA), the data relating to the fluid infusion system 104 that is stored or communicated may not appropriately include patient personal health information such as PHI and PII.

[0065] In some non-limiting embodiments, the operating parameters of the fluid injection operation performed by the fluid injection system 104 may include one or more exemplary data types, which are disclosed in U.S. Patent Application No. 10 / 143,562, filed on 10 May 2002 and issued as U.S. Patent No. 7,457,804; U.S. Patent Application No. 12 / 254,318, filed on 20 October 2008 and issued as U.S. Patent No. 7,996,381; and U.S. Patent Application No. 13 / 180,175, filed on 11 July 2011 and issued as U.S. Patent No. 8,521,716, each of which is incorporated herein by reference in whole.

[0066] In some non-limiting embodiments, data relating to malfunctions encountered during one or more operations of the fluid injection system 104 may include identifiers of errors related to the operation of the fluid injection system 104. These identifiers may include error codes (e.g., specific error codes related to the type of malfunction that occurred). Additionally or alternatively, data relating to anomalies encountered during one or more operations of the fluid injection system 104 may include operating parameters of the fluid injection system 104 related to the anomaly. For example, data relating to malfunctions encountered during one or more operations of the fluid injection system 104 may include temperature measurements of components of the fluid injection system 104, pressure measurements related to components used with the fluid injection system 104 (e.g., disposable sets, e.g., multi-use disposable sets (MUDS), single-use disposable sets (SUDS), syringes, or tube sets), measurements of the electrical characteristics of the electrical components of the fluid injection system 104 (e.g., voltage, current, power, etc.), and / or other relevant values ​​of variables and / or system components.

[0067] In some non-limiting embodiments, the functions of the software application for accessing the fluid injection system 104 include: functions related to obtaining data (e.g., reading, scanning, retrieving from a data structure, etc.) related to the error codes of the fluid injection system 104 (e.g., error codes generated by the fluid injection system 104); functions related to determining the location of the fluid injection system 104 (e.g., location based on Global Positioning System (GPS) location); functions related to generating the service history of the fluid injection system 104; functions related to providing the service history of the fluid injection system 104 (e.g., providing download, display, print, and transmission of messages containing the service history); functions related to providing a list of assets (e.g., multiple fluid injection systems 104, one or more components of the fluid injection system 104, components of multiple fluid injection systems 104, etc.); functions related to adding assets to the list of assets; functions related to providing a list of functions of the software environment of the fluid injection system 104 covered by the user license; and user Functions related to initiating billing (e.g., automatic billing) for one or more functions of the software environment of the fluid injection system 104 covered by the license; functions related to adding one or more functions of the software environment of the fluid injection system 104 (e.g., VirtualCARE® remote support enabling safe and reliable remote monitoring of the contrast agent injection system and software to minimize downtime, SelectCARE®, PartnerCARE®, and DirectCARE® service contract programs that provide high levels of service and capability including VirtualCARE®, TechCARE®, and equipment support services such as the TechCARE® NxT obsolescence program by Bayer, which also includes services and capabilities provided through the service contract program); functions related to generating service requests for the fluid injection system 104; functions related to registering warranties; consumables used during fluid injection procedures (e.g., multi-use disposable sets (MUDS),Functions related to providing data relating to single-use disposable sets (SUDS), syringes or tube sets; functions related to providing a list of one or more fluid injection protocols to the fluid injection system 104; functions related to adding or restoring one or more fluid injection protocols to the fluid injection system 104 (e.g., restoring according to service procedures); functions related to providing and / or receiving data relating to user preferences (e.g., user preferences relating to the appearance and feel of the software application, such as the display color and / or language of the data provided); functions related to providing software to the software environment of the fluid injection system 104 (e.g., providing an operating system); fluid injection system The functions may include functions related to providing instructions for the operation of 104, functions related to providing data related to service procedures to be performed on the fluid injection system 104 (e.g., data related to diagnostic and / or troubleshooting capabilities for service procedures, such as augmented reality (AR) capabilities for service procedures, real-time data related to the characteristics of components of the fluid injection system 104, such as calibration values, fluids, batteries, motors, etc.), functions related to providing data related to service procedures performed on the fluid injection system 104 (e.g., service reports based on service procedures, final checklists following service procedures, messages confirming completion of service procedures, etc.), and / or functions related to providing complaints about the product.

[0068] In some non-limiting embodiments, the functionality relating to providing a list of assets may include functionality relating to providing a list of assets related to user licenses. In some non-limiting embodiments, the functionality may provide a list of assets related to user licenses provided in accordance with an encryption protocol. In some non-limiting embodiments, the list of assets may include identifiers for scanning room unit (SRU) and control room unit (CRU) IDs. In some non-limiting embodiments, the list of assets may be organized (e.g., ranked) based on user preferences. In some non-limiting embodiments, the functionality may provide reports (e.g., service reports) relating to a list of assets related to user licenses (e.g., reports containing data related to each asset in the asset list, one or more assets in the asset list, etc.) (e.g., providing to download, view, print, and send messages containing reports, etc.). In some non-limiting embodiments, the functionality may provide to transmit reports to systems outside the fluid injection system 104 (e.g., service management systems, flight recorder systems, etc.). In some non-limiting embodiments, the function may provide data related to each asset, including software configuration (e.g., current software level), calibration date (e.g., most recent calibration date, all calibration dates, etc.), the user who performed the calibration, and the type of asset being calibrated (e.g., pressure, potentiometer, etc.).

[0069] In some non-limiting embodiments, functions related to providing software to the software environment of the fluid injection system 104 may provide software uploads, such as updates (e.g., patches) and additional functions, to the software environment of the fluid injection system 104, and / or software downloads from the software environment of the fluid injection system 104. For example, this function may provide software uploads and / or software downloads to the software environment of the fluid injection system 104 when a connection to the communication network 112 via a software application for accessing the fluid injection system 104 is unavailable. In some non-limiting embodiments, software uploads may be stored (e.g., preloaded) on a user device 110 via a software application and uploaded to the software environment of the fluid injection system 104 when a connection to the communication network 112 is unavailable. In some non-limiting embodiments, the function may provide a display of the size and / or completion status (e.g., a status completion bar) of software uploads to and / or software downloads from the fluid injection system 104.

[0070] In some non-limiting embodiments, the functionality related to determining the location of the fluid injection system 104 may include sending a request for the location of the fluid injection system 104, receiving data related to the location of the fluid injection system 104, and determining the location of the fluid injection system 104 based on the data related to the location of the fluid injection system 104. In some non-limiting embodiments, the request for the location of the fluid injection system 104 may include a message (e.g., an RFID-based message) transmitted via a communication method such as broadcast, multicast, and / or unicast.

[0071] In some non-limiting embodiments, the login process may include a user logging into a computer system, website, account, software platform, network (e.g., local network), intranet, etc. For example, a user may log in to the access management system 102 via a mobile application on a user device 110. In some non-limiting embodiments, the access management system 102 may receive login requests from the user device 110 via a mobile application (e.g., a mobile application associated with the access management system 102 stored on the user device 110). In some non-limiting embodiments, the access management system 102 may receive data related to user identification information and may authenticate a user based on the data related to user identification information as part of the login process. For example, a login request may include data related to user identification, and the access management system 102 may authenticate a user using all or part of the data related to user identification. In some non-limiting embodiments, the access management system 102 may authenticate a user using a multi-factor authentication process. For example, the access management system 102 may use data related to user identification information and additional data received from the user device 110 during the login process to authenticate a user.

[0072] In some non-limiting embodiments, the access management system 102 may authenticate a user based on a user license associated with the fluid injection system 104. For example, the access management system 102 may use data related to user identification to determine whether a user is associated with a valid user license. In some non-limiting embodiments, the access management system 102 may authenticate a user based on the determination that the user is associated with a valid user license. In some non-limiting embodiments, the access management system 102 may not be required to authenticate a user based on the determination that the user is not associated with a valid user license. In some non-limiting embodiments, the access management system 102 may revoke a user's access to the fluid injection system 104 based on the expiration date of the user license associated with the user. In some non-limiting embodiments, the access management system 102 may authenticate a user for access to a specific fluid injection system (e.g., a specific model of fluid injection system, a fluid injection system having a specific identifier, etc.) based on a user license.

[0073] In some non-limiting embodiments, the access management system 102 may authenticate a user based on data related to the identifier of the fluid injection system 104. For example, the access management system 102 may retrieve data related to the identifier of the fluid injection system 104 and use the data related to user identification and the data related to the identifier of the fluid injection system 104 to determine whether the user is associated with a valid user license for the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may authenticate a user based on the determination that the user is associated with a valid user license for the fluid injection system 104 identified by the identifier. In some non-limiting embodiments, the access management system 102 may not have to authenticate a user based on the determination that the user is not associated with a valid user license for the fluid injection system 104 identified by the identifier.

[0074] In some non-limiting embodiments, the access management system 102 can authenticate a user based on an indicator provided by a user device 110. For example, a user may use the user device 110 to scan an indicator such as a code associated with the fluid injection system 104 (e.g., a barcode such as Quick Response (QR) Code®), and the access management system 102 may receive data from the user device 110 related to the indicator, such as data related to the identifier of the fluid injection system 104, and data related to the user's user identification. The access management system 102 can authenticate a user based on the data related to the identifier of the fluid injection system 104 and the data related to the user's user identification. In some non-limiting embodiments, the access management system 102 may include one or more embodiments of a QR Code® system and / or other devices and systems, as disclosed in International Patent Application No. PCT / US2021 / 032659 filed on 17 May 2021, the disclosure of which is incorporated herein by reference in whole.

[0075] In some non-limiting embodiments, the access management system 102 can authenticate a user without a connection to the communication network 112. For example, the access management system 102 can authenticate a user via a software application stored on the user device 110 when a communication connection to the communication network 112 is unavailable. In some non-limiting embodiments, the access management system 102 can determine that a connection to the communication network 112 is unavailable to the user device 110 via a software application, and the access management system 102 can authenticate a user when a connection to the communication network 112 is available. For example, the access management system 102 can determine that a connection to the communication network 112 is unavailable, and the access management system 102 can periodically attempt to establish a communication connection to the communication network 112. The access management system 102 can authenticate a user when it determines that a connection to the communication network 112 is available via a software application.

[0076] In some non-limiting embodiments, the access management system 102 can receive login requests and perform actions based on those requests. For example, the access management system 102 can determine whether data related to user identification provided as part of the login request matches existing data related to user identification stored in a data structure (e.g., stored in user profiles within the data structure). The access management system 102 can provide a response to the user device 110 indicating that the user has successfully logged in, or that the data related to user identification information provided as part of the login request does not match existing data related to user identification information stored in the data structure.

[0077] In some non-limiting embodiments, the access management system 102 may create user profiles (e.g., account user profiles) based on data related to user identification. For example, if it is determined that a logged-in user is a new user, the access management system 102 may create a user profile and store the user profile in a data structure. In some non-limiting embodiments, the access management system 102 may create user profiles for applications, multiple applications, or the organization's software environment. In some non-limiting embodiments, the access management system 102 may create and / or modify user profiles based on data related to user identification received from a user device 110 via a mobile application.

[0078] In some non-limiting embodiments, the access management system 102 may acquire data related to user identification to determine that a user has been authenticated for access to the software application of the fluid injection system 104. For example, a user may provide a device identifier to the access management system 102 via a user device 110 (e.g., a mobile application stored on the user device 110), and the access management system 102 may determine the user's identification information based on the device identifier. The access management system 102 may determine that the user's identification information is associated with the software application and authenticate the user for access to the software application. In some non-limiting embodiments, the access management system 102 may acquire data related to user identification as part of or following the login process.

[0079] In some non-limiting embodiments, the access management system 102 can facilitate communication between the user's user device 110 and the fluid injection system 104. For example, the access management system 102 can establish a short-range wireless communication connection (e.g., Bluetooth® communication connection, Near Field Communication (NFC) communication connection, etc.) between the user device 110 and the fluid injection system 104. In another example, the access management system 102 can establish a wired communication connection between the user device 110 and the fluid injection system 104 (e.g., using the respective Universal Serial Bus (USB) ports of the user device 110 and the fluid injection system 104). In some non-limiting embodiments, the access management system 102 can facilitate communication between the user's user device 110 and the fluid injection system 104 via a software application stored on the user device 110 when a communication connection to the communication network 112 is unavailable. In some non-limiting embodiments, the access management system 102 can use the communication connection between the user device 110 and the fluid injection system 104 to provide data related to the fluid injection system 104 via a software application. In some non-limiting embodiments, the access management system 102 may communicate with medical imaging systems, fluid injection system service and control systems, hospital information systems, radiology information systems, service management systems (e.g., ServiceMax, SAP Mobile, etc.), and / or web servers (e.g., web servers associated with software applications) (e.g., through communication via software applications). In some non-limiting embodiments, the access management system 102 may communicate with gateway devices, one or more systems, and / or one or more applications disclosed in International Patent Application No. PCT / US2021 / 040800, filed on 8 July 2021, the disclosure of which is incorporated herein by reference in whole.

[0080] As shown in Figure 3, in step 304, process 300 includes the step of providing data that identifies one or more functions of a software application for accessing the fluid injection system. For example, the access management system 102 may provide the user device 110 with data that identifies one or more functions of a software application for accessing the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may provide the user with a plurality of function identifiers (e.g., a list of identifiers for a plurality of functions) of functions of the software application for accessing the fluid injection system 104 via a graphical user interface (GUI) on the user device 110.

[0081] In some non-limiting embodiments, the multiple function identifiers may be a subset of all function identifiers of the software application for accessing the fluid injection system 104. For example, the multiple application identifiers may be associated with a subset of functions of the software application to which a user is authorized to access (e.g., available for access to the user) based on the user's access level. In some non-limiting embodiments, the access level may be based on the user's user profile. For example, the access level may be based on the job position specified in the user's user profile (e.g., the user's role within the company, such as a field service engineer, clinical technician, distributor, or biomedical engineer). In some non-limiting embodiments, the access management system 102 may determine one or more functions of the software application for accessing the fluid injection system 104 to which a user is authorized to access, and the access management system 102 may provide (e.g., only provide) function identifiers for one or more functions to which the user is authorized to access.

[0082] As shown in Figure 3, in step 306, process 300 includes receiving data that identifies selected functions of a software application for accessing the fluid injection system. For example, the access management system 102 may receive data that identifies selected functions of a software application for accessing the fluid injection system 104.

[0083] In some non-limiting embodiments, the access management system 102 may receive data identifying selected functions of one or more functions of a software application for accessing the fluid injection system 104, based on user input to a GUI provided via a user device 110. In some non-limiting embodiments, the access management system 102 may receive information related to user selections of GUI elements displayed by the GUI on the screen of the user device 110. For example, based on the detection of user interaction with the GUI by the user device 110, the user device 110 may provide instructions for user selection to the access management system 102. The GUI elements may correspond to selected functions of one or more functions for which identification data has been provided via the GUI on the screen of the user device 110.

[0084] In some non-limiting embodiments, the access management system 102 may receive requests for access to a selected function based on the selection of a function from among several functions. For example, the access management system 102 may receive requests for access to a selected function based on the user selecting a GUI element corresponding to the function in the GUI on the user device 110. In some non-limiting embodiments, the access management system 102 may provide prompts to the user via the GUI on the user device 110 to provide information regarding the request for access to the selected function. For example, the prompt may ask the user to provide user-related data that has not been previously received and is useful in determining whether to provide access to the selected function.

[0085] As shown in Figure 3, in step 308, process 300 includes the step of providing access to selected features of a software application for accessing the fluid injection system. For example, the access management system 102 may provide access to selected features of a software application for accessing the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may provide access to features of a software application for accessing the fluid injection system 104 to a user device 110 (e.g., the user of user device 110) based on the access management system 102 which authenticates the user for accessing the fluid injection system 104 (e.g., only). In some non-limiting embodiments, the access management system 102 may provide access to specific features of a software application for accessing the fluid injection system 104 (e.g., features related to remote service procedures for the fluid injection system 104) to the user device 110 based on the access management system 102 which authenticates the user for accessing the fluid injection system 104.

[0086] In some non-limiting embodiments, the access management system 102 may provide access to selected functions of a software application for accessing the fluid injection system 104 stored on the user device 110 when a communication connection to the communication network 112 is unavailable. For example, the access management system 102 may determine that a connection to the communication network 112 is unavailable and attempt to establish a communication connection (e.g., a short-range wireless connection) between the user device 110 and the fluid injection system 104. The access management system 102 may provide access to selected functions of the software application via the communication connection between the user device 110 and the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may provide access to selected functions of the software application when one or more components of the fluid injection system 104 (e.g., an injector head, a display, a single-board computer printed circuit board (PCB), a servo CPU PCB, etc.) are being serviced (e.g., removed and / or replaced).

[0087] In some non-limiting embodiments, the access management system 102 can perform operations related to selected functions of the software application for accessing the fluid injection system 104. For example, the access management system 102 can receive and / or provide data related to selected functions of the software application for accessing the fluid injection system 104. In a particular example, the access management system 102 may scan the error codes of the fluid injection system 104, generate a service history of the fluid injection system 104, provide a service history of the fluid injection system 104, provide a list of assets, add an asset to the list of assets, provide a list of functions of the software environment of the fluid injection system 104 covered by a user license, initiate a billing procedure for one or more functions of the software environment of the fluid injection system 104 covered by a user license, add one or more functions of the software environment of the fluid injection system 104 to a user license, generate a service request for the fluid injection system 104, and provide a guarantee. It is possible to register, provide data on consumables used during the fluid injection procedure of the fluid injection system 104, provide a list of one or more fluid injection protocols to the fluid injection system 104, add or restore one or more fluid injection protocols to the fluid injection system 104, provide and / or receive data on user preferences for software applications, provide software to the software environment of the fluid injection system 104, provide instructions for the operation of the fluid injection system 104, provide data related to service procedures to be performed on the fluid injection system 104, and / or provide complaints regarding products such as the fluid injection system 104.

[0088] In some non-limiting embodiments, the access management system 102 may perform actions based on completing actions related to selected functions of a software application. For example, the access management system 102 may provide a GUI on the display screen of the fluid injection system 104 or workstation device 106 displaying an image (e.g., an image of a QR code®), and a user device 110 may scan the image. Based on the image scanning, the user device 110 may determine data related to selected functions of the software application, such as a report on service procedures performed on the fluid injection system 104. The user device 110 may provide the data related to selected functions of the software application to the access management system 102 via the software application. Based on receiving the data related to selected functions of the software application, the access management system 102 may cause the fluid injection system 104 to perform a start operation (e.g., a restart operation). In some non-limiting embodiments, the access management system 102 may provide a GUI on the display screen of the fluid injection system 104 or workstation device 106 that displays a second image (e.g., a second image of a QR code®), and the user device 110 may generate a secure key via a software application to scan the image and provide it to the fluid injection system 104 to perform an activation operation.

[0089] Referring here to Figures 4A and 4B, Figure 4A shows a non-limiting embodiment of a fluid injection system 400, such as a MEDRAD® Stellant FLEX CT injection system located in a CT room 4000. In some non-limiting embodiments, the fluid injection system 400 may be the same as or similar to the fluid injection system 104. As shown in Figure 4A, the fluid injection system 400 may include a branching system including a scanning room unit and its control room unit located in the scanning room 4001 and control room 4002 of the CT room 4000, respectively. In a non-limiting embodiment, the scanning room unit may include an injector head unit 401, and the control room unit may include a workstation 414, such as a Certegra® workstation having a display screen 416. As shown in Figure 4B, the injector head unit 401 may include a housing 402 and at least one fluid reservoir 404, such as a syringe or fluid pump container. In some non-limiting embodiments, the fluid injection system 400 may include drive components for controlling the flow of fluid into and out of the fluid reservoirs, such as pistons associated with each of the fluid reservoirs 404 that drive plungers 406 within the barrels of the fluid reservoirs 404, as best shown in Figure 4B. In some non-limiting embodiments, each of the fluid reservoirs 404 is adapted to interface with the housing 402 in a releasable manner at a port 408. Each fluid reservoir 404 of the fluid injection system 400 is configured to be filled with at least one medical fluid F, such as imaging contrast agent, saline solution, a combination of both contrast agent and saline solution in a desired ratio, or any other desired medical fluid. Each fluid reservoir 404 may be filled with a different medical fluid F. In some non-limiting embodiments, the fluid injection system 400 may also be a multi-syringe injector as shown, where several fluid reservoirs 404 may be oriented side by side or in a different spatial relationship and actuated separately by their respective pistons associated with the fluid injection system 400.

[0090] In some non-limiting embodiments, the fluid infusion system 400 may be used during a medical procedure to infuse at least one medical fluid F into the patient's vascular system by driving plungers 406 associated with a fluid reservoir 404 together with their respective drive components. Each drive component can move its corresponding plunger 406 toward the distal end 410 of the fluid reservoir 404 to drain the fluid F from the fluid reservoir 404 into and through the fluid pathway set 412 during priming, purging, and / or fluid delivery steps. In some non-limiting embodiments, the fluid pathway set 412 includes at least one tube or set of tubes configured to fluidize each fluid reservoir 404, and each fluid reservoir 404 can be positioned to fluidize with a flexible dosing tube and associated catheter to deliver the fluid F from each fluid reservoir 404 to the patient at a vascular access site.

[0091] Referring here to Figure 4C, Figure 4C shows another non-limiting embodiment of the fluid infusion system 400, namely a multifluid delivery system such as the MEDRAD® Centargo CT infusion system having a display screen 418. As shown in Figure 4C, the fluid infusion system 400 may be configured (e.g., adapted) to provide feedback regarding compliance with the instructions for use. In some non-limiting embodiments, the fluid infusion system 400 includes an electric fluid injector 101' connected to a fluid delivery set intended to be associated with an infusion device for delivering fluids to a patient from one or more single-dose or multi-dose containers and a fluid pathway set under pressure. In some non-limiting embodiments, the fluid injector 101' includes an injector housing 102' having opposing sides 104', a distal or upper end 106', and a proximal or lower end 108'. The injector housing 102' encloses 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 (hereinafter referred to as electronic control devices) used to control the operation of reciprocating drive components such as drive members associated with the fluid injection system 400. Such drive members may be reciprocating via electromechanical drive components such as ball screw shafts driven by motors, voice coil actuators, rack and pinion gear drives, and linear motors.

[0092] In some non-limiting embodiments, the fluid infusion system 400 may include at least one bulk fluid connector 118' for connecting to at least one bulk fluid source 120'. Alternatively, the fluid source may be a single-dose vial instead of a bulk source. In some examples, multiple bulk fluid connectors 118' may be provided. In some non-limiting embodiments, three bulk fluid connectors 118' may be provided side-by-side or in other arrangements. In some non-limiting embodiments, at least one bulk fluid connector 118' may be a spike configured to connect detachably to at least one bulk fluid source 120', such as a vial, bottle, or bag. At least one bulk fluid connector 118' may have a reusable or non-reusable interface with each new bulk fluid source 120'. At least one bulk fluid connector 118' may be formed on or attached by a tube having multiple patient disposable sets, as described herein. At least one bulk fluid source 120' may be configured to receive a medical fluid, such as saline solution, imaging contrast solution, or other medical fluid, for delivery to the fluid infusion system 400. When connected to the fluid infusion system 400, the injector housing 102' may have at least one support member 122' for supporting the at least one bulk fluid source 120'. In some non-limiting embodiments, the fluid infusion system 400 may include a connection port 128' to which a disposable patient line (not shown) is connected, allowing the medical fluid to be administered to a patient via a catheter according to a desired infusion protocol.

[0093] Referring here to Figures 5A to 5W, Figures 5A to 5W are diagrams of GUI screens that may be provided by the access management system 102 via a software application for accessing the fluid injection system 104. In some non-limiting embodiments, the GUI screens may be provided on the display screens of the fluid injection system 104, the workstation device 106, the user device 110, and / or separate systems or devices. In some non-limiting embodiments, the assets described in relation to the description of Figures 5A to 5W may refer to a fluid injection system such as the fluid injection system 104.

[0094] Referring now to Figure 5A, Figure 5A is a diagram of GUI 501 which includes fields for a user to log in to a software application to access a fluid injection system 104 operated by an access management system 102. Referring now to Figure 5B, Figure 5B is a diagram of GUI 502 which includes a list of functions of the software application for accessing the fluid injection system 104. As shown in Figure 5B, GUI 502 may provide a field 5022 for a message to the user, a field 5024 for data related to the user license, and multiple GUI elements 5026 for selecting functions of the software application.

[0095] Referring now to Figure 5C, Figure 5C is a diagram of GUI 503 for functions related to providing and / or receiving data about user preferences. As shown in Figure 5C, GUI 503 may provide a field 5032 for entering user preferences, including language selection, username for user profile, password, and data related to the service provider for service of the fluid injection system 104. Referring now to Figure 5D, Figure 5D is a diagram of GUI 504 for functions related to providing a list of assets. As shown in Figure 5D, GUI 504 may include a field 5042 having data related to each asset in the list of assets, including asset name, location, room identifier, serial number, asset tag number, coverage description, and status description. As further shown in Figure 5D, GUI 504 may provide a GUI element 5044 for selecting an asset and a GUI element 5046 for proceeding to another GUI regarding the selected asset. As further shown in Figure 5D, GUI 504 may provide a GUI element 5048 for printing the data provided in GUI 504.

[0096] Referring now to Figure 5E, Figure 5E is a diagram of GUI 505 for a function related to providing data related to the software configuration of an asset. As shown in Figure 5E, GUI 505 may include a field 5052 having data related to the software configuration of an asset, including the asset name, serial number, software version, and data related to software updates. As further shown in Figure 5E, GUI 505 may provide a GUI element 5054 for refreshing the data provided in GUI 505 and a GUI element 5056 for printing the data provided in GUI 505. Referring now to Figure 5F, Figure 5F is a diagram of GUI 506 for a function related to providing software uploads to the software environment of an asset. As shown in Figure 5F, GUI 506 may include a field 5062 having data related to software updates, including the asset name, serial number, software version, and data related to software updates. As further shown in Figure 5F, GUI 506 may provide a GUI element 5064 for proceeding to another GUI for a selected asset and a field 5066 for entering instructions regarding software updates.

[0097] Referring now to Figure 5G, Figure 5G is a diagram of GUI 507, a function related to providing a software components list (SBOM) for an asset. As shown in Figure 5G, GUI 507 may include a field 5072 having SBOM-related data, including the asset name, serial number, and data related to software updates. As further shown in Figure 5G, GUI 507 may provide a GUI element 5074 for printing the SBOM-related data provided in GUI 507. Referring now to Figure 5H, Figure 5H is a diagram of GUI 508, a function related to providing a product configuration for an asset. As shown in Figure 5H, GUI 508 may include a field 5082 having product configuration-related data, including the asset name, serial number, and data related to the asset components (e.g., part number, description, serial number, software version, and software update version). As further shown in Figure 5H, GUI 508 may provide a GUI element 5084 for printing the product configuration-related data provided in GUI 508.

[0098] Referring here to Figure 5I, Figure 5I is a diagram of GUI 509 for a function related to providing data related to one or more user licenses for an asset. As shown in Figure 5I, GUI 509 may include fields 5092 that have data related to the user license of the asset, including the asset name, and data related to the user license of the asset (e.g., license number, description, license installation date, license expiration date, and license installer identifier). As further shown in Figure 5H, GUI 509 may provide a GUI element 5094 for printing the data related to the user license of the asset provided in GUI 509.

[0099] Referring here to Figure 5J, which is a diagram of the GUI 510 for a function related to the renewal of a subscription associated with a user license for an asset function. As illustrated in Figure 5J, the GUI 510 may include a field 5102 having data related to renewing a subscription, including the username, user license number, service level agreement (SLA), whether the entitlement is active or not, the payment method for the subscription, the subscription period, and the effective date. As further shown in Figure 5J, the GUI 510 may provide a GUI element 5104 for accessing the user license agreement (ULA) and a GUI element 5106 for enabling automatic renewal of the subscription. As further shown in Figure 5J, the GUI 510 may provide a GUI element 5108 for printing the data related to the subscription renewal provided in the GUI 510.

[0100] Referring now to Figure 5K, Figure 5K is a diagram of GUI 511 for functions related to reading QR codes (e.g., QR codes displayed on a screen). As shown in Figure 5K, GUI 511 may include a field for capturing an image of a QR code (e.g., via an image capture device such as a camera on a user device such as user device 110). Referring now to Figure 5L, Figure 5L is a diagram of GUI 512 for functions related to providing and / or receiving asset-related data. As shown in Figure 5L, GUI 512 may include a field 5122 having asset-related data, including data related to an asset identifier, product name, serial number, asset tag, software version, installation date, and asset location (e.g., asset number such as facility name, facility address, room identifier of the asset location, and internal asset number used to identify the asset in the facility). As further shown in Figure 5L, GUI 512 may provide a GUI element 5124 for accessing a list of assets (e.g., via GUI 504).

[0101] Referring here to Figure 5M, which is a diagram of GUI 513 for functions related to asset registration (e.g., registering an asset in the user license asset list, registering an asset in the user profile asset list, etc.). As shown in Figure 5M, GUI 513 may include fields 5132 with asset-related data, including an asset identifier, product name, serial number, asset tag, software version, installation date, operating date, and asset number, such as facility name, facility address, room identifier of the asset location, and internal asset number used to identify the asset in the facility. As further shown in Figure 5M, GUI 513 may provide GUI elements 5134 for sending asset-related data to GUI 513 for registration procedures.

[0102] Referring here to Figure 5N, which is a diagram of the GUI 514 for a function related to adding user licenses associated with an asset. As shown in Figure 5N, the GUI 514 may include fields 5142 that have asset-related data, including an asset identifier, serial number, asset tag, user license expiration date, and data related to the asset's location (e.g., asset number such as facility name, facility address, room identifier of the asset's location, and internal asset number used to identify the asset in the facility). Further shown in Figure 5N, the GUI 514 may transmit the asset-related data provided in the GUI 514 to provide a GUI element 5144 for adding user licenses associated with the asset.

[0103] Referring here to Figure 5O, which is a diagram of GUI 515 for a function related to the deletion of user licenses associated with an asset. As shown in Figure 5O, GUI 515 may include a field 5152 having asset-related data, including an asset identifier, serial number, asset tag, user license expiration date, and data related to the asset's location (e.g., asset number such as facility name, facility address, room identifier of the asset's location, and internal asset number used to identify the asset in the facility). Further shown in Figure 5O, GUI 515 may provide a GUI element 5154 for deleting user licenses associated with an asset by transmitting the asset-related data provided in GUI 514.

[0104] Referring here to Figure 5P, Figure 5P is a diagram of GUI 516 for a function related to providing an asset with data related to consumables used during a fluid injection procedure. As shown in Figure 5P, GUI 516 may include a field 5162 having data related to the asset's consumables, including the product name and data related to the consumables available for the asset. As further shown in Figure 5P, GUI 516 may provide a GUI element 5164 for providing links to websites related to the consumables.

[0105] Referring here to Figure 5Q, which is a diagram of GUI 517 for a function related to reading error codes generated by an asset. As shown in Figure 5Q, GUI 517 can be displayed after a user device reads a QR code (registered trademark) that provides an error code. As further shown in Figure 5Q, GUI 517 may include a field 5172 having data related to the asset that generated the error code, including the product name, serial number, and asset tag. As further shown in Figure 5Q, GUI 517 may include multiple fields 5174 for entering data related to the error code, including a description of the error code, possible causes of the error code, and possible corrective actions for the error code. As further shown in Figure 5Q, GUI 517 may provide a GUI element 5176 for providing a link to training content for the asset and a GUI element 5178 for accessing asset functions related to service tools for the asset.

[0106] Referring now to Figure 5R, which is a diagram of GUI 518 for a function related to generating a service request for an asset. As shown in Figure 5R, GUI 518 may include fields 5182 that have asset-related data, including product name, serial number, asset tag, data related to the asset's location (e.g., facility name and room identifier of the asset's location), data related to the contact for the service request (e.g., personal name and telephone number), and data related to the error code generated by the asset. As further shown in Figure 5R, GUI 518 may include fields 5184 for entering data related to the asset's symptoms and the severity of the symptoms (e.g., high, medium, or low), which are the reason for the service request. As further shown in Figure 5R, GUI 518 may provide a GUI element 5186 for submitting a service request.

[0107] Referring now to Figure 5S, Figure 5S is a diagram of GUI 519 for a function related to generating confirmation of receipt of a service request for an asset. As shown in Figure 5S, GUI 519 may include fields 5192 for entering data related to the confirmation of a service request (e.g., estimated time of arrival and comments from the person confirming receipt of the service request). As further shown in Figure 5S, GUI 519 may provide a GUI element 5194 for sending a confirmation of receipt of a service request.

[0108] Referring now to Figure 5T, which is a diagram of GUI 520 for a function related to providing the status of a service request for an asset. As shown in Figure 5T, GUI 520 may include fields 5202 for entering data related to the status of a service request (e.g., an indication that the service request has been submitted, an indication that an acknowledgment of receipt of the service request has been sent, an estimated time of arrival, an indication that the service request has been completed, data related to contacting the person who has confirmed receipt of the service request, and fields for entering data related to the service request). Further shown in Figure 5T, GUI 520 may include a field 5204 for entering comments regarding the status of the service request for the asset.

[0109] Referring now to Figure 5U, which is a diagram of GUI 521 for a function related to providing product reports for assets. As shown in Figure 5U, GUI 521 may include fields 5212 for providing data related to product report notifications. In some non-limiting embodiments, GUI 521 may be generated and provided after the completion of a service request.

[0110] Referring now to Figure 5V, which is a diagram of GUI 522 of the functionality related to providing product reports for assets. As shown in Figure 5V, GUI 522 may include fields 5222 that have asset-related data, including product name, part number (e.g., master part number, material number, etc.), lot number, serial number, asset tag number, data related to the asset location (e.g., facility name and room identifier of the asset location), and data related to contacts for the product report (e.g., individual's name, title, department, telephone number, and email address). As further shown in Figure 5V, GUI 522 may provide GUI elements 5224 for submitting product reports.

[0111] Referring now to Figure 5W, Figure 5W is a diagram of GUI 523 for functions related to providing component (e.g., parts) requests for assets. As shown in Figure 5W, GUI 523 may include fields 5232 for entering data related to component requests for assets (e.g., asset identifier, asset serial number, item number, part number, description, indication of whether the component has been replaced, return serial number, and quantity indication). As further shown in Figure 5W, GUI 523 may provide GUI element 5234 for submitting component requests.

[0112] This disclosure is described in detail for illustrative purposes based on what is considered to be the most practical and preferred embodiments at present; however, such details are for that purpose only, and this disclosure is not limited to the disclosed embodiments, but rather intended to cover modifications and equivalent configurations that fall within the spirit and scope of the appended claims. For example, this disclosure is intended to allow, wherever possible, one or more aspects of any embodiment to be combined with one or more aspects of any other embodiment. [Explanation of Symbols]

[0113] 100 Environment 101' Electric fluid injector 102 Access Management System 102' Injector Housing 104 Fluid Injection System 104' Side view 106 Workstation Devices 106' Distal or upper end 108 Support System 108' Proximal or lower end 110 User Devices 112 Communication Networks 118' Bulk Fluid Connector 120' bulk fluid source 122' Support member 128' Connection Port 200 devices Bus 202 204 Processors 206 memory 208 Memory Components 210 Input Components 212 Output Components 214 Communication Interface 300 processes 400 Fluid Injection System 401 Injector Head Unit 402 Housing 404 Fluid Reservoir 406 Plunger 408 ports 410 Distal end of fluid reservoir 404 412 Fluid Path Set 414 Workstations 416 Display screen 418 Display screen Room 4000: Computed Tomography (CT) Room 4001 Scanning Room 4002 Control Room 5022 Field 5024 Field 5026 Graphical User Interface (GUI) elements 5032 Field 5042 Field 5044 GUI elements 5046 GUI elements 5048 GUI elements 5052 Field 5054 GUI elements 5056 GUI elements 5062 Field 5064 GUI elements 5066 Field 5072 Field 5074 GUI elements 5082 Field 5084 GUI elements 5092 Field 5094 GUI elements 5102 Field 5104 GUI elements 5106 GUI elements 5108 GUI elements 5122 Field 5124 GUI elements 5132 Field 5134 GUI elements 5142 Field 5144 GUI elements 5152 Field 5154 GUI elements 5162 Field 5164 GUI elements 5172 Field 5174 Field 5176 GUI elements 5178 GUI elements 5182 Field 5184 Field 5186 GUI elements 5192 Field 5194 GUI elements 5202 Field 5204 Field 5212 Field 5222 Field 5224 GUI elements 5232 Field 5234 GUI elements

Claims

1. A system for accessing a fluid injection system, Authenticate the user for access to the aforementioned fluid injection system, The data provides identification of one or more functions of a software application for accessing the fluid injection system. The software application for accessing the fluid injection system receives data identifying the selected function of the software application, This provides access to the selected function of the software application for accessing the fluid injection system. A system including at least one processor that is programmed or configured in such a way.

2. The aforementioned at least one processor is Displaying the data related to the selected function of the software application for accessing the fluid injection system via the graphical user interface (GUI) of the mobile application on the user device. The system according to claim 1, further programmed or configured as follows.

3. The aforementioned at least one processor is Based on authenticating the user for access to the fluid injection system, it is determined whether the user is authorized to access the selected function of the software application for accessing the fluid injection system. The system according to claim 1, further programmed or configured as follows.

4. When determining whether the user is authorized to access selected functions of the software application for accessing the fluid injection system, the at least one processor: Determine whether the user has an access level that authorizes the user to access the selected function of the software application for accessing the fluid injection system. The system according to claim 3, further programmed or configured as follows.

5. The fluid injection system includes a display screen, and the at least one processor is Data related to the fluid injection system is displayed on the display screen of the fluid injection system. The system according to claim 1, further programmed or configured as follows.

6. The aforementioned at least one processor is To provide data related to the fluid injection system, the selected function of the software application of the fluid injection system is accessed, and the data related to the fluid injection system includes data related to one or more operations of the fluid injection system. Further programmed or configured as follows: The aforementioned at least one processor is The data related to one or more operations of the fluid injection system is recorded. The system according to claim 1, further programmed or configured as follows.

7. When providing access to the selected function of the software application for accessing the fluid injection system, the at least one processor, Based on determining that the user is authorized to access the selected function of the software application, access to the selected function of the software application for accessing the fluid injection system is provided. The system according to claim 1, programmed or configured as such.

8. A computer program product for accessing a fluid injection system, wherein the computer program product, when executed by at least one processor, provides to the at least one processor, The user is authenticated to access the aforementioned fluid injection system. To provide data that identifies one or more functions of a software application for accessing the fluid injection system, The system receives data identifying the selected function of the software application of the fluid injection system. To provide access to the selected function of the software application of the fluid injection system, A computer program product comprising at least one non-temporary computer-readable medium containing one or more instructions.

9. The one or more instructions further provide to the at least one processor: To display data related to the selected function of the software application of the fluid injection system via the graphical user interface (GUI) of a mobile application on a user device, The computer program product according to claim 8.

10. The one or more instructions further provide to the at least one processor: Based on authenticating the user for access to the fluid injection system, it is determined whether the user is authorized to access the selected function of the software application of the fluid injection system. The computer program product according to claim 8.

11. The one or more instructions that cause the at least one processor to determine whether the user is authorized to access the selected function of the software application for accessing the fluid injection system further cause the at least one processor to: The system determines whether the user has an access level that authenticates the user's access to the selected function of the software application for accessing the fluid injection system. The computer program product according to claim 10.

12. The fluid injection system includes a display screen, and the one or more instructions further provide to the at least one processor, The data related to the fluid injection system is displayed on the display screen of the fluid injection system. The computer program product according to claim 8.

13. The one or more instructions further provide to the at least one processor: To provide data related to the fluid injection system, the selected function of the software application for accessing the fluid injection system is accessed, and the data related to the fluid injection system includes data related to one or more operations of the fluid injection system. The one or more instructions further provide to the at least one processor: To record the data related to one or more operations of the fluid injection system, The computer program product according to claim 8.

14. The one or more instructions that cause the at least one processor to provide access to the selected function of the software application for accessing the fluid injection system further cause the at least one processor to: Based on determining that the user is authorized to access the selected function of the software application for accessing the fluid injection system, access to the selected function of the software application for accessing the fluid injection system is provided. The computer program product according to claim 8.

15. A method for accessing a fluid injection system, A step of authenticating a user for access to the fluid injection system using at least one processor, The steps include using at least one processor to provide data identifying one or more functions of a software application for accessing the fluid injection system, The steps include: using at least one processor to receive data identifying selected functions of the software application for accessing the fluid injection system; The steps include: providing access to the selected function of the software application for accessing the fluid injection system using the at least one processor; Methods that include...

16. The step of displaying data related to the selected function of the software application of the fluid injection system via the graphical user interface (GUI) of a mobile application on a user device. The method according to claim 15, further comprising:

17. A step of determining whether the user is authorized to access the selected function of the software application for accessing the fluid injection system, based on the step of authenticating the user for accessing the fluid injection system. The method according to claim 15, further comprising:

18. The step of determining whether the user is authorized to access the selected function of the software application for accessing the fluid injection system is: The step of determining whether the user has an access level that authorizes the user to access the selected function of the software application for accessing the fluid injection system. The method according to claim 17, including the method described in claim 17.

19. The fluid injection system includes a display screen, and the method is, The step of displaying data related to the fluid injection system on the display screen of the fluid injection system. The method according to claim 15, further comprising:

20. A step of accessing the selected function of the software application for accessing the fluid injection system in order to provide data related to the fluid injection system, wherein the data related to the fluid injection system includes data related to one or more operations of the fluid injection system. It further includes, The aforementioned method, A step of recording the data related to one or more operations of the fluid injection system. The method according to claim 15, further comprising:

21. The step of providing access to the selected function of the software application for accessing the fluid injection system is: A step of determining that the user is authorized to access the selected function of the software application, and then providing access to the selected function of the software application for accessing the fluid injection system. The method according to claim 15, including the method described in claim 15.

Images