Difference between revisions of "Open source openemr"

From OpenEMR Project Wiki
Line 18: Line 18:
:*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.
:*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.
::*Main issue is potential for bias.
:*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.


==Show example of clinics that successfully use the product==
==Show example of clinics that successfully use the product==

Revision as of 19:05, 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 and 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.

Discuss how to choose vendor/support

  • 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.
  • 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.

Show example of clinics that successfully use the product