--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
To unsubscribe from this group and stop receiving emails from it, send an email to implementers...@openmrs.org.
--
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implem...@openmrs.org
Unsubscribe: implementers...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
To unsubscribe from this group and stop receiving emails from it, send an email to implementers...@openmrs.org.
Hi Alex,
We've tried using both OpenMRS and building systems from scratch for similar projects and recently decided that wherever possible we're going to use OpenMRS. We found ourselves reinventing the wheel a lot and having to build customised applications from scratch for different projects is very time consuming. For us, the major pros of using OpenMRS are the flexibility that it allows, and that it saves us development time when we need to get something running. Some folks running small clinics may find OpenMRS to be overkill. In my experience, while that may be true in the initial phases, as those implementations grow in scope and complexity, one often starts to need the functionality that OpenMRS provides.
Having said the above, I think the decision needs to be made in the context of your requirements and whether or not OpenMRS meets your specific needs (or can be configured/customised to meet them in the time that you have)
Ali
Running OpenMRS on a desktop can work fine for a small clinic. As Steven pointed out, we run KenyaEMR on an HP desktop, and in Vietnam we are beginning to run them on small mac mini servers (quite powerful, but low priced, more energy efficient, and small in physical size). We run OpenMRS in virtual machines with VirtualBox hosting rather than on the host machine directly, and there are definitely some advantages to that. I’d be glad to talk more about that if you are interested.
I also would suggest making sure you have an external encrypted backup for your data (such as on an external drive or USB stick or such) though in case of hardware failure.
- Jan
Hi Alex.
I agree with the ideas and awesome responses from the team.
Just to ask which platform do you intend to run it on?
Wycliffe
Hey Alvin,
A quick list of advantages for a VM are:
· Known Environment: A VM provides a known environment in which to run your system. We found in implementations on bare metal that many times the environment had changed over the course of time (other systems loaded, configuration settings changed, security changed, hardware changes, etc) that caused problems running the system. By putting the system onto a VM, we could control what that environment was, what co-existed on the environment, and what happened to it easier. The long-term goal would be to renew that environment completely during upgrades, but we are still working on that.
· Hardware Changes: Changing / Upgrading hardware is simplified as you merely need to export your VM and move it to the new machine. I just upgraded mac mini servers in the OpenELIS implementations in Cote d’Ivoire and it greatly simplified the process. It was much easier for the system administrators I am mentoring there as well.
· Backups and Restores: you can take snapshots of the entire VM, rather than just backing up data, making restores simpler for problems during upgrades and such. This doesn’t mean you shouldn’t backup the data itself regularly though…
· Simplified Installation: Many times we find there isn’t the capacity at the sites to do installations from scratch, which can be complicated. By supplying a VM appliance, installation can be performed by a more advanced SA and deployed in places where they can just learn to manage the VM and its host.
· Reduced Hardware Costs: You can run multiple software on the server without conflicts since each one can be isolated in it’s own VM, so you can maximize your use of the same pieces of hardware. For example, having OpenELIS on one VM and OpenMRS on another VM – if one of the VMs needs to be restarted, it doesn’t affect the other system.
Just my two cents. I’m sure there would be some counter arguments to these, and there are some disadvantages – like you pointed out that some resources are used by the host.
Jan
From: Alvin B. Marcelo [mailto:alvin....@gmail.com]
Sent: Tuesday, October 22, 2013 4:46 PM
To: Jan Flowers
Subject: Fw: Can I use a desktop as my server?
Jan,
What are the pros and cons of running the OMRS server as a guest host on the Mac OSX VirtualBox?
Doesn't it 'eat' resources (eg, the osx) that could be maximally allocated fully to Linux?
Eager to learn,
Alvin
Sent from my BB Curve 9320
From: Jan Flowers <jfl...@uw.edu>
Sender: implem...@openmrs.org
Date: Tue, 22 Oct 2013 16:29:44 +0000
Subject: RE: Can I use a desktop as my server?
Running OpenMRS on a desktop can work fine for a small clinic. As Steven pointed out, we run KenyaEMR on an HP desktop, and in Vietnam we are beginning to run them on small mac mini servers (quite powerful, but low priced, more energy efficient, and small in physical size). We run OpenMRS in virtual machines with VirtualBox hosting rather than on the host machine directly, and there are definitely some advantages to that. I’d be glad to talk more about that if you are interested.
I also would suggest making sure you have an external encrypted backup for your data (such as on an external drive or USB stick or such) though in case of hardware failure.
- Jan
From: implem...@openmrs.org [mailto:implem...@openmrs.org] On Behalf Of Alex Ocampo
Sent: Tuesday, October 22, 2013 8:25 AM
To: implem...@openmrs.org
Subject: Re: Can I use a desktop as my server?
Thank you all!
Good work Alex.
For any challenges keep us posted
Thats to the point. Also with time be thinking of using unix or linux platform because of its stability.
Regards
Hi Alex,Yeah, from my experience, transition period from Windows to Linux (especially Ubuntu) is quite low . But i have only limited amount of experience in Unix.
On Fri, Oct 25, 2013 at 12:46 PM, Alex Ocampo <alexoc...@gmail.com> wrote:Sorry for my platform illiteracy, but why is Linux or unix more stable? Is it easy to transition a windows operating system to linux?AlexOn Thu, Oct 24, 2013 at 3:24 PM, wycs Nyachiro <georg...@gmail.com> wrote:Thats to the point. Also with time be thinking of using unix or linux platform because of its stability.
Regards
On Oct 24, 2013 4:58 PM, "Alex Ocampo" <alexoc...@gmail.com> wrote:Hi Wycs-Thanks so much. Also to answer your question about the platform. I'm not sure if this is what you mean but we are running it on Windows. We are looking at doing point of care data entry and have touchscreen devices to deploy in each of our consulting rooms and in our clinical lab.Does that answer your question?AlexOn Thu, Oct 24, 2013 at 1:52 PM, wycs Nyachiro <georg...@gmail.com> wrote:
Good work Alex.
For any challenges keep us posted
On Oct 24, 2013 2:33 PM, "Alex Ocampo" <alexoc...@gmail.com> wrote:Just want to say THANK YOU to everyone for your help and advice. Our clinic has downloaded the enterprise version and are in the process of customizing OpenMRS so we can implement it in our clinic.THANKS!!
Alex Ocampo (Ghana)On Wed, Oct 23, 2013 at 12:12 AM, Jan Flowers <jfl...@uw.edu> wrote:Hey Alvin,
A quick list of advantages for a VM are:
·
Shangeetha Sivasothy,
Undergraduate,Department of Electronics and Telecommunication Engineering,University of Moratuwa
--
--
To unsubscribe from this group and stop receiving emails from it, send an email to implementers...@openmrs.org.
+1 for your idea about the matrix to compare real use cases of current implementations.
Would we put it on this page? If so, I’d be glad to add Vietnam’s and Mozambique’s implementation setup.
Jan
You could get some real use case examples here…
https://wiki.openmrs.org/display/docs/OpenMRS+Implementation+Survey+2012
Could the Tomcat allocated system memory be something that gets reported “automatically” via the Atlas module?
James
Thanks! I added a link to the specifications page for quick access for people.