[Loris-dev] Feedback and Behavioural QC permissions

[Rida Abou-Haidar]

Hi Normand,

You are correct, in the current state of things, the Behavioural QC
functionality is an all-or-nothing architecture where you either can or
can't edit the QC on a specific instrument, timepoint and/or candidate.

As for the intended use, I can give you an example from a couple currently
active projects. The data-entry personnel are responsible of transferring
all the data on paper to LORIS, this constitutes the Initial Data-entry
Step.  Once that is done, the instruments are set to status:Complete. The
monitoring personnel then randomly select a certain percentage of the
completed instruments and flag them for monitoring (this step is still
manual at this point but we are hoping on automating it in a near future).
the Instrument (or even entire Timepoints) flagged for monitoring get
reviewed by the proper personnel and any encountered issues with the data
are reported using the feedback panel. This initiates a back and forth on
each specific issue until the issue is resolved and at that time it can be
set to closed (by the monitoring personnel usually) in the feedback panel.

Keep in . mind that feedback can be either at a candidate level, a
timepoint level or an instrument level. I have attached a couple of
diagrams showing our workflows for the CCNA project. Keep in mind that not
all these steps have to be linear, we chose to place them as such to
facilitate our own personal goals but some of these can be inverted and
some completely not used. I do not have any permissions default assignment
unfortunately, we manage that with an internal google sheet giving each
user a role and defining a set of permissions for that role. We are however
looking forward to incorporating a similar feature into loris 19.0 (PR:
https://github.com/aces/Loris/pull/2642)

Hopefully this answers all your questions and sorry for the delayed reply,
Best,
Rida Abou-Haidar
CCNA Software Developer
Montreal Neurological Institute
McGill University
rida.loris at gmail.com



On Mon, Oct 9, 2017 at 11:43 AM Normand Côté <ncote at aviscuriosa.com> wrote:

> Perhaps someone here can enlighten me on something related to the Feedback
> functionality.
>
> We would like our site users to see and respond to Feedback, but not be
> able to change the BVL QC Type and Status in the left panel.  However,
> these functions are both controlled by the "Behavioural QC" (internally "
> bvl_feedback") permission.
>
> Perhaps I've misunderstood the intended use for the Behavioural QC
> functionality.  In our scenario, the site users would do data entry and
> respond to feedback initiated by the DCC.  A clinical monitor attached to
> the DCC would be responsible for hardcopy QC.  If the BVL QC is expected to
> be done by the site, what would you recommend for the DCC-level QC on an
> instrument instance?
>
> Is there any documentation on the expected workflow in Loris, i.e. the
> normal sequence of steps for completion of a study, from data entry to data
> export, with standard permission assignment?  I can piece this together
> from the available functionality, but it would be useful to see how Loris
> was intended to be used.
> _______________________________________________
> Loris-dev mailing list
> Loris-dev at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20171017/f71b3504/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-10-17 at 4.44.00 PM.png
Type: image/png
Size: 535040 bytes
Desc: not available
URL: <http://www.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20171017/f71b3504/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-10-17 at 4.44.10 PM.png
Type: image/png
Size: 1395126 bytes
Desc: not available
URL: <http://www.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20171017/f71b3504/attachment-0003.png>