Remote ConnectivityRemote ConnectivityGLI meeting, 17 April 2013GLI meeting, 17 April 2013

© Cepheid2

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?

© Cepheid3

2012 Pilot study

Objectives•Monitor deployed systems

– MTB testing activity– Performance

o Systemso Userso Modules

– Disease

•User evaluation of the prototype

•Improvements during Pilot with user input (NHLS, others)

© Cepheid4

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

FullTest

Result

TestResult Analytes

Error logs

System

Modules

© Cepheid5

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* and real-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

RemotemonitoringMonitor systems

& usersTrend disease

Report, Extract

Control data collection & user access

Run tests

Reporterapplication

API

TechSupport

© Cepheid6

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 ConnectivityRemote ConnectivityThank youThank you