The goal of GSoC is to give students an excellent experience in open source development, leading them to become lifelong productive open source coders. In return for investing in mentorship, OpenMRS has been blessed with many incredible returns on this investment! Some of it has been in code, but the best has been people: @nyoman, @surangak, @maany, @raff, @k.joseph, @jordan, @maurya, @harsha89, @bholagabbar, and @ivange94 to name just a few.
As we have for the past decade, we want to put together an awesome list of mentors & projects for GSoC this year to attract the best students into long-lasting open-source careers while writing code & saving lives with OpenMRS!
GSoC projects can be new modules/projects or involve enhancements or new features for an existing module/project.
Attributes of a great GSoC project
Must involve coding and be OpenMRS-related
Clear objectives
A minimal viable product can be completed in 6-8 weeks(allowing time for bug fixing, documentation, and getting to production).
Meaningful contributions to the community
Involvement of at least one motivated product owner (e.g., implementation) eager to use the projectās output
Do you have ideas for potential GSoC projects? Please let us know.
Letās get the discussions going. Our goal is to have many projects fleshed out as gsoc2017-labeled project pages by 9 Feb.
Mentors (thus far, add your name here if you can mentor)
Use Googleās TensorFlow to determine if a cancer tumor is benign or malign (very simple ML application)
Add xyz feature to Patient Dashboard in the reference application. (@ssmusoke should fill in which feature!)
Support standard model for recording āMedication Dispensedā in the EMR API module (or in its own new module): introduce a standard way to record that drugs were dispensed to the patient, storing this as obs. Provide REST and FHIR APIs for this. Add (simple) support for this in the reference application.
we are thinking this yearās GSoC prototyping on a generic cross over reporting tool/platform for all default and userās additional metrics within reporting periods such as; monthly, quarterly, daily, annually etc into DHIS and any other future similar softwares we wish to communicate to, i hope to propose this project preferably next week
OCL Subscription module should support concept attributes
@raff are there other things weād put together with this in an āOCL Subscription module improvementsā project? (@raff: no more improvements needed at the moment, concept attributes alone is not enough for a GSoC project)
Use Googleās TensorFlow to determine if a cancer tumor is benign or malign (very simple ML application).
The problem is that TensorFlow is C++ and its API is Python, therefore itās not well suited as a module.
Iāll share some quick thoughts. Clearly these are not full proposals, and someone would need to flesh them out, and mentor them.
FHIR module improvements. I donāt know enough about the current state to know what we should prioritize, but I imagine we could implement some more resources. We could also update it from DSTU2 to STU3 (assuming this is released as expected before June).
Open Concept Lab improvements: the python/django OCL application needs a lot of improvements, both cosmetic and functional. I would imagine @paynejd as mentor with @ball as backup mentor.
Add xyz feature to Patient Dashboard in the reference application. (@ssmusoke should fill in which feature!)
Built-In Reports for the Reference Application (packaged as an OMOD+OWA so they can be used elsewhere too). Hardcoded reports, graphs, etc to give some basic insight into your data, e.g. listing all patients seen today, broken down by demographics, place of origin (based on address), encounter types, encounter locations, diagnoses, etc.
Support Medication Dispensing in the EMR API module (or in its own new module): introduce a standard way to record that drugs were dispensed to the patient, storing this as obs. Provide REST and FHIR APIs for this. Add (simple) support for this in the reference application.
Platform support for Anonymous Patients, i.e. āJohn Doeā patients admitted to emergency who need a temporary patient record until they can be identified.
Improvements to the OpenMRS Add-On Index. (Iād expect to have this live before GSoC starts, and there will surely be improvements worth making at that point, but I donāt know what yet.) I donāt know if I can commit to mentoring though.
we are thinking this yearās GSoC prototyping on a generic cross over reporting tool/platform for all default and userās additional metrics within reporting periods such as; monthly, quarterly, daily, annually etc into DHIS and any other future similar softwares we wish to communicate to, i hope to propose this project preferably next week
@dkayiwa I am afraid the last couple of weeks have been taken up with other hospital projects: Payroll/HR/accounting and so not got around to this. Are you referring to the workflow and queue management proposal?
