| Literature DB >> 32223740 |
Lavanya Vasudevan1,2, Kristin Schroeder3,4,5, Yadurshini Raveendran3, Kunal Goel6, Christina Makarushka7, Nestory Masalu5, Leah L Zullig8,9.
Abstract
BACKGROUND: In high-income countries (HICs), increased rates of survival among pediatric cancer patients are achieved through the use of protocol-driven treatment. Compared to HICs, differences in infrastructure, supportive care, and human resources, make compliance with protocol-driven treatment challenging in low- and middle-income countries (LMICs). For successful implementation of protocol-driven treatment, treatment protocols must be resource-adapted for the LMIC context, and additional supportive tools must be developed to promote protocol compliance. In Tanzania, an LMIC where resource-adapted treatment protocols are available, digital health applications could promote protocol compliance through incorporation of systematic decision support algorithms, reminders and alerts related to patient visits, and up-to-date data for care coordination. However, evidence on the use of digital health applications in improving compliance with protocol-driven treatment for pediatric cancer is limited. This study protocol describes the development and evaluation of a digital health application, called mNavigator, to facilitate compliance with protocol-driven treatment for pediatric cancer in Tanzania.Entities:
Keywords: Burkitt lymphoma; Client health records; Digital health; Healthcare provider decision support; Low- and middle-income countries; Pediatric cancer; Protocol-driven treatment; Retinoblastoma; Tanzania; Treatment abandonment
Mesh:
Year: 2020 PMID: 32223740 PMCID: PMC7104518 DOI: 10.1186/s12885-020-6611-3
Source DB: PubMed Journal: BMC Cancer ISSN: 1471-2407 Impact factor: 4.430
The TIDieR (Template for Intervention Description and Replication) Checklist*: Information to include when describing an intervention and the location of the information
| Item number | Item | Where located ** | |
|---|---|---|---|
| Primary paper | Other † (details) | ||
| BRIEF NAME | |||
| 1. | Provide the name or a phrase that describes the intervention. | ____8________ | ______________ |
| WHY | |||
| 2. | Describe any rationale, theory, or goal of the elements essential to the intervention. | ___13, Additional file | _____________ |
| WHAT | |||
| 3. | Materials: Describe any physical or informational materials used in the intervention, including those provided to participants or used in intervention delivery or in training of intervention providers. Provide information on where the materials can be accessed (e.g. online appendix, URL). | ___9-11_____ | _____________ |
| 4. | Procedures: Describe each of the procedures, activities, and/or processes used in the intervention, including any enabling or support activities. | _13–18, table 2_ | _____________ |
| WHO PROVIDED | |||
| 5. | For each category of intervention provider (e.g. psychologist, nursing assistant), describe their expertise, background and any specific training given. | __12_____ | _____________ |
| HOW | |||
| 6. | Describe the modes of delivery (e.g. face-to-face or by some other mechanism, such as internet or telephone) of the intervention and whether it was provided individually or in a group. | __12-13________ | _____________ |
| WHERE | |||
| 7. | Describe the type(s) of location(s) where the intervention occurred, including any necessary infrastructure or relevant features. | ___9, Additional file | _____________ |
| WHEN and HOW MUCH | |||
| 8. | Describe the number of times the intervention was delivered and over what period of time including the number of sessions, their schedule, and their duration, intensity or dose. | ____12_______ | _____________ |
| TAILORING | |||
| 9. | If the intervention was planned to be personalised, titrated or adapted, then describe what, why, when, and how. | _14, figure 1___ | _____________ |
| MODIFICATIONS | |||
| 10.a | If the intervention was modified during the course of the study, describe the changes (what, why, when, and how). | _____N/A_____ | _____________ |
| HOW WELL | |||
| 11. | Planned: If intervention adherence or fidelity was assessed, describe how and by whom, and if any strategies were used to maintain or improve fidelity, describe them. | _assessed by data from app (protocol compliance), Tables | _____________ |
| 12.a | Actual: If intervention adherence or fidelity was assessed, describe the extent to which the intervention was delivered as planned. | ____N/A______ | _____________ |
a These items are not relevant to the protocol and cannot be described until the study is complete
Summary of study activities using the Consolidated Framework for Implementation Research process
| CFIR phase | Activities | Tasks |
|---|---|---|
| PLAN | Workflow mapping | Existing clinical workflows Provider tasks Patient navigator tasks |
| Form development | Translation of clinical workflows and national treatment guidelines to data entry forms Programming in CommCare HQ | |
| ENGAGE | Quality assurance | Personas De-identified patient records Iterative testing and updates |
| Usability testing | System usability score Think aloud method | |
| EXECUTE | In-country training | Training on mNavigator In-country capacity building for sustainability |
| Implementation in routine clinical use | Supported launch Full launch | |
| REFLECT AND EVALUATE | Implementation- effectiveness hybrid design | Clinical effectiveness System evaluation Implementation factors |
Fig. 1Detailed draft workflow for retinoblastoma staging incorporating clinical workflows at BMC and the nationally-approved resource-adapted standardized treatment protocol
Fig. 2mNavigator user interface draft. a. mNavigator home screen. b. List of forms built in for Burkitt lymphoma patients. c. Example case detail showing contact information of a fictitious patient. d. Example of data entry question on tumor staging with pictorial support. e. Illustration of automated calculation of next chemotherapy cycle dates. h. Display example of chemotherapy cycle status
Summary of outcomes related to intervention effectiveness and their measurement
| Outcome | Measure | Data source |
|---|---|---|
| Change in protocol compliance (primary outcome) | Percent difference in protocol compliance with mNavigator and historical compliance. Protocol compliance is calculated as proportion of protocol steps completed, based on a compliance checklist. | mNavigator data from prospectively registered pediatric cancer patients from July 2019 – July 2020 and data extracted from paper charts for patients registered at BMC from 2015 – June 2019 entered into mNavigator |
| Change in treatment abandonment (secondary outcome) | Calculated as the difference in proportion of patients registered in mNavigator who abandoned treatment compared to historical controls who abandoned treatment. Treatment abandonment is defined as missing four or more consecutive weeks of treatment or follow-up while still on therapy. | Data from mNavigator (outcome form) |
| Change in treatment completion rate | Calculated as the proportion of patients registered in mNavigator who completed treatment compared to historical controls | Data from mNavigator (outcome form) |
| Change in time to diagnosis | Change in the number of days to diagnosis using mNavigator compared to historical controls. Time to diagnosis is computed as the duration from registration to diagnosis | Data from mNavigator (registration form; diagnosis form) |
System-level outcomes related to the mNavigator application
| Outcome | Measure | Data source |
|---|---|---|
| Usabilitya | System usability scale score ranging from 0 to 100. A SUS score above a 68 is considered above average and anything below 68 is below average. | 10-point validated system usability scale |
| Acceptability | Proportion of providers who would continue to use the app. Proportion of providers who would recommend the app to others. | Semi-structured interviews |
| Utilization | Number of forms submitted, stratified, by users, per month of implementation | Data from mNavigator (Mobile users statistics) |
| Reach | Number of patients registered in mNavigator during study period | Data from mNavigator (Mobile users statistics) |
| Stability | • Number of instances of mNavigator failure per month (all-causes) • Number of instances of CommCare failure per month (all-causes) • Number of instances of device • failure per month (all-causes) | Data from CommCare (Worker Activity and Daily Activity reports) cross checked with manual reports from Mobile users |
| Training | Number of hours of initial training as well as hours of ongoing support provided during the first month of Implementation | Manually recorded from Duke team members that are performing initial training |
| User-proficiency | Number of users who are proficient in use of mNavigator within first month of implementation | Data from CommCare (Worker Activity reports) |
| Time per form | Average time in minutes spent completing each form, stratified by form | Data from mNavigator (Mobile users statistics) |
| Time per patient | Total time in minutes spent entering patient data in mNavigator, from time of registration until an outcome is recorded. Calculated by summing time for completing each form by patient. | Data from mNavigator (Mobile users statistics) |
aSystem Usability Scale developed by John Brooke is available from www.usability.gov