IP Library Granted Patent US 12,451,247
Granted Patent B2
US 12,451,247 · App. 16/764,092 · Granted Oct 21, 2025

User interface for managing a multiple diagnostic engine environment

Inventors: Karen Lim (Brighton, MA); Prabhu Ramachandran (Newton, MA)
Assignee: Siemens Healthcare Diagnostics Inc.
G16H50/20G16H10/60G16H40/20G16H50/30G16H50/70
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,451,247
App. No.
16/764,092
Granted
Oct 21, 2025
Kind
B2
Abstract

A point of care system may comprise a plurality of diagnostic engines and an IDM in electronic communication with each of the plurality of diagnostic engines. Each of the plurality of diagnostic engines may perform testing on a sample inserted into the diagnostic engine. The IDM may be configured to communicate with each of the plurality of diagnostic engines to enable a plurality of tests to be performed on multiple different samples substantially simultaneously by a plurality of users using the plurality of diagnostic engines and to present a single user interface for managing testing by the plurality of diagnostic engines and for receiving the results of tests performed by each of the plurality of diagnostic engines.

Claims (69)

1. A method performed by an instrument data manager (IDM) in electronic communication with a first diagnostic engine and a second diagnostic engine, the first diagnostic engine and the second diagnostic engine each including a processor configured to adjust one or more characteristics of the first diagnostic engine and the second diagnostic engine to keep the first diagnostic engine and the second diagnostic engine within operating conditions to obtain measured results of corresponding tests, and a memory that stores one or more values representing the measured result of the corresponding tests, the first diagnostic engine and the second diagnostic engine having no user interface display, the method comprising:

receiving, via a single user interface displayed on a display screen and from a first user, a first request to perform a first test on a first fluid sample associated with the first diagnostic engine;

sending, to the first diagnostic engine and in response to the first request, a first instruction to perform the first test on the first fluid sample associated with the first diagnostic engine;

receiving, via the single user interface displayed on the display screen and from a second user, a second request to perform a second test on a second sample associated with the second diagnostic engine;

sending, to the second diagnostic engine and in response to the second request, a second instruction to perform the second test associated with the second diagnostic engine;

receiving from the first diagnostic engine, one or more first measured result of the first test, wherein the first diagnostic engine, without control from the IDM, carries out the first test to obtain the one or more first measured result of the first test, by:

mixing the first fluid sample a first time;

heating, using a heating element, the first fluid sample;

mixing the first fluid sample a second time, subsequent to heating the first fluid sample; and

taking, using an optical scanner, an optical reading of the first fluid sample;

receiving from the second diagnostic engine, one or more second measured result of the second test, wherein the second diagnostic engine, without control from the IDM, carries out the second test to obtain the one or more second measured result; and

processing one or more of the one or more first measured result and the one or more second measured result to determine a calculated result;

presenting, on the single user interface for managing testing of the first diagnostic engine and the second diagnostic engine, the calculated result,

wherein the IDM does not control: the first diagnostic engine to obtain measured results of the first test subsequent to sending the first instruction in response to the first request; or the second diagnostic engine to obtain measured results of the second test subsequent to sending the second instruction in response to the second request; and

wherein the first test and the second test are performed simultaneously.

2. The method of claim 1 , further comprising:

prompting, via the single user interface, the first user to enter information corresponding to the first fluid sample associated with the first diagnostic engine; and

prompting, via the single user interface, the second user to enter information corresponding to the second sample associated with the second diagnostic engine,

wherein the information includes one or more of a patient identifier, a patient demographic, a sample demographic, and order information.

3. The method of claim 2 , wherein prompting at least one of the first user to enter information corresponding to the first fluid sample associated with the first diagnostic engine and the second user to enter information corresponding to the second sample associated with the second diagnostic engine is displayed after the corresponding test has been initiated.

4. The method of claim 1 , further comprising:

displaying, via the single user interface and after initiating the first test associated with the first diagnostic engine, a first icon representing the first diagnostic engine; and

displaying, via the single user interface and after initiating the second test associated with the second diagnostic engine, a second icon representing the second diagnostic engine.

5. The method of claim 1 , wherein the second diagnostic engine comprises at least one of a blood gas diagnostic engine, a cardiac diagnostic engine, a coagulation diagnostic engine, a diabetes diagnostic engine, and a urinalysis diagnostic engine.

6. The method of claim 5 , wherein the first diagnostic engine and the second diagnostic engine are different types of diagnostic engines.

7. The method of claim 1 , wherein the first user is a different user than the second user.

8. The method of claim 1 , wherein the IDM receives measured results from the first diagnostic engine in non-real time.

9. The method of claim 8 , wherein processing one or more of the one or more first measured result and the one or more second measured result to determine the calculated result includes generating the calculated result based on the measured result and at least one other parameter,

wherein the at least one other parameter comprises demographic information associated with a patient and a time of day at which the measured result was determined.

10. The method of claim 1 , further comprising:

receiving from the first diagnostic engine a first status of the first test and from the second diagnostic engine a second status of the second test, each of the first status and the second status being one or more of: a percentage complete, a time remaining, and a time elapsed; and

presenting on the single user interface for managing testing of the first diagnostic engine and the second diagnostic engine, the first status of the first diagnostic engine the second status of the second diagnostic engine.

11. An instrument data manager (IDM) in electronic communication with a first diagnostic engine and a second diagnostic engine, the first diagnostic engine and the second diagnostic engine each including a processor configured to adjust one or more characteristics of the first diagnostic engine and the second diagnostic engine to keep the first diagnostic engine and the second diagnostic engine within operating conditions to obtain measured results of corresponding tests, and a memory that stores one or more values representing the measured result of the corresponding tests, the first diagnostic engine and the second diagnostic engine having no user interface display, wherein the IDM comprises a processor and a memory, the memory storing computer executable instructions which, when executed by the processor, cause the IDM to perform operations comprising:

receiving, via a single user interface displayed on a display screen and from a first user, a first request to perform a first test on a first fluid sample associated with the first diagnostic engine;

sending, to the first diagnostic engine and in response to the first request, a first instruction to perform the first test on the first fluid sample associated with the first diagnostic engine;

receiving, via the single user interface displayed on the display screen and from a second user, a second request to perform a second test on a second sample associated with the second diagnostic engine; and

sending, to the second diagnostic engine and in response to the second request, a second instruction to perform the second test associated with the second diagnostic engine,

receiving, from the first diagnostic engine, one or more first measured result of the first test, wherein the first diagnostic engine, without control from the IDM, carries out the first test to obtain the one or more first measured result of the first test by:

mixing the first fluid sample a first time;

heating, using a heating element, the first fluid sample;

mixing the first fluid sample a second time, subsequent to heating the first fluid sample; and

taking, using an optical scanner, an optical reading of the first fluid sample;

receiving from the second diagnostic engine, one or more second measured result of the second test, wherein the second diagnostic engine, without control from the IDM, carries out the second test to obtain the one or more second measured result; and

processing one or more of the one or more first measured result and the one or more second measured result to determine a calculated result;

wherein the first test associated with the first diagnostic engine and the second test associated with the second diagnostic engine are performed simultaneously; and

wherein the IDM does not control: the first diagnostic engine to obtain measured results of the first test subsequent to sending the first instruction in response to the first request; or the second diagnostic engine to obtain measured results of the second test subsequent to sending the second instruction in response to the second request.

12. The IDM of claim 11 , wherein the instructions, when executed, further cause the IDM to perform operations comprising:

prompting, via the single user interface, the first user to enter information corresponding to the first fluid sample associated with the first diagnostic engine; and

prompting, via the single user interface, the second user to enter information corresponding to the second sample associated with the second diagnostic engine,

wherein the information includes one or more of a patient identifier, a patient demographic, a sample demographic, and order information.

13. The IDM of claim 12 , wherein prompting at least one of the first user to enter information corresponding to the first fluid sample associated with the first diagnostic engine and the second user to enter information corresponding to the second sample associated with the second diagnostic engine is displayed after the corresponding test has been initiated.

14. The IDM of claim 11 , wherein the instructions, when executed, further cause the IDM to perform operations comprising:

displaying, via the single user interface and after initiating the first test associated with the first diagnostic engine, a first icon representing the first diagnostic engine; and

displaying, via the single user interface and after initiating the second test associated with the second diagnostic engine, a second icon representing the second diagnostic engine.

15. The IDM of claim 11 , wherein the second diagnostic engine comprises at least one of a blood gas diagnostic engine, a cardiac diagnostic engine, a coagulation diagnostic engine, a diabetes diagnostic engine, and a urinalysis diagnostic engine.

16. The IDM of claim 15 , wherein the first diagnostic engine and the second diagnostic engine are different types of diagnostic engines.

17. The IDM of claim 11 , wherein the first user is a different user than the second user.

18. The IDM of claim 11 , wherein the IDM receives measured results from the first diagnostic engine in non-real time.

19. The IDM of claim 18 , wherein processing one or more of the one or more first measured result and the one or more second measured result to determine the calculated result includes generating the a calculated result based on the measured result and at least one other parameter,

wherein the at least one other parameter comprises demographic information associated with a patient or a time of day at which the measured result was determined.

20. An instrument data manager (IDM) in electronic communication with a first diagnostic engine and a second diagnostic engine, the first diagnostic engine and the second diagnostic engine each including a processor configured to adjust one or more characteristics of the first diagnostic engine and the second diagnostic engine to keep the first diagnostic engine and the second diagnostic engine within operating conditions to obtain measured results of corresponding tests, and a memory that stores one or more values representing the measured result of the corresponding tests, the first diagnostic engine and the second diagnostic engine having no user interface display, wherein the IDM comprises a processor and a memory, the memory storing computer executable instructions which, when executed by the processor, cause the IDM to perform operations comprising:

receiving, via a single user interface displayed on a display screen and from a first user, a first request to perform a first test on a first sample associated with the first diagnostic engine;

sending, to the first diagnostic engine and in response to the first request, a first instruction to perform the first test on the first sample associated with the first diagnostic engine, wherein the first diagnostic engine comprises a device responsive to chemical characteristics, the device comprising one or more of a chemical surface, an integrated circuit structure, a micro-electromechanical structure, and an optical sensor;

receiving, via the single user interface displayed on the display screen and from a second user, a second request to perform a second test on a second sample associated with the second diagnostic engine; and

sending, to the second diagnostic engine and in response to the second request, a second instruction to perform the second test associated with the second diagnostic engine;

receiving, from the first diagnostic engine, one or more first measured result of the first test, wherein, without control from the IDM, the first diagnostic engine carries out the first test to obtain the one or more first measured result of the first test by recognizing an analyte of interest in the first sample by using one or more of membrane entrapment, physical adsorption, matrix entrapment, reaction chamber, and covalent bonding to produce one or more of a charge and an optical change at one or more of a sensor-transducer interface and an electrode;

receiving from the second diagnostic engine, one or more second measured result of the second test, wherein the second diagnostic engine carries out the second test without control from the IDM to obtain the one or more second measured result; and

processing one or more of the one or more first measured result and the one or more second measured result to determine a calculated result; and

