gnumed-devel
[Top][All Lists]
Advanced

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

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


From: Karsten Hilbert
Subject: Re: draft Re: [Gnumed-devel] Managing users: restricting access within GNUmed
Date: Thu, 6 Aug 2009 16:14:39 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Wed, Aug 05, 2009 at 11:19:47AM -0700, Jim Busser wrote:

> >a) enable GNUmed to create clerical and clinical users
> >   (currently all users are clinically enabled)
> 
> create/add?
> 
>       gm-clinical
>       gm-clerical

Yes. gm-doctors can be used as gm-clinical.

> ignore for now (as they do nothing)

see the other post

> or deactivate
>       gm-staff_medical
>       gm-staff_office
>       gm-trainees_medical
>       gm-trainees_office

done

> >b) withdraw access to the schemata blobs. and clin. from
> >   clerical users
> 
> would be done in an upgrade db script ?

yes

> >     - then see what happens
> >     - re-design the schemata to conform to this split
> 
> blobs links documents to medical stays... presumably if some
> clerical staff help with the work of scanning (document archiving)
> they might need this?

yes

> also the clerical person who helps with referrals may need
> some extra / partial documents access

A person helping with referrals is not a clerical person.
They are by definition entitled to clinical access.

> trf... (are these triggers?)

yes

> >Note that this approach will make PostgreSQL 8.4 a
> >requirement for GNUmed.
> 
> Would this be a problem only if people are eager to use a future
> gnumed client (once it would depend on pg 8.4) with a server running
> less than Squeeze or equivalent?

Debian/Lenny will likely never have PostgreSQL 8.4. 
Squeeze will, however, so, yes.

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]