On Sep 13, 2008, at 11:02 AM, johnf wrote:
>> Understood. I developed a similar system for a medical
>> records
>> company once. In that case, we didn't delete the old patient records;
>> we simply had a master patient record and a 1:1 patientInfo record;
>> when the information changed, we added a new patient info record, and
>> updated the pointer in the master table. Historical records, though,
>> pointed to the info record, not the master, as these were never
>> changed.
>
> Just a question on database design. Did you consider de-normalizing
> the
> invoice table such that it had the patient info in the header. IOW
> keeping
> the address, etc. that was available at the time of the transaction.
No, because there were many, many tables that referenced patient
information. Having to repeat this denormalized info in each would not
have been efficient. Much simpler to use the patient alias approach.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
