Leave a comment at the end of this page or email contact@krishagni.com
Configure Role-Based Workflows (v8.1)
Introduction
In some workflows, the clinic staff collects primary specimens at the collection site. On receiving the specimen, the biobank technician processes it into desired aliquots and stores them in the freezer. The clinic staff need not have access to the aliquots, storage containers, etc.
To achieve this, v8.1 supports:
Configuring add/edit screens based on user roles
Configuring specimen collection table
Role-Based Display of Fields
When collecting primary specimens, the clinic staff should not see the container fields. At the same time, the biobank technician needs to store the specimens and add other specimen details. To restrict specific fields on add, edit, and overview pages, you can add rules in the CP workflow. Refer to the wiki page for more information.
Specimen Collection Table
During the specimen collection step, the clinic staff should only see the fields they enter the data for. All the other fields, like containers, etc., should be hidden from them. Refer to the wiki page for more information on configuring the specimen collection table.
Restrictions to Update Records
The clinic staff collects specimens and sends them to the lab, and then the biobank technician receives the specimens.
Once specimens are received, the clinic staff should not be able to edit those specimens/visits/participants. To enable this feature, you can follow the steps:
Log in as a super admin and navigate to 'Settings'.
Search for the 'Coordinator Role' property and add the role name.
The clinic staff cannot edit the below-mentioned once this setting is enabled:
Received specimens.
Visit- if any of the specimens within the visit is received.
Participant- if any of the specimens from the collected visits are received.
The clinic staff will get limited access to operations in the system. All the buttons except the ones listed below will be hidden from them:
Buttons Hidden from Coordinator
When this feature is enabled, the Coordinators can only see the needed options for their workflows.
Page | Buttons Visible | Tabs Visible |
|---|---|---|
Participant Overview | Edit, Add to Another Protocol, Delete | Visits, Specimens, Forms, Specimen Tree |
Participant list view | Add participant, View specimens, More (Generate CP reports, View CP details, Dashboards, Survey Invitations) |
|
Visits Overview | Edit, Add specimen, Delete, Specimens Manifest | Forms, Specimen Tree |
Specimen Overview | Edit, Add to cart, Delete | Forms, Specimen Tree |
Specimen list view | Add participant, Actions (Edit, Delete, Service Request), Add to cart, View participants, More (Generate CP reports, View CP details, Dashboards, Survey Invitations) |
|
Carts | Edit, Print, Delete, Close, Receive, Add/Edit Event, Request Note: They will not be able to perform operations like print, receive, add/edit events for the CP that they are coordinators to. |
|
Query | Edit, Print, Delete, Close, Receive, Add/Edit Event, Request Note: They will not be able to perform operations like print, receive, add/edit events for the CP that they are coordinators to. |
|
Example CP Definition
Leave a comment at the end of this page or email contact@krishagni.com