Quality and ISO/IEC 17025
This page is for laboratories working to ISO/IEC 17025 or preparing for accreditation. It lists which SmartLIMS features support which requirements, and, just as important, what SmartLIMS doesn't do, so you know what your quality system has to cover elsewhere.
Who this is for: Laboratory owners and quality managers, and anyone evaluating SmartLIMS · You need: nothing; this page is an explanation
Important: SmartLIMS supports many ISO/IEC 17025 requirements, but using it doesn't make a laboratory compliant or accredited. Accreditation depends on your own procedures, your validation of the software for your use, and your accreditation body's assessment. Treat this page as input for that work, not as a statement of compliance.
The idea in short
SmartLIMS helps you keep a controlled, traceable path from a customer's request to a reviewed result:
- Requests are recorded consistently. Every request is filled in with a form, and each request keeps the exact form version it was made with.
- Samples are uniquely identified. Requests and samples get tracking numbers that are unique within your company.
- Results are reviewed in steps. Results go through verification and confirmation, and can be sent back for redo, with a reason.
- Access is controlled. People only see and do what their role allows.
- Request history is kept. An append-only audit trail records who moved a request on, when, and in which role.
Some areas that ISO/IEC 17025 covers aren't in SmartLIMS at all, such as equipment and calibration. They are listed under Gaps.
Which features support which requirement
The clause numbers refer to ISO/IEC 17025:2017.
| Clause | Requirement (short) | How SmartLIMS supports it | What stays with you |
|---|---|---|---|
| 4.2 | Confidentiality | Each company's data is kept apart. Users only see their own company. Roles limit what each user can open. See Data, security and audit trail. | Confidentiality agreements, and deciding who gets which role. |
| 6.2 | Personnel | Users, roles and permissions, departments. Separate permissions for verifying and for confirming results. | Competence records, training and formal authorization of staff are not kept in SmartLIMS. |
| 6.4, 6.5 | Equipment, metrological traceability | Not supported. | Keep equipment, calibration and reference-material records elsewhere. |
| 7.1 | Review of requests | Requests are captured through controlled forms, with customers, products and the tests ordered. Each request keeps its form version. | Your review of whether you can do the work, and agreeing deviations with the customer. |
| 7.2 | Selection and validation of methods | Parameters carry unit, LOD, LOQ, measurement uncertainty, reference values and an Accredited mark. | Method validation and verification records are not kept in SmartLIMS. |
| 7.4 | Handling of test items | Unique internal and external tracking numbers per request and sample. Each sample records its received date. Messages can be attached to a sample. | Storage conditions, retention and disposal of samples. |
| 7.5 | Technical records | Each result records who entered it and when, who verified it and who confirmed it. A result sent back shows who sent it back and why, until it is verified again. Request status changes are in the audit trail. | See Gaps: earlier result values are not kept. |
| 7.6 | Measurement uncertainty | Uncertainty can be stored on a parameter and entered with each result. | SmartLIMS doesn't calculate uncertainty. Your uncertainty budgets stay in your own records. |
| 7.7 | Ensuring the validity of results | Two review steps (verification, confirmation). Reflex testing for extra tests a result calls for. | Proficiency testing, control charts and internal quality-control schemes are not in SmartLIMS. |
| 7.8 | Reporting of results | Results are compared with regulatory limits in force on the sample's received date and marked Pass or Fail. Expert opinions per work order or for the whole request. | Test reports are put together from the request's data and can be previewed and printed, but not yet approved and issued (no verdict, signatures or stored issued copy). Your decision rule for statements of conformity. |
| 7.10 | Nonconforming work | Results can be sent back for redo with a reason. Requests can go back to Configuration for reflex testing. | Recording, evaluating and closing nonconformities. |
| 7.11 | Control of data and information management | Permissions, company data separation, audit trail of requests, versioned forms, rulebooks that can't be edited by mistake. | Validating SmartLIMS for your use, and hosting and backup arrangements (see Data, security and audit trail). |
| 8.3, 8.4 | Control of documents and records | Forms are versioned: each saved version is frozen, and requests keep theirs. The request audit trail is append-only. | Your management-system documents and their approval. |
Clause 7.9 (complaints) and the management-system requirements of clause 8 (risks, internal audits, management review, corrective actions) aren't handled in SmartLIMS.
Result review: verification and confirmation
Verification is the second-level check of a result, usually by a senior analyst. Confirmation is the final sign-off. Both are recorded on each result.
| Work order status | Meaning | Who moves it on |
|---|---|---|
| Not started | No work done yet. | The analyst clicks Start. |
| In progress | Results are being entered. | The analyst clicks Submit for verification. |
| For verification | Waiting for the second-level check. | A user with "Verify work order tasks" clicks Verify or Send back for rework. |
| Redo | Sent back to be done again, with an optional reason. | The analyst corrects the result and clicks Submit for verification again. |
| Verified | Checked, waiting for final sign-off. | A user with "Confirm work order tasks" clicks Confirm or Send back for rework. |
| Confirmed | Final sign-off given. | If needed, a user with "Confirm work order tasks" can take it back to Verified, or a reviewer can Send back for rework for redo. |
When a result goes back to Redo or In progress, its earlier verification and confirmation are cleared, so the result must be reviewed again.
See Work orders and results for the full steps.
📷 Screenshot: a work order with one parameter in "For verification", showing who entered the result, and the Verify and Send back for rework buttons
What the audit trail records
Every request has an audit trail. Entries can't be edited or deleted. Each entry records the person, the role they had at that moment, the date and time, and where it applies the old and new status, the sample and a note.
| Entry | Written when |
|---|---|
| Request created | A request is created. |
| Status changed | The request moves to another status. |
| Assignees updated | People are assigned to a sample, or removed. |
| Sample configuration completed | An assignee marks their part of the sample's setup done. |
| Reflex eligibility changed | A sample is marked or unmarked for reflex testing. |
| Reflex testing triggered | Reflex testing is started on a sample. |
| Expert opinion updated | An expert opinion is changed. |
| Sample frameworks updated | A sample's regulatory frameworks change. |
| Request frameworks updated | The request's regulatory frameworks change. |
| Billing updated by Financial | Financial reports a new invoice state or number. See Financial (invoicing). |
Requests brought over from the earlier LABIS system also show their historical entries, such as "Expert opinion confirmed" and "Notice confirmed".
Gaps you need to cover yourself
These are things an assessor may ask about that SmartLIMS doesn't do today:
- Test reports are not yet issued. Test reports shows each request's report as it prints, built from the form, the results and the report template, and you can print it from the browser. But a report can't yet be approved, signed and issued, the verdict isn't given, and no issued copy is stored. Until then, every page says DRAFT; issue and archive the signed report as you do today. See Test reports.
- Earlier result values are not kept. When a result is changed, the new value replaces the old one. Who entered, verified and confirmed it is recorded, but not the previous value.
- Work order actions are not in the request audit trail. Starting, submitting, verifying, confirming and sending back results are stamped on the result itself, not listed in the request's audit trail.
- No enforced four-eyes check. SmartLIMS doesn't stop a person from verifying a result they entered themselves, if they have the permission. If your procedures require independent review, set up roles so that analysts don't have "Verify work order tasks", or check it in your reviews.
- No equipment, calibration or reference-material management.
- No method validation records, competence records or training records.
- No uncertainty calculation. Uncertainty is entered, not calculated.
- No complaints, nonconformity or corrective-action register.
- Hosting and backups are not something you can check from inside SmartLIMS. Contact SmartLabSys for details on hosting and backups.
Tips
- Keep "Verify work order tasks" and "Confirm work order tasks" with different, experienced people. That gives you independent review even though SmartLIMS doesn't enforce it.
- Before you change a form that is in use, remember that existing requests keep their old version. New requests use the new one.
- Mark accredited parameters with Accredited, so the scope is visible where the work is done.
- Write a reason when you click Send back for rework. It tells the analyst what to fix, and stays on the result until it is verified again.