[Top][All Lists]

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

[Gnumed-devel] chronic vs acute, was: Turtorials

From: Karsten Hilbert
Subject: [Gnumed-devel] chronic vs acute, was: Turtorials
Date: Sun, 4 Jul 2010 23:50:22 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Jul 02, 2010 at 05:41:55PM -0300, Rogerio Luz Coelho wrote:

> 2nd - Wishlist:
> I would like to see in the future the Problem List with a separator:
> Chronic  / Acute
> This is somewhat done by the client already by the "grouping" of problems,
> but my thinking would b e as follows:
> - first the problem list could have a difference in permissions for
> modifications in the Chronic list and a Acute list where even Dr.Joe can
> make encounters and episodes. This is specially interesting in settings
> where we have a Clinical Ambulatory and a ER in the same setting or sharing
> the same EMR.
> - second this facilitates the job of doctors while browsing the EMR -
> besides, acute diagnostics generally arenĀ“t supposed to be that precise ...

Rogerio, this is what I wrote back then:

> On Thu, Jun 24, 2010 at 01:52:09PM +0200, Hilbert, Sebastian wrote:
> > Anyone up to creating this for GNUmed ?
> >
> Problem list.
> This shows how Vista seems to consider it a good idea to
> support an immediacy flag on problems.
> The German GP research also knows this flag.
> Do you see value in supporting
>       clin.health_issue.immediacy
>       clin.episode.immediacy
> ?  Values would be NULL (undecided), chronic, and acute.
> We already sort of support this except from a different
> angle:
>       clin.health_issue.is_active

This flag cannot tell which of the active problems is
chronic but it can tell that inactive problems are NOT
chronic :-)

Does that suffice ?

After all, any problem that is thought active warrants
attention, regardless of being chronic or not.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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