At 3:51 PM -0500 3/4/05, Horst Herb wrote:
I sometimes do enter records for the wrong patient accidentally, and only
notice next time I see that patient.
I then manually graft this record by direct database manipulation, because the
user interface doesn't let me, and this is a PITA.

Emphasizes the value of having that patient photo on the screen!

On account of our having clin_root_item we cannot simply change the patient to whom the record is linked (we wouldn't want to, anyway)

So would we

- first go to patient A who had an inappropriate entry

- - audit this "wrong record" with an audit comment "wrong patient" and a sOAP note to document whether or not any action is needed for patient A based on this wrong entry and then

- for the patient into whose record the data *should have gone* (patient B), assuming you can figure out who that was...

- - somehow clone the content of the obsoleted record(s) into a clin_root_item that belongs to the correct patient, but the user navigation could be tricky - might you want some sort of "memorizing" of the particular entry (or entries) that were obsoleted under patient A, and then navigate to Patient B, select the most suitable health_issue and choose a function to copy the content obsoleted from patient A into new rows for patient B?


_______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel

Reply via email to