Nice description Elpidio. Salman- ----- Original Message ----- From: "Elpidio Latorilla" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 16, 2004 8:47 PM Subject: Re: AW: [Care2002-developers] about patients and personnel in the same table
Hello Salman, thanks a lot for your analysis. I agree that the patient is a separate entity from a personnel. This is actually implemented inside the database where all data pertinent to patient (as a patient) are stored in separate tables (lets call it patient tables) while the data pertinent to personnel (as hospital staffer) are separate in their own appropriate tables too (lets call it personnel tables). I think the main cause of confusion is the data of a person (as a person) which are neither patient data nor personnel data (like birthdate, SS nr. etc). One can also name these as data which are common to both (depending on how one views it). To visualize it somewhat: Person data: name, birthdate, address, SS nr., Nat. ID., etc. Patient data: admission date, insurance, diagnosis, therapies, prescriptions,etc. Personnel data: employment date, length of contract, job, salary level, vacation, tax ID,etc. This is the current structure within care2x. Of course, if a group or country believes that they need (for whatever reason there may be) to include the Person data inside both Patient data and Personnel data, they can do it. Merging their code to the main release is a different question and must be tackled separately (if ever needed). Another way is to keep the current structure and just modify the GUI to satisfy the local needs, just like those solutions suggested by Daniel Ignat. This would present the least problem in merging codes. Elpidio On Monday 15 November 2004 14:27, Salman HM wrote: > So here it comes from an analyst's view point: > A staff member in a hospital can get treated at his/her hospital. By > becoming a patient, this new entity MUST go on the patients file/table; > Name and National Id nr get duplicated, and that's OK. To Normalise by > keeping the data on the personnel table is a severe violation of entity > definition. > > Also, a sick staffer is a patient class like an insured patient; he/she has > a treatment/coverage plan, the provider of which is the hospital itself. In > fact, in some cases both the hospital and insurance companies will provide > the coverage based on a) the types of medical services/treatments rendered, > and b) percentage of cover. ------------------------------------------------------- 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 ------------------------------------------------------- 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
