Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
title2014 Internship Project

This project is being considered as a potential project for 2014 Internships. If you are a potential intern and are interested in working on this project, please discuss it in detail with the mentor(s) listed here before submitting your internship proposal.

Primary mentor

Unknown User (jeremy)

Backup mentor


Assigned to



Many international communities are looking for low-bandwidth, low-resource solutions for hosting and connecting to OpenMRS via 2G or 3G networks.  They need a version of OpenMRS that can be accessed easily through a mobile browser or a laptop connected to a low-bandwidth ISP.



This project aims to provide a modified UI atop (or in place) of the reference application, sufficiently reducing the size of the pages and associated resources. It will take direction from the existing reference application for which pages or views should be modified or replaced.

Project Champions


  1. Identify the heaviest / most resource-laden page views in the reference application
  2. Establish a style guide for a low-bandwidth skin
  3. Implement replacements for login, app list, registration, and visit dashboards
  4. Load a visit dashboard within a "reasonable" time over a 2G connection
  5. Provide instructions on how to write a low-bandwidth version of existing or new views


The classic use case for this module would be a health worker using a tablet or smartphone in a 2G area; we should not be concerned with feature phone web page rendering problems.  Similarly a satellite uplink or tethered phone in a low connectivity area would be ideal for demonstrating the benefits of using this module in place of the reference application.


I believe the key to this will be smart UI design and a style guide that allows for minimal page entities while conveying the right amount of information and functionality.  We might trade off automation for page load timing.  We could also investigate how to preload some data and allow the phone to catch up and enable automation after the user has some way to view the bulk of the data.


  • To be developed


  • To be provided