| Literature DB >> 35348672 |
I Robertson1, C Harrison2, K Y B Ng1, N Macklon3, Y Cheong1, J Boivin2.
Abstract
STUDY QUESTION: Is it possible to develop a patient smartphone application for medically assisted reproduction (MAR) that is acceptable to patients and fertility staff? SUMMARY ANSWER: Staff and patients responded positively to the MediEmo smartphone application, perceiving it to be acceptable and feasible to implement in a busy clinic. WHAT IS KNOWN ALREADY: Digital tools are increasingly popular to provide practical, administrative and psychological support alongside medical treatments. Apps and other digital tools have been developed for use alongside MAR but there is very limited research on the development or acceptability and feasibility of these tools. STUDY DESIGN, SIZE, DURATION: Mixed methods research. This article outlines the development phase of the MediEmo smartphone app, which was guided by the Medical Research Council development framework for complex interventions. The resulting MediEmo app was then implemented into a single centre for MAR in the UK, acceptability evaluated and feasibility explored among 1106 potential participants undertaking IVF cycles. PARTICIPANTS/MATERIALS, SETTING,Entities:
Keywords: IVF mobile phone application; MediEmo; digital technology; mHealth intervention; medical support; psychological support
Mesh:
Year: 2022 PMID: 35348672 PMCID: PMC9071224 DOI: 10.1093/humrep/deac046
Source DB: PubMed Journal: Hum Reprod ISSN: 0268-1161 Impact factor: 6.353
Steps in MediEmo development carried out before the implementation data collection.
| Task and aim | Participants | Materials | Outcome |
|---|---|---|---|
|
| Academic psychologists (n = 2) in consultation with clinicians (n = 2), software engineer (n = 1), nurse manager (n = 1) |
Psychosocial studies Treatment questionnaires (n = 6) Existing fertility-related apps (n = 10) Inquiry with UK clinics (n = 21) regarding app usage | Decision to focus on medical and emotional management of fertility treatment management and the mobile application format. |
|
| |||
|
|
Patients (n = 17) Staff (n = 12) | Mixed methods approach with rating scales, structured list of features and open text questions |
Patients’ desirable support features were reassurance, coping techniques, chat forum, buddy-pairing and support call in waiting period. Staff desirable features were automated appointments, medication management FAQs for patients, a trigger for wellbeing check-in to distressed patients in 2-week waiting period. Benefits proposed for these features were patient support and connection to clinic, timely help-seeking and time efficiencies for staff (e.g. reduced phone calls) that could be re-allocated to patient support. Mobile application would help provide 24-h support. |
|
| |||
|
| Based on Phase I and Phase II psychologists (Cardiff University) developed the critical features specification that were then reviewed and agreed with the clinical and software engineering members of the technical working group | Technical/resource feasibility of: (i) FAQ/information, (ii) symptom checker, (iii) chat room and buddy system, (iv) appointment management, (v) medication and test result management, (vi) staff and patient communication channel, (vii) treatment stage tracker, (viii) emotion symptom tracker and trigger for calling nurse when distressed, (ix) coping techniques for 2-week waiting, (x) data collection feature and service evaluation. | The following components were taken forward (i) information support (FAQ, clinic and IVF information, symptom checker), (ii) monitoring of medication and mood (medication timeline, appointment schedule, mood tracking), (iii) feedback (reminders, trigger for nurse wellbeing check), (iv) coping support (positive reappraisal coping, distraction, thought challenges) and (v) data collection for service evaluation. Technical needs around onboarding, security and privacy, platform and 24-h access, push notifications, continuous updating, data capture and analytics were also identified. |
|
| |||
|
| Technical working group with software engineering team | List of core critical features (Phase II) |
Decision to create a secure cloud-based patient portal with registration (app downloaded App Store or Google Play). Portal automatically receives and encrypts patient registration data and links patient and clinic via unique identifier. Data entered (patient, staff) automatically synchronized keeping portal always up to date. Aggregated mood data used to trigger personal response to patient stress. |
|
| |||
|
| N = 26 users |
Implementation of MediEmo prototype Mixed method consultation, 18 questions about practicality, look and feel and attitude MediEmo |
Overall, above average ratings for practicality and look and feel, and attitude towards MediEmo. Most consistently preferred were medication timeline and information features, considerable variation about other features (i.e. messaging, mood management, coping support) depending on need and previous treatment experience. MediEmo prototype amended to address practical issues of implementation and user preferences. |
Technical working group involved in all aspects of project development.
FAQ, frequently asked questions.
See text for sources consulted.
DrIVF; MyMobileFertility; IVTFertility; FertilityFriend; CinncinnatiFertility; InfertilitySurvivalKit; TheFertilityApp; FertilityView; IVFBabyInTheMaking; iVitro.
Summary of included features (including description by content and delivery characteristics according to Intervention Taxonomy (ITAX)).
Figure 1.Bar plot of patients in each user category, showing total potential user cohort, number using medication timeline only (Medi), number using medication and emotional tracking (Medi + Emo), passive users who downloaded the app but did not use it and those who declined to use the app (non-users).
Break down for number of days of engagement per participant for medication timeline component.
| Number of days medication timeline used | N (number of Medi medication timeline users) | % of Medi users |
|---|---|---|
| (n = 883) | ||
| 1–2 | 112 | 12.7 |
| 3–5 | 27 | 3.1 |
| 6–8 | 31 | 3.5 |
| 9–11 | 27 | 3.1 |
| 12+ | 686 | 77.7 |
Figure 2.Usage pattern of MediEmo emotional tracking during IVF/ICSI. Day of cycle refers to the day in the IVF cycle emotional data was entered on relative to egg collection/transvaginal oocyte recovery day (TVOR day = 0).
Figure 3.Mean negative (red) and positive (blue) emotion scores (±SEM) from day −14 to +14 from day of egg collection.
Figure 4.Mean attitude score for each attitude statement (±standard error bar). Higher scores indicate more positive attitudes.