| Note |
|---|
This page is outdated and no longer receives updates! |
This overview of mobile tools that interact with OpenMRS is intended as a resource for implementers who may be interested in using such tools. If you are developing or innovating with mobile devices and want to share ideas, check out the Mobile Work Group.
| Info | |
|---|---|
| title | Note :The mobile tools on this page use various methods for exchanging data with OpenMRS. A majority of these tools use the ?XForms Module. Attendees of a mobile break out session at the 2009 OpenMRS implementers meeting agreed that using the XForms module to integrate various mobile tools to with OpenMRS would be a good way to collaborate. |
...
Table of Contents - click links to navigate
mOpenMRS (mobile OpenMRS)
| Anchor | ||||
|---|---|---|---|---|
|
...
eg http://122.234.244.132:8088/openmrs.
Treatment supporter logs in the system
Cohorts are downloaded
Patients are downloaded
Patients Forms are downloaded
Patients are searched
Form(s) related to the patient are filled
Forms are uploaded
Encounters are uploaded and can be viewed by providers using
Note: Currently cohorts are mapped with users based on the cohort name. Therefore the cohort name has to be the same as the user name. Eg, user 'peter' would have only see cohort also called 'peter'
The data is exchanged with the server using Xforms module built by Daniel Kaiwa (who developed the initial OpenXData-OpenMRS application)
Implementation Details: For the treatment of TB patients we follow the internationally recognised and followed method of Directly Observed Therapy. In DOT a trained treatment supporter administers the dose to a TB patient and watches the patient take it. This is then recorded everyday along with other very important information such as side effects, any noticeable changes in patient's contacts (immediate family such as parents, spouse, etc). In the mobile application's pilot implementation we provided 3 treatment supporters Nokia 2710NE cell phones with the OpenMRS mobile application pre-installed. The mobile implementation or mOpenMRS allows quick reporting and enables the providers to view the patient status on the browser window when they log into OpenMRS. The mobile application allows treatment supporters to download cohorts (group of patients assigned to each treatment supporter), download forms and upload filled forms to the server. More can be found on this Google Group ict4chw
Pre-requisites:
OpenMRS Version 1.5
XForms module (used and tested with 3.7.9)
J2ME enabled phones
Cost: Open source
Download: projects:JAR File, projects:JAD file
Future Work/ Enhancements
Remove dependency on cohort name and user name by introducing link table in the database for making the cohort-user mapping.
Incorporate GPS
Known Issues
1) Some* *incorrect URLs can make the application download for a long time without giving proper error
...
Where to find additional Information: The FrontlineSMS:Medic website, or contact Field Director Isaac Holeman.
| Anchor | ||||
|---|---|---|---|---|
|
...
General need/use case:
This application provides an interface for accessing OpenMRS via a J2ME phone. Useful for community/mobile health workers who need access to the OMRS system, for example, a health worker at small health center supported by a large hospital which runs OpenMRS.
How it works:
Health worker logs in with user name and password
Downloads available cohorts (if all patients then all patients must be available as a cohort?)
Selects a cohort and downloads the list of patients in this cohort. To save on data costs it is probably worth creating sensible sub-sets of patients
xForms in the openMRS system that represent a range of customizable encounters can then be downloaded onto the mobile phone.
Healthworker can then user the mobile interface to edit and submit forms for each patient and uploaded to openMRS.
If health worker wants to find a patient that is not on their phone, they can query the OpenMRS server and download that patient's file.
Prerequisites:
Requires ?XForms Module to be running on openMRS server
Requires J2ME enabled phone. In Pakistan, IRD have tried it running on sub $100 phones e.g. Nokia 2700 with success. It has also opened on Nokia 2600 but not tried serious usage.
openMRS 1.5 (not openMRS 1.6). The mobile client has not been updated to encompass more recent features of openMRS 1.6 and therefore although xforms module is compatible with 1.6 the mobile client currently available (also v1.6) is not.
GPRS connectivity
Download:
http://code.zegeba.org/svn/openxdata_binaries/Releases/OpenMRS%20Mobile/
Lite edition is for phones without GPS (same nomenclature as OpenXData)
Costs:
Free and open source.
Expertise Required:
Current Implementations: ?
...
Where to find additional Information: Contact Aliya Walji (awalji atat grameenfoundation.org) or Bruce MacCleod (macleod atat usm.maine.edu)
| Anchor | ||||
|---|---|---|---|---|
|
...
Overview. Tools to help organizations collect, aggregate and visualize their data. Focused on data standards (i.e. Xforms), and using robust tools (Android software platform and compatible phones) to ensure organizations can collect rich data.
Form Filling (demo). Has functionality in ODK Collect so you can download an OpenMRS XForm and fill it out (both text and binary data) and submit it back to OpenMRS as an encounter.
Patient Summaries (demo). Users can view a list of patients and view and edit encounters on the phone. Concepts like weight and CD4 are graphed. All changes to the patient gets synchronized to the server.
How it works: Developed on Android, will initially communicate data via GPRS or WiFi. UI very robust.
...
Muzima
General need/use case: Muzima Muzima is an ongoing effort to consolidate the mobile based system around AMPATH.
How it works: Muzima API
Costs: Free and Open Source
...
Github repos: https://github.com/organizations/muzima | Mailing list: https://groups.google.com/forum/?hl=en&fromgroups#!forum/muzima
| Anchor | ||||
|---|---|---|---|---|
|
SMS, USSD services for Patients
General need/use case: Medical data must be accessible to a patient through many channels. This DEMO Application will allow a patient to access and edit their OpenMRS system information through SMS, USSD. Patients will be able to edit their details, view structured medical data, see current prescriptions, and etc.
...
| Anchor | ||||
|---|---|---|---|---|
|
OpenMRS-iOS Client
General need/use case:
The goal of this project is to provide an OpenMRS client for iOS devices.
Features: Login to any OpenMRS installation, Search for patients, Add patients to the database, View patient visits and vitals, Record a patient's vitals, Take visit notes, Use the app offline. You can store selected patients to an encrypted database on your device, then access them anywhere in the world.
How it works:
...
The app communicates with OpenMRS using REST. The app can store patient data offline in an encrypted database.
Costs: Free and Open-source
...
The goal of this project is to provide OpenMRS 2.x client for Android devices. The app will cover most of the functionality of the web application including registering patients, taking visit notes, capturing vitals, etc..
How it works: The app will communicate with OpenMRS using REST. It will support working off-line (without network connection) with a chosen subset of patients. The database on the device will be encrypted and password protected to secure patient data.
Costs: Free and Open-source
...