System, method, and computer program product for automated diagnostic imaging procedures

EP4673953A1Pending Publication Date: 2026-01-07BAYER HEALTHCARE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
EP2024715981
Authority / Receiving Office
EP · EP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-03-01
Filing Date
2024-02-28
Publication Date
2026-01-07

AI Technical Summary

Technical Problem

Current medical imaging devices require significant training and expertise, limiting their accessibility and throughput due to the need for specialized operators, even for simpler systems like handheld ultrasound devices.

Method used

A system that includes a processor to communicate with a fluid injection system, an imaging system, a sensor system, and a user device, which sets and enables imaging protocols based on patient data, allowing for automated diagnostic imaging procedures and reducing the need for expert operators by prompting users to initiate procedures and adjusting protocols based on threshold satisfaction.

Benefits of technology

Enables automated diagnostic imaging procedures, reducing the barrier of expertise required for operation and increasing accessibility and efficiency by allowing non-experts to perform imaging tasks with minimal training, thereby improving the availability and speed of medical imaging services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2024017599_06092024_PF_FP
    Figure US2024017599_06092024_PF_FP
Patent Text Reader

Abstract

Systems, methods, and computer program products are provided for automated diagnostic imaging procedures. An example system includes at least one processor configured to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient; determine, based on the procedure data, whether a threshold for performing a next portion of the patient procedure is satisfied; and enable, based on a determination that the threshold for performing the next portion of the patient procedure is satisfied, at least one of the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device, to perform the next portion of the patient procedure.
Need to check novelty before this filing date? Find Prior Art

Description

SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR AUTOMATED DIAGNOSTIC IMAGING PROCEDURESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 487,867, filed March 1 , 2023, the disclosure of which is hereby incorporated by reference in its entirety.BACKGROUND1 . Technical Field

[0002] This disclosure relates generally to diagnostic imaging procedures and, in nonlimiting embodiments or aspects, to systems, methods, and computer program products for automated diagnostic imaging procedures.2. Technical Considerations

[0003] Technology and the technical capabilities of devices and systems improve over time. When the technology is just good enough, an integrated design may be needed to get more from each part. Interfaces, subsystems, and / or components may be optimized to give better overall system performance. The overall design generally is done or overseen by one organization. Eventually the system may meet the customer needs well enough that “excess technical capabilities” can be used to standardize interfaces and designs. Hardware modules may become interchangeable and / or upgradeable, and the system may recognize new hardware and / or upgrades with minimal to no user direction or interaction. The systems become more and more complex and more and more capable. Some of the capability can be used to simplify the operation for the user.

[0004] User-facing capabilities and the basis of competition evolve along a generally similar parallel path. Initially, these improvements may be used to improve the basic outputs or results of the system. In medical imaging, these improvements may be associated with aspects such as resolution, volume covered, speed of image acquisition and / or the like. Eventually the essential capabilities may be “good enough” and it may become hard to justify increasing them further unless there is little to no cost for the improvement. Reliability of the device and system may now become a bigger focus.Eventually, simplicity of use, speed of learning how to operate the system, and a level of training or experience needed by the operator may be considered. Initially, experts, such as PhDs, MDs, and / or the like may be needed. Eventually those with a bachelor's degree, an associate degree, on-the-job experience, and ultimately even novices can use the system. Ultimately, competition may be based on price or output per unit price.

[0005] In medical imaging, for example, in computed tomography (CT), some consider that there have been five generations of CT scanners based on the geometry of the X- ray beam and how the X-ray source and detectors move. There is currently a new generation of X-ray detectors referred to as “photon counting CT” that may ultimately bring significant improvements in resolution and at the same time significant dose reduction. This may expand the application of, and thus the demand for, CT imaging.

[0006] In magnetic resonance imaging (MRI), many image parameters are dependent on signal-to-noise ratio, which improves with field strength. Workhorse MR scanners include 1.5T (Tesla) scanners. A top of the line MR scanner may typically have a 3.0T field strength, though there are also 7T scanners and 10T scanners. Siemens has recently introduced a 0.55T scanner with very sophisticated electronics and software that can perform as well or better for some imaging tasks than existing higher field scanners. This represents a new value point in MR scanning.

[0007] As price is reduced, such devices generally become available to more people. However, if there is significant training required for the use of such a device, then that training becomes the barrier or bottleneck to the use of the device. This is true even for simpler systems, such as handheld ultrasound, which is very operator dependent.

[0008] Existing solutions for addressing training or expertise limitations associated with medical imaging devices may rely on providing experts with remote operation capabilities. Experts using remote operation capability, however, may not provide an ultimate or optimal solution. Although individual remote expert users may be more efficient than if they had to perform all of the patient handling experiences too, they are still a bottleneck in throughput.SUMMARY

[0009] Accordingly, provided are improved systems, methods, and computer program products for automated diagnostic imaging procedures.

[0010] According to non-limiting embodiments or aspects, provided is a system, including: at least one processor configured to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0011] In some non-limiting embodiments or aspects, the at least one processor is further configured to: set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that thethreshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0012] In some non-limiting embodiments or aspects, the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0013] In some non-limiting embodiments or aspects, the procedure order further includes procedure parameters associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0014] In some non-limiting embodiments or aspects, the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0015] In some non-limiting embodiments or aspects, the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: providing, via the user device, at least one prompt to the user; and receiving, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

[0016] In some non-limiting embodiments or aspects, the at least one processor is further configured to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0017] According to some non-limiting embodiments or aspects, provided is a method, including: communicating, with at least one processor, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; setting, with the at least one processor, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation andthe imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the imaging portion of the patient procedure; receiving, with the at least one processor, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0018] In some non-limiting embodiments or aspects, the method further includes: setting, with the at least one processor, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicating, with the at least one processor, with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injectionoperation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disabling, with the at least one processor, the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjusting, with the at least one processor, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicating, with the at least one processor with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and storing, with the at least one processor, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0019] In some non-limiting embodiments or aspects, the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: verifying, with the at least one processor, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0020] In some non-limiting embodiments or aspects, the procedure order further includes procedure parameters associated with the patient procedure, and whereindetermining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: verifying, with the at least one processor, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0021] In some non-limiting embodiments or aspects, the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: receiving, with the at least one processor, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, with the at least one processor, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0022] In some non-limiting embodiments or aspects, determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: providing, with the at least one processor, via the user device, at least one prompt to the user; and receiving, with the at least one processor, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

[0023] In some non-limiting embodiments or aspects, the method further includes: receiving, with the at least one processor, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according toat least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and controlling, with the at least one processor, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0024] According to some non-limiting embodiments or aspects, provided is a computer program product including at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0025] In some non-limiting embodiments or aspects, the program instructions, when executed by at least one processor, further cause the at least one processor to: set, basedon the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imagingoperation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0026] In some non-limiting embodiments or aspects, the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0027] In some non-limiting embodiments or aspects, the procedure order further includes procedure parameters associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0028] In some non-limiting embodiments or aspects, the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of thepatient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0029] In some non-limiting embodiments or aspects, the program instructions, when executed by at least one processor, further cause the at least one processor to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0030] Further non-limiting embodiments or aspects are set forth in the following numbered clauses:

[0031] Clause 1 : A system, comprising: at least one processor configured to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in responseto enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0032] Clause 2: The system of clause 1 , wherein the at least one processor is further configured to: set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injectionprotocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0033] Clause 3: The system of clause 1 or 2, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0034] Clause 4: The system of any of clauses 1-3, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0035] Clause 5: The system of any of clauses 1 -4, wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0036] Clause 6: The system of any of clauses 1 -5, wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: providing, via the user device, at least one prompt to the user; and receiving, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

[0037] Clause 7: The system of any of clauses 1 -6, wherein the at least one processor is further configured to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0038] Clause 8: A method, comprising: communicating, with at least one processor, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein thefluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; setting, with the at least one processor, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the imaging portion of the patient procedure; receiving, with the at least one processor, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0039] Clause 9: The method of clause 8, further comprising: setting, with the at least one processor, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the test portion of the patient procedure; receive, from the user device, a user inputincluding an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicating, with the at least one processor, with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disabling, with the at least one processor, the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjusting, with the at least one processor, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicating, with the at least one processor with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and storing, with the at least one processor, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0040] Clause 10: The method of clause 8 or 9, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with ascheduled patient, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: verifying, with the at least one processor, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0041] Clause 11 : The method of any of clauses 8-10, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: verifying, with the at least one processor, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0042] Clause 12: The method of any of clauses 8-11 , wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: receiving, with the at least one processor, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, with the at least one processor, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0043] Clause 13: The method of any of clauses 8-12, wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: providing, with the at least one processor, via the user device, at least one prompt to the user; and receiving, with the at least one processor, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

[0044] Clause 14: The method of any of clauses 8-14, further comprising: receiving, with the at least one processor, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and controlling, with the at least one processor, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0045] Clause 15: A computer program product comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on thedetermination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0046] Clause 16: The system of clause 15, wherein the program instructions, when executed by at least one processor, further cause the at least one processor to: set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injectionprotocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0047] Clause 17 : The system of clause 15 or 16, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

[0048] Clause 18: The system of any of clauses 15-17, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whetherthe threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

[0049] Clause 19: The system of any of clauses 15-18, wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

[0050] Clause 20: The system of any of clauses 15-19, wherein the program instructions, when executed by at least one processor, further cause the at least one processor to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

[0051] These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the disclosed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Additional advantages and details are explained in greater detail below with reference to the non-limiting, exemplary embodiments that are illustrated in the accompanying schematic figures, in which:

[0053] FIG. 1 A is a schematic diagram of a system for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects;

[0054] FIG. 1 B is a schematic diagram of an implementation of a system for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects;

[0055] FIG. 2 is a schematic diagram of example components of one or more devices of FIGS. 1 A and / or 1 B, according to some non-limiting embodiments or aspects;

[0056] FIG. 3 is a flow diagram of a method for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects;

[0057] FIGS. 4A-4C is a workflow diagram of an implementation of a method for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects;

[0058] FIGS. 5A and 5B are perspective views of non-limiting embodiments or aspects of a contact sensor device;

[0059] FIG. 5C is a diagram of non-limiting embodiments or aspects of components of a contact sensor device;

[0060] FIG. 5D is a perspective view of non-limiting embodiments or aspects of a contact sensor device attached to an extremity of a patient;

[0061] FIG. 5E is a cross sectional view of non-limiting embodiments or aspects of a contact sensor device attached to an extremity of a patient; and

[0062] FIGS. 6A-6E are perspective views of non-limiting embodiments or aspects of a contact sensor device.DETAILED DESCRIPTION

[0063] For purposes of the description hereinafter, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and derivatives thereof shall relate to the embodiments as they are oriented in the drawing figures. However, it is to be understood that the present disclosure may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary and non-limiting embodiments or aspects of the disclosed subject matter. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting.

[0064] Some non-limiting embodiments or aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, more than the threshold, higher than the threshold, greater than or equal to the threshold, less than the threshold, fewer than the threshold, lower than the threshold, less than or equal to the threshold, equal to the threshold, etc.

[0065] No aspect, component, element, structure, act, step, function, instruction, and / or the like used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more” and “at least one.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and / or the like) and may be used interchangeably with “one or more” or “at least one.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based at least partially on” unless explicitly stated otherwise. In addition, reference to an action being “based on” a condition may refer to the action being “in response to” the condition. For example, the phrases “based on” and “in response to” may, in some non-limiting embodiments or aspects, refer to acondition for automatically triggering an action (e.g., a specific operation of an electronic device, such as a computing device, a processor, and / or the like).

[0066] As used herein, the term “communication” may refer to the reception, receipt, transmission, transfer, provision, and / or the like of data (e.g., information, signals, messages, instructions, commands, and / or the like). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, and / or the like) to be in communication with another unit means that the one unit is able to directly or indirectly receive information from and / or transmit information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, and / or the like) that is wired and / or wireless in nature. Additionally, two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and / or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may be in communication with a second unit if at least one intermediary unit processes information received from the first unit and communicates the processed information or results thereof to the second unit. In some non-limiting embodiments or aspects, a message may refer to a network packet (e.g., a data packet and / or the like) that includes data. It will be appreciated that numerous other arrangements are possible.

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

[0068] As used herein, the term “server” may refer to or include one or more computing devices that are operated by or facilitate communication and processing for multipleparties in a network environment, such as the Internet, although it will be appreciated that communication may be facilitated over one or more public or private network environments and that various other arrangements are possible. Further, multiple computing devices (e.g., servers, mobile devices, etc.) directly or indirectly communicating in the network environment may constitute a “system.”

