Re: [Gnumed-devel] Mistaken Patients - PNG enclosed (was: A question re demographics)

[Jim Busser]

On Jul 20, 2004, at 12:40 AM, Horst Herb wrote:

> > > he leaves the door he says" Dr, that script is wrong - you have 
> > > written
> > > it for Mr Bloggs, but I am Mr Jones". That after I diligently 
> > > documented
> > > everything, of course.
>
> Cut & paste helps a little

but presumably you cannot have each patient "active" in separate 
windows (which would facilitate going back and forth) - or can you? If 
not, you would have to copy what you want, and then go back to some 
sort of list to activate the destination patient (thereby deactivating 
the source patient) - a LOT of work!

> but for the *wrong* patient record to go through
> and manually delete all entries (prescriptions, past history, SOAP,
> allergies ...)

Instead of deleting, why not just update the records by linking to the 
RIGHT patient? I can see no reason, other than doing so accurately / 
completely. Would seem to require that, for example, for a SOAP entry:

- clin_narrative rows be updated on:
- - fk_encounter  - doable in one step for all affected rows
      e.g. by selecting what SHOULD have been the correct
      patient appointment) and
- - fk_episode - a bit more work but still a savings?
      i.e. if there are three RFEs, each would need to be mapped
      to a suitable episode of the target patient, however once done
      for any one RFE, the related SOAP / AOEs could "move" with it
- the ancestor clin_root_item would have its corresponding
      fk_ fields updated to match (hence will also have been audited)

The wrong patient could have had new clin_health_issues and episodes 
created which would either need to be deleted or updated, depending on 
whether suitable values already exist.

Is the above a sensible way to do things, and does it depend only on 
someone who makes this error often enough (or who gets frustrated soon 
enough) that it becomes worth their while to get it coded up?

PS what would the reason be that the table clin_root_item specifies an 
Fkey (for example, clin_episode.id) while the table clin_narrative does 
not?