Table 3.
Aspects | Apps, n (%) | ||
Security and privacya | |||
|
Specificity: Health specificity of information available to apps | ||
|
Standard | 4 (40) | |
|
Nonstandard | 1 (10) | |
|
Medical | 5 (50) | |
|
Leaks: Potential damage through information leaks | ||
|
None | 6 (60) | |
|
Low | 0 (0) | |
|
High | 4 (40) | |
|
Change: Potential damage through manipulation (change) of information | ||
|
None | 1 (10) | |
|
Low | 1 (10) | |
|
High | 8 (80) | |
|
Loss: Potential damage through loss of information | ||
|
None | 4 (40) | |
|
Low | 2 (20) | |
|
High | 4 (40) | |
|
Value: Value of information to third parties | ||
|
|
None | 4 (40) |
|
|
Low | 2 (20) |
|
|
High | 4 (40) |
Quality of information | |||
|
Include a disclaimer to report limitations | 5 (50) | |
|
Mention the source of the provided information | 4 (40) | |
|
Mention how often the information is updated | 0 (0) |
aAnalyzed using the security and privacy assessment tool for mHealth apps proposed by Dehling et al [16].