On 03/09/13 02:04 -0700, Kaushik S wrote: > > > On Tuesday, September 3, 2013 2:16:53 PM UTC+5:30, Cédric Krier wrote: > > > > > > > > ok, thanks. That would be the way to go for the delete case alone. > > > > > > But when a new entry has been added to the externalDB.privileged_list, > > > there will be no existing patient. So, we can't do the same. > > > > But how could you get patient to invoice that is not recorded as > > patient? > > > > > > > Well, that is because he is a patient, but not a privileged patient :). > > The externalDB maintains its own unique id but for privileged persons only. > There is no id for anyone else. So, the hospital maintains its own unique > id for each patient. We maintain a mapping of the two ids for the > privileged persons. > > So, basically we have a case where the patient is in the hospital's > database. But he has no id in the externalDB. Now suddenly, we get a > notification that a new entry has been made in the privileged list. We need > to know who this is. So, the hospital staff will look at the passport, date > of birth etc and manually match the hospital.patientid to the > externalDB.id. After that, system would know that the existing patient has > become a privileged patient. > > We have this problem because there is no unique id like a social security > number for everyone. I didn't want to go into all these details initially. > If something is not clear please let me know.
So for me, there is fundamentaly something wrong in the design of the workflow. If you can not do the matching, there is no way to get this work correctly. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpmLJKE9hnqM.pgp
Description: PGP signature
