Systems, methods, and computer program products for providing access to a fluid infusion system

Abstract

A system for securely accessing a fluid injection system is disclosed, the system including at least one processor programmed or configured to: authenticate a user for access to the fluid injection system, provide data identifying one or more features of a software application for accessing the fluid injection system, receive data identifying selected features of the software application for accessing the fluid injection system, and provide access to the selected features of the software application for accessing the fluid injection system.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 63 / 088,343, filed October 6, 2020, the entire disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates generally to systems, devices, products, apparatus, and methods for providing access to electronic devices, and in one particular embodiment, to systems, products, and methods for safely accessing fluid injection systems. [Background technology]

[0003] Injection devices, such as fluid injection devices (e.g., medical fluid delivery devices), can be used by medical practitioners, such as physicians, in medical diagnostic and / or therapeutic procedures. For example, a medical practitioner can use a fluid injection device to inject one or more medical fluids into a patient. Fluid injection devices can be used for pressurized injection of medical fluids, such as radiocontrast materials (e.g., contrast agents, radiographic contrast media, contrast media, etc.), and / or flushing agents, such as saline, in medical imaging procedures, such as angiography, computed tomography (CT), ultrasound, magnetic resonance imaging (MRI), and positron emission tomography (PET). In some cases, fluid injection devices are designed to deliver a preset amount of medical fluid at a preset flow rate.

[0004] In some cases, access to the infusion device's software may be provided via a hardware key (e.g., dongle, software protection dongle, software protection key, etc.), such as a Hardware Anti-Software Piracy (HASP) key. The hardware key may be an electronic copy and software content protection device. When connected to the infusion device, the hardware key can be used to unlock software functionality and / or decrypt content. The hardware key may include (e.g., be programmed with) a product key (e.g., a software key) and / or other cryptographic protection mechanisms and may enable access to the infusion device's software when the hardware key is connected to an electrical connector, such as a Universal Serial Bus (USB) connector, of the infusion device. Summary of the Invention [Means for solving the problem]

[0005] Thus, there is provided a system, device, product, apparatus, and / or method for securely accessing a fluid injection system that improves 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, the system including 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.

[0008] Clause 2: The system described in Clause 1, wherein at least one processor is further programmed or configured to display data related to selected functions of the software application for accessing the fluid injection system via a graphical user interface (GUI) of the mobile application on the 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 the user is authorized to access selected features of the software application for accessing the fluid injection system based on authenticating the user for access to the fluid injection system.

[0010] Clause 4: A system described in any one of clauses 1 to 3, wherein when determining whether a user is authorized to access selected features of a software application for accessing a 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 selected features of the software application for accessing a fluid injection system.

[0011] Clause 5: A system described in any one of clauses 1 to 4, wherein the fluid injection system includes a display screen, and the 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.

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

[0013] Clause 7: A system described in any one of clauses 1 to 6, wherein when 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 the selected functions of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected functions of the software application.

[0014] Clause 8: A computer program product for accessing a fluid injection system, the computer program product including at least one non-transitory computer-readable medium containing one or more instructions that, when executed by at least one processor, cause the 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 of the fluid injection system, and provide access to the selected functions of the software application of the fluid injection system.

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

[0016] Clause 10: The computer program product of clause 8 or 9, wherein the one or more instructions further cause at least one processor to determine whether the user is authorized to access selected functions of the software application of 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 the one or more instructions that cause at least one processor to determine whether a user is authorized to access selected features of a software application for accessing a fluid injection system further cause the at least one processor to determine whether the user has an access level that authorizes the user to access selected features of a software application for accessing a fluid injection system.

[0018] Clause 12: A computer program product described in any one of clauses 8 to 11, wherein the fluid injection system includes a display screen, and the 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 the one or more instructions further cause the at least one processor to access selected functions of the software application for accessing the fluid injection system 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, and wherein the one or more instructions further cause the at least one processor to record the data related to the 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 the one or more instructions that cause at least one processor to provide access to selected features of the software application for accessing the fluid injection system further cause the at least one processor to provide access to the selected features of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected features of the software application for accessing the fluid injection system.

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

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

[0023] Clause 17: The method described in 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 the step of authenticating the user for access to the fluid injection system.

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

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

[0026] Clause 20: A method according to any one of clauses 15 to 19, further comprising the step of accessing a selected function of a software application for accessing a fluid injection system 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 comprises the step of recording the data relating to one or more operations of the fluid injection system.

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

[0028] These and other features of the present disclosure, as well as the method of operation and function of the associated elements of structure, and the combination of parts and economies of manufacture, will become more apparent from a consideration of the following description and appended claims, taken in conjunction with the accompanying drawings, all of which form a part hereof, and in which like reference numerals indicate corresponding parts in the various drawings. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the present disclosure. As used in this specification and the 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 explained in more detail below with reference to exemplary embodiments shown in the accompanying schematic drawings. [Brief explanation of the drawings]

[0030] [Figure 1] FIG. 1 is a diagram of a non-limiting embodiment of an environment in which the systems, devices, products, apparatus, and / or methods described herein may be implemented in accordance with the principles of the present disclosure. [Figure 2] FIG. 2 is a diagram of a non-limiting embodiment of components of one or more systems or one or more devices of FIG. 1. [Figure 3] 1 is a flow chart of a non-limiting embodiment of a process for safely accessing a fluid injection system. [Figure 4A] FIG. 1 illustrates a non-limiting example of an imaging suite and a non-limiting embodiment of a fluid injection system therein. [Figure 4B] 4B illustrates an injector head unit of the fluid injection system shown in FIG. 4A. [Figure 4C] FIG. 1 illustrates another non-limiting embodiment of a fluid injection system. [Figure 5A] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5B] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5C] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5D] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5E] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5F] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5G] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5H] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5I] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5J]1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5K] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5L] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5M] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5N] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5O] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5P] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5Q] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5R] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5S] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5T]1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5U] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5V] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. [Figure 5W] 1A-1C are diagrams of non-limiting embodiments of graphical user interfaces (GUIs) displayed during a process for securely accessing a fluid injection system. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0033] As used herein, the terms “communication” and “communicating” can refer to receiving, accepting, sending, forwarding, and / or providing information (e.g., data, signals, messages, instructions, commands, etc.). One unit (e.g., a device, a system, a component of a device or system, a combination thereof, and / or the like) communicating with another unit means that one unit can directly or indirectly receive information from the other unit and / or transmit information to the other unit. This can refer to a direct or indirect connection that is wired and / or wireless in nature. 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, a first unit can communicate with a second unit even if the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may communicate with a second unit if at least one intermediate unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and communicates the processed information to the second unit. In some non-limiting embodiments, a message may refer to a network packet containing data (e.g., a data packet, etc.). 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, such as, but not limited to, a processor, a server, a client device, a software application, and / or other similar components. Additionally, references to a "server" or a "processor" as used herein can refer to a previously listed server and / or processor, a different server and / or processor, and / or a combination of servers and / or processors listed as performing a previous step or function. For example, as used herein and in the claims, a first server and / or a first processor listed as performing a first step or function can refer to the same or a different server and / or processor listed as performing a second step or function.

