Dear Mr. Antas, I was considering imaging workstations, which is a completely different thing from stupid SAA terminals running on old-moded HIS systems, which still account for the majority of HISs I have seen so far. Have a look in you local radiology department. Which machines do they run there reporting on ? Do the use dragon-dictate or any other voice recognition system ? If yes, I suppose the use MS-machines..What machines do they use to grab images ?
Imaging for Linux -to my opinion- is still in its child years. Support for grabber cards other then BT848/878 -if any- is poor. Imaging for Java is still more behind. (I know that these statements will account for some more "minus scoring" an my behalf) Btw. i-path client is a MS-windows application ;-) Your considerations about MS-systems security are 100% right anyway. Greetings Alex ----- Original Message ----- From: "J. Antas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 19, 2004 12:25 PM Subject: Re: [Care2002-developers] digital camera Alexander Hölzel wrote: > I suppose most Care2x clients will operate under MS-Win OS, so WDM will be > the appropriate technology to use. That suggests that you have few, or no, previous experience with hospital IT. Care2x is open source and free. Micro$oft isn't neither free nor open source. Micro$oft does not like open source at all. An hospital that relies in Windows is arguably an unreliable and unsecure hospital. Contrary to what Micro$oft hardly tries to convince you Windows is unreliable and full of back doors. Security policy is unenforceable as Windows networks are fundamentally unsecure: anyone with boot access to a terminal may easily and instantaneously acquire administrator privileges. For years hospitals have not relied in Windows neither for their main "heavy" software, nor for their (terminal) clients. In fact concepts like "secure" or "reliable" are difficult to conciliate with words derived from "Micro$oft". Instead, I would expect that most Care2x installations would be made over something much more secure, something like BSD or Linux. Those systems also have the added value of being both free and open source. Additionally, under Linux there is a beautiful way of making a hospital network that involves LTSP (The Linux Terminal Server project: http://www.ltsp.org/) and SSI clustering (openSSI:http://openssi.org/) and Heartbeat (http://linux-ha.org/heartbeat/). That way you will have clustering with high availability and transparent node registration and load balancing. Also you will have NO MASS STORAGE in the local terminal, meaning that each time that a terminal is leaved unattended or is disconnected there will be no information available to be carried out of that institution. How is that for clinical (or operational, or financial) data security? Also, looking at the hardware side, local terminals may be constructed from old, recycled, cheap hardware, starting from old pentium II 300 MHz to high tech over 3 GHz Opteron 64. J. Antas ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
