Hello Jean-Philippe, On Friday 14 May 2004 07:48, Jean-Philippe LIOT wrote: > I am really happy to give my little improvement to your great project. I do > not have enough time to work daily on it but i will make my best to > continue.
Yes, it is a very good improvement indeed. And good news, I got it running in PostgreSQL now and the refresh-date is now inputted in the local date format. But I cannot simply distribute the scripts now because they use several global values needed in the PostgreSQL running version of Care2x. They will surely be in the coming Generation 2 release of Care2x which is not very far from now. Actually I am about to package the release but this PostgreSQL has lots of quirks that make my life not easy (I know, the postgre people will stone me to death me for saying this). > Immunization : I am working on a generic form to fill the the care's tables > specially care_type_immunization and any other table such as > care_address_citytown, care_tyope_*. You could pass to the script a name of > a table and it will generate 3 scripts to list, create and update the > table. I could use the address book form as example? Wow that would be nice. Ok, you can use the address book as the example. > Another question : Is there a way to make a link beetween persons in order > to show familly link. It could interesting to know who is in charge with a > person, who will pay. In my case, i could make a difference beetween > patient and owner of the animal. I suggest just adding a field to the > care_person table which would refer to a number "nr" of another person. If > the field is set to Null, it is a standalone person. In the search form, we > could show the major person and the searched person in a tree. For > instance, Yes, these are already in the tables. The implementation was not done due to priorities. Here are the fields in the care_person table that you can use: mother_pid = points to the PID of the mother father_pid = points to the PID of the father contact_pid = points to the PID of the contact person Now since the encounter is in a separate care_encounter table, you can use the following fields in the care_encounter table: guarantor_pid = points to the PID of the person who guarantee to pay the bills This is usually needed when the person has no insurance as guarantor. contact_pid = this might look redundant to the above field in care_person table but the idea behind this is that this contact is considered temporary contact only during the encounter period and may or may not be the same as the main contact person in the care_person table. contact_relation = a free text field describing the relation of the contact to patient e.g. priest, girlfriend, wife, etc. current_attd_dr_nr = points to the personnel/employee number of the doctor who is currently assigned to attend to the patient consulting_dr = a free text of the consulting physician's name. This is free text because of the high probability that the physician is not a direct employee of the hospital (therefore no employee number). But if you think that there are some more needed elements, please let us know. Best regards, elpidio ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
