Application Name: Reference Application (via docker-compose)
I am from Germany and here in Germany we have a self organised non-profit group called “Medibüro” which helps people getting in touch with doctors for free. http://www.medibuero-hamburg.org/english
This is mostly, but not exclusively, used by refugees. Anyone who kinda fell through the cracks or hasn’t managed to gain a solid footing including papers and basic health care can come to us and we will try (and most of the time succeed) to find a doctor willing to help for free. No questions asked, no papers, no problem.
This has been going quite well since 1994. But well, everything is on paper. And when someone comes in we have to sift through old file cards to find a doctor that treats the problem of our client, speaks his/her language and hasn’t been annoyed by us too often lately.
I don’t want to get into too many details because then no one will read this. I’m sorry if I omitted too many details.
OpenMRS solves most of the problems the MediBüro has. One specific thing however is different from other OpenMRS use cases.
Every hospital usually has a very clear timetable. You have your doctors, nurses, clerks and the all have specific abilities and they all can enter their shifts and you can define how long what sort of appointment will take. So when a patient walks in, you search for someone treating problem X in some time-range and book an appointment without asking the provider.
In our case we need to search for a provider based on language and abilities, ranked by how many appointments they already have, whether they do it for free or need to be paid with our donations and whether they are reachable due to holidays and so on. And once we have found a suitable provider, we would call the medical practice, make an appointment and note it in the app. At least that’s the idea.
What I tried:
I tried to mingle in the provider add on but kinda broke everything. My best guess was to go through the “Provider Management Module” > “Manage Other Settings” and see if I can show a custom field such as “Language” from the person/provider but that didn’t work. I think the closest I got was a list of all possibilities via “Language:provider.attributes.firstElement”.
I tinkered a bit with the source code as well by adding an extra selectable option for “Set the person attribute type to include on the advanced search page” in the openmrs-module-providermanagement file “/omod/src/main/webapp/pages/manageOtherSettings.gsp” which worked in the UI but did not offer any search results.
I tried other similar stuff as well but sadly I did those things before an extended holiday so I can’t get too specific or technical without getting back into the code for a while and basically going though most of the trial and error pain again.
What I’d like to ask though is whether I’m on the right track at all? Should I try to extend the feature set of the provider module? Should I try to build something different with the HTML form editor? Should I aim at building a completely different add on? Is there some distribution already aiming at a problem similar to ours? Any general tips?
I hope I posted this in the right corner of the forum and managed to explain our goal and problem properly.
Kind regards Paul