How a sample moves through LIMS
This page follows a request and its samples from intake until the report is sent. It explains who does each step and what the statuses mean, so you know what to do next and what the people after you expect.
Who this is for: Lab staff and laboratory owners · You need: nothing; each step names its permission
The idea in short
Two things have a status in SmartLIMS:
- The request has one status for the whole order: Received → Configuration → In progress → Validated → Authorized → Ready to send → Sent. People with the "Manage requests" permission move it on with a button on the request page.
- Each parameter line in a work order has its own status, from Not started to Confirmed. The work order shows a summary of its lines. Analysts and reviewers move the lines on.
One move happens by itself: when the request's last result is confirmed, the request becomes Validated. Every other move is a person's decision.
The flow, step by step
- Request received. Reception staff create the request: they pick a form, name each sample they received and click Create request. The request starts as Received. See Lab requests.
- Details filled in. On the request's edit page you fill in the general information, each sample's fields and documents, and the regulatory frameworks. A sample can be a set, with components tested one by one. See Lab requests.
- Configuration. Technicians find the request in Work order setup in the sidebar (see Lab requests) and open it. Click Start configuration. For each sample you choose the people who set it up (the assignees). Each assignee prepares their part and clicks Mark my part done. The sample shows Not configured, Partially configured or Configured.
- Work orders. For each sample you add the testing it needs with Add to work order: a product (all its groups of parameters), one or more groups of parameters, or single parameters. If the sample needs preparation first, add a preparation order with Add preparation work order. See Work orders and results.
- In progress. Click Move to in progress. Each group of parameters in a work order belongs to a department. Members of that department take the work (Take group or Take), click Start, enter values and click Save results.
- For verification. When a result is ready, the analyst clicks Submit for verification.
- Verification. A reviewer opens Result verification in the sidebar and checks each result. They click Verify to accept it, or Send back for rework to return it for redo, with an optional reason.
- Confirmation. A final reviewer opens Result confirmation in the sidebar and clicks Confirm on verified results. They can still make small corrections or send a result back.
- Validated. Confirming the request's last result moves it to Validated by itself (someone with "Manage requests" can also click Move to validated). This is the technical review of the whole request.
- Authorized. A responsible person clicks Authorize. This releases the request. Financial bills authorized requests by default, and a request that came from SmartQC shows the new status there too.
- Sent. The report goes to the client. Prepare for sending marks the request Ready to send while the report is put together; Mark as sent archives and locks it. See Sent and locked.
📷 Screenshot: the request page with the status badge and the Start configuration button
Request statuses
| Status | What it means | Who moves it on |
|---|---|---|
| Received | The request and its samples are logged. Only a request in this status can be deleted. | Someone with "Manage requests" clicks Start configuration. |
| Configuration | Samples are being set up: assignees, work orders, frameworks. | Someone with "Manage requests" clicks Move to in progress. |
| In progress | Testing is under way. | Moves by itself when the last result is confirmed, or someone with "Manage requests" clicks Move to validated. |
| Validated | The results have passed technical review. | Someone with "Manage requests" clicks Authorize. |
| Authorized | The request is released. | Someone with "Manage requests" clicks Prepare for sending or Mark as sent. |
| Ready to send | The report is being prepared for the client. | Someone with "Manage requests" clicks Mark as sent (or Back to Authorized). |
| Sent | The report went to the client; the request is archived and locked. This is the last status. | Nobody. Someone with "Unlock sent requests" can Unlock it, with a reason, to correct it. |
Work order statuses
Each parameter line in a work order has one of these statuses. The work order and each group show a summary: for example, a work order is For verification once every line is at least submitted.
| Status | What it means | Who moves it on |
|---|---|---|
| Not started | Nobody has started this test yet. | The assigned analyst (or any member of the group's department) clicks Start. |
| In progress | The analyst is working on it and entering results. | The analyst clicks Submit for verification. |
| For verification | A result is waiting for review. | A user with "Verify work order tasks" clicks Verify or Send back for rework. |
| Redo | A reviewer sent the result back. The reason is shown with it. | The analyst corrects it and clicks Submit for verification again. |
| Verified | A reviewer accepted the result. | A user with "Confirm work order tasks" clicks Confirm, or a reviewer clicks Send back for rework. |
| Confirmed | The final check is done. | Nobody, unless a reviewer sends it back. |
SmartLIMS records who verified, confirmed or sent back each result, and when. It does not stop the person who entered a result from verifying it; if your quality system needs a second person, make that a rule in your lab and give the permissions accordingly.
Preparation and testing orders
Some samples need a step before testing can even be planned, for example finding out what a textile is made of before choosing the tests. That step is a preparation order.
- A sample can have one preparation order and one testing order.
- A testing order made after the preparation order is linked to it. It shows Waiting on preparation and its result entry stays locked until the preparation order is verified.
- The preparation results are shown on the testing order, so the analyst does not have to look them up.
Preparation is different from redo (doing the same test again) and from reflex testing (adding tests because of a result).
Redo
A reviewer who is not happy with a result clicks Send back for rework and can explain why. The line goes to Redo, any earlier verification is cleared, and the analyst sees the reason. After correcting it, the analyst submits it for verification again.
Reflex testing
Reflex testing means adding tests because of a result, for example a confirmation test after a positive screening.
- During configuration, click Allow reflex testing in the sample's ⋯ menu where this may happen.
- While the request is In progress, click Trigger reflex testing… in that sample's ⋯ menu.
- The request goes back to Configuration for that sample. Add the extra tests to its work order, then move the request to In progress again.
Only samples with reflex testing allowed can trigger it. Each trigger is written to the request's audit trail.
Expert opinion
The expert opinion is the lab's written conclusion. For each request you choose how it is written:
- Per work order (the default): each work order has its own expert opinion.
- Consolidated expert opinion: one opinion on the request covers all samples. Pull from work orders gathers the opinions already written on the work orders into it.
Tips
- Result verification and Result confirmation in the sidebar list only the work orders waiting for that step. See Find work orders.
- A request's history (Activity → History on the request page) lists every status change and who made it.
- Requests can't be put on hold, rejected or cancelled in SmartLIMS yet.