| Literature DB >> 28351881 |
Ranit Mishori1, Michael Anastario2, Karen Naimer3, Sucharita Varanasi4, Hope Ferdowsian3, Dori Abel5, Kevin Chugh6.
Abstract
Digital health development and use has been expansive and operationalized in a variety of settings and modalities around the world, including in low- and middle-income countries. Mobile applications have been developed for a variety of health professionals and frontline health workers including physicians, midwives, nurses, and community health workers. However, there are no published studies on the development and use of digital health related to human rights fieldwork and to our knowledge no mobile health platforms exist specifically for use by frontline health workers to forensically and clinically document sexual violence. We describe a participatory development and user design process with Congolese end-users of a novel human rights app for clinicians intended to standardize the documentation of sexual violence evidence for forensic and legal purposes, called MediCapt. The app, yet to be launched and still in the future proofing phase, has included several development phases: (1) initial needs assessment conducted in 2011, (2) prototype development and field-testing in 2014 with 8 Congolese physicians, (3) prototype refinement and field-testing in 2015 with 9 clinicians. Feedback from the first field-testing phase was incorporated into the design of the second prototype; key features that were added to MediCapt include the ability for users to take photographs and draw on a pictogram to include as part of the evidence package, as well as the ability to print a form with the completed data. Questionnaires and key-informant interviews during the second and third field-testing phases revealed overall positive attitudes about MediCapt, but multiple perceived and actual barriers to implementation were identified, from personal behaviors, such as individual clinicians' comfort with new technology, to more systemic and infrastructure factors, such as strong cultural preferences for print documentation of evidence and limited Internet connectivity. Next phases of development include consideration of patients' acceptance of this technology, how it actually fits in the clinical workflow, and testing of how to transfer the collected evidence to law enforcement and legal authorities. Ultimately, we plan on conducting a robust evaluation to assess effectiveness of the app on medical, legal, and human rights outcomes. We believe our experience of collecting data that will potentially serve as legal evidence broadens the traditional scope of digital health and crosses a wide range of fields including medical, technological, legal, and ethical, and thus propose refining and defining this unique field of exploration as mobile justice, or mJustice. © Mishori et al.Entities:
Mesh:
Year: 2017 PMID: 28351881 PMCID: PMC5478223 DOI: 10.9745/GHSP-D-16-00233
Source DB: PubMed Journal: Glob Health Sci Pract ISSN: 2169-575X
FIGURE 1General Architecture of the MediCapt App
The screen on the left shows the home screen; the middle screen is the main menu that allows users to complete a new sexual violence form, browse saved forms, and sync their data when connected to the Internet; and the screen on the right shows an example of data-entry fields.
FIGURE 2Flow of Sexual Violence Evidence Using the MediCapt App
Abbreviation: API, application programming interface.
MediCapt Development Process Compared With Principles for Digital Development Benchmarks
| Principles for Digital Development | MediCapt Development Process |
|---|---|
| Develop context-appropriate solutions informed by user needs | ✓ |
| Include all user groups in planning, development, implementation, and assessment | ✓ |
| Develop projects in incremental and iterative manner | ✓ |
| Design solutions that learn from and enhance existing workflows, and plan for organizational adaptation | ✓ |
| Ensure solutions are sensitive to, and useful for, the most marginalized populations: women, children, those with disabilities, and those affected by conflict and disaster | ✓ |
| Participate in networks and communities of like-minded practitioners | ✓ |
| Align existing technological, legal, and regulatory policies | ✓ |
| Design for scale from the start, and assess and mitigate dependencies that might limit ability to scale | ✓ |
| Employ a systems approach to design, considering implications of design beyond an immediate project | ✓ |
| Be replicable and customizable in other countries and contexts | Planned |
| Demonstrate impact before scaling a solution | In process |
| Analyze all technology choices through the lens of national and regional scale | ✓ |
| Factor in partnerships from the beginning, and start early negotiations | ✓ |
| Plan for sustainability from the start, including planning for long-term financial health | In process |
| Utilize and invest in local communities and developers by default, and help catalyze their growth | Not done |
| Engage with local governments to ensure integration into national strategy, and identify high-level government advocates | ✓ |
| Design projects so that impact can be measured at discrete milestones with a focus on outcomes rather than outputs | In process |
| Evaluation innovative solutions and areas where there are gaps in data and evidence | ✓ |
| Use real-time information to monitor and inform management decisions at all levels | Planned for future |
| When possible, leverage data as a by-product of user actions and transactions for assessment | Planned for future |
| Adopt and expand existing open standards | Partially done |
| Open data and functionalities, and expose them in documented APIs | ✓ |
| Invest in software as a public good | ✓ |
| Develop software to be open source by default with the code made available in public repositories and supported through developer communities | Planned for future |
| Use, modify, and extend existing tools, platforms, and frameworks when possible | ✓ |
| Develop in modular ways favoring approaches that are interoperable over those that are monolithic by design | ✓ |
| Assess and mitigate risks to the security of users and their data | ✓ |
| Consider the context and needs for privacy of personally identifiable information when designing solutions and mitigate accordingly | ✓ |
| Ensure equity and fairness in co-creation, and protect the best interests of the end-users | ✓ |
| Engage diverse expertise across disciplines and industries at all stages | ✓ |
| Work across sector silos to create coordinated and more holistic approaches | In progress |
| Document work, results, processes, and best practices, and share them widely | ✓ |
| Publish materials under a creative commons license by default, with strong rationale if another licensing approach is taken | ✓ |
Abbreviation: API, application programming interface.
FIGURE 3Pictogram Feature in the MediCapt App to Document Location and Type of Injuries
Left: The provider can show the location of the patient's injuries on a pictogram, shown with red dots.
Right: The provider can also include additional clinical data (e.g., type, size, and depth) about a specific injury.
Barriers to Integrating MediCapt Sexual Violence Documentation App Into Existing Workflows Reported by Key Informants (N=9)
| Type of Barrier | Examples |
|---|---|
| Infrastructural |
Frequent periods with no electricity No Wi-Fi availability during electricity stoppage time Lack of clarity regarding data storage, cloud location, and capacity Limited or no availability of printers and copiers and their associated supplies |
| Systemic and organizational |
Questions regarding organizational support of project (at hospital, district, regional, and national levels) Long-standing workflow practices that promote redundancy and inefficiency (need for multiple copies including the patient chart, carnet, and Standard Sexual Violence form) Need to train multiple clinicians in using app and allowing clinicians time off for training Limited or no availability of electronic medical record system or links to hospital archives |
| Personal behavior |
Educational barriers for technology use (minimal) Personal leadership attributes that affect workflow within health care facility Presence of and ability to negotiate perceived jealously and peer resentment Degree of willingness to try new things Degree of willingness to invest more time initially in learning and using app |