Re: access to review audits (was Re: [Gnumed-devel] encounter edit before final save)

[James Busser]

On 13-Aug-08, at 1:48 PM, Karsten Hilbert wrote:

> On Wed, Aug 13, 2008 at 02:48:28PM -0300, Rogerio Luz wrote:
>
> > Couldn´t the RR(RR) field in the left ... in the list of exames be  
> > made some
> > other colour ... for example RED ??
> What would that mean ? Which of the columns was edited when
> the row header changes color ?

It would seem that it would have to be the cell(s) --- the result or  
results themselves --- which had been edited, which would need to be  
made another colour.

> > Do you understad? when something is edited after a save it would  
> > turn RED,
> > so when you open the exam list ... RED means I need to look this  
> > again?
> Nah, red is way to in-your-face for that.

Amber (yellow-orange) on traffic signals denotes caution so perhaps  
amber or an even lighter colour (flax, light peach) might do?

        http://forums.bf2s.com/viewtopic.php?id=46435

re progress notes, Karsten replied in the thread "Wiki user guide now  
more fully linked"
> Note that so far the row_version is only taken into account
> when displaying test results. Narrative doesn't yet have it.

Is it manageable to be added to the next database version, and what  
options should be considered for making a revision > 0 visible?

I had been worried that colorization could be too distracting in the  
EMR tree, however if the problem list were collapsed at the episode  
level, and if only some subset of the "open" episodes was exposed,  
and if within an episode not all encounters would be constantly in  
view (they may be scrolled out of view) then the  
"offending" (distracting) encounters may not even be in view all the  
time. Thus any distraction by color, when it would be for trivial  
changes, may only come into view when relevant. Is this analysis  
correct?