Help me on this … I have multiple clients who wants to use the openEMR application hosted on my server. Is there anyway that using a single instance of the code and database I can segregate their data. Is there any build in feature of openEMR which will led me do this easily. Please suggest the best way to accomplish this task.
multiple clients sharing the same installation sounds like a maintenance headache to me. It might be better to have a separate installation for each client and setup virtual hosts in your web server.
Right, OpenEMR does not support that currently. The general rule is, unless you want the installations sharing the same patient data, the databases should be separate.
I hate to differ, but it’s not too complicated to do this in Unix or in OpenEMR, and it’s easier than maintaining multiple separate source bases when everyone is using the same base version. Bug fixes only have to be applied one time, for instance. We have developed the tools to automate the database and http configuration processes. It does require a solid understanding of symbolic linking, Apache SSL and SQL database administration.
Thanks everyone for your suggestions. Yes, I think that separate databases is the easiest way to go ahead but in my case the #clients are not fixed. Creating databases dynamically is not a big deal… but can lead me to troubles if numbers increases out of my expectations… What about changing the database schema to accommodate company id in order to segregate the company’s data. If anybody has already worked on similar changes, please suggest what are the areas I need to take care of ….