I’m using the following as a part of my OpenMRS development environment:
OpenMRS platform 1.11.4
Reference application 2.3 (with those 36 modules that came along)
My requirement is that I want to go multi-tenant with the current implementation on hand. Here’re my points in support of that:
Requirements of new system:
A multi-tenant system with 1 server, 1 database and multiple tenant architecture
Keeping the data for each account/clinic isolated (no clinic can view patients from other clinic)
Single application instance making clinic attach/detach easy and time saving
Multiple branches/sites of the same clinic/hospital operating from different geographic locations able to share patient information among themselves
Drawbacks of current system:
Running single instance on one machine isn’t a good idea (we cannot afford to setup a server for every instance we offer to a clinic/health-center)
Running multiple instances of OpenMRS on single machine using multiple tomcat containers isn’t a good idea (we’ll need a server with very high capabilities and maintaining database also become tedious)
Can anyone help me in guiding if/how I can manage to achieve the above requirements.
Also, I wanted to know if OpenMRS team is working in the direction of making the system multi-tenant.
Work with @themoonraker13 to find a time on a Design Call, and we can try to make sure that our core developers such as @darius and @wyclif are in attendance. You can then describe your requirements to them in detail and they can help you design a solution.
Hello to everyone,
I’m new in the OpenMrs and I wan’t to know if this program is what I need.
For the moment I found, in OpenMRS, all the services I need, but not that one in the title .
So, in OpenMrs how to allow a doctor to view only their patients?
hi @wyclif, i intend to limit the doctors to view all the patient’s record.
BTW i solved this problem using the Sync.mod.
I put an istance of the program in the main server and I used it like the father, this istance doesn’t share his data with the others istance of the program, later on I created one istance for every clinics. Every istance of the program has his own DB and share his own data with the main istance of the program.
Probably it’s not the best way to do this but I don’t have enough time and in this way everything it’s working.
Thanks for everything
@themoonraker13 interesting problem - the project that I am working with is trying to solve the problem from the opposite direction, there are individual installations (currently in the hundreds soon to be over a thousand). Each installation is based at a facility (no guarantee of a consistent Internet connection), and is at the same version (OpenMRS, HTML forms and concepts) - but there is a need to bring the patient records (or extracts) together to a central database.
Here site level users and metadata are not synced, neither are concepts and forms (as they are expected to be similar). So I am hoping to pick ideas from the conference using the Sync Module, manual export/import (with encryption to protect PII during transfer) etc.
The merged data (father instance) would be read-only, with an anonymised and de-identified dump used reporting and analysis purposes.
it seems that this still didn’t get on the calendar. Do you want to go ahead and pick a date to get this rolling? I can only do anytime after the 15th of Jan, but don’t mind me, you’re welcome to go ahead and organize the call without me
Support for multi-tenant hosting is something that we (Banda Health) are actively pursuing as well and I’m glad to see that this is coming back up again. Our requirements are a bit different than @themoonraker13’s in that we would “only” need multi-tenant support for the REST and data access calls but not in the UI or much of the RefApp. Perhaps this reduced scope might be a good starting point for full multi-tenant support?
Can we revive the possibility of getting this on an upcoming design call and is the any interest from others to discuss this beyond @angshuonline?