Versions Compared

Version Old Version 6 New Version 7
Changes made by

Ellen Ball

Ellen Ball

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Primary mentor

Daniel Kayiwa

Backup mentor

Ellen Ball

Assigned to


...

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.   

Initial development of this module was already completed (See here).  This project must be completed before it can be used, but many features are already completed.  There was a great start during OMRS17 Hackathon in Malawi.Initial development of this module was already completed (See here), and now it needs some further improvements as mentioned in the objectives

This would be implemented by Partners In Health (Haiti and other locations) when MVP (minimum viable product) is completed and tested.

Dev Resources

...

  • Java
  • Spring
  • JavaScript
  • HTML/CSS
  • MySQL

Objectives

...

  • Automating the LABC module installation, need to reduce the workload at the beginning of a user.
  • Create a REST endpoint to show/edit the configurations of LBAC 
    • Create Person Attributes for LBAC.
    • Global Property attribute for LBAC.
    • Check and show about the required module’s versions to use a feature from LBAC.
    • Login Screen managements.
    • LBAC On/OFF feature.
    • Migrate a patient/list of patients from one location(or unknown) to another location.
  • Enable encounter access based on patient location or multiple admitted/channeled locations.
  • Add location restrictions to Reporting-REST, and Reference metadata modules.

Extra Credit

  • Write a report for users about Condition ListsComplete all the minimal work so Condition List can be used in production RA-209
    • 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 
    • etc.

Extra Credit

  • Write a RefApp ConditionList report in MySQL or CohortBuilder
  • RA-208 Allow some users to add Conditions directly from the Consult Note (extra checkbox in addition to primary/secondary and confirmed)

Resources

...