November 2011

Technological Systems in Medical Settings – Beta Testing and Demonstration

Dr. Sanjoy Sanyal

Associate Professor and Course Director of Neurosciences

MUA

Contents• Hitchhiker’s Guide to the Galaxy – Insanely great!

• Technological Systems in Medical Settings

• Systems Development Processes

• Systems Testing Processes

• Usability / Usefulness, Usability Testing Instruments

• InQsit Online Examination System: CSUQ, ETC, Beta testing, Score Grading, Preliminary results

• InQsit for Faculty

• Demonstration of 2 Clinical Systems (External)

• Conclusion – What was that again?

SMART: A project should be

• Simple

• Measurable

• Achievable

• Realistic

• Time-bound

Three projects are described

• Beta testing of an Online Examination system

• System for Automated staging of Breast cancer

• System for giving adjusted risk of CV event

Systems defined

Technological systems• Medical care settings:

Strategic (DSS, EIS); Tactical (MIS); Operational (PAS; Clinical EMR / EHR / EPR, CPOE, ETP, LIS, PACS)

Technological Systems• Telemedicine –

Telematics systems

• Subject / Task based systems (OT, Admission-Discharge systems); Simulation systems (Acute capability model, Pollution Asthma project, Renal services simulation)

• Medical education setting: Many of above; LMS (Moodle); Online lecture systems; Online Exam systems (Questionmark, InQsit)

Systems Development

Systems Develop

ment

• Multiple iterations till Alpha / Internal Acceptance Testing

Testing ProcessesAlpha (α) testing: Internal Acceptance Testing

• Simulated / actual operational testing by independent team at developers' site

• It is a form of Internal Acceptance testing, before it goes to Beta (β) testing

Beta (β) testing:

• Comes after Alpha (α) testing

• β versions released to limited audience outside programming team, or made available to open public to increase number of feedback

• Ensures product has few faults / ‘bugs’

Beta testing

Testing processes(External) Acceptance testing:

• Can be conducted by end-user, customer or client

• Whether or not to accept product

Regression testing:

• After modifying S/W, re-run previously passing tests

• Ensures modifications have not caused regression of previous functionality

– Sanity testing: Quickly checking for bizarre behaviour

– Smoke testing: Testing for basic functionality

INQSIT online exam system

Usability – Usefulness – Users –Qs• Usability: How easy is it for me to use the system?

• Usefulness: Does it make my work easier?

• Users: Consultative; Representative; Consensus

Usability Testing Instruments• QUIS (27): Questionnaire for User Interface Satisfaction –

Chin et al

• PUEU (12): Perceived Usefulness and Ease of Use – Davis

• NAU (5): Nielsen’s Attributes of Usability – Nielsen

• NHE (10): Nielsen’s Heuristic Evaluation – Nielsen

• CSUQ (19): Lewis

• ASQ (3): After-scenario Questionnaire – Lewis

• PHUE (13): Practical Heuristics for Usability Evaluation – Perlman

• PUTQ (100): Purdue Usability Testing Questionnaire – Lin et

CSUQ – Lewis

CSUQ – Lewis

Score gradingScore 19 - 56

Dis-satisfied

We are concerned that you are not entirely satisfied with the online examination system. We would like you tell us about it in more detail.

57 - 95

Neither +/-

It seems you are still double-minded about the new online exam system. Is there anything we can do to help you make up your mind?

96 - 133

Satisfied We are happy to note that you are satisfied with the new online exam system. We can assure you, your faith in the system is quite justified.

Beta test preliminary results

Beta Test Preliminary Results• Average

question-wise score = 5.33 / 7 (Mildly-Moderately agree)

• Average total score = 101.2 / 133 (Satisfied)

Beta Test Preliminary Results

• Qs 9: The system gives error messages that clearly tells me how to fix problems (This was an ambiguous question)

INQSIT for faculty

INQSIT for faculty

Conclusion – What was that, again?