System Usability Scale for Health Applications
System Usability Scale for Health Applications (SUS-Health) · Also known as: SUS-Health, System Usability Scale, SUS
The System Usability Scale (SUS) is a rapid, validated tool for measuring perceived usability of digital products, widely adapted for health applications. Developed by John Brooke in 1996 and extensively validated by Bangor and colleagues, the 10-item SUS generates a single composite score reflecting users' subjective perception of ease of use, learnability, and overall system quality. Its simplicity and robustness have made it the de facto standard for usability assessment in health technology research.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use SUS during iterative app development: test prototype, measure SUS, identify problems, redesign, retest. Essential before releasing apps to health system partners or clinical trials. Use SUS for comparative evaluation—test competing apps or competing design variants (A/B testing) to select the more usable option. Include SUS in clinical trials evaluating digital interventions to document that usability was not a confounder of null results. Use in health system procurement to ensure selected apps meet usability standards.
Strengths & limitations
- Brevity and speed: 10 items administered in 2–3 minutes; enables rapid testing in busy clinical settings and iterative development cycles.
- Robustness and universal validation: Extensively validated across 500+ diverse products (healthcare, finance, transportation, entertainment); strong psychometric properties; single reliable score captures overall usability perception.
- Actionable insights: Despite simplicity, open-ended follow-up questions reveal specific pain points; designers can correlate low item scores with specific interface problems.
- Reference database: Abundant published SUS data enables benchmarking of health apps against other healthcare technologies and consumer apps.
- Subjective perception, not objective performance: SUS measures perceived usability, not actual task completion rates or error frequencies. Users may report high usability while making errors, or low usability despite efficient task completion.
- Limited diagnostic detail: SUS provides an overall score but not granular information about which interface elements cause friction; qualitative follow-up or usability testing (think-aloud, eye-tracking) needed to pinpoint problems.
- Leniency bias: Participants often rate systems more positively than objective performance warrants, particularly if they feel grateful for access or perceive researchers as invested in the app.
- Limited sensitivity to domain-specific usability: SUS does not capture healthcare-specific usability considerations (clinical decision support integration, EHR workflow fit, patient safety implications).
Frequently asked
What SUS score indicates an app is ready for clinical use?
SUS ≥70 is a reasonable threshold for clinical release, indicating generally acceptable usability. However, clinical readiness depends on more than usability—also assess clinical effectiveness, security, regulatory compliance, and clinical integration. An app with SUS 75 but poor security or ineffective algorithm should not be released.
Should I test with healthcare providers and patients separately, or combined?
Test both if the app serves both populations (e.g., telemedicine app used by patients and clinicians). Their usability needs may differ substantially. Separate SUS scoring for each population enables design optimization for each user group.
Can SUS be administered remotely or must it be in-person?
SUS can be administered remotely via email, web survey, or phone interview. Remote administration introduces fatigue bias (longer questionnaires show lower scores), but SUS's brevity mitigates this. Consider pairing with qualitative interview to capture context.
How should I respond if a user refuses to complete SUS?
Missing SUS data is common; aim for 60% completion rate in remote studies. If substantial portion of users refuse or skip SUS, investigate whether they abandoned the app due to usability; non-response may indicate usability failure rather than engagement issues.
Sources
- Brooke, J. (1996). SUS—A quick and dirty usability scale. In P. W. Jordan, B. Weerdmeester, A. Thomas, & I. L. McClelland (Eds.), Usability evaluation in industry (pp. 189–194). Taylor & Francis. ISBN: 978-0-7484-0635-1
- Bangor, A., Kortum, P. T., & Miller, J. T. (2008). An empirical evaluation of the System Usability Scale. International Journal of Human-Computer Interaction, 24(6), 574–594. DOI: 10.1080/10447310802205776 ↗
How to cite this page
ScholarGate. (2026, June 3). System Usability Scale for Health Applications (SUS-Health). ScholarGate. https://scholargate.app/en/health-informatics/health-app-usability-scale
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Digital Health Acceptance ScaleHealth Informatics↔ compare
- eHealth Literacy ScaleHealth Informatics↔ compare
- Telemedicine Satisfaction ScaleHealth Informatics↔ compare