[0035] In some cases, the fluid infusion device may be part of a group of devices used in a medical treatment facility, such as a hospital, during patient treatment. An individual, such as a technician (e.g., a field service engineer), administrator, or other person appropriately trained in the operation of the fluid infusion device, can access the software of the fluid infusion device via the hardware key. In some examples, the individual can access service-related software tools via the hardware key. In one example, the fluid infusion device may malfunction during a fluid infusion operation, and the individual can obtain information about the malfunction by connecting the hardware key to the fluid infusion device and downloading a report containing the information. Additionally, the individual can install software updates to the fluid infusion device, including product enhancements, operating system updates, and / or security updates (e.g., security patches), for example, via the use of the hardware key.

[0036] However, an individual may be required to possess a hardware key to access the fluid infusion device, and the physical nature of the hardware key lends itself to the possibility of loss, damage, and / or theft. Furthermore, multiple hardware keys may be associated with a particular fluid infusion device, with more than one key being required to access all of the software functionality of that fluid infusion device. Furthermore, the product key associated with the hardware key may expire following the term of the user license, and as part of the user license renewal process, the operator of the fluid infusion device may be required to obtain and provide identification information for the fluid infusion device. The process of obtaining and providing identification information for the fluid infusion device may be resource- and labor-intensive on the operator's behalf. Similarly, when components of a fluid infusion 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 functionality of the fluid infusion device.

[0037] Non-limiting embodiments of the present disclosure relate to systems, devices, products, apparatus, and / or methods for securely accessing a fluid injection system. In some non-limiting embodiments, the access control 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 features of a software application for accessing the fluid injection system, receive data identifying selected features of the software application for accessing the fluid injection system, and provide access to the selected features 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 related to the selected features of the software application for accessing the fluid injection system via a graphical user interface (GUI) of a mobile application on the user device. In some non-limiting embodiments, the at least one processor is further programmed or configured to determine whether the user is authorized to access the selected features of the software application for accessing the fluid injection system based on authenticating the user for access to the fluid injection system. In some non-limiting embodiments, when determining whether the user is authorized to access the selected features 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 features 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 the at least one processor is further programmed or configured to cause data related to the fluid injection system to be displayed on the display screen of the fluid injection system. In some non-limiting embodiments, the at least one processor is further programmed or configured to access selected features of a software application of the fluid injection system to provide data related to the fluid injection system, the data related to the fluid injection system including data related to one or more operations of the fluid injection system, and the at least one processor is further programmed or configured to record the data related to the one or more operations of the fluid injection system. In some non-limiting embodiments, when providing access to the selected features of the software application for accessing the fluid injection system, the at least one processor is programmed or configured to provide access to the selected features of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected features of the software application.

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

[0040] 1, which is a diagram of an exemplary environment 100 in which the devices, systems, and / or methods described herein may be implemented. As shown in FIG. 1, the environment 100 includes an access management system 102, a fluid infusion 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 infusion system 104, the workstation device 106, the support system 108, and / or the user device 110 may be interconnected (e.g., establish a connection to communicate) via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection.

[0041] In some non-limiting embodiments, the access management system 102 includes one or more devices that can communicate with the fluid infusion system 104, the workstation device 106, the support system 108, and / or the user device 110 via a communication network 112. For example, the access management system 102 can 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 can be a component of the fluid infusion system 104 and / or the workstation device 106.

[0042] In some non-limiting embodiments, the fluid injection system 104 includes one or more devices capable of communicating with the access management system 102, the workstation device 106, the support system 108, and / or the user device 110 via the communication network 112. For example, the fluid injection system 104 can 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 injection system 104 includes one or more injection devices (e.g., one or more fluid injection devices). In some non-limiting embodiments, the fluid injection system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid containing a contrast agent to the patient and / or administer an aqueous fluid, such as saline, to the patient before, during, and / or after administration of the contrast fluid. For example, the fluid injection system 104 can inject one or more prescribed doses of contrast fluid directly into the patient's bloodstream via a hypodermic needle and syringe. In some non-limiting embodiments, the fluid injection system 104 may be configured to continuously administer an aqueous fluid to the patient through a peripheral intravenous line (PIV) and a 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 injection system 104 is configured to inject a dose of contrast fluid followed by a specific volume of aqueous fluid. In some non-limiting embodiments, the fluid injection system 104 may include a device capable of reading (e.g., scanning) a barcode, such as a quick response (QR) code.

[0043] In certain non-limiting embodiments, the fluid injection system 104 may include one or more exemplary injection systems or injectors, such as those described in U.S. patent application Ser. No. 09 / 715,330, filed Nov. 17, 2000, and issued as U.S. Patent No. 6,643,537; U.S. patent application Ser. No. 09 / 982,518, filed Oct. 18, 2001, and issued as U.S. Patent No. 7,094,216; U.S. patent application Ser. No. 09 / 982,518, filed Apr. 16, 2004, and issued as U.S. Patent No. 7,556,619; No. 10 / 825,866, U.S. patent application Ser. No. 12 / 437,011, filed May 7, 2009, issued as U.S. Patent No. 8,337,456, U.S. patent application Ser. No. 12 / 476,513, filed June 2, 2009, issued as U.S. Patent No. 8,147,464, and U.S. patent application Ser. No. 11 / 004,670, filed December 3, 2004, issued as U.S. Patent No. 8,540,698, the disclosures of each of which are incorporated herein by reference in their entirety. In some non-limiting embodiments, the fluid injection system 104 may include a MEDRAD® Stellant CT injection system, a MEDRAD® Stellant FLEX CT injection system, a MEDRAD® Spectris Solaris EP MR injection system, a MEDRAD® MRXperion MR injection system, a MEDRAD® Salient contrast injection system, a MEDRAD® Mark 7 Arterion injection system, a MEDRAD® Avanta fluid management injection system, a MEDRAD® Intego PET injection system, or a MEDRAD® Centargo CT injection system, all of which are provided by Bayer.

