80 likes | 227 Views
Remote Connectivity. GLI meeting, 17 April 2013. The issue. Deployment of GeneXpert systems Are they installed, are they being used? Was the user training efficient? Are the logistics working? Where are issues to be addressed? How do we measure the effectiveness of the program?.
E N D
Remote Connectivity GLI meeting, 17 April 2013
The issue • Deployment of GeneXpert systems • Are they installed, are they being used? • Was the user training efficient? • Are the logistics working? • Where are issues to be addressed? • How do we measure the effectiveness of the program?
2012 Pilot study Objectives • Monitor deployed systems • MTB testing activity • Performance • Systems • Users • Modules • Disease • User evaluation of the prototype • Improvements during Pilot with user input (NHLS, others)
Data collection • Pilot • Lab ID • Date, duration • Test type • Lot & serial numbers • Test Result • User name • Main error • Adding to 2013 product • Analytes (CT, EP, …) • Pressure & T°sensors • Full error logs • System status • Module status Full Test Result Analytes System Test Result Error logs Modules
2013 planned remote monitoring product • Monitoring and trending • Usage*, diseases*, systems, modules, user training, … • Central data control by customer • Define which data is collected* or shared with users* and others • Local admin user can approve data collection if desired • Full data capability • Historical* andreal-time* • Technical status • Share with external applications • API for external apps to collect data • When given rights by the customer • Cepheid Support (*) as in pilot Tech Support Control data collection & user access Remote monitoring Monitor systems & users Trend disease Report, Extract API Reporter application Run tests
Status • Design phase • Interested in wish-list for API from external developers • V.1 planned end 2013 • Remote monitoring as described here • V.2 in 2014 • Extended capabilities • Customer network server (enables patient data)
Remote Connectivity Thank you