wherein the IDM does not control: the first diagnostic engine to obtain measured results of the first test subsequent to sending the first instruction in response to the first request, or the second diagnostic engine to obtain measured results of the second test subsequent to sending the second instruction in response to the second request.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2020
From: LIM, KAREN; RAMACHANDRAN, PRABHU
To: SIEMENS HEALTHCARE DIAGNOSTICS INC.
Reel/Frame 052661/0680 →
Continuity (2)
Provisional Application 62588697 · Nov 20, 2017
Related Publication 20200286621A1 · Sep 10, 2020
References Cited (93)
US 5807256A · Taguchi et al. · 1998 [cited by applicant]
US 5812419A · Chupp et al. · 1998 [cited by applicant]
US 6055487A · Margery · 2000 [cited by examiner]
US 6581012B1 · Aryev · 2003 [cited by examiner]
US 7509232B2 · Seher et al. · 2009 [cited by applicant]
US 8041463B2 · Pollack et al. · 2011 [cited by applicant]
US 8894946B2 · Nielsen et al. · 2014 [cited by applicant]
US 9259734B2 · Williams et al. · 2016 [cited by applicant]
US 9285366B2 · Burd et al. · 2016 [cited by applicant]
US 9417210B2 · Arlen et al. · 2016 [cited by applicant]
US 9418493B1 · Dong · 2016 [cited by applicant]
US 9458488B2 · Johnson et al. · 2016 [cited by applicant]
US 10607724B2 · Miyauchi · 2020 [cited by examiner]
US 20060259265A1 · Mishima · 2006 [cited by examiner]
US 20070038406A1 · Uemura · 2007 [cited by examiner]
US 20070124099A1 · Onomichi · 2007 [cited by examiner]
US 20070254277A1 · Scrabeck et al. · 2007 [cited by applicant]
US 20080103814A1 · Fabius et al. · 2008 [cited by applicant]
US 20080250477A1 · Samuelsson et al. · 2008 [cited by applicant]
US 20080312893A1 · Denton · 2008 [cited by applicant]
US 20090163832A1 · Sunderani · 2009 [cited by applicant]
US 20100212675A1 · Walling et al. · 2010 [cited by applicant]
US 20100292618A1 · Okuya et al. · 2010 [cited by applicant]
US 20110020785A1 · Lowery, Jr. et al. · 2011 [cited by applicant]
US 20110245061A1 · Haechler · 2011 [cited by applicant]
US 20110245089A1 · Scott et al. · 2011 [cited by applicant]
US 20120029303A1 · Shaya · 2012 [cited by applicant]
US 20120042214A1 · Jacobs et al. · 2012 [cited by applicant]
US 20120046203A1 · Walsh et al. · 2012 [cited by applicant]
US 20130260414A1 · Yao · 2013 [cited by examiner]
US 20140058755A1 · Macoviak et al. · 2014 [cited by applicant]
US 20140075032A1 · Vasudevan et al. · 2014 [cited by applicant]
US 20140100811A1 · Fuchs et al. · 2014 [cited by applicant]
US 20140194305A1 · Kayyem et al. · 2014 [cited by applicant]
US 20140251836A1 · Feeney · 2014 [cited by applicant]
US 20140316813A1 · Bauer · 2014 [cited by applicant]
US 20150127270A1 · Goemann-Thoss · 2015 [cited by examiner]
US 20150212104A1 · Furrer et al. · 2015 [cited by applicant]
US 20150268186A1 · Pagels · 2015 [cited by applicant]
US 20150338427A1 · Pollack · 2015 [cited by examiner]
US 20160020986A1 · Bosko et al. · 2016 [cited by applicant]
US 20160025639A1 · Jakubowicz · 2016 [cited by applicant]
US 20160054307A1 · Pinkowitz et al. · 2016 [cited by applicant]
US 20160314254A1 · Nakamura et al. · 2016 [cited by applicant]
US 20160321421A1 · Delgrande et al. · 2016 [cited by applicant]
US 20170049964A1 · Varsavsky · 2017 [cited by examiner]
US 20170067922A1 · Antoni · 2017 [cited by examiner]
US 20170076054A1 · Tindel et al. · 2017 [cited by applicant]
US 20170177724A1 · Booker et al. · 2017 [cited by applicant]
US 20180046871A1 · Ionita · 2018 [cited by examiner]
CN 101444419A · 2009 [cited by applicant]
CN 101556629A · 2009 [cited by applicant]
CN 102264294A · 2011 [cited by applicant]
CN 102651995A · 2012 [cited by applicant]
CN 105122254A · 2015 [cited by applicant]
CN 106126958A · 2016 [cited by applicant]
CN 106548039A · 2017 [cited by applicant]
DE 202009018545U1 · 2012 [cited by applicant]
DK 0483595T3 · 2002 [cited by applicant]
JP 2002329004A · 2002 [cited by applicant]
JP 2003202346A · 2003 [cited by applicant]
JP 2004201886A · 2004 [cited by applicant]
JP 2009104674A · 2009 [cited by applicant]
JP 2010263953A · 2010 [cited by applicant]
JP 2011096235A · 2011 [cited by applicant]
JP 2011186862A · 2011 [cited by applicant]
JP 2012052850A · 2012 [cited by applicant]
JP 2013077335A · 2013 [cited by applicant]
JP 2013541079A · 2013 [cited by applicant]
JP 2015170187A · 2015 [cited by applicant]
JP 2015201003A · 2015 [cited by applicant]
JP 2016109697A · 2016 [cited by applicant]
JP 2017018573A · 2017 [cited by applicant]
WO 03048998A2 · 2003 [cited by applicant]
WO 2008097793A1 · 2008 [cited by applicant]
WO 2011072860A1 · 2011 [cited by applicant]
WO 2015143309A1 · 2015 [cited by applicant]
WO 2015187480A1 · 2015 [cited by applicant]
WO 2016127089A1 · 2016 [cited by applicant]
WO 2016188738A1 · 2016 [cited by applicant]
WO 2017190029A1 · 2017 [cited by applicant]
International Search Report and Written Opinion of International Application No. PCT/US2018/061551 dated Jan. 16, 2019. [cited by applicant]
European Search Report and Search Opinion of European Application No. 18879008.3 dated Dec. 21, 2020. [cited by applicant]
Radiometer ABL80 Flex Brochure, 2009, pp. 1-10. [cited by applicant]
Apple et al., “Clinical Evaluation of the First Medical Whole Blood, Point-of-Care Testing Device for Detection of Myocardial Infarction”, 2000, Clinical Chemistry 46, No. 10, pp. 1604-1609. [cited by applicant]
Abbot Point of Care “i-STAT® 1 System Manual”, Mar. 7, 2013, pp. 1-606. [cited by applicant]
Abbott “i-STAT® Cartridge Menu Brochure”, Oct. 2016, p. 1. [cited by applicant]
“i-STAT Handheld”, 045714, Rev B, Dec. 2016, pp. 1-10. [cited by applicant]
“Samsung Labgeo PT10,” Samsung, 2015, pp. 1-4. [cited by applicant]
You et al., “Point-of-Care Test Equipment for Flexible Laboratory Automation”, 2014, SAGE Journal of Laboratory Automation, vol. 19(4), pp. 403-412. [cited by applicant]
Bao Chen et al:“HLSVD versus AMARES for magnetic resonance spectroscopy data quantification”, Journal of Clinical Rehabilitative Tissue Engineering Research Jan. 22, 2011 vol. 15, No. 4, ISSN 1673-8225, pp. 683-686, Jan… [cited by applicant]
Chu Yang et al:“Detection of helium leakage from Siemens Impact 1. 0T superconducting MR”, Nov. 10, 1996. [cited by applicant]
Ewels et al; “MultiQC: summarize analysis results for multiple tools and samples in a single report” Oct. 2016, Bioinformatics, vol. 32, Issue 19, pp. 3047-3048. [cited by applicant]