[0044] In some non-limiting embodiments, the workstation device 106 includes one or more devices capable of communicating with the access control system 102, the fluid injection system 104, the support system 108, and / or the user devices 110 via the communications network 112. For example, the workstation device 106 may include one or more computing devices, such as computers, including desktop computers, laptops, tablets, and the like. 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 operating parameters of the fluid injection system 104 during operation (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, support system 108 may include one or more devices capable of communicating with access management system 102, fluid infusion system 104, workstation device 106, and / or user device 110 via communication network 112. For example, support system 108 may include computing devices such as a computer, a server (e.g., a web server), a group of servers, and / or other similar devices. In some non-limiting embodiments, support system 108 may include back-end systems associated with access management system 102, fluid infusion system 104, and / or workstation device 106. In some non-limiting embodiments, support system 108 may include a cloud computing system that stores data in associated databases. In some non-limiting embodiments, support system 108 may interact with fluid infusion system 104 to provide functionality such as remote equipment services for fluid infusion system 104 (e.g., VirtualCARE® remote equipment support services are for infusion systems and devices provided by Bayer). In certain non-limiting embodiments, the support system 108 may be operated by or on behalf of an original equipment manufacturer (OEM) of the fluid injection system 104 (e.g., an OEM of one or more components or devices of the fluid injection system 104), a provider of the fluid injection system 104, an imaging site or hospital where the fluid injection system 104 operates, and / or a service technician assigned to the fluid injection system 104, etc. In certain non-limiting embodiments, the support system 108 may include a hospital information system (HIS), a radiology information system (RIS), etc. In certain 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 capable of communicating with the access management system 102, the fluid infusion 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, a laptop, etc.) or a mobile device (e.g., a smartphone, a tablet, etc.). In some non-limiting embodiments, the user device 110 may be capable of reading (e.g., scanning) a barcode, such as a quick response (QR) code. In some non-limiting embodiments, the user device 110 may be configured to transmit and / or receive data from another device or system (e.g., the fluid infusion system 104, the workstation device 106) via a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, and / or the like). 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 examples, 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 (e.g., installed and / or executed on) user device 110 (e.g., applications stored on user device 110, such as mobile device applications, native applications for the mobile device, mobile cloud applications for the mobile device, etc.).

[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 a cellular network (e.g., a long-term evolution (LTE) network, a third-generation (3G) network, a fourth-generation (4G) network, a fifth-generation (5G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, a cloud computing network, a short-range wireless communication network (e.g., a Bluetooth network, a near field communication (NFC) network, etc.), etc., and / or a combination 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, different systems and / or devices than those shown in Figure 1, and / or different arrangements of systems and / or devices may be present. Furthermore, two or more systems or devices shown in Figure 1 may be implemented within a single system or device, or a single system or device shown in Figure 1 may be implemented as multiple distributed systems or devices. Additionally or alternatively, a set of systems or devices (e.g., one or more systems, one or more devices, etc.) of environment 100 may perform one or more functions described as being performed by another set of systems or another set of devices of environment 100.

[0049] 2, which is a diagram of exemplary components of a device 200. The 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, the workstation device 106, one or more devices of the support system 108, and / or the 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 the device 200. As shown in FIG. 2, the 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, processor 204 may be implemented in hardware, software, or a combination of hardware and software. For example, processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.). Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by processor 204.

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

[0052] Input components 210 may include components that enable device 200 to receive information via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally or alternatively, input components 210 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output components 212 may include components that provide output information from device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

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

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

[0055] Software instructions may be loaded into memory 206 and / or storage component 208 from another computer-readable medium or from another device via communications interface 214. When executed, the software instructions stored in memory 206 and / or storage component 208 can cause processor 204 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry can be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry 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, fewer, different, or differently arranged components than those shown in Figure 2. Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

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

[0058] Aspects of non-limiting embodiments herein (e.g., one or more of the steps of process 300) may be performed in connection with a software application, such as a mobile application having a client-side component 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 infusion 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 on the fluid infusion system 104 and / or the workstation device 106. In some non-limiting embodiments, one or more functions of the software application may provide access to one or more functions of the software environment of the fluid infusion 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 a modality worklist, a system for providing patient demographic information for fluid injection procedures and / or medical imaging procedures, etc.), 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] 3 , at step 302, the process 300 includes authenticating a user for access to the fluid injection system. For example, the access management system 102 can authenticate a 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 can authenticate a user for access to the fluid injection system 104 via a software application independent of (e.g., without) a hardware key. In some non-limiting embodiments, the access management system 102 can receive data related to user identification from a 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 a login process, and the access management system 102 can use the data related to user identification to authenticate 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 can generate a graphical user interface (GUI) and provide the GUI for display on the user device 110 to receive user input as part of the login process. The user input may include login credentials. In some non-limiting embodiments, the login credentials may include data related to a user identity, such as data identifying a username, a password, an employee identification number, a device identifier (e.g., an Internet Protocol (IP) address, a Media Access Control (MAC) address, etc.), a telephone number, an office location, and / or an office address, etc. In some non-limiting embodiments, the login credentials may include a biometric measurement of the user (e.g., a fingerprint, an iris scan, an image of a body part of the user, etc.).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 the access management system 102 can determine, based on the user's authentication, 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 infusion system 104 to authenticate a user for access to the fluid infusion system 104. For example, the access management system 102 can generate the login credentials (e.g., password, passcode, etc.) based on a clock (e.g., an internal clock of the user device 110). In some non-limiting embodiments, the access management system 102 can provide a GUI to the fluid infusion system 104 or the workstation device 106 (e.g., on a display screen of the fluid infusion system 104 or the workstation device 106) to display an indicator, and the access management system 102 can receive login credentials associated with the indicator 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 infusion system 104 or the workstation device 106 that displays 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 login credentials associated with the image, and the user device 110 can provide the login credentials to access the management system 102 via the software application. The access management system 102 can authenticate a user for access to the fluid injection system 104 based on receiving login credentials via a software application. In some non-limiting embodiments, the access management system 102 can provide a GUI to the user device 110 for displaying an indicator, and the access management system 102 can receive login credentials associated with the indicator from the fluid injection system 104 via the software application. For example, the access management system 102 can provide a GUI on a 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 the image, and the fluid injection system 104 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 the login credentials via the software application.

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

