IP Library › Granted Patent US 12,433,990
Granted Patent B2
US 12,433,990 · App. 18/030,138 · Granted Oct 7, 2025

System, method, and computer program product for providing access to fluid injection systems

Inventors: Frank DeSensi (Allison Park, PA); Barry Skirble (Allison Park, PA); Anthony Scolieri (Glenshaw, PA); Karthikeyan Ranganathan (Gibsonia, PA)
Assignee: BAYER HEALTHCARE LLC
A61M5/007G06F21/35G16H20/17G16H40/67A61B5/1171A61M2205/502A61M2205/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,433,990
App. No.
18/030,138
Granted
Oct 7, 2025
Kind
B2
Abstract

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

Claims (82)

1. A system for accessing a fluid injection system comprising:

at least one processor programmed or configured to:

authenticate a user for access to a fluid injection system, wherein the fluid injection system is configured to administer contrast fluid including a contrast agent to a patient, wherein, when authenticating the user for access to the fluid injection system, the at least one processor is programmed or configured to:

provide a graphical user interface (GUI) on a display screen that displays an image to scan by a user device associated with the user,

receive a login credential associated with the image via a software application for accessing the fluid injection system, the software application being on the user device associated with the user, and

authenticate the user for access to the fluid injection system based on receiving the login credential via the software application;

provide data identifying one or more features of the software application for accessing the fluid injection system based on an input received via the software application, wherein the one or more features of the software application comprises:

one or more features associated with providing data associated with the fluid injection system, wherein the one or more features associated with providing data associated with the fluid injection system comprises:

a feature associated with obtaining data associated with an error code of the fluid injection system,

a feature associated with generating a service history of the fluid injection system,

a feature associated with providing the service history of the fluid injection system,

a feature associated with generating a service request for the fluid injection system,

a feature associated with providing instructions for operation of the fluid injection system,

a feature associated with providing data associated with a service procedure to be performed on the fluid injection system,

a feature associated with providing data associated with a service procedure that was performed on the fluid injection system, or

any combination thereof;

receive data identifying a selected feature of the software application for accessing the fluid injection system;

determine whether the user is authorized to access the selected feature of the software application based on authenticating the user for access to the fluid injection system, wherein, when determining whether the user is authorized to access selected feature of the software application, the at least one processor is programmed or configured to:

determine whether the user has a level of access that authorizes the user to access the selected feature of the software application, wherein the level of access is based on a user profile of the user; and

provide access to the selected feature of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected feature of the software application.

2. The system of claim 1 , wherein the at least one processor is further programmed or configured to:

display the data associated with the selected feature of the software application for accessing the fluid injection system via a graphical user interface (GUI) of the software application on the user device.

3. The system of claim 1 , wherein the fluid injection system comprises a display screen, and wherein the at least one processor is further programmed or configured to:

cause data associated with the fluid injection system to be displayed on the display screen of the fluid injection system.

4. The system of claim 1 , wherein the at least one processor is further programmed or configured to:

access the selected feature of the software application of the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system comprises data associated with one or more operations of the fluid injection system; and

wherein the at least one processor is further programmed or configured to:

log the data associated with one or more operations of the fluid injection system.

5. A computer program product for accessing a fluid injection system, the computer program product comprising at least one non-transitory computer-readable medium including one or more instructions that, when executed by at least one processor, cause the at least one processor to:

authenticate a user for access to a fluid injection system, wherein the fluid injection system is configured to administer contrast fluid including a contrast agent to a patient, wherein, the one or more instructions that cause the at least one processor to authenticate the user for access to the fluid injection system, cause the at least one processor to:

provide a graphical user interface (GUI) on a display screen associated with the fluid injection system that displays an image to scan by a user device,

receive a login credential associated with the image via a software application for accessing the fluid injection system, and

authenticate the user for access to the fluid injection system based on receiving the login credential via the software application;

provide data identifying one or more features of the software application for accessing the fluid injection system based on an input received via the software application, wherein the one or more features of the software application comprises:

one or more features associated with providing data associated with the fluid injection system, wherein the one or more features associated with providing data associated with the fluid injection system comprises:

 a feature associated with obtaining data associated with an error code of the fluid injection system,

 a feature associated with generating a service history of the fluid injection system,

 a feature associated with providing the service history of the fluid injection system,

 a feature associated with generating a service request for the fluid injection system,

 a feature associated with providing instructions for operation of the fluid injection system,

 a feature associated with providing data associated with a service procedure to be performed on the fluid injection system,

 a feature associated with providing data associated with a service procedure that was performed on the fluid injection system, or

 any combination thereof;

receive data identifying a selected feature of the software application of the fluid injection system;

determine whether the user is authorized to access the selected feature of the software application based on authenticating the user for access to the fluid injection system, wherein, the one or more instructions that cause the at least one processor to determine whether the user is authorized to access selected feature of the software application, cause the at least one processor to:

