gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Re: Managing users: restricting access within GNUmed


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: Managing users: restricting access within GNUmed
Date: Tue, 4 Aug 2009 13:48:52 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Mon, Aug 03, 2009 at 09:58:19PM -0700, Jim Busser wrote:

> I would be interested in comments, either privately or on-list, on the 
> suitability of ideas in my last post, namely

They are, conceptually, entirely suitable. Ways of
implementing them are numerous and thorny. Some ways
are fake.

> Two additional thoughts:
> 
> 1) is_confidential WHERE directive is NULL could support a
> scenario where –  in the absence of a patient stipulation,
> but in a clinician's precautionary judgement – it would be
> prudent to designate something confidential, in order to
> better assist its default exclusion from automated outgoing
> reports
> 
> 2) perhaps the operational (practical) difference between
> 
>    clinical data *coded* "confidential" (which any clinician can see)
> 
> and 
> 
>    clinical data *not* coded "confidential" (which any clinician can see)
>
> lies more outside the praxis where --- as with additional
> thought (1) --- the state of an item being confidential
> could assist some default exclusion from scripted
> abstracting

Yes, that was the intent.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346




reply via email to

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