System, method, and computer program product for implementing a remote console for use in diagnostic imaging procedures

JP2025516233A5Pending Publication Date: 2026-05-11BAYER HEALTHCARE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
BAYER HEALTHCARE LLC
Filing Date
2023-04-27
Publication Date
2026-05-11

AI Technical Summary

Technical Problem

Current diagnostic imaging systems lack an efficient and integrated remote console for managing the delivery of contrast agents and imaging protocols, leading to potential errors and inefficiencies in imaging procedures.

Method used

A system comprising a user interface and at least one processor that integrates an infusion system for delivering fluids and an imaging system, allowing for the receipt and control of treatment data, user input, and automated alerts to ensure precise and efficient operation.

Benefits of technology

The system enhances the accuracy and efficiency of diagnostic imaging procedures by providing real-time data management, automated alerts, and user input control, thereby reducing errors and improving patient outcomes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A system, method, and computer program product for implementing a remote console for use in diagnostic imaging may include a user interface and / or at least one processor, the at least one processor receiving treatment data related to a treatment for a patient from at least one of an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, at least one of the infusion system and the imaging system including at least one additional user interface different from the user interface, the infusion system communicating with the imaging system and providing, via the user interface, a display generated based on the treatment data, receiving, via the user interface, user input, and controlling, based on the user input, the operation of at least one of the infusion system and the imaging system, as programmed and / or configured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 336,512, filed on April 29, 2022, the entire disclosure of which is incorporated herein by reference.

[0002] The present disclosure generally relates to diagnostic imaging and, in some non - limiting embodiments or aspects, to a remote console for use in an imaging diagnostic procedure.

Background Art

[0003] Visualization of various medical conditions is made possible through X - ray, computed tomography, magnetic resonance, or other medical imaging modalities by injecting a contrast agent into a patient's bloodstream. Contrast agent delivery is more effective and efficient using a medical device called a "powered fluid injector system" that can be programmed to deliver a specific amount of contrast agent at a specific flow rate at a specific timing related to image acquisition.

Summary of the Invention

Problems to be Solved by the Invention

[0004] Accordingly, improved systems, devices, products, apparatuses, and / or methods are provided for implementing a remote console for use in an imaging diagnostic procedure.

Means for Solving the Problems

[0005] According to some non-limiting embodiments or aspects, a system is provided that includes a user interface and at least one processor. The system includes an infusion system configured to deliver fluid to a patient and an imaging system configured to scan the patient. The at least one processor is programmed and / or configured to receive treatment data related to a treatment for the patient from at least one of the infusion system and the imaging system. At least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface. The infusion system communicates with the imaging system and provides a display generated based on the treatment data via the user interface, receives user input via the user interface, and controls the operation of at least one of the infusion system and the imaging system based on the user input.

[0006] In some non-limiting embodiments or aspects, the treatment data includes at least one of the following: at least one image captured by a camera associated with at least one of the infusion system and the imaging system, information received via at least one additional user interface, sensor data captured by at least one sensor associated with at least one of the infusion system and the imaging system, or any combination thereof.

[0007] In some non-limiting embodiments or aspects, the treatment data includes at least one image, and the at least one image includes at least one of the following: one or more images of the patient, one or more images of an operator of at least one of the infusion system and the imaging system, one or more images of the patient's IV access location, one or more images of the injector, one or more images of the scanner, or any combination thereof.

[0008] In some non-limiting embodiments or aspects, the treatment data includes information received via at least one additional user interface, and the information received via at least one additional user interface includes at least one of the following, namely, image prescription, pre-treatment checklist, display of patient consent, adverse reaction checklist, selection of injection protocol, programming, and change, selection of imaging protocol, programming, and change, request to start an operation, request to end a treatment, information captured at the end of a treatment, information for secondary acquisition, information for billing procedures, or any combination thereof.

[0009] In some non-limiting embodiments or aspects, the treatment data includes sensor data captured by at least one sensor associated with at least one of an injection system and an imaging system, and the at least one sensor includes at least one of the following sensors, namely, a flow sensor, a temperature sensor, an accelerometer, a vibration sensor, a strain gauge, a motor current sensor, an optical sensor, a scanner, or any combination thereof, and the treatment data includes the following parameters determined based on the sensor data, namely, movement associated with the patient, sound associated with the patient, communication state between the scanner and the injector, one or more images of the patient captured by the scanner, amount of noise associated with one or more images of the patient captured by the scanner, enhancement or saturation level associated with one or more images of the patient captured by the scanner, flow rate during one or more fluid injections by the injector, duration of one or more fluid injections by the injector, volume pumped and / or delivered during one or more injections by the injector, achieved pressure of one or more injections by the injector, imaging signal from a region of interest at a point in time or over a certain period of time, ECG gating sequence, patient's pulse, or any combination thereof.

[0010] In some non-limiting embodiments or aspects, sensor data is captured by at least one sensor during at least one of the following, namely, the setup of at least one of the injector and the scanner, the arming of the injector, the period during which the injector is armed, the keep vein open (KVO) operation by the injector, the delivery of a test bolus and / or a tracking bolus to the patient by the injector, the delivery of a contrast agent to the patient by the injector, the period after the delivery of the contrast agent to the patient, the delivery of a saline flush to the patient by the injector, the period after the delivery of the saline flush to the patient, the scan of the patient by the scanner, or any combination thereof.

[0011] In some non-limiting embodiments or aspects, the display includes an alert, and at least one of the infusion system and the imaging system generates an alert based on at least one of the following, namely, sensor data, user input, patient data associated with the patient, or any combination thereof.

[0012] In some non-limiting embodiments or aspects, the treatment data includes patient data associated with the patient, namely, at least one of the following parameters: age, weight, height, body mass index, cardiac output, risk or probability of an adverse event, adverse event, estimated or measured glomerular filtration rate (eGFR), previous infusion history including one or more reactions to a contrast agent, the location of the patient IV access point, the quality of the patient IV access point, or any combination thereof.

[0013] In some non-limiting embodiments or aspects, the display includes an alert, and at least one of the infusion system and the imaging system generates an alert based on patient data before arming the injector for treatment.

[0014] In some non-limiting embodiments or aspects, at least one processor is further programmed and / or configured to obtain information associated with at least one of a procedure and a patient from at least one of the following, namely, an electronic medical record (EMR) system, a radiology information system (RIS), an image archiving and communication system (PACS), a hospital information system (HIS), a hospital enterprise information system, a cross-location network, or any combination thereof.

[0015] In some non-limiting embodiments or aspects, the user input includes at least one of selection, programming, and modification of at least one of an injection protocol and an imaging protocol.

[0016] In some non-limiting embodiments or aspects, the display includes a prompt for verifying the operation of at least one of an injection system and an imaging system, and at least one processor is programmed and / or configured to control the operation of at least one of the injection system and the imaging system such that the operation of at least one of the injection system and the imaging system is prevented from being executed until a response to the prompt is received via the user interface.

[0017] In some non-limiting embodiments or aspects, the operations include at least one of the following operations, namely, an operation of changing the display of at least one additional user interface, an operation of receiving additional user input via at least one additional user interface, an operation of setting an injection protocol in an injector, an operation of setting an imaging protocol in a scanner, an operation of starting a filling process by the injector, an operation of starting data capture by the injector, an operation of arming the injector, an operation of starting a keep vein open (KVO) procedure by the injector, an operation of starting a saline test injection by the injector, an operation of starting a drug injection by the injector, an operation of starting a contrast agent test injection by the injector, an operation of starting a contrast agent injection by the injector, an operation of starting a saline flush injection by the injector, an operation of starting a scan by the scanner, an operation of aborting a test injection by the injector, an operation of aborting a contrast agent injection by the injector, an operation of aborting a saline flush injection by the injector, an operation of aborting a scan by the scanner, an operation of ending a patient treatment, or at least one of any combination thereof.

[0018] In some non-limiting embodiments or aspects, the operations include at least one of delivering a fluid to a patient using an injector and scanning a patient using a scanner, and at least one processor is programmed and / or configured to control the operation of at least one of an injection system and an imaging system by controlling at least one of the injection system and the imaging system to change and abort the operation.

[0019] In some non-limiting embodiments or aspects, the treatment data includes one or more images of a patient captured by a scanner, and at least one processor is programmed and / or configured to process the one or more images to select a subset of the one or more images, and the display is generated based on the selected subset of the one or more images.

[0020] In some non-limiting embodiments or aspects, the scanner includes at least one of the following, namely, a magnetic resonance (MR) scanner, a computed tomography (CT) scanner, a positron emission tomography / computed tomography (PET / CT) scanner, a positron emission tomography / magnetic resonance (PET / MR) scanner, a positron emission tomography (PET) scanner, a single photon emission computed tomography (SPECT) scanner, an ultrasonic system, an infrared imaging system, a photoacoustic imaging system, or any combination thereof.

[0021] In some non-limiting embodiments or aspects, the injection system, the imaging system, and at least one additional user interface are disposed at the treatment location, and the user interface is disposed at a support location different from the treatment location.

[0022] In some non-limiting embodiments or aspects, the treatment location includes at least one of the following locations, namely, a hospital, an imaging center, a mobile imaging trailer, an outpatient medical facility, a nursing center, a vehicle, or any combination thereof.

[0023] In some non-limiting embodiments or aspects, the user input includes at least one of the following, namely, a response to a prompt for verifying the operation of at least one of the injection system and the imaging system, an instruction to at least one of the injection system and the imaging system for starting, changing, and / or executing the operation of at least one of the injection system and the imaging system, or any combination thereof.

[0024] In some non-limiting embodiments or aspects, the display includes at least one alert, and at least one alert includes, hereinafter, an indication that a procedure has been completed, an indication of whether the procedure has been correctly performed, an indication that the operator appears to be hesitating during programming, a real-time display of measurement parameters associated with fluid injection, a display of detected adverse events, a display of patient discomfort, a display of patient movement, a display of the quality of one or more images of the patient captured by a scanner, or at least one of any combination thereof.

[0025] In some non-limiting embodiments or aspects, at least one processor is programmed and / or configured to receive authentication data associated with a user account from at least one of an injection system and an imaging system via at least one additional user interface, and to restrict the initiation and / or change of one or more operations of at least one of the injection system and the imaging system via at least one additional user interface by the user account based on a permission level associated with the user account, wherein the permission level associated with the user account is determined based on the authentication data.

[0026] In some non-limiting embodiments or aspects, the permission level is further determined based on at least one of the following, namely, some procedures associated with the user account, the quality, experience, and / or other evaluations associated with the user account, the type and / or manner of the procedure, the type of patient, or any combination thereof.

[0027] In some non-limiting embodiments or aspects, the permission level associated with a user account is selected from one of the following permission levels: a first permission level at which the user account is restricted from changing at least one of an infusion protocol and a scan protocol; a second permission level at which the user account is restricted from changing a first subset of parameters of at least one of an infusion protocol and a scan protocol and can change a second subset of parameters of at least one of an infusion protocol and a scan protocol; and a third permission level at which the user account is enabled to change each parameter of at least one of an infusion protocol and a scan protocol.

[0028] According to some non-limiting embodiments or aspects, a method is provided that includes providing a user interface using at least one processor; receiving, using at least one processor, treatment data associated with a treatment for a patient from at least one of an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface and the infusion system is in communication with the imaging system; providing, using at least one processor, a display via the user interface, the display being generated based on the treatment data; receiving, using at least one processor, user input via the user interface; and controlling, using at least one processor, the operation of at least one of the infusion system and the imaging system based on the user input.

[0029] According to some non-limiting embodiments or aspects, a computer program product is provided that includes at least one non-transitory computer-readable storage medium containing program instructions that, when executed by at least one processor, cause the at least one processor to provide a user interface, receive treatment data related to a treatment for a patient from at least one of an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, where at least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface, the infusion system communicates with the imaging system, provide a display generated based on the treatment data via the user interface, receive user input via the user interface, and control the operation of at least one of the infusion system and the imaging system based on the user input.

[0030] Further non-limiting embodiments or aspects are described in the clauses numbered below.

[0031] Clause 1. A system comprising at least one processor programmed and / or configured to receive treatment data related to a treatment for a patient from at least one of a user interface and an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, where at least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface, the infusion system communicates with the imaging system, provide a display generated based on the treatment data via the user interface, receive user input via the user interface, and control the operation of at least one of the infusion system and the imaging system based on the user input.

[0032] Clause 2. The treatment data includes at least one of the following, namely, at least one image captured by a camera associated with at least one of the injection system and the imaging system, information received via at least one additional user interface, sensor data captured by at least one sensor associated with at least one of the injection system and the imaging system, or any combination thereof, for the system described in Clause 1.

[0033] Clause 3. The treatment data includes at least one image, and at least one image includes at least one of the following, namely, one or more images of the patient, one or more images of an operator of at least one of the injection system and the imaging system, one or more images of the patient's IV access location, one or more images of the injector, one or more images of the scanner, or any combination thereof, for the system described in Clause 1 or 2.

[0034] Clause 4. The treatment data includes information received via at least one additional user interface, and the information received via at least one additional user interface includes at least one of the following, namely, image prescription, pre-treatment checklist, display of patient consent, adverse reaction checklist, selection of injection protocol, programming, and changes, selection of imaging protocol, programming, and changes, request to start an operation, request to end a treatment, information captured at the end of a treatment, information for secondary acquisition, information for billing procedures, or any combination thereof, for the system described in any of Clauses 1 to 3.

[0035] Clause 5. The treatment data includes sensor data captured by at least one sensor associated with at least one of the infusion system and the imaging system, and the at least one sensor includes at least one of the following sensors, namely, a flow sensor, a temperature sensor, an accelerometer, a vibration sensor, a strain gauge, a motor current sensor, an optical sensor, a scanner, or any combination thereof. The treatment data includes the following parameters determined based on the sensor data, namely, movement associated with the patient, sound associated with the patient, communication status between the scanner and the injector, one or more images of the patient captured by the scanner, the amount of noise associated with one or more images of the patient captured by the scanner, the enhancement or saturation level associated with one or more images of the patient captured by the scanner, the flow rate during one or more fluid infusions by the injector, the duration of one or more fluid infusions by the injector, the volume pumped and / or delivered during one or more infusions by the injector, the achieved pressure of one or more infusions by the injector, an imaging signal from a region of interest at a point in time or over a certain period of time, an ECG gating sequence, the patient's pulse, or at least one of any combination thereof, for the system according to any one of Clauses 1 to 4.

[0036] Clause 6. The sensor data is captured by at least one sensor during at least one of the following, namely, the setup of at least one of the injector and the scanner, the arming of the injector, the period during which the injector is armed, the keep vein open (KVO) operation by the injector, the delivery of a test bolus and / or a tracking bolus to the patient by the injector, the delivery of a contrast agent to the patient by the injector, the period after the delivery of the contrast agent to the patient, the delivery of a saline flush solution to the patient by the injector, the period after the delivery of the saline flush solution to the patient, the scan of the patient by the scanner, or any combination thereof, for the system according to any one of Clauses 1 to 5.

[0037] Clause 7. The display includes an alert, and at least one of the infusion system and the imaging system generates an alert based on at least one of the following, namely, sensor data, user input, patient data associated with the patient, or any combination thereof, of the system according to any one of Clauses 1 to 6.

[0038] Clause 8. The treatment data includes patient data associated with the patient, namely, at least one of the following parameters: age, weight, height, body mass index, cardiac output, risk or probability of adverse events, adverse events, estimated or measured glomerular filtration rate (eGFR), previous infusion history including one or more allergic reactions to contrast agents, location of the patient's IV access point, quality of the patient's IV access point, or any combination thereof, of the system according to any one of Clauses 1 to 7.

[0039] Clause 9. The display includes an alert, and at least one of the infusion system and the imaging system generates an alert based on patient data before arming the injector for treatment, of the system according to any one of Clauses 1 to 7.

[0040] Clause 10. At least one processor is further programmed and / or configured to obtain information associated with at least one of the treatment and the patient from at least one of the following, namely, an electronic medical record (EMR) system, a radiology information system (RIS), an image archiving and communication system (PACS), a hospital information system (HIS), a hospital enterprise information system, a cross-location network, or any combination thereof, of the system according to any one of Clauses 1 to 8.

[0041] Clause 11. The user input includes at least one of the selection, programming, and modification of at least one of the infusion protocol and the imaging protocol, of the system according to any one of Clauses 1 to 9.

[0042] Clause 12. The display includes a prompt for verifying the operation of at least one of the injection system and the imaging system, and at least one processor controls the operation of at least one of the injection system and the imaging system by controlling at least one of the injection system and the imaging system so that the operation of at least one of the injection system and the imaging system is prevented until a response to the prompt is received via the user interface, and is programmed and / or configured to control the operation of at least one of the injection system and the imaging system as described in any of Clauses 1 to 10.

[0043] Clause 13. The operation includes at least one of the following operations, namely, an operation of changing the display of at least one additional user interface, an operation of receiving additional user input via at least one additional user interface, an operation of setting an injection protocol in the injector, an operation of setting an imaging protocol in the scanner, an operation of starting a filling process by the injector, an operation of starting data capture by the injector, an operation of arming the injector, an operation of starting a keep vein open (KVO) procedure by the injector, an operation of starting a saline test injection by the injector, an operation of starting a drug injection by the injector, an operation of starting a contrast agent test injection by the injector, an operation of starting a contrast agent injection by the injector, an operation of starting a scan by the scanner, an operation of aborting a test injection by the injector, an operation of aborting a contrast agent injection by the injector, an operation of starting a saline flush injection by the injector, an operation of aborting a saline flush injection by the injector, an operation of aborting a scan by the scanner, an operation of ending a patient's treatment, or any combination thereof, and is a system as described in any of Clauses 1 to 11.

[0044] Clause 14. The operation includes at least one of delivering fluid to a patient using an injector and scanning a patient using a scanner, and at least one processor is programmed and / or configured to control the operation of at least one of an infusion system and an imaging system by controlling at least one of the infusion system and the imaging system such that at least one of the infusion system and the imaging system changes and aborts the operation, the system according to any one of Clauses 1 to 13.

[0045] Clause 15. The treatment data includes one or more images of a patient captured by a scanner, and at least one processor is programmed and / or configured to process one or more images to select a subset of the one or more images, and the display is generated based on the selected subset of the one or more images, the system according to any one of Clauses 1 to 14.

[0046] Clause 16. The scanner includes at least one of the following, namely, a magnetic resonance (MR) scanner, a computed tomography (CT) scanner, a positron emission tomography / computed tomography (PET / CT) scanner, a positron emission tomography / magnetic resonance (PET / MR) scanner, a single photon emission computed tomography (SPECT) scanner, an ultrasonic system, an infrared imaging system, a photoacoustic imaging system, or any combination thereof, the system according to any one of Clauses 1 to 15.

[0047] Clause 17. The infusion system, the imaging system, and at least one additional user interface are disposed at the treatment location, and the user interface is disposed at a support location different from the treatment location, the system according to any one of Clauses 1 to 16.

[0048] Clause 18. The treatment location includes at least one of the following locations, namely, a hospital, an imaging center, a mobile imaging trailer, an outpatient medical facility, a nursing center, a vehicle, or any combination thereof, the system according to any one of Clauses 1 to 17.

[0049] Clause 19. The user input includes, among others, at least one of the following: a response to a prompt for verifying the operation of at least one of the injection system and the imaging system, an instruction to at least one of the injection system and the imaging system for starting, changing, and / or executing the operation of at least one of the injection system and the imaging system, or any combination thereof, in the system according to any one of Clauses 1 to 18.

[0050] Clause 20. The display includes at least one alert, and at least one alert includes, among others, at least one of the following: an indication that the treatment is completed, an indication of whether the treatment has been correctly executed, an indication that the operator appears to be hesitating during programming, a real-time display of measurement parameters associated with fluid injection, a display of detected harmful events, a display of the quality of one or more images of the patient captured by the scanner, or any combination thereof, in the system according to any one of Clauses 1 to 19.

[0051] Clause 21. At least one processor is programmed and / or configured to receive authentication data associated with a user account from at least one of the injection system and the imaging system via at least one additional user interface, and based on the privilege level associated with the user account, to restrict the start and / or change of one or more operations of at least one of the injection system and the imaging system via at least one additional user interface by the user account, where the privilege level associated with the user account is determined based on the authentication data, in the system according to any one of Clauses 1 to 20.

[0052] Clause 22. The permission level is further determined based on at least one of the following, namely, several treatments associated with the user account, the quality, experience, and / or other evaluations associated with the user account, the type and / or manner of treatment, the type of patient, or any combination thereof, in the system described in any of Clauses 1 to 21.

[0053] Clause 23. The permission level associated with the user account is selected from one of the following permission levels, namely, a first permission level in which the user account is restricted from changing at least one of the injection protocol and the scan protocol, a second permission level in which the user account is restricted from changing a first subset of the parameters of at least one of the injection protocol and the scan protocol and can change a second subset of the parameters of at least one of the injection protocol and the scan protocol, and a third permission level in which the user account is enabled to change each parameter of at least one of the injection protocol and the scan protocol, in the system described in any of Clauses 1 to 22.

[0054] Step 24. Providing a user interface using at least one processor; receiving, using at least one processor, treatment data associated with a treatment for a patient from at least one of an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface and the infusion system is in communication with the imaging system; providing, using at least one processor, a display via the user interface, the display being generated based on the treatment data; receiving, using at least one processor, user input via the user interface; and controlling, using at least one processor, the operation of at least one of the infusion system and the imaging system based on the user input. A method comprising the above steps.

[0055] Clause 25. A computer program product comprising at least one non-transitory computer-readable storage medium including program instructions that, when executed by at least one processor, cause the at least one processor to provide a user interface; receive treatment data related to a treatment for a patient from at least one of an infusion system including an injector configured to deliver fluid to the patient and an imaging system including a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one additional user interface different from the user interface and the infusion system is in communication with the imaging system; provide a display generated based on the treatment data via the user interface; receive user input via the user interface; and control the operation of at least one of the infusion system and the imaging system based on the user input.

[0056] These and other features and characteristics of the present disclosure, as well as the related elements of the operation methods and structures, functions, combinations of components, and manufacturing economies will become more apparent by considering the following description and the appended claims with reference to the accompanying drawings, all of which are incorporated herein by reference and in which like numerals indicate corresponding parts in the various figures. However, it should be clearly understood that the drawings are for illustrative and explanatory purposes only and are not intended as a definition of limitation. As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

[0057] Further advantages and details will be described in more detail below with reference to the exemplary embodiments shown in the accompanying schematic drawings.

Brief Description of the Drawings

[0058]

Fig. 1A

Fig. 1B

Fig. 2

Fig. 3

Fig. 4A

Fig. 4B

Fig. 4C

Fig. 5

[0059] It should be understood that the present disclosure may contemplate various alternative displacements and step sequences, unless explicitly specified 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 and non-limiting embodiments or aspects. Accordingly, the specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein should not be considered limiting.

[0060] As used herein, terms such as aspects, components, elements, structures, operations, steps, functions, instructions, etc. should not be construed as important or essential unless so explicitly described. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more" and "at least one". Further, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one". The term "one" or a similar term is used when only one item is intended. Also, as used herein, terms such as "has", "have", "having", etc. are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified.

[0061] As used herein, the term "communication" can refer to the reception, receipt, transmission, transfer, provision, etc. of data (e.g., information, signals, messages, instructions, commands, etc.). For one unit (e.g., a device, a system, a component of a device or system, a combination thereof, etc.) to communicate with another unit means that one unit can receive information directly or indirectly from the other unit and / or transmit information to the other unit. This can refer to direct or indirect connections (e.g., direct communication connections, indirect communication connections, etc.) that are essentially wired and / or wireless. Further, two units can communicate with each other even if the transmitted information is modified, processed, relayed, and / or routed between the first unit and the second unit. For example, a first unit can communicate with a second unit even if the first unit receives information passively and does not actively transmit the information to the second unit. As another example, a first unit can communicate with a second unit when at least one intermediate unit processes the information received from the first unit and communicates the processed information to the second unit.

[0062] It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, software, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware can be designed based on the description herein to implement the systems and / or methods.

[0063] Several non-limiting embodiments or aspects can be described herein in relation to a threshold. As used herein, meeting a threshold can refer to a value that is greater than, greater than, higher than, greater than or equal to, less than, less than, lower than, less than or equal to, or equal to the threshold. In some non-limiting embodiments or aspects, there can be multiple thresholds associated with a single parameter or measurement value. For example, during fluid delivery, a pressure higher than a first threshold can indicate a blocked fluid path, and a pressure lower than a second threshold can indicate a leaking and / or damaged fluid path.

[0064] As used herein, the term "computing device" can refer to one or more electronic devices configured to process data. A computing device can, in some examples, include components necessary to receive, process, and output data such as a processor, display, memory, input device, network interface, etc. The computing device can be a mobile device. As an example, a mobile device can include a cellular phone (e.g., a smartphone or a standard cellular phone), a portable computer, a wearable device (e.g., a watch, glasses, lenses, clothing, etc.), a PDA, and / or other similar devices. The computing device can also be a desktop computer or other form of non-mobile computer.

[0065] As used herein, the term "mobile device" can refer to one or more portable electronic devices configured to communicate with one or more networks. By way of example, mobile devices can include cellular phones (e.g., smartphones or standard cell phones), portable computers (e.g., tablet computers, laptop computers, etc.), wearable devices (e.g., watches, glasses, lenses, clothing, etc.), personal digital assistants (PDAs), and / or other similar devices. As used herein, the terms "client device" and "user device" refer to any electronic device configured to communicate with one or more servers or remote devices and / or systems. A client device or user device can include a mobile device, a network-enabled device (e.g., a network-enabled television, refrigerator, thermostat, etc.), a computer, an infusion system, and / or any other device or system capable of communicating with a network.

[0066] As used herein, the terms "server" and / or "processor" can refer to or include one or more computing devices that are operated by or facilitate communication and processing for multiple parties in a network environment such as the Internet, although the communication can be facilitated via one or more public or private network environments and various other configurations are possible. Further, multiple computing devices (e.g., servers, injectors, mobile devices, etc.) that communicate directly or indirectly within a network environment can constitute a "system". References herein to a "server" or "processor" can refer to the servers and / or processors enumerated earlier as performing a previous step or function, different servers and / or processors, and / or combinations of servers and / or processors. For example, as used herein and in the claims, a first server and / or a first processor enumerated as performing a first step or function can refer to the same or different servers and / or processors enumerated as performing a second step or function.

[0067] As used herein, the terms "user interface" or "graphical user interface" refer to a generated display such as one or more graphical user interfaces (GUIs) with which a user can interact directly or indirectly (e.g., via a keyboard, mouse, touch screen, etc.).

[0068] As used herein, terms such as "scan" and "scanning" by, for example, a scanner, refer to obtaining and / or generating one or more information used to create one or more images and / or measurements of a patient, such as a CT scan or an image.

[0069] Non-limiting embodiments or aspects of the present disclosure can provide one or more of the following benefits to its users, their colleagues, their employers, their patients, and / or their patient caregivers. It can enable less experienced users (e.g., technicians, radiologic technologists, nurses, medical assistants, etc.) to complete procedures that these less experienced users have little or no experience with. One more experienced user can assist or supervise multiple less experienced users. All technicians can work like experts. It can enable local and / or "on-the-ground" training for users. It can function as a safety net for new users, reduce stress, and reduce the need for local supervision. They can provide continuous training in the course of normal operations. It can facilitate standardization and protocol optimization. It can help ensure that imaging procedures have sufficient diagnostic quality. It can help maximize throughput. It can help minimize repeat scans if inappropriate. It can help monitor patient safety by having more checks than a single user can provide. It can provide an input to assist the user in determining whether a repeat scan can be attempted. If successful, it can then facilitate the reuse of the same procedure and promote learning. It can enable a virtual imaging expert to operate or manage multiple scanners at geographically different locations that would otherwise require travel and take time. It can monitor performance, e.g., throughput, human factors related to all devices and systems, and overall procedure quality. It can optimize the integration of scanners and injector consoles (e.g., merging or combining two separate user interfaces, etc.). It can reduce duplicate data entry. It can help address a shortage of healthcare workers. It can help redistribute tasks previously performed on a scanner. It can enable each individual involved to focus on core tasks. It can enhance patient convenience and imaging quality. It can facilitate the sharing of expertise within an organization.It is possible to facilitate customer training from two different parties, for example, an injector supplier and an imaging device supplier, simultaneously. For example, better workload leveling or distribution can be achieved, such as eliminating the need for the most experienced person to handle most of the difficult cases. Costs can be reduced by not dispatching full-time / specialist users from one geographical site to another. Patients can undergo scans near their location, eliminating the need to travel to where the specialist is located, thus enhancing patient satisfaction and saving patient time. For example, since the protocol is not restricted by local users' specialists, multiple imaging devices can be utilized better. This can help prevent specialists from being overly dispersed or overworked. Specialists can perform high-level tasks instead of all low-level tasks, thereby enhancing job satisfaction for specialists. It is possible to facilitate real-time consultations regarding outliers or high-risk patients and outlier treatments or new treatments. It is possible to enable local technicians and virtual imaging specialists to have the same situation view regarding the treatment. Options can be provided for either local or remote control of the start of the treatment. Alerts and / or warnings can be provided when the treatment has off-label settings (such as full dose vs. half dose in MR). A step-by-step protocol can be provided for less experienced technicians. A "fourth-eye check" can be provided in relation to the handling of adverse events. This can help facilitate and centralize adverse event reporting. The scanner and injector interfaces can be combined to provide a more unified user interface experience. Local technicians can be enabled to focus more on the patient as well as the patient's comfort and safety. Local technicians can be enabled to focus on the patient and reduce the patient's drop-off during the treatment. It is possible to provide an appearance according to the context of a specific contrast-enhanced scan protocol and incorporate specific injection protocols. It is possible to enable service staff training or cross-training from two parties simultaneously (for example, the organizations of injectors and imaging devices).It can enable remote screening of patients. It can enable local nurses who focus on patients and remote technicians who focus on scanners and protocols. It can provide benefits in terms of sustainability as it enables training without the need for movement. As the number of specialists required to operate the imaging system is increasing, it may be increasingly needed. It can enable access to remote specialists to answer more stringent questions from patients. It can provide guidance across multiple injector systems, for example, injectors from Bayer, Ulrich, Nemoto, etc. They can enable remote consultations with patients to improve compliance and cooperation, thereby reducing "post-scan anxiety". These advantages and features mentioned in this specification of non-limiting embodiments or aspects of the present disclosure can be achieved, for example, by a less experienced user seeking help from a more experienced user, interacting with a more experienced user, and / or providing consultations with a more experienced user. Thereby, a more experienced user can observe and / or propose / intervene in the use of the system by a less experienced user, and / or notify or alert any user that interaction and / or consultation may be beneficial for at least one of the imaging system, injection system, treatment system, support system, local system, and / or their additional devices.

[0070] Referring now to FIG. 1A, FIG. 1A is a diagram of an exemplary environment 100 in which the systems, devices, methods, and / or products described herein may be implemented. As shown in FIG. 1A, the environment 100 can include a support location 101 that includes a support system 102, one or more treatment locations 104 that include one or more treatment systems 106, a database system 108, and / or a communication network 110.

[0071] The support system 102 can include one or more devices that can receive data and / or information from one or more treatment systems 106 and / or communicate data and / or information to one or more treatment systems 106 at one or more treatment locations 104 and / or database systems 108 (e.g., via a communication network 110, etc.). For example, the support system 102 can include one or more computing devices such as one or more computers, portable computers (e.g., tablet computers, etc.), mobile devices (e.g., wearable devices such as mobile phones, smartphones, wristwatches, glasses, lenses, and / or clothing, PDAs, etc.), servers, groups of servers, and / or other similar devices.

[0072] The support system 102 can include a user interface 103 (e.g., an input component 210, an output component 212, etc.). The support location 101 including the support system 102 including the user interface 103 can include a remote console control room, an isolation room, a home office, etc.

[0073] The treatment location 104 can include one or more treatment systems 106 (e.g., a single treatment system 106, multiple treatment systems 106, etc.). For example, the treatment location 104 can include a hospital, an imaging center, a mobile imaging trailer, an emergency vehicle (e.g., an ambulance, etc.), a mobile imaging device (e.g., Hyperfine's Swoop (registered trademark) portable MR imaging system (trademark), etc.), a mobile CT device, etc. As an example, the environment 100 can include a plurality of treatment locations 104 including a plurality of treatment systems 106. In such an example, the plurality of treatment locations 104 can include a plurality of different locations (e.g., a hospital, an imaging center, an ambulance, etc.), and / or the support location 101 can include a location different from the plurality of treatment locations 104.

[0074] Treatment system 106 can include one or more devices that can receive data and / or information from support system 102 and / or database system 108 (e.g., via communication network 110, etc.) and / or communicate data and / or information to support system 102 and / or database system 108. For example, treatment system 106 can include one or more computers, portable computers (e.g., tablet computers, etc.), mobile devices (e.g., wearable devices such as mobile phones, smart phones, wristwatches, glasses, lenses, and / or clothing, PDAs, etc.), servers, groups of servers, and / or other similar devices, such as computing devices.

[0075] Referring also to FIG. 1B here, FIG. 1B is a diagram of exemplary components of treatment system 106. As shown in FIG. 6, the treatment system can include an imaging system 120 including a scanner 122, an injection system 130 including an injector 132, and / or a local system 140. The imaging system 120 including the scanner 122, the injection system 130 including the injector 132, and / or the local system 140 can be interconnected (e.g., establish a connection for communication, etc.) via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. Treatment system 106 can also include devices and / or systems that are not explicitly part of scanner 122 or injector 132, which are also part of a selected treatment, such as patient monitoring devices, anesthesia devices, and / or similar healthcare devices. Such devices can communicate with treatment system 106, local system 140, and / or any system associated with any support system 102. In some non-limiting embodiments or aspects, one or more additional or auxiliary devices (e.g., one or more sensors, patient monitors, infusion pumps, anesthesia devices, biopsy guidance systems, etc.), each of which can include the user interface itself, can be connected to and / or communicate with scanner 122, injector 132, and / or local system 140.

[0076] The imaging system 120 can include one or more devices, software, and / or hardware configured to set an imaging protocol (e.g., scan time, etc.) and acquire non-contrast and contrast-enhanced scans of a patient. For example, the imaging system 120 can include a scanner 122 configured to image a patient according to one or more imaging protocols. As an example, the imaging system 120 can include a magnetic resonance imaging (MRI) system, a computed tomography (CT) system, a positron emission tomography / computed tomography (PET / CT) system, a positron emission tomography / magnetic resonance (PET / MR) system, a positron emission tomography (PET) system, a single photon emission computed tomography (SPECT) system, an ultrasonic system, a radiopharmaceutical therapy (RPT) system, an infrared imaging system, a photoacoustic imaging system, etc. In such an example, the scanner 122 can include a magnetic resonance (MR) scanner, a computed tomography (CT) scanner, a positron emission tomography / computed tomography (PET / CT) scanner, a positron emission tomography / magnetic resonance (PET / MR) scanner, a positron emission tomography (PET) scanner, a single photon emission computed tomography (SPECT) scanner, an ultrasonic system, a radiopharmaceutical therapy (RPT) scanner, an infrared imaging scanner, a photoacoustic imaging scanner, etc. As an example, the imaging system 120 can include an imaging system as described in U.S. Patent Application No. 16 / 710,118, filed on December 11, 2019, the entire content of which is incorporated herein by reference. In some non-limiting embodiments or aspects, the imaging system 120 can include a Siemens Syngo remote console, a Siemens Healthineers Somatom Go CT system, a General Electric Signa MR system, etc.

[0077] In some non-limiting embodiments or aspects, the imaging system 120 includes a system for a standardized MRI examination with patient-centered scan workflow compliance, as described in U.S. Patent Application No. 17 / 458,753, filed August 27, 2021, the disclosure of which is hereby incorporated by reference in its entirety.

[0078] The infusion system 130 may include one or more devices, software, and / or hardware configured to set one or more infusion protocols and deliver one or more fluids (e.g., saline, contrast agent, stress agent, etc.) to a patient according to the one or more infusion protocols. An infusion protocol generally includes one or more phases, each phase specifying two of the one or more fluids being infused and optionally the concentration of the fluid being infused, as well as the flow rate, volume, and duration of that stage of the infusion (e.g., since the volume infused = flow rate × duration, and / or the integral of the flow rate over the infusion duration for more complex protocols, only two independent variables of these three parameters exist). Other infusion parameters that may vary between different phases or be constant across all phases may include at least one of the ratio of the fluids being infused, e.g., the proportion of contrast agent in the total fluid flow rate, pressure limits, pressure limit behavior, flow rate limits, occlusion indication, or any combination thereof. Some injectors may be configured to have one, some, or all time-varying values of the infusion parameters. For example, the infusion system 130 may include an injector 132 configured to deliver one or more fluids (e.g., saline, contrast agent, etc.) to a patient according to one or more infusion protocols. As an example, the infusion system 130 can include a contrast agent infusion system as described in U.S. Patent No. 6,643,537 and / or No. 7,937,134, the entire contents of each of which are hereby incorporated by reference herein, and / or as described in published International Application No. 2019046299. As an example, the infusion system 130 can include the MEDRAD® Stellant FLEX CT infusion system, the MEDRAD® MRXperion MR infusion system, the MEDRAD® Mark 7 arterial infusion system, the MEDRAD® Intego PET infusion system, the MEDRAD® Spectris Solaris EP MR infusion system, the MEDRAD® Stellant CT infusion system, a workstation from With Certegra®, etc.

[0079] In some non-limiting embodiments or aspects, the imaging system 120, the infusion system 130, and / or the local system 140 may include one or more sensors, patient monitors, infusion pumps, anesthesia devices, biopsy guidance systems, and / or one or more additional devices such as the like that can receive, determine, measure, and / or sense sensor data related to, for example, a patient, the scanner 122, the injector 132, and / or an operator. For example, the imaging system 120, the infusion system 130, and / or the local system 140 may include and / or receive sensor data from the following sensors, namely, an image capture device, an accelerometer, a strain gauge, a global positioning system (GPS), a skin resistivity or conductance sensor, a heart rate monitor, a microphone, a heat or temperature sensor, a pulse oximeter, a hydration sensor, a dosimeter, an ultrasonic sensor, an acoustic sensor, and one or more electrodes configured to measure at least one of tissue impedance, electromyogram (EMG), and electrocardiogram (ECG), a microwave sensor, a mechanical impedance sensor, a chemical sensor, a force or pressure sensor, a flow sensor, a vibration sensor, a motor current sensor, an optical sensor, a patient scale, the scanner 122, the injector 132, or any combination thereof. In some non-limiting embodiments or aspects, the imaging system 120, the infusion system 130, and / or the local system 140 may include and / or receive sensor data from one or more sensors described by International Patent Application Publication No. 2021 / 222771, published on November 4, 2021, filed as International Patent Application PCT / US2021 / 030210 on April 30, 2021, the entire contents of which are incorporated herein by reference.

[0080] The local system 140 can include one or more devices that can receive data and / or information from the imaging system 120 and / or the injection system 130, and / or communicate data and / or information to the imaging system 120 and / or the injection system 130. For example, the local system 140 can include computing devices such as one or more computers, portable computers (e.g., tablet computers, etc.), mobile devices (e.g., wearable devices such as mobile phones, smartphones, watches, glasses, lenses, and / or clothing, PDAs, etc.), servers, groups of servers, and / or other similar devices. As an example, the local system 140 can be implemented by and / or associated with a hospital, an imaging center, a mobile imaging trailer, an emergency vehicle (e.g., an ambulance, etc.), a mobile imaging device (e.g., Hyperfine's Swoop (registered trademark) portable MR imaging system (trademark), etc.), a portable or mobile CT device, etc. In some non-limiting embodiments or aspects, the local system 140 can include one or more additional or auxiliary devices (e.g., one or more sensors, patient monitors, infusion pumps, anesthesia equipment, biopsy guidance systems, etc.) that can each include a user interface itself and can be connected and / or communicate with the scanner 122 and / or the injector 132.

[0081] The database system 108 can receive information and / or data from one or more treatment systems 106 at one or more treatment locations 104 and / or support systems 102 (e.g., via a communication network 110, etc.), and / or can communicate information and / or data to one or more treatment systems 106 at one or more treatment locations 104 and / or support systems 102 (e.g., via a communication network 110, etc.), and can include one or more devices. For example, the database system 108 can include one or more computing systems (e.g., one or more computing devices, one or more server computers, one or more mobile computing devices, etc.) including one or more processors. As an example, the database system 108 can include an electronic medical record (EMR) system, a radiology information system (RIS), an image archiving and communication system (PACS), a hospital information system (HIS), a hospital enterprise information system, an insurance or payment information system, a national health information system, a cross-location network, or any combination thereof.

[0082] The communication network 110 can include one or more wired and / or wireless networks. For example, the communication network 110 can be a cellular network (e.g., a Long-Term Evolution (LTE) network, a 3rd generation (3G) network, a 4th generation (4G) network, a 5th generation (5G) network, a 6th generation (6G) network, a Code Division Multiple Access (CDMA) network, etc.), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), a private network, an ad-hoc network, an intranet, the Internet, an optical fiber-based network, a cloud computing network, a short-range wireless communication network (e.g., a Bluetooth (registered trademark) network, a Near Field Communication (NFC) network, etc.), and / or a combination of these or other types of networks.

[0083] The number and arrangement of the devices and systems shown in FIGS. 1A and 1B are provided as an example. There may be additional devices and / or systems, fewer devices and / or systems, different devices and / or systems, or devices and / or systems with an arrangement different from those shown in FIGS. 1A and 1B. Further, two or more devices and / or systems shown in FIGS. 1A and 1B may be implemented within a single device and / or system, or a single device and / or system shown in FIGS. 1A and 1B may be implemented as a plurality of distributed devices and / or systems. Additionally or alternatively, a set of devices and / or systems of the environment 100 and / or the treatment system 106 (e.g., one or more devices or systems) can perform one or more functions described as being performed by another set of devices and / or systems of the environment 100 and / or the treatment system 106.

[0084] Referring now to FIG. 2, FIG. 2 is a diagram of exemplary components of device 200. Device 200 may correspond to one or more of the devices of imaging system 120, injection system 130, local system 140, support system 102, treatment system 106, database system 108, and / or communication network 110. In some non-limiting embodiments or aspects, one or more of the devices of imaging system 120, injection system 130, local system 140, support system 102, treatment system 106, database system 108, and / or communication network 110 may include at least one device 200 and / or at least one component of device 200. As shown in FIG. 2, device 200 can include bus 202, processor 204, memory 206, storage component 208, input component 210, output component 212, and communication interface 214.

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

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

[0087] The input component 210 can include components that enable the device 200 to receive information via user input, etc. (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, a microphone, etc.). Additionally or alternatively, the input component 210 can include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). The output component 212 can include components that provide output information from the device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

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

[0089] Device 200 can execute one or more processes described herein. Device 200 can execute these processes based on a processor 204 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), etc.) that executes software instructions stored by a computer-readable medium such as memory 206 and / or storage component 208. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A non-transitory memory device includes a memory space located within a single physical memory device or a memory space that spans multiple physical memory devices.

[0090] The 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 can cause processor 204 to execute one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to execute one or more processes described herein. Accordingly, the embodiments or aspects described herein are not limited to any particular combination of hardware circuitry and software.

[0091] Memory 206 and / or storage component 208 can include data storage or one or more data structures (e.g., a database, etc.). Device 200 can receive, store, communicate, or search for information stored in a data storage device or one or more data structures within memory 206 and / or storage component 208.

[0092] The number and arrangement of the components shown in FIG. 2 are provided as an example. In some non-limiting embodiments or aspects, device 200 may include additional components, fewer components, different components, or components in a different arrangement than those shown in FIG. 2. 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.

[0093] Referring now to FIG. 3, FIG. 3 is a flowchart of a non-limiting embodiment or aspect of a process 300 for implementing a remote console for use in an image diagnostic procedure. In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., fully, partially, etc.) by support system 102 (e.g., one or more devices of support system 102). In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., fully, partially, etc.) by other devices or groups of devices separate from or including support system 102, such as treatment system 106 (e.g., one or more devices of treatment system 106), database system 108 (e.g., one or more devices of database system 108), imaging system 120 (e.g., one or more devices of imaging system 120), injection system 130 (e.g., one or more devices of injection system 130), and / or local system 140 (e.g., one or more devices of local system 140).

[0094] As shown in FIG. 3, in step 302, process 300 includes receiving treatment data. For example, support system 102 can receive treatment data. As an example, support system 102 can receive treatment data related to a patient's treatment from at least one of infusion system 130 including an injector 132 configured to deliver fluid to the patient and imaging system 120 including a scanner 122 configured to scan the patient. In such an example, support system 102 can receive treatment data related to a patient's treatment from database system 108.

[0095] Support system 102 may include a support user interface 103, and / or at least one of infusion system 130 and imaging system 120 may include at least one additional user interface different from support user interface 103 (e.g., scanner user interface 123 and / or injector user interface 133, etc.). Support system 102 may be disposed at support location 101, and infusion system 130 and imaging system 120 may be disposed at treatment location 104 different from support location 101. For example, support user interface 103 may be disposed at a different location remote from treatment location 104 where scanner user interface 123 and / or injector user interface 133 are disposed. As an example, support location 101 including support system 102 including support user interface 103 can include a remote console control room, an isolation room, a home office, etc., and / or treatment location 104 including scanner 122, scanner user interface 123, injector 132, and injector user interface 133 can include at least one of the locations of a hospital, an imaging center, a mobile imaging trailer, a vehicle, or any combination thereof. In such an example, infusion system 130 can communicate with imaging system 120 (e.g., via a controller area network (CAN), etc.).

[0096] In some non-limiting embodiments or aspects, the support user interface 103, as well as the scanner user interface 123 and the injector user interface 133, enable an operator or local technician (e.g., a radiologic technologist, radiation therapist, medical assistant, etc.) at the treatment position 104 to communicate continuously, regularly, and / or as needed with a user or virtual imaging expert (e.g., a radiologist, assistant, experienced radiologic technologist, etc.) at the support position 101 (e.g., via a headset communication unit, via a chat window on the UI display, etc.).

[0097] The treatment data can include at least one of the following, namely, at least one image captured by an image capture device (e.g., a camera, etc.) associated with at least one of the injection system 130 and the imaging system 120, information received via the scanner user interface 123 and / or the injector user interface 133, sensor data captured by at least one sensor associated with at least one of the injection system 130 and the imaging system 120, user input received via the support user interface 103, patient data, or any combination thereof. In some non-limiting embodiments or aspects, the treatment data includes information and / or data automatically collected by the support system 102 during use by a user of the injection system 130 including the injector 132 and / or the imaging system 120 including the scanner 122, such as indirect user input including usage metrics, user selections, etc.

[0098] Images captured by an image capture device (e.g., a camera, etc.) associated with at least one of the injection system 130 and the imaging system 120 may hereinafter include at least one of the following, i.e., one or more images of a patient, one or more images of an operator of at least one of the injection system 130 and the imaging system 120 (e.g., the injector 132 and / or the scanner 122, etc.), one or more images of the patient's IV access location, one or more images of the injector 132, one or more images of the scanner 122, or any combination thereof. For example, the injection system 130, the imaging system 120, and / or the local system 140 may include an image capture device configured to monitor the environment (e.g., a scan room, a control room, etc.) surrounding the injector 132 and / or the scanner 122.

[0099] Information received via the scanner user interface 123 and / or the injector user interface 133 may hereinafter include at least one of the following, i.e., an image prescription, a pre-treatment checklist, a display of patient consent, a harmful reaction checklist, a selection of an injection protocol, programming, and at least one of changes, a selection of an imaging protocol, programming, and at least one of changes, a request to start an operation, a request to end a treatment, information captured at the end of a treatment, information for secondary acquisition, information for a billing procedure, or any combination thereof.

[0100] Sensor data can include parameters related to the patient, scanner 122, injector 132, additional or auxiliary devices, and / or the operator. For example, sensor data related to the patient, scanner 122, injector 132, and / or the operator can include, among other things, movement related to the patient during the procedure, sounds related to the patient during the procedure (e.g., crying out for help, etc.), patient weight on the scanner 122, scan timing of the scanner 122, communication status between the scanner 122 and the injector 132, one or more images or scans of the patient captured by the scanner 122, amount of noise associated with one or more images or scans of the patient captured by the scanner 122 (e.g., signal-to-noise ratio (SNR), etc.), artifacts associated with one or more images or scans of the patient captured by the scanner 122 (e.g., level of artifacts, number of artifacts, etc.), enhancement or saturation level associated with one or more images or scans of the patient captured by the scanner 122, imaging signal from a region of interest at a single point in time or over a certain period of time, maintenance status of the scanner 122, flow rate during one or more injections by the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), ECG gating sequence, patient pulse, flow rate programmed to be achieved for one or more injections by the injector 132, volume pumped and / or delivered during one or more injections by the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), volume programmed to be delivered during one or more injections by the injector 132, duration of one or more injections by the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), difference between the flow rate during one or more injections by the injector 132 and the programmed flow rate (e.g., set by injection parameters of the injection protocol, etc.) for one or more injections, difference between the volume pumped and / or delivered during one or more injections by the injector 132 and the programmed volume (e.g., set by injection parameters of the injection protocol, etc.) to be pumped and / or delivered during one or more injections, number of injections by the injector 132, achieved pressure during one or more injections by the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.),The difference between the achieved pressure during one or more injections by the injector 132 and the pressure programmed to be achieved (e.g., set by injection parameters of an injection protocol, etc.), the pressure limit or threshold at which the injection system is programmed to stop the delivery of the injection by the injector 132 if it is exceeded, the period during which the power is on (e.g., maximum value, minimum value, average value, total value, etc.), the number of times the power has been cycled for the scanner 122 and / or the injector 132, the energy consumption of the scanner 122 and / or the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), the linear amount of power delivered or used by the scanner 122 and / or the injector 132 (e.g., the integral of ((pressure)*(flow rate)) / (time), etc.), the non-linear amount of power delivered or used by the scanner 122 and / or the injector 132 (e.g., the integral of f(pressure)*(time), etc.), the voltage in the scanner 122 and / or the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), the resistance in the scanner 122 and / or the injector 132, the current in the scanner 122 and / or the injector 132, the noise or signal level in the scanner 122 and / or the injector 132, the mechanical force generated by the motor of the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), the number of camera reads, the number and / or type of error codes received by the scanner 122 and / or the injector 132, the number, duration and / or type of user interface keys actuated (e.g., pressed) on the scanner 122 and / or the injector 132, the power line status associated with the scanner 122 and / or the injector 132, the temperature and / or humidity inside the scanner 122 and / or the injector 132 (e.g., set by injection parameters of an injection protocol, etc.), the temperature and / or humidity of the environment surrounding the scanner 122 and / or the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), the vibration frequency and / or amplitude of the scanner 122 and / or the injector 132 (e.g., maximum value, minimum value, average value, total value, etc.), the number of times the scanner 122 and / or the injector 132 is cleaned, the wear staff evaluation of the scanner 122 and / or the injector 132 (e.g.,Staff evaluations of the cleanliness of the scanner 122 and / or injector 132 (e.g., numerical evaluations, etc.), service records of the service of the scanner 122 and / or injector 132 (e.g., the number of services performed, the types of services performed, etc.), system evaluations of wear associated with the scanner 122 and / or injector 132 (e.g., numerical evaluations, etc.), system evaluations of cleanliness associated with the scanner 122 and / or injector 132 (e.g., numerical evaluations, etc.), the number of one or more disposable supplies (e.g., syringes, transfer sets, single-use, multiple-use, etc.) sold at and / or used by the associated treatment location 104, the amount of contrast agent used by the injector 132, the type of contrast agent used by the injector 132, the vial size of the contrast agent used by the injector 132, the number of injectors at the treatment location 104, the rotation rate of the user or operator associated with the treatment location 104, the identifier of the user or operator associated with one or more operations or uses of the scanner 122 and / or injector 132, the identifier of the customer associated with the treatment location 104, the indication of liquid within the scanner 122 and / or injector 132 (e.g., as detected or measured by one or more liquid sensors, etc.), the amount of X-ray radiation, RF exposure, magnetic field exposure, etc. (e.g., maximum value, minimum value, average value, total value, etc.) in the environment surrounding the scanner 122 and / or injector 132, one or more injection protocols used for one or more injections, one or more imaging protocols used for one or more scans, etc., can include at least one of them.,

[0101] In some non-limiting embodiments or aspects, the sensor data associated with the injector 132 includes one or more exemplary data types, information types, and / or parameters disclosed in U.S. Patent Application No. 10 / 143,562, filed May 10, 2002, and issued as U.S. Patent No. 7,457,804; U.S. Patent Application No. 12 / 254,318, filed October 20, 2008, and issued as U.S. Patent No. 7,996,381; U.S. Patent Application No. 13 / 180,175, filed July 11, 2011, and published as U.S. Patent Publication No. 8,521,716; International Patent Application Publication No. 2017 / 027724, filed April 6, 2016, and published February 16, 2017; and International Patent Application Publication No. 2017 / 040152, filed August 24, 2016, and published March 9, 2017, the entire disclosures of each of which are incorporated herein by reference.

[0102] In some non-limiting embodiments or aspects, sensor data related to a patient can include at least one of the following parameters: first, parameters that can be affected by infusion and / or changes in the patient's health status, such as heart rate, sound or vibration (e.g., sound or vibration related to fluid inflow, sound or vibration near the injection site, etc.), temperature (e.g., temperature of fluid inflow, temperature near the injection site, local temperature, tissue temperature, etc.), oxygen saturation (e.g., oxygen saturation of fluid inflow, oxygen saturation near the injection site, etc.), pulse rate, ECG, body fat / hydration ratio, tissue impedance, blood vessel distribution level, blood vessel diameter, hydration level, hematocrit value, skin resistivity, blood pressure, muscle tension level, light absorption rate level, sway or tremor, or movement / motion (e.g., yes, no, level, etc.), arm position, arm circumference, respiratory rate, respiratory depth, amount of radiation absorbed, airtightness of the contact sensor device, position stability, and / or contact integrity, amount of swelling and / or displacement, EMG, skin color, amount of surface vasodilation (flushing), bioimpedance, light absorption rate, inflammation level, etc.; second, parameters that are less likely to be directly affected by infusion and / or changes in the patient's health status, such as fat / muscle ratio, hemoglobin level, etc.; third, environmental parameters such as the environmental temperature of the environment surrounding the patient, the atmospheric pressure of the environment surrounding the patient, ambient light level, ambient sound level, etc., or any combination thereof.

[0103] In some non-limiting embodiments or aspects, the support system 102 can determine sensor data to compare the expected performance between contrast agents using a concentration / viscosity ratio, as described in "Impact of CT Injector Technology and Contrast Media Viscosity on Vascular Enhancement: Evaluation in a Circulation Phantom" by McDermott M, Kemper C, Barone W, Jost G, Endrikat J., the entire disclosure of which is incorporated herein by reference, Br J Radiol., May 1, 2020; 93(1109):20190868.doi:10.1259 / bjr.20190868, Epub Feb 20, 2020, PMID:32017607, PMCID:PMC7217576.

[0104] In some non-limiting embodiments or aspects, the treatment data may include at least one of the following conditions determined based on sensor data: overpressure relief of the injector 132, premature termination of injection by the injector 132, unexpected injection timing related to one or more fluid injections by the injector 132, unexpected scan timing related to one or more scans by the scanner 122, indication that injection was not performed when expected, injection flow rate violating a threshold flow rate, injection volume violating a threshold volume, injection pressure violating a threshold pressure, violation of a catheter rule set, violation of a pediatric injector guardrail, dropout or error of a communication interface in the scanner 122 and / or the injector 132, amount of noise (e.g., signal-to-noise ratio (SNR), etc.) related to one or more images or scans of a patient captured by the scanner 122 that violates a threshold noise level, occurrence of artifacts (e.g., level of artifacts, number of artifacts, etc.) related to one or more images or scans of a patient captured by the scanner 122, expansion or saturation level related to one or more images or scans of a patient captured by the scanner 122 that violates a threshold expansion or saturation level, venous contamination, leakage or breakage of a fluid path shown and / or associated in a pressure curve, premature enhancement, patient movement, patient adverse reaction, maintenance status related to the scanner 122 and / or the injector 132, inexperienced operator (e.g., operator hesitation, programming statistics, etc.), activation of a help button, extravasation related to one or more injections, air injection related to one or more injections, occlusion related to one or more injections, patency of an IV line, impedance of the injector 132 that violates a threshold impedance (e.g., for predicting pressure limits, etc.), or any combination thereof.

[0105] In some non-limiting embodiments or aspects, sensor data is captured by at least one sensor during at least one of the following, namely, the settings of the injector 132 and / or the scanner 122, the arming of the injector 132, the period during which the injector 132 is armed, the keep vein open (KVO) operation by the injector 132, the delivery of a test bolus and / or a tracking bolus to the patient by the injector 132, the delivery of a contrast agent to the patient by the injector 132, the period after the delivery of the contrast agent to the patient, the delivery of a saline flush to the patient by the injector, the period after the delivery of the saline flush to the patient, the scan of the patient by the scanner, or any combination thereof.

[0106] In some non-limiting embodiments or aspects, the treatment data includes patient data. The patient data includes the following parameters related to the patient, namely, age, gender, weight, height, body mass index (BMI), cardiac output, type of treatment being performed, previous chemotherapy status such as harmful peripheral vein conditions due to long-term oncological treatment (e.g., "yes", "no", number of chemotherapy cycles received, etc.), estimated glomerular filtration rate (eGFR) (e.g., 45 ml / min / 1.73 m 2Less than eGFR, etc.), previous injection history including one or more allergic reactions to contrast agents, thyroid stimulating hormone (TSH) level, triiodothyronine (FT3) / thyroxine (FT4) ratio (FT3 / FT4), amount or level of environmental impact (e.g., regional iodine saturation amount or level in the area related to the patient's region or location, etc.), previous reaction to previous contrast agent injection state (e.g., yes, no, level, etc.), state of atopic disorder (e.g., yes, no, level, etc.), medical conditions related to the presence of diabetes and / or hypertension such as the state of diabetic nephropathy (e.g., yes, no, level, etc.), congestive heart failure state (e.g., yes, no, level, etc.), hematocrit value, known or suspected renal insufficiency state (e.g., yes, no, level, etc.), malignant tumor state (e.g., yes, no, level, etc.), implanted device for central venous access state (e.g., yes, no, level, etc.), type of drug, type of contrast agent administered in contrast agent injection, type of contrast agent injection and / or imaging examination, flow rate related to contrast agent injection, catheter gauge related to contrast agent injection, total volume of fluid related to contrast agent injection, pressure curve related to contrast agent injection, injection site related to contrast agent injection, location of the patient's IV access point, quality of the patient's IV access point (defined, for example, by the level of expertise of the technician related to the installation of the IV access point), or at least one of any combination thereof. In some non-limiting embodiments or aspects, the patient data can include sensor data determined before the contrast agent injection is administered to the patient and / or sensor data determined during and / or after one or more previous contrast agent injections previously administered to the patient.

[0107] In some non-limiting embodiments or aspects, the support system 102 obtains information related to at least one of a treatment and a patient (e.g., treatment data, patient data, etc.) from one or more database systems 108. For example, the support system 102 can obtain information associated with at least one of a treatment and a patient from at least one of the following, namely, an electronic medical record (EMR) system, a radiology information system (RIS), an image archiving and communication system (PACS), a hospital information system (HIS), a hospital enterprise information system, a cross-location network, or any combination thereof.

[0108] As shown in FIG. 3, in step 304, the process 300 includes providing a display via a user interface. For example, the support system 102 can provide a display via a user interface. As an example, the support system 102 can provide a display via the user interface 103. In such an example, the display can be generated based on treatment data.

[0109] In some non-limiting embodiments or aspects, the display provided via the support user interface 103 may include an alert. For example, the infusion system 130 and / or the imaging system 120 may generate an alert based on at least one of the following, namely, treatment data, patient data, sensor data, user input received via the support user interface 103, user input received via the scanner user interface 123 and / or the injector user interface 133, or any combination thereof. As an example, the alert may be associated with one or more of the parameters or conditions described herein, determined based on treatment data, patient data, sensor data, user input received via the support user interface 103, and / or user input received via the scanner user interface 123 and / or the injector user interface 133. In such an example, the display can include an alert, and / or the infusion system 130 and / or the imaging system 120 can generate an alert based on patient data before arming the injector 132 for treatment.

[0110] Alerts provided via the support user interface 103 can include at least one of the following, namely, an indication that the treatment is complete, an indication of whether the treatment was performed correctly, a sound emitted by the scanner 122 replicated by the support system 102, an indication that the operator appears to be hesitating during programming, an indication of whether the operator is looking at the correct injector at the correct patient and treatment location, a real-time display of infusion parameters (e.g., pressure graph, infusion phase, etc.), an indication of an adverse event (e.g., extravasation, etc.), the selected infusion protocol, the selected imaging protocol, an indication of the quality of one or more images of the patient captured by the scanner 122, or any combination thereof.

[0111] In some non-limiting embodiments or aspects, the display provided via the support user interface 103 may mirror the display provided via the scanner user interface 123 and / or the injector user interface 133. In some non-limiting embodiments or aspects, the support user interface 103, the scanner user interface 123, and / or the injector user interface 133 can include an independent workflow recognition user interface as described in U.S. Patent No. 11,090,440, published August 17, 2021, the entire disclosure of which is incorporated herein by reference.

[0112] In some non-limiting embodiments or aspects, the display provided via the support user interface 103 includes prompts for verifying or approving the operation of the scanner 122 and / or the injector 132. For example, the operations can include operations to change the display of the scanner user interface 123 and / or the injector user interface 133, operations to receive further user input via the scanner user interface 123 and / or the injector user interface 133, operations to set an injection protocol in the injector 132, operations to set an imaging protocol in the scanner 122, operations to start a loading process by the injector 132, operations to start data capture by the injector 132, operations to arm the injector 132, operations to start a keep vein open (KVO) procedure by the injector 132, operations to start a saline test injection by the injector 132, operations to start a drug injection by the injector 132, operations to start a contrast agent test injection by the injector 132, operations to start a contrast agent injection by the injector 132, operations to start a scan by the scanner 122, operations to abort a test injection by the injector 132, operations to abort a contrast agent injection by the injector 132, operations to abort a scan by the scanner 122, operations to start a saline flush injection by the injector, operations to abort a saline flush injection by the injector, operations to end a patient treatment, or at least one of any combination thereof. As an example, the operations and / or the displays associated therewith can include one or more of the operations described in U.S. Patent No. 11,232,862, published January 25, 2022, the entire disclosure of which is incorporated herein by reference, and can be used for predictive maintenance of the infusion system. In some non-limiting embodiments or aspects, the contrast agent injection can include dual-flow injection in which controlled ratios of each of the contrast agent and saline are delivered together simultaneously or sequentially in a bolus small enough for the contrast agent and saline to be effectively mixed before being imaged.

[0113] In some non-limiting embodiments or aspects, the operation of the injector 132 can include delivering a test bolus and / or determining an injection protocol based thereon, as described in International Patent Application Publication No. 2020 / 247370, published December 10, 2020, filed as International Patent Application PCT / US2020 / 035699 on June 2, 2020, the entire disclosure of which is incorporated herein by reference.

[0114] In some non-limiting embodiments or aspects, the treatment data can include one or more images (and / or one or more segments thereof) of a patient captured by the scanner 122, and / or the support system 102 (and / or the imaging system 120, etc.) can process one or more images to select a subset of the one or more images, and / or the support system 102 can generate a display based on the selected subset of the one or more images. For example, the support system 102 (and / or the imaging system 120, etc.) can process one or more images using a machine learning model and / or other image processing algorithms and select a subset of the one or more images according to one or more quality controls or thresholds.

[0115] Referring also to FIGS. 4A-4C, FIGS. 4A-4C illustrate an implementation 400 of a non-limiting embodiment or aspect of a user interface of a remote console for use in an image diagnostic procedure. As shown in FIG. 4A, the support system 102 can provide a display via the user interface 103. For example, the display can include a plurality of segmented displays or sections corresponding to a plurality of treatment systems 106 (e.g., system A, system B, system C, system D, etc.). As an example, the segmented display or section corresponding to each treatment system 106 can be generated based on treatment data associated with and / or received from that treatment system 106. For example, as shown in FIG. 4A, the segmented display or section of each treatment system 106 can include one or more of a real-time display or live video feed of each location, which can be in various treatment states, one or more alerts associated with each location, a mirrored scanner user interface associated with each location, a mirrored injector user interface associated with each location, etc.

[0116] As further shown in FIG. 4A, the segmented displays or sections of each treatment system 106 may be the same or similar in size to other sections. For example, the support system 102 can provide a display via the user interface 103 in a way that does not explicitly draw the attention of the virtual imaging expert monitoring the plurality of treatment systems 106 to one treatment system 106 more than to other treatment systems. However, the support system 102 can automatically provide, via the user interface 103, a display having one or more of the segmented displays or sections for one or more of the treatment systems 106 in an enlarged or zoomed way compared to other segmented displays or sections for other treatment systems based on treatment data. For example, as shown in FIG. 4B, the support system 102 can automatically provide, via the user interface 103, the segmented display or section of System B in an enlarged, zoomed, and / or highlighted way compared to other segmented displays or sections for other treatment systems based on treatment data. As an example, the support system 102 can, in response to at least one of generating or receiving an alert associated with System B, generating or receiving a prompt for verifying or approving the operation of the scanner 122 and / or injector 132 of System B, receiving user input via the user interface 103, receiving user input via the scanner user interface 123 and / or injector user interface 133, any combination thereof, etc., automatically provide, via the user interface 103, the segmented display or section for System B on the display in an enlarged, zoomed-in, and / or highlighted way.For example, the support system 102 may be configured to automatically draw the attention of a virtual imaging expert who monitors a plurality of treatment systems 106 to a treatment system 106 or its operator that currently and / or most urgently requires input and / or assistance from the virtual imaging expert, such as for the virtual imaging expert to confirm the operation of the imaging system 120 and / or the injection system 130 before its start.

[0117] The support system 102 can automatically provide, via the user interface 103, a portion of the segmented display or one of the sections for one or more of the treatment systems 106 in an enlarged or zoomed manner compared to other portions of the segmented display or section based on treatment data. For example, as shown in FIGS. 4B and 4C, the support system 102 can automatically provide, via the user interface 103, a portion of the segmented display or section of System B in an enlarged, zoomed-in, and / or highlighted manner compared to other portions based on treatment data. As an example, the support system 102 can generate or receive an alert associated with System B, generate or receive a prompt for verifying or approving the operation of scanner 122 and / or injector 132 of System B, receive user input via the user interface 103, receive user input via the scanner user interface 123 and / or injector user interface 133, and in response to at least one of these, such as any combination thereof, automatically provide, via the user interface 103, a portion of the segmented display or section for System B in an enlarged, zoomed-in, and / or highlighted manner. For example, the support system 102 can be configured to automatically draw the attention of a virtual imaging expert monitoring System B to information and / or data related to current alerts and / or prompts to be addressed in System B, such as for the virtual imaging expert to verify the operation of the imaging system 120 and / or injection system 130 before its start as shown in FIG. 4B and to monitor the operation of the imaging system 120 and / or injection system 130 during its execution as shown in FIG. 4C.

[0118] As shown in FIG. 3, in step 306, process 300 includes receiving user input via a user interface. For example, support system 102 can receive user input via a user interface. As an example, support system 102 can receive user input via support user interface 103.

[0119] In some non-limiting embodiments or aspects, the user input includes at least one of selection, programming, and modification of at least one of an injection protocol and an imaging protocol. For example, support system 102 and / or injection system 130 can adjust at least one of a maximum flow rate, maximum pressure, injection duration, total volume of fluid, or any combination thereof of fluid injection based on the user input.

[0120] In some non-limiting embodiments or aspects, the user input includes a response (e.g., confirmation, rejection, etc.) to a prompt for verifying or approving the operation of scanner 122 and / or injector 132. For example, if support user interface 103 includes a display including a prompt for verifying the operation of imaging system 120 and / or injection system 130, support system 102 may receive a response from the user via support user interface 103 for verifying or rejecting the operation.

[0121] In some non-limiting embodiments or aspects, the user input includes instructions to the scanner 122 and / or the injector 132 to start, modify, and / or execute the operation of the scanner 122 and / or the injector 132. For example, the user input may include operations to change the display of the scanner user interface 123 and / or the injector user interface 133, operations to receive further user input via the scanner user interface 123 and / or the injector user interface 133, operations to set an injection protocol (e.g., phase, volume, flow rate, pressure limit, type of fluid, etc.) in the injector 132, operations to set an imaging protocol in the scanner 122, operations to start a loading process by the injector 132, operations to start data capture by the injector 132, operations to arm the injector 132, operations to start a keep vein open (KVO) procedure by the injector 132, operations to start a saline test injection by the injector 132, operations to start a drug injection by the injector 132, operations to start a contrast agent test injection by the injector 132, operations to start a contrast agent injection by the injector 132, operations to start a scan by the scanner 122, operations to abort a test injection by the injector 132, operations to abort a contrast agent injection by the injector 132, operations to abort a scan by the scanner 122, operations to start a saline flush injection by the injector, operations to abort a saline flush injection by the injector, operations to end a patient treatment, or instructions to the scanner 122 and / or the injector 132 to start, modify, and / or execute at least one of any combination thereof. As an example, the operations and / or the user input related thereto can include one or more of the operations described in U.S. Patent No. 11,232,862, published on January 25, 2022, the entire disclosure of which is incorporated herein by reference.

[0122] In some non-limiting embodiments or aspects, the user input includes injection protocol parameters (e.g., phase, volume, flow rate, pressure limit, etc.), the type of fluid related to fluid delivery (e.g., type of contrast agent, saline, etc.), quality assurance guardrail parameters, patient health information (e.g., CIN risk, allergies, etc.), air check confirmation, checkboxes for patient characteristics to guide protocol selection, one or more safety inputs, checks, and / or stops, documentation of adverse events, the location and / or method of IV access, or any combination thereof. In some non-limiting embodiments or aspects, the user input includes system-enabled communication between a first user at scanner 122 and a second user at a support system 102 (e.g., remote console, etc.), such as voice communication in the scanner space or console, voice capture and camera capture (optionally with a display of the user at work), video conferencing communication, text communication, etc.

[0123] In some non-limiting embodiments or aspects, the user input can include any of the user inputs described by International Patent Application Publication No. 2021 / 222771, published on November 4, 2021, which was filed as International Patent Application PCT / US2021 / 030210 on April 30, 2021, the entire contents of which are incorporated herein by reference.

[0124] As shown in FIG. 3, in step 308, process 300 includes controlling the operation of the injection system and / or the imaging system based on user input. For example, support system 102 may control the operation of the injection system and / or the imaging system based on user input. As an example, support system 102 may control the operation of at least one of the injection system and the imaging system based on user input. In such an example, support system 102 may control injection system 130 and / or imaging system 120 to perform at least one of modifying and aborting the operation. As an example, support system 102 may control injection system 130 to change or abort an operation including delivering fluid to a patient using injector 132. As an example, support system 102 may control imaging system 120 to change or abort an operation including scanning a patient using scanner 122.

[0125] In some non-limiting embodiments or aspects, the support system 102 controls the scanner 122 and / or the injector 132 based on user input to perform the following operations, namely, changing the display of the scanner user interface 123 and / or the injector user interface 133, receiving further user input via the scanner user interface 123 and / or the injector user interface 133, setting the injection protocol in the injector 132, setting the imaging protocol in the scanner 122, starting the loading process by the injector 132, starting data capture by the injector 132, arming the injector 132, starting a keep vein open (KVO) procedure by the injector 132, starting a saline test injection by the injector 132, starting a drug injection by the injector 132, starting a contrast agent test injection by the injector 132, starting a contrast agent injection by the injector 132, starting a scan by the scanner 122, aborting a test injection by the injector 132, aborting a contrast agent injection by the injector 132, aborting a scan by the scanner 122, starting a saline flush injection by the injector, aborting a saline flush injection by the injector, ending the patient's treatment, or starting and / or executing at least one of any combination thereof.

[0126] In some non-limiting embodiments or aspects, if the display of the support user interface 103 includes a prompt for verifying the operation of the injection system 130 and / or the imaging system 120, the support system 102 may control the operation of the injection system 130 and / or the imaging system 120 by preventing the injection system 130 and / or the imaging system 120 from performing the operation until a response to the prompt is received via the support user interface 103.

[0127] In some non-limiting embodiments or aspects, the support system 102 receives authentication data (e.g., username, password, etc.) associated with a user account (e.g., an operator's user account, etc.) from the injection system 130 and / or the imaging system 120 via the injector user interface 133 and / or the scanner user interface 123. For example, the support system 102 may restrict one or more operations of the injection system 130 and / or the imaging system 120 from being initiated and / or changed by the user account via the injector user interface 133 and / or the scanner user interface 123 based on the privilege level associated with the user account. As an example, the support system 102 can determine the privilege level associated with the user account on the authentication data. In such an example, the privilege level associated with the user account may be selected from one of the following privilege levels, namely, a first privilege level where the user account is restricted from changing at least one of the injection protocol and the scan protocol, a second privilege level where the user account is restricted from changing a first subset of at least one parameter of the injection protocol and the scan protocol and can change a second subset of at least one parameter of the injection protocol and the scan protocol, and a third privilege level where the user account is enabled to change each parameter of at least one of the injection protocol and the scan protocol.

[0128] In some non-limiting embodiments or aspects, the support system 102 may further determine the privilege level associated with the user account based on at least one of the following, namely, some procedures associated with the user account, the quality, experience, and / or other evaluations associated with the user account, the type and / or manner of the procedure, the type of patient, or any combination thereof.

[0129] In some non-limiting embodiments or aspects, the treatment system 106 can include a failsafe that fails in a mode where the treatment system 106 can operate locally to take images or inject contrast agents (e.g., such that the imaging system 120 and the injection system 130 can still operate locally) if communication with the support system 102 fails and / or if some other aspect of the support system 102 fails.

[0130] Referring now to FIG. 5, FIG. 5 is a diagram of an implementation 500 of a non-limiting embodiment or aspect of a process for implementing a remote console for use in an image diagnostic procedure. As shown in FIG. 5, the implementation 500 includes a support system 502, a treatment system 506, an imaging system 520, and / or an injection system 530. In some non-limiting embodiments or aspects, the support system 502 can be the same as or similar to the support system 102. In some non-limiting embodiments or aspects, the treatment system 506 can be the same as or similar to the treatment system 106. In some non-limiting embodiments or aspects, the imaging system 520 can be the same as or similar to the imaging system 120. In some non-limiting embodiments or aspects, the injection system 530 can be the same as or similar to the injection system 130.

[0131] As shown by reference numeral 550 in FIG. 5, the support system 502 can provide a patient display to a virtual imaging expert (e.g., a remote user) (e.g., in response to the patient arriving at the location of the treatment system 506). For example, a radiologic technologist (and / or a medical assistant, local user, etc.) at the location of the treatment system 506 can meet the patient and confirm the patient's identity, and the virtual imaging expert can simultaneously confirm the patient's identity and / or advise the radiologic technologist via the support system 502. A treatment prescription (e.g., CT liver treatment / examination, MR heart treatment / examination, etc.), a pre-treatment checklist, and / or patient characteristics may be obtained by the treatment system 506 and / or input or imported by the radiologic technologist from an EHR and / or EMR system. As further shown by reference numeral 550, the support system 502 provides a virtual imaging expert with a treatment checklist, patient characteristics, IV access location, etc., so that the virtual imaging expert can review the treatment checklist, patient characteristics, IV access location, and / or advise the radiologic technologist regarding the same. As further shown by reference numeral 550, the support system 502 can provide a virtual imaging expert with a display for monitoring local radiologic technologists and / or systems (e.g., the imaging system 520, the injection system 530, etc.) for correct actions and / or alerts or potential adverse events generated based on patient characteristics and / or the pre-treatment checklist.

[0132] As shown by reference numeral 555 in FIG. 5, the support system 502 and / or the treatment system 506 can obtain injection and / or imaging protocols (e.g., from EMR, from a protocol database, etc.). As further shown by reference numeral 555, the support system 502 provides the virtual imaging expert with the injection and / or imaging protocol so that the virtual imaging expert can review the injection and / or imaging protocol and / or advise the radiologist thereon. The radiologist can load an injector that can be remotely monitored by the virtual imaging expert via the support system 502. As further shown by reference numeral 555, the virtual imaging expert can remotely set, adjust, and / or review the injection and / or imaging protocol (e.g., scan parameters, region of interest (ROI), etc.) via the support system 502, and the radiologist can operate the injector to check for air. Depending on the authority level of the on-site radiologist, the technician can perform some, most, or all of the functions listed for the virtual imaging expert, and the virtual imaging expert can wait, for example, when requested by the on-site radiologist and / or intervene when alerted by the support system 102, monitor the process at the treatment location, and interact as needed.

[0133] The non-limiting embodiments or aspects of the authority levels described herein are exemplary. For example, multi-level and / or multi-dimensional authority schemas with various authorities can be used. As an example, a user can use a protocol as is, modify a protocol, create a new protocol, eliminate a protocol, and / or overwrite / block the actions of another user.

[0134] As shown by reference number 560 in FIG. 5, a local radiologist can initiate a test injection, and the support system 502 can provide information or data to a virtual imaging expert to monitor the technician and / or patient during the test injection. If the test injection includes only a saline injection, the local sensors, on-site technicians, and / or virtual imaging expert can confirm that the fluid has flowed properly to the patient and / or that there has been no extravasation and / or adverse events. If the test injection includes a contrast agent used to capture information about the patient, the same monitoring for proper flow may be performed as described above, and when the injection system 530 delivers the test injection, the imaging system 520 can generate tracking bolus data for adjusting the injection protocol (e.g., contrast agent dosage optimization, images at peak enhancement, etc.), which the support system 502 can provide to the virtual imaging expert. Examples of adjustments are described in International Patent Application Publication No. 2020 / 247370, published December 10, 2020, filed June 2, 2020, as International Patent Application PCT / US2020 / 035699, the entire contents of which are incorporated herein by reference.

[0135] As shown by reference numeral 565 in FIG. 5, after test injection, the virtual imaging expert can adjust the injection and / or imaging protocol via the support system 502, which can be verified by the local radiologist. As further shown by reference numeral 565 in FIG. 5, the virtual imaging expert can initiate the injection via the support system 502, for example, if the local radiologist does not have sufficient system privileges to locally initiate the injection in the treatment system 506, and / or if the local radiologist has sufficient system privileges to locally initiate the injection in the treatment system 506, and / or if a manual injection procedure is performed, the local radiologist can initiate the injection via the treatment system 506. At any time during the injection, the virtual imaging expert can abort the procedure via the support system 502, and / or the support system 502 can automatically abort the procedure based on the treatment data, thereby causing the injection system 530 to stop the injection and / or the imaging system 520 to stop the imaging. At any time during the injection, the imaging system 520 and / or the injection system 530 can detect the status and abort the injection, the imaging procedure, or a combination thereof. As further shown by reference numeral 565 in FIG. 5, when an image is available from the imaging system 520, the support system 502 can provide the image to the virtual imaging expert for review in order to identify image artifacts, vein contamination, delayed enhancement, etc. If there are issues determined from the review, the support system 502 and / or the virtual imaging expert can decide to repeat part or all of the imaging procedure.

[0136] After the procedure is completed, the virtual imaging expert can evaluate the patient's status and the quality of the procedure via the support system 502, which can archive or store information and / or data related to the procedure (e.g., in a database, etc.).

[0137] While embodiments or aspects have been described in detail for purposes of illustration and explanation, such details are for that purpose only, and the embodiments or aspects are not limited to the disclosed embodiments or aspects. On the contrary, it should be understood that they are intended to cover modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the present disclosure is intended, to the extent possible, to combine one or more features of any embodiment or aspect with one or more features of any other embodiment or aspect. In fact, any of these features can be combined in ways not specifically recited in the claims and / or not disclosed herein. Each of the dependent claims listed below may directly depend on only one claim, but the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.

Description of Reference Numerals

[0138] 100 Environment 101 Support Location 102 Support System 103 Support User Interface 103 User Interface 104 Treatment Location 106 Treatment System 108 Database System 110 Communication Network 120 Imaging System 122 Scanner 123 Scanner User Interface 130 Injection System 132 Injector 133 Injector User Interface 140 Local System 200 Device 202 Bus 204 Processor 206 Memory 208 Storage Component 210 Input Component 212 Output Component 214 Communication Interface 300 Process 302 Step 304 Step 306 Step 308 Step 400 Implementation 500 Implementation 502 Support System 506 Treatment System 520 Imaging System 530 Injection System 550 Reference Number 555 Reference Number 560 Reference Number 565 Reference Number

Claims

1. User interface and The system receives treatment data related to the treatment for the patient from at least one of a first treatment system among a plurality of treatment systems, which includes an infusion system comprising an injector configured to deliver fluid to the patient, and an imaging system comprising a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one further user interface distinct from the user interface, and the infusion system communicates with the imaging system, The user interface provides a display generated based on the treatment data, the display further includes a plurality of segmented displays or sections corresponding to the plurality of treatment systems, including the first treatment system. The user interface receives user input, Based on the user input, the operation of at least one of the injection system and the imaging system is controlled. A processor programmed and / or configured in such a way as, A system that includes these features.

2. The aforementioned treatment data is as follows, namely, At least one image captured by a camera associated with at least one of the injection system and the imaging system, Information received via the aforementioned at least one further user interface, Sensor data acquired by at least one sensor associated with at least one of the injection system and the imaging system, or any combination thereof The system according to claim 1, comprising at least one of the following.

3. The aforementioned treatment data includes the at least one image, and the at least one image is as follows: One or more images of the aforementioned patient, One or more images of the operator of at least one of the injection system and the imaging system, One or more images of the IV access site of the aforementioned patient, One or more images of the aforementioned injector, One or more images from the aforementioned scanner, or any combination thereof The system according to claim 2, comprising at least one of the following.

4. The processing data includes the information received via the at least one further user interface, and the information received via the at least one further user interface is as follows: Image prescription, Pre-treatment checklist, Display of patient consent, Adverse reaction checklist, At least one of the following: selection, programming, and modification of the injection protocol. At least one of the following: selection, programming, and modification of the imaging protocol. Request to initiate the aforementioned operation, Request to terminate the aforementioned procedure, Information acquired at the end of the aforementioned procedure, Information for secondary acquisition, Information for billing procedures, or any combination thereof The system according to claim 2, comprising at least one of the following.

5. The treatment data includes sensor data acquired by at least one sensor associated with at least one of the injection system and the imaging system, wherein the at least one sensor is one of the following sensors: flow sensor, Temperature sensor, accelerometer, Vibration sensor, Strain gauge, Motor current sensor, Optical sensor, The aforementioned scanner, or any combination thereof It includes at least one of the following: The procedure data includes at least one of the following parameters determined based on the sensor data: movement associated with the patient, sound associated with the patient, communication status between the scanner and the injector, one or more images of the patient captured by the scanner, amount of noise associated with one or more images of the patient captured by the scanner, enhancement or saturation level associated with one or more images of the patient captured by the scanner, flow rate during one or more fluid injections by the injector, duration of one or more fluid injections by the injector, volume pumped and / or delivered during one or more injections by the injector, pressure achieved during one or more injections by the injector, imaging signals from a region of interest over a point in time or over a period of time, ECG gating sequence, patient pulse, or any combination thereof. The system according to claim 2.

6. The aforementioned sensor data is as follows: Setup of at least one of the injector and the scanner, Arming of the aforementioned injector, During the period in which the injector is armed, The aforementioned injector performs venous occlusion (KVO) maintenance, Delivery of the test bolus and / or follow-up bolus to the patient by the injector, Delivery of contrast agent to the patient by the injector, During the period following the delivery of the contrast agent to the patient, Delivery of physiological saline solution to the patient by the injector, During the period after the delivery of the aforementioned saline solution to the patient, Scanning of the patient by the aforementioned scanner, or any combination thereof The system according to claim 5, wherein at least one of the following is captured by the at least one sensor.

7. The aforementioned display includes an alert, and at least one of the injection system and the imaging system is as follows: The aforementioned sensor data, The aforementioned user input, Patient data associated with the aforementioned patient, or any combination thereof The system according to claim 5, which generates an alert based on at least one of the following.

8. The aforementioned treatment data includes the following parameters associated with the patient, namely, age, body weight, height, Body Mass Index cardiac output, Risk or probability of adverse events, Adverse events, Estimated glomerular filtration rate (eGFR), Previous injection history including one or more allergic reactions to contrast agents, Patient IV access point location, The quality of the aforementioned patient IV access point, or any combination thereof Patient data including at least one of the following: The system according to claim 1, wherein the display includes an alert, and at least one of the infusion system and the imaging system generates the alert based on the patient data before arming the injector for the procedure.

9. The aforementioned at least one processor is as follows: Electronic Medical Record (EMR) system, Radiation Information System (RIS), Image Archiving and Communication System (PACS), Hospital Information System (HIS), Hospital corporate information system, Cross-location network, or any combination thereof The system according to claim 1, further programmed and / or configured to obtain information associated with the procedure and at least one of the patients from at least one of the following:

10. The system according to claim 1, wherein the user input includes at least one of selecting, programming, and modifying at least one of an injection protocol and an imaging protocol.

11. The display includes a prompt to confirm the operation of at least one of the injection system and the imaging system, and the at least one processor, Control the injection system and the imaging system such that at least one of them is prevented from performing the operation until a response to the prompt is received via the user interface. The system is programmed and / or configured to control the operation of at least one of the injection system and the imaging system. The aforementioned operation is the following operation, namely, The operation of changing the display of at least one further user interface, An operation to receive further user input through at least one further user interface, The operation of setting the injection protocol in the aforementioned injector, The operation of setting the imaging protocol in the scanner, An operation to initiate the loading process using the aforementioned injector, The operation to start data acquisition by the aforementioned injector, The action of arming the injector, The action of initiating the venous patency maintenance (KVO) procedure using the aforementioned injector, The operation of initiating the physiological saline test injection using the aforementioned injector, The operation of initiating drug injection using the aforementioned injector, The operation to initiate the contrast agent test injection using the aforementioned injector, The operation of initiating the injection of contrast agent by the aforementioned injector, The operation to start scanning with the aforementioned scanner, An action to stop the injection of the physiological saline test by the injector, An action to stop the contrast agent test injection by the aforementioned injector, An action to stop the injection of contrast agent by the aforementioned injector, The operation of initiating the injection of physiological saline solution using the aforementioned injector, An action to stop the injection of the physiological saline solution by the injector, The operation to stop scanning by the aforementioned scanner, An action to terminate the treatment for the aforementioned patient, or any combination thereof including at least one of the following: The system according to claim 1.

12. The operation includes at least one of delivering fluid to the patient using the injector and scanning the patient using the scanner, and the at least one processor is Controlling at least one of the injection system and the imaging system to change and discontinue the operation of at least one of the injection system and the imaging system. The system according to claim 1, which is programmed and / or configured to control the operation of at least one of the injection system and the imaging system.

13. The system according to claim 1, wherein the treatment data includes one or more images of the patient captured by the scanner, the at least one processor is programmed and / or configured to process the one or more images to select a subset of the one or more images, and the display is generated based on the selected subset of the one or more images.

14. The system according to claim 1, wherein the scanner includes at least one of the following: a magnetic resonance (MR) scanner, a computed tomography (CT) scanner, a positron emission tomography / computed tomography (PET / CT) scanner, a positron emission tomography / magnetic resonance (PET / MR) scanner, a single-photon emission computed tomography (SPECT) scanner, an ultrasound system, an infrared imaging system, a photoacoustic imaging system, or any combination thereof.

15. The injection system, the imaging system, and the at least one further user interface are located at the treatment location, and the user interface is located at a support location different from the treatment location. The system according to claim 1, wherein the treatment location includes at least one of the following locations: a hospital, an imaging center, a mobile imaging trailer, a vehicle, or any combination thereof.

16. The user input is as follows: A response to a prompt for confirming the operation of at least one of the injection system and the imaging system, Commands to the at least one of the injection system and the imaging system to start, change, and / or execute the operation of the at least one of the injection system and the imaging system, or any combination thereof The system according to claim 1, comprising at least one of the following.

17. The system according to claim 1, wherein the display includes at least one alert, the at least one alert including, namely, an indication that the procedure is complete, an indication that the procedure was performed correctly, an indication that the operator appears to be hesitating during programming, a real-time display of a measurement parameter associated with fluid injection, a display of a detected adverse event, a display of the quality of one or more images of the patient captured by the scanner, or any combination thereof.

18. The aforementioned at least one processor is Authentication data associated with a user account is received from at least one of the injection system and the imaging system via the at least one further user interface. Based on the permission level associated with the user account, the operation of at least one of the injection system and the imaging system is restricted from being initiated and / or modified by the user account through the at least one further user interface, the permission level associated with the user account is determined based on the authentication data. The system according to claim 1, programmed and / or configured as follows.

19. The aforementioned authority levels are as follows: Several actions associated with the aforementioned user account, The quality, experience, and / or other evaluations associated with the aforementioned user account, The type and / or manner of the aforementioned treatment, The aforementioned patient type, or any combination thereof The system according to claim 18, further determined based on at least one of the following.

20. The permission levels associated with the aforementioned user account are the following permission levels, namely: The user account has a first privilege level that restricts it from modifying at least one of the injection protocol and the scan protocol. A second level of privilege is available that restricts the user account from modifying a first subset of the parameters of the injection protocol and the scan protocol, and allows the user account to modify a second subset of the parameters of the injection protocol and the scan protocol. A third privilege level to which the user account is enabled to modify at least one of the parameters of the injection protocol and the scan protocol. The system according to claim 18, selected from one of the following.

21. A step of providing a user interface using at least one processor, A step of using the at least one processor to receive treatment data associated with a treatment for a patient from at least one of a first treatment system among a plurality of treatment systems, which includes an infusion system comprising an injector configured to deliver fluid to a patient, and an imaging system comprising a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one further user interface different from the user interface, and the infusion system communicates with the imaging system. A step of providing a display via the user interface using at least one processor, wherein the display is generated based on the treatment data, and the display further comprises a plurality of segmented displays or sections corresponding to a plurality of treatment systems, including the first treatment system. The steps include receiving user input via the user interface using at least one of the aforementioned processors, A step of using the at least one processor to control the operation of at least one of the injection system and the imaging system based on the user input, A step of using the at least one processor to automatically provide, via the user interface, an enlarged or zoomed-in view of a first segmented display or section of the first treatment system compared to other segmented displays or sections of the plurality of treatment systems, based on at least one of the treatment data, the user input, or any combination thereof. Methods that include...

22. A computer program product comprising at least one non-temporary computer-readable storage medium containing program instructions, wherein when the program instructions are executed by at least one processor, the at least one processor receives To provide a user interface, Receiving treatment data related to the treatment for the patient from at least one of a first treatment system among a plurality of treatment systems, which includes an infusion system comprising an injector configured to deliver fluid to the patient and an imaging system comprising a scanner configured to scan the patient, wherein at least one of the infusion system and the imaging system includes at least one further user interface distinct from the user interface, and the infusion system communicates with the imaging system, receiving, To provide a display generated based on the treatment data via the user interface, wherein the display further comprises a plurality of segmented displays or sections corresponding to the plurality of treatment systems, including the first treatment system. Receiving user input via the aforementioned user interface, Based on the user input, the operation of at least one of the injection system and the imaging system is controlled. To automatically provide, via the user interface, an enlarged or zoomed-in view of the first segmented display or section of the first treatment system compared to other segmented displays or sections of the plurality of treatment systems, based on at least one of the treatment data, the user input, or any combination thereof. A computer program product that executes a command.