[Top][All Lists]

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

Re: [Gnumed-devel] Protecting staff privacy

From: Jim Busser
Subject: Re: [Gnumed-devel] Protecting staff privacy
Date: Fri, 08 Jul 2011 07:18:04 -0700

On 2011-07-08, at 4:27 AM, Karsten Hilbert wrote:

> You mean, like, when activating a patient ?

Precisely. The query that identifies the single match (or the multiple matches 
that generates a pick-list) should need to include whether or not the person is 
a member of dem.staff and, if they are a member of staff, the client should not 
actually activate the staff without first prompting

        You have selected a member of staff, for whom
        privacy is especially important. Are you sure
        you want to activate this record?

        default <No>       <Yes>

The default could be "yes" if it is desired to make easier the confirmation. 
That decision may lie in the balance of whether staff often (appropriately) 
activate other staff for their demographics, in order to contact them about 
work-related scheduling or questions about patients on staff days off. Once 
GNUmed supports restrictions, normal staff will presumably lack access to view 
each other's non-demographic (i.e. health) information. At that point, the 
notification is really mainly needed among clinicians who could browse anything 
they wanted (even though they shouldn't) and this is not so much about trust / 
abuse as avoiding the appearance of nosiness as a consequence of stray mouse 
click or wrong choice.

-- Jim

reply via email to

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