gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] a writeup on EMR structure


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] a writeup on EMR structure
Date: Mon, 5 May 2003 12:44:45 +0200
User-agent: Mutt/1.3.22.1i

>> Clinical narrative
>> ------------------
> Can I propose that clin_narrative be the ancestor table of the other
> tables such as script, allergy, instead of linking to it. A search on
> clin_narrative allows us to access all free string history notes,
> but avoids the overhead of linking (and the danger of mis-linking, as 
> clin_narrative has its its own link to id_patient)
Wait, re my previous concern about not being able to have more
than one free text field in *specific* EMR content tables if
clin_narrative is made an ancestor of clin_*. The solution is,
of course, that one can happily link to direct entries in ones
ancestor table (sort of linking to 'itself'). Hence,
clin_narrative would act as a non-specific clinical item
table.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346




reply via email to

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