Primary mentor | |
Backup mentor | Ellen Ball |
Assigned to |
Abstract
| Excerpt |
|---|
OpenMRS RefApp needs Condition Lists. 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. |
Dev Resources
- GitHub : https://github.com/openmrs/openmrs-module-locationbasedaccess
- JIRA : https://issues.openmrs.org/projects/LBAC/issues
Requirements
- Good Java, Spring and JavaScript skills
- Soft skills to interact with the community in order to gather requirements and technical feedback
Skills Needed
- Java
- Spring
- JavaScript
- HTML/CSS
- MySQL
Objectives-2
- 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
- Create a dashboard for LBAC module - Prefer to go for a react OWA.
- Create a OWA page to show/edit the configurations of LBAC through the REST endpoint.
- Create a OWA page with required functions for patient migrations from one location(or unknown) to another location.
Resources
- Download the Location Based Access Control v0.1.1
- Deployment Steps
- Project GitHub Link
- Project JIRA Link
- Final Report : GSoC 2018 - Location Based Access Control
- OpenMRS AOP
- Location-Based Login
- OpenMRS SDK
- Program Location Module
- Security and Access Control
- Notes from 2014-09-29 Design Forum
- Notes from 2014-09-24 Design Forum
- Notes from 2015-06-01 Design Forum
- Notes from 2015-06-15 Design Forum
Background
Any self-respecting medical record 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).
...
- 0-to-n Conditions associated with an Encounter
| Gliffy | ||
|---|---|---|
|
See Also
- Notes from 2014-09-29 Design Forum
- Notes from 2014-09-24 Design Forum
- Notes from 2015-06-01 Design Forum
- Notes from 2015-06-15 Design Forum
|