[0069] As used herein, the term “system” may refer to one or more computing devices or combinations of computing devices (e.g., processors, servers, client devices, software applications, components of such, and / or the like). Reference to “a device,” “a server,” “a processor,” and / or the like, as used herein, may refer to a previously-recited device, server, or processor that is recited as performing a previous step or function, a different device, server, or processor, and / or a combination of devices, servers, and / or processors. For example, as used in the specification and the claims, a first device, a first server, or a first processor that is recited as performing a first step or a first function may refer to the same or different device, server, or processor recited as performing a second step or a second function.

[0070] Non-limiting embodiments or aspects of the present disclosure provide systems, methods, and computer program products for automated diagnostic imaging procedures that are able to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operationand the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

[0071] In this way, non-limiting embodiments or aspects of the present disclosure may provide an improved solution for addressing training or expertise limitations associated with medical imaging devices by having the relevant expertise of a remote operator captured and codified in a computer system so that this experience is available instantly when needed at every machine. Accordingly, non-limiting embodiments or aspects of the present disclosure may go beyond the capabilities of a remote operation console and provide operational devices and systems with sufficient built-in operational capabilities in the form of algorithms and computer programs such that a local caregiver may not need to know how to program or plan a study with the imaging equipment. The local patient caregiver may be focused on preparing the patient, comforting them, answering questions, ensuring their safety, and placing them in the proper position in association with the imaging system. Then “one button” may be actuated to direct the system to take the scan that was prescribed by the referring physician and, optionally, make some or all of a diagnosis using artificial intelligence (Al). In additional embodiments, the system may use as inputs the symptoms and other information about the patient to select, set up, and execute the appropriate protocols determined by various medical societies or the local doctors, and interpret the results of the study.

[0072] Non-limiting embodiments or aspects of the present disclosure may use an imaging suite including an imaging device for acquiring an image and an injection device for delivering contrast to a patient, a human patient caregiver trained and certified in care of the patient and in safety in the presence of the applicable imaging modality for caring for the patient, and a management system configured to provide for safe operation of the applicable imaging equipment and optimization of the imaging study to the patient that may be in communication with the patient caregiver and operate the injector and imagingsystems. In unusual circumstances or as needed, additional embodiments or aspects may include a communications mechanism for use in communicating to a human (e.g., a remote helper or specialist, etc.) with whom the patient caregiver can consult. This “backup” person may be onsite or may be remotely located from the imaging suite.

[0073] To facilitate safe operation with a local patient caregiver, additional system connected safety equipment may be installed, such as a portal monitor outside the door of an magnetic resonance MR) imaging suite to alert to the presence of any ferromagnetic materials approaching the entrance of the MR imaging suite, one or more cameras to enable the system or caregiver to ensure that no one unexpected is in a computed tomography (CT) imaging suite when the radiation source is operating, interlocks on CT doors so that the radiation source is automatically turned off if the door is opened, and / or the like. Such additional safety equipment may be connected to any local user interfaces, the imaging equipment controls, and / or the management system. To further facilitate safe operation, features such as power injected saline flush boluses and / or an initial saline phase during any test or imaging boluses may be incorporated into injection protocols. Further, non-limiting embodiments or aspects of the present disclosure may use a high flow test bolus as described in International Patent Application Publication No. W02020 / 247370A1 , the disclosure of which is hereby incorporated by reference in its entirety, which may enable sophisticated design and customization of the imaging bolus and acquisition protocols to the specific patient with no additional work or need for training of the caregiver.

[0074] Referring now to FIG. 1A, shown is a schematic diagram of a system 100 for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects. As shown in FIG. 1A, system 100 for automated diagnostic imaging procedures may include fluid injector system 102, imaging system 104, sensor system 106, user device 108, management system 110, auxiliary system 112, and / or communication network 114. Referring also to FIG. 1 B, shown is a schematic diagram of an implementation 150 of system 100 for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects. As shown in FIG. 1 B, implementation 150 may include injector 152, injector control and computation system 154, injector user interface 156, imager 158, imager control and computation system 160,imager user interface 162, contact sensor(s) 164A, non-contact sensor(s) 164B, management control and computation system 166, hospital information system(s) 168, cloud computing and offsite resources 170, and / or management user interface 172. Systems and / or devices of system 100 and / or implementation 150 may interconnect (e.g., communicate information and / or data, etc.) via wired connections, wireless connections, ora combination of wired and wireless connections (e.g., via communication network 114, etc.). System 100 may be located in a hospital, an imaging center, a mobile imaging trailer, an emergency vehicle with scanners, a mobile MRI (e.g., a Hyperfine® imaging system, etc.), a mobile CT for head scans, a home imaging system, a Battlefield I MASH / Emergency Relief station, any combination thereof, and / or the like. In some non-limiting embodiments or aspects, management user interface 172 may combine some or all aspects of injector user interface 156 and imager user interface 162 to provide a more unified and thus simplified user experience. In some non-limiting embodiments or aspects, some or all aspects of user interface 172 may be on one or both of injector user interface 156 and imager user interface 162 to provide a more familiar user experience.

[0075] Fluid injection system 102 may include one or more devices, software, and / or hardware configured to set up one or more injection protocols and deliver one or more fluids (e.g., contrast agents, etc.) to a patient according to one or more injection protocols. An injection protocol commonly includes one or more phases, with each phase specifying the fluid and optionally fluid concentration to be injected, and two of the flow rate, volume, and duration of that phase of the injection (e.g., because volume injected = flow rate x duration, there are only two independent variables out of those three parameters). Other injection parameters, which may be different for different phases or constant for all phases, may include at least one of pressure limits, flow rate limits, occlusion indications, any combination thereof, and / or the like. Some injectors may be configured to have a time varying value of one, some, or all of the injection parameters. For example, fluid injection system 102 may include injector 152, injector control and computation system 154, and / or injector user interface 156. As an example, fluid injection system 102 may include a contrast injection system as described in U.S. Pat. Nos. 6,643,537 and / or 7,937,134 and / or as described in published International Application No. WO2019046299A1 , the disclosure of each of which is hereby incorporated by reference in its entirety. As anexample, fluid injection system 102 may include the MEDRAD® Stellant FLEX CT Injection System, the MEDRAD® MRXperion MR Injection System, the MEDRAD® Mark 7 Arterion Injection System, the MEDRAD® Intego PET Infusion System, the MEDRAD® Spectris Solaris EP MR Injection System, the MEDRAD® Stellant CT Injection System With Certegra® Workstation, the MEDRAD Centargo® CT Injection System and / or the like manufactured by any of the many companies making approved devices.

[0076] Imaging system 104 may include one or more devices, software, and / or hardware configured to set up imaging protocols and acquire non-contrast and / or contrast-enhanced scans of a patient. For example, imaging system 104 may include imager 158, imager control and computation system 160, and / or imager user interface 162. As an example, imaging system 104 may include a magnetic resonance imaging (MRI) system, a computed tomography (CT) system, an ultrasound system, a singlephoton emission computed tomography (SPECT) system, a positron emission tomography system (PET), a positron emission tomography-magnetic resonance (PET / MRI) system, a positron emission tomography-computed tomography (PET / CT) system, an angiography system, an interventional radiology (IR) system, an ultrasound system, and / or other imaging modalities used on humans or animals. As an example, imaging system 104 may include an imaging system as described in U.S. Patent Application Publication No. 2020 / 0146647A1 , filed on Dec. 11 , 2019, the entire contents of which is hereby incorporated by reference. In some non-limiting embodiments or aspects, imaging system 104 may include Siemens Healthineers' Somatom Go CT Systems, General Electric's Signa MR Systems, and / or the like.

[0077] Sensor system 106 may include sensors 164A and / or 164B configured to determine (e.g., determine, collect, acquire, capture, measure, sense, etc.) sensor data associated with a patient and / or a fluid injection (e.g., a contrast media injection, etc.) for the patient. For example, sensor system 106 may include contact sensor(s) 164A (e.g., a sensor that contacts a patient to determine sensor data, a sensor included in contact sensor device 500 and / or 800 wearable by a patient, etc.) and / or non-contact sensors 164B (e.g., a sensor device that does not contact a patient to determine sensor data, an image capture device, etc.).

[0078] Contact sensor 164A may include at least one of the following sensors: an accelerometer; a strain gauge; a global positioning system (GPS); a skin resistivity or conductance sensor; a heart rate monitor; a microphone (e.g., a microphone configured to measure sound in tissue of a patient, for example an inflow sound of contrast media, saline, or other drugs in a vessel, etc.); a thermal or temperature sensor (e.g., a temperature sensor configured to measure a change in tissue temperature due to injected saline and / or contrast fluid, etc.); a pulse oximeter (e.g. a pulse oximeter configured to measure a pulse rate, a change in oxygenation level, a patient hydration, and / or a local tissue perfusion, etc.); a hydration sensor; a dosimeter; an Apple watch or similar device; an ultrasound sensor; an acoustic sensor (e.g., a sonic acoustic sensor, an infrasonic acoustic sensor, etc.); one or more electrodes configured to measure tissue impedance, perform an electromyogram (EMG), and / or an electrocardiogram (ECG or EKG); a respiration measuring sensor; a microwave sensor; a mechanical impedance sensor; a chemical sensor; a force or pressure sensor; a body-worn camera worn by the patient and / or the user / operator, a headset communicator worn by a local technologist to enable the local technologist and a virtual imaging specialist to be in contact, or any combination thereof. In some non-limiting embodiments or aspects, contact sensor 164A may be included in contact sensor device 500 and / or contact sensor device 800 as described herein. In some non-limiting embodiments or aspects, contact sensor 164A may be included on at least one of the following locations; a catheter (e.g., a tip of a catheter, etc.), on an arm of a patient over a tip of a catheter in the patient, on an arm of a patient proximate to an injection site or a tip of a catheter in the patient, on a connector tube upstream of a catheter, on another portion of a body of a patient; on an area surrounding an injection site, or any combination thereof. In some non-limiting embodiments or aspects, contact sensor 164A may include a single device including a single sensor, a single device including multiple sensors, and / or multiple devices including either a single sensor or multiple sensors. Existing devices including existing sensors may be incorporated into non-limiting embodiments or aspects of sensor system 106 and / or provide measurements to sensor system 106. Example existing devices may include an Apple watch, a Fitbit exercise monitor, and / or the like, which a patient may be wearing, ECG or respiratory monitors that may be part of imaging system 104, pulse oximeters orother monitoring equipment that may already be available and / or in use in an imaging suite and / or healthcare facility, and / or the like.

[0079] Non-contact sensor 164B may include one or more image capture devices configured to capture a plurality of images of a patient over a period of time (e.g., images of an injection site and / or an area surrounding an injection site, etc.), such as a camera (e.g., a visible light camera, an infrared (IR) camera, etc.), a LiDAR sensor, or any combination thereof. An IR camera may include at least one of the following IR cameras: a near IR camera (e.g., silicon sensing, etc.) configured to capture light having a near IR wavelength, a short wavelength IR camera configured as a spectral imager to capture light having a short IR wavelength, a medium wavelength IR camera configured to capture light having a medium IR wavelength, a long wavelength IR camera configured to capture light having a long IR wavelength, or any combination thereof. In some non-limiting embodiments or aspects, non-contact sensor 164B may include a camera system as disclosed by U.S. Patent Application Publication No. 2023 / 0173172A1 , the disclosure of which is hereby incorporated by reference in its entirety.

[0080] In some non-limiting embodiments or aspects, non-contact sensor 164B may include an image capture device configured to capture images using ambient illumination. In some non-limiting embodiments or aspects, non-contact sensor 164B may include one or more illumination devices configured to provide at least one of the following types of illumination for an image capture device: additional ambient illumination, localized additional illumination (e.g., at an injection site, etc.), through tissue illumination, a projected pattern or grid, cross projections, or any combination thereof for use by the image capture device in capturing the images. For example, non-contact sensor 164B may include a camera as described in International Patent Application Publication No. WO2021 / 108286A1 , filed Nov. 23, 2020, the disclosure of which is hereby incorporated by reference in its entirety. Non-contact sensor 164B may include two or more cameras to provide binocular or 3D vision, which may enable 3D determination of phenomena such as swelling, gross motion in 3D, or vibrations or small motions in 3D.

[0081] In some non-limiting embodiments or aspects, non-contact sensor 164B may be mounted on imager 158, on injector 152, on a bed of a patient, on a pedestal pole, on an adjustable, overhead counterpoise, on a ceiling, and / or the like. In some non-limitingembodiments or aspects, non-contact sensor 164B may be held by a patient during a fluid injection (e.g., a contrast media injection, etc.) and / or an imaging examination. In some non-limiting embodiments or aspects, non-contact sensor 164B may be remotely controlled by a user (e.g., via user device 108, etc.) to pan and zoom to a desired field of view. In some non-limiting embodiments or aspects, sensor system 106 may control noncontact sensor 164B using one or more object tracking techniques to automatically follow an extremity (e.g., an arm, a leg, a hand, a foot, etc.) of a patient including an injection site.

