You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Work Flow: Full name here please! Protocol: All protocols Step: Last step of lab protocol
Description:
Adding a comment field or a flexible field in LIMS after a protocol is completed would be useful. Sometimes, you realise things afterwards or discover mistakes, and it would be helpful to add notes in a flexible/open comment field for each protocol. For example, once I uploaded the wrong QC document (although all QC data was manually entered correctly, so no errors were registered in the LIMS). I noticed the mistake two weeks later, and it would have been great to be able to attach the correct file at the end of the protocol as a 'note'.
The text was updated successfully, but these errors were encountered:
KSV found that the permission to modify completed steps can be assigned to specific user roles by the LIMS administrator. See more here
We will discuss which specific users/roles that will have this possibility, so that any completed step changes are performed in a QA compliant way
idalindegaard
changed the title
Flexible section after a LIMS protocol for "Notes"
Enable permission to modify/add notes in completed steps
Oct 14, 2024
Lims Issue
For definitions of headings below see Basic Concepts.
Work Flow: Full name here please!
Protocol: All protocols
Step: Last step of lab protocol
Description:
Adding a comment field or a flexible field in LIMS after a protocol is completed would be useful. Sometimes, you realise things afterwards or discover mistakes, and it would be helpful to add notes in a flexible/open comment field for each protocol. For example, once I uploaded the wrong QC document (although all QC data was manually entered correctly, so no errors were registered in the LIMS). I noticed the mistake two weeks later, and it would have been great to be able to attach the correct file at the end of the protocol as a 'note'.
The text was updated successfully, but these errors were encountered: