This sounds reasonable and certainly is, but there are some more complications. I try to be database independent, too, letting the deployment of a particular database to be site specific. The problem I also ran into at our state is the required use of MSSql on an Windows platform. Something like PostgresSQL was beyond their willingness to move.
Also, the system would have to meet CDC reporting requirements, for which much of their software is used, not because they find it useful, but because it is required to meet their reporting requirements. They will be using NEDSS because it is supported by CDC and reduces their exposure to responsiblity of software risk. Thus an open source solution also needs to be NEDSS-compliant or PHIN compatible in the US these days. Something better isn't the only driving force these days. Dave > ------------Original Message------------ > From: Tim Churches <[EMAIL PROTECTED]> > To: [email protected] > Date: Fri, Dec-24-2004 8:01 AM > Subject: Re: Open source tools for population health epidemiology and public > health > > David Forslund wrote: > > I know a number of folks who would be interested, but the inability > to > > run the software on Win platforms removes them > > from consideration at this time. > > All of the tools and infrastructure used are cross-platform, with the > exception of PostgreSQL - but that will soon be also with the imminent > release of Version 8.0, which will run natively under MS-Windows as > well. It's just that MS-Windows is not our primary development > platform, > and we haven't had time to recompile, test and package various > components for it - but we will, in due course (or someone else might > volunteer to take on that task). > > Tim C > >
