LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2004-03-29 13:09:54 +00:00
parent ecaa34d55a
commit d0e543cdbe
3 changed files with 151 additions and 163 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
View File

@ -2755,7 +2755,7 @@ the <ULINK URL="../IP-Masquerade-HOWTO/index.html">IP-Masquerade-HOWTO</ULink>.
Medicine-HOWTO</ULink>,
<CiteTitle>Linux Medicine-HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: Jul 2003</CiteTitle>.
<CiteTitle>Updated: Mar 2004</CiteTitle>.
Some pointers to Linux software (mostly GPLed) for the
medical sciences. </Para>
</ListItem>

2
LDP/howto/docbook/HOWTO-INDEX/miscSect.sgml
View File

@ -385,7 +385,7 @@ Use Linux to control your home electrical devices. </Para>
Medicine-HOWTO</ULink>,
<CiteTitle>Linux Medicine-HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: Jul 2003</CiteTitle>.
<CiteTitle>Updated: Mar 2004</CiteTitle>.
Some pointers to Linux software (mostly GPLed) for the
medical sciences. </Para>
</ListItem>

310
LDP/howto/docbook/Medicine-HOWTO.sgml
View File

@ -3,6 +3,14 @@
<articleinfo>
<title>Linux Medicine-HOWTO</title>
<author>
<firstname>Walt</firstname>
<surname>Pennington</surname>
<affiliation>
<address>wpennington@pennfirm.com</address>
</affiliation>
</author>
<author>
<firstname>Gerardo</firstname>
<surname>Arnaez</surname>
@ -21,7 +29,6 @@
</affiliation>
</author>
<author>
<firstname>Werner</firstname>
<surname>Heuser</surname>
@ -33,6 +40,12 @@
</author>
<revhistory>
<revision>
<revnumber>2.3</revnumber>
<date>2004-03-24</date>
<authorinitials>gea</authorinitials>
<revremark>Slight updates</revremark>
</revision>
<revision>
<revnumber>2.2</revnumber>
<date>2003-07-11</date>
@ -78,7 +91,6 @@
<revremark>There are too many projects. There are much better sites for information. This document will change its focus and be more of a stable document and pointing to active sites with better and more up-to-date information. This document is not intended to be complete, and parts of it will seem out of place in its new function.</revremark>
</revision>
<revision>
<revnumber>2.0.5</revnumber>
<date>2002-07-26</date>
@ -86,7 +98,6 @@
<revremark>Added in OpenEMR. I also need to add back in the german sections, but will need help on it.</revremark>
</revision>
<revision>
<revnumber>2.0.4</revnumber>
<date>2002-04-06</date>
@ -94,9 +105,6 @@
<revremark>Added Kpumpe and OIO library info</revremark>
</revision>
<revision>
<revnumber>2.0.3</revnumber>
<date>2002-03-02</date>
@ -305,8 +313,7 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<sect2>
<title>DEBIAN-MED HOMEPAGE</title>
<para>A better place to look for medical information is <ulink url=" http://auric.debian.org/~tille/debian-med/">Debian-Med</ulink> which is already better organized than this page. You should look here first, then come here, as I think the focus of this How-To will eventually be a How-to install working applications that I think is useful and actually useful.
</para>
<para>One location to find information on medical projects is <ulink url="http://www.debian.org/devel/debian-med/">Debian-Med</ulink>. Debian-Med has a very nice listing of projects.</para>
</sect2>
</sect1>
@ -322,7 +329,7 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<sect3>
<title>LinuxMedNews</title>
<para> <ulink url="http://www.LinuxMedNews.org/"> LinuxMedNews</ulink> is a site designed to facilitate, amplify and begin the process of fundamentally changing medical education and practice into a more effective, fair and humane enterprise using modern technologies. The site uses Zope and a slashdot clone Squishdot to accomplish these goals. It is not intended to be doctor-centric, it is intended to be an interesting/fun forum and resource for anyone who has an interest in health care and open source.
<para> <ulink url="http://www.LinuxMedNews.org/"> LinuxMedNews</ulink> is the unofficial news site for Linux and medical projects. LinuxMedNews.org is designed to facilitate announcements and sharing, of information related to open source applications and how they are advancing the efforts of medicine worldwide. LinuxMedNews is published using Squishdot and Zope for its news and project collection. LinuxMedNews is intended to be an interesting and fun resource for anyone with an interest in health care and open source.
</para>
</sect3>
@ -340,7 +347,7 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<title>Organizations</title>
<sect3>
<title>American Medical Informatics Association</title>
<para><ulink url="http://www.amia.org">AMIA</ulink> is a association that is quite a resource for the informatics community. Unfortunately, they require a subscription to join, but I have found that some mailing-lists will add you. I have found the cs-wg mailing list the most interesting, with some of the best discussion going around. The discussion are extremely good and informative.
<para><ulink url="http://www.amia.org">AMIA</ulink> is an association supporting the technology and informatics for the medical community. AMIA sponsors an Open Source Working Group. The OS-WG has providers, clinics, hospitals, hardware manufacturers and researchers worldwide giving a broad perspective for the technology needs and uses within medicine. AMIA does require a subscription, however AMIA offers an associate membership for $30 for one year. At this membership level, you can join one working group and its mailing list.
</para>
</sect3>
</sect2>
@ -351,7 +358,7 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<sect3>
<title>OpenHealth</title>
<para><ulink url="http://www.openhealth.com/">OpenHealth</ulink> is a another community that I have found has a good mailing list discussion. You can join the mailing list by going <ulink url="http://www.openhealth.com/en/healthcare.html"> Here</ulink>. It also contains a <ulink url="http://www.openhealth.com/en/healthlinks.html"> Link</ulink> to a list of other open-source works.
<para><ulink url="http://www.openhealth.com/">OpenHealth</ulink> is a company owned mailing list for community discussion of issues related to open source software development for medical projects. This is one of the largest and most popular lists for discussion of topics related to science and medicine and has an international population. In late 2003 and early 2004 there were problems with users trying to joing the list. Minoru Development, the owner of the OpenHealth List, is working with Bud Bruegger to improve administrative issues, and since Bud has assumed the administrative role, joining the list or resolving list issues is typically resolved in one to two days. Join the mailing list by going <ulink url="http://www.openhealth.com/en/healthcare.html"> Here</ulink>. Minoru Development also has a <ulink url="http://www.openhealth.com/en/healthlinks.html"> Link</ulink> to a list of other open-source application projects.
</para>
</sect3>
@ -359,7 +366,7 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<sect3>
<title>Open Source Health Care Alliance</title>
<para>
<ulink url="http://www.oshca.org/"> Open Source Health Care Alliance (OSHCA)</ulink> is a collaborative forum to promote and facilitate open source software in human and veterinary health care.
<ulink url="http://www.oshca.org/"> Open Source Health Care Alliance (OSHCA)</ulink> is a collaborative forum to promote and facilitate open source software in human and veterinary health care. At the OSCHA web site most of the information is stale, and there is a direction to the OpenHealth mailing list.
</para>
</sect3>
@ -385,40 +392,27 @@ Though I hope trademarks will be superfluous sometimes (you may see what I mean
<sect2>
<title>Debian Med</title>
<para>The linux distribution by Debian is a well known and highly respected one. The developers are all volunteers and dedicated. Recently, it was announced that Debian would start making a Debian Med Package. This is very very good news, because one of the things Debian is known for is its "APT-GET" interface. This allows applications to be installed with the simple command of "apt-get install [application]". For example, if I wanted to install the OIO record system, I would simply type in 'apt-get install oio' and the apt-get program would not only install the OIO software, but would also install any software that OIO is Dependant on to run, such as the postgres database and Zope software and would configure it so that you could immediately start using it.</para>
<para>If you think I sound enthusiastic about this project, I am, because it simply would be perfect for the rest of the projects that are being developed in that would ease installment.</para>
<para>I urge to visit the Debian Med Homepage, by clicking <ulink url="http://auric.debian.org/~tille/debian-med/">HERE</ulink>
</para>
<para>Debian-Med is a Debian meta-project allows for installation of medical themed appliations. Debian-Med is not a separate distribution, but is an extended functionality for Debian users. Below you will see many applications for the medical community. Typically, you would download and install a single application, and resolve any issues that arise during an installation. Debian-Med solves that installation issue. The Debian-Med project leaders will note that an application is a medical or biosciences related application. </para>
<para>After you have installed Debian, you can choose to load either a single application, or you can choose to load Debian-Med. Loading Debian-Med will install all of the applications that have been designated as medical or biosciences related. The Debian-Med project can be found in the Apt-get repositories. <ulink url="http://www.debian.org/devel/debian-med/">Click here to access the Debian-Med home page</ulink></para>
</sect2>
<sect2>
<title>OpenEMR</title>
<para>OpenEMR is a modular, HIPAA compliant, Open Source, cross-platform
Electronic Medical Records system (EMRS) developed by Synitech Incorporated
(www.synitech.com). It facilitates efficient office management through
automated patient record journaling, and has been successfully
integrated with third-party technologies including speech recognition, secure
wireless access, touch screen portables, and biometric authentication.
Interface screens are theme-able and optimized for consistency,
simplicity, speed of access to patient information, and minimum eye strain.
OpenEMR is based upon widely-used public standards to achieve maximum
compatibility with evolving technologies</para>
<para>OpenEMR is a modular, HIPAA compliant, open source, practice management, electronic medical record and prescription writing application. OpenEMR should have billing capability using FreeB by late April 2004. The planned billing functionality for OpenEMR will include the ability to generate ANSI X12 or HCFA 1500 forms, or submit bills directly to Medicaid, Medicare or private insurers. The developers on the project are actively working on completing the billing functionality. 2.5.2 is the latest version of OpenEMR and includes the ability to find the first available appointment on the calendar for a provider, direct links to encounters from the calendar, different calendar views for a provider or office staff, reporting using phpMyAdmin and prescription writing.</para>
<para>OpenEMR uses Linux, Apache, MySQL and PHP. OpenEMR incorporates the work of several open source projects such as PostCalendar from PostNuke for calendaring, and phpMyAdmin for database reporting and manipulation. OpenEMR is also integrating the work of FreeB for billing.</para>
<para><ulink url="http://www.openemr.net">At the OpenEMR.net User forum you will find several user testimonials about installing, migrating data and customizing OpenEMR in actual medical office environments.</ulink></para>
<sect3>
<title>Last Update:</title>
<para> March 25, 2004
</para>
</sect3>
<para>OpenEMR has been in development and beta testing for the past 2 years,
and is finally released to the public for download. The system is cross
platform, and operates on top of Apache or IIS, PHP and MySQL. OpenEMR
is fully HIPAA compliant and includes advanced authorization and
auditing functionality, HIPAA-mandated automatic timeouts, group-based user
configuration, extensive logging, and supports patient-requested file
changes. There is a growing developer base dedicated to making extensible
and configurable encounter forms and patient/office statistical
reports, and Synitech will soon release its template Notice of Information
Practices intended for use with OpenEMR</para>
<para>I have yet to have any experience with this software. Please let me know if you have experience with it. </para>
<para>I tried installing it, but the instruction are for crap.</para>
</sect2>
@ -429,7 +423,7 @@ Practices intended for use with OpenEMR</para>
<sect2>
<title>VISTA (DHCP)</title>
<para> <ulink url="http://www.hardhats.org"> VISTA</ulink> is a huge, VA hospital funded project, electron medical records system. I used this system, when I was a resident, in the Va hospital, and it simply was the best system (that I had used). I'm actually surprised that not more people know about this. I am not sure about the license, but the software and documentation is available under the Freedom of Information Act, but you need to send <ulink url="http://hardhats.org/foia.html"> REQUESTS</ulink> to get access to the software on CD. They are currently starting to host more and more of the code on-line, though.
<para> <ulink url="http://www.hardhats.org"> VISTA</ulink> is a largest and most comprehensive of open source medical projects. VISTA is an open source application that is funded by the federal government for use by the Veterans Administration at its hospitals and clinics. I used this system, when I was a resident, in the VA hospital, and it was the best system that I had used. This is a wonderful project that I can recommend. I am not sure about the software license, but the software and documentation are available from the U.S. Federal Government. To obtain the software you must file a Freedom of Information Act ("FOIA") request. The current fees to obtain VISTA on CD are $53US for the main VISTA packages and $13 for imageing. <ulink url="http://hardhats.org/foia.html"> REQUESTS</ulink> to get access to the software on CD. Some of the cost may be on-line, so please email the team at hardhats.org.
</para>
@ -442,61 +436,69 @@ Practices intended for use with OpenEMR</para>
</sect2>
<sect2>
<title>WorldVista and OpenVista</title>
<para> <ulink url="http://www.worldvista.org">WorldVista and OpenVista</ulink> are open source variants of VISTA.</para>
<para>WorldVista helps make healthcare information technology more affordable and more widely available both within the United States and internationally. WorldVistA extends and improves VistA for use outside its original setting through such activities as developing packages for pediatrics, obstetrics, and other hospital services not used in veterans' hospitals. WorldVistA also helps those who choose to adopt VistA successfully master, install, and maintain the software. As the group of VistA adopters and programmers grows, we work to develop it into a collaborative, consensus-based, open-source community.
</para>
<para> The OpenVistA project will help its adopters eliminate these fees by allowing VistA to run on the GT.M programming environment and the Linux operating system, both of which are open source and free. Historically, VISTA required adopters to pay licensing fees for the systems on which it runs: the programming environment (MUMPS) and the operating system underneath (such as Microsoft Windows or VMS). By reducing licensing costs, OpenVistA frees up money to be spent on medicine, medical professionals, and other resources more likely to directly improve patient care. Like all WorldVistA projects, the OpenVistA project not only provides adopters with the software itself but also transfers knowledge and expertise and builds long-term mutual support relationships between adopters and the rest of the worldwide VistA community. This software is for medical clinics, FQHC, hospitals, medicine training facilities, and community medical clinics.</para>
<sect3>
<title>Last Update:</title>
<para>12/20/2003
</para>
</sect3>
</sect2>
<sect2>
<title>SQL Clinic</title>
<para>
<ulink url="http://www.sqlclinic.net"> SQL clinic</ulink> is an impressive application that was developed for mental health workers, sponsored by their local hospital. What is most impressive is the amount of documentation. However it is unclear how useful the application would be for other non mental-health professionals.
<ulink url="http://www.sqlclinic.net"> SQL clinic</ulink> is an impressive application that was developed for mental health workers, sponsored by their local hospital. What is most impressive is the amount of documentation. SQL Clinic in its current format may require additional customization for use outside of mental-health projects.
</para>
<para>
<blockquote>
<attribution>Thomas Good writes</attribution>
<para>
To address the point about its utility outside the mental health sector: we are doing a spin-off called (believe it or not) SQL Cafe. Why? The local Indian restaurant (www.tasteofindia.org - I do their web pages) has hired us to design a custom database that tracks vendors, customers, uses a cgi based on-line menu (to replace the html version, so modifications don't require html skills) and so on.
SQL Clinic is designed to be reverse engineered and used for medical or other purposes. SQL CLinic is based on Lincoln Stein's CGI.pm module and the incredible horsepower of PostgreSQL. The developer's goal for SQL Clinic is for the project to have utility as an example of how to access postgres via Perl than as a mere clinical application.
</para>
<para>
Seriously, one other thing about SQL Clinic is that it was designed to be reverse engineered and used for other purposes. It's all based on Lincoln Stein's CGI.pm module (a terrific tool) and the incredible horsepower of Postgres. So I suspect, once Ingo and I get it a bit more streamlined, that SQL Clinic may have greater utility as an example of how to access postgres via Perl than as a mere clinical application. At least that is our goal.
</para>
</blockquote>
</para>
<sect3>
<title>Last Update:</title>
<para>Feb 2, 20002
<para>Feb 21, 2004
</para>
</sect3>
</sect2>
<sect2>
<title>Electronic Obstetrical Record System</title>
<title>FreeB</title>
<para>
<ulink url="http://www.eors.org"> EORS</ulink> is a quite a well-developed medical management system used by the developers themselves in their OB practice. The layout is somewhat Star Trek-ish, but quite useful and well developed.
</para>
<sect3>
<title>Last Update:</title>
<para>Unclear
</para>
</sect3>
</sect2>
<sect2>
<title>Freemed</title>
<para> <ulink url="http://www.freemed.org/"> Freemed</ulink> is a medical management software package that runs in a web browser window. It currently uses Apache, an SQL back-end (usually MySQL, but there's an SQL Abstraction for this), and PHP, and is non-browser specific. It aims to duplicate all of the functionality of programs such as The Medical Manager, while remaining free to the community.
</para>
<para> <ulink url="http://www.freeb.org/"> FreeB</ulink> is a medical billing engine. It is a collection of formats, as well as an engine capable of connecting with any Practice Management System that implements the FreeB API (XML-RPC). It supports HIPAA-compliant ANSI X12 837 electronic billing and HCFA 1500 paper formats.
</para>
<sect3>
<title>Last Update</title>
<para>Unclear. July 9, 2001 ?
<para>March 25, 2004
</para>
</sect3>
</sect2>
<sect2>
<title>FreeMED</title>
<para> <ulink url="http://www.freemed.org/"> Freemed</ulink> is a web based medical practice management and electronic medical record application. FreeMED runs on Apache, a SQL back-end (usually MySQL, but there's an SQL Abstraction for this), and PHP. FreeMED aims to duplicate functionality of proprietary applications such as Medical Manager, while remaining open source.
</para>
<para>FreeMED is working on two functional additions: billing with FreeB and reporting using Agata. FreeB will allow FreeMED users to send ANSI X12 or HCFA 1500 forms directly to a payer. Agata, an open source replacement for Crystal Reports, will allow a practice to create custom reports for FQHC UDS reporting or other reporting needs.
</para>
<sect3>
<title>Last Update</title>
<para>March 25, 2004
</para>
</sect3>
</sect2>
@ -504,30 +506,73 @@ Practices intended for use with OpenEMR</para>
<sect2>
<title>Freemed-YiRC</title>
<para> <ulink url="http://freemed-yirc.familyandyouth.org/"> Freemed-YiRC</ulink> is a PHP package based on Freemed for use with Youth in Residential Care (YiRC) agencies. Its aim is to be a complete package to replace legacy non-free apps which aren't customizable. Since it's PHP-based, all that is needed for the client is a good Web browser with extensive table support. It can use both Postgres and MySQL databases.
<para> <ulink url="http://freemed-yirc.familyandyouth.org/"> Freemed-YiRC</ulink> is based on FreeMED for use with Youth in Residential Care (YiRC) agencies. Its aim is to be a complete package to replace legacy non-free apps which aren't customizable. As a PHP-based application, all that is needed is a web browser with extensive table support. It uses either Postgres or MySQL databases.
</para>
<sect3>
<title>Last Update:</title>
<para>02/04/2002
<para>11/23/2003
</para>
</sect3>
</sect2>
<sect2>
<title>Care2x</title>
<para> <ulink url="http://care2x.org/">Care2x</ulink> is for hospitals and health care organizations. It is designed to integrate the different information systems existing in these organizations into a single efficient system. Care2x solves the problems inherent in a network of multiple programs that are incompatible with each other. It can integrate almost any type of services, systems, departments, clinics, processes, data, or communication that exist in a hospital. Care2x's design can even handle non-medical services or functions like security or maintenance. All of its functions can be accessed with a Web browser, and all program modules are processed on the server side.
</para>
<sect3>
<title>Last Update:</title>
<para>01/10/2004
</para>
</sect3>
</sect2>
<sect2>
<title>Medical DataServer</title>
<para> <ulink url="http://www.mii.ucla.edu/dataserver/">Medical DataServer</ulink> is an XML gateway, specially tailored for the medical domain. It provides an enterprise-quality platform for aggregating XML-based patient medical records, in both clinical and research applications. It is middleware, situated between clients and traditional Health Information Systems (HIS), Radiology Information Systems (RIS), and Picture Archive and Communication Systems (PACS). It supports relational (SQL), SOAP, and HTTP data sources out of the box, but is highly extensible for custom types. A suite of Web-based tools allows for the centralized management of distributed data sources, and the rapid deployment of new services. It addresses HIPAA concerns with query auditing, tight integration with security mechanisms, and patient record de-identification.
</para>
<sect3>
<title>Last Update:</title>
<para>03/25/2004
</para>
</sect3>
</sect2>
<sect2>
<title>OpenClinic</title>
<para> <ulink url="http://openclinic.sourceforge.net/openclinic/index.html">OpenClinic</ulink> OpenClinic is an easy to use, open source medical records system. It has been mainly developed for private clinics, surgeries, and private doctors. It is platform independent and has a multi-language architecture.
</para>
<sect3>
<title>Last Update:</title>
<para>12/20/2003
</para>
</sect3>
</sect2>
<sect2>
<title>GNUMed</title>
<para> <ulink url="http://www.gnumed.net"> GNUMed</ulink> is a GNU's project to develop a comprehensive medical management solution.
<para> <ulink url="http://www.gnumed.org/"> GNUMed</ulink> is suited to doctors in community practice, but may suit others who provide a degree of comprehensive care (general internists, pediatricians, others). GNUMed will support a few or many networked users with secure local or remote access. GNUMed will also operate on a single computer. The GNUMed project recommends testing GNUMed on a single computer to examine the software's features for a particular practice.
GNUMed is comprised of a group of practicing physicians, programmers and open source software enthusiasts from around the world. GNUMed's data is accessed via business objects implemented in Python directly accessing the PostgreSQL RDBMS. GNUMed will also access various types of data stores such as other RDBMS or LDAP.
</para>
<sect3>
<title>Last update:</title>
<para>2000-11-22
<para>12/30/2003
</para>
</sect3>
</sect2>
@ -535,13 +580,12 @@ Practices intended for use with OpenEMR</para>
<sect2>
<title>GNotary</title>
<para> <ulink url="http://gnumed.net/gnotary/"> GNOTARY</ulink> is a client that provide the ability to notarize digital documents using a server to prove that digital documents have not been tampered with after their initial creation date. This is a very important piece of software.
<para> <ulink url="http://www.gnumed.net/gnotary/"> GNOTARY</ulink> is a part of the GNUMed Utility Collection and is designed to provide the ability to notarize digital documents using a server. The purpose of the notary for medical records is to prove that digital documents have not been tampered with after their initial creation date.
</para>
<para>The author provides a GNotary server to provide the actually notarization on a separate system.</para>
<sect3>
<title>Last Update:</title>
<para>2001-06-24</para>
<para>11/26/2001</para>
</sect3>
</sect2>
@ -549,62 +593,18 @@ Practices intended for use with OpenEMR</para>
<sect2>
<title>Res Medicinae</title>
<para><ulink url="http://sourceforge.net/projects/resmedicinae">Res Medicinae</ulink> is to become a comprising software solution for use in Medicine which combines intuitive ease of use with the advantages of the CYBOP
Framework. It uses latest technology adhering to common standards for
medical
software and will such be open to many other medical systems.</para>
<para>
Res Medicinae is the attempt to overcome high pricing in the realm of
Medical
Information Systems and to provide users with a free, stable, secure,
platform-independent, extensive system.
<para><ulink url="http://resmedicinae.sourceforge.net/">Res Medicinae</ulink> is to become a comprising software solution for use in medicine which combines intuitive ease of use with the advantages of the CYBOL programming language. It uses latest technology adhering to common standards for medical software and will such be open to many other medical systems.
<para>Res Medicinae is the attempt to overcome high pricing in the realm of medical information systems and to provide users with a free, stable, secure, platform-independent, extensive system.
</para>
<para>
Res Medicinae is and will be free in every meaning. Its contributors
enjoy
working together communicating over mailing lists and are encouraged by
the
idea of sharing their knowledge with those people living on "the poorer
side
of" the world.</para>
<sect3>
<title>Last Update:</title>
<para>10/4/2002</para>
</sect3>
</sect2>
<sect2>
<title>The LittleFish Health Project
</title>
<para> The "Littlefish Health Project" does not exist
anymore.
Some months ago, the administrators of both projects agreed to merge
"Littlefish" into "Res Medicinae". You can still find the Littlefish
material on ResMedicinae's website, see the menu there.</para>
</sect2>
<!-- <sect2>Last Update:
<p>2000-04-01, I am currently trying to contact the maintainer
-->
<sect2>
<title>Free Practice Management - FreePM</title>
<para><ulink url="http://www.freepm.org"> FreePM</ulink> is an open source project to create a provider designed patient centered electronic medical record and practice management application. This is probably one of the most developed projects out there, seems already quite usable in its Demo. More significantly, they offer services to help actually run their software in a real office, but all the code is open-source and they seem committed to this philosophy.
</para>
<para>
I have successfully installed this and gotten it to run. Please look for further info in chapter 7.
</para>
<para> Read a review of it <ulink url="http://www.linuxmednews.com/linuxmednews/993731309/index_html"> HERE</ulink>.
</para>
</sect2>
<!--
<sect2>Last Update:
<p>Unclear, possibly Nov, 2001.
-->
<sect2>
<title>Open Infrastructure for Outcomes
@ -622,7 +622,7 @@ material on ResMedicinae's website, see the menu there.</para>
</sect3>
<sect3><title>Update</title>
<para>I have successfully installed this and believe that this is a real contender. In the HOW-TO Install section, I may try to replicate all documents or use the fine documentation and just comment on it, making special note of problems encountered during installation and use
<para>I have successfully installed this and believe that this is an excellent application. In the HOW-TO Install section, I may try to replicate all documents or use the fine documentation and just comment on it, making special note of problems encountered during installation and use
</para>
</sect3>
</sect2>
@ -634,19 +634,6 @@ material on ResMedicinae's website, see the menu there.</para>
-->
<sect2>
<title>myPACS
</title>
<para><ulink url="http://sol.cc.u-szeged.hu/~kszabo/myPACS.html"> MyPACS</ulink> is a Web-based medical image management system. It is written in PHP 3.x and uses MySQL for the relational database back-end. It features searching capabilities, uploading of images and patient data from a Web browser into shared and private image repositories, and thumbnail creation and image conversion using ImageMagick. Currently MyPACS is not compatible with the DICOM standard.
</para>
<!--
<sect2>Last Update:
<p>
-->
</sect2>
<sect2>
<title>LIMS - Laboratory Information Management Systems</title>
@ -759,10 +746,10 @@ material on ResMedicinae's website, see the menu there.</para>
<title>FreeVET</title>
<para>He writes<blockquote>
<para>Earlier versions of the Medicine HOWTO included a reference to a
projectknown as FreeVet, a FOSS package available via QPL, aimed at being such
project known as FreeVet, a FOSS package available via QPL, aimed at being such
a solution. The project appears to have died after reaching a
relativelyhigh level of development and maturity. The only currently accessible
information and code that i've been able to find is here:
relatively high level of development and maturity. The only currently accessible
information and code that I've been able to find is here:
<ulink url="http://www-med-chemie.vu-wien.ac.at/mirrors/FreeVet/"> FreeVet</ulink></para>
</blockquote></para>
@ -950,13 +937,13 @@ www.TxOutcome.Org
<sect4>
<title>Running the Zope Server</title>
<para>Tim Cook also wrote two scripts to start the server and stop the server. Be sure you our in the FreePM directory. You will know this if you see the files 'start' and 'stop' in there. It is also the same directory where you ran the <userinput>./install</userinput>. To start the Zope server, type <userinput>./start</userinput>. However you might want to type <userinput>./start&</userinput> to make it a background process which will free up your terminal window. This will also allow you to stop the Zope Server by typing <userinput>./stop</userinput> instead of hitting the CRTL-C key combination, a rather blunt way of stopping the Zope server and not an aestheically pleasing way of stopping the zope process.
<para>Tim Cook also wrote two scripts to start the server and stop the server. Be sure you our in the FreePM directory. You will know this if you see the files 'start' and 'stop' in there. It is also the same directory where you ran the <userinput>./install</userinput>. To start the Zope server, type <userinput>./start</userinput>. However you might want to type <userinput>./start&</userinput> to make it a background process which will free up your terminal window. This will also allow you to stop the Zope Server by typing <userinput>./stop</userinput> instead of hitting the CRTL-C key combination, a rather blunt way of stopping the Zope server and not an aesthetically pleasing way of stopping the zope process.
</para>
</sect4>
<sect4>
<title>Installing the FreePM zope products </title>
<para>The key thing before I talk about installing the zope products is that, the first user, Admin, can only add other users and can not by itself actaully magane any products. You first need to add a new user and make the user a manager before you can do anything else.
<para>The key thing before I talk about installing the zope products is that, the first user, Admin, can only add other users and can not by itself actually manage any products. You first need to add a new user and make the user a manager before you can do anything else.
</para>
<para>
To log into the running Zope server, you need to open a browser, type in http://127.0.0.1:8080 or depending on how new the Zope server is http://127.0.0.1:9673. If you look at the output during the install it will tell you what to what port to connect. <caution><para>Note: Using the old port 8080 would conflict, which is why Zope changed the port connection.</para></caution> At this point you should the zope introductory page, if not, make sure you have the correct port.
@ -964,17 +951,17 @@ www.TxOutcome.Org
<para>Go ahead and click on the link that says Zope management interface or enter http:127.0.0.1:8080/manage and you should the zope management screen. You know you are in the correct section if you see a root folder at the top of the Left Frame. To make sure we are on the same page, go ahead and click on the Root Folder icon in the right Frame.</para>
<para>You then should see the list of contents of the Root Folder on the Right Frame.</para>
<para>Look for and click on the <emphasis>acl_users</emphasis> folder. select add new user, fill in the required fields. You leave the domain field blank. And then besure sure to select role. In this case, click on <emphasis>manager</emphasis> for this user.</para>
<para>I am having problems sucessfully loggin out completely using zope, so when you intend to switch users, be sure to completely close all broswer windows.</para>
<para>Once you added a new user that has the role of manager, log back in. THat is to say, Close all browers and open up a new browers and go the the zope management screen. You should be asked for a login at this point. Go ahead and enter in you new user login and password.</para>
<para>Once you are logged in as an user (not the admin user), go ahead and click on the Root Folder on the top of the left frame. Scrool to the bottom of the Right Frame and you should see the Import/Export button. You see a new screen. In the Field Import File Name, enter FreePMProduct.zexp and then hit the import button. You should see a new scree nindicating success</para>
<para>The next step, is to again hit on the Root Folder Icon at the TOP LEFT FRAME. Again hit the Import/Export button, but this time, you want to import FreePM.zexp. Then hit the Import button. <caution><para>Note that it will take some time to import the FreePM.zexp Zope product as it is quite large and you may get a brower error. I almost lost hair doing this stage because I coulnd tfigure out what was going wrong. In fact nothing was going wrong, it just took some time to import this large (32MB) zope prodcut. If you want to make sure something is acutally going on, I recommend using the <userinput>top</userinput> unix command, which will show you that python is actively still working to import FreePM.zexp.</para> </caution></para>
<para>Look for and click on the <emphasis>acl_users</emphasis> folder. select add new user, fill in the required fields. You leave the domain field blank. And then be sure sure to select role. In this case, click on <emphasis>manager</emphasis> for this user.</para>
<para>I am having problems successfully logging out completely using zope, so when you intend to switch users, be sure to completely close all browser windows.</para>
<para>Once you added a new user that has the role of manager, log back in. That is to say, Close all browsers and open up a new browsers and go the the zope management screen. You should be asked for a login at this point. Go ahead and enter in you new user login and password.</para>
<para>Once you are logged in as an user (not the admin user), go ahead and click on the Root Folder on the top of the left frame. Scroll to the bottom of the Right Frame and you should see the Import/Export button. You see a new screen. In the Field Import File Name, enter FreePM Product.zexp and then hit the import button. You should see a new scree indicating success</para>
<para>The next step, is to again hit on the Root Folder Icon at the TOP LEFT FRAME. Again hit the Import/Export button, but this time, you want to import FreePM.zexp. Then hit the Import button. <caution><para>Note that it will take some time to import the FreePM.zexp Zope product as it is quite large and you may get a browser error. I almost lost hair doing this stage because I could not figure out what was going wrong. In fact nothing was going wrong, it just took some time to import this large (32MB) zope product. If you want to make sure something is actually going on, I recommend using the <userinput>top</userinput> unix command, which will show you that python is actively still working to import FreePM.zexp.</para> </caution></para>
</sect4>
<sect4>
<title>Running FreePM </title>
<para>To actually get to the FreePM, you need to open a browser and go to http://127.0.0.1:8080/FreePM</para>
<para>You should see the introductor screen of FreePM. However, so far I can only add patients but can not edit any sensitive information. This section will need a lot of work</para>
<para>You should see the introductory screen of FreePM. However, so far I can only add patients but can not edit any sensitive information. This section will need a lot of work</para>
</sect4>
</sect3>
@ -1006,7 +993,7 @@ www.TxOutcome.Org
<sect1><title>Usefull Applications</title>
<sect1><title>Useful Applications</title>
<sect2><title>KPumpe</title>
<para>
By David Weisgerber (http://freshmeat.net/users/david84/)
@ -1037,10 +1024,10 @@ www.TxOutcome.Org
<sect2>
<title>Too Many Projects</title>
<para>Having spend some time on looking at the available software, I can only say that currently, we simply have an abundance of development, but little progress. I keep seeing multiple projects trying to achieve the same thing, but the resources are spread too think and so they fail. I wonder if there were some way to concentrate the various developers onto one project. The questions remain as to what main ideas should be focused on. Obviously the first one should be a Medical records application. That is a coherent, portable, way to contain, process, and use all the medical data that is generate by a patient.</para>
<para>The second focus should be on software for a workign clinic. This seems to be much harder since it would involve the billling seciton. However this would also include things like scheduling and multitude of forms that a clinic uses in day to day use.
<para>The second focus should be on software for a working clinic. This seems to be much harder since it would involve the billing section. However this would also include things like scheduling and multitude of forms that a clinic uses in day to day use.
</para>
<para>THe third focus (one I know little about) would be in the more specialized applications like Imagaing, which seems to already have quite a bit of working software, but is inherently hard to make because not everyone has access to CT scanners and such.
<para>The third focus (one I know little about) would be in the more specialized applications like Imageing, which seems to already have quite a bit of working software, but is inherently hard to make because not everyone has access to CT scanners and such.
</para>
</sect2>
@ -1051,7 +1038,7 @@ www.TxOutcome.Org
<sect3>
<title>Debian as Standard linux distribution</title>
<para>I realize that urging people to consider debian as the standard linux system when it comes to medical applications is probably like arguing about religions. But.. :) The point is that our audience is not Linux gurus who only use slack or can configure applications from source tar balls. Debian provides an extremely sophisticated and easy to use installation process that is ideal for people who want to get a system running.
<para>I realize that urging people to consider Debian as the standard linux system when it comes to medical applications is probably like arguing about religions. But.. :) The point is that our audience is not Linux gurus who only use slack or can configure applications from source tar balls. Debian provides an extremely sophisticated and easy to use installation process that is ideal for people who want to get a system running.
</para>
</sect3>
@ -1059,8 +1046,8 @@ www.TxOutcome.Org
<sect2><title>I work and what is needed.</title>
<para>Now that I have been working for almost two weeks, here are a few things I have learned. While a resident, I did part of my training at the VA hospitals which had a superb information system, but it required that we type out everything from the smallest order to the emergency stat orders. This seemed to work weel for teh VA since most of the Doctors had residents do their notes or they tended to dictate very little, writing very breif, sometimes cryptic, notes about the status of their patient. Now that I am in the private world, the only thing that seems to be saving medicine are the transciptionists who take the garbled spped talk that doctors do and type out coherent statements. The problem that I see with many of these data systems is that seem to assume that doctors have the time which they dont (there is barely enough time to see a patient properly let alone do all the coding na dthen write out a clear note.</para>
<para>Several idea come out that doctors will merely have to tick off boxes on a palm device to indicate what they did, but this is fine for billing but not so for the actualy medical record, which even though is breif contains much more subtley then any billing coding system could have. Perhaps what we need is to maintain the medical record in its narrative form and have a parser go throught it and pull the important bits and then it would enter this stuff into database. It is an idea, but surely a worthwhile one since Doctors simply can not sit aroung computer terminals (as I am doing, but it is a Sunday)
<para>Now that I have been working for almost two weeks, here are a few things I have learned. While a resident, I did part of my training at the VA hospitals which had a superb information system, but it required that we type out everything from the smallest order to the emergency stat orders. This seemed to work well for the VA since most of the Doctors had residents do their notes or they tended to dictate very little, writing very brief, sometimes cryptic, notes about the status of their patient. Now that I am in the private world, the only thing that seems to be saving medicine are the transciptionists who take the garbled speed talk that doctors do and type out coherent statements. The problem that I see with many of these data systems is that seem to assume that doctors have the time which they don't (there is barely enough time to see a patient properly let alone do all the coding and then write out a clear note.</para>
<para>Several idea come out that doctors will merely have to tick off boxes on a palm device to indicate what they did, but this is fine for billing but not so for the actually medical record, which even though is brief contains much more subtly then any billing coding system could have. Perhaps what we need is to maintain the medical record in its narrative form and have a parser go through it and pull the important bits and then it would enter this stuff into database. It is an idea, but surely a worthwhile one since Doctors simply can not sit around computer terminals (as I am doing, but it is a Sunday)
</para></sect2>
</sect1>
@ -1153,3 +1140,4 @@ erschienen. Der bekannte Abschnitt zu Linux und Medizin ist
</sect1>
</article>