| Literature DB >> 25138438 |
Amos S Hundert1, Anna Huguet, Patrick J McGrath, Jennifer N Stinson, Mike Wheaton.
Abstract
BACKGROUND: Headache diaries are often used by headache sufferers to self-monitor headaches. With advances in mobile technology, mobile electronic diary apps are becoming increasingly common.Entities:
Keywords: apps; diary; headache; mHealth; mobile phone; review; smartphone; technology
Year: 2014 PMID: 25138438 PMCID: PMC4147710 DOI: 10.2196/mhealth.3452
Source DB: PubMed Journal: JMIR Mhealth Uhealth ISSN: 2291-5222 Impact factor: 4.773
Headache variables recommended by headache experts (n=10).
| Headache variablea | Number of experts recommending, n (%) |
| Headache severity/intensity | 10 (100) |
| Headache triggers | 9 (90) |
| Medication/treatment taken for headache | 9 (90) |
| Associated headache symptoms | 7 (70) |
| Headache frequency (derived from headache occurrence) | 6 (60) |
| Headache-related disability | 5 (50) |
| Headache duration | 5 (50) |
| Response to medication/treatment | 3 (30) |
| Ongoing preventative medication | 2 (20) |
| Time of headache onset | 2 (20) |
| Date of headache | 2 (20) |
| Presence of aura | 2 (20) |
| Menses | 2 (20) |
| Headache pain location | 2 (20) |
| Headache pain quality | 2 (20) |
| Side effects of treatment | 1 (10) |
| Time of treatment | 1 (10) |
| Nonpharmacological treatments | 1 (10) |
| Life events (eg, travel, exercise) | 1 (10) |
| Prodrome symptoms | 1 (10) |
| Sought care from health professionals | 1 (10) |
| Worry/anxiety/fear rating | 1 (10) |
| Stress/mood rating | 1 (10) |
| Sleep rating | 1 (10) |
aVariables recommended by 50% or more of the experts were considered clinically relevant.
Nielson usability heuristics [21].
| Heuristic | Description |
| Visibility of system status | The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. |
| Match between system and the real world | The system should speak the user’s language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. The system should follow real-world conventions, making information appear in a natural and logical order. |
| User control and freedom | Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. The system should support undo and redo. |
| Consistency and standards | Users should not have to wonder whether different words, situations, or actions mean the same thing. The system should follow platform conventions. |
| Error prevention | Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. |
| Recognition rather than recall | Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. |
| Flexibility and efficiency of use | Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. The system should allow users to tailor frequent actions. |
| Aesthetic and minimalist design | Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility. |
| Help users recognize, diagnose, and recover from errors | Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. |
| Help and documentation | Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, be focused on the user's task, list concrete steps to be carried out, and not be too large. |
Available headache diary apps (n=38) and their characteristics, ordered by number of app criteria met.
| Name | Platform/ | Price, Can$ | App criteria | Number of app | ||||||
| Created with headache expertise | Published in scientific | Headache variables measured / Clinically relevant | Usability score (%) | Custom | Reportsb / Reports linking multiple variables | Export data from app | ||||
| iHeadache | iOS/1.45 | 4.99 | Yes | No | 8/7 | 90 | Few/Yes | Yes/No | Yes | 5 |
| Headache Diary (ecoHeadache) | iOS/2.3 | 1.99 | No | No | 13/7 | 94 | Many/Yes | Yes/Yes | Yes | 5 |
| Headache Diary Proc | Android/3.7 | 2.99 | No | No | 10/7 | 82 | Few/Yes | Yes/Yes | Yes | 5 |
| Headache Diary Prod | iOS/1.5 | 3.99 | No | No | 12/7 | 94 | Many/No | Yes/Yes | Yes | 4 |
| Migraine Diary | iOS/2.4.1 | 1.99 | No | No | 10/7 | 90 | Many/No | Yes/Yes | Yes | 4 |
| PainCal | iOS/2.0 | 1.99 | No | No | 9/6 | 80 | Many/Yes | Yes/Yes | Yes | 4 |
| A Migraine Diary for You | iOS&Android /1.1.3 & 1.1 | 4.99 / | No | No | 13/7 | 62 | Many/Yes | Yes/Yes | Yes | 4 |
| Migraine | iOS/1.1 | Free | Yes | No | 7/6 | 72 | Few/No | Yes/Yes | Yes | 3 |
| Migralex | iOS/1.1 | Free | Yes | No | 10/5 | 84 | Few/No | Yes/No | Yes | 3 |
| Oh, My head | iOS/1.0 | 1.99 | No | No | 5/2 | 76 | Few/Yes | Yes/Yes | No | 3 |
| Migraine Free | iOS/1.1 | Free | Yes | No | 5/5 | 74 | None/No | Yes/Yes | Yes | 3 |
| Cluster Headaches | Android | Free | No | No | 4/3 | 80 | Few/No | Yes/Yes | Yes | 3 |
| Headache Relief Log | Android/1.07 | 1.00 | No | No | 7/4 | 80 | Few/No | Yes/Yes | Yes | 3 |
| Headache App | iOS&Android /1.4.5 & 1.5 | Free | No | No | 9/6 | 76 | Many/No | Yes/Yes | Yes | 3 |
| Headache Notee | iOS&Android /1.2.1 & 1.0.3 | Free | No | No | 6/5 | 84 | Few/No | Yes/Yes | Yes | 3 |
| Migraine Meter | iOS/2.6 | Free | Yes | No | 9/7 | 82 | Few/No | Yes/No | Yes | 3 |
| PainTrek | iOS/1.1 | Free | Yes | No | 8/5 | 66 | None/Yes | Yes/Yes | No | 2 |
| American | iOS/1.0.1 | Free | Yes | No | 7/5 | 74 | No/No | No/No | Yes | 2 |
| PainCalendar | iOS/1.0 | 5.99 | No | No | 9/6 | 86 | Few/No | Yes/Yes | No | 2 |
| Headache & | iOS/2.5.0 | 1.99 | No | No | 5/3 | 74 | No/Yes | Yes/Yes | Yes | 2 |
| Migraine | iOS/0.9.1 | Free | No | No | 4/4 | 86 | Few/No | No/No | Yes | 2 |
| MigraineMate | iOS/2.198 | Free | No | No | 3/2 | 94 | No/No | Yes/Yes | No | 2 |
| Migraine Diary | iOS/1.0 | Free | No | No | 8/6 | 86 | No/No | No/No | Yes | 2 |
| Headachef | iOS/1.1.0 | 4.99 | No | No | 6/4 | 82 | Few/No | Yes/Yes | No | 2 |
| Migraine Stop | iOS/1.0 | Free | No | No | 9/6 | 92 | No/No | Yes/No | Yes | 2 |
| Migraine tracker! | iOS/4.0 | Free | No | No | 2/1 | 82 | No/No | No/No | No | 2 |
| Headache diaryg | Android/1.3.0 | 1.34 | No | No | 7/6 | 72 | Few/No | Yes/Yes | Yes | 2 |
| Migraine | Android/4.0 | 1.96 | No | No | 10/6 | 86 | Few/No | Yes/No | Yes | 2 |
| HeadacheDiary | Android/1.0 | 2.04 | No | No | 6/6 | 76 | No/Yes | Yes/Yes | No | 2 |
| Headache Diaryh | Android/1.25 | Free | No | No | 7/4 | 74 | Few/No | Yes/Yes | Yes | 2 |
| MyGraine | iOS/1.1 | Free | No | No | 9/5 | 70 | Few/No | Yes/Yes | Yes | 2 |
| Migraine Institute | iOS/1.4 | 0.99 | Yes | No | 8/6 | 74 | No/No | No/No | Yes | 2 |
| Ubiqi Health | Android/2.1 | Free | No | No | 7/5 | 82 | Many/No | No/No | Noi | 1 |
| Migraine Tracker | Android/0.9b | Free | No | No | 4/3 | 86 | No/No | No/No | No | 1 |
| My Headache Diary | iOS/1.1 | Free | No | No | 7/5 | 72 | No/No | No/No | No | 0 |
| migraineDiary | Android/0.1 | Free | No | No | 5/4 | 72 | No/No | No/No | No | 0 |
| Headache Diaryj | Android/1.1 | 0.99 | No | No | 6/5 | 64 | No/No | No/No | No | 0 |
| Headache & | iOS/1.2 | 0.99 | No | No | 5/3 | 0k | Few/No | No/No | No | 0 |
aFew: 3 or less headache variables allow for custom answer options; Many: more than 3 headache variables allow for custom answer options.
bRefers to the app’s ability to create reports in general, not necessarily custom reports or reports linking multiple variables.
cDeveloped by Froggyware.
dDeveloped by appcellent GmbH.
eFull name: Headache Note – You can manage headache by recording the pain and the taken medicine (iOS name); Headache Note-be healthier- (Android name).
fFull name: Headache – migraine and headache journal/log/calendar.
gDeveloped by Marcel Shroder.
hDeveloped by Benjamin Gerfelder.
iAble to export data from website component associated with app.
jDeveloped by Tmoney.
kNot usable; unable to load headache entries.
Figure 1The home screen of iHeadache (left), ecoHeadache (middle), and Headache Diary Pro (right).
Number of apps meeting each app criterion (N=38).
| Criterion | Number of apps meeting the criterion, n (%) |
| 1. Created with headache expertise | 7 (18) |
| 2. Formal psychometric and feasibility testing | 0 (0) |
| 3. Clinically relevant headache variables measured | 7 (18) |
| 4. Usable | 24 (63) |
| 5. Customizable answer options and reports | 9 (24) |
| 6. Reports linking multiple variables | 22 (58) |
| 7. Export headache data from app | 25 (66) |
Headache variables measured by all apps (n=7) meeting 4 or more app criteria.
| Headache variables measured | App | ||||||
|
| iHeadache | Headache Diary (ecoHeadache) | Headache Diary Proa | Headache Diary Prob | Migraine Diary | PainCal | A Migraine Diary for You |
| Headache severity/intensity | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Headache triggers | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Medication/treatment taken for headache | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Associated headache symptoms | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Headache frequency | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Headache-related disability | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✓ |
| Headache duration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Time of headache onset | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Headache pain location |
| ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Headache pain quality |
| ✓ |
| ✓ |
| ✓ | ✓ |
| Nonpharmacological treatment and coping strategies |
| ✓ |
| ✓ | ✓ |
| ✓ |
| Type of day (eg, work, school) |
| ✓ |
|
|
|
|
|
| Type of headache |
| ✓ | ✓ |
|
|
|
|
| Weather when headache occurred |
|
|
|
|
|
| ✓ |
| Activity when headache occurred |
|
|
|
|
|
| ✓ |
| Geographical location when headache |
|
|
| ✓ |
|
|
|
aDeveloped by Froggyware.
bDeveloped by appcellent GmbH.