One word about encryption:
In Linux, with the new 2.6.8.x kernel (which btw seems to be quite stable, after 6 months of testing), you have native (loop) filesystem encryption, if want it. So, you have a passphrase and if the system is stopped or rebooted, you cannot read the original data, you need to write to passphrase first in order to access the encrypted filesystem, then for that session the encryption is transparent, I mean, people who may access by any means your running computer, may read the 'encrypted' data.
The 2.4.x kernel need a patch to do that, or you may use a no-native implementation (cloop ?? I am not sure)
In Windows I know about a (proprietary) solution named 'PGPDisk' which lets you create an encrypted folder and there you may store your mysql data. The result is the same as above.
MySQL dosen't have (as I know) native 'storing' encryption support (it may have 'transmition' encryption with OpenSSL, if compiled so)
-- Daniel Ignat PHP Programmer and SysAdmin
Walter Nunez wrote:
I understand of similar way, a hospital's employee gets sick and himself becomes that hospital's patient.
This is a question of two developers Alejandro del Garate and Juan
Rossano, the main aspect will be the security of the data of the patient..
They have so much experience in HIS at argentinian hospitals.
My first answer was about the database encryption in the near future and redundancy of data,
but thinking about the future and the political decision to implementing, we could have all the possible answers and variants
Thanks a lot Elpidio and Daniel
Walter
Hello Walter,
I just suggested that possibility based on my understanding of your idea to separate the personal data of the hospital's personnel from the patient data. Since the personal data are the same, you can use the same structure. Of course this means that once a hospital's employee gets sick and himself becomes that hospital's patient, you might need to reenter his personal data as a patient. This means double work and redundancy of data.
I personally wanted to avoid this redundancy thats why there is currently only one person data table and it also contains the data of the hospital's personnel.
But I understood your last posting that you might need a true separation so I suggested the previous solution. Please correct me if I am wrong.
Elpidio
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
