Difference between revisions of "Open source openemr"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| Line 36: | Line 36: | ||
::::*Forum discussion of how to streamline this decision for users is here: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/4832281 | ::::*Forum discussion of how to streamline this decision for users is here: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/4832281 | ||
==Show | ==Show examples of clinics that successfully use the product== | ||
:*Place reviews on sourceforge at http://sourceforge.net/projects/openemr/reviews/ | :*Place reviews on sourceforge at http://sourceforge.net/projects/openemr/reviews/ | ||
:*More detailed entries will be placed on the [[Success Stories]] wiki page | :*More detailed entries will be placed on the [[Success Stories]] wiki page | ||
Revision as of 21:24, 26 November 2011
Overview
Articles to convince users why open source emrs are better than proprietary emrs by:
- 1) defining open source software
- 2) describing why open source EMR's are better than proprietary EMR's
- 3) describing how to find a vendor/support
- 4) showing examples of OpenEMR working in practices.
Define open source software and describe why open source EMR's are better than proprietary EMR's.
- This subject is discussed on the following pages/websites:
- Specifically, the 'What is Open Source' and 'Why use an Open Source EMR' sections.
- This will always be a work in progress. For any input, please post in any of the OpenEMR Forums.
- This is a work in progress and is actively discussed in the following OEMR organization forum here: http://www.oemr.org/phpBB3/viewtopic.php?f=2&t=22
- This is a work in progress and is actively discussed in the following OEMR organization forum here: http://www.oemr.org/phpBB3/viewtopic.php?f=2&t=22
Discuss how to choose vendor/support
- Looking through the Commercial Support web page is an option.
- Main issue is how do new users know which one to choose.
- Asking for recommendations is likely a more effective option. For example, emailing (or even posting on sourceforge to keep open) what a user is looking for, which is then followed by recommendations from the community.
- Main issue is potential for bias and conflict of interest.
- Also the issue of getting the code into the official codebase
- Discuss the merits of this, for example:
- Then the new feature will continue to be supported into the future.
- Then the new feature may be improved by others in the future.
- New features in the future won't break the original feature.
- Giving back to the community that provided you with free EMR software.
- Discuss how this will effect the choice of a vendor.
- Should seek a vendor whom has demonstrated ability to get new features into the codebase.
- Check for their activity on the forums.
- Check their commit activity: http://github.com/openemr/openemr/commits/master
- Ask the vendor how active they are on the forums and how many features/commits they have contributed to the official codebase.
- Ask for recommendations from others in the community.
- Forum discussion of how to streamline this decision for users is here: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/4832281
Show examples of clinics that successfully use the product
- Place reviews on sourceforge at http://sourceforge.net/projects/openemr/reviews/
- More detailed entries will be placed on the Success Stories wiki page
