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 -- Walter Alfonso N�nez Rivera M�dico - Programador Pascual de Andagoya 140 Lima 32 Per� ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
