Difference between revisions of "User:Shawndouglas/sandbox/sublevel17"
Shawndouglas (talk | contribs) |
Shawndouglas (talk | contribs) |
||
Line 95: | Line 95: | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 8.3.2 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''7.10''' The system shall be capable of uniquely identifying documents created in and added to the system. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 7.9 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''8.2''' The system shall allow authorized personnel to document complaints and problems reported to the laboratory or production facility. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.2.2<br />ISO/IEC 17025:2017 6.2.3<br />ISO/IEC 17025:2017 6.2.5<br />ISO/IEC 17025:2017 6.2.6 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''8.8''' The system shall map available system tasks (such as approved test methods) or sample types (such as select agents and toxins) to available training paths and certifications, such that only trained, certified, and experienced personnel are able to perform assigned tasks. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.4.7<br />ISO/IEC 17025:2017 6.4.8 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''10.7''' The system shall allow for the configuration of calibration and maintenance frequency and time frames for—as well as the manual and automatic scheduling of calibration or maintenance of—equipment, instruments, and systems. Available intervals should include days, weeks, months, and years. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.4.4<br />ISO/IEC 17025:2017 6.4.9 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''10.9''' The system shall clearly identify any instrument that is out-of-calibration, beyond its preventative maintenance due date, or under investigation and prevent it from being selected for use. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.4.8 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''10.10''' The system shall be able to show all instances of scheduled calibration, preventative maintenance, and service dates for an instrument. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.4.13 <br />ISO/IEC 17025:2017 6.5 | ||
| style="padding:10px; background-color:white;" | | |||
| style="padding:10px; background-color:white;" |'''10.11''' The system shall be able to link a calibration activity to certified reference material or designated measurement processes. | |||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- | ||
| style="padding:10px;" | | | style="padding:10px;" |ISO/IEC 17025:2017 6.4.8<br />ISO/IEC 17025:2017 6.4.13 | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |'''10.13''' The system shall be able to uniquely identify each instrument and any associated components and maintain that and other information—such as manufacturer, model number, serial number, and calibration and maintenance history—within the system. | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" | | ||
|- | |- |
Revision as of 21:17, 13 January 2023
This is sublevel17 of my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see my discussion page instead. |
Sandbox begins below
Title: What are the key elements of a LIMS to better comply with ISO/IEC 17025?
Author for citation: Shawn E. Douglas
License for content: Creative Commons Attribution-ShareAlike 4.0 International
Publication date: TBD
Introduction
This article will turn to LIMSpec—a laboratory informatics requirements specification document that has evolved significantly over the years—for input into what the base and specialty requirements of a LIMS are in regards to better complying with ISO/IEC 17025. With the current version of LIMSpec having at its core standards such as ASTM E1578-18 Standard Guide for Laboratory Informatics and ISO/IEC 17025 Testing and calibration laboratories, the LIMSpec makes for a durable requirements document that, when used to acquire an informatics solution, can better help a laboratory choose appropriate functionality based upon current standards, regulations, guidance, and more. In particular, this article will look at the touch points of ISO/IEC 17025 with LIMSpec and highlight their importance.
But before we get into specific requirements, let's take a brief look at the connection between a laboratory informatics solution like a laboratory information management system (LIMS) and managing quality in the laboratory.
LIMS and quality management
ISO/IEC 17025 and its connection to various LIMS requirements
|