Encounter Diagnosis Sprint 4

Owned by Iheanyichukwu Kelechi
Last updated: Mar 27, 2018
2 min read

General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Kelechi Iheanyichukwu

Timeline

Start Date: Mar 26, 2018 

End Date: Apr 6, 2018 

Participants

  • Cecilia Nalubega 

  • Patrick Luwum

  • Kelechi Iheanyichukwu

  • Arthur Thungu

  • Isaiah King'ori

  • Segun Ola

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 these domain objects

  2. Refactor emrapi module's DiagnosisService and ConditionService to use new functionality

  3. Create a ticket for migrating existing data captured via the emrapi module

  4. Create a ticket for updating the UIs in the reference application to use new tables

  5. Refactor emrapi module's ConditionService to use new functionality

  6. Introduce new REST APIs for Condition object

  7. Create a ticket for migrating existing condition data captured via emrapi module



Sprint Dashboard 





Key

Summary

T

Created

Updated

Due

Assignee

Reporter

P

Status

Resolution

Key

Summary

T

Created

Updated

Due

Assignee

Reporter

P

Status

Resolution

TRUNK-5015

Core data model should support Encounter Diagnoses

2017-01-17

2018-03-12



Kelechi Iheanyichukwu

Darius Jazayeri

IN PROGRESS

Unresolved







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 http://en.flossmanuals.net/openmrs-developers-guide/support/

  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. 

Resources

JIRA board: https://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=149

Github repo: https://github.com/openmrs/openmrs-core