[0063] In some non-limiting embodiments, features (e.g., services, tools, etc.) of a software application for accessing the fluid injection system 104 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 obtain 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 obtain data related to a user profile, and / or data related to a user license (e.g., a software license for a user), etc.

[0064] In some examples, the data associated with the fluid injection system 104 may include data related to an identifier of the fluid injection system 104 (e.g., a device identifier of the fluid injection system 104, a model number of the fluid injection system 104, a serial number of the fluid injection system 104, etc.), data related to the software or hardware of the fluid injection system 104 (e.g., the software configuration of the fluid injection system 104, the hardware configuration of the fluid injection system 104, a software version of the fluid injection system 104, such as the software version of the operating system of the fluid injection system 104, the software revision number of the fluid injection system 104, identifiers of one or more software patches applied to the fluid injection system 104, etc.), and / or data related to the network connection of the fluid injection system 104 (e.g., a MAC address of a network interface controller (NIC) of the fluid injection system 104, an IP address of the fluid injection system 104, etc.). In some non-limiting embodiments, the data associated with the fluid injection system 104 may include data related to one or more operations of the fluid injection system 104. The data related to one or more operations of the fluid injection system 104 may include data related 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, operating parameters of the fluid injection operations performed by the fluid injection system 104, data related to patient demographics of patients on whom the fluid injection operations were performed by the fluid injection system 104, etc.), data related to the configuration of the fluid injection system 104 (e.g., the configuration of fluid delivery components of the fluid injection system 104, a Cybersecurity Component Table (CBOM) of the fluid injection system 104, a Software Component Table (SBOM) of the fluid injection system 104, etc.), and / or data related to malfunctions encountered during one or more operations of the fluid injection system 104. In some non-limiting embodiments, the access control system 102 may log (e.g., store in a data log) data related to the fluid injection system 104.For example, the access control system 102 may record data related to one or more operations of the fluid infusion system 104. It should be noted that because embodiments of the present disclosure comply with all legal requirements, e.g., the Health Insurance Portability and Accountability Act (HIPAA), data related to the fluid infusion system 104 that is stored or communicated may not properly include patient personal health information, such as PHI and PII.

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

[0066] In certain non-limiting embodiments, data related to a malfunction encountered during one or more operations of the fluid injection system 104 may include an identifier of an error associated with the operation of the fluid injection system 104. The identifier of the error associated with the operation of the fluid injection system 104 may include an error code (e.g., a specific error code associated with the type of malfunction that occurred). Additionally or alternatively, data related to an anomaly encountered during one or more operations of the fluid injection system 104 may include an operating parameter of the fluid injection system 104 associated with the anomaly. For example, data related to a malfunction 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 associated with components used with the fluid injection system 104 (e.g., a disposable set, e.g., a multiple use disposable set (MUDS), a single use disposable set (SUDS), a syringe or tubing set), measurements of electrical characteristics (e.g., voltage, current, power, etc.) of electrical components of the fluid injection system 104, and / or other related values ​​of variables and / or system components.

[0067] In some non-limiting embodiments, the functionality of the software application for accessing the fluid injection system 104 includes functionality related to obtaining (e.g., reading, scanning, retrieving from a data structure, etc.) data related to error codes of the fluid injection system 104 (e.g., error codes generated by the fluid injection system 104), functionality related to determining the location of the fluid injection system 104 (e.g., location based on a Global Positioning System (GPS) location), functionality related to generating a service history of the fluid injection system 104, functionality related to providing the service history of the fluid injection system 104 (e.g., providing for downloading, displaying, printing, sending, etc., a message including the service history), functionality 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.), functionality related to adding an asset to the list of assets, functionality related to providing a list of the functionality of the software environment of the fluid injection system 104 that is covered by a user license ... functionality related to initiating billing (e.g., automatic billing) for one or more features of the software environment of the fluid injection system 104 that are covered by the license; functionality related to adding one or more features of the software environment of the fluid injection system 104 to a user license (e.g., VirtualCARE® Remote Support, which enables safe and reliable remote monitoring of the contrast injection system and software to minimize downtime; equipment support services such as SelectCARE®, PartnerCARE®, and DirectCARE® service contract programs that provide a high level of service and capabilities, including VirtualCARE®; TechCARE®, Bayer's TechCARE® NxT non-obsolescence program, which also includes services and capabilities offered through its service contract programs); functionality related to generating service requests for the fluid injection system 104; functionality related to registering a warranty;functionality related to providing data related to a fluid injection system 104 (e.g., a single-use disposable set (SUDS), syringe, or tubing set); functionality related to providing a list of one or more fluid injection protocols to the fluid injection system 104; functionality related to adding or restoring one or more fluid injection protocols to the fluid injection system 104 (e.g., restoring pursuant to a service procedure); functionality related to providing and / or receiving data regarding user preferences (e.g., user preferences related to the look and feel of the software application, such as the display color and / or language of the data provided); functionality related to providing software for the software environment of the fluid injection system 104 (e.g., providing an operating system); 104, functionality related to providing instructions for operation of the fluid injection system 104, functionality related to providing data related to a service procedure to be performed on the fluid injection system 104 (e.g., data related to diagnostic and / or troubleshooting capabilities for the service procedure, such as augmented reality (AR) capabilities for the service procedure, real-time data related to aspects of components of the fluid injection system 104, such as calibration values, fluid, battery, motor, etc.), functionality related to providing data related to a service procedure performed on the fluid injection system 104 (e.g., a service report based on the service procedure, a final checklist following the service procedure, a message including confirmation of completion of the service procedure, etc.), and / or functionality related to providing product complaints.

[0068] In some non-limiting embodiments, the functionality associated with providing a list of assets may include functionality associated with providing a list of assets associated with a user license. In some non-limiting embodiments, the functionality may provide a list of assets associated with a user license provided according to an encryption protocol. In some non-limiting embodiments, the list of assets may include identifiers of scan 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 a report (e.g., a service report) associated with the list of assets associated with the user license (e.g., a report including data associated with each asset in the list of assets, one or more assets in the list of assets, etc.) (e.g., provide for downloading, displaying, printing, sending, etc. a message including the report). In some non-limiting embodiments, the functionality may provide for sending a report to a system external to the fluid injection system 104 (e.g., a service management system, a flight recorder system, etc.). In some non-limiting embodiments, the functionality can provide data related to each asset, including software configuration (e.g., current software level), calibration date (e.g., last calibration date, all calibration dates, etc.), the user who performed the calibration, and the aspect of the asset that was calibrated (e.g., pressure, potentiometer, etc.).

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

[0070] In some non-limiting embodiments, functionality related to determining the location of the fluid injection system 104 may provide for 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) sent 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 in to a computer system, a website, an account, a software platform, a network (e.g., a local network), an intranet, etc. For example, a user may log in to the access management system 102 via a mobile application on the user device 110. In some non-limiting embodiments, the access management system 102 may receive a login request 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 the user based on the data related to the user identification information as part of the login process. For example, the login request may include data related to user identification, and the access management system 102 may authenticate the user using all or a portion of the data related to the user identification. In some non-limiting embodiments, the access management system 102 may authenticate the user using a multi-factor authentication process. For example, the access management system 102 may use data related to the user identification information and additional data received from the user device 110 during the login process to authenticate the user.

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

