Page Comparison

General Information

...

The goal has been sub divided into several tasks:

1. Introduce a new convenience class CodedOrFreeText
2. Introduce an Enum for "diagnosis certainty"
3. Introduce an Enum for "condition status"
4. Introduce new Condition domain object, backed by a new `condition` table
5. Introduce a new Diagnosis domain object, backed by a new `encounter_diagnosis` table
6. Introduce new REST APIs for these domain objects
7. Refactor emrapi module's DiagnosisService and ConditionService to use new functionality
8. Create a ticket for migrating existing data captured via the emrapi module
9. Create a ticket for updating the UIs in the reference application to use new tables
10. Refactor emrapi module's ConditionService to use new functionality
11. Create condition data access implementation
12. Introduce new REST APIs for Condition object
13. Create Diagnosis data access implementation
14. Create DiagnosisService implementation
15. Create ConditionService implementation
16. Create a ticket for migrating existing condition data captured via emrapi module

Sprint Dashboard  Jira LegacyserverOpenMRS Issuescolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues20jqlQuerykey = TRUNK-5015 serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95

Key	Summary	T	Created	Updated	Due	Assignee	Reporter	P	Status	Resolution
TRUNK-5015	Core data model should support Encounter Diagnoses	Image Added	2017-01-17	2018-02-26		Segun Ola	Darius Jazayeri	Image Added	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.

...

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=136

...