Re: [Gnumed-devel] jl-gui - access to log tables

[Karsten Hilbert]

On Tue, Aug 20, 2013 at 07:46:51AM +0200, Jerzy Luszawski wrote:

> > Can you explain the need for:
> > 
> > GRANT SELECT ON TABLE audit.log_health_issue TO "gm-doctors";
> > GRANT SELECT ON TABLE audit.log_episode TO "gm-doctors";
> > GRANT SELECT ON TABLE audit.log_encounter TO "gm-doctors";
> > GRANT SELECT ON TABLE audit.log_clin_narrative TO "gm-doctors";
> 
> I frequently save narratives, then in couple of minutes (eg. after
> re-examining the patient) go back to it to correct/amend it. It is not
> necessary nor convenient to have lots of entries like "correction: arm
> abduction is 90 degrees not 60" when the child shows better on second
> look, or I just need to rephrase something. That is one of the features
> of my EncounterEdit plugin - it allows to *change* the saved narrative
> (I'm not sure if another plugin has this capability now, is certainly
> was missing couple of years ago when I created my plugin.).  
> Of course all changes are audited. And of course I want to know the
> history of these changes, if it exists. For example to check if it was
> really me who entered the data, or one of my colleagues. So I need
> access to audit tables. 
> I also created a possibility to see the history in my EMRMutiView
> plugin. As the audit data are not for everyday use, the presentation is
> very raw and ugly :) just to see the data without launching DB browser.

I understand. I added the above grants.

> > GRANT SELECT ON TABLE audit.log_test_result TO "gm-doctors";
> This and following tables are not used in any particular way by me, but
> I think that doctors should have access to it anyway.

I can in a way understand this sentiment. Since there's no
immediate use of creating those grants ATM let's leave that
until there's a demonstrable need.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346