[0073] In some non-limiting embodiments, the access management system 102 can authenticate a user based on data associated with an identifier of the fluid injection system 104. For example, the access management system 102 can obtain data associated with an identifier of the fluid injection system 104 and use the data associated with the user identification and the data associated with 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 can authenticate a user based on determining 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 authenticate a user based on determining 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 the user device 110. For example, the user can use the user device 110 to scan an indicator, such as a code (e.g., a barcode such as a quick response (QR) code) associated with the fluid infusion system 104, and the access management system 102 can receive data associated with the indicator from the user device 110, such as data associated with an identifier for the fluid infusion system 104 and data associated with a user identification of the user. The access management system 102 can authenticate the user based on the data associated with the identifier for the fluid infusion system 104 and data associated with a user identification of the user. In some non-limiting embodiments, the access management system 102 can include one or more aspects of a QR code system and / or other devices and systems, as disclosed in International Patent Application No. PCT / US2021 / 032659, filed May 17, 2021, the disclosure of which is incorporated herein by reference in its entirety.

[0075] In some non-limiting embodiments, the access management system 102 can authenticate a user without a connection to the communications 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 communications connection to the communications network 112 is unavailable. In some non-limiting embodiments, the access management system 102 can determine that a connection to the communications network 112 is unavailable to the user device 110 via the software application, and the access management system 102 can authenticate a user when a connection to the communications network 112 is available. For example, the access management system 102 can determine that a connection to the communications network 112 is unavailable, and the access management system 102 can periodically attempt to establish a communications connection to the communications network 112. The access management system 102 can authenticate a user when the access management system 102 determines that a connection to the communications network 112 is available via the software application.

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

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

[0078] In some non-limiting embodiments, the access management system 102 can obtain data related to user identification to determine that a user is authenticated for access to a software application of the fluid injection system 104. For example, a user can 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 can determine the user's identity based on the device identifier. The access management system 102 can determine that the user's identity 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 can obtain data related to user identification as part of or following a login process.

[0079] In some non-limiting embodiments, the access management system 102 can facilitate communication between a user's user device 110 and the fluid infusion system 104. For example, the access management system 102 can establish a short-range wireless communication connection (e.g., a Bluetooth® communication connection, a near field communication (NFC) communication connection, etc.) between the user device 110 and the fluid infusion system 104. In another example, the access management system 102 can establish a wired communication connection between the user device 110 and the fluid infusion system 104 (e.g., using a universal serial bus (USB) port on each of the user device 110 and the fluid infusion system 104). In some non-limiting embodiments, the access management system 102 can facilitate communication between a user's user device 110 and the fluid infusion 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 provide data related to the fluid infusion system 104 via the software application using the communication connection between the user device 110 and the fluid infusion system 104. In some non-limiting embodiments, the access control system 102 can communicate (e.g., via a software application) with a medical imaging system, a fluid injection system service and control system, a hospital information system, a radiology information system, a service management system (e.g., ServiceMax, SAP Mobile, etc.), and / or a web server (e.g., a web server associated with a software application). In some non-limiting embodiments, the access control system 102 can communicate with a gateway device, one or more systems, and / or one or more applications disclosed in International Patent Application No. PCT / US2021 / 040800, filed July 8, 2021, the disclosure of which is incorporated herein by reference in its entirety.

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

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

[0082] 3, in step 306, process 300 includes receiving data identifying selected features of a software application for accessing a fluid injection system. For example, access control system 102 may receive data identifying selected features of a software application for accessing fluid injection system 104.

[0083] In some non-limiting embodiments, the access management system 102 can receive data identifying a selected function of one or more functions of a software application for accessing the fluid injection system 104 based on a user's input to a GUI provided via the user device 110. In some non-limiting embodiments, the access management system 102 can receive information related to a user's selection of a GUI element displayed by the GUI on the screen of the user device 110. For example, based on the user device 110 detecting user interaction with the GUI, the user device 110 can provide an indication of the user selection to the access management system 102. The GUI element can correspond to a selected function of the one or more functions for which identification data was provided via the GUI on the screen of the user device 110.

[0084] In some non-limiting embodiments, the access management system 102 can receive a request for access to a selected function based on a selection of a function from among a plurality of functions. For example, the access management system 102 can receive a request for access to a selected function based on a user selecting a GUI element corresponding to the function in a GUI on the user device 110. In some non-limiting embodiments, the access management system 102 can provide a prompt 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 can request the user to provide data relevant to the user that has not previously been received and that is useful for determining whether to provide access to the selected function.

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

[0086] In some non-limiting embodiments, the access management system 102 can provide access to selected features 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 can determine that a connection to the communication network 112 is unavailable, and the access management system 102 can attempt to establish a communication connection (e.g., a short-range wireless communication connection) between the user device 110 and the fluid injection system 104. The access management system 102 can provide access to selected features 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 can provide access to selected features 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 serviced (e.g., removed and / or replaced).

