Also paste the contents of /var/www/bahmni_config/.
We don’t have the appointment module as a service. That is why it is giving unrecognized service.
What version of Bahmni have you installed?
We checked this with Himabindu and the conclusion is that there is “a compatibility issue with the omod version and bahmni version…”
The question is how to fix it?
Do we have anywhere a DEMO of the Appointments module that I could see it in function?
Gurpreet has edited the Appointment Module page with the findings:
“KNOWN ISSUE It
seems Appointment Module is not running on Bahmni v0.82 due to an omod
incompatibility. We will work to resolve this issue soon. If you are
interested in helping out, please let us know. This issue can be tracked
in Mingle here: #2008”
I just copy-pasted the above here that it can be linked, who ever looks at it that it relates to the same issue of omod incompatibility and the current Bahmni version 0.82.
Hello,
I was looking this homepage linkage too because it is indeed a bit illogical. I’ve tried to change the openMRS module itself to give another path for the icon.
I’ve edited the file home.gsp (/opt/openmrs/openmrs/WEB-INF/view/module/appointmentschedulingui/pages/)
by replacing this line
{ icon: “icon-home”, link: ‘/’ + OPENMRS_CONTEXT_PATH + ‘/index.htm’ },
with
{ icon: “icon-home”, link: ‘/home’ },
After that I also restarted the openmrs service with the command
sudo service openmrs restart
But I do not see any effect. The link is still the same.
I know that this type of changes would need to be done again after possible upgrade or module updates but it is not very usable like this either. We need to get a Bahmni homepage link there.
Assuming that when running Bahmni we do not (ever) want to see the regular OpenMRS homepage, then we could add something like this to the Bahmni core module:
Thanks, Darius!
I’ll have a look at that. Although I think we should anyhow be able to reach the openMRS page for administrative settings, not to get re-directed in case we really need to go there.
Back to the core ideas of Appointments module. I was previously testing Appointments module on the side of OpenMRS and also viewed this video:
As we can see in that video, the time slots are creating one hour blocks for the system (in the video minutes 20:30). Anyhow Bahmni seems not respecting those slots. I created a provider having ONE hour slots for few days between 9am and 3pm. When I was booking an appointment for a test patient, it selected the whole day as an appointment time! It definitely should not work like that.
Another thing is that I can’t understand how a registration clerk can easily see the daily program, all the appointments for the day of for the whole week? You can see if you search for a patient but maybe you do not even remember what patients you have and it doesn’t give you the whole picture anyhow.
We have been asked to poke around in the context of a new upcoming implementation for a private clinic. One of the important features that they are looking for is the scheduling of patients appointments.
I see that the appointment scheduling Trello card is ‘under consideration’, is there any more visibility on this?
If not, can we assume that you will leverage the existing Appointment Scheduling and Appointment Scheduling UI modules? This would allow us to make those work within Bahmni (as described above in this thread) until a fully fledged appointment scheduling feature is eventually rolled out by the Bahmni team.
@mksd, my best guess is that we’ll end up using the REST API of the appointment scheduling module, but reworking the UI.
So, if you were to start today using the appointmentscheduling API and UI from the reference application, you’ll probably have a straightforward migration path. (But this is not guarantee!)
(Would you have some time/capacity to collaborate on this, if it would get things moving faster? Or is this just a “see what’s there already” situation?)
We haven’t started working on development of Appointment Scheduling module. If you can give inputs on your requirements that will be helpful.
Currently the requirements we are seeing might be around booking an Appointment for
a) A Patient, and
b) A resource (like a procedure room), and
c) A provider, and
d) A service (like for physiotherapy, etc)
The idea being – that one may want to create an appointment for an OT with the above — and we will need to ensure that some provider/room is not double booked. Discussions are in progress.
In another hospital the requirement is much more simpler… as mentioned in this trello card: Here the original requirement was just about scheduling a patient for a particular “service” on a particular day. This should be possible based on the criteria mentioned above, as long as other factors can be set to optional.
What requirements are you hoping for?
We haven’t yet decided if we will enhance the existing OpenMRS module, or write a new one. It will depend on the requirements and discussion with customers and OpenMRS Team.
This is a real requirement from… a still potential client. Should they want to move forward with Bahmni we will have to deliver something quick and we will certainly be willing to collaborate on getting the ‘final’ feature out.
I would say that the probability that things go through is > 75%, to settle ideas.
Deliver something quick means that we will have to start with Appointment Scheduling UI, that seems to be the only way to go at this juncture. We understand that the UI will change as long as we are not taken into backward compatibility issues later on. Especially around the transition between the old and the new UI.
@gsluthra , thanks for your detailed post.
We don’t know yet but we have some room for manoeuvre. This client intends to trial Bahmni on a small (and kind of autonomous) part of its facility at first. For this early trial phase they will be ok with starting with Appointment Scheduling UI, and while using it they will certainly come up with ideas to improve the appointment scheduling experience. As soon as possible we will then provide feedback on the Trello card.
Your suggestion seems to be more feature full than what they have discussed so far, but again, we will submit your current design idea and see what they think about it.
Are you going to update the Trello card with the latest status of the requirements?
ERROR - ModuleFactory.startModule(627) |2017-07-07 00:09:33,070| Module Appointment Scheduling Module cannot be started because it requires the following module(s): reporting 0.9.2 Please install and start these modules first.
INFO - LoggingAdvice.invoke(116) |2017-07-07 00:09:33,094| In method AlertService.saveAlert. Arguments: Alert=Alert: #null,
INFO - LoggingAdvice.invoke(156) |2017-07-07 00:09:33,142| Exiting method saveAlert
ERROR - ModuleFactory.startModule(627) |2017-07-07 00:10:00,651| Module Appointment Scheduling Module cannot be started because it requires the following module(s): reporting 0.9.2 Please install and start these modules first.
INFO - LoggingAdvice.invoke(116) |2017-07-07 00:10:00,679| In method AlertService.saveAlert. Arguments: Alert=Alert: #null,
INFO - LoggingAdvice.invoke(156) |2017-07-07 00:10:00,707| Exiting method saveAlert
ERROR - ModuleFactory.startModule(627) |2017-07-07 00:10:00,757| Module App UI Module cannot be started because it requires the following module(s): uicommons ${uicommonsModuleVersion}, uiframework 2.5.2, appframework 2.0 Please install and start these modules first.
INFO - LoggingAdvice.invoke(116) |2017-07-07 00:10:00,762| In method AlertService.saveAlert. Arguments: Alert=Alert: #null,
INFO - LoggingAdvice.invoke(156) |2017-07-07 00:10:00,766| Exiting method saveAlert
ERROR - ModuleFactory.startModule(627) |2017-07-07 00:10:00,790| Module Appointment Scheduling UI Module cannot be started because it requires the following module(s): uicommons 2.1, uiframework 3.9, appframework 2.9, appointmentscheduling ${appointmentSchedulingVersion}, appui, coreapps 1.11.1, emrapi, reporting Please install and start these modules first.
INFO - LoggingAdvice.invoke(116) |2017-07-07 00:10:00,798| In method AlertService.saveAlert. Arguments: Alert=Alert: #null,
INFO - LoggingAdvice.invoke(156) |2017-07-07 00:10:00,802| Exiting method saveAlert
ERROR - ModuleFactory.startModule(627) |2017-07-07 00:10:27,333| Module App UI Module cannot be started because it requires the following module(s): uicommons ${uicommonsModuleVersion}, uiframework 2.5.2, appframework 2.0 Please install and start these modules first.
INFO - LoggingAdvice.invoke(116) |2017-07-07 00:10:27,345| In method AlertService.saveAlert. Arguments: Alert=Alert: #null,
INFO - LoggingAdvice.invoke(156) |2017-07-07 00:10:27,385| Exiting method saveAlert
I have installed Bahmni and wanted to go through it about how it is working.
As far as I know it is an EMR that combines the openmrs as Backend and openerp for the inventory and others.
But I am not able to get the directory or path to customize the actual openmrs backend code so that I can see the changes.
Can I not customize the backend code in Bahmni? Or is there anything that I am missing or need to do for coding with java and mysql in openmrs within Bahmni?
Sam,
I think you will need to setup the development environment to have the full bahmni code to edit and customize. There are a lot of things you can customize using the JSON files in
/opt/bahmni-web/etc/bahmni_config
I saw on your other post that you already found the wiki page that describes setting up the dev environment:
Just out of curiosity, what are you trying to customize for your setting? I’m also starting to customize my implementation, and learning a lot. Maybe we can make some noise and get the developers to help us along.
Hello,
I am having a problem that lately showed up, The appointment module when I go to Appointments scheduling > appointment list, the records there do not match the ones generated in the excel sheet from Reports > Appointment Details. I can not figure out where the problem is while it was working perfectly fine a month or 2 ago.
Can you provide some more details – for instance in Reports – there might be some SQL configuration which says what query is being fired. This will be in UI’s config-folder/openmrs/apps/reports/report.json.
You can check that SQL in DB and compare it to what Appointments screen is showing.