determine whether the user has a level of access that authorizes the user to access the selected feature of the software application, wherein the level of access is based on a user profile of the user; and

provide access to the selected feature of the software application of the fluid injection system based on determining that the user is authorized to access the selected feature of the software application.

6. The computer program product of claim 5 , wherein the one or more instructions further cause the at least one processor to:

display data associated with the selected feature of the software application of the fluid injection system via a graphical user interface (GUI) of the software application on the user device.

7. The computer program product of claim 5 , wherein the fluid injection system comprises a display screen, and wherein the one or more instructions further cause the at least one processor to:

cause data associated with the fluid injection system to be displayed on the display screen of the fluid injection system.

8. The computer program product of claim 5 , wherein the one or more instructions further cause the at least one processor to:

access the selected feature of the software application for accessing the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system comprises data associated with one or more operations of the fluid injection system; and

wherein the one or more instructions further cause the at least one processor to:

log the data associated with the one or more operations of the fluid injection system.

9. A method for accessing a fluid injection system comprising:

authenticating, with at least one processor, a user for access to a fluid injection system, wherein the fluid injection system is configured to administer contrast fluid including a contrast agent to a patient, wherein, when authenticating the user for access to the fluid injection system, the at least one processor is programmed or configured to;

providing a graphical user interface (GUI) on a display screen associated with the fluid injection system that displays an image to scan by a user device associated with the user,

receiving a login credential associated with the image via a software application for accessing the fluid injection system, the software application being on the user device associated with the user, and

authenticating the user for access to fluid injection system based on receiving the login credential via the software application;

providing, with the at least one processor, data identifying one or more features of the software application for accessing the fluid injection system based on an input received via the software application, wherein the one or more features of the software application comprises:

one or more features associated with providing data associated with the fluid injection system, wherein the one or more features associated with providing data associated with the fluid injection system comprises:

a feature associated with obtaining data associated with an error code of the fluid injection system,

a feature associated with generating a service history of the fluid injection system,

a feature associated with providing the service history of the fluid injection system,

a feature associated with generating the service request for the fluid injection system,

a feature associated with providing instructions for operation of the fluid injection system,

a feature associated with providing data associated with a service procedure to be performed on the fluid injection system,

a feature associated with providing data associated with a service procedure that was performed on the fluid injection system, or

any combination thereof;

receiving, with the at least one processor, data identifying a selected feature of the software application for accessing the fluid injection system;

determining, with the at least one processor, whether the user is authorized to access the selected feature of the software application based on authenticating the user for access to the fluid injection system, wherein determining whether the user is authorized to access selected feature of the software application comprises:

determining whether the user has a level of access that authorizes the user to access the selected feature of the software application, wherein the level of access is based on a user profile of the user; and

providing, with the at least one processor, access to the selected feature of the software application for accessing the fluid injection system based on determining that the user is authorized to access the selected feature of the software application.

10. The method of claim 9 , further comprising:

displaying data associated with the selected feature of the software application of the fluid injection system via a graphical user interface (GUI) of the software application on the user device.

11. The method of claim 9 , wherein the fluid injection system comprises the display screen, and wherein the method further comprises:

causing data associated with the fluid injection system to be displayed on the display screen of the fluid injection system.

12. The method of claim 9 , further comprising:

accessing the selected feature of the software application for accessing the fluid injection system to provide data associated with the fluid injection system, wherein the data associated with the fluid injection system comprises data associated with one or more operations of the fluid injection system; and

wherein the method further comprises:

logging the data associated with the one or more operations of the fluid injection system.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2023
From: DESENSI, FRANK; SKIRBLE, BARRY; SCOLIERI, ANTHONY; RANGANATHAN, KARTHIKEYAN
To: BAYER HEALTHCARE LLC
Reel/Frame 064888/0175 →
Continuity (2)
Provisional Application 63088343 · Oct 6, 2020
Related Publication 20230364325A1 · Nov 16, 2023
References Cited (74)
US 3977391A · Fleischmann · 1976 [cited by applicant]
US 6317623B1 · Griffiths et al. · 2001 [cited by applicant]
US 6643537B1 · Zatezalo et al. · 2003 [cited by applicant]
US 7094216B2 · Trombley, III et al. · 2006 [cited by applicant]
US 7457804B2 · Uber, III et al. · 2008 [cited by applicant]
US 7549977B2 · Schriver et al. · 2009 [cited by applicant]
US 7553294B2 · Lazzaro et al. · 2009 [cited by applicant]
US 7556619B2 · Spohn et al. · 2009 [cited by applicant]
US 7563249B2 · Schriver et al. · 2009 [cited by applicant]
US 7766873B2 · Moberg et al. · 2010 [cited by applicant]
US 7775966B2 · Dlugos et al. · 2010 [cited by applicant]
US 7996381B2 · Uber, III et al. · 2011 [cited by applicant]
US 8095241B2 · Palmerton et al. · 2012 [cited by applicant]
US 8147464B2 · Spohn et al. · 2012 [cited by applicant]
US 8337456B2 · Schriver et al. · 2012 [cited by applicant]
US 8521716B2 · Uber, III et al. · 2013 [cited by applicant]
US 8540698B2 · Spohn et al. · 2013 [cited by applicant]
US 8945051B2 · Schriver et al. · 2015 [cited by applicant]
US 9173995B1 · Tucker et al. · 2015 [cited by applicant]
US 9463335B2 · Griffith et al. · 2016 [cited by applicant]
US 10124110B2 · Dedig et al. · 2018 [cited by applicant]
US 10507319B2 · Haury et al. · 2019 [cited by applicant]
US 10549084B2 · Sokolov et al. · 2020 [cited by applicant]
US 10583256B2 · Berry et al. · 2020 [cited by applicant]
US 20020070157A1 · Yamada · 2002 [cited by applicant]
US 20030216692A1 · Fago et al. · 2003 [cited by applicant]
US 20040138920A1 · Sawanaga et al. · 2004 [cited by applicant]
US 20090070342A1 · Uber, III et al. · 2009 [cited by applicant]
US 20100189227A1 · Mannar et al. · 2010 [cited by applicant]
US 20100305506A1 · Fahrer · 2010 [cited by applicant]
US 20120110651A1 · Van Biljon et al. · 2012 [cited by applicant]
US 20120209569A1 · Becourt et al. · 2012 [cited by applicant]
US 20140249500A1 · Estes · 2014 [cited by applicant]
US 20140266713A1 · Sehgal et al. · 2014 [cited by applicant]
US 20150201912A1 · Mercer et al. · 2015 [cited by applicant]
US 20150230760A1 · Schneider · 2015 [cited by applicant]
US 20150374901A1 · Kohler · 2015 [cited by examiner]
US 20160034722A1 · Joseph et al. · 2016 [cited by applicant]
US 20160213853A1 · Despa et al. · 2016 [cited by applicant]
US 20170182258A1 · Michael · 2017 [cited by applicant]
US 20180161496A1 · Berry et al. · 2018 [cited by applicant]
US 20180240548A1 · Spohn et al. · 2018 [cited by applicant]
US 20180286510A1 · Kwan et al. · 2018 [cited by applicant]
US 20190050375A1 · Fitzgibbon et al. · 2019 [cited by applicant]
US 20200310900A1 · Hipp et al. · 2020 [cited by applicant]
US 20210272687A1 · Klopfenstein et al. · 2021 [cited by applicant]
US 20220148718A1 · Schriver et al. · 2022 [cited by applicant]
CN 114360703A · 2022 [cited by applicant]
EP 1563859A1 · 2005 [cited by applicant]
JP 2010509984A · 2010 [cited by applicant]
JP 2011516196A · 2011 [cited by applicant]
WO 2008063429A2 · 2008 [cited by applicant]
WO 2009125398A2 · 2009 [cited by applicant]
WO 2013075127A1 · 2013 [cited by applicant]
WO 2015106107A1 · 2015 [cited by applicant]
WO 2016112163A1 · 2016 [cited by applicant]
WO 2017005861A1 · 2017 [cited by applicant]
WO 2017027724A1 · 2017 [cited by applicant]
WO 2017040152A1 · 2017 [cited by applicant]
WO 2018075386A1 · 2018 [cited by applicant]
WO 2018144369A1 · 2018 [cited by applicant]
WO 2019032784A1 · 2019 [cited by applicant]
WO 2019035986A1 · 2019 [cited by applicant]
WO 2019046261A1 · 2019 [cited by applicant]
WO 2019046282A1 · 2019 [cited by applicant]
WO 2021102070A1 · 2021 [cited by applicant]
WO 2021222771A1 · 2021 [cited by applicant]
WO 2021236472A1 · 2021 [cited by applicant]
WO 2022015560A1 · 2022 [cited by applicant]
Charles M. Able et al., A model for preemptive maintenance of medical linear accelerators-predictive maintenance, Radiation Oncology, 2016, vol. 11/ No. 36. [cited by applicant]
From Conventional Injector to Smart Injector Brochure for EmpowerCTA Injector System, 2017. [cited by applicant]
International Preliminary Report on Patentability from PCT Application No. PCT/US2021/053359, mailed Apr. 20, 2023. [cited by applicant]
Mana Sezdi., Two Different Maintenance Strategies in the Hospital Environment: Preventive Maintenance for Older Technology Devices and Predictive Maintenance for Newer High-Tech Devices, Journal of Healthcare Engineerin… [cited by applicant]
Patil Ravindra, et al.,, Predictive Modeling for Corrective Maintenance of Imaging devices from Machine Logs, IEEE, 2017, 1676-1679. [cited by applicant]