| Literature DB >> 27731861 |
Jean Christophe Rusatira1, Brian Tomaszewski, Vincent Dusabejambo, Vincent Ndayiragije, Snedden Gonsalves, Aishwarya Sawant, Angeline Mumararungu, George Gasana, Etienne Amendezo, Anne Haake, Leon Mutesa.
Abstract
BACKGROUND: Lack of access to health and medical education resources for doctors in the developing world is a serious global health problem. In Rwanda, with a population of 11 million, there is only one medical school, hence a shortage in well-trained medical staff. The growth of interactive health technologies has played a role in the improvement of health care in developed countries and has offered alternative ways to offer continuous medical education while improving patient's care. However, low and middle-income countries (LMIC) like Rwanda have struggled to implement medical education technologies adapted to local settings in medical practice and continuing education. Developing a user-centered mobile computing approach for medical and health education programs has potential to bring continuous medical education to doctors in rural and urban areas of Rwanda and influence patient care outcomes.Entities:
Keywords: mobile medical education; technology; user-centered design
Year: 2016 PMID: 27731861 PMCID: PMC5041362 DOI: 10.2196/mededu.5336
Source DB: PubMed Journal: JMIR Med Educ ISSN: 2369-3762
| Number | Principle | Rwanda mobile medical educator app |
| P1 | Understand the user, task, and environment requirements | Choose appropriate metrics: baseline study and needs assessment |
| P2 | Encourage early and active involvement of users | Interaction between users and developers to develop first version of prototype |
| P3 | Be driven and refined by user-centered evaluation | Valid evaluation metrics |
| P4 | Include iteration of design solutions | Continuous interaction between developers and end users in their home environment leading to several prototypes |
| P5 | Address the whole user experience | Evaluation metrics that covers all aspects “usability” (ie, effectiveness, efficiency, satisfaction) |
| P6 | Encourage a multi-disciplinary design | Identify need and potential impact |
| S1 | Understand and specify the context of use | Identify need and potential impact through the baseline study |
| S2 | Specify the user requirements for medical education, knowledge sharing and decision making support | Questionnaires and interviews for needs assessment |
| S3 | Produce design solutions to meet user requirements | Prototypes available for testing of usability |
| S4 | Evaluate the designs against requirements | Evaluation metrics (effectiveness, efficiency, satisfaction) |
Figure 1Doctors’ means of accessing the Internet in hospitals.
Figure 2Internet use for medical resources.
Figure 3Medical resources used from the Internet.
Figure 4Means of accessing the Internet.
Figure 5Examples of outdated medical books in a Rwandan hospital library.
Figure 6Use case diagram for the mobile medical educator application for Rwandan medical doctors.
Detailed use cases.
| ID | Name | Description |
| UC1 | User registration | This use case describes how to sign up for the app |
| UC2 | User login | This use case describes how to sign in for the app |
| UC3 | Validate medical license | This use case describes how the app will validate doctors credentials with MOH |
| UC4 | Access MOH guideline documentation | This use case describes how a doctor consults the MOH guidelines in the app |
| UC5 | Create discussion thread | This use case describes how a doctor discusses a general topic with fellow doctors |
| UC6 | Search discussion thread | This use case describes how a user searches for a discussion thread |
| UC7 | Access patient case studies | This use case describes how a user accesses a patient discussion thread |
| UC8 | Archive discussions and case studies for offline access | This use case describes how the doctor makes discussion available for offline use |
| UC9 | Update experienced doctor privileges | This use case describes how the app administrator updates the users with experienced doctor privileges |
| UC10 | Edit discussion thread | This describes how to edit existing discussion thread |
| UC11 | Delete discussion thread | This use case describes how a user will delete a discussion thread |
| UC12 | Edit a patient case record | This use case describes how a user can edit a patient case record |
| UC13 | Search a patient case record | This use case describes how a user can search for a patient case record |
| UC14 | Post a comment to a discussion thread | This use case describes how the doctor adds a new post/comment to discussion thread |
| UC15 | Delete a patient case record | This use case describes how the system deletes a patient’s case discussion record |
| UC16 | Create a patient case record | This use case describes how a doctor creates a patient record discussion |