Gjergj Sheldija wrote: > this is exactly my idea. Healthcare Information Systems (HIS) are complex systems.
The software used to support HIS tends to also get complex. Some proven ways to deal with complexity are: - code modularity; - dropping non core code from the core application (for instance, is the integrated content management system - the so-called cafe module - really needed? The ticket system?); - reduce support complexity, e.g., define a known, reliable, supporting environment like a well known set of reliable open source applications, runing over a reliable and also open source OS (for instance, Linux. Ubuntu Linux even coexists well with windows and OS X). - simplify DBMS to core connecting code. All code in these critical connections tend to introduce semantic mismatches and usually add minimal value to the project. > but this is going to be a decision that only all of us can make together. > just an example for the modules, how are they going to be installed and > managed ? > via xml files ? via db tables ? module repositories something like > JSR-170 ? It is only needed to see how very successful projects, like the non-HIS project Drupal <http://drupal.org/>, solved those very same problems. With the added interested of the needed code being open source, well maintained and freely available to be downloaded and included into the Care2x project. > as you see the decision cannot be taken from one person alone... In fact open source projects are sometimes compared to the pacemaker cells in the heart. Those beating faster and more predictably tend to lead the pack. Most of the time it is not a democratic process. People either don't care, or they manifest only to criticize. Successful Open Source projects defend themselves from this tendency by: - lowering people's expectations, i.e., by simplifying the project's main objectives (they purposely do not intend to be all things to all people) - focusing in security (use less code, always code with reliability and security in mind) and only introduce new features after fully debugging and stabilizing the existing code. Either way always ask yourself: "In what way will this code help the patient and how will it avoid any harm to that same patient?" M. ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
