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

Abstract

A system for secure access to a fluid injection system is disclosed. The system includes at least one processor programmed or configured to authenticate user access to the fluid injection system, provide data identifying one or more characteristics of a software application used to access the fluid injection system, receive data identifying selected characteristics of the software application used to access the fluid injection system, and provide access to the selected characteristics of the software application used to access the fluid injection system.

Description

[0001] Cross-references to related applications

[0002] 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. Technical Field

[0003] This disclosure generally relates to systems, devices, products, apparatuses, and methods for providing access to electronic devices, and in a particular embodiment, to systems, products, and methods for secure access to fluid injection systems. Background Technology

[0004] An infusion device, such as a fluid infusion device (e.g., a medical fluid delivery device), can be used by medical practitioners (such as physicians) for medical diagnostic and / or medical treatment procedures. For example, a medical practitioner can use a fluid infusion device to infuse one or more medical fluids into a patient. Fluid infusion devices can be used to pressurize and infuse medical fluids, such as radiographic materials (e.g., contrast agents, radiographic contrast media, etc.), and / or flushing agents (e.g., saline solution), during medical imaging procedures (e.g., angiography, computed tomography (CT), ultrasound, magnetic resonance imaging (MRI), and positron emission tomography (PET)). In some cases, fluid infusion devices are designed to deliver a predetermined amount of medical fluid at a predetermined flow rate.

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

[0006] Therefore, systems, apparatuses, products, devices and / or methods for securely accessing fluid injection systems are provided, improving the availability and / or accessibility of information about the software environment of the fluid injection system.

[0007] Further non-limiting embodiments are described in the following numbered clauses:

[0008] Clause 1. A system for accessing a fluid injection system, comprising: at least one processor programmed or configured to: authenticate user 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.

[0009] Clause 2. The system according to Clause 1, wherein the at least one processor is further programmed or configured to display the data related to selected features of a software application for accessing the fluid injection system via a graphical user interface (GUI) of a mobile application on a user device.

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

[0011] Clause 4. The system according to any one of Clauses 1-3, wherein, when determining whether the user is authorized to access selected features of a software application for accessing the fluid injection system, the at least one processor is programmed or configured to: determine whether the user has an access level that authorizes the user to access selected features of a software application for accessing the fluid injection system.

[0012] Clause 5. The system according to any one of Clauses 1-4, wherein the fluid injection system includes a display screen, and wherein the at least one processor is further programmed or configured to display data associated with the fluid injection system on the display screen of the fluid injection system.

[0013] Clause 6. The system according to any one of Clauses 1-5, wherein 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, 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 at least one processor is further programmed or configured to: record the data related to one or more operations of the fluid injection system.

[0014] Clause 7. The system according to any one of Clauses 1-6, wherein, when providing access to selected features of a software application for accessing the fluid injection system, the at least one processor is programmed or configured to: provide access to selected features of a 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.

[0015] Clause 8. A computer program product for accessing a fluid injection system, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, the one or more instructions, when executed by at least one processor, causing the at least one processor to: authenticate user 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 the fluid injection system; and provide access to the selected features of the software application for the fluid injection system.

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

[0017] Clause 10. A computer program product according to Clause 8 or 9, wherein the one or more instructions further cause the at least one processor to: determine, based on authenticating the user's access to the fluid injection system, select features of a software application that authorizes the user to access the fluid injection system.

[0018] Clause 11. The computer program product according to any one of Clauses 8-10, wherein the one or more instructions that cause the at least one processor to determine whether the user is authorized to access selected features of the software application for accessing the 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 the selected features of the software application for accessing the fluid injection system.

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

[0020] Clause 13. A computer program product according to any one of Clauses 8-12, wherein the one or more instructions further cause the at least one processor to: access selected features of a software application for accessing the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system includes data associated with 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 associated with the one or more operations of the fluid injection system.

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

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

[0023] Clause 16. The method according to Clause 15 further includes: displaying data related to selected features of the software application of the fluid injection system via a graphical user interface (GUI) of a mobile application on a user device.

[0024] Clause 17. The method according to Clause 15 or 16 further includes: determining, based on authenticating the user's access to the fluid injection system, whether the user is authorized to access selected features of the software application used to access the fluid injection system.

[0025] Clause 18. The method according to any one of Clauses 15-17, wherein determining whether the user is authorized to access selected features of the software application for accessing the fluid injection system comprises: determining 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.

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

[0027] Clause 20. The method according to any one of Clauses 15-19 further comprises: accessing selected features of a software application for accessing the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system includes data associated with one or more operations of the fluid injection system; and wherein the method further comprises: recording the data associated with one or more operations of the fluid injection system.

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

[0029] These and other features of this disclosure, as well as the methods of operation and function of structurally related elements, and the economic efficiency of component assembly and manufacturing, will become more apparent upon consideration of the following description and appended claims with reference to the accompanying drawings, all of which form part of this specification, wherein the same reference numerals denote corresponding parts in the figures. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to be construed as limiting the scope of this disclosure. As used in the specification and claims, the singular forms “a,” “an,” and “the” include the plural objects referred to, unless the context clearly specifies otherwise. Attached Figure Description

[0030] Additional advantages and details of this disclosure are described in more detail below with reference to exemplary embodiments illustrated in the accompanying diagrams, wherein:

[0031] Figure 1 Figures are provided for non-limiting embodiments of the environments in which the systems, devices, products, apparatuses, and / or methods described herein can be implemented based on the principles of this disclosure;

[0032] Figure 2 for Figure 1 A diagram of a non-limiting embodiment of a component of one or more systems or devices;

[0033] Figure 3 A flowchart of a non-limiting embodiment of a process for secure access to a fluid injection system;

[0034] Figure 4AA non-limiting example of an imaging kit and a non-limiting embodiment of a fluid injection system therein are shown;

[0035] Figure 4B It shows Figure 4A The injector head unit of the fluid injection system shown;

[0036] Figure 4C Another non-limiting embodiment of the fluid injection system is shown; and

[0037] Figure 5A-5W A diagram illustrating a non-limiting embodiment of a graphical user interface (GUI) displayed during a process of securely accessing a fluid injection system. Detailed Implementation

[0038] For the purposes described below, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and their derivatives should be used in connection with this disclosure as oriented as they are in the accompanying drawings. However, it should be understood that this disclosure may take various alternative variations and sequences of steps unless expressly stated to the contrary. It should also be understood that the specific devices and processes shown in the accompanying drawings and described in the following specification are merely exemplary embodiments of this disclosure. Therefore, unless otherwise stated, specific dimensions and other physical features relating to embodiments disclosed herein should not be considered as limitations.

[0039] No aspect, component, element, structure, action, step, function, instruction, etc., used herein should be construed as critical or necessary unless explicitly stated otherwise. Furthermore, 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.” Additionally, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with “one or more” or “at least one.” The term “an” or similar language is used when only one item is intended to be used. Furthermore, as used herein, the terms “having,” “possessing,” “containing,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.”

[0040] As used herein, the terms "communication" and "transmission" can refer to the receiving, accepting, transmitting, conveying, or providing of information (e.g., data, signals, messages, instructions, commands, etc.). For one unit (e.g., a device, system, component of a device or system, a combination thereof, etc.) to communicate with another unit means that one unit is able to receive information directly or indirectly from and / or transmit information to the other unit. This can refer to a direct or indirect connection that is essentially wired and / or wireless. Furthermore, two units can communicate with each other even if the transmitted information can be modified, processed, relayed, and / or routed between the first and second units. For example, the first unit can communicate with the second unit even if it passively receives information and does not actively transmit information to the second unit. As another example, the first unit can communicate with the second unit if at least one intermediate unit (e.g., a third unit located between the first and second units) processes information received from the first unit and transmits the processed information to the second unit. In some non-limiting embodiments, a message can refer to a network packet (e.g., a data packet, etc.) that includes data. It should be understood that many other arrangements are also possible.

[0041] As used herein, the term "system" can refer to one or more computing devices or combinations of computing devices (e.g., but not limited to processors, servers, client devices, software applications, and / or other similar components). Furthermore, as used herein, references to "server" or "processor" can refer to the server and / or processor previously stated to perform the preceding steps or functions, different servers and / or processors, and / or combinations of servers and / or processors. For example, as used in the specification and claims, a first server and / or first processor stated to perform a first step or function can refer to the same or different server and / or processor referred to as performing a second step or function.

[0042] In some cases, a fluid injection device may be part of a set of devices used in a medical facility, such as a hospital, during patient treatment. Technicians (e.g., field service engineers), administrators, or other individuals appropriately trained in the operation of the fluid injection device may access its software via a hardware key. In some examples, an individual may access service-related software tools via a hardware key. In one example, the fluid injection device may malfunction during fluid injection operation, and an individual may obtain information about the malfunction by connecting a hardware key to the fluid injection device and downloading a report including that information. Furthermore, an individual may, for example, install software updates to the fluid injection device using a hardware key; these updates may include product feature enhancements, operating system updates, and / or security updates (e.g., security patches).

[0043] However, individuals may need hardware keys to access fluid injection equipment, and the physical nature of these keys makes them susceptible to loss, damage, or theft. Furthermore, multiple hardware keys can be associated with a specific fluid injection device, requiring more than one key to access all of the device's software functions. Additionally, the product key associated with the hardware key may expire after a period of user license, and as part of the user license renewal process, the operator of the fluid injection device may need to obtain and provide identification information for the device. The process of obtaining and providing identification information for the fluid injection device can be resource- and labor-intensive on behalf of the operator. Similarly, when maintaining and / or replacing components of the fluid injection device, the product key may need to be updated on the hardware key before the hardware key can access the device's software functions.

[0044] Non-limiting embodiments of this disclosure relate to systems, devices, products, apparatuses, and / or methods for secure access to a fluid injection system. In some non-limiting embodiments, the access management system may include at least one processor programmed or configured to: authenticate user access to the fluid injection system; provide data identifying one or more features of a software application used to access the fluid injection system; receive data identifying selected features of the software application used to access the fluid injection system; and provide access to the selected features of the software application used to access the fluid injection system. In some non-limiting embodiments, at least one processor is further programmed or configured to: display data related to the selected features of the software application used to access the fluid injection system via a graphical user interface (GUI) of a mobile application on a user device. In some non-limiting embodiments, at least one processor is further programmed or configured to: determine, based on authenticated user access to the fluid injection system, whether a user is authorized to access the selected features of the software application used to access the fluid injection system. In some non-limiting embodiments, when determining whether a user is authorized to access the selected features of the software application used to access the fluid injection system, at least one processor is 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 used to access the fluid injection system.

[0045] In some non-limiting embodiments, the fluid injection system includes a display screen, and at least one processor is further programmed or configured to display data related to the fluid injection system on the display screen. In some non-limiting embodiments, 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, wherein the data related to the fluid injection system includes data related to one or more operations of the fluid injection system; and at least one processor is further programmed or configured to record data related to one or more operations of the fluid injection system. In some non-limiting embodiments, when providing access to selected features of a software application for accessing the fluid injection system, at least one processor is programmed or configured to provide access to 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.

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

[0047] For reference Figure 1 , Figure 1 A diagram of an example environment 100 for implementing the devices, systems, and / or methods described herein. (See diagram for example.) Figure 1 As shown, environment 100 includes access management system 102, fluid injection system 104, workstation device 106, support system 108, user device 110, and communication network 112. In some non-limiting embodiments, access management system 102, fluid injection system 104, workstation device 106, support system 108, and / or user device 110 may be interconnected (e.g., establishing connections for communication) via wired connections, wireless connections, or a combination of wired and wireless connections.

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

[0049] In some non-limiting embodiments, the fluid infusion system 104 includes one or more devices capable of communicating with the access management system 102, workstation device 106, support system 108, and / or user device 110 via the communication network 112. For example, the fluid infusion system 104 may include computing devices, such as one or more computers, servers, a set of servers, and / or other similar devices. In some non-limiting embodiments, the fluid infusion system 104 includes one or more infusion devices (e.g., one or more fluid infusion devices). In some non-limiting embodiments, the fluid infusion system 104 is configured to administer (e.g., inject, deliver, etc.) a contrast fluid comprising a contrast agent to a patient, and / or administer an aqueous fluid, such as saline, to the patient before, during, and / or after the administration of the contrast fluid. For example, the fluid infusion system 104 may administer one or more prescription doses of contrast fluid directly into the patient's bloodstream via a subcutaneous injection needle and syringe. In some non-limiting embodiments, the fluid infusion system 104 may be configured to continuously administer an aqueous fluid to a patient via a peripheral venous line (PIV) and catheter, and one or more prescription doses of contrast fluid may be introduced into the PIV and administered to the patient via the catheter. In some non-limiting embodiments, the fluid infusion system 104 is configured to infuse a dose of contrast fluid, followed by administration of a specific volume of aqueous fluid. In some non-limiting embodiments, the fluid infusion system 104 may include a device capable of reading (e.g., scanning) barcodes, such as quick response (QR) codes.

[0050] In some non-limiting embodiments, the fluid injection system 104 may include one or more exemplary injection systems or injectors disclosed in the following patents: U.S. Patent Application Serial No. 09 / 715,330, filed November 17, 2000 (granted as U.S. Patent No. 6,643,537); U.S. Patent Application Serial No. 09 / 982,518, filed October 18, 2001 (granted as U.S. Patent No. 7,094,216); and U.S. Patent Application Serial No. 10 / 825,866, filed April 16, 2004 (granted as U.S. Patent No. 6,643,537). U.S. Patent No. 7,556,619; U.S. Patent Application Serial No. 12 / 437,011, filed May 7, 2009 (granted as U.S. Patent No. 8,337,456); U.S. Patent Application Serial No. 12 / 476,513, filed June 2, 2009 (granted as U.S. Patent No. 8,147,464); and U.S. Patent Application Serial No. 11 / 004,670, filed December 3, 2004 (granted as U.S. 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 Stellant CT Injection System Stellant FLEX CT Injection System Spectris Solaris EP MR Injection System MRXperion MR Injection System Salient Contrast Injection System Mark 7 Arterion Injection System Avanta Fluid Management Injection System Intego PET infusion system or Centargo CT injection system, all of which are provided by Bayer.

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

[0052] In some non-limiting embodiments, the support system 108 may include one or more devices capable of communicating with the access management system 102, the fluid injection system 104, the workstation device 106, and / or the user device 110 via the communication network 112. For example, the remote system 108 may include computing devices such as computers, servers (e.g., web servers), a set of servers, and / or other similar devices. In some non-limiting embodiments, the support system 108 may include backend systems associated with the access management system 102, the fluid injection system 104, and / or the workstation device 106. In some non-limiting embodiments, the support system 108 may include a cloud computing system that stores data in an associated database. In some non-limiting embodiments, the support system 108 is capable of interacting with the fluid injection system 104 to provide functionality, such as remote device services for the fluid injection system 104 (e.g., services provided by Bayer for injection systems and devices). Remote equipment support services). In some non-limiting embodiments, support system 108 may be operated or operated on behalf of the original equipment manufacturer (OEM) of fluid injection system 104 (e.g., the OEM of one or more components or devices of fluid injection system 104), the provider of fluid injection system 104, the imaging facility or hospital operating fluid injection system 104, service technicians assigned to fluid injection system 104, etc. In some non-limiting embodiments, support system 108 may include a hospital information system (HIS), a radiology information system (RIS), etc. In some non-limiting embodiments, support system 108 may include a customer relationship management (CRM) system.

[0053] In some non-limiting embodiments, user equipment 110 may include one or more devices capable of communicating with access management system 102, fluid injection system 104, workstation device 106, and / or support system 108 via communication network 112. For example, user equipment 110 may include computing devices such as computers (e.g., desktop computers, laptop computers, etc.) or mobile devices (e.g., smartphones, tablets, etc.). In some non-limiting embodiments, user equipment 110 is capable of reading (e.g., scanning) barcodes, such as quick response (QR) codes. In some non-limiting embodiments, user equipment 110 may be configured to communicate via short-range wireless communication connections (e.g., NFC communication connections, RFID communication connections, etc.). The user equipment 110 transmits and / or receives data to and / or from another device or system (e.g., fluid injection system 104, workstation device 106), including communication connections, etc. In some non-limiting embodiments, the user equipment 110 may be configured to transmit and / or receive data via radio frequency identification (RFID). For example, the user equipment 110 may include an RFID reader. In some non-limiting embodiments, the user equipment 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 thereon) the user equipment 110 (e.g., applications stored on the user equipment 110, such as mobile device applications, local applications for mobile devices, mobile cloud applications for mobile devices, etc.).

[0054] In some non-limiting embodiments, the communication network 112 may include one or more wired and / or wireless networks. For example, the communication network 112 may include cellular networks (e.g., Long Term Evolution (LTE) networks, third-generation (3G) networks, fourth-generation (4G) networks, fifth-generation (5G) networks, Code Division Multiple Access (CDMA) networks, etc.), Public Land Mobile Networks (PLMNs), Local Area Networks (LANs), Wide Area Networks (WANs), Metropolitan Area Networks (MANs), telephone networks (e.g., Public Switched Telephone Networks (PSTN)), private networks, self-organizing networks, intranets, the Internet, fiber-optic-based networks, cloud computing networks, short-range wireless communication networks (e.g., Networks, near field communication (NFC) networks, and / or combinations of these or other types of networks.

[0055] Figure 1 The number and layout of the systems, devices, and networks shown are provided as examples. Figure 1 Compared to what is shown, there can be additional systems and / or equipment, fewer systems and / or equipment, different systems and / or equipment, and / or systems and / or equipment with different arrangements. Furthermore, Figure 1 The two or more systems or devices shown can be implemented within a single system or a single device, or Figure 1 The single system or single device shown can be implemented as multiple distributed systems or devices. Additionally or alternatively, a group of systems or a group of devices in environment 100 (e.g., one or more systems, one or more devices, etc.) can perform one or more functions described as being performed by another group of systems or another group of devices in environment 100.

[0056] For reference Figure 2 , Figure 2This is an example component diagram of device 200. Device 200 may correspond to one or more devices of access management system 102, one or more devices of fluid injection system 104, workstation device 106, one or more devices of support system 108, and / or user device 110. In some non-limiting embodiments, access management system 102, fluid injection system 104, workstation device 106, support system 108, and / or user device 110 may include at least one device 200 and / or at least one component of device 200. Figure 2 As shown, device 200 may include bus 202, processor 204, memory 206, storage component 208, input component 210, output component 212 and communication interface 214.

[0057] Bus 202 may include components that allow 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), graphics processing unit (GPU), accelerated processing unit (APU), etc.), microprocessor, digital signal processor (DSP), and / or any processing component that can be programmed to perform functions (e.g., a field-programmable gate array (FPGA), 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 storage, optical storage, etc.) that stores information and / or instructions for use by processor 204.

[0058] Storage component 208 may store information and / or software associated with the operation and use of device 200. For example, storage component 208 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, solid-state drives, etc.), compact discs (CDs), digital versatile optical discs (DVDs), floppy disks, cartridges, magnetic tapes, and / or other types of computer-readable media, and corresponding drives.

[0059] Input component 210 may include components that allow device 200 to receive information, such as through user input (e.g., a touchscreen display, keyboard, keypad, mouse, button, switch, microphone, etc.). Additionally, or alternatively, input component 210 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, accelerometer, gyroscope, actuator, etc.). Output component 212 may include components that provide output information from device 200 (e.g., a display, speaker, one or more light-emitting diodes (LEDs), etc.).

[0060] Communication interface 214 may include transceiver-like components (e.g., transceiver, separate receiver, and transmitter, etc.) that enable device 200 to communicate with other devices, such as via wired connection, wireless connection, or a combination of wired and wireless connection. Communication interface 214 may allow device 200 to receive information from and / or provide information to another device. For example, 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, etc. Interfaces, cellular network interfaces, etc.

[0061] Device 200 can perform one or more of the processes described herein. Device 200 can perform these processes based on software instructions stored in a computer-readable medium, such as memory 206 and / or storage component 208, executed by processor 204. 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 memory space located within a single physical storage device or memory space distributed across multiple physical storage devices.

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

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

[0064] For reference Figure 3 , Figure 3This is a flowchart of a non-limiting embodiment of a process 300 for secure access to a fluid injection system. In some non-limiting embodiments, one or more steps of process 300 are performed by an access management system 102 (e.g., one or more devices of access management system 102, etc.) (e.g., fully, partially, etc.). In some non-limiting embodiments, one or more steps of process 300 are performed by another device or group of devices (e.g., fully, partially, etc.) that is separate from or includes 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.

[0065] Aspects of the non-limiting embodiments herein (e.g., one or more steps of process 300) may be performed in relation to a software application (e.g., a mobile application) whose client-side components are 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 (e.g., controlled) by the access management system 102 to access one or more features of the software environment of the fluid injection system 104 (e.g., one or more software applications, one or more software services, one or more software tools, etc. of the software environment). Additionally or alternatively, one or more aspects of the software application may be stored on the fluid injection system 104 and / or workstation device 106. In some non-limiting embodiments, one or more features of the software application may provide access to one or more features of the software environment of the fluid injection system 104.

[0066] In some non-limiting embodiments, one or more features of the software environment of the fluid injection system 104 may include features associated with a patient procedure tracking system (e.g., a system for operating modal work lists, a system for providing patient demographic information for fluid injection procedures and / or medical imaging procedures, etc.), features associated with a fluid injector management system, features associated with an image archiving and communication system (e.g., a picture archiving and communication system (PACS)), features associated with a radiology information system (RIS), and / or features associated with a radiology analysis system (e.g., those marketed and sold by Bayer HealthCare LLC). Enterprise applications).

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

[0068] In some non-limiting embodiments, the access management system 102 may generate login credentials to provide to the fluid injection system 104, thereby authenticating user access to the fluid injection system 104. For example, the access management system 102 may generate login credentials (e.g., password, passcode, etc.) based on a clock (e.g., the internal clock of user equipment 110). In some non-limiting embodiments, the access management system 102 may provide a GUI to display indicators on the fluid injection system 104 or workstation device 106 (e.g., on the display screen of the fluid injection system 104 or workstation device 106), and the access management system 102 may receive login credentials associated with the indicators from user equipment 110 via a software application. For example, the access management system 102 may provide a GUI displaying an image (e.g., an image of a QR code) on the display screen of the fluid injection system 104 or workstation device 106, and user equipment 110 may scan the image. User equipment 110 may determine the login credentials associated with the image, and user equipment 110 may provide the login credentials to the access management system 102 via a software application. Access management system 102 can authenticate user access to fluid injection system 104 based on login credentials received via a software application. In some non-limiting embodiments, access management system 102 can provide a GUI on user equipment 110 to display indicators, and access management system 102 can receive login credentials associated with the indicators from fluid injection system 104 via a software application. For example, access management system 102 can provide a GUI displaying an image (e.g., an image of a QR code) on the display screen of user equipment 110, and fluid injection system 104 can scan the image. Fluid injection system 104 can determine the login credentials associated with the image, and fluid injection system 104 can provide the login credentials to access management system 102 via a software application. Access management system 102 can authenticate user access to fluid injection system 104 based on login credentials received via a software application.

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

[0070] In some non-limiting embodiments, features (e.g., services, tools, etc.) of the software application used to access the fluid injection system 104 may include one or more features associated with providing data associated with the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may communicate with a web application (e.g., with a web application operated by a web server) to obtain data associated with the fluid injection system 104 through the software application. For example, the access management system 102 may communicate with a web application to obtain data associated with a user profile, data associated with user licenses (e.g., a user's software license), etc.

[0071] In some examples, data associated with the fluid injection system 104 may include data related to the identifier of the fluid injection system 104 (e.g., device identifier of the fluid injection system 104, model of the fluid injection system 104, serial number of the fluid injection system 104, etc.), data associated with the software or hardware of the fluid injection system 104 (e.g., software configuration of the fluid injection system 104, hardware configuration of the fluid injection system 104, software version of the fluid injection system 104, such as the software version of the operating system of the fluid injection system 104, software revision number of the fluid injection system 104, identifiers of one or more software patches that have been applied to the fluid injection system 104, etc.), and / or data associated with the network connectivity of the fluid injection system 104 (e.g., MAC address of the network interface controller (NIC) of the fluid injection system 104, IP address of the fluid injection system 104, etc.). In some non-limiting embodiments, data associated with the fluid injection system 104 may include data associated with one or more operations of the fluid injection system 104. Data associated with one or more operations of the fluid injection system 104 may include data associated with operations performed by the fluid injection system 104 (e.g., the number of fluid injection operations performed by the fluid injection system 104, the number of times the fluid injection operations were performed by the fluid injection system 104, the operating parameters of the fluid injection operations performed by the fluid injection system 104, data associated with patient demographics of the patients to whom the fluid injection system 104 performed fluid injection operations, etc.), data associated with the configuration of the fluid injection system 104 (e.g., the configuration of the fluid delivery components of the fluid injection system 104, the cybersecurity bill of materials (CBOM) of the fluid injection system 104, the software bill of materials (SBOM) of the fluid injection system 104, etc.), and / or data associated with faults encountered during one or more operations of the fluid injection system 104. In some non-limiting embodiments, the access management system 102 may log (e.g., store in a data log) data associated with the fluid injection system 104. For example, the access management system 102 may log data associated with one or more operations of the fluid injection system 104. Note that embodiments of this disclosure comply with all legal requirements, such as the Health Insurance Portability and Accountability Act (HIPAA), which allow data stored or transmitted in connection with the fluid infusion system 104 to exclude the patient’s personal health information, such as appropriate PHI and PII.

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

[0073] In some non-limiting embodiments, data associated with faults encountered during one or more operations of the fluid injection system 104 may include identifiers of errors associated with the operation of the fluid injection system 104. Identifiers of errors associated with the operation of the fluid injection system 104 may include error codes (e.g., specific error codes associated with the type of fault encountered). Additionally or alternatively, data associated with faults encountered during one or more operations of the fluid injection system 104 may include operating parameters of the fluid injection system 104 associated with the fault. For example, data associated with faults 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 by the fluid injection system 104 (e.g., disposable components, such as multiple-use disposable kits (MUDS), single-use disposable kits (SUDS), syringes, or tubing kits), measurements of electrical characteristics (e.g., voltage, current, power, etc.) of electrical components of the fluid injection system 104, and / or other relevant values ​​of variables and / or system components.

[0074] In some non-limiting embodiments, the features of the software application for accessing the fluid injection system 104 may include features related to acquiring (e.g., reading, scanning, retrieving from a data structure, etc.) error codes of the fluid injection system 104 (e.g., error codes generated therefrom), features related to determining the location of the fluid injection system 104 (e.g., location based on Global Positioning System (GPS) location), features related to generating the service history of the fluid injection system 104, and features associated with providing (e.g., providing downloads, displays, prints, transmissions of included messages, etc.) the service history of the fluid injection system 104. Features associated with providing an asset list (e.g., multiple fluid injection systems 104, one or more components of fluid injection systems 104, components of multiple fluid injection systems 104, etc.), features associated with adding assets to the asset list, features associated with providing a list of features of the software environment of the fluid injection system 104 covered by user licenses, features associated with initiating billing (e.g., automatic billing) for one or more features of the software environment of the fluid injection system 104 covered by user licenses, and features associated with adding one or more features of the software environment of the fluid injection system 104 (e.g., equipment support services, etc.). Remote support allows for secure and reliable remote monitoring of its contrast media injection system and software to minimize downtime; and Service agreement procedures that provide a higher level of service and capabilities, including and The NxT non-obsolescence plan, which also includes services and capabilities provided by Bayer through the service agreement plan, includes features associated with user licenses, features associated with generating service requests for the fluid injection system 104, features associated with registering a warranty, features associated with providing data associated with consumables used during the fluid injection procedure (e.g., multiple-use disposable kits (MUDS), single-use disposable kits (SUDS), syringes, or tubing kits), features associated with providing a list of one or more fluid injection protocols to the fluid injection system 104, features associated with adding or restoring (e.g., restoring after a service procedure) one or more fluid injection protocols to the fluid injection system 104, and features associated with providing and / or receiving information about user preferences (e.g., user preferences associated with the appearance and feel of the software application, such as the display color of the provided data and / or other information). Features associated with data related to the fluid injection system 104 (e.g., providing an operating system), features associated with providing operating instructions for the fluid injection system 104, features associated with providing data related to the service procedures to be performed on the fluid injection system 104 (e.g., data related to the diagnostic and / or troubleshooting capabilities of the service procedures, such as the augmented reality (AR) capabilities of the service procedures, real-time data related to the component aspects of the fluid injection system 104, such as calibration values, fluid, battery, motor, etc.), features associated with providing data related to the service procedures performed on the fluid injection system 104 (e.g., service reports based on the service procedures, final checklists after the service procedures, messages containing confirmation of service procedure completion, etc.), and / or features associated with providing complaints about the product.

[0075] In some non-limiting embodiments, features associated with providing an asset list may include features associated with providing a user license. In some non-limiting embodiments, this feature may provide an asset list associated with a user license provided according to an encryption protocol. In some non-limiting embodiments, the asset list may include identifiers for Scan Room Unit (SRU) and Control Room Unit (CRU) IDs. In some non-limiting embodiments, the asset list may be organized (e.g., sorted) based on user preferences. In some non-limiting embodiments, this feature may provide (e.g., provide messages such as downloads, displays, prints, and transmissions) reports associated with the asset list (e.g., service reports) (e.g., reports containing data related to each asset in the asset list, one or more assets in the asset list, etc.), which are associated with a user license. In some non-limiting embodiments, this feature may provide the ability to transmit reports to systems outside the fluid injection system 104 (e.g., a service management system, a flight recorder system, etc.). In some non-limiting embodiments, this feature may provide data associated with each asset, including software configuration (e.g., current software level), calibration date (e.g., most recent calibration date, all calibration dates, etc.), the user who performed the calibration, and various aspects of the asset being calibrated (e.g., pressure, potentiometer, etc.).

[0076] In some non-limiting embodiments, features related to providing software to the software environment of the fluid injection system 104 may provide software uploads, such as updates (e.g., patches) and additional features, and / or software downloads from the software environment of the fluid injection system 104. For example, this feature may provide software uploads and / or software downloads from the software environment of the fluid injection system 104 when a connection to the communication network 112 via the software application used to access the fluid injection system 104 is unavailable. In some non-limiting embodiments, software uploads may be stored (e.g., preloaded) on the user equipment 110 via the software application and may be uploaded to the software environment of the fluid injection system 104 when a connection to the communication network 112 is unavailable. In some non-limiting embodiments, this feature may provide size indications and / or completion status indications (e.g., status completion bars) for uploading and / or downloading software to and / or from the fluid injection system 104.

[0077] In some non-limiting embodiments, features related to determining the location of the fluid injection system 104 may include: transmitting 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 transmitted via a communication method, such as broadcast, multicast, unicast, etc. (e.g., an RFID-based message).

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

[0079] In some non-limiting embodiments, the access management system 102 may authenticate users based on user licenses associated with the fluid injection system 104. For example, the access management system 102 may use data associated with user identification to determine whether a user is associated with a valid user license. In some non-limiting embodiments, the access management system 102 may authenticate users based on determining that a user is associated with a valid user license. In some non-limiting embodiments, the access management system 102 may authenticate users without determining that a user is not associated with a valid user license. In some non-limiting embodiments, the access management system 102 may remove a user's access to the fluid injection system 104 based on the expiration of the user license associated with the user. In some non-limiting embodiments, the access management system 102 may authenticate a user's access to a specific fluid injection system (e.g., a specific model of fluid injection system, a fluid injection system with a specific identifier, etc.) based on user licenses.

[0080] In some non-limiting embodiments, the access management system 102 may authenticate a user based on data associated with an identifier of the fluid injection system 104. For example, the access management system 102 may obtain data associated with an identifier of the fluid injection system 104 and use data associated with a user identification and 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 may authenticate the 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 the 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.

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

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

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

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

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

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

[0087] like Figure 3 As shown, in step 304, process 300 includes providing data identifying one or more features of a software application used to access the fluid injection system. For example, access management system 102 may provide user equipment 110 with data identifying one or more features of a software application used to access fluid injection system 104. In some non-limiting embodiments, access management system 102 may provide a user with multiple feature identifiers (e.g., a list of identifiers for multiple features) of the software application used to access fluid injection system 104 via a graphical user interface (GUI) on user equipment 110.

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

[0089] like Figure 3 As shown, in step 306, process 300 includes receiving data that identifies selected characteristics of a software application used to access the fluid injection system. For example, access management system 102 may receive data that identifies selected characteristics of a software application used to access fluid injection system 104.

[0090] In some non-limiting embodiments, based on user input to the GUI provided via user equipment 110, access management system 102 may receive data identifying selected features of one or more characteristics of a software application for accessing fluid injection system 104. In some non-limiting embodiments, access management system 102 may receive information associated with user selections of GUI elements displayed by the GUI on the screen of user equipment 110. For example, based on user equipment 110 detecting user interaction with the GUI, user equipment 110 may provide access management system 102 with an indication of the user's selection. GUI elements may correspond to selected features of one or more features, the identification data of which is provided via the GUI on the screen of user equipment 110.

[0091] In some non-limiting embodiments, the access management system 102 may receive a request for access to a selected feature based on a feature selected from a plurality of features. For example, the access management system 102 may receive a request for access to a selected feature based on a user selecting a GUI element corresponding to a feature in the GUI on the user device 110. In some non-limiting embodiments, the access management system 102 may provide a prompt to the user via the GUI on the user device 110 to provide information requesting access to the selected feature. For example, the prompt may request the user to provide user-associated data that has not been previously received and may help determine whether to grant access to the selected feature.

[0092] like Figure 3 As shown, in step 308, process 300 includes providing access to selected features of a software application used to access the fluid injection system 104. For example, access management system 102 can provide access to selected features of a software application used to access the fluid injection system 104. In some non-limiting embodiments, based on user access to the fluid injection system 104 authenticated by access management system 102, access management system 102 can (e.g., only) provide access to features of the software application used to access the fluid injection system 104 to user equipment 110 (e.g., the user of user equipment 110). In some non-limiting embodiments, based on user access to the fluid injection system 102 authenticated by access management system 102, access management system 102 can provide user equipment 110 with access to specific features of the software application used to access the fluid injection system 104 (e.g., features associated with a remote service program of the fluid injection system 104).

[0093] In some non-limiting embodiments, when a communication connection to the communication network 112 is unavailable, the access management system 102 can provide access to selected features of a software application stored on the user equipment 110 for accessing the fluid injection system 104. 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 equipment 110 and the fluid injection system 104. The access management system 102 can provide access to selected features of the software application through the communication connection between the user equipment 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., injector head, display, single-board computer printed circuit board (PCB), servo CPU PCB, etc.) are being repaired (e.g., removed and / or replaced).

[0094] In some non-limiting embodiments, the access management system 102 may perform actions related to selected features of the software application used to access the fluid injection system 104. For example, the access management system 102 may receive and / or provide data associated with selected features of the software application used to access the fluid injection system 104. In a specific example, the access management system 102 may scan error codes of the fluid injection system 104, generate a service history of the fluid injection system 104, provide the service history of the fluid injection system 104, provide an asset list, add assets to the asset list, provide a list of features of the software environment of the fluid injection system 104 covered by user licenses, initiate an accounting procedure for one or more features of the software environment of the fluid injection system 104 covered by user licenses, add one or more features of the software environment of the fluid injection system 104 to user licenses, generate service requests for the fluid injection system 104, register warranties, provide data related to consumables used during fluid injection procedures of the fluid injection system 104, provide a list of one or more fluid injection protocols to the fluid injection system 104, add or restore one or more fluid injection protocols to the fluid injection system 104, provide and / or receive data on user preferences for software applications, provide software to the software environment of the fluid injection system 104, provide instructions for the operation of the fluid injection system 104, provide data associated with service procedures to be performed on the fluid injection system 104, and / or provide complaints about products such as the fluid injection system 104.

[0095] In some non-limiting embodiments, the access management system 102 may perform actions based on actions associated with selected features of a software application. For example, the access management system 102 may provide a GUI displaying an image (e.g., an image of a QR code) on the display screen of the fluid injection system 104 or workstation device 106, and the user device 110 may scan the image. The user device 110 may determine data associated with selected features of the software application based on the scanned image, such as a report on a service procedure executed on the fluid injection system 104. The user device 110 may provide the data associated with the selected features of the software application to the access management system 102 via the software application. The access management system 102 may cause the fluid injection system 104 to perform a startup operation (e.g., a restart operation) based on receiving the data associated with the selected features of the software application. In some non-limiting embodiments, the access management system 102 may provide a GUI on the display screen of the fluid injection system 104 or the workstation device 106 to display a second image (e.g., a second image of a QR code), and the user device 110 may scan the image and generate a security key via a software application to provide to the fluid injection system 104 to enable the fluid injection system 104 to perform a startup operation.

[0096] Now for reference Figure 4A and 4B , Figure 4A A non-limiting embodiment of the fluid injection system 400 is shown, such as that located in a CT kit 4000. Stellant FLEX CT injection system. In some non-limiting embodiments, the fluid injection system 400 may be the same as or similar to the fluid injection system 104. Figure 4A As shown, the fluid injection system 400 may include a bifurcation system comprising a scanning chamber unit and a control chamber unit located in the scanning chamber 4001 and control chamber 1002 of the CT kit 4000, respectively. In a non-limiting embodiment, the scanning chamber unit may include an injection head unit 401, and the control chamber unit may include a workstation 414 with a display screen 416, such as a Certegra workstation. In a non-limiting embodiment, the scanning chamber unit may include an injector head unit 401, and the control chamber unit may include a workstation 414, such as a Certegra workstation with a display screen 416. Workstation. For example... Figure 4B As shown, 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, such as Figure 4B As best illustrated, the fluid infusion system 400 may include drive components for controlling the inflow or outflow of fluid into fluid reservoirs, such as a piston associated with each fluid reservoir 404 that drives a plunger 406 within the cylinder of the fluid reservoir 404. In some non-limiting embodiments, each fluid reservoir 404 is adapted to be releasably engaged with a housing 402 at a port 408. Each fluid reservoir 404 of the fluid infusion system 400 is configured to be filled with at least one medical fluid F, such as an imaging contrast agent, a saline solution, or a combination of both a contrast medium and a saline solution in a desired proportion, 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 infusion system 400 may be a multi-syringe injector, as shown, where several fluid reservoirs 404 may be oriented side-by-side or in another spatial relationship and individually actuated by a corresponding piston associated with the fluid infusion system 400.

[0097] In some non-limiting embodiments, the fluid infusion system 400 can be used during a medical procedure to infuse at least one medical fluid F into a patient's vascular system by driving plungers 406 associated with fluid reservoirs 404 using their respective drive components. During perfusion, flushing, and / or fluid delivery steps, 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 a fluid pathway kit 412. In some non-limiting embodiments, the fluid pathway kit 412 may include at least one tubing or tubing kit configured to be in fluid communication with each fluid reservoir 404 to allow each fluid reservoir 404 to be in fluid communication with a flexible drug delivery tubing and an associated catheter for delivering fluid F from each fluid reservoir 404 to the patient at a vascular access location.

[0098] For reference Figure 4C , Figure 4C Another non-limiting embodiment of the fluid injection system 400 is shown, namely a multi-fluid delivery system, such as one with a display screen 418. Centargo CT injection system. For example... Figure 4C As shown, the fluid infusion system 400 can be configured (e.g., adapted) to provide feedback on adherence to instructions for use. In some non-limiting embodiments, the fluid infusion system 400 includes a powered fluid injector 101' connected to a fluid delivery kit designed to be associated with an injector device to deliver fluid under pressure from one or more single-dose or multi-dose containers and fluid pathway kits into 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' encapsulates various mechanical drive components, electrical and power components required to drive the mechanical drive components, and control components, such as electronic storage devices and electronic control devices (hereinafter referred to as (a plurality of) electronic control devices), for controlling the operation of a reciprocatingly movable drive member, such as the drive member associated with the fluid infusion system 400. Such a drive component can be reciprocated by an electromechanical drive assembly, such as a ball screw driven by a motor, a voice coil actuator, a rack and pinion transmission device, a linear motor, etc.

[0099] In some non-limiting embodiments, the fluid infusion system 400 may include at least one body fluid connector 118' for connection to at least one body fluid source 120'. Alternatively, the fluid source may be a single-dose vial instead of a body fluid source. In some examples, multiple body fluid connectors 118' may be provided. In some non-limiting embodiments, three body fluid connectors 118' may be provided side-by-side or in other arrangements. In some non-limiting embodiments, at least one body fluid connector 118' may be a spike, such as a vial, bottle, or bag, configured to removably connect to at least one body fluid source 120'. At least one body fluid connector 118' may have a reusable or non-reusable interface to each new body fluid source 120'. As described herein, at least one body fluid connector 118' may be formed on or attached to a multi-patient disposable kit. The at least one body fluid source 120' may be configured to receive medical fluids, such as saline, imaging contrast solutions, or other medical fluids, for delivery to the fluid infusion system 400. The injector housing 102' may have at least one support member 122' for supporting at least one bulk fluid source 120' once 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 single-use patient line (not shown) is connected for allowing (multiple) medical fluids to be administered to the patient via a catheter according to a desired injection protocol.

[0100] For reference Figure 5A-5W , Figure 5A-5W This is a screen diagram of a GUI that can be provided by the access management system 102 through a software application for accessing the fluid injection system 104. In some non-limiting embodiments, the GUI screen can be provided on the display screen of the fluid injection system 104, workstation device 106, user device 110, and / or individual systems or devices. In some non-limiting embodiments, regarding Figure 5A-5W The asset discussed in the description may refer to a fluid injection system, such as fluid injection system 104.

[0101] For reference Figure 5A , Figure 5A This is a schematic diagram of GUI 501, which includes fields for users to log in to a software application for accessing the fluid injection system 104 operated by the access management system 102. Now refer to... Figure 5B , Figure 5B This is a diagram of GUI 502, which includes a list of features of the software application used to access the fluid injection system 104. (See diagram 502.) Figure 5BAs shown, GUI 502 can provide the user with fields 5022 for messages, fields 5024 for data associated with user permissions, and multiple GUI elements 5026 for selecting features of the software application.

[0102] For reference Figure 5C , Figure 5C A diagram of GUI 503 related to providing and / or receiving data about user preferences. (See diagram 503 for example.) Figure 5C As shown, GUI 503 can provide fields 5032 for inputting user preferences, including language selection, username for the user profile, password, and data related to the service provider of fluid injection system 104. Now refer to... Figure 5D , Figure 5D This is a diagram of GUI 504 related to the features associated with providing an asset list. (See diagram 504.) Figure 5D As shown, GUI 504 may include fields 5042 with data associated with each asset in the asset list, including asset name, location, room identifier, serial number, asset tag number, coverage description, and status description. Figure 5D As further shown, GUI 504 can provide GUI element 5044 for selecting an asset and GUI element 5046 for proceeding to another GUI related to the selected asset. Figure 5D As further shown, GUI 504 can provide GUI element 5048 for printing the data provided in GUI 504.

[0103] For reference Figure 5E , Figure 5E A diagram of GUI 505 showing characteristics related to data associated with the software configuration of the provided assets. (See diagram 505.) Figure 5E As shown, GUI 505 may include a field 5052 containing data associated with the asset's software configuration, including the asset name, serial number, software version, and data associated with software updates. Figure 5D As further shown, GUI 504 can provide GUI element 5054 for refreshing the data provided in GUI 505 and GUI element 5056 for printing the data provided in GUI 505. Now refer to Figure 5F , Figure 5F This is a diagram of GUI 506 related to the features associated with providing software uploads to the software environment of the asset. (See diagram 506.) Figure 5F As shown, GUI 506 may include a field 5062 containing data associated with the software update, including asset name, serial number, software version, and data associated with the software update. Figure 5FAs further shown, GUI 506 can provide GUI element 5064 and field 5066, GUI element 5064 for navigating to another GUI for the selected asset, and field 5066 for entering instructions regarding software updates.

[0104] Now for reference Figure 5G , Figure 5G A diagram of GUI 507 for the features related to the Software Bill of Materials (SBOM) providing the assets. (See diagram 507.) Figure 5G As shown, GUI 507 may include field 5072 with data associated with the SBOM, including asset name, serial number, and data associated with software updates. For example... Figure 5G As further shown, GUI 507 can provide GUI element 5074 for printing data associated with the SBOM provided in GUI 507. Now refer to Figure 5H , Figure 5H This is a diagram of GUI 508 related to the features associated with providing product configuration for assets. (See diagram 508.) Figure 5H As shown, GUI 508 may include fields 5082 with data associated with product configuration, including asset name, serial number, and data associated with the asset's components (e.g., part number, description, serial number, software version, and software update version). Figure 5H As further shown, GUI 508 can provide GUI element 5084 for printing data associated with the product configuration provided in GUI 508.

[0105] Now for reference Figure 5I , Figure 5I A diagram of a graphical user interface 509 for providing features related to data associated with one or more user licenses for an asset. (See diagram 509 for example.) Figure 5I As shown, GUI 509 may include a field 5092 containing data associated with user licenses for an asset, including the asset name and data associated with user licenses for the asset (e.g., license number, description, license installation date, license expiration date, and license installer identifier). Figure 5H As further shown, GUI 509 can provide GUI element 5094 for printing data associated with user licenses for assets provided in GUI 509.

[0106] Now for reference Figure 5J , Figure 5J A diagram of GUI 510 for features related to updating user licenses used for asset characteristics. (See diagram 510.) Figure 5JAs shown, GUI 510 may include fields 5102 containing data associated with the subscription update, including username, user license number, service level agreement (SLA), whether rights are enabled, payment method for the subscription, subscription duration, and effective date. Figure 5J As further illustrated, GUI 510 can provide GUI element 5104 for accessing the User License Agreement (ULA) and GUI element 5106 for implementing automatic updates of the subscription. Figure 5J As further shown, GUI 510 can provide GUI element 5108 for printing and updating data associated with subscriptions provided in GUI 510.

[0107] For reference Figure 5K , Figure 5K A diagram of GUI511 showing features related to reading QR codes (e.g., QR codes displayed on a screen). Figure 5K As shown, GUI 511 may include fields for capturing (e.g., via an image capture device such as a camera on a user device such as user device 110) a QR code image. Now refer to Figure 5L , Figure 5L This is a diagram of GUI 512 related to the features of providing and / or receiving data associated with assets. (See diagram 512 for example.) Figure 5L As shown, GUI 512 may include fields 5122 with data associated with the asset, including asset identifier, product name, serial number, asset label, software version, installation date, and data associated with the 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 the asset at the facility). Figure 5L As further shown, GUI 512 can provide GUI element 5124 for accessing the asset list (e.g., via GUI 504).

[0108] Now for reference Figure 5M , Figure 5M A diagram of GUI 513 showing features related to registered assets (e.g., registering assets to a user-permitted asset list, registering assets to a user profile asset list, etc.). Figure 5M As shown, GUI 513 may include fields 5132 with data associated with the asset, including asset identifier, product name, serial number, asset tag, software version, installation date, commissioning date, and data associated with the 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 the asset at the facility). Figure 5MAs further shown, GUI 513 can provide GUI element 5134 for transmitting data associated with assets provided in GUI 513 for the registration process.

[0109] Now for reference Figure 5N , Figure 5N A diagram of GUI 514 for adding user license-related features associated with assets. (See diagram 514.) Figure 5N As shown, GUI 514 may include fields 5142 with data associated with the asset, including asset identifier, serial number, asset tag, expiry date of user license, and data associated with the 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 the asset at the facility). Figure 5N As further shown, GUI 514 can provide GUI element 5144 for transmitting asset-related data provided in GUI 514 to add user licenses associated with the asset.

[0110] Now for reference Figure 5O , Figure 5O A diagram of GUI 515 for removing features related to user licenses associated with assets. (See diagram 515.) Figure 5O As shown, GUI 515 may include fields 5152 with data associated with the asset, including asset identifier, serial number, asset tag, expiry date of user license, and data associated with the 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 the asset at the facility). Figure 5O As further shown, GUI 515 can provide GUI element 5154 for transmitting asset-related data provided in GUI 514 to remove user licenses associated with the asset.

[0111] For reference Figure 5P , Figure 5P A diagram of GUI 516 related to providing data on consumables used by assets during fluid injection procedures. (See diagram 516 for example.) Figure 5P As shown, GUI 516 may include a field 5162 with data associated with consumables of the asset, including product name and data associated with available consumables of the asset. For example... Figure 5P As further shown, GUI 516 can provide GUI element 5164 for providing links to websites associated with consumables.

[0112] Now for reference Figure 5Q , Figure 5Q A diagram of GUI 517 showing the features related to reading error codes generated from assets. (See diagram 517 for example.) Figure 5Q As shown, GUI 517 can be displayed after the user device reads the QR code providing the error code. Figure 5Q As further illustrated, GUI 517 may include fields 5172 containing data associated with the asset that generated the error code, including product name, serial number, and asset tag. For example... Figure 5Q As further illustrated, the GUI 517 may include multiple fields 5174 for inputting data associated with the error code, including a description of the error code, possible causes of the error code, and possible remedies for the error code. Figure 5Q As further shown, GUI 517 can provide GUI element 5176 for providing links to training content for the asset, and GUI element 5178 for accessing asset features associated with the asset's service tools.

[0113] Now for reference Figure 5R , Figure 5R A diagram of GUI 518 showing the features associated with generating asset service requests. (See diagram 518 for example.) Figure 5R As shown, GUI 518 may include fields 5182 with data associated with the asset, including product name, serial number, asset tag, data associated with the asset location (e.g., facility name and room identifier of the asset location), data associated with the contact person requesting service (e.g., personal name and phone number), and data associated with error codes generated by the asset. Figure 5R As further illustrated, GUI 518 may include a field 5184 for inputting data associated with a symptom of an asset, the reason for the service request, and the severity of the symptom (e.g., high, medium, or low). Figure 5R As further shown, GUI 518 can provide GUI element 5186 for transmitting service requests.

[0114] Now for reference Figure 5S , Figure 5S A diagram of GUI 519 showing the features related to receiving confirmation for generating asset service requests. (See diagram 519 for example.) Figure 5S As shown, GUI 519 may include field 5192 for inputting data associated with confirmation of the service request (e.g., estimated arrival time and comments from the individual who confirmed receipt of the service request). Figure 5S As further shown, GUI519 can provide GUI element 5194 for receiving confirmation of the transmission service request.

[0115] Now for reference Figure 5T , Figure 5T A diagram of GUI 520 showing characteristics related to the status of asset service request provision. (See diagram 520 for example.) Figure 5TAs shown, GUI 520 may include fields 5202 for inputting data associated with the status of a service request (e.g., indication that a service request has been transmitted, indication that a confirmation of receipt of a service request has been transmitted, estimated arrival time, indication that a service request has been completed, data associated with the individual who confirmed receipt of the service request, and fields for inputting data associated with the service request, etc.). Figure 5T As further shown, GUI 520 may include a field 5204 for entering comments about the service request status of an asset.

[0116] Now for reference Figure 5U , Figure 5U A diagram of GUI 521 showing the features related to providing product reports on assets. (See diagram 521.) Figure 5U As shown, GUI 521 may include fields 5212 for providing data associated with notifications related to product reports. In some non-limiting embodiments, GUI 521 may be generated and provided after a service request has been completed.

[0117] Now for reference Figure 5V , Figure 5V A diagram of GUI 522 showing the features related to providing product reports on assets. (See diagram 522.) Figure 5V As shown, GUI 522 may include fields 5222 containing data associated with the asset, including product name, part number (e.g., master part number, material number, etc.), lot number, serial number, asset tag number, data associated with the asset location (e.g., facility name and room identifier of the asset location), and data associated with the contact person for the product report (e.g., individual's name, title, department, telephone number, and email address). Figure 5V As further shown, GUI 522 can provide GUI element 5224 for transmitting product reports.

[0118] Now for reference Figure 5W , Figure 5W A schematic diagram of GUI 523 for requesting features related to components (e.g., parts) providing assets. (See diagram 523 for example.) Figure 5W As shown, GUI 523 may include fields 5232 for inputting data associated with a component request for an asset (e.g., asset identifier, asset serial number, item number, part number, description, indication of whether the component has been replaced, return serial number, and quantity indication). Figure 5W As further shown, GUI 523 can provide GUI element 5234 for transmitting component requests.

[0119] While this disclosure has been described in detail with respect to embodiments currently considered to be most practical and preferred for illustrative purposes, it should be understood that such detailed description is for that purpose only, and that this disclosure is not limited to the disclosed embodiments, but rather is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that this disclosure contemplates that one or more aspects of any embodiment may be combined with one or more aspects of any other embodiment to the extent possible.

Claims

1. A system for accessing a fluid injection system, comprising: At least one processor is programmed or configured to: Authenticating user access to a fluid injection system, wherein the fluid injection system is configured to administer a contrast fluid comprising a contrast agent to a patient, wherein, when authenticating user access to the fluid injection system, the at least one processor is programmed or configured to: A graphical user interface (GUI) is provided on the display screen, which displays an image to be scanned by a user device associated with the user. The login credentials associated with the image are received via a software application used to access the fluid injection system, the software application being on the user device associated with the user. The user's access to the fluid injection system is authenticated by receiving the login credentials via the software application. Based on input received via the software application, data is provided that identifies one or more characteristics of the software application used to access the fluid injection system, wherein the one or more characteristics of the software application include: One or more features associated with providing data related to the fluid injection system, wherein the one or more features associated with providing data related to the fluid injection system include: Features associated with acquiring data related to error codes of the fluid injection system Features associated with generating the service history of the fluid injection system Features associated with the service history of the fluid injection system provided, Features associated with generating the service request for the fluid injection system Features associated with providing operating instructions for the fluid injection system, Features associated with providing data related to the service procedures to be performed on the fluid injection system. Features associated with providing data related to the service procedures performed on the fluid injection system, or Any combination thereof; Receive data identifying selected features of the software application used to access the fluid injection system; Based on authenticating the user's access to the fluid injection system, it is determined whether the user is authorized to access selected features of the software application, wherein, when determining whether the user is authorized to access selected features of the software application, the at least one processor is programmed or configured to: Determine whether the user has an access level that authorizes the user to access the software application based on selected characteristics, wherein the access level is based on the user's user profile; and Based on determining selected features that authorize the user to access the software application, access to selected features of the software application for accessing the fluid injection system is provided.

2. The system according to claim 1, wherein, The at least one processor is further programmed or configured to: The data related to selected features of the software application used to access the fluid injection system is displayed through the graphical user interface (GUI) of the software application on the user device.

3. The system according to claim 1, wherein, The fluid injection system includes the display screen, and wherein the at least one processor is further programmed or configured to: Displays related to the fluid injection system are shown on the display screen of the fluid injection system.

4. The system according to claim 1, wherein, The at least one processor is further programmed or configured to: Accessing selected features of the software application of 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 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.

5. A computer program product for accessing a fluid injection system, the computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising one or more instructions, the one or more instructions causing the at least one processor, when executed by at least one processor, to: Authenticated user access to a fluid injection system, wherein the fluid injection system is configured to administer a contrast fluid comprising a contrast agent to a patient, wherein... The one or more instructions that enable the at least one processor to authenticate the user's access to the fluid injection system cause the at least one processor to: A graphical user interface (GUI) is provided on the display screen, which displays the image to be scanned by the user device. Receive login credentials associated with the image via a software application used to access the fluid injection system, and The user's access to the fluid injection system is authenticated by receiving the login credentials via the software application. Based on input received via the software application, data is provided that identifies one or more characteristics of the software application used to access the fluid injection system, wherein the one or more characteristics of the software application include: One or more features associated with providing data related to the fluid injection system, wherein the one or more features associated with providing data related to the fluid injection system include: Features associated with acquiring data related to error codes of the fluid injection system Features associated with generating the service history of the fluid injection system Features associated with the service history of the fluid injection system provided, Features associated with generating the service request for the fluid injection system Features associated with providing operating instructions for the fluid injection system, Features associated with providing data related to the service procedures to be performed on the fluid injection system. Features associated with providing data related to the service procedures performed on the fluid injection system, or Any combination thereof; Receive data that identifies selected features of the software application used in the fluid injection system; Based on authenticating the user's access to the fluid injection system, it is determined whether the user is authorized to access selected features of the software application, wherein the one or more instructions that cause the at least one processor to determine whether the user is authorized to access the selected features of the software application cause the at least one processor to: Determine whether the user has an access level that authorizes the user to access the software application based on selected characteristics, wherein the access level is based on the user's user profile; and Based on determining selected features that authorize the user to access the software application, access to selected features of the software application for the fluid injection system is provided.

6. The computer program product according to claim 5, wherein, The one or more instructions also cause the at least one processor to: Data associated with selected features of the software application of the fluid injection system is displayed through the graphical user interface (GUI) of the software application on the user equipment.

7. The computer program product according to claim 5, wherein, The fluid injection system includes the display screen, and wherein the one or more instructions further cause the at least one processor to: Displays related to the fluid injection system are shown on the display screen of the fluid injection system.

8. The computer program product according to claim 5, wherein, The one or more instructions also cause the at least one processor to: Accessing selected features of a software application used to access the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system includes data associated with 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 operation of the fluid injection system or the one or more.

9. A method for accessing a fluid injection system, comprising: At least one processor authenticates user access to a fluid infusion system, wherein the fluid infusion system is configured to administer a contrast fluid comprising a contrast agent to a patient, wherein, when authenticating user access to the fluid infusion system, the at least one processor is programmed or configured to: A graphical user interface (GUI) is provided on the display screen, which displays an image to be scanned by a user device associated with the user. The login credentials associated with the image are received via a software application used to access the fluid injection system, the software application being on the user device associated with the user. The user's access to the fluid injection system is authenticated by receiving the login credentials via the software application. Using the at least one processor, data is provided based on input received via the software application to identify one or more features of the software application for accessing the fluid injection system, wherein the one or more features of the software application include: One or more features associated with providing data related to the fluid injection system, wherein the one or more features associated with providing data related to the fluid injection system include: Features associated with acquiring data related to error codes of the fluid injection system Features associated with generating the service history of the fluid injection system Features associated with the service history of the fluid injection system provided, Features associated with generating the service request for the fluid injection system Features associated with providing operating instructions for the fluid injection system, Features associated with providing data related to the service procedures to be performed on the fluid injection system. Features associated with providing data related to the service procedures performed on the fluid injection system, or Any combination thereof; The at least one processor receives data identifying selected features of the software application used to access the fluid injection system; Using the at least one processor, determining whether the user is authorized to access the software application based on selected features of authenticating the user's access to the fluid injection system, wherein the selected features of determining whether the user is authorized to access the software application include: Determine whether the user has an access level that authorizes the user to access the software application based on selected characteristics, wherein the access level is based on the user's user profile; and The at least one processor provides access to selected features of the software application for accessing the fluid injection system based on determining that the user is authorized to access the software application.

10. The method of claim 9, further comprising: Data related to selected features of the software application of the fluid injection system is displayed through the graphical user interface (GUI) of the software application on the user equipment.

11. The method according to claim 9, wherein, The fluid injection system includes the display screen, and the method further includes: Displays related to the fluid injection system are shown on the display screen of the fluid injection system.

12. The method of claim 9, further comprising: Accessing selected features of a software application used to access the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system includes data associated with one or more operations of the fluid injection system; and The method further includes: Record the data related to one or more operations of the fluid injection system.

Images