Page tree
Skip to end of metadata
Go to start of metadata

General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Patrick Alvin Luwum


Start Date:  

End Date:  


  • Cecilia Nalubega 
  • Patrick Luwum
  • Kelechi Iheanyichukwu
  • Arthur Thungu
  • Isaiah King'ori

Sprint Goals

This sprint designed to implement Conditions and Encounter Diagnoses in the OpenMRS core platform.

The goal has been sub divided into several tasks:

  1. Introduce new REST APIs for the Diagnosis object
  2. Refactor emrapi module's DiagnosisService to use new functionality
  3. Create a ticket for updating the UIs in the reference application to use new diagnosis tables
  4. Introduce new REST APIs for the Condition object
  5. Migrate existing condition data captured via the emrapi module
  6. Migrate existing diagnosis data captured via the emrapi module
  7. Refactor emrapi module's ConditionService to use new functionality
  8. Create a ticket for updating the UIs in the reference application to use new condition tables

Sprint Dashboard












TRUNK-5015Core data model should support Encounter DiagnosesNew Feature2017-01-172018-03-12
Kelechi IheanyichukwuDarius JazayeriMustIN PROGRESSUnresolved

How to Participate 

Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.

The general process:

  1. New to OpenMRS sprints? Want help getting started? Join IRC and say "???": I'd like to participate in the sprint!". If you get no response, just ping any of the above sprint participants as per the IRC tips at
  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page at:
    • Make sure it does not depend on a ticket that is incomplete.
  3. If you have any questions about the ticket, ask on the group chat
  4. Do the ticket. See our HOWTO for git. Sprint specific git HOWTO for devs with push rights: whatever works for you :-) If you don't like pull requests, don't send them. Commit and push directly to the main repo. If you do like pull requests, fork the main repo and send pull requests, but merge them right after. My favorite way is to work on the main repo, but create local branches (without pushing them to the main repo). Merge branches locally to the master and push to the main repo.
  5. Join the daily scrum to share your updates

During Project Notes for the sprint

To be added while the project progresses 

Sprint Retrospective:

To be added after the end of the sprint. 


JIRA board:

Github repo:

  • No labels