[Top][All Lists]

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

Re: [Gnumed-devel] Formatting of SOAP row and metadata

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Formatting of SOAP row and metadata
Date: Sat, 23 Jul 2011 22:12:08 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, Jul 23, 2011 at 10:00:49AM -0700, Jim Busser wrote:

> For the sake of argument, what would it take to remove, from the EMR tree 
> view, those multiple and agreed-redundant lines

Careful: ONLY agreed-redundant lines within the context of
the in-context EMR Journal *snippet* browser.

These lines are NOT redundant in the non-contextual
chronologically-only EMR Journal !

Both (GUI) views (EMR Journal and tree journal snippets) are
constructed from the same (database) view
(clin.v_emr_journal and its constituing views).

> e.g.
>         Episode "postop infected laceration L forearm" in health
>         issue "9/2000 extraterrestrial infection"
> Would it need one of
> (1)   redefining clin.v_test_results_journal to not include that metadata


> or
> (2)   defining a new view to be used in EMR tree for such data? 

That would be possible as well.

> IMHO -- pending the opinions of others -- if redundancy of
> information will distract from the purpose of helping to
> understand the history of the patient *, then one of (1) or
> (2) would IMO be warranted.
> -- Jim
> * since a purpose to review the history of the EMR entries themselves is 
> arguably a different purpose which may involve the logs

Or, arguably, understanding when we declared an episode
and/or health issue to exist informs on when we realized
some illness to be present.

I want more opinions on that.

OTOH, regarding the test results - I could agree to remove
the episode meta data from that journal view since we don't
include that meta data information with the other
journal-formatted EMR entries either.

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]