Details
-
Type:
Epic
-
Status: Waiting for Dev
-
Priority:
TBD
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Complexity:Undetermined
-
Epic Name:Condition List
Description
The API for this is defined in: EA-40
Gliffy Diagrams
Issue Links
- depends on
-
EA-40
Condition List V1
-
- Ready for Work
-
- relates to
-
TRUNK-1633
Limit classes of concepts usable on the Problem List in the Patiant Dashboard
-
- Design
-
Issues in Epic
Activity
We may want to consider calling this "Condition List" (i.e., using the term "Condition" instead of "Problem" to align with FHIR and other more recent work in this space).
Burke Mamlin
added a comment - We may want to consider calling this "Condition List" (i.e., using the term "Condition" instead of "Problem" to align with FHIR and other more recent work in this space). Does this epic need to be included in the Condition List board? On the 12/1 PM call it was noted that this is the epic of tickets from the original sprint. However it appears EA-40 is the epic with tickets. Does RA-209 have relevent info that should be filtered in?
Jamie Thomas
added a comment - Does this epic need to be included in the Condition List board? On the 12/1 PM call it was noted that this is the epic of tickets from the original sprint. However it appears EA-40 is the epic with tickets. Does RA-209 have relevent info that should be filtered in? I assigned this ticket to Émerson Hernandez for book-keeping purposes, since the Bahmni team is working on this.
Darius Jazayeri
added a comment - I assigned this ticket to Émerson Hernandez for book-keeping purposes, since the Bahmni team is working on this. Hi,
I went through this and @EA-40, but I can't seem to find any indication of the work done/planned for the UI end of managing conditions. Will this be on the technical roadmap for OpenMRS 2.3 too?
Suranga Kasthurirathne
added a comment - Hi,
I went through this and @ EA-40 , but I can't seem to find any indication of the work done/planned for the UI end of managing conditions. Will this be on the technical roadmap for OpenMRS 2.3 too?
CC Harsha Kumara In EA-40, a Java API was created.
We still need to create tickets for an implement (a) a web service API, (b) a UI for this.
The idea is that these should be part of OpenMRS 2.3, but that's going to depend on people having time to spec these things out.
Darius Jazayeri
added a comment - In EA-40 , a Java API was created.
We still need to create tickets for an implement (a) a web service API, (b) a UI for this.
The idea is that these should be part of OpenMRS 2.3, but that's going to depend on people having time to spec these things out. Thank you [~djazayeri], we'll keep our eyes peeled for this 
Suranga Kasthurirathne
added a comment - Thank you [~djazayeri] , we'll keep our eyes peeled for this Suranga Kasthurirathne, you may want to watch the road map page at http://om.rs/roadmap. We try to update it weekly (excluding holidays).
Burke Mamlin
added a comment - Suranga Kasthurirathne , you may want to watch the road map page at http://om.rs/roadmap . We try to update it weekly (excluding holidays). 
Once this epic is solved in the reference application, we should see if it's trivial to address this in the legacy UI as well. See TRUNK-1633