[0087] In some non-limiting embodiments, the access management system 102 can perform operations related to selected features of a 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 features of a software application for accessing the fluid injection system 104. In particular examples, the access management system 102 can scan for error codes in the fluid injection system 104, generate a service history for the fluid injection system 104, provide a service history for the fluid injection system 104, provide a list of assets, add assets to the list of assets, provide a list of features of the software environment of the fluid injection system 104 that are covered by a user license, initiate a billing procedure for one or more features of the software environment of the fluid injection system 104 that are covered by a user license, add one or more features 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 issue a warranty. The fluid injection system 104 may register, provide data regarding consumables used during a fluid injection procedure, 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 regarding user preferences for the software application, provide software to the software environment of the fluid injection system 104, provide instructions for 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 can perform an action based on completing an action associated with a selected function of a software application. For example, the access management system 102 can provide a GUI on a display screen of the fluid injection system 104 or workstation device 106 that displays an image (e.g., an image of a QR code (registered trademark, see below)), and the user device 110 can scan the image. Based on the scanning of the image, the user device 110 can determine data associated with the selected function of the software application, such as a report on a service procedure performed on the fluid injection system 104. The user device 110 can provide the data associated with the selected function of the software application to the access management system 102 via the software application. Based on receiving the data associated with the selected function of the software application, the access management system 102 can cause the fluid injection system 104 to perform an initiation action (e.g., a restart operation). In some non-limiting embodiments, the access control system 102 can provide a GUI on a 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 can scan the image and generate a secure key via a software application to provide to the fluid injection system 104 to cause the fluid injection system 104 to perform an activation operation.

[0089] 4A and 4B, FIG. 4A illustrates a non-limiting embodiment of a fluid injection system 400, such as a MEDRAD® Stellant FLEX CT injection system, disposed in a CT suite 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 FIG. 4A, the fluid injection system 400 may include a branched system including a scan room unit and a control room unit disposed in a scan room 4001 and a control room 4002, respectively, of the CT suite 4000. In a non-limiting embodiment, the scan 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 FIG. 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 a piston associated with each of the fluid reservoirs 404 that drives a plunger 406 within the barrel of the fluid reservoir 404, as best shown in FIG. 4B . In some non-limiting embodiments, each of the fluid reservoirs 404 is adapted to releasably interface with the housing 402 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 an imaging contrast agent, saline, a combination of both contrast agent and saline 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 be a multi-syringe injector, as shown, where the several fluid reservoirs 404 may be oriented side-by-side or in another spatial relationship and are separately actuated by respective pistons associated with the fluid injection system 400.

[0090] In some non-limiting embodiments, the fluid injection system 400 may be used during a medical procedure to inject at least one medical fluid F into a patient's vascular system by driving plungers 406 associated with fluid reservoirs 404 with respective drive components. Each drive component can move its corresponding plunger 406 toward the distal end 410 of the fluid reservoir 404 to expel 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 tubing set configured to fluidly communicate with each fluid reservoir 404, and each fluid reservoir 404 can be placed in fluid communication with a flexible administration tubing and associated catheter to deliver fluid F from each fluid reservoir 404 to a patient at a vascular access site.

[0091] Referring now to FIG. 4C, FIG. 4C illustrates another non-limiting embodiment of a fluid injection system 400, i.e., a multi-fluid delivery system such as a MEDRAD® Centargo CT injection system, having a display screen 418. As shown in FIG. 4C, the fluid injection system 400 may be configured (e.g., adapted) to provide feedback regarding compliance with instructions for use. In some non-limiting embodiments, the fluid injection system 400 includes a powered fluid injector 101′ connected to a fluid delivery set intended to be associated with an injection device for delivering fluid under pressure from one or more single-dose or multi-dose containers and a fluid pathway set to a patient. In some non-limiting embodiments, the 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 electronic control devices) used to control the operation of reciprocable drive members such as those associated with the fluid injection system 400. Such drive members may be reciprocable via electromechanical drive components such as ball screw shafts driven by motors, voice coil actuators, rack and pinion gear drives, linear motors, and the like.

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

[0093] 5A-5W, which are illustrations 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 a display screen of the fluid injection system 104, the workstation device 106, the user device 110, and / or a separate system or device. In some non-limiting embodiments, the assets described with respect to the description of FIGS. 5A-5W may refer to a fluid injection system, such as the fluid injection system 104.

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

[0095] Referring now to FIG. 5C, FIG. 5C is an illustration of a GUI 503 for functionality related to providing and / or receiving data related to user preferences. As shown in FIG. 5C, GUI 503 may provide fields 5032 for entering user preferences, including language selection, a user profile username, a password, and data related to a service provider for servicing the fluid injection system 104. Referring now to FIG. 5D, FIG. 5D is an illustration of a GUI 504 for functionality related to providing a list of assets. As shown in FIG. 5D, GUI 504 may include fields 5042 with 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 FIG. 5D, GUI 504 may provide a GUI element 5044 for selecting an asset and a GUI element 5046 for proceeding to another GUI for the selected asset. As further shown in FIG. 5D, GUI 504 may provide a GUI element 5048 for printing data provided in GUI 504.

[0096] Referring now to FIG. 5E, FIG. 5E is an illustration of a GUI 505 for functionality related to providing data related to an asset's software configuration. As shown in FIG. 5E, GUI 505 may include a field 5052 having data related to the asset's software configuration, including data related to the asset's name, serial number, software version, and software updates. As further shown in FIG. 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 FIG. 5F, FIG. 5F is an illustration of a GUI 506 for functionality related to providing a software upload to an asset's software environment. As shown in FIG. 5F, GUI 506 may include a field 5062 having data related to a software update, including data related to the asset's name, serial number, software version, and software updates. As further shown in FIG. 5F, GUI 506 may provide a GUI element 5064 for proceeding to another GUI for the selected asset and a field 5066 for entering instructions regarding the software update.

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

[0098] 5I, which is an illustration of a GUI 509 of functionality related to providing data related to one or more user licenses for an asset. As shown in FIG. 5I, GUI 509 can include fields 5092 with data related to the user license for the asset, including the asset name, and data related to the user license for the asset (e.g., license number, description, license installation date, license expiration date, and license installer identifier). As further shown in FIG. 5H, GUI 509 can provide a GUI element 5094 for printing the data related to the user license for the asset provided in GUI 509.

[0099] Referring now to FIG. 5J, FIG. 5J is a diagram of a GUI 510 for functionality related to subscription renewal associated with a user license for an asset feature. As shown in FIG. 5J, GUI 510 may include fields 5102 with data related to renewing a subscription, including a user name, a user license number, a service level agreement (SLA), whether the entitlement is enabled, a payment method for the subscription, the subscription term, and an effective date. As further shown in FIG. 5J, GUI 510 may provide a GUI element 5104 for accessing a user license agreement (ULA) and a GUI element 5106 for enabling automatic subscription renewal. As further shown in FIG. 5J, GUI 510 may provide a GUI element 5108 for printing data related to subscription renewal provided in GUI 510.

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

[0101] 5M, which is a diagram of a GUI 513 for functionality related to asset registration (e.g., registering an asset in a user license's list of assets, registering an asset in a user profile's list of assets, etc.). As shown in FIG. 5M, GUI 513 may include fields 5132 with data related to the asset, including an asset identifier, product name, serial number, asset tag, software version, installation date, operation date, and data related to the asset's location (e.g., facility name, facility address, asset location room identifier, and asset number such as an internal asset number used to identify the asset at the facility). As further shown in FIG. 5M, GUI 513 can provide a GUI element 5134 for submitting data related to the asset provided to GUI 513 for the registration procedure.

[0102] 5N, which is an illustration of a GUI 514 for functionality related to adding a user license associated with an asset. As shown in FIG. 5N, GUI 514 may include fields 5142 with data related to the asset, including an asset identifier, a serial number, an asset tag, an effective date of the user license, and data related to the location of the asset (e.g., the facility name, the facility address, the room identifier for the asset's location, and an asset number such as an internal asset number used to identify the asset at the facility). As further shown in FIG. 5N, GUI 514 may provide a GUI element 5144 for submitting the data related to the asset provided in GUI 514 to add a user license associated with the asset.

[0103] 5O, which is an illustration of a GUI 515 for functionality related to deleting a user license associated with an asset. As shown in FIG. 5O, GUI 515 can include fields 5152 with data related to the asset, including an asset identifier, a serial number, an asset tag, an effective date of the user license, and data related to the location of the asset (e.g., the facility name, the facility address, the room identifier for the asset's location, and an asset number such as an internal asset number used to identify the asset at the facility). As further shown in FIG. 5O, GUI 515 can provide a GUI element 5154 for submitting the data related to the asset provided in GUI 514 to delete the user license associated with the asset.

[0104]

[0047] Referring now to Figure 5P, Figure 5P is an illustration of a GUI 516 for functionality 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 with data related to the asset's consumables, including product name and data related to the asset's available consumables. As further shown in Figure 5P, GUI 516 may provide a GUI element 5164 for providing a link to a website related to the consumables.

[0105] Referring now to FIG. 5Q, FIG. 5Q is an illustration of a GUI 517 for functionality related to reading an error code generated by an asset. As shown in FIG. 5Q, GUI 517 may be displayed after a user device reads a QR code that provides an error code. As further shown in FIG. 5Q, GUI 517 may include a field 5172 with data related to the asset that generated the error code, including the product name, serial number, and asset tag. As further shown in FIG. 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 remedies for the error code. As further shown in FIG. 5Q, GUI 517 may provide a GUI element 5176 for providing links to training content for the asset and a GUI element 5178 for accessing asset functionality related to service tools for the asset.

[0106] Referring now to FIG. 5R, FIG. 5R is an illustration of a GUI 518 for functionality related to generating a service request for an asset. As shown in FIG. 5R, GUI 518 may include fields 5182 with data related to the asset, including the product name, serial number, asset tag, data related to the asset's location (e.g., facility name and room identifier for the asset's location), data related to a contact for the service request (e.g., individual's name and phone number), and data related to error codes generated by the asset. As further shown in FIG. 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) that are the reason for the service request. As further shown in FIG. 5R, GUI 518 may provide a GUI element 5186 for submitting a service request.

[0107]

[0041] Referring now to Figure 5S, Figure 5S is an illustration of a GUI 519 of functionality related to generating a 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 the service request (e.g., estimated time of arrival and comments from the individual confirming receipt of the service request). As further shown in Figure 5S, GUI 519 may provide a GUI element 5194 for sending the confirmation of receipt of the service request.

[0108] 5T, which is an illustration of a GUI 520 of functionality related to providing the status of a service request for an asset. As shown in FIG. 5T, GUI 520 may include fields 5202 for entering data related to the status of the service request (e.g., an indication that the service request has been submitted, an indication that a confirmation of receipt of the service request has been submitted, an estimated time of arrival, an indication that the service request has been completed, data related to contacting an individual confirming receipt of the service request, and fields for entering data related to the service request). As further shown in FIG. 5T, GUI 520 may include a field 5204 for entering comments regarding the status of the service request for the asset.

[0109] 5U, which is an illustration of a GUI 521 for functionality related to providing a product report for an asset. As shown in FIG. 5U, GUI 521 may include a field 5212 for providing data related to notification of the product report. In some non-limiting embodiments, GUI 521 may be generated and provided after completion of a service request.

[0110] 5V, which is an illustration of a GUI 522 for functionality related to providing a product report for an asset. As shown in FIG. 5V, the GUI 522 may include fields 5222 with data related to the asset, including the product name, part number (e.g., master part number, material number, etc.), lot number, serial number, asset tag number, data related to the asset's location (e.g., facility name and room identifier for the asset's location), and data related to a contact for the product report (e.g., an individual's name, title, department, phone number, and email address). As further shown in FIG. 5V, the GUI 522 may provide a GUI element 5224 for submitting a product report.

[0111] 5W, which is an illustration of a GUI 523 for functionality related to submitting a component (e.g., part) request for an asset. As shown in FIG. 5W, GUI 523 may include fields 5232 for entering data related to a component request for an asset (e.g., asset identifier, asset serial number, item number, part number, description, indication of whether the component is being replaced, return serial number, and indication of quantity). As further shown in FIG. 5W, GUI 523 may provide a GUI element 5234 for submitting a component request.

[0112] While the present disclosure has been described in detail for purposes of illustration based on what are presently considered to be the most practical and preferred embodiments, it should be understood that such detail is for that purpose only and that the present disclosure is not limited to the disclosed embodiments, but on the contrary, is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the present disclosure contemplates that one or more aspects of any embodiment can be combined with one or more aspects of any other embodiment, to the extent possible. [Explanation of symbols]

[0113] 100 Environment 101' Electric fluid injector 102 Access Control System 102' Injector Housing 104 Fluid Injection System 104' Side 106 Workstation Devices 106' distal or upper end 108 Support System 108' proximal or lower end 110 User Devices 112 Communication Network 118' Bulk Fluid Connector 120' Bulk Fluid Source 122' Support member 128' connection port 200 devices 202 Bus 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 port 410 distal end of fluid reservoir 404 412 Fluid Path Set 414 workstations 416 Display screen 418 Display screen 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. 1. A system for accessing a fluid injection system, comprising: authenticating a user for access to the fluid injection system, the fluid injection system configured to administer a contrast fluid including a contrast agent to a patient, wherein upon authenticating the user for access to the fluid injection system: providing a graphical user interface (GUI) on a display screen that displays images scanned by a user device associated with said user; receiving login authentication associated with the image via a software application for accessing the fluid injection system, the software application being on the user device associated with the user; authenticating the user for access to the fluid injection system based on receiving the login authentication via the software application; At least one processor is programmed or configured to: providing data identifying one or more functions of the software application for accessing the fluid injection system based on input received via the software application, wherein the one or more functions of the software application: One or more functions associated with providing data related to the fluid injection system, wherein the one or more functions associated with providing data related to the fluid injection system include: functionality relating to obtaining data relating to error codes of the fluid injection system; functionality relating to generating a service history of the fluid injection system; functionality relating to providing the service history of the fluid injection system; functionality associated with generating a service request for the fluid injection system; functionality related to providing operational instructions for the fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; or any combination thereof, receiving data identifying selected features of the software application for accessing the fluid injection system; determining whether the user is authorized to access the selected functionality of the software application based on authenticating the user for access to the fluid injection system, wherein, when determining whether the user is authorized to access the selected functionality of the software application, the at least one processor is programmed or configured to determine whether the user has an access level to authorize access to the selected functionality of the software application, wherein the access level is based on a user profile of the user; providing access to the selected functionality of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected functionality of the software application; a system including said at least one processor programmed or configured to:

2. The at least one processor: displaying the data identifying the selected functionality of the software application for accessing the fluid injection system via the GUI of the software application on the user device 10. The system of claim 1, further programmed or configured to:

3. The fluid injection system includes the display screen, and the at least one processor: Displaying data related to the fluid injection system on the display screen of the fluid injection system.

10. The system of claim 1, further programmed or configured to:

4. The at least one processor: accessing the selected function of the software application of the fluid injection system to provide data related to the fluid injection system, the data related to the fluid injection system including data related to one or more operations of the fluid injection system; further programmed or configured to The at least one processor: Recording the data associated with one or more operations of the fluid injection system.

10. The system of claim 1, further programmed or configured to:

5. 1. A computer program for accessing a fluid injection system, the computer program comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: and authenticating a user for access to the fluid injection system, the fluid injection system being configured to administer a contrast fluid including a contrast agent to a patient, wherein the one or more instructions cause the at least one processor to authenticate the user for access to the fluid injection system: providing a graphical user interface (GUI) on a display screen that displays images scanned by the user device; receiving, via a software application for accessing the fluid injection system, login authentication associated with the image; authenticating the user for access to the fluid injection system based on receiving the login authentication via the software application; causing the at least one processor to causing, based on input received via the software application, to provide data identifying one or more functions of the software application for accessing the fluid injection system, wherein the one or more functions of the software application: One or more functions associated with providing data related to the fluid injection system, wherein the one or more functions associated with providing data related to the fluid injection system include: functionality relating to obtaining data relating to error codes of the fluid injection system; functionality relating to generating a service history of the fluid injection system; functionality relating to providing the service history of the fluid injection system; functionality associated with generating a service request for the fluid injection system; functionality related to providing operational instructions for the fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; or any combination thereof, receiving data identifying selected features of the software application of the fluid injection system; determining whether the user is authorized to access the selected functionality of the software application based on authenticating the user for access to the fluid injection system, wherein the one or more instructions causing the at least one processor to determine whether the user is authorized to access the selected functionality of the software application include: determining whether the user has an access level to authorize access to the selected functionality of the software application, wherein the access level is based on a user profile of the user; causing the fluid injection system to provide access to the selected functionality of the software application based on determining that the user is authorized to access the selected functionality of the software application. and at least one non-transitory computer-readable medium containing said one or more instructions.

6. The one or more instructions further cause the at least one processor to: displaying data identifying the selected function of the software application of the fluid injection system via the GUI of the software application on the user device.

6. A computer program according to claim 5.

7. The fluid injection system includes the display screen, and the one or more instructions further include: displaying data related to the fluid injection system on the display screen of the fluid injection system; 6. A computer program according to claim 5.

8. The one or more instructions further cause the at least one processor to: accessing the selected function of the software application for accessing the fluid injection system to provide data related to the fluid injection system, the data related to the fluid injection system including data related to one or more operations of the fluid injection system; The one or more instructions further cause the at least one processor to: recording the data associated with the one or more operations of the fluid injection system; 6. A computer program according to claim 5.

9. 1. A method for accessing a fluid injection system, comprising: authenticating, by at least one processor, a user for access to the fluid injection system, the fluid injection system configured to administer a contrast fluid including a contrast agent to a patient, and upon authenticating the user for access to the fluid injection system: providing a graphical user interface (GUI) on a display screen that displays an image scanned by a user device associated with said user; receiving login authentication associated with the image via a software application for accessing the fluid injection system, the software application being on the user device associated with the user; authenticating the user for access to the fluid injection system based on receiving the login authentication via the software application; the at least one processor is programmed or configured to: providing, by the at least one processor, data identifying one or more functions of the software application for accessing the fluid injection system based on input received via the software application, the one or more functions of the software application: One or more functions associated with providing data related to the fluid injection system, wherein the one or more functions associated with providing data related to the fluid injection system include: functionality relating to obtaining data relating to error codes of the fluid injection system; functionality relating to generating a service history of the fluid injection system; functionality relating to providing the service history of the fluid injection system; functionality associated with generating a service request for the fluid injection system; functionality related to providing operational instructions for the fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; functionality relating to providing data relating to service procedures performed on said fluid injection system; or any combination thereof, receiving, by the at least one processor, data identifying selected features of the software application for accessing the fluid injection system; determining, by the at least one processor, whether the user is authorized to access the selected functionality of the software application based on authenticating the user for access to the fluid injection system, wherein determining whether the user is authorized to access the selected functionality of the software application includes: determining whether the user has an access level to authorize access to the selected functionality of the software application, wherein the access level is based on a user profile of the user; providing, by the at least one processor, access to the selected functionality of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected functionality of the software application; Including, method.

10. The method of claim 1, further comprising: displaying, by the at least one processor, data identifying the selected function of the software application of the fluid injection system via the GUI of the software application on the user device.

10. The method of claim 9, further comprising:

11. The fluid injection system includes the display screen, and the method further comprises: causing the at least one processor to display data related to the fluid injection system on the display screen of the fluid injection system.

10. The method of claim 9, further comprising:

12. The method of claim 11, further comprising: accessing, by the at least one processor, the selected function of the software application for accessing the fluid injection system 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. further comprising The method comprises: recording, by the at least one processor, the data associated with the one or more operations of the fluid injection system.

10. The method of claim 9, further comprising:

Images