Question 5 of 6 Intermediate Concept
What is the difference between configuration change and validated workflow change?
Short answer
A configuration change alters system settings. A validated workflow change alters the intended or controlled process. One can cause the other, so assess impact rather than relying on the technical label.
Why
Consider adding a new sample status to a LIMS dropdown. Technically it may be configuration, but if it changes when results can be released or how unsuitable samples are rejected, it changes a controlled workflow. Trace the requirement to affected user roles, interfaces, historical records and reports.
Decide the appropriate validation effort from patient or product risk, not whether the change required new code. Compare a low-risk display colour update with a new rule that bypasses second-person review. The latter needs evidence that approvals and segregation of duties remain effective.
Document change control, regression tests, permissions, training and rollback, and where applicable obtain quality approval before release. Avoid describing every configuration change as automatically subject to one fixed regulatory test script. Intended use and governing procedures decide the required scope.
Common mistakes
- Equating no source-code modification with no need for validation or formal change assessment
The interviewer might ask next
Which simple-looking LIMS configuration change could have high patient-safety impact?