Hi Robert, The field name can be what you suggested - what I put in was a little generic. I certainly want you to be happy.
In case there are hospitals that do not use the alt_pid field, keeping it NULL would allow them to proceed. Attempting to copy into alt_pid the value in pid if alt_pid is NULL would bring in anomalies and clash with similar numbers in the alt_pid that were not NULL in the first place. Hence the UNIQUEness for alt_pid would have to wait till you decide how to use it when alt_pid is absent (multiple NULL alt_pids should be able to exist). What is now in place is just a place holder. Please give it some thought as to how hospitals starting anew entirely in Care2x would be able to use it alongside with hospitals that intend to use Care2x for only a part of their operations whilst relying on their own HIS for others. Regards, Ap.Muthu > Hi Muthu, > > I am not so sure that it is really a legacy issue. Nearly all hospitals > I've visited they have either their own HIS and want to use care2x from > a specific point or they use it side-by-side. > > But in all cases they will continue their numbering format what is > always historical based and care2x has to work with it and I do not > think that they will change it one day. > > If it can be NULL in that way I have some doubts, but let see what it > will bring for results from the reality. But the indexing of that table > is not really funny. Better would be a unique key over pid, "alt_pid", > the birth date, first name, last name and registration timestamp instead > of having index for each column. > > That could have good benefits when this table will be joined afterwards > with other tables (avoiding of full table scans). > > Robert > > > Am Montag, den 01.11.2010, 07:47 +0530 schrieb Ap.Muthu: >> Hi Robert, >> >> Isn't this more of a legacy issue. >> Once the hospital is entirely on Care2x, it will not be necessary. >> >> This is quite useful if the patient is referred from another hospital. >> >> Rather than hospital_file_number, the field can be generic as alt_pid >> NULL >> This field should be optional and not null and not even unique. >> >> Regards, >> Ap.Muthu >> >> >> > Hi, >> > >> > Just out of experience.. and because I am doing that now again (as >> > always)... >> > >> > ALTER TABLE `care_person` ADD `hospital_file_number` VARCHAR( 20 ) NOT >> > NULL AFTER `pid` >> > >> > What do you think? Is it a major need and all of you have the need to >> > place there somewhere existing and already used hospital file numbers? >> > >> > Then we will add it to the next care2x release. >> > >> > Thanks >> > Robert >> > >> > p.s. Is there any need of having a documentation or example file how to >> > use tools like pentho's PDI to migrate existing datasets to care2x? >> > ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
