Hello @dkayiwa and @ball ,I am interested in working on the Condition List project. I have submitted 4 PR’s out of which 3 have been merged and 1 is waiting for code review. I am well familiar with Java,PHP,MySql,Android and web technologies like HTML,CSS,JS,Bootstrap, which would be of help in the project completion.I am as well trying to get familiar with the Spring framework. I would like to contribute more to this platform by solving more issues and also by taking up this project in GSOC 2019. I request you to provide me with the initial guidance and further information regarding the project. Thank you
I’m sorry for the late reply ma’am. Can i get details on how I can start contributing to this project.
@haripriya Thanks for your interest. As @ball has mentioned, get started by reviewing information about the project here https://wiki.openmrs.org/display/projects/Condition+List
@ball I request you to help me in getting a few points cleared. In the following wiki page https://wiki.openmrs.org/display/projects/Condition+List , in objectives the last point has etc , can i get details on the other objective which you are pointing to by that? I would also like to get more insight on Design Ideas section.
Also there is a null pointer exception being thrown by ConditionController.save() while trying to save the condition
Can you create a ticket for it? https://wiki.openmrs.org/display/docs/Tickets
@haripriya Thanks for reaching out. I’ve updated the wiki page and added/clarified additional objectives.
Thank you for the quick response Could you please help me get a clear picture of what this point " * Write a RefApp ConditionList report in MySQL or CohortBuilder" means ?
Okay I will
@haripriya Data In; Data Out. It’s helpful to a clinician to view/modify the patient’s condition list at point of care on the dashboard. It’s equally helpful for data analysts/scientists/M&E (monitoring and evaluation) to see a list of patients within a period of time with chronic conditions along with the condition.
I don’t know exactly what is provided in the RefApp for reports. For example, Does the cohort builder (1 or 2) show anything from the condition list? (I don’t think so). What do other groups use to export data? Should it be an exported csv file? Should it be a webpage? I don’t see anything here: https://demo.openmrs.org/openmrs/reportingui/reportsapp/home.page.
For Partners In Health implementations, we have a ton of reports. Many are written in MySQL and export data in csv format. For any GSoC intern, we’ll discuss and attack data out (reporting) after the point-of-care work is completed.
For a flavor of our reports, this screenshot shows the magnitude and variety:
Thank you for providing a better insight Trying to summarize, does it mean the objective of that point is to get a list of patients who exhibit certain conditions and get the result in a specified format by providing a new slot for conditions in the cohort builder UI? I checked the report module and the data is being exported in .xls format ,so should we be exporting in .xls format as well?
If it’s a full export, the user can sort/filter by condition. If you want to get fancy, you could include a condition as an input to the query.
This could include modifying the cohort builder for conditions.
It could be both of these tasks.
As long as non-propriety and free spreadsheets (LibreOffice and Google Drive spreadsheet) can import the file, xls or csv is fine.
@ball Could you please help me understand this ticket - https://issues.openmrs.org/browse/RA-1486 . I didn’t get why we are supposed to cut-short the autocomplete list when its always better to have more options to choose from. Could you explain giving an example.
The list of all CIEL diagnoses is huge (10,000+). Partners In Health doesn’t have all of these, but we want to limit to a smaller set of chronic care diseases (ie. HIV, diabetes, hypertension, etc.). Someone else in the community might want the whole list.
As an example, there are 80! diagnoses with HIV in the name. See this: https://www.openconceptlab.org/search/?conceptClass=Diagnosis&q=hiv
I would like to suggest a new feature for this project. I don’t think we are currently having an option to import conditions into the database using a .csv file. I feel there would be circumstances where clinicians would have data regarding the conditions in some .csv file. It would involve a lot of effort if the person had to enter each and every condition looking at the .csv file. To reduce this effort we can add functionality which would allow the user to directly import the csv file,from where the data is read and displayed. What is your opinion on this @ball and @dkayiwa ?