Difference between revisions of "User:Shawndouglas/sandbox/sublevel17"

From LIMSWiki
Jump to navigationJump to search
(Replaced content with "<div class="nonumtoc">__TOC__</div> {{ombox | type = notice | style = width: 960px; | text = This is sublevel17 of my sandbox, where I play with features and...")
Tag: Replaced
 
(51 intermediate revisions by the same user not shown)
Line 7: Line 7:


==Sandbox begins below==
==Sandbox begins below==
[[File:Daily Operations in the Core Lab Aboard USNS Comfort (49826052293).jpg|right|350px]]
'''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''': [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International]
'''Publication date''': TBD
==Introduction==
This article will turn to [[LII:LIMSpec 2022 R2|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|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==
{|
| STYLE="vertical-align:top;"|
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0" width="70%"
|-
  | colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"|'''Table 1.''' ISO/IEC 17025:2017's parts that relate to and drive LIMSpec requirements.
|-
  ! style="color:brown; background-color:#ffffee; width:220px;"| ISO/IEC 17025:2017 part(s)
  ! style="color:brown; background-color:#ffffee;"| Associated LIMSpec requirement
  ! style="color:brown; background-color:#ffffee;"| In plain terms ...
|-
  | style="padding:10px;" |ISO/IEC 17025:2017 7.3.3
  | style="padding:10px; background-color:white;" |'''1.9''' The system shall be able to define the collection and sampling details for registered samples or specimens, including container size and type, number of containers, collection date and time, temperature, name of the collector, lot number, storage location, preservation method, collection methods used (standard and nonstandard), sampling methods used, safety concerns, and retention period.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.4.2
  | style="padding:10px; background-color:white;" |'''1.13''' The system shall assign each sample registered in the system a unique identifier using methodologies such as an ID with an incrementing integer or a user-defined naming format.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.4.3
  | style="padding:10px; background-color:white;" |'''1.16''' The system should provide a means to document any undesirable or unexpected characteristics of a submitted sample.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.4.2
  | style="padding:10px; background-color:white;" |'''2.8''' The system should allow for the accurate identification of a physical sample or specimen in the system via barcode or RFID technology.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.7.2
  | style="padding:10px; background-color:white;" |'''2.11''' The system shall allow samples, specimens, and tests to be created and used specifically for capturing data related to unique forms of sampling and testing such as representative sampling, calibration testing, quality control testing, preventative maintenance testing, stability testing, sterility testing, remediated testing, compatibility testing, identity testing, proficiency testing, and service-event-related testing.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 6.2.6<br />ISO/IEC 17025:2017 7.7.1<br />ISO/IEC 17025:2017 7.8.1.1
  | style="padding:10px; background-color:white;" |'''4.4''' The system shall provide one or more levels of review, as well as interpretation and documentation of results—whether entered manually or via an automated process—before release.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.5.1<br />ISO/IEC 17025:2017 7.8.1.1<br />ISO/IEC 17025:2017 7.8.2.1<br />ISO/IEC 17025:2017 7.8.3.1
  | style="padding:10px; background-color:white;" |'''6.5''' The system shall substantiate the status of verified results by using tools like a certificate of analysis, which shall include details like unique identifiers; analysis procedures used; reference intervals; environmental conditions; who provided the results; additional comments, opinions, and interpretations and who provided them; and applicable times and dates.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.8.8
  | style="padding:10px; background-color:white;" |'''6.9''' The system shall clearly identify a changed, amended, or re-issued report as being such, and clearly identify any change of information and reason for change in such a report.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 5.3<br />ISO/IEC 17025:2017 5.5<br />ISO/IEC 17025:2017 8.3.2
  | style="padding:10px; background-color:white;" |'''7.1''' The system shall be capable of creating, managing, and securely holding a variety of document types, while also allowing for the review and approval of those documents using version and release controls.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 (throughout)
  | style="padding:10px; background-color:white;" |'''7.2''' The system shall have the ability to readily provide authorized access to electronic documents such as standard operating procedures, quality manuals, laboratory management plans, instrument manuals, employee medical records, material safety data sheets, information exchange agreements, confidentiality agreements, and other applicable documents to designated personnel and officials.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.5.2<br />ISO/IEC 17025:2017 8.3.2
  | style="padding:10px; background-color:white;" |'''7.3''' The system shall be able to clearly provide the most current version of a document and archive prior versions.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 6.5<br />ISO/IEC 17025:2017 7.2.1.3<br />ISO/IEC 17025:2017 7.3.1–2
  | style="padding:10px; background-color:white;" |'''7.5''' The system shall allow the creation, approval, rejection, and management of sampling and test methods performed at the laboratory, capturing details about the test method, method reference, specifications, assigned limits, holding times, etc. as required by a reference method or regulation.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 6.2.6<br />ISO/IEC 17025:2017 7.2.2.1<br />ISO/IEC 17025:2017 7.2.2.4
  | style="padding:10px; background-color:white;" |'''7.6''' The system shall provide a means for recording validation information for modified existing or new in-house test methods, either as a method itself or through some other means. Validation information such as procedures used, specifications, performance characteristics, and results obtained shall be allowed as input.
  | style="padding:10px; background-color:white;" |
|- 
  | 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;" |'''7.7''' The system shall maintain training and certification records for personnel and allow the assignment of available training paths and certifications to specific personnel, such that only trained, certified, and experienced personnel are able to perform assigned tasks.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.3.2
  | 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;" |ISO/IEC 17025:2017 7.9
  | 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;" |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;" |'''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;" |ISO/IEC 17025:2017 6.4.7<br />ISO/IEC 17025:2017 6.4.8
  | 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;" |ISO/IEC 17025:2017 6.4.4<br />ISO/IEC 17025:2017 6.4.9
  | 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;" |ISO/IEC 17025:2017 6.4.8
  | 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;" |ISO/IEC 17025:2017 6.4.13 <br />ISO/IEC 17025:2017 6.5
  | 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;" |ISO/IEC 17025:2017 6.4.8<br />ISO/IEC 17025:2017 6.4.13
  | 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;" |ISO/IEC 17025:2017 6.4.4–5<br />ISO/IEC 17025:2017 6.4.13 
  | style="padding:10px; background-color:white;" |'''10.15''' The system shall be capable of chronologically logging details for scheduled and unscheduled calibration and maintenance activities for each instrument, including calibration status, calibration standard, date and time of calibration or maintenance, work performed, who conducted it, and signatures of those verifying the completed activities.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.2.1.7<br />ISO/IEC 17025:2017 7.2.2.1<br />ISO/IEC 17025:2017 7.10.2<br />ISO/IEC 17025:2017 8.7
  | style="padding:10px; background-color:white;" |'''16.3''' The system shall be able to record instances of identified nonconformance and method deviation, as well as the actions required to restore the process to conformity. In the case of a planned deviation, the system shall require documentation, justification, proof of validation, adjusted reference intervals, and authorization for the deviated process.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.7.1
  | style="padding:10px; background-color:white;" |'''18.1''' The system should allow authorized users to configure the generation of statistical trending and control charts.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.8.2
  | style="padding:10px; background-color:white;" |'''19.7''' The system shall allow for the documentation and management of internal and external audit activities, while allowing samples, methods, tests, results, reports, documents, and more to be clearly associated with that corresponding audit activity.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.4.2
  | style="padding:10px; background-color:white;" |'''27.3''' The system shall provide a means to choose—based on date and type of data—electronic data and metadata to archive.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.4.2
  | style="padding:10px; background-color:white;" |'''27.4''' The system shall provide a guaranteed means to retrieve and restore archived data and metadata that is readable and accurate.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.4.2
  | style="padding:10px; background-color:white;" |'''27.11''' The system’s data storage tools shall provide data backup and retrieval functions that meet or exceed industry best practices, including producing exact and complete backups that are secure and encrypted from manipulation and loss.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 6.3.3<br />ISO/IEC 17025:2017 6.3.4
  | style="padding:10px; background-color:white;" |'''30.9''' The system should allow for other types of facility monitoring (such as alarm, light, lock, and door statuses) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored systems and their status changes.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 6.3.3<br />ISO/IEC 17025:2017 6.3.4<br />ISO/IEC 17025:2017 7.4.4
  | style="padding:10px; background-color:white;" |'''30.11''' The system should allow for environmental control and monitoring of equipment (such as incubators and freezers) and send notifications when necessary with recommendations for immediate and corrective action. The system should also maintain a log of all such monitored equipment and their associated status changes.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 8.4.2
  | style="padding:10px; background-color:white;" |'''31.4''' The system shall have a mechanism to securely retain data in the system for a specific time period and enable protections that ensure the accurate and ready retrieval of that data throughout the records retention period.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 4.2.1<br />ISO/IEC 17025:2017 7.11.3
  | style="padding:10px; background-color:white;" |'''32.22''' The system shall provide a security interface usable across all modules of the system that secures data and operations and prevents unauthorized access to data and functions.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.11.5
  | style="padding:10px; background-color:white;" |'''33.4''' The system should be well documented by the vendor in comprehensive training material for all aspects of system use, including administration, operation, and troubleshooting.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.11.2
  | style="padding:10px; background-color:white;" |'''33.5''' The system shall be validated initially and periodically, with those validation activities being documented, to ensure the accuracy, consistency, and reliability of system performance and its electronic records.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.8.7.1<br />ISO/IEC 17025:2017 7.11.3<br />ISO/IEC 17025:2017 8.3.2
  | style="padding:10px; background-color:white;" |'''34.4''' The system shall support the ability to define, record, and change the level of access for individual users to system groups, roles, machines, processes, and objects based on their responsibilities, including when those responsibilities change. The system should be able to provide a list of individuals assigned to a given system group, role, machine, process, or object.
  | style="padding:10px; background-color:white;" |
|- 
  | style="padding:10px;" |ISO/IEC 17025:2017 7.11.3
  | style="padding:10px; background-color:white;" |'''34.7''' The vendor shall restrict logical access to database storage components to authorized individuals. If providing a hosted service, the vendor should also restrict physical access to database storage components to authorized individuals. (In the case of an on-site solution, the buyer is responsible for limiting physical access to database storage components to meet 21 CFR Part 11, HIPAA, and CJIS guidelines.)
  | style="padding:10px; background-color:white;" |
|- 
|}
|}
In other words, Table 1 would indicate the following functionality as important to a lab attempting to conform to ISO/IEC 17025:
==Conclusion==
==References==
{{Reflist|colwidth=30em}}
<!---Place all category tags here-->
[[Category:LIMS FAQ articles (added in 2022)]]
[[Category:LIMS FAQ articles (all)]]
[[Category:LIMS FAQ articles on ISO/IEC 17025]]

Latest revision as of 19:57, 1 December 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

Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel17&oldid=53595"