Primary mentor | |
Backup mentor | |
Assigned to |
| Table of Contents |
|---|
Abstract
| Excerpt |
|---|
Any self-respecting medical record (EMR) system needs to be able to track patient conditions (what is often called the patient's "Problem List"). We have chosen "Condition" instead of "Problem" to align with contemporary thinking (e.g., since "Pregnancy" isn't really a "Problem" for most people). OpenMRS RefApp needs Condition Lists. This functionality exists in Bahmni-style OpenMRS. What is a Condition List? It is a chronic condition which is important for all clinical care of the patient and lasts 3 months or more. Chronic conditions include NCDs (Diabetes, hypertension, epilepsy, depression, asthma, COPD, arthritis, etc), cancers, infectious diseases (HIV, Hepatitis), and pregnancy. This wiki page provides additional information. Initial development of this module was already completed (See here). This project must be completed before it can be used. There was a great start during the OMRS17 Hackathon in Malawi. This would be implemented by Partners In Health (Haiti and other locations) when MVP (minimum viable product) is completed and tested. Other implementations are bound to use this when version 1 is completed. |
...
- Complete all the minimal work so Condition List can be used in production RA-209
- Complete these tickets:
- RA-1458 Only allow current and past dates for conditions
- RA-1459 Onset and Inactive date should be displayed for inactive conditions
- RA-1461 Remove "History_of" functionality
- RA-1486 Configure list of valid condition lists for implementations
- EA-40 Condition List V1
- EA-51 Extend EncounterTransaction to include conditions during save
- RA-208 Allow some users to add Conditions directly from the Consult Note (extra checkbox in addition to primary/secondary and confirmed). Design/add to the consult note, so that conditions can be displayed or added directly on the same pages as diagnoses. (see attachment for Bahmni diagnoses/condition list page)
- Write a RefApp ConditionList report in MySQL or CohortBuilder
...
| Gliffy | ||||
|---|---|---|---|---|
|
Reports
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.
What is provided in the RefApp for reports. For example, Does the cohort builder (1 or 2) show anything from the condition list? (don't think so). What do other groups use to export data? Should it be an exported csv file? Should it be a webpage? Nothing appears here: https://demo.openmrs.org/openmrs/reportingui/reportsapp/home.page.
For Partners In Health implementations, there are a ton of reports. Many are written in MySQL and export data in csv format.