[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gnumed
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] gnumed |
Date: |
Wed, 13 Oct 2004 23:17:40 +0200 |
User-agent: |
Mutt/1.3.22.1i |
> >There extent to which clin_medication has to replicate a drug database
> >to store script information is an open question.
> >
> so what's the preferred way of storing script information?
Note that clin_medication is NOT AT ALL the table where script
information is stored ! And so the comment says. It is used to
store the current medication of the patient.
Scripts are stored in form_instances/form_data.
> application specific tables that link to clin_medication ?
>
> Is quantity and repeats fairly universal?
There is no such thing as repeats in Germany. For *any* refill
you'll need to get a new prescription from a doctor.
> The web client is barely usable now; it can do demographic ( basic , no
> multiaddresses, no relative linking)
> insert and edit, find ; allergy, medication, clinical narrative, health
> issue , clin episode , vaccination ,
> printable summary page , and INSERT into the database - but no UPDATE :(
Sounds good nonetheless.
> - but at
> least it's using gnumed ;)
> ( better to be a gnu serf , than a ocean informatics.biz lackey , hey?)
Sure, but IF at some poing GnuMed is going to adopt a "foreign"
way of storing and handling clinical data it is very likely to
be OpenEHR. However, for that there need to be bodies of code
implementing that Archetypes stuff.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346