Re: [Gnumed-devel] Gnumed on Debian 'Sid' (sort of)

[Karsten Hilbert]

Michael,

> The problem seems to lie somewhere in the bootstrapping.
> 
> The error message I get is:
> "no staff name on file for current database login"
> (details below)
> 
> This has got me a bit confused 'cause I can access the database
> (gnumed) with pgaccess and see 'test-doc' which looks like a staff
> to me.
The notion of "user" has been enhanced recently. We now
require DB logins (ie PostgreSQL accounts) to correspond to an
explicit staff member in table staff (v_staff is nicer).
Consequently, only persons known in identity/names can
be listed as staff members, eg GnuMed does not differentiate
between staff members, fellow practitioners, patients, etc.
They are all "identities". Only through data in additional
tables do they take on particular roles.

Why is this so ? GnuMed (medically !) attributes entered data
to a "real" staff member, not a DB account. Eventually it will
(should it ?) be possible to enter data "on behalf of" another
staff member (eg. Dr.X did such and such a procedure which is
entered by nurse Y). This will require an additional
authentication step such that Dr.X gives his nurse Y
permission to enter data that's content-wise attributed to
Dr.X.

At the time the only mapped DB account is "any-doc" which
corresponds to Dr.Leonard McCoy for whom test data is included
in the SQL sources. I do recommend people add mappings (or mail
suggestions to me) for test-doc etc. I'd prefer virtual but
well-known staff members from, say, Deep Space 9, Enterprise,
what-not :-)

Good to see you back. Happy New Year to you.

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