gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] patient object - backend listener


From: Horst Herb
Subject: Re: [Gnumed-devel] patient object - backend listener
Date: Fri, 7 Feb 2003 07:34:41 +1100
User-agent: KMail/1.5

On Thursday 06 February 2003 23:18, Karsten Hilbert wrote:
> So, mainly it boils down to the *same provider* recording
> conflicting data of the same type within the same timeframe.
> Not that's a bit unlikely, agreed. But it can happen, e.g. if
> I (improperly) seize the other doc's ID for the moment.
>
> Anyone still see any flaws here ?

No flaws. Seizing another doctors ID should not be possible. And even if 
post-it ntes on the monitor would make it possible, then you have bigger 
problems than record corruption: fraud.
Clashes within the same provider are not possible without deliberate ID fraud.

> This still leaves us with the question of HOW to detect this
> situation. Shall we add timestamps or some other identifier to
> the rows via the audit parent ?

Timestamps are added automatically in the audit trail.

Horst




reply via email to

[Prev in Thread] Current Thread [Next in Thread]