Hello, I am currently working with a group of friends to develop a medical data base for a local charity. We have decided that OpenMRS meets the needs that they require perfectly and it even has a pre-built skeleton for us to base our work on.
The following order of operation is what is planned for our project.
Work from the OpenMRS Standalone application.
Design the Standalone application to meet the needs that are required from the charity.
Create the necessary amount of admin and user accounts that the charity needs.
Transfer over patient information from their previous “database”.
Create some sort of instructions for the charity workers; this way they wont have to depend on us for any further development.
Concerns that we currently face:
Is it possible to develop what we intend through the standalone application entirely or would we have to develop through the core as well?
How can multiple people have access to the standalone application for the same database? In other words, how can I be working on the same standalone application while my group members work on different aspects for that same application?
Once we have developed and implemented everything that we desired and was required from the charity, would we need to transfer over to a server?
I’m not quite sure whether this would be the correct manner of approach for our intended plan, so any recommendations would be appreciated.
Stand alone is recommended for people exploring openmrs.I would encourage using the openmrs enterprise edition which looks more suitable for your case.You could simply make your customized modules than developing things at openmrs core.By the way,did you get a chance to look and have a feel of openmrs reference application,enterprise edition,if not kindly do so ie on the production section of ref app on this link
https://openmrs.org/download/
To access an openmrs instance using the same database,you simply need to be on the same network with the machine having openmrs.This then means using the ip address for example http://10.31.0.222:8080/openmrs.
Then simply make sure you use ip addresses on the same network with your running instance of openmrs for the different devices that you would need to access the system.
For this,do you have an estimate of the numbers of people who will be using the system?
Hello Herbert, thank you for the reply and clarifying some things up. To answer your question, the estimated amount of people that will be using this system will be 20 employees and 200-300 patients.
Just to clarify some statements you made:
What exactly is meant by making our customized modules and then developing on openmrs core?
-The way I’m understanding this is go through modules already created then select the ones that would be best fitting for us, then implement them. Just downloading them and placing them in the appropriate folder would implement them into the database, or will it depend for each specific feature the individual modules offer? Also when would you recommend working through the core?
*You also mention that you recommend us working through the enterprise edition rather than the standalone?
-Our intended plan of operation was familiarizing ourselves with the standalone application then learning through the wiki how to operate from there. We also saw a page on the wiki that guides on how to transfer the data base from the standalone to the enterprise. Would it be more beneficiary for us to begin directly from the enterprise edition?
And yes, I have taken the opportunity to run the reference application through the enterprise edition. Now that I think about it, we might be talking about the standalone and the enterprise edition synonymously. Either way, I have went through and it looks perfect for what we intend to create and use it for.