[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] address@hidden: Archetypes: Medication order, risks a
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] address@hidden: Archetypes: Medication order, risks and goals] |
Date: |
Wed, 1 Jun 2005 15:49:11 +0200 |
User-agent: |
Mutt/1.3.22.1i |
On Wed, Jun 01, 2005 at 01:56:41PM +0100, Adrian Midgley wrote:
> > 1) select items (medication orders)
> > - add dosage/instructions/...
> > - add to queue
> 1b having indicated diagnosis, accept or exceptionally decline giving a
> reason all or less of the suggested group of prescription items teh
> hinting engine presents.
> If none is presented, select from the {personal>local formulary> entire
> dictionary.
> Modify dosage instructions if required.
Yes, those are details pertinent to actual implementation.
> > 2) assemble prescription aggregate instance
> > - authorise/kick-off
> > - subject to locale rules, eg target channel, no of items
> > - queue up for outbound processing
> I expect either my computer, or my staff, to handle all that.
Surely. But they are part of what needs to be put into code.
> > 3) process outbound queues
> > - get from queue
> > - process
> > - send to target (print/mail/fax it)
> > It may be easiest to start off with 3). Adrian, what do you
> > think ?
> I think 3 should not usually be a doctor task,
Surely not ! :-)
> but yes, I agree it is a good place to start.
IMO it particularly is the best place for something generic
across EMRs.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346