|Feature||Description||Status||Point of Contact||Comments|
| || || || || |
|OCL subscription module |
Using KenyaEMR as a use case, create a tool for subscribing an OpenMRS instance to a dictionary (e.g. the CIEL dictionary)
Retrospective data entry
Basic support for retrospective data entry within the Reference Application
|Needs a user centric story - add to existing ticket|
|OpenMRS Web Framework|
Ranking REST tickets on 5 Aug design call.
Unknown User (burke) and Unknown User (darius) discussed 24-July-2015 and Darius will make a Talk topic to move this forward.
Bahmni technical deep dive scheduled for 4 June Developers Forum.
17 June design forum will discuss progress (coordinating various efforts). As well as look at how to make REST services more robust. Darius still working w/ Bahmni on fundamental pieces of their web framework to pull into OpenMRS (will talk about this on future call).
25 June dev forum on REST web services: how to substantially improve them W/ Burke Mamlin & Darius Jazayeri
OpenMRS has a lot of flexibility and extensibility with a central concept dictionary, RBAC, forms, reports, modules, and apps; however, it's not always easy to know which metadata goes with which functionality. The goal of vertical packaging is to define best practices for managing and relating all of the components (metadata & behavior) that work together to solve a particular problem within OpenMRS. Eventually, we envision a way that someone could easily add the MDRTB package to their OpenMRS implementation to begin treating MDRTB patients... or upgrade their Oncology package, etc.
Need to look at the design we had and see if we can get it in 2.3
Unknown User (burke) to share first draft of metadata mapping design on Talk.
First step will be to add ability to map metadata, 22 June design forum
Discussed on 20 May design forum.
Manage & view patient problems (e.g., on the patient dashboard and integrated with diagnosis capture)
see Condition List board
Daniel took a look at condition list to see what we need to do to get the API in 2.3 and believes if we do not get volunteers on admin sprint then condition list will not be ready.,
13 April WIP given on design call
1 June design forum to define how encounter diagnoses should work with conditions (and condition list).
Talked w/ Bahmni BA (Saranya) about use cases and requirements on 15 June design forum
|Basic Order Entry for meds and tests||Basic ordering of meds and tests "out of the box" in Reference Application.|
Ad Hoc Analysis tool (v1)
Incorporate new cohort definition tool.
|Concept Management Improvements||Allow for concept merging and easier browsing through concepts and references terms without losing frame of reference.|| || || |
Improvements to Permissions (technical implementation)
Avoid giving all API privileges to users
Needs discussion and design
Would like input from implementations, PIH (Mark, Mike, David) AMPATH, Kenya EMR, BAMI/JSS
Need to reach out for inputs!
Kiran has started helping with this
|Provider Management||Would include provider types and ability to retire the old provider management module. Will remove UI library module once provider management is in the core.|| || |