[0082] In some non-limiting embodiments or aspects, fluid injection system 102, imaging system 104, user device 108, and / or auxiliary system 112 may include one or more additional sensors (e.g., contact sensors 164A, non-contact sensors 164B, etc.) configured to determine sensor data associated with a patient and / or a fluid injection (e.g., a contrast media injection, etc.) for the patient and / or store and / or provide sensor data determined by one or more additional sensors configured to determine sensor data associated with a patient and / or a fluid injection for the patient. Exemplary sensors may include respiration bands and / or ECG electrodes to enable injection and / or image acquisition in relation to a patient's respiration and / or heartbeat, respectively.

[0083] Referring now to FIGS. 5A and 5B, FIGS. 5A and 5B are perspective views of non-limiting embodiments or aspects of contact sensor device 500. Sensor system 106 may include contact sensor device 500, and / or contact sensor device 500 may include at least one contact sensor 502 of contact sensors 164A of sensor system 106 that are configured to determine sensor data associated with a patient and / or a fluid injection for the patient. Referring also to FIG. 5C, contact sensor device 500 may include housing 504 that houses contact sensors 502, communication device 506, processor 508, user input / feedback device 510, and / or battery 512. Housing 504 may provide a waterproof seal between an interior of housing 504 including contact sensors 502, communication device 506, processor 508, user input / feedback device 510, and / or battery 512 and an exterior of housing 504 such that contact sensors 502, communication device 506, processor 508, user input / feedback device 510, and / or battery 512 and / or electronic components thereof are sealed from an external environment surrounding contact sensor device 500 and / or such that contact sensor device 500 may be easily disinfected andeligible for multi-patient use. Housing 504 may have an elongated shape that extends between first end 505a and second end 505b. For example, as shown in FIG. 5D, housing 504 may include a bracelet-shaped wearable for a patient configured to be attached proximally to an injection site on an extremity (e.g., an arm, a leg, etc.) of a patient to measure sensor data associated with the patient before, during, and / or after a fluid injection and / or an examination (e.g., an MRI exam, a CT exam, etc.). As an example, housing 504 may include a flexible exterior or frame (e.g., an antibacterial silicone exterior or frame, etc.), which is configured to flex or bend to surround an extremity of a patient, and which houses internally contact sensors 502, communication device 506, processor 508, user input / feedback device 510, and / or battery 512 and / or electronic components thereof, and fluidically seals the internal components of contact sensor device 500 from an external environment. As an example, housing 504 may include an elastic member(s), for example, metal, plastic or foam, which urges the sensor(s) against the skin with an appropriate force or pressure. The elastic members may also urge the housing into a shape that assists in gripping an extremity of the patient.

[0084] In some non-limiting embodiments or aspects, as shown in FIG. 5D, contact sensor device 500 may include a removable strip or sheath 550 configured to surround, cover or separate housing 504 from skin contact to protect contact sensor device 500 from cross contamination (e.g., from patient to patient or via hands of a technologist, etc.). In some non-limiting embodiments or aspects, contact sensor device 500 may be a disposable or single-use device including printed sensors 502 and on a printed sensor pad or housing 504 that may adhere (e.g., via an adhesive layer, etc.) to the skin of the patient adjacent to an injection site.

[0085] In some non-limiting embodiments or aspects, housing 504 may be configured to immobilize an extremity (e.g., an arm, etc.) of the patient by preventing or restricting the patient from bending the extremity and thereby constricting a vein and / or a catheter or dislodging the catheter from the vein. For example, housing 504 may be configured as an elbow brace or exoskeleton. As an example, housing 504 may also immobilize the injection site to facilitate observation of the injection site by non-contact sensor(s) 164B.

[0086] In some non-limiting embodiments or aspects, housing 504 may include removable and / or disposable attachment means, such as a flexible patch, a fabric strip,an adhesive connector, a mechanical latch, a blood pressure cuff, a hook and loop fastener, such as a Velcro®-type attachment, and / or a suction cup. For example, contact sensor device 500 may be configured to attach to a dressing, such as the BD Tegaderm™ Transparent Film Dressing via physical alignment indicia, to another device (e.g., injector 152, imager 158, a disposable dressing, etc.), and / or to the patient. As an example, housing 504 may have a cylinder or hockey puck shape including an adhesive connected to attach housing 504 to the patient. In some non-limiting embodiments or aspects, housing 504 may include a clear disposable band to enable a user to visually inspect skin of a patient adjacent an injection site. Depending upon a shape or shapes of various segments of housing 504, an attachment mechanism configured to urge housing 504 and / or contact sensor(s) 164A into proper contact with a patient to may include: double sided adhesive tapes compatible with skin, a disposable strap or band; a strap with a disposable isolation patch or element (which may be especially useful for patients with arms with significant hair); a wrap that is inflated to a desired non-occlusive pressure similar to a blood pressure cuff; elastic force as in a “slap” bracelet; an elastomeric band or bracelet which may optionally be disposable and / or clear to allow for visual inspection of skin near the injection site; and / or attachment to a Tegaderm™ or similar existing device on a patient arm via physical indicia on the existing device. Additionally, or alternatively, housing 504 and / or contact sensor(s) 164A may not be mechanically attached to the patient but may be held in contact with the patient by having the patient lay on housing 504 and / or contact sensor(s) 164A or place his / her arm on or in housing 504 and / or contact sensor(s) 164A. Housing 504 and / or contact sensor(s) 164A may also be laid loosely onto the patient. In these cases, gravity and / or the effort of the patient may hold housing 504 and / or contact sensor(s) 164A in contact with the patient.

[0087] Sterility and / or cross contamination concerns are relatively low for non-contact sensor 164B because non-contact sensor 164B need not contact the patient. One or more of the following approaches may provide sufficient sterility and / or cross contamination prevention aspects for contact sensor device 500 and / or contact sensor 164A: a disposable attachment barrier; a cleaning of contacting aspects (e.g., electrodes, housing 504, etc.) of contact sensor device 500 and / or contact sensor 164A with a disinfecting wipe or spray; a “home base” or mount for holding and optionally for storing and / orcharging contact sensor device 500 and / or contact sensor 164A between patients, which may also include a sterilizing device, for example UV lamp, ozone treatment, or disinfecting wipe station; inclusion of self-sterilizing surfaces, for example a silver nanoparticle surface or film; a sheath into which contact sensor device 500 and / or contact sensor 164A may be slipped before use; an interposed, disposable barrier layer placed between the patient skin and contact sensor device 500 and / or contact sensor 164A; and / or some or all of contact sensor device 500 and / or contact sensor 164A may be sufficiently low cost that at least one segment or portion thereof may be used once for a patient and be thrown away or given to the patient as a “freebie” for their subsequent medical or home / personal use.

[0088] The giving away of an at least one segment or portion of contact sensor device 500 and / or contact sensor 164A a may be a good “marketing” and patient satisfaction activity or action. The application described herein in connection with patient information, education, electronic consenting, and similar functions may be configured to interface with the freebie segment or portion and enable the segment or portion to be a personal pulse oximeter and / or skin contact thermometer, for example that the patient can use at home.

[0089] Communication device 506 may include a wired and / or wireless communication device configured to communicate to an external device and / or system (e.g., fluid injection system 102, imaging system 104, sensor system 106, user device 108, management system 110, auxiliary system 112, etc.) sensor data associated with a patient.

[0090] Processor 508 may be programmed and / or configured to control one or more operations of contact sensors 502 and / or to determine sensor data associated with a patient. In some non-limiting embodiments or aspects, processor 508 may include a low power microcontroller unit (MCU).

[0091] User input / feedback device 510 may be configured to receive a user input from a user and / or to provide feedback to the user. For example, user input / feedback device 510 may include at least one of the following: a display, a light-emitting diode (LED), an audio output device (e.g., a buzzer, a speaker, a headset, etc.), a haptic output device (e.g., a vibrator, etc.) or any combination thereof. As an example, a user may establishcommunications with (e.g., pair, etc.) contact sensor device 500 with an external device and / or system via user input / feedback device 510 and / or provide prompts and / or instructions, which may be received from the external device and / or system, to a patient via user input / feedback device 510. In some non-limiting embodiments or aspects, user input / feedback device 510 may function as a patient call button configured to automatically call a user outside the scan room in response to being actuated.

[0092] User input / feedback device 510 may be partitioned between various pieces of hardware. For example, some input and / or output features or functions may be realized on contact sensor device 500. Some of the same and / or other functions may be accessible through a separate, purpose built, specific use user input / feedback device 510. Some of the same or other functions may be accessible through a general or multipurpose user input / feedback device 510, for example an iPhone. Some of the same and / or other functions may be accessible through a user interface of other equipment associated with a study or procedure being performed, for example injector interface 156 and / or imager user interface 162. Battery 512 may include a rechargeable battery (e.g., a battery rechargeable via an inductive charging technique, etc.), a single use battery, a replaceable battery, a wired connection to an external battery and / or power source, or any combination thereof. Battery 512 may provide power for operating components of contact sensor device 500.

[0093] Still referring to FIGS. 5A-5D, and referring also to FIG. 5E, contact sensors 502 may be orientated in a pattern, for example, circumferentially around an extremity of a patient when contact sensor device 500 is attached to the extremity of the patient such that contact sensors 502 may measure sensor data including tissue parameters and / or the like in a transversal cross-section of the extremity of the patient. For example, contact sensors 502 may be spaced apart from each other along a length of housing 504 extending from first end 505a to second end 505b. Contact sensor 502 sensing modes may include transmissive, reflective, absorptive, listen or passively measure modes. Different modes may be used for different sensors. Multiple and / or hybrid modes may be used depending on ambient and / or patient conditions. Phase gated sensing (e.g., phase locked loops (PLL), etc.), synchronous sensing, and / or other existing sensing means may be used for noise / interference reduction and / or ambient signal cancellation. A signalsensed may be a narrow segment of a possible spectrum and / or a broad segment of a possible spectrum to which subsequent processing may be applied.

[0094] Referring now to FIGS. 6A-6E, FIGS. 6A-6E are perspective views of nonlimiting embodiments or aspects of contact sensor device 800. Sensor system 106 may include contact sensor device 800 and / or contact sensor device 800 may include at least one contact sensor (e.g., 804, 808, 810, etc.) of the one or more contact sensors 164A of sensor system 106 that are configured to determine sensor data associated with a patient and / or a fluid injection (e.g., a contrast media injection, etc.) for the patient. In some nonlimiting embodiments or aspects, sensor system 106 may include contact sensor device 500 and contact sensor device 800, one of contact sensor device 500 and contact sensor device 800, or neither contact sensor device 500 nor contact sensor device 800. Further, contact sensor device 500 can be implemented within contact sensor device 800 (or vice- versa), and / or contact sensor device 500 can perform one or more functions as described as being performed by contact sensor device 800 (or vice-versa).

[0095] Contact sensor device 800 may include housing 802 and finger sensor 804 (e.g., a pulse oximeter, etc.). Finger sensor 804 may be connected to housing 802 via wire 806. Housing 802 may include electronic components 808, conductivity probes or electrodes 810, and / or disposable adhesive protector 812. Electronic components 808 may include contact sensors 164A, a processor, a memory, a wired and / or wireless communication device, a user input / feedback device, and / or a battery. For example, electronic components 808 of contact sensor device 800 may be the same as or similar to components of contact sensor device 500 described herein with respect to FIG. 50.

[0096] Housing 802 may include a soft, molded strap (e.g., a plastic strap, etc.) over molded onto a stiffener (e.g., a bendable wire, a semi-flexible metal frame, etc.). In some non-limiting embodiments or aspects, housing 802 may extend between first end 805a and second end 805b and be configured to wrap around a palm and / or a wrist of a patient. For example, as shown in FIG. 6A, housing 802 may be configured to wrap around a middle of a palm of a patient with finger sensor 804 connected to housing 802 via wire 806. For example, as shown in FIG. 6B, housing 802 may be configured to wrap around a wrist of a patient with finger sensor 804 connected to housing 802 via wire 806. For example, as shown in FIG. 6C, housing 802 may be configured to wrap around a palmand a wrist of a patient with finger sensor 804 connected to housing 802 via wire 806. In some non-limiting embodiment or aspects, first end 805a of housing 802 may be configured to connect to second end 805b of housing 802 via a connection mechanism (e.g., a strap, a Velcro fastener, a button, etc.) In some non-limiting embodiments or aspects, housing 802 may include a glove configured to be worn on a hand of a patient such that housing 802 fully covers the hand and wrist of the patient as shown in FIG. 6D, which enables finger sensor 804 to be connected to housing 802 without the use of an exposed wire.

[0097] Conductivity probes or electrodes 810 may provide a direct conductive contact with the skin of a patient, for example, for a skin resistance sensor configured to detect a skin resistivity of a patient. Tissue electrical properties may be measured with a direct current and / or an alternating current, including various RF and microwave frequencies up to and including visible light.

[0098] Disposable adhesive protector 812 may include a disposable film configured to reduce or eliminate direct contact of housing 802 with a patient. For example, disposable adhesive protector 812 may include a sheet (e.g., a plastic sheet, a vinyl sheet, a latex sheet, a paper sheet, etc.) including a first side configured to directly contact a patient and a second side including an adhesive configured to adhere disposable adhesive protector 812 to a side of housing 802 that faces the patient when contact sensor device 800 is worn by the patient. In such an arrangement, disposable adhesive protector 812 may include openings sized and shaped to enable conductivity probes or electrodes 810 to directly contact the skin of the patient through disposable adhesive protector 812, or adhesive protector 812 may contain segments of conductive material to make or enhance contact between the skin and contact sensor device 800.

[0099] Selected aspects of contact sensors 500, 800 may be disposable or single use and other aspects may be reusable or multi-use depending upon an approach taken to cross contamination reduction and prevention and / or the cost of various aspects. This may include a spectrum of options. At one end the spectrum, contact sensors 500, 800 may be totally multi-use and, for example, being decontaminated by spraying, wiping, or immersing in a cleaning solution or having a surface that kills any biological active entities and / or catalyzes the destruction of contaminating chemicals to, on the other end of thespectrum of options, the sensors 500, 800 being fully single use and being thrown out or given to the patient to take home and use elsewhere as their wellbeing and healthcare needs may find useful. Intermediate aspects or embodiments on this spectrum of multiusability may provide a single use, single layer material between the contact surface and the skin; may envelop the sensor in a single use sheath (e.g., sheath 550, etc.); may involve some sensors or aspects of the sensor to be single use, for example a thermistor or the photo diodes and photo transistor of a pulse oximeter, while the electronics that read the sensors are reusable; may provide for all the sensors and material contacting the skin to be single use while the data processor, batteries, and communication parts of contact sensors 500, 800 may be reusable.

[0100] Referring again to FIGS. 1A and 1 B, user device 108 may include one or more devices capable of receiving information and / or data from fluid injection system 102, imaging system 104, sensor system 106, management system 110, and / or auxiliary system 112 (e.g., via communication network 114, etc.) and / or communicating information and / or data to fluid injection system 102, imaging system 104, sensor system 106, management system 110, and / or auxiliary system 112 (e.g., via communication network 114, etc.). For example, user device 108 may include one or more computing systems including one or more processors (e.g., one or more computing devices, one or more server computers, one or more mobile computing devices, one or more tablet computers, one or more mobile phones, etc ). In some non-limiting embodiments or aspects, user device 108 may include at least one of the following: injector user interface 156, imager user interface 162, management user interface 172, any combination thereof, and / or the like.

[0101] User device 108 may take on various forms, be called various names, and / or be performed by various specific devices or systems depending upon the user(s) involved and the healthcare environment / system in which it is being used. For example, user device 108 may be a patient device, a patient portal or a patient care portal into which a patient enters information, signs in for a medical appointment or procedure, provides electronic consent, and / or receives information / training / support / comfort about any procedure which is to happen or answers to any questions about a future or past procedure. User device 108 may include the user's personal phone, tablet, and / orcomputer which may be running an application or accessing a web based service to provide functions of non-limiting embodiments or aspects described herein. User device 108 may be a part of a patient care portal provided by the patient's health provider or insurer. User device 108 may be a physician device 108 or physician portal 108 which provides patient data and / or adverse event risk assessment. User device 108 may be specifically associated with one or more of the other devices in this system, for example the fluid injector system 102, the imaging system 104, or the sensor system 106. Additionally, or alternatively, user device 108 may be physically located where it is most advantageous for the user performing a specific function or using a specific output or system aspect. For example, the patient may be using the patient portal (e.g., user device 108) to enter data or receive information in their referring or prescribing physician office or location, in their home, in a waiting area, or even in a public place such as a restaurant or parking lot. For example, a patient or caregiver may be accessing user device 108 wherever it is convenient for them to do so and functionally enabled by a specific implementation of the system. For example, a radiologist may, for example, access user device 108 in their office, in a preparation room, in the imaging suite, or in a reading room. For example, a technologist may access user device 108 through an aspect of management system 110, fluid injection system 102, sensor system 106, and / or imaging system 104.

[0102] Management system 110 may include one or more devices capable of receiving information and / or data from fluid injection system 102, imaging system 104, sensor system 106, user device 108, and / or auxiliary system 112 (e.g., via communication network 114, etc.) and / or communicating information and / or data to fluid injection system 102, imaging system 104, sensor system 106, user device 108, and / or auxiliary system 112 (e.g., via communication network 114, etc.). For example, management system 110 may include one or more computing systems including one or more processors (e.g., one or more computing devices, one or more server computers, one or more mobile computing devices, etc.). As an example, management system 110 may include management control and computation system 166 and / or management user interface 172. In some non-limiting embodiments or aspects, management system 110 may be implemented within fluid injection system 102, imaging system 104, sensorsystem 106, user device 108, and / or auxiliary system 112 (e.g., where auxiliary system 112 may or may not be associated with fluid injection system 102 and / or imaging system 104). In some non-limiting embodiments or aspects, management user interface 172 may be implemented or provided via user device 108.

[0103] Auxiliary system 112 may include one or more devices capable of receiving information and / or data from fluid injection system 102, imaging system 104, sensor system 106, user device 108, and / or management system 110 (e.g., via communication network 114, etc.) and / or communicating information and / or data to fluid injection system 102, imaging system 104, sensor system 106, user device 108, and / or management system 110 (e.g., via communication network 114, etc.). For example, auxiliary system 112 may include one or more computing systems including one or more processors (e.g., one or more computing devices, one or more server computers, one or more mobile computing devices, etc.). As an example, auxiliary system 112 may include hospital information system(s) (HIS) 168, cloud computing and offsite resources 170, electronic medical records (EMR), a radiology information system(s) (RIS), a modality worklist (MWL), a patient portal to a healthcare system, a telemedicine portal, a picture archiving and communication system(s) (PACS), a laboratory information system(s) (LIS), an injection system(s) (e.g., fluid injection system 102, etc.), an imaging system(s) (e.g., imaging system 104, etc.), a smart phone, a tablet computer, or any combination thereof.

[0104] Communication network 114 may include one or more wired and / or wireless networks. For example, communication network 114 may include a cellular network (e.g., a long-term evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a sixth generation (6G) network, a code division multiple access (CDMA) network, etc.), a short range wireless communication network (e.g., a Bluetooth 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., the public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, a controller area network (CAN), a data communication and control for medical imaging systems as disclosed, for example, by U.S. Patent No. 6,970,735,the entire disclosure of which is hereby incorporated by reference in its entirety, and / or the like, and / or a combination of these or other types of networks.

[0105] The number and arrangement of systems and devices shown in FIGS. 1 A and 1 B are provided as an example. There may be additional systems and / or devices, fewer systems and / or devices, different systems and / or devices, and / or differently arranged systems and / or devices than those shown in FIGS. 1 A and 1 B. Furthermore, two or more systems or devices shown in FIGS. 1A and 1 B may be implemented within a single system or device, or a single system or device shown in FIGS. 1A and 1 B may be implemented as multiple, distributed systems or devices. Additionally or alternatively, a set of systems (e.g., one or more systems) or a set of devices (e.g., one or more devices) of system 100 and / or implementation 150 may perform one or more functions described as being performed by another set of systems or another set of devices of system 100 and / or implementation 150.

[0106] Referring now to FIG. 2, shown is a diagram of example components of a device 200 according to non-limiting embodiments. Device 200 may correspond to fluid injector system 102, imaging system 104, sensor system 106, user device 108, management system 110, auxiliary system 112, communication network 114, injector 152, injector control and computation system 154, injector user interface 156, imager 158, imager control and computation system 160, imager user interface 162, contact sensor(s) 164A, non-contact sensor(s) 164B, management control and computation system 166, hospital information system(s) 168, cloud computing and offsite resources 170, and / or management user interface 172, as an example. In some non-limiting embodiments, such systems or devices may include at least one device 200 and / or at least one component of device 200. The number and arrangement of components shown are provided as an example. In some non-limiting embodiments, device 200 may include additional components, fewer components, different components, or differently arranged components than those shown. Additionally, or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

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

[0108] With continued reference to FIG. 2, storage component 208 may store information and / or software related to the operation and use of device 200. For example, storage component 208 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid-state disk, etc.) and / or another type of computer-readable medium. Input component 210 may include a component that permits device 200 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively, input component 210 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 212 may include a component that provides output information from device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). Communication interface 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 214 may permit device 200 to receive information from another device and / or provide information to another device. For example, communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency(RF) interface, a universal serial bus (USB) interface, a Wi-Fi® interface, a cellular network interface, and / or the like.

[0109] Device 200 may perform one or more processes described herein. Device 200 may perform these processes based on processor 204 executing software instructions stored by a computer-readable medium, such as memory 206 and / or storage component 208. A computer-readable medium may include any non-transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices. 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, software instructions stored in memory 206 and / or storage component 208 may cause processor 204 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments described herein are not limited to any specific combination of hardware circuitry and software. The term “configured to,” as used herein, may refer to an arrangement of software, device(s), and / or hardware for performing and / or enabling one or more functions (e.g., actions, processes, steps of a process, and / or the like). For example, “a processor configured to” may refer to a processor that executes software instructions (e.g., program code) that cause the processor to perform one or more functions.

[0110] Referring now to FIG. 3, shown is a flow diagram for a method 300 for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects. The steps shown in FIG. 3 are for example purposes only. It will be appreciated that additional, fewer, different, and / or a different order of steps may be used in some non-limiting embodiments or aspects. In some non-limiting embodiments or aspects, a step may be automatically performed in response to performance and / or completion of a prior step.

[0111] As shown in FIG. 3, at step 302, method 300 includes preparing for a test portion of a patient procedure. For example, management system 110 may prepare for a test portion of a patient procedure. As an example, management system 110 may prepare fluid injection system 102 including injector 152, imaging system 104 includingimager 158, and / or sensor system 106 including contact sensor(s) 164A and / or noncontact sensor(s) 164B for a test portion of a patient procedure.

[0112] Management system 110 may communicate, with fluid injection system 102 including fluid injector 152, imaging system 104 including imager 158, sensor system 106 including at least one sensor 164, and user device 108, procedure data associated with a patient and a patient procedure associated with the patient. For example, management system 110 may obtain procedure data associated with a patient and a patient procedure associated with the patient. As an example, management system 110 may receive and / or retrieve procedure data associated with a patient and a patient procedure associated with the patient from at least one of the following: fluid injection system 102, imaging system 104, sensor system 106, user device 108, auxiliary system 112, or any combination thereof. Procedure data may also be obtained directly from the patient by a human or by interaction with a user interface of management system 110 that may prompt a user and / or the patient for and record such data. In general, management system 110 may communicate to the operator to instruct them what to do and, if the operator has any questions, management system 110 may include conversational ability or training information to coach the operator through the tasks which the operator is being asked to perform.

[0113] Procedure data may include procedure data, patient data, sensor data, test injection feedback, test imaging results, imaging injection feedback, an injection protocol, an imaging protocol, imaging results, or any combination thereof. Procedure data may include a procedure order associated with a patient procedure (e.g., an imaging prescription for the patient, an indication of a fluid in injector 152 (e.g., a contrast type, saline, etc.), quality assurance parameters, patient health information (e.g., a CIN risk, patient allergies, etc.), procedure parameters associated with the patient procedure, and / or the like. For example, procedure parameters associated with a patient procedure may include at least one of the following parameters: scheduled patient parameters associated with a scheduled patient (e.g., patient data including parameters associated with a scheduled patient, etc.), scheduled protocol parameters associated with a scheduled injection protocol, or any combination thereof.

[0114] Patient data may include at least one of the following parameters associated with a patient: an age; a gender; a weight; a prior chemotherapy status, such as an adverse peripheral venous status due to long-term oncological treatment, and / or the like (e.g., a yes, a no, a number of cycles of chemotherapy received, etc.); an estimated glomerular filtration rate (eGFR) (e.g., an eGFR of less than 45 ml / min / 1.73 m2, etc.); a thyroid stimulating hormone (TSH) level; a Triiodothyronine (FT3) Thyroxine (FT4) ratio (FT3 / FT4); an amount or level of an environmental influence (e.g., a regional iodine saturation or nutrition amount or level for a region or location associated with the patient, etc.); a prior reaction to a previous fluid injection status (e.g., a yes, a no, a level, etc.); an atopic disorder status (e.g., a yes, a no, a level, etc.); a medical status as it relates to existence of diabetes and / or hypertension, such as a diabetic nephropathy status, and / or the like (e.g., a yes, a no, a level, etc.); a congestive heart failure status (e.g., a yes, a no, a level, etc.); a hematocrit level; a known or suspected renal failure status (e.g., a yes, a no, a level, etc.); a malignancy status (e.g., a yes, a no, a level, etc.); an implanted device for a central venous access status (e.g., a yes, a no, a level, etc.); ambulatory status of the patient or any neurological deficits that would require some extra patient care attention for the caregiver; a type of a medication; a type of fluid media to be administered in a fluid injection; a type of a fluid injection and / or imaging exam; a flow rate associated with a fluid injection; a catheter gauge associated with a fluid injection; a total volume of fluid associated with a fluid injection; a pressure curve associated with a fluid injection, an injection site associated with a fluid injection; any combination thereof, and / or the like. In some non-limiting embodiments or aspects, patient data may include sensor data determined before a fluid injection is administered to a patient and / or sensor data determined during and / or after one or more previous fluid injections previously administered to the patient.

[0115] In some non-limiting embodiments or aspects, management system 110 may provide and / or implement a patient care system or patient care portal that is accessible via an application (e.g., via user device 108, etc.), for example, as software on a personal device, a smart phone, a tablet computer and / or other computer, a web site, and / or a custom device which may be loaned or given to a patient. The patient care portal may promote the patient's wellbeing, primarily before the fluid delivery and imaging study byproviding information to the patient and collecting information from the patient as described herein. The application may provide patient support for imaging procedure referrals, screening, preparation, access, education (e.g. videos and / or written / graphical materials, etc.), health information management, and / or patient feedback to providers on user experience. For example, the application may be used to consolidate and manage patient data, sensor data, and / or other information during the chain of patient care steps for a diagnostic imaging procedure, from an initial prescription for an imaging scan to tracking diagnostic outcomes for future reference. The application may promote mental wellbeing by providing the patient with relevant information to help the patient have a more successful, for example, to be less likely to startle and move in a manner that can reduce the quality of the scan, and more positive diagnostic imaging experience. The application may make patient experience information more visible to the patient community, referring clinicians, provider networks, and / or others to improve diagnostic imaging procedures as well as to other aspects of management system 110, such as the automated diagnostic imaging procedures of management system 110. The application may eliminate or substantially reduce a likelihood of missed appointments due to uninformed patients, cancelled appointments due to fear of the procedure, workflow delays while a patient fills out forms, a likelihood of poor imaging outcomes due to lack of adequate patient preparation or patient inability to accomplish certain tasks associated with a procedure, for example breathing at the correct times, and / or patient discomfort due to patient uncertainty or unfamiliarity with the normal aspects of the procedure. Accordingly, the patient care portal or system may provide healthcare community-based diagnostic imaging patient support, tie user experience to diagnostic imaging, link information together for the patient to help provide a better patient experience, improve patient referral and care to obtain improved diagnostic imaging experiences and outcomes, increase patient compliance and comfort, more efficiently utilize diagnostic imaging center resources, and / or improve diagnostic imaging quality.

[0116] Management system 110 may obtain patient data and / or sensor data associated with a patient via the application for the patient care portal or system. The application may be accessible by a referring physician that prescribes an imaging scan to assist in scheduling the imaging scan for the patient. For example, the application mayapply one or more user selected filters and / or a weighted sum algorithm (e.g., a location of the patient, an insurance type of the patient, a type of scan prescribed, quality ratings, etc.) to a list of available imaging center locations to determine an imaging center location to recommend to the patient. The application may provide information to the patient to help the patient prepare for and learn about the imaging procedure experience. The patient portal displayed on user device 108 may enable the patient to preconfigure imaging scan room options, such as ambiance or lighting, music, temperature, and / or the like before the imaging scan and / or provide additional patient data. This data may be automatically communicated to the imaging suite by management system 110 at the time of the patient's scan. The patient portal displayed on user device 108 may provide information (e.g., a video, etc.) of what the patient may expect the day of the scan and / or a calendar notification and direction to the imaging scan location, which may improve patient comfort, wellbeing and / or satisfaction.

[0117] At a check-in for the imaging scan, patient data associated with the patient may be automatically synched or retrieved by management system 110 from auxiliary system 112 and / or the cloud and / or the patient portal via user device 108, thereby reducing an amount of time needed for the patient to check-in. Management system 110 may automatically retrieve medical records and patient preferences before or during check-in and present the medical records and patient preferences to the patient via the application on user device 108 for faster confirmation of the correctness and completeness of the records and the patient's preferences. Management system 110 may use the application to provide an automated and integrated consent process in which the patient electronically consents (e.g., on user device 108, etc.) to one or more procedures via the application, which may improve and / or increase a technologist's quality time with the patient. Management system 110 may use the application to assess or confirm ambulatory status of the patient, any neurological deficits of the patient, and / or other conditions of the patient that may require some extra patient care attention from the caregiver.

[0118] After check-in, veins of the patient may be scanned by imaging system 104 (e.g., by one or more cameras of imaging system 104, etc.), and management system 110 may analyze and / or save the scanned images of the veins of the patient. A systemsuch as that disclosed in U.S. Patent Application Publications 2004 / 0171923A1 and / or 2008 / 01471 7A1 , filed on Dec. 6, 2003 and Dec. 18, 2006, respectively, the entire disclosure of each of which is hereby incorporated by reference in its entirety, may be used to assess a patient's veins and optionally facilitate access to the veins. For example, the patient data and vein analysis may be used to adjust or recommend adjustments or limits upon a fluid injection protocol and / or an imaging protocol for the patient, which may be presented to a user (e.g., a radiologist, etc.) via the application on user device 108 for approval or directly to the injector system 102 or the imaging system 104. Sensor system 106 (e.g., a smart bed sensor, a camera, contact sensor device 500 and / or 800, etc.) may continuously determine patient data, sensor data, and / or scan data associated with the patient, and management system 110 may adjust, based on the measured patient data, sensor data, and / or sensor data, the fluid injection protocol and / or the imaging protocol for the patient, which may be presented to a user (e.g., a radiologist, etc.) via the application on user device 108 for approval by the user. Or, said adjustment may be made automatically, within preselected limits. For example, a patient based dosage and a cardiac output of the patient enables a fluid injection protocol and scan duration to be adjusted for the patient. Sensors may be physically a part of the imaging system 104, the fluid injection system 102, and / or the space or environment in which both are operating. Sensors may be freestanding or placed on the patient. The operator may wear sensors, for example, a virtual reality display, a body camera, and / or the like.

[0119] Sensor data may include at least one of the following parameters associated with a patient: firstly, parameters which may be affected by an injection and / or changes in patient wellbeing such as data associated with programmed flow rates; actual or measured flow rates, pressures; concentrations, and / or other injection related data; a heart rate; a sound or vibration (e.g., a sound or vibration associated with a fluid inflow, a sound or vibration proximate an injection site, etc.); a temperature (e.g., a temperature of a fluid inflow, a temperature proximate an injection site, a localized temperature, a tissue temperature, etc.); an oxygen saturation level (e.g., an oxygen saturation of a fluid inflow, an oxygen saturation proximate an injection site, etc.); a pulse rate; an ECG; a body fat / water-content ratio; a tissue impedance; a vessel distribution level; a vessel diameter; a hydration level; a hematocrit level; a skin resistivity; a blood pressure; a muscle tensionlevel; a light absorptivity level; a shaking or trembling or a movement / motion (e.g., a yes, a no, a level, etc.); an arm position; an arm circumference; a respiration rate; a respiration depth; an amount of absorbed radiation; a tightness, a position stability, and / or a contact integrity of contact sensor device 500 and / or 800; an amount of swelling and / or displacement; an EMG; a skin color and / or a change thereof; a surface vessel dilation (flushing) amount; a bio-impedance; a light absorptivity; an inflammation level; a patient ability to hold breath, a patient ability to follow instructions, a patient ability to timely follow instruction, a patient ability to remain still or unmoving; secondly, parameters which are not likely to be immediately affected by an injection and / or changes in a patient wellbeing such as a fat / muscle ratio; a hemoglobin level; and thirdly, environmental parameters such as an environmental temperature of an environment surrounding the patient, a barometric pressure in an environment surrounding the patient; an ambient light level; an ambient sound level; or any combination thereof. Sensor data may be determined (e.g., determined, collected, acquired, captured, measured, sensed, etc.), before, during, and / or after a fluid injection (and / or before, during, and / or after a test injection administered to a patient before the fluid injection).

[0120] For example, injection system 102 including injector 152 may sense a pressure associated with an injection operation, a pressure limiting causing a flow reduction and / or a loss of timing, an injection volume (e.g., an insufficient injection volume, etc.), a keep vein open (KVO) pressure, and / or the like. For example, imaging system 104 including imager 158 may sense air in a fluid path element, an unexpected delay in enhancement, a scanner scout image / topogram, and / or the like. For example, management system 110 may test for blood vessel access using powered fluid injector systems as disclosed in U.S. Patent Application Publication No. 2021 / 0125697A1 , the disclosure of which is hereby incorporated by reference in its entirety.

[0121] Multiple data processors, data paths, and / or data analysis algorithms may be used to condition various forms and / or streams of procedure data, patient data, and / or sensor data and / or to combine the various forms and / or streams of patient data and / or sensor data into new forms and / or new streams of data and / or to discriminate additional streams of data. The procedure data, patient data, and / or sensor data and / or the data streams thereof may be used by management system 110 to make recommendations toa user and / or to control operations of fluid injection system 102 and / or imaging system 104 (e.g., to determine whether to enable and / or prompt the user to a next step of the workflow for the patient procedure, to disable an injection and / or imaging operation, to enable an injection or imaging operation, to set or adjust one or more injection and / or imaging protocols, to determine whether an injection is a normal injection proceeding as expected, to determine a wellbeing level of a patient, to control fluid injection system 102 and / or imaging system 104 in response to such determinations, etc.). For example, the recommendations and / or system control may enable medical patient caregivers trained in patient safety in relation to system 100 and untrained in the detailed operation of the injection and imaging equipment to place a patient in the imaging unit and once the patient is safely in place, to initiate a scan using system 100; allow a nurse / technologist to focus on patient care and safety, give more personal care to the patient they are with, help ensure compliance with practices guidelines and policy, improve repeatability, consistency, and quantification; and / or the like.

[0122] In some non-limiting embodiments or aspects, management system 110 may determine and / or provide, based on patient data and / or sensor data associated with a patient, a prediction associated with the patient (e.g., an initial risk predication, a test prediction, a current risk prediction, etc.) and / or a wellbeing of the patient as described in U.S. Patent 11 ,896,352, granted February 13, 2024, the disclosure of which is hereby incorporated by reference in its entirety.

[0123] Referring also to FIGS. 4A-4C, shown is a workflow diagram of an implementation 400 of a method 300 for automated diagnostic imaging procedures, according to some non-limiting embodiments or aspects. The workflow steps shown in FIGS. 4A-4C are for example purposes only. It will be appreciated that additional, fewer, different, and / or a different order of workflow steps may be used in some non-limiting embodiments or aspects. In some non-limiting embodiments or aspects, a workflow step may be automatically performed in response to performance and / or completion of a prior step.

[0124] As shown in FIG. 4A, at reference number 402, before a patient arrives at an imaging location, management system 110 may obtain (e.g., via an application on user device 108, etc.) patient data associated with the patient including a consent of the patientfor conducting the patient procedure. At reference number 404 of FIG. 4A, management system 110 may provide (e.g., via an application on user device 108, etc.) coaching and / or preparation instructions to the patient.

[0125] After the patient arrives at the imaging location, as shown at reference number 406 of FIG. 4A, management system 110 may obtain (e.g., via an application on user device 108, from fluid injection system 102, imaging system 104, sensor system 106, auxiliary system 112, etc.) patient data associated with the patient including patient parameters including a patient identifier associated with the patient (e.g., a unique identifier, etc.) to “check-in” the patient, the consent of the patient for conducting the patient procedure (e.g., if not previously obtained prior to the patient’s arrival, etc.), procedure data associated with the patient procedure including a procedure order associated with the patient procedure and / or procedure parameters associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and / or the like. For example, the procedure data may include patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient. Management system 110 may provide (e.g., via user device 108, etc.) a checklist for a local caregiver including prompts for any additional / missing data needed from the patient. Fluid injector 152 may be disabled, for example, by management system 110, from performing a fluid injection operation for the patient procedure, and / or imager 158 may be disabled, for example, by management system 110, from performing an imaging operation for the patient procedure.

[0126] Management system 110 may provide one or more recommendations, prompts, and / or alerts to the user. For example, at one or more appropriate stages in the procedure flow, management system 110 may provide a prompt to administer a medication to the patient before the fluid injection; a prompt to adjust an injection protocol for the fluid injection and / or an imaging protocol for an imaging scan; a prompt to prepare the patient before the fluid injection; a prompt to consult a specialist physician on the at least one adverse event; a prompt to observe and / or follow-up with the patient after the fluid injection and / or the imaging scan; an indication that a procedure is completed; an indication that a procedure executed OK and / or not OK; a local and / or remote scannerreplicated sound of the injector, matching and / or different local and remote information displays; an indication of user hesitancy during programming; an indication of whether a remote operator is looking at a correct injector at a correct site with a correct patient; a real-time display of injection parameters (e.g., a pressure graph, injection phases, etc.); a documentation of adverse events (e.g., extravasation) or near misses of adverse events; matching or different local and remote information displays can match or be different; an injector protocol, a imaging protocol, a combined injection and imaging protocols; an indication of a quality of an image; an indication that an injection protocol and an imaging protocol match (and / or a breathing protocol) match; an indication that injection parameters are restricted to a certain range (e.g. a restricted volume, a restricted duration, a restricted injection time, etc.); recommended injection parameters to correspond to an imaging protocol; an indication of sending data outputs to RIS any combination thereof; and / or the like.

[0127] In some non-limiting embodiments or aspects, at one or more appropriate points or at an end of the procedure flow, management system 110 may provide one or more predictive maintenance predictions as disclosed by U.S. Patent No. 11 ,232,862, the disclosure of which is hereby incorporated by reference in its entirety. In some nonlimiting embodiments or aspects, management system 110 may provide the one or more predictive maintenance predictions via independent workflow aware user interfaces as disclosed by U.S. Patent No. 11 ,090,440, the disclosure of which is hereby incorporated by reference in its entirety.

[0128] Management system 110 may determine and recommend actions that a user (e.g., a healthcare worker, etc.) should take in order to proceed in the workflow for the patient procedure and / or to reduce a probability of the patient experiencing an adverse event. As an example, management system 110 may consult a look-up table and / or apply an algorithm (e.g., a hard coded or a machine learning model, etc.) to the procedure data to determine one or more prompts or recommendations to provide to the user to progress in the workflow for the patient procedure (e.g., to ensure a threshold or checklist for performing a next step of the workflow for the patient procedure is satisfied, etc.), to reduce the probability of the patient experiencing the adverse event, and / or to adjust oneor more thresholds to be used by a sensor for monitoring for a good injection and / or an adverse event.

[0129] Management system 110 may monitor for one or more conditions associated with the patient procedure based the procedure data (e.g., based on sensor data received from injection system 102, imager system 104, sensor system 106, etc.). For example, management system 110 may monitor for and alert the user to at least one of the following conditions: over-pressure disarms; premature injection termination; unexpected injector and scanner timing; no injection when an injection is expected; an over-rate injection, an over and / or under-volume injection, an over and / or under-pressure injection; a system error (e.g., a critical error, a non-critical critical error for any component within system 110, such as disclosed by U.S. Patent Application Publication No. 2022 / 0068471 A1 , the entire disclosure of which is hereby incorporated by reference in its entirety); a rule exception (e.g., a catheter rules set, pediatric injector guardrails, etc.); image artifacts; over enhancement and / or image saturation; under enhancement at specified ROI's; image noise beyond expected (SNR); under-rate (e.g., tolerances, etc.); venous contamination; unusual pressure curves to indicate fluid path breaks; premature enhancement (e.g., KVO issues, etc.); no enhancement or opacification where expected; a patient movement (e.g., providing breathing instruction or auto instruction not to move, for example, as disclosed in U.S. Patent No. 11 ,510,629, the disclosure of which is hereby incorporated by reference in its entirety, etc.); a patient adverse reaction; insufficient volume when programming; insufficient volume trigger for saline if too much saline is delivered via KVO or test injection(s); a maintenance status for devices involved (e.g., recently calibrated, checked out, etc.); a patient and / or user help button actuation; patient vocalizations and / or sounds; contrast in an unwanted location (e.g., nuclear medication extravasation, etc.); an air injection; an occlusion; test injection pressure to monitor for patency and / or incorrect catheter size being used; impedance to predict pressure limiting; breathing rhythm for adjusting breathing instructions according to patient breathing rhythm; communication interface drop outs and / or errors; operator hesitancy and / or programming statistics (e.g., to monitor for operator difficulty, etc.); any combination thereof; and / or the like. In some non-limiting embodiments or aspects, management system 110 may monitor fluid injection system 102 as disclosed by U.S. PatentApplication Publication No. US2022 / 0375586A1 , the disclosure of which is hereby incorporated by reference in its entirety. Management system 110 may provide the one or more recommendations, prompts, and / or alerts to the user in response to detecting the one or more conditions associated with the patient procedure based the procedure data.

[0130] Management system 110, may recommend to the healthcare provider to control and / or adjust one or more operations of fluid injection system 102 and / or imaging system 104, and / or where legally permitted, may automatically control and / or adjust one or more operations of fluid injection system 102 and / or imaging system 104. For example, management system 110 may recommend for manual adjustment or automatically adjust an injection protocol for the fluid injection (e.g., adjust a maximum flow rate, adjust a maximum pressure, adjust an injection duration, adjust a total volume of fluid or contrast delivered or to be delivered (e.g. to reduce total iodine loading), etc.) and / or an imaging protocol for an imaging scan (e.g., adjust a scan time and / or duration (e.g. to accommodate a patient who cannot hold their breath for an initially planned scan duration), adjust kVp (e.g. reduce kVp to allow for an adequate image contrast with a reduced total iodine loading), adjust breathing instructions, etc.). As an example, management system 110 may consult a look-up table and / or apply an algorithm (e.g., a response surface, a machine learning model, etc.) to the initial risk prediction and / or the patient data and / or the sensor data used to generate the initial risk prediction to determine one or more adjustments to the injection protocol and / or the imaging protocol that may reduce the probability of the patient experiencing the adverse event.

[0131] Management system 110 may determine and recommend, based on the procedure data, a prompt to administer a medication to the patient before the contrast media injection according to applicable guidelines (e.g., American College of Radiology (ACR) guidelines, etc.) and / or a prompt to observe the patient for a predetermined interval (e.g., for a time period longer than normal for a high risk patient) after the contrast media injection while monitoring one or more parameters of the patient. For example, based on patient data associated with individualized renal function of the patient, such as laboratory surrogate parameters thereof (e.g., eGFR, etc.) and / or a current medication of the patient, management system 110 may determine a prompt to prepare the patient before the contrast media injection according to applicable guidelines (e.g., European Society ofUrogenital Radiology guidelines, etc.) associated with contrast media induced nephrotoxicity, such as by administering intravenous hydration, and / or the like, a prompt (and / or an automatic control) to adjust an injection protocol for the contrast media injection and / or an imaging protocol for an imaging scan, and / or a prompt to follow-up with the patient with respect to renal function after the exam, for example to reduce the total iodine given to the patient. For example, based on patient data associated with a known thyroid disorder of the patient, an environmental influence of the patient (e.g., a regional iodine saturation or nutrition for a region in which the patient lives, etc.), and / or a current medication of the patient, management system 110 may determine prompt to forgo the contrast media injection and associated imaging exam until a consultation with an endocrinologist is obtained due association with a thyroid disorder (e.g., thyrotoxicosis, etc.) and / or a prompt to administer a medication to the patient before the contrast media injection.

[0132] Management system 110 may determine, based on the procedure data, whether a threshold (e.g., a checklist, etc.) for performing a next step of the workflow for the patient procedure is satisfied (e.g., whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied, whether a threshold for performing an imaging portion of the patient procedure associated with the patient is satisfied, etc.). For example, a threshold for performing a next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) may include at least one of the following: whether a user input associated with a prompt provided to the user is received, whether a user confirmation associated with current or previous step of the workflow for the patient procedure is received, whether one or more procedure parameters and / or one or more patient parameters have been verified, any combination thereof, and / or the like. As an example, management system may determine based on the procedure data, whether a threshold (e.g., a checklist, etc.) for performing a next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: providing, via the user device, at least one prompt to the user; and receiving, viathe user device, at least one user input associated with at least one user confirmation of the at least one prompt.

[0133] As shown at reference number 408 of FIG. 4A, management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient. As an example, management system 110 may verify that a name, a gender, a birthdate, a weight, a renal function, a prior adverse event, and / or the like associated with the patient correspond to a name, a gender, a birthdate, a weight, a renal function, a prior adverse event, and / or the like associated with the scheduled patient.

[0134] As shown at reference number 410 of FIG. 4A, management system 110 may be configured to determine, based on the procedure data, whether the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying, based on the patient parameters, the procedure parameters, and at least one standards-based or institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule. For example, management system 110 may apply an algorithm or aspects of one or more algorithms, which may be an adaptation or implementation of one or more or a combination of: an individual physician's practice, a professional society guideline, and / or a hospital procedure into computer code, to the procedure data associated with the patient to determine whether the patient procedure associated with the patient corresponds to the at least one institutional rule. In such an example, different hospitals may have different algorithms or aspects of one or more algorithms based on a local preference, a practice, a country, and / or other factors associated with the different hospitals. In another aspect or embodiment, management system 110 may present the patient data to the physician or healthcare provider who in his / her head may make the assessment of risk, wellbeing, ordistress, which may be manually entered into management system 110 for use in subsequent steps.

[0135] As shown at reference number 412 of FIG. 4A, management system 110 may provide an alert (e.g., via user device 108, etc.) indicating to the user what supplies (e.g., IV lines, catheters, etc.) associated with the patient procedure are to be ready / prepared and / or provide a list of the supplies associated with the patient procedure for the user to collect and prepare. If prompted by the user, management system 110 may provide further details about the supplies and / or may provide instructions on how to prepare relevant supplies. As shown at reference number 414 of FIG. 4A, management system 110 may receive (e.g., via user device 108, etc.) user confirmation that the supplies associated with the patient procedure are ready / prepared. For example, management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the user confirmation that the supplies associated with the patient procedure are ready / prepared has been received.

[0136] As shown at reference number 416 of FIG. 4A, management system 110 may provide (e.g., via user device 108, etc.) one or more recommendations and / or alerts to the user. For example, management system 110 may provide a recommended IV placement location on the patient body and / or a recommended IV size. As an example, management system 110 may apply one or more rules (e.g., a rules engine, etc.) to the procedure data (e.g., a prior history with patient and procedure need, a max flow rate on needle size and location, etc.) to determine the recommended IV placement location on the patient body and / or the recommended IV size. At this time management system 110 may provide (e.g., via user device 108, etc.) a prompt to the user to install the IV in the patient. Management system 110 (e.g., via user device 108, etc.) may provide training or coaching material to help the user with IV placement. Management system 110 (e.g., via user device 108, etc.) may also provide the ability for the user to summon help with the IV placement if needed.

[0137] After the user places the IV in the vein of the patient, as shown at reference number 418 of FIG. 4A, management system 110 may receive (e.g., via user device 108,etc.) user confirmation that the patient IV is installed in the patient. For example, management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the user confirmation that the patient IV is installed in the patient has been received. At this time management system 110 may provide (e.g., via user device 108, etc.) a prompt to the user to situate the patient in imager 158.

[0138] After the user situates the patient in imager 158, as shown at reference number 420 of FIG. 4A, management system 110 may receive (e.g., via user device 108, etc.) user confirmation that the patient is situated in imager 158. For example, management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the user confirmation that the patient is situated in imager 158 has been received. Additionally, or alternatively, management system 110 may confirm proper positioning via one or more sensors, for example, via a camera monitoring the patient in the imager and / or sensors on the patient bed. At this time management system 110 may provide (e.g., via user device 108, etc.) a prompt to load injector 152 with the fluids for injection (e.g., with saline, with contrast, etc.). Management system 110 (e.g., via user device 108, etc.) may help coach the user on how to load the injector and may receive communications from the injector as the steps are completed. If an unexpected event happens, management system 110 (e.g., via user device 108, etc.) may inquire about the event and / or coach the user to correct the event.

[0139] After the user loads injector 152 with fluids for injection, as shown at reference number 422 of FIG. 4A, management system 110 may verify that injector 152 is loaded with the correct fluids, for example contrast and saline. For example, the procedure parameters may include a scheduled contrast associated with the patient procedure, and management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of thepatient procedure associated with the patient is satisfied, etc.) by: receiving, from fluid injection system 102, contrast data associated with a contrast loaded in injector 152; and verifying, based on the contrast data associated with the contrast loaded in injector 152 and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure. At this time, management system 110 may provide (e.g., via user device 108, etc.) a prompt to prime each patient line.

[0140] As shown at reference number 424 of FIG. 4B, management system 110 may receive an indication when each patient line is primed. In some non-limiting embodiments or aspects, fluid injection system 102 may automatically prime each patient line in response to that line being connected to injector 152 and / or provide an indication to management system 110 that each line is primed. In some non-limiting embodiments or aspects, the user may manually prime each patient line connected to injector 152 and / or provide the indication to management system 110 that each line is primed. Management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the indication each patient line is primed has been received. At this time management system 110 may provide (e.g., via user device 108, etc.) a prompt to connect injector 152 to the patient IV.

[0141] After the user connects injector 152 to the patient IV, as shown at reference number 426 of FIG. 4B, management system 110 may receive (e.g., via user device 108, etc.) user confirmation that injector 152 is connected to the patient IV. In some nonlimiting embodiments or aspects, management system 110 may receive a signal from a camera or other sensor that the injector 152 is connected to the patient IV. For example, management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing the next portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the user confirmation injector 152 is connected to the patient IV has been received. At this timemanagement system 110 may provide (e.g., via user device 108, etc.) a prompt to perform a patency check.

[0142] Management system 110 may provide for the injector 152 to conduct a patency check as shown at reference number 428. Such a patency check may involve injecting a modest volume of saline at the flow rate of the normal injector for several seconds to confirm that the IV catheter is open, situated in a vein, and that fluid moves down the vein towards the central circulation. The patency check may be initiated by the user triggering the injector 152 after the management system 110 enables the injector 152 to perform the injection operation or patency check, or the patency check may be initiated automatically by the management system 110 directly at the injector 152. To confirm patency, experienced users touch the patient’s limb just downstream from the catheter tip. Optionally, one or more of the sensors described here may listen, look, or otherwise sense for satisfactory flow into and down the vein and report the same to management system 110.

[0143] After the user performs the patency check, as shown at reference number 428 of FIG. 4B, management system 110 may receive user confirmation of the patency check (e.g., via user device 108, etc.) and / or sensor confirmation of the patency check (e.g., from sensor system 106, etc.). If the patency check shows an irregularity, management system 110 may provide (e.g., via user device 108, etc.) a recommendation to the user for addressing the irregularity. Management system 110 may perform other fluid path checks based on sensor data received from sensor system 106 and / or injection system 102. Management system 110 may be configured to determine, based on the procedure data, whether the threshold for performing the next step of the workflow for the patient procedure is satisfied (e.g., whether the threshold for performing a test portion of the patient procedure associated with the patient is satisfied, etc.) by: verifying that the user confirmation of the patency check and / or the sensor confirmation of the patency check has been received.

[0144] As shown at reference number 430 of FIG. 4B, management system 110 may set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure, a test imaging protocol associated with the test portion of the patient procedure, an imaging injection protocol associated with an imaging portion of thepatient procedure, an imaging protocol associated with the imaging portion of the patient procedure, or any combination thereof. For example, management system 110 may automatically set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and / or an imaging injection protocol associated with an imaging portion of the patient procedure (e.g., set a maximum flow rate, set a maximum pressure, set an injection duration, set a total volume of fluid or contrast delivered or to be delivered (e.g. to reduce total iodine loading), etc.) and / or automatically set, based on the procedure data, a test imaging protocol associated with the test portion of the patient procedure and / or an imaging protocol associated with the imaging portion of the patient procedure (e.g., set a scan time and / or duration (e.g. to accommodate a patient who cannot hold their breath for an initially planned scan duration), set kVp (e.g. reduce kVp to allow for an adequate image contrast with a reduced total iodine loading), set breathing instructions, etc.). As an example, management system 110 may consult a look-up table and / or apply an algorithm (e.g., a response surface, a machine learning model, etc.) to the initial risk prediction and / or the patient data and / or the sensor data used to generate the initial risk prediction to determine one or more parameters for the injection protocol and / or the imaging protocol that may reduce the probability of the patient experiencing the adverse event.

[0145] In some non-limiting embodiments or aspects, management system 110 may set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure, a test imaging protocol associated with the test portion of the patient procedure, an imaging injection protocol associated with an imaging portion of the patient procedure, an imaging protocol associated with the imaging portion of the patient procedure, or any combination thereof using a system for standardized MRI examinations with patient-centric scan workflow adaptations as disclosed by U.S. Patent Application Publication No. 2022 / 0068472A1 , the entire disclosure of which is hereby incorporated by reference in its entirety. In some non-limiting embodiments or aspects, management system 110 may set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure, a test imaging protocol associated with the test portion of the patient procedure, an imaging injection protocol associated with an imaging portion of the patient procedure, an imaging protocol associated with the imagingportion of the patient procedure, or any combination thereof by generating one or more protocols embodying contrast and radiation dose management techniques as disclosed by International Patent Application No. PCT / US2023 / 032215, the entire disclosure of which is hereby incorporated by reference in its entirety. In some non-limiting embodiments or aspects, management system 110 may set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure, a test imaging protocol associated with the test portion of the patient procedure, an imaging injection protocol associated with an imaging portion of the patient procedure, an imaging protocol associated with the imaging portion of the patient procedure, or any combination thereof using systems and methods for associating injector and scanner protocols as disclosed by International Patent Application No. WO2023212188A1 , the disclosure of which is hereby incorporated by reference in its entirety.

[0146] As shown at reference number 432, management system 110 may determine, based on the procedure data, whether the threshold for performing the test portion (e.g., a test injection, etc.) of the patient procedure associated with the patient is satisfied. For example, management system 110 may verify that each aspect of the threshold or item on the checklist has occurred (e.g., each prompt responded to, each user confirmation received, each verification of patient data satisfactorily performed, etc.). If management system 110 determines that one or more aspects of the of threshold for performing the test portion (e.g., a test injection, etc.) of the patient procedure associated with the patient is not satisfied, management system 110 may automatically provide a prompt to the user (e.g., via user device 108, etc.) request the user to remedy the unsatisfied aspect (e.g., to provide a user confirmation, load injector 152, proceed with insufficient volume, etc.).

[0147] As shown at reference number 434 of FIG. 4B, management system 110 may enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, fluid injector 152 to perform the fluid injection operation and imager 158 to perform the imaging operation. For example, management system 110 may communicate a command to injection system 102 including injector 152 that causes injection system 102 to enable injector 152 to perform an injection operation. As an example, management system 110 may communicate a command to imaging system 104 including imager 158 that causes imaging system 104to unlock imager 158 to enable imager 158 to perform an imaging operation or scan. In response to enabling fluid injector 152 to perform the fluid injection operation and imager 158 to perform the imaging operation, management system 110 may prompt (e.g., via user device 108, etc.) the user to initiate the test portion of the patient procedure. As shown at reference number 436 of FIG. 4B, management system 110 may receive, from user device 108, a user input including an instruction to initiate the test portion of the patient procedure. In some non-limiting embodiments or aspects, management system 110 may directly initiate the test portion of the patient procedure if regulations allow.

[0148] Referring again to FIG. 3, at step 304, method 300 includes performing the test portion of the patient procedure. For example, management system 110 may perform the test portion of the patient procedure. As an example, management system 110 may control fluid injection system 102 including injector 152, imaging system 104 including imager 158, and / or sensor system 106 including contact sensor(s) 164A and / or noncontact sensor(s) 164B to perform the test portion of the patient procedure. In such an example, and referring also to FIG. 4B, as shown at step 438, in response to receiving the instruction to initiate the test portion of the patient procedure, management system 110 may control fluid injector 1512 to perform the fluid injection operation according to the test injection protocol and imager 158 to perform the imaging operation according to the test imaging protocol.

[0149] As shown in FIG. 3, at step 306, method 300 includes preparing for an imaging portion of the patient procedure. For example, management system 110 may prepare for an imaging portion of the patient procedure. As an example, management system 110 may prepare fluid injection system 102 including injector 152, imaging system 104 including imager 158, and / or sensor system 106 including contact sensor(s) 164A and / or non-contact sensor(s) 164B for an imaging portion of the patient procedure.

[0150] As shown at step 440 of FIG. 4B, management system 110 may receive user confirmation associated with the test injection (e.g., via user device 108, etc.) and / or sensor confirmation associated with the test injection (e.g., from fluid injection system 102, from imaging system 104, from sensor system 106, etc.). For example, fluid injection system 102, imaging system 104, and / or sensor system 106 may provide procedure data including feedback on the test injection to management system 110. For example,management system 110 may communicate with fluid injection system 102 including fluid injector 152, imaging system 104 including imager 158, sensor system 106 including the at least one sensor 164, and / or user device 108 to receive further procedure data associated with the patient and the patient procedure associated with the patient (e.g., further procedure data associated with the test injection, the fluid injection operation performed according to the test injection protocol and / or the imaging operation performed according to the test imaging protocol etc.).

[0151] As shown at step 442 of FIG. 4C, after fluid injector 152 performs the fluid injection operation according to the test injection protocol and imager 158 performs the imaging operation according to the test imaging protocol, management system 110 may disable fluid injector 152 from performing the fluid injection operation for the patient procedure and imager 158 from performing the imaging operation for the patient procedure. For example, management system 110 may communicate a command to injection system 102 including injector 152 that causes injection system 102 to lock injector 152 to prevent injector 152 from performing an injection operation until enabled by management system 110. As an example, management system 110 may communicate a command to imaging system 104 including imager 158 that causes imaging system 104 to lock imager 158 to prevent imager 158 from performing an imaging operation or scan until enabled by management system 110.

[0152] As shown at step 444 of FIG. 4C, management system 110 may adjust, based on the procedure data and / or the further procedure data (e.g., the test injection feedback, etc.), an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure. For example, management system 110 may automatically adjust, based on the procedure data and / or the further procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure (e.g., adjust a maximum flow rate, adjust a maximum pressure, adjust an injection duration, adjust a total volume of fluid or contrast delivered or to be delivered (e.g. to reduce total iodine loading), etc.) and / or automatically adjust, based on the procedure data, an imaging protocol associated with the imaging portion of the patient procedure (e.g., adjust a scan time and / or duration (e.g. to accommodate a patient who cannot hold their breath for an initially planned scanduration), adjust kVp (e.g. reduce kVp to allow for an adequate image contrast with a reduced total iodine loading), adjust breathing instructions, etc.). As an example, management system 110 may consult a look-up table and / or apply an algorithm (e.g., a response surface, a machine learning model, etc.) to the initial risk prediction and / or the patient data and / or the sensor data used to generate the initial risk prediction to determine one or more adjustments to the injection protocol and / or the imaging protocol that may reduce the probability of the patient experiencing the adverse event. (See, e.g. U.S. Patent 11 ,896,352) In some non-limiting embodiments or aspects, management system 110 may automatically control fluid injection system 102 based on a hydraulic resistance as disclosed in U.S. Patent Application Publication No. 2023 / 0181816A1 , the disclosure of which is hereby incorporated by reference in its entirety.

[0153] As shown at step 446 of FIG. 4C, management system 110 may determine, based on the procedure data and the further procedure data (e.g., test injection feedback, etc.), whether a threshold for performing the imaging portion (e.g., an imaging injection, etc.) of the patient procedure associated with the patient is satisfied. For example, management system 110 may verify that each aspect of the threshold or item on the checklist has occurred (e.g., each prompt responded to, each user confirmation received, each verification of patient data satisfactorily performed, etc.). If management system 110 determines that one or more aspects of the of threshold for performing the imaging portion (e.g., an imaging injection, etc.) of the patient procedure associated with the patient is not satisfied, management system 110 may automatically provide a prompt to the user (e.g., via user device 108, etc.) to request the user to remedy the unsatisfied aspect (e.g., to provide a user confirmation, load injector 152, etc.). The management system 110 may also provide guidance to the user on what to do to remedy the unsatisfied aspect and / or provide the user the ability to request help, either local or remote.

[0154] As shown at step 448 of FIG. 4C, management system 110 may enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, fluid injector 152 to perform the fluid injection operation and imager 158 to perform the imaging operation. In response to enabling fluid injector 152 to perform the fluid injection operation and imager 158 to perform the imaging operation, management system 110 may prompt (e.g., via userdevice 108, etc.) the user to initiate the imaging portion of the patient procedure. As shown at reference number 450, management system 110 may receive, from user device 108, a user input including an instruction to initiate the imaging portion (e.g., the imaging injection, etc.) of the patient procedure. Alternatively, if regulations allow it, the management system 110 may automatically initiate the imaging portion (e.g., the imaging injection, etc.) of the patient procedure.

[0155] Referring again to FIG. 3, at step 308, method 300 includes performing the imaging portion of the patient procedure. For example, management system 110 may perform the imaging portion of the patient procedure. As an example, management system 110 may control fluid injection system 102 including injector 152, imaging system 104 including imager 158, and / or sensor system 106 including contact sensor(s) 164A and / or non-contact sensor(s) 164B to perform the imaging portion of the patient procedure. In such an example, and referring also to FIG. 4C, as shown at reference number 452, in response to receiving the instruction to initiate the imaging portion of the patient procedure, management system 110 may control fluid injection system 102 including fluid injector 152 to perform the fluid injection operation according to the imaging injection protocol and imaging system 104 including imager 158 to perform the imaging operation according to the imaging protocol.

[0156] In some non-limiting embodiments or aspects, management system 110 may receive, from sensor system 106 including the at least one sensor 164, when fluid injector 152 is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when fluid injector 152 is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, fluid injector 152 to adjust a flow rate of the fluid injection operation. For example, during the imaging portion of the patient procedure, injection system 102 may control injector 152 to inject an imaging bolus for scan programming. If injection system 102 detects that injector 152 violates a threshold pressure associated with the imaging injection, management system 110 may recommend one or more components of injector 152 for the user to inspect and / or control injector 152 to adjust flow rate of thefluid injection operation. Injection system 102 may perform other checks during the imaging portion of the patient procedure, such as checking for “spongy brake” scenarios, performing an impedance assessment that may cause management system 110 to alert the user that the threshold pressure may be violated, and / or feeding measured parameters into P3T patent algorithm for calculating protocol parameters.

[0157] As shown in FIG. 3, at step 310, method 300 includes performing analysis and / or reporting of the patient procedure. For example, management system 110 may perform analysis and / or reporting of the patient procedure.

[0158] Referring also to FIG. 4C, as shown at reference number 454, management system 110 may receive user confirmation associated with the imaging injection (e.g., via user device 108, etc.) and / or sensor confirmation associated with the imaging injection (e.g., from fluid injection n system 102, from imaging system 104, from sensor system 106, etc.). For example, fluid injection system 102, imaging system 104, and / or sensor system 106 may provide procedure data including feedback on the imaging injection to management system 110. For example, management system 110 may communicate with fluid injection system 102 including fluid injector 152, imaging system 104 including imager 158, sensor system 106 including the at least one sensor 164, and / or user device 108 to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol.

[0159] Management system 110 may perform a scan image assessment of one or more of the medical images acquired by imaging system 104, which may be presented to a user (e.g., a radiologist, etc.) via the application on user device 108 for confirmation of the scan image assessment. For example, management system 110 may apply one or more artificial intelligence based image assessment tools to the scanned images of the patient to assess a quality of the scan and / or provide diagnostic recommendations, such as disclosed by International Patent Application Publication No. W02006 / 116700, the disclosure of which is hereby incorporated by reference in its entirety. The medical scanned images and / or analysis thereof may be stored (e.g., in auxiliary system 112, in the cloud, etc.) for retrieval via the application by the radiology team and / or the patient. Management system 110 may use the application to continuously monitor equipmentand / or supplies and automatically order new equipment and / or supplies when an inventory level fails to satisfy a threshold level and / or equipment breaks or fails.

[0160] As shown at reference number 456 of FIG. 4C, the patient IV may be disconnected from injector 152 and removed from the patient by the user and, as shown at reference number 458 of FIG. 4C, the patient may be removed from imager 158.

[0161] As shown at reference number 460 of FIG. 4C, management system 110 may store (e.g., in auxiliary system 112, in the patient’s EMR, etc.) the contrast used for the injection and / or other procedure information associated with the patient procedure in associated with the identifier of the patient. For example, management system 110 may automatically modify the patient’s record to provide an alert that other tests may be affected by contrast in the patient, and / or the like. As an example, management system 110 may store in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

[0162] As shown at reference number 462 of FIG. 4C, management system 110 may provide an indication (e.g., via user device 108, etc.) that indicates whether system 100 is ready for a next patient and / or other recommended actions for the user to make system 100 ready. Management system 110 may also provide training and / or other aid to the user as requested to help them make system 100 read for the next patient. As shown at reference number 464 of FIG. 4C, management system 110 may begin setup of system 110 for the next patient.

[0163] Although embodiments have been described in detail for the purpose of illustration, it is to be understood that such detail is solely for that purpose and that the disclosure is not limited to the disclosed embodiments or aspects, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment or aspect can be combined with one or more features of any other embodiment or aspect. It is also anticipated that non-limiting embodiments or aspects of the present disclosure may be applied to a wide variety of systems for automated diagnostic imaging procedures with a wide variety of configurations of user interfaces,sensors, and / or operating procedures in a wide variety of locations and / or regulatory environments with different rules on what a human operator has to do and initiate and the qualifications required of that person. For example, in some countries a radiologist may be required to be the person who triggers the injector to do a test injection or an imaging injection. It is also anticipated that all of these (for example, equipment and regulations) may evolve over time. Thus, in some more basic situations, the user may perform a function of the sensor system 106 with the user’s senses being used as a sensor and user input from the user being provided as sensor data. While it is desirable to move to more automatic and, thus, more human error resistance operation, it may not be practical in all situations for practical, legal, economic, or reliability reasons. In other situations some sensor data may be based on user input and other sensor data may be based on non-human input.

[0164] Non-limiting embodiments or aspects of the present disclosure may encompass imaging studies which may involve two or more of any of the injections described herein. For example, a second patency check injection may be performed after resolving an issue that was found and fixed after the initial patency check. The second patency check may be performed to confirm that the issue was fully or satisfactorily resolved. A third patency check may be performed if the problem was not resolved. A second test bolus may be performed if there are regions of interests (ROIs) that are not measurable on a single CT scan even though the regions may be on final scan because of the timing and / or bed motion. Similarly, there may be multiple injections during the imaging procedure itself. Some may be single injections with long holds or pauses programmed into the injection protocol. For example, there is a procedure to study the head and neck where a non-contrast scan is performed followed by an injection of 60ml of contrast at 3ml / s, then the patient remains on the table for 6 minutes, then 40m Is of contrast is injected and bolus tracking is used to scan of the head and neck as soon as the arteries have been sufficiently enhanced by the second bolus of contrast. In other imaging protocols, the multiple injections may be totally separate injections with separate injection protocols.

[0165] As used herein, the terms “caregiver”, “healthcare worker”, “user”, “operator”, “technologist”, “radiographer”, “radiologist”, and / or “doctor” may indicate a person who isallowed by an organization to operate one or more aspects of system 100 and / or by local regulations to operate one or more aspects of system 100, which may be different than other caregivers of the patient, for example, a relative or hired caregiver, even if these other caregivers possess some form of medical training or credentialing.

Claims

WHAT IS CLAIMED IS:

1. A system, comprising: at least one processor configured to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; and in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

2. The system of claim 1 , wherein the at least one processor is further configured to: set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure,wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

3. The system of claim 2, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

4. The system of claim 3, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by:verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

5. The system of claim 4, wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

6. The system of claim 2, wherein the at least one processor is configured to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: providing, via the user device, at least one prompt to the user; and receiving, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

7. The system of claim 2, wherein the at least one processor is further configured to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the testinjection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

8. A method, comprising: communicating, with at least one processor, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; setting, with the at least one processor, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the imaging portion of the patient procedure; receiving, with the at least one processor, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; andin response to receiving the instruction to initiate the imaging portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

9. The method of claim 8, further comprising: setting, with the at least one processor, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determining, with the at least one processor, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enabling, with the at least one processor, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompting, with the at least one processor, the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure; in response to receiving the instruction to initiate the test portion of the patient procedure, controlling, with the at least one processor, the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicating, with the at least one processor, with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol;after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disabling, with the at least one processor, the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjusting, with the at least one processor, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicating, with the at least one processor with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and storing, with the at least one processor, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

10. The method of claim 9, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduled patient, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes:verifying, with the at least one processor, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.11 . The method of claim 10, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: verifying, with the at least one processor, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

12. The method of claim 11 , wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: receiving, with the at least one processor, from the fluid injection system, contrast data associated with a contrast loaded in the injector; and verifying, with the at least one processor, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

13. The method of claim 9, wherein determining, with the at least one processor, based on the procedure data, at least one of (i) whether the threshold forperforming the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, includes: providing, with the at least one processor, via the user device, at least one prompt to the user; and receiving, with the at least one processor, via the user device, at least one user input associated with at least one user confirmation of the at least one prompt.

14. The method of claim 9, further comprising: receiving, with the at least one processor, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and controlling, with the at least one processor, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.

15. A computer program product comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to: communicate, with a fluid injection system including a fluid injector, an imaging system including an imager, a sensor system including at least one sensor, and a user device, procedure data associated with a patient and a patient procedure associated with the patient, wherein the fluid injector is initially disabled from performing a fluid injection operation for the patient procedure, and wherein the imager is initially disabled from performing an imaging operation for the patient procedure; set, based on the procedure data, an imaging injection protocol associated with an imaging portion of the patient procedure and an imaging protocol associated with the imaging portion of the patient procedure;determine, based on the procedure data, whether a threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied; enable, based on the determination that the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the imaging portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the imaging portion of the patient procedure; in response to receiving the instruction to initiate the imaging portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the imaging injection protocol and the imager to perform the imaging operation according to the imaging protocol.

16. The system of claim 15, wherein the program instructions, when executed by at least one processor, further cause the at least one processor to: set, based on the procedure data, a test injection protocol associated with a test portion of the patient procedure and a test imaging protocol associated with the test portion of the patient procedure; determine, based on the procedure data, whether a threshold for performing a test portion of the patient procedure associated with the patient is satisfied; enable, based on a determination that the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation; in response to enabling the fluid injector to perform the fluid injection operation and the imager to perform the imaging operation, prompt the user to initiate the test portion of the patient procedure; receive, from the user device, a user input including an instruction to initiate the test portion of the patient procedure;in response to receiving the instruction to initiate the test portion of the patient procedure, control the fluid injector to perform the fluid injection operation according to the test injection protocol and the imager to perform the imaging operation according to the test imaging protocol; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive further procedure data associated with the fluid injection operation performed according to the test injection protocol and the imaging operation performed according to the test imaging protocol; after the fluid injector performs the fluid injection operation according to the test injection protocol and the imager performs the imaging operation according to the test imaging protocol, disable the fluid injector from performing the fluid injection operation for the patient procedure and the imager from performing the imaging operation; adjust, based on the procedure data and the further procedure data, the imaging injection protocol associated with the imaging portion of the patient procedure and the imaging protocol associated with the imaging portion of the patient procedure, wherein whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied is further determined based the still further procedure data; communicate with the fluid injection system including the fluid injector, the imaging system including the imager, the sensor system including the at least one sensor, and the user device to receive still further procedure data associated with the fluid injection operation performed according to the imaging injection protocol and the imaging operation performed according to the imaging protocol; and store, in a database, in association with a patient identifier associated with the patient, at least a portion of at least one of the procedure data, the further procedure data, the still further procedure data, or any combination thereof.

17. The system of claim 16, wherein the procedure data includes patient parameters associated with the patient and a procedure order associated with the patient procedure and including scheduled patient parameters associated with a scheduledpatient, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters associated with the patient and the scheduled patient parameters associated with the scheduled patient, that the patient corresponds to the scheduled patient.

18. The system of claim 17, wherein the procedure order further includes procedure parameters associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: verifying, based on the patient parameters, the procedure parameters, and at least one institutional rule, that the patient procedure associated with the patient corresponds to the at least one institutional rule.

19. The system of claim 18, wherein the procedure parameters include a scheduled contrast associated with the patient procedure, and wherein the program instructions, when executed by at least one processor, cause the at least one processor to determine, based on the procedure data, at least one of (i) whether the threshold for performing the test portion of the patient procedure associated with the patient is satisfied, (ii) whether the threshold for performing the imaging portion of the patient procedure associated with the patient is satisfied, or any combination thereof, by: receiving, from the fluid injection system, contrast data associated with a contrast loaded in the injector; andverifying, based on the contrast data associated with the contrast loaded in the injector and the procedure parameters including the scheduled contrast associated with the patient procedure, that the contrast loaded in the injector corresponds to the scheduled contrast associated with the patient procedure.

20. The system of claim 16, wherein the program instructions, when executed by at least one processor, further cause the at least one processor to: receive, from the sensor system including the at least one sensor, when the fluid injector is performing the fluid injection operation according to at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, sensor data associated with the patient; and control, based on the sensor data associated with the patient, when the fluid injector is performing the fluid injection operation according to the at least one of the test injection protocol, the imaging injection protocol, or any combination thereof, the fluid injector to adjust a flow rate of the fluid injection operation.