I recently asked some questions about how to speed up record access for an existing emr, which is fairly slow for large records. The answer seemed to be that thin client sessions works the best if the network isn't good enough.
one can set up multiple thin client sessions between two computers running debian or any linux to see how gnumed performs; my laptop with 512mb 2.8 ghz pentium 4 was the "server", and it did quite well using vnc4server running on the debian system on the laptop. The idea was to create multiple user accounts e.g. user1, user2, etc.. then copy the gnumed tree into each of the user directories ( make all users part of the "users" group and chgrp -R users gnumed-cvs-directory ). also have ssh-server running on the server. then from the client machine , ssh into each user account, e.g. ssh [EMAIL PROTECTED], then run vncpasswd , followed by vncserver. the display number and the password for each user has to be remembered. then logout, and using vnc4viewer laptop:<display-no> and enter password. this will give you a X desktop for each user's display , and my laptop managed 6 sessions without too much difficulty ( vnc4viewer gave an adequate desktop size for gnumed). In each desktop, then just go into a xterm session and change into the gnumed client directory that has been copied to that user's directory and run sh gm-0_2-from-cvs.sh it doesn't matter if any-doc is used as the gnumed user each time. now if you are in au and use a fairly common emr, you can use gnumed to browse the patient demographics and progress notes. the importers scripts are in client/importers/au/md2/a , use dbf_2_pg first to create a postgresql database from the dbf /dbt files, and then use the script in gnumed_import to transfer the patients.dbf , the doctors.dbf and progress.dbf/ dbt into a gnumed_v2 database, _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
