[med-svn] r5539 - trunk/community/papers/11_med-floss_luxemburg
Andreas Tille
tille at alioth.debian.org
Mon Dec 6 20:40:48 UTC 2010
Author: tille
Date: 2010-12-06 20:40:48 +0000 (Mon, 06 Dec 2010)
New Revision: 5539
Modified:
trunk/community/papers/11_med-floss_luxemburg/debian-med.bib
trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
Log:
Started to enhance paper
Modified: trunk/community/papers/11_med-floss_luxemburg/debian-med.bib
===================================================================
--- trunk/community/papers/11_med-floss_luxemburg/debian-med.bib 2010-12-06 12:08:18 UTC (rev 5538)
+++ trunk/community/papers/11_med-floss_luxemburg/debian-med.bib 2010-12-06 20:40:48 UTC (rev 5539)
@@ -275,3 +275,17 @@
YEAR="2008",
URL="http://www.gnumed.org/"
}
+
+ at ARTICLE{freediams:2010,
+ AUTHOR="Eric Maeker",
+ TITLE={{FreeDiams}},
+ YEAR="2010",
+ URL="http://www.freemedforms.com/"
+}
+
+ at ARTICLE{openmrs:2010,
+ AUTHOR="OpenMRS Developers",
+ TITLE={{OpenMRS}},
+ YEAR="2010",
+ URL="http://www.openmrs.org/"
+}
Modified: trunk/community/papers/11_med-floss_luxemburg/paper-text.tex
===================================================================
--- trunk/community/papers/11_med-floss_luxemburg/paper-text.tex 2010-12-06 12:08:18 UTC (rev 5538)
+++ trunk/community/papers/11_med-floss_luxemburg/paper-text.tex 2010-12-06 20:40:48 UTC (rev 5539)
@@ -71,14 +71,19 @@
The field of patient management and medical health record applications
which is considered by most people as the basic health care software.
Currently the only representative of this software which is
-included into Debian id GNUmed \cite{gnumed:2008}. It has turned out
+included into Debian is GNUmed \cite{gnumed:2008}. It has turned out
that there are a lot of similar Free Software projects that try to
solve more or less the same problem but diverge in the techniques used
(programming language, database server, etc.), user interface (GUI or
-web aplication) and the basic ideas about workflow and philosophy. It
+web application) and the basic ideas about work flow and philosophy. It
is planed to include those alternatives that fit Debian quality
standards and look promising regarding longevity of the project.
+In addition to GNUmed Debian has packaged the pharmaceutical drugs
+prescriptor and interactions checker FreeDiams \cite{freediams:2010}
+which can also run standalone or in connection with other medical
+health record applications.
+
The even larger task to manage a hospital is also tackled by several
projects and the most famous one OpenVista\cite{openvista:2008} as a
real enterprise grade health care information system is a really
@@ -87,41 +92,16 @@
used in OpenVista. To overcome this problem the strategy of
\DebianMed is to try to involve the upstream authors into the
packaging. This has happened in August 2009 and we are positive that
-we will see OpenVista in Debian sooner or later.
+we will see OpenVista in Debian at some point in time.
+Another application for hospital management is
+OpenMRS\cite{openmrs:2010} which is in preparation of being included
+into Debian and chances are good that this will be finished in the
+beginning of 2011.
-\section{Methods}
-\subsection{Unique technology supporting Debian's principles in packaging}
+\section{Principles of Free Software Distribution}
-\subsubsection{Build daemons}
-
-Sites external to the Debian main distribution may offer packages only
-for a subset of architectures. The Debian main distribution, however,
-automatically compiles software for all 13 architectures that are
-supported by the Debian effort. To get a package into Debian, be it
-novel or an update of an existing package, the maintainer of a package
-submits the source code of the program together with his changes on
-the code to create the package. The build daemons (or autobuilders)
-compile the packages for each of the supported systems and make the
-resulting package publicly available for download. Logs of the build
-platforms are available online for everybody's inspection.
-
-
-\subsubsection{Bug tracking system}
-
-Users should give immediate feedback about problems arising in using a
-package. They always have the choice of reporting these to the
-upstream developer, usually per email. A particular strength of
-\printurl{www.sourceforge.net}{SourceForget.net} is to bring users of
-a particular software together. Earlier than this effort was the
-\printurl{www.debian.org/Bugs}{Debian Bug Tracking System} (BTS). The
-maintainer of a software can decide if the bug should be forwarded to
-the upstream developers of the package or if it is fixed by
-himself. All problems are made public and hence the whole community
-may contribute to solving a particular issue.
-
-
\subsection{Sharing the work}
The Debian Project is an association of individuals who share the
@@ -159,6 +139,86 @@
they follow the rules of the policy). This is referred to as {\em
Do-o-cracy} in Debian which means: The doer decides what is done.
+\subsubsection{Active influence of small groups}
+
+This {\em Do-o-cracy} principle enables individuals or small groups to
+influence actively the support of certain work fields. While company
+driven Linux distributions somehow have to compete in market relevant
+fields with other distributors a pure community driven distribution
+which has no specific need to support basically mainstream software.
+Debian Med is actively profiting from this fact and is supporting a
+lot of applications which are very specific to medical care which are
+not contained in any large distribution.
+
+The advantage of plugging Free Medical Software directly into a large
+Linux distribution over creating a separate distribution with a
+specific focus on medical care will be discussed below.
+
+\subsection{Technological infrastructure of Debian}
+
+\subsubsection{Bug tracking system}
+
+Users should give immediate feedback about problems arising in using a
+package. They always have the choice of reporting these to the
+upstream developer, usually per email. A particular strength of
+\printurl{www.sourceforge.net}{SourceForget.net} is to bring users of
+a particular software together. Earlier than this effort was the
+\printurl{www.debian.org/Bugs}{Debian Bug Tracking System} (BTS). The
+maintainer of a software can decide if the bug should be forwarded to
+the upstream developers of the package or if it is fixed by
+himself. All problems are made public and hence the whole community
+may contribute to solving a particular issue.
+
+In the case of Free Medical Software the upstream projects frequently
+do not feature such a bug tracking system. Thus the inclusion of such
+software into Debian adds extra value to the project because users can
+report issues via the Debian BTS and the maintainer of the package
+works as proxy to contact the software authors. For the user this has
+the comfort of a consistent bug reporting interface and the software
+authors might get extra technical information provided by the Debian
+maintainer who is supposed to have decent technical knowledge.
+
+\subsubsection{Quality Assurance}
+
+To assure a constant quality Debian has several technical means which
+are for instance:
+
+\begin{description}
+ \item[Autobuilders] There are periodical tests to rebuild all
+ software which should be included in the future release. This
+ verifies compilation against recent build tools and might uncover
+ technical problems in the software. This is an additional check
+ to the build daemons mentioned below.
+ \item[Automated upgrade checks] Before a the a new version of Debian
+ will be released automatic tests are done where every single
+ package will be automatically installed into a clean stable system
+ of the last published Debian release and then the system will be
+ upgraded to the future stable release. This makes sure that new
+ Debian releases can be rolled out smoothly in release critical
+ applications.
+ \item[Package Installation and Deinstallation] The tool piuparts
+ tests that .deb packages (as used by Debian) handle installation,
+ upgrading, and removal correctly. It does this by creating a
+ minimal Debian installation in a chroot, and installing,
+ upgrading, and removing packages in that environment, and
+ comparing the state of the directory tree before and after.
+\end{description}
+
+\subsubsection{Build daemons}
+
+Sites external to the Debian main distribution may offer packages only
+for a subset of architectures. The Debian main distribution, however,
+automatically compiles software for all 13 architectures that are
+supported by the Debian effort. To get a package into Debian, be it
+novel or an update of an existing package, the maintainer of a package
+submits the source code of the program together with his changes on
+the code to create the package. The build daemons (or autobuilders)
+compile the packages for each of the supported systems and make the
+resulting package publicly available for download. Logs of the build
+platforms are available online for everybody's inspection.
+
+
+
\subsection{Selection of packages}
Debian contains more than 20000 binary packages, and this number is
More information about the debian-med-commit
mailing list