gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] design comment: prescription/drug ID


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] design comment: prescription/drug ID
Date: Fri, 9 Apr 2004 14:49:36 +0200
User-agent: Mutt/1.3.22.1i

> > The clinical schema cannot depend on the drugref schema as
> > GnuMed clients should access drugref via xml rpc. 
> 
> My point is that writing an XML-RPC layer for AMIS could
> be just as hard as rearranging the data and importing it into the drugref 
> schema,
Fully agreed. AMIS we got as source data so we can and should
import it into drugref, given we receive permission to do so.

However, there's a bunch of other drug databases on the
market. People will want to use them, hence interface GnuMed
to them. So we still need the "domained ID" approach. All the
better if that ID is a drugref PUDRI. We won't be able to
successfully *impose* such a thing, however. The only thing we
will impose by attempting that is decrease use of GnuMed.

> > Hilfsmittel) etc etc. 
> > IMO it should be possible to have generic
> > therapy-intent collecting code and branching out to locale
> > specific code upon script instantiation/actuation. I know this
> > could lead to more work.
> I like this idea, but it deviates somewhat from the existing GUI approach.
Not *really*. Richard is doing something similar to that,
collecting prescribed drugs in a list and eventually
generating scripts when pressing the generic top bar print
button.

> What this implies is a "super-widget" that subsumes the prescription, 
> referral and requests editareas
> (and vaccinations, which are really a special case of prescription anyway)
I knew this would show up. When I thought about that I
convinced myself that referrals and requests are *requests*
for therapy, not the actual therapy itself.

Vaccinations, well, yes, one could construe that I am
prescribing the vaccine (and administering it myself instead
of letting the patient do that at home). IMO it's sufficiently
"different" to afford a tailored edit area. Which we already
have.

> Actually, thinking about it, you don't need a editarea at all: have one 
> "permanent" phrasewheel at
> the bottom, and a text box (wxStyledTextCtrl: lots of pretty colours) above 
> which displays the clinical narrative 
> generated so far, and a "prompt" on the bottom left
> which changes as we work, from "health issue", to "presentation", "physical", 
> "impression", "therapy", "drug", "form", and so on.
> We need some method of skipping steps and going back of course.
This is an idea I really like even if only for the standard
SOAP, eg. ongoing notes not directly related to (and recorded
while entering) vaccinations/allergies/referrals/requests.

This is a mini-project. Wiki, anyone ?  :-)

BTW, I do understand one is tempted to merge requests and
referrals. Richard, what's your use case angle here ?

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]