Difference between revisions of "Template:LIMSpec/Introduction and methodology"
Shawndouglas (talk | contribs) (Updated content for 2022.) |
Shawndouglas (talk | contribs) m (Access date) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
===Introduction=== | ===Introduction=== | ||
[[File:Systems Requirement Analysis.jpg|700px|right]]Merriam-Webster defines a "specification" as "a detailed precise presentation of something or of a plan or proposal for something."<ref name="MWSpec">{{cite web |url=https://www.merriam-webster.com/dictionary/specification |title=specification |work=Merriam-Webster |publisher=Merriam-Webster, Inc |accessdate= | [[File:Systems Requirement Analysis.jpg|700px|right]]Merriam-Webster defines a "specification" as "a detailed precise presentation of something or of a plan or proposal for something."<ref name="MWSpec">{{cite web |url=https://www.merriam-webster.com/dictionary/specification |title=specification |work=Merriam-Webster |publisher=Merriam-Webster, Inc |accessdate=07 December 2022}}</ref> In other words, an existing or theoretical product, concept, or idea is presented in detail for a particular audience. In a broad sense, detailing the specifics about a project, concept, or idea to others is just common sense. This applies just as well to the world of software development, where a software requirements specification is essential for preventing the second most commonly cited reason for project failure: poor requirements management.<ref name="BiegRequire14">{{cite web |url=https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/requirements-management.pdf |format=PDF |title=Introduction |work=Requirements Management: A Core Competency for Project and Program Success |author=Bieg, D.P. |publisher=Project Management Institute |page=3 |date=August 2014 |accessdate=07 December 2022}}</ref> | ||
In fact, the ISO/IEC/IEEE 29148:2018 standard (a conglomeration of what was formerly IEEE 830 and other standards) is in place to help specify "the required processes implemented in the engineering activities that result in requirements for systems and software products" and provides guidelines for how to apply those requirements.<ref name="ISO29148">{{cite web |url=https://www.iso.org/standard/72089.html |title=ISO/IEC/IEEE 29148:2018 |publisher=International Organization for Standardization |date=November 2018 |accessdate= | In fact, the ISO/IEC/IEEE 29148:2018 standard (a conglomeration of what was formerly IEEE 830 and other standards) is in place to help specify "the required processes implemented in the engineering activities that result in requirements for systems and software products" and provides guidelines for how to apply those requirements.<ref name="ISO29148">{{cite web |url=https://www.iso.org/standard/72089.html |title=ISO/IEC/IEEE 29148:2018 |publisher=International Organization for Standardization |date=November 2018 |accessdate=07 December 2022}}</ref> The standard describes the characteristics that make up quality software requirement development, including aspects such as<ref name="SeibertHowDoYou11">{{cite web |url=https://hubtechinsider.wordpress.com/2011/07/28/how-do-you-write-software-requirements-what-are-software-requirements-what-is-a-software-requirement/ |title=How do you write software requirements? What are software requirements? What is a software requirement? |work=HubTechInsider |author=Seibert, P. |date=28 July 2011 |accessdate=07 December 2022}}</ref>: | ||
* correctly describing system behavior; | * correctly describing system behavior; | ||
Line 10: | Line 10: | ||
* unequivocally ensuring the requirements are testable, modifiable, and traceable. | * unequivocally ensuring the requirements are testable, modifiable, and traceable. | ||
A requirement typically comes in the form of a statement that begins with "the system/user/vendor shall/should ..." and focuses on a provided service, reaction to input, or expected behavior in a given situation. The statement may be abstract (high-level) or specific and detailed to a precise function. The statement may also be of a functional nature, describing functionality or services in detail, or of a non-functional nature, describing the constraints of a given functionality or service and how it's rendered. An example of a functional software requirement could be "the user shall be able to query either all of the initial set of databases or select a subset from it." This statement describes specific functionality the system should have. On the other hand, a non-functional requirement, for example, may state "the system's query tool shall conform to the ABC 123-2014 standard." The statement describes a constraint placed upon the system's query functionality. Once compiled, a set of requirements can serve not only to strengthen the software requirements specification, but the requirements set can also be used for bidding on a contract or serve as the basis for a specific contract that is being finalized.<ref name="MemonSoftware10">{{cite web |url=https://www.cs.umd.edu/~atif/Teaching/Spring2010/Slides/3.pdf |format=PDF |title=Software Requirements: Descriptions and specifications of a system |author=Memon, A. |publisher=University of Maryland |date=Spring 2010 |accessdate= | A requirement typically comes in the form of a statement that begins with "the system/user/vendor shall/should ..." and focuses on a provided service, reaction to input, or expected behavior in a given situation. The statement may be abstract (high-level) or specific and detailed to a precise function. The statement may also be of a functional nature, describing functionality or services in detail, or of a non-functional nature, describing the constraints of a given functionality or service and how it's rendered. An example of a functional software requirement could be "the user shall be able to query either all of the initial set of databases or select a subset from it." This statement describes specific functionality the system should have. On the other hand, a non-functional requirement, for example, may state "the system's query tool shall conform to the ABC 123-2014 standard." The statement describes a constraint placed upon the system's query functionality. Once compiled, a set of requirements can serve not only to strengthen the software requirements specification, but the requirements set can also be used for bidding on a contract or serve as the basis for a specific contract that is being finalized.<ref name="MemonSoftware10">{{cite web |url=https://www.cs.umd.edu/~atif/Teaching/Spring2010/Slides/3.pdf |format=PDF |title=Software Requirements: Descriptions and specifications of a system |author=Memon, A. |publisher=University of Maryland |date=Spring 2010 |accessdate=07 December 2022}}</ref> | ||
Over the years, a wide variety of companies, consultants, and researchers have compiled public and private software requirements specifications for [[laboratory informatics]] systems. These compiled lists of requirements for how a given laboratory informatics solution should be developed, delivered, and maintained have changed as technology and user demand have evolved. Often times, these requirements documents turn into a mix of "wishlist" requirements from potential and active clients, as well as regulation-mandated requirements. The wishlist items aren't necessarily ignored by developers, but they do in fact have to be prioritized as "nice to have" or "essential to system operation," or something in between.<ref name="AasemAnalysis10">{{cite journal |title=Analysis and optimization of software requirements prioritization techniques |author=Aasem, M.; Ramzan, M.; Jaffar, A. |journal=Proceedings from the 2010 International Conference on Information and Emerging Technologies |pages=1–6 |year=2010 |doi=10.1109/ICIET.2010.5625687}}</ref><ref name="Hirsch10Steps13">{{cite web |url=https://www.phase2technology.com/blog/successful-requirements-gathering |title=10 Steps To Successful Requirements Gathering |author=Hirsch, J. |publisher=Phase2 Technology, LLC |date=22 November 2013 |accessdate= | Over the years, a wide variety of companies, consultants, and researchers have compiled public and private software requirements specifications for [[laboratory informatics]] systems. These compiled lists of requirements for how a given laboratory informatics solution should be developed, delivered, and maintained have changed as technology and user demand have evolved. Often times, these requirements documents turn into a mix of "wishlist" requirements from potential and active clients, as well as regulation-mandated requirements. The wishlist items aren't necessarily ignored by developers, but they do in fact have to be prioritized as "nice to have" or "essential to system operation," or something in between.<ref name="AasemAnalysis10">{{cite journal |title=Analysis and optimization of software requirements prioritization techniques |author=Aasem, M.; Ramzan, M.; Jaffar, A. |journal=Proceedings from the 2010 International Conference on Information and Emerging Technologies |pages=1–6 |year=2010 |doi=10.1109/ICIET.2010.5625687}}</ref><ref name="Hirsch10Steps13">{{cite web |url=https://www.phase2technology.com/blog/successful-requirements-gathering |title=10 Steps To Successful Requirements Gathering |author=Hirsch, J. |publisher=Phase2 Technology, LLC |date=22 November 2013 |accessdate=07 December 2022}}</ref><ref name="BurrissSoftware07">{{cite web |url=http://sce2.umkc.edu/BIT/burrise/pl/requirements/ |archiveurl=https://web.archive.org/web/20190724173601/http://sce2.umkc.edu/BIT/burrise/pl/requirements/ |title=Requirements Specification |work=CS451R, University of Missouri–Kansas City |author=Burris, E. |publisher=University of Missouri–Kansas City |date=2007 |archivedate=24 July 2019 |accessdate=07 December 2022}}</ref> While this reasonable mix of requirements has served informatics software developers well<ref name="HofmannRequire01">{{cite journal |title=Requirements engineering as a success factor in software projects |author=Hofmann, H.F.; Lehner, F. |journal=IEEE Software |volume=18 |issue=4 |pages=58–66 |year=2001 |doi=10.1109/MS.2001.936219}}</ref>, sometimes a fresh approach is required. | ||
What follows is an attempt to look less at the wishlists of laboratories and more directly at what requirements current regulatory schemes, industry standards, and organizational guidelines place on the ever-evolving array of laboratory informatics systems being developed today. What does the United States' [[21 CFR Part 11]] have to say about how your [[laboratory information management system]] (LIMS), [[laboratory information system]] (LIS), [[electronic laboratory notebook]] (ELN), and other systems operate? What does the European Union's Annex 11 dictate in those same regards? The following five chapters list those requirements, supported by one or more regulations, standards, and guidelines. The final chapter discusses how to best put this requirements specification to use. | What follows is an attempt to look less at the wishlists of laboratories and more directly at what requirements current regulatory schemes, industry standards, and organizational guidelines place on the ever-evolving array of laboratory informatics systems being developed today. What does the United States' [[21 CFR Part 11]] have to say about how your [[laboratory information management system]] (LIMS), [[laboratory information system]] (LIS), [[electronic laboratory notebook]] (ELN), and other systems operate? What does the European Union's Annex 11 dictate in those same regards? The following five chapters list those requirements, supported by one or more regulations, standards, and guidelines. The final chapter discusses how to best put this requirements specification to use. | ||
Line 21: | Line 21: | ||
This LIMSpec borrows from that requirements checklist and then adds more to it from a wide variety of sources. An attempt has been made to find the most relevant regulations, standards, and guidance that shape how a compliant laboratory informatics system is developed and maintained. However, this should definitely be considered a work in progress, with more to be added with additional public and private comment on missing sources. | This LIMSpec borrows from that requirements checklist and then adds more to it from a wide variety of sources. An attempt has been made to find the most relevant regulations, standards, and guidance that shape how a compliant laboratory informatics system is developed and maintained. However, this should definitely be considered a work in progress, with more to be added with additional public and private comment on missing sources. | ||
That said, this | That said, this fourth revision (December 2022) taps into more than 130 resources, including the following: | ||
{| | {| | ||
Line 27: | Line 27: | ||
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0" width="80%" | {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0" width="80%" | ||
|- | |- | ||
| colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"|'''Table 1.''' Regulations, standards, guidance, and other documents guiding LIMSpec development. <sup>*</sup> indicates added, updated, or revised for 2022 update. | | colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"|'''Table 1.''' Regulations, standards, guidance, and other documents guiding LIMSpec development. <sup>*</sup> indicates added, updated, or revised for December 2022 update. | ||
|- | |- | ||
! style="color:brown; background-color:#ffffee; width:500px;"| Regulation, Specification, or Guidance | ! style="color:brown; background-color:#ffffee; width:500px;"| Regulation, Specification, or Guidance | ||
Line 35: | Line 35: | ||
| style="padding:10px; background-color:white;" |Office of Personnel Management > Civil Service Regulations > Programs for Specific Positions and Examinations (Miscellaneous) > Information Security Responsibilities for Employees who Manage or Use Federal Information Systems > Information systems security awareness training program | | style="padding:10px; background-color:white;" |Office of Personnel Management > Civil Service Regulations > Programs for Specific Positions and Examinations (Miscellaneous) > Information Security Responsibilities for Employees who Manage or Use Federal Information Systems > Information systems security awareness training program | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/7/part-91 7 CFR Part 91] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/7/part-91 7 CFR Part 91] | ||
| style="padding:10px; background-color:white;" |Agricultural Marketing Service (Standards, Inspections, Marketing Practices), Department of Agriculture > Commodity Laboratory Testing Programs > Services and General Information | | style="padding:10px; background-color:white;" |Agricultural Marketing Service (Standards, Inspections, Marketing Practices), Department of Agriculture > Commodity Laboratory Testing Programs > Services and General Information | ||
|- | |- | ||
Line 41: | Line 41: | ||
| style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Possession, Use, and Transfer of Select Agents and Toxins | | style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Possession, Use, and Transfer of Select Agents and Toxins | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/9/part-2 9 CFR Part 2] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/9/part-2 9 CFR Part 2] | ||
| style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Animal Welfare > Regulations | | style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Animal Welfare > Regulations | ||
|- | |- | ||
Line 47: | Line 47: | ||
| style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Viruses, Serums, Toxins, and Analogous Products; Organisms and Vectors > Possession, Use, and Transfer of Select Agents and Toxins | | style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Viruses, Serums, Toxins, and Analogous Products; Organisms and Vectors > Possession, Use, and Transfer of Select Agents and Toxins | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/10/part-20 10 CFR Part 20] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/10/part-20 10 CFR Part 20] | ||
| style="padding:10px; background-color:white;" |Nuclear Regulatory Commission > Standards for Protection Against Radiation | | style="padding:10px; background-color:white;" |Nuclear Regulatory Commission > Standards for Protection Against Radiation | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/10/part-30 10 CFR Part 30] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/10/part-30 10 CFR Part 30] | ||
| style="padding:10px; background-color:white;" |Nuclear Regulatory Commission > Rules of General Applicability to Domestic Licensing of Byproduct Material | | style="padding:10px; background-color:white;" |Nuclear Regulatory Commission > Rules of General Applicability to Domestic Licensing of Byproduct Material | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-1 21 CFR Part 1]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > General Enforcement Regulations | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-7 21 CFR Part 7] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-7 21 CFR Part 7] | ||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > Enforcement Policy | | style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > Enforcement Policy | ||
Line 62: | Line 65: | ||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > Good Laboratory Practice for Nonclinical Laboratory Studies | | style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > Good Laboratory Practice for Nonclinical Laboratory Studies | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-106 21 CFR Part 106]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Infant Formula Requirements Pertaining to Current Good Manufacturing Practice, Quality Control Procedures, Quality Factors, Records and Reports, and Notifications | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-110 21 CFR Part 110]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Current Good Manufacturing Practice in Manufacturing, Packing, or Holding Human Food | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-111 21 CFR Part 111]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Current Good Manufacturing Practice in Manufacturing, Packaging, Labeling, or Holding Operations for Dietary Supplements | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-112 21 CFR Part 112]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Standards for the Growing, Harvesting, Packing, and Holding of Produce for Human Consumption | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-114 21 CFR Part 114]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Acidified Foods | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-117 21 CFR Part 117]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Current Good Manufacturing Practice, Hazard Analysis, and Risk-based Preventive Controls for Human Food | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-120 21 CFR Part 120]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Hazard Analysis and Critical Control Point (HACCP) Systems | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-123 21 CFR Part 123]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Fish and Fishery Products | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-129 21 CFR Part 129]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Food for Human Consumption > Processing and Bottling of Bottled Drinking Water | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-211 21 CFR Part 211] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-211 21 CFR Part 211] | ||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs: General > Current Good Manufacturing Practice for Finished Pharmaceuticals | | style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs: General > Current Good Manufacturing Practice for Finished Pharmaceuticals | ||
Line 77: | Line 107: | ||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs for Human Use > Investigational New Drug Application | | style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs for Human Use > Investigational New Drug Application | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-507 21 CFR Part 507]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Animal Drugs, Feeds, and Related Products > Current Good Manufacturing Practice, Hazard Analysis, and Risk-based Preventive Controls for Food for Animals | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-606 21 CFR Part 606] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-606 21 CFR Part 606] | ||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Biologics > Current Good Manufacturing Practice for Blood and Blood Components | | style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Biologics > Current Good Manufacturing Practice for Blood and Blood Components | ||
Line 122: | Line 155: | ||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Water Programs > National Primary Drinking Water Regulations | | style="padding:10px; background-color:white;" |Environmental Protection Agency > Water Programs > National Primary Drinking Water Regulations | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-262 40 CFR Part 262] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-262 40 CFR Part 262] | ||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Solid Wastes > Standards Applicable to Generators of Hazardous Waste | | style="padding:10px; background-color:white;" |Environmental Protection Agency > Solid Wastes > Standards Applicable to Generators of Hazardous Waste | ||
|- | |- | ||
Line 143: | Line 176: | ||
| style="padding:10px; background-color:white;" |Public Health Service, Department of Health and Human Services > Quarantine, Inspection, Licensing > Select Agents and Toxins | | style="padding:10px; background-color:white;" |Public Health Service, Department of Health and Human Services > Quarantine, Inspection, Licensing > Select Agents and Toxins | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/42/part-93 42 CFR Part 93] | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/42/part-93 42 CFR Part 93] | ||
| style="padding:10px; background-color:white;" |Public Health Service, Department of Health and Human Services > Health Assessments and Health Effects Studies of Hazardous Substances Releases and Facilities > Public Health Service Policies on Research Misconduct | | style="padding:10px; background-color:white;" |Public Health Service, Department of Health and Human Services > Health Assessments and Health Effects Studies of Hazardous Substances Releases and Facilities > Public Health Service Policies on Research Misconduct | ||
|- | |- | ||
Line 161: | Line 194: | ||
| style="padding:10px; background-color:white;" |Department of Health and Human Services > Health Information Technology > Health Information Technology Standards, Implementation Specifications, and Certification Criteria and Certification Programs for Health Information Technology | | style="padding:10px; background-color:white;" |Department of Health and Human Services > Health Information Technology > Health Information Technology Standards, Implementation Specifications, and Certification Criteria and Certification Programs for Health Information Technology | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.uslegalforms.com/form-library/256001-c211-specific-checklist-combined-iso-iec-17025-and-veterinary-laboratory-accreditation A2LA C211, Specific Checklist, Combined ISO/IEC 17025 and Veterinary Laboratory Accreditation Program] | | style="padding:10px; width:350px;" |[https://www.govinfo.gov/app/details/FR-1996-07-25/96-17837/summary 61 FR 38806]<sup>*</sup> | ||
| style="padding:10px; background-color:white;" |Food Safety and Inspection Service, Department of Agriculture > Pathogen Reduction; Hazard Analysis and Critical Control Point (HACCP) Systems | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.uslegalforms.com/form-library/256001-c211-specific-checklist-combined-iso-iec-17025-and-veterinary-laboratory-accreditation A2LA C211, Specific Checklist, Combined ISO/IEC 17025 and Veterinary Laboratory Accreditation Program] | |||
| style="padding:10px; background-color:white;" |American Association for Laboratory Accreditation | | style="padding:10px; background-color:white;" |American Association for Laboratory Accreditation | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.359.5506&rep=rep1&type=pdf A2LA C223, Specific Checklist, Forensic Examination Accreditation Program-Testing] | | style="padding:10px; width:350px;" |[https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.359.5506&rep=rep1&type=pdf A2LA C223, Specific Checklist, Forensic Examination Accreditation Program-Testing] | ||
| style="padding:10px; background-color:white;" |American Association for Laboratory Accreditation | | style="padding:10px; background-color:white;" |American Association for Laboratory Accreditation | ||
|- | |- | ||
Line 176: | Line 212: | ||
| style="padding:10px; background-color:white;" |American Board of Forensic Toxicology | | style="padding:10px; background-color:white;" |American Board of Forensic Toxicology | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.acmg.net/ACMG/Medical-Genetics-Practice-Resources/Genetics_Lab_Standards/ACMG/Medical-Genetics-Practice-Resources/Genetics_Lab_Standards.aspx ACMG Technical Standards for Clinical Genetics Laboratories] | | style="padding:10px; width:350px;" |[https://www.acmg.net/ACMG/Medical-Genetics-Practice-Resources/Genetics_Lab_Standards/ACMG/Medical-Genetics-Practice-Resources/Genetics_Lab_Standards.aspx ACMG Technical Standards for Clinical Genetics Laboratories] | ||
| style="padding:10px; background-color:white;" |American College of Medical Genetics and Genomics | | style="padding:10px; background-color:white;" |American College of Medical Genetics and Genomics | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.aihaaccreditedlabs.org/Policies/Pages/default.aspx AIHA-LAP Policies 2022] | | style="padding:10px; width:350px;" |[https://www.aihaaccreditedlabs.org/Policies/Pages/default.aspx AIHA-LAP Policies 2022] | ||
| style="padding:10px; background-color:white;" |American Industrial Hygiene Association Laboratory Accreditation Programs | | style="padding:10px; background-color:white;" |American Industrial Hygiene Association Laboratory Accreditation Programs | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.aphl.org/aboutAPHL/publications/Documents/GH-2019May-LIS-Guidebook-web.pdf APHL 2019 LIS Project Management Guidebook] | | style="padding:10px; width:350px;" |[https://www.aphl.org/aboutAPHL/publications/Documents/GH-2019May-LIS-Guidebook-web.pdf APHL 2019 LIS Project Management Guidebook] | ||
| style="padding:10px; background-color:white;" |Association of Public Health Laboratories | | style="padding:10px; background-color:white;" |Association of Public Health Laboratories | ||
|- | |- | ||
Line 200: | Line 236: | ||
| style="padding:10px; background-color:white;" |ASTM E1578-18 ''Standard Guide for Laboratory Informatics'' | | style="padding:10px; background-color:white;" |ASTM E1578-18 ''Standard Guide for Laboratory Informatics'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://elss.cap.org/elss/ShowProperty?nodePath=/UCMCON/Contribution%20Folders/DctmContent/education/OnlineCourseContent/2017/LAP-TLTM/misc/lam.pdf CAP Laboratory Accreditation Manual] | | style="padding:10px; width:350px;" |[https://cdn.scsglobalservices.com/files/program_documents/brc_food_standard_8_0.pdf BRC GSFS, Issue 8]<sup>*</sup> | ||
| style="padding:10px; background-color:white;" |BRC Global Standards' Global Standard for Food Safety, Issue 8 | |||
|- | |||
| style="padding:10px; width:350px;" |[https://elss.cap.org/elss/ShowProperty?nodePath=/UCMCON/Contribution%20Folders/DctmContent/education/OnlineCourseContent/2017/LAP-TLTM/misc/lam.pdf CAP Laboratory Accreditation Manual] | |||
| style="padding:10px; background-color:white;" |College of American Pathologists | | style="padding:10px; background-color:white;" |College of American Pathologists | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.cdc.gov/labs/BMBL.html CDC Biosafety in Microbiological and Biomedical Laboratories (BMBL)] | | style="padding:10px; width:350px;" |[https://www.cdc.gov/labs/BMBL.html CDC Biosafety in Microbiological and Biomedical Laboratories (BMBL)] | ||
| style="padding:10px; background-color:white;" |U.S. Centers for Disease Control and Prevention | | style="padding:10px; background-color:white;" |U.S. Centers for Disease Control and Prevention | ||
|- | |- | ||
Line 212: | Line 251: | ||
| style="padding:10px; background-color:white;" |Federal Bureau of Investigation, Criminal Justice Information Services | | style="padding:10px; background-color:white;" |Federal Bureau of Investigation, Criminal Justice Information Services | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://clsi.org/standards/products/automation-and-informatics/documents/auto15/ CLSI AUTO15] | | style="padding:10px; width:350px;" |[https://clsi.org/standards/products/automation-and-informatics/documents/auto15/ CLSI AUTO15] | ||
| style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | | style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://clsi.org/standards/products/automation-and-informatics/documents/auto16/ CLSI AUTO16] | | style="padding:10px; width:350px;" |[https://clsi.org/standards/products/automation-and-informatics/documents/auto16/ CLSI AUTO16] | ||
| style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | | style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://clsi.org/standards/products/quality-management-systems/documents/qms22/ CLSI QMS22] | | style="padding:10px; width:350px;" |[https://clsi.org/standards/products/quality-management-systems/documents/qms22/ CLSI QMS22] | ||
| style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | | style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https:// | | style="padding:10px; width:350px;" |[https://www.fao.org/fao-who-codexalimentarius/sh-proxy/en/?lnk=1&url=https%253A%252F%252Fworkspace.fao.org%252Fsites%252Fcodex%252FStandards%252FCXC%2B1-1969%252FCXC_001e.pdf Codex Alimentarius CXC 1-1969]<sup>*</sup> | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |Food and Agriculture Organization of the United Nations' Codex Alimentarius CXC 1-1969 ''General Principles of Good Hygiene'' | ||
|- | |||
| style="padding:10px; width:350px;" |[https://www.fao.org/fao-who-codexalimentarius/sh-proxy/en/?lnk=1&url=https%253A%252F%252Fworkspace.fao.org%252Fsites%252Fcodex%252FStandards%252FCXS%2B193-1995%252FCXS_193e.pdf Codex Alimentarius CXS 193-1995]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Food and Agriculture Organization of the United Nations' Codex Alimentarius CXS 193-1995 ''General Standard for Contaminants and Toxins in Food and Feed'' | |||
|- | |- | ||
| style="padding:10px; width:350px;" |[https:// | | style="padding:10px; width:350px;" |[https://www.fao.org/fao-who-codexalimentarius/sh-proxy/en/?lnk=1&url=https%253A%252F%252Fworkspace.fao.org%252Fsites%252Fcodex%252FStandards%252FCXS%2B234-1999%252FCXS_234e.pdf Codex Alimentarius CXS 234-1999]<sup>*</sup> | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |Food and Agriculture Organization of the United Nations' Codex Alimentarius CXS 234-1999 ''Recommended Methods of Analysis and Sampling'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https:// | | style="padding:10px; width:350px;" |[https://denix.osd.mil/edqw/documents/documents/gen-data-validation-rev1/ DoD General Data Validation Guidelines] | ||
| style="padding:10px; background-color:white;" | | | style="padding:10px; background-color:white;" |U.S. Department of Defense | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.ema.europa.eu/en/human-regulatory/research-development/compliance/good-manufacturing-practice/guidance-good-manufacturing-practice-good-distribution-practice-questions-answers EMA Guidance on good manufacturing practice and good distribution practice] | | style="padding:10px; width:350px;" |[https://www.ema.europa.eu/en/human-regulatory/research-development/compliance/good-manufacturing-practice/guidance-good-manufacturing-practice-good-distribution-practice-questions-answers EMA Guidance on good manufacturing practice and good distribution practice] | ||
| style="padding:10px; background-color:white;" |E.U. European Medicines Agency | | style="padding:10px; background-color:white;" |E.U. European Medicines Agency | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.epa.gov/dwlabcert/laboratory-certification-manual-drinking-water EPA 815-R-05-004 + supplements] | | style="padding:10px; width:350px;" |[https://www.epa.gov/dwlabcert/laboratory-certification-manual-drinking-water EPA 815-R-05-004 + supplements] | ||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency | | style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency | ||
|- | |- | ||
Line 248: | Line 290: | ||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency Staged Electronic Data Deliverable | | style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency Staged Electronic Data Deliverable | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://orapartners.fda.gov/cs/groups/public/documents/document/b2hh/bmri/~edisp/rpohandbook.pdf FDA Office of Regulatory Affairs Data Exchange (ORA DX) Program] | | style="padding:10px; width:350px;" |[https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-4/annex11_01-2011_en.pdf E.U. Annex 11] | ||
| style="padding:10px; background-color:white;" |European Union, European Commission | |||
|- | |||
| style="padding:10px; width:350px;" |[https://eur-lex.europa.eu/eli/dir/2003/94/oj E.U. Commission Directive 2003/94/EC] | |||
| style="padding:10px; background-color:white;" |European Union, European Commission | |||
|- | |||
| style="padding:10px; width:350px;" |[https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02004R0852-20210324 E.U. Commission Reg. No. 852/2004]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |European Union, European Commission | |||
|- | |||
| style="padding:10px; width:350px;" |[https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02005R2073-20200308 E.U. Commission Reg. No. 2073/2005]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |European Union, European Commission | |||
|- | |||
| style="padding:10px; width:350px;" |[https://orapartners.fda.gov/cs/groups/public/documents/document/b2hh/bmri/~edisp/rpohandbook.pdf FDA Office of Regulatory Affairs Data Exchange (ORA DX) Program] | |||
| style="padding:10px; background-color:white;" |U.S. Food and Drug Administration | | style="padding:10px; background-color:white;" |U.S. Food and Drug Administration | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.fda.gov/food/hazard-analysis-critical-control-point-haccp/haccp-principles-application-guidelines FDA Hazard Analysis Critical Control Point (HACCP)] | | style="padding:10px; width:350px;" |[https://www.fda.gov/food/hazard-analysis-critical-control-point-haccp/haccp-principles-application-guidelines FDA Hazard Analysis Critical Control Point (HACCP)] | ||
| style="padding:10px; background-color:white;" |U.S. Food and Drug Administration | | style="padding:10px; background-color:white;" |U.S. Food and Drug Administration | ||
|- | |||
| style="padding:10px; width:350px;" |[https://mygfsi.com/news-and-resources/?_keyword=GFSI%20Benchmarking%20Requirements&_type=publications GFSI Benchmarking Rqmts., v2020.1]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Global Food Safety Initiative Benchmarking Requirements Version 2020.1 | |||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.icar.org/Guidelines/15-Data-Exchange.pdf ICAR 15 Data Exchange] | | style="padding:10px; width:350px;" |[https://www.icar.org/Guidelines/15-Data-Exchange.pdf ICAR 15 Data Exchange] | ||
| style="padding:10px; background-color:white;" |International Committee for Animal Recording | | style="padding:10px; background-color:white;" |International Committee for Animal Recording | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://ichgcp.net/ ICH GCP] | | style="padding:10px; width:350px;" |[https://ichgcp.net/ ICH GCP] | ||
| style="padding:10px; background-color:white;" |International Council for Harmonisation Good Clinical Practice | | style="padding:10px; background-color:white;" |International Council for Harmonisation Good Clinical Practice | ||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ifs-certification.com/images/standards/ifs_food7/documents/standards/IFS_Food7_en.pdf IFS Food 7]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |International Featured Standards' Food 7 Standard | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ifs-certification.com/images/standards/ifs_pacsecure2/documents/standards/IFS_pacsecure2_en.pdf IFS PACsecure 2]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |International Featured Standards' PACsecure 2 Standard | |||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/56115.html ISO 15189:2012] | | style="padding:10px; width:350px;" |[https://www.iso.org/standard/56115.html ISO 15189:2012] | ||
Line 265: | Line 328: | ||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/66912.html ISO/IEC 17025:2017] | | style="padding:10px; width:350px;" |[https://www.iso.org/standard/66912.html ISO/IEC 17025:2017] | ||
| style="padding:10px; background-color:white;" |ISO/IEC 17025:2017 ''General requirements for the competence of testing and calibration laboratories'' | | style="padding:10px; background-color:white;" |ISO/IEC 17025:2017 ''General requirements for the competence of testing and calibration laboratories'' | ||
|- | |||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/44001.html ISO/TS 22002-1:2009]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |ISO/TS 22002-1:2009 ''Prerequisite programmes on food safety — Part 1: Food manufacturing'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/60969.html ISO/TS 22002-4:2013]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |ISO/TS 22002-4:2013 ''Prerequisite programmes on food safety — Part 4: Food packaging manufacturing'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/66126.html ISO/TS 22002-6:2016]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |ISO/TS 22002-6:2016 ''Prerequisite programmes on food safety — Part 6: Feed and animal food production'' | |||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.aphis.usda.gov/animal_health/nahln/downloads/MessagingQuickGuide.pdf NAHLN HL7 Messaging Quick User Guide] | | style="padding:10px; width:350px;" |[https://www.aphis.usda.gov/animal_health/nahln/downloads/MessagingQuickGuide.pdf NAHLN HL7 Messaging Quick User Guide] | ||
Line 272: | Line 344: | ||
| style="padding:10px; background-color:white;" |National Animal Health Laboratory Network | | style="padding:10px; background-color:white;" |National Animal Health Laboratory Network | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.wadsworth.org/regulatory/clep/clinical-labs/laboratory-standards NYSDOH CLEP Clinical Laboratory Standards of Practice, General Systems Standards] | | style="padding:10px; width:350px;" |[https://www.wadsworth.org/regulatory/clep/clinical-labs/laboratory-standards NYSDOH CLEP Clinical Laboratory Standards of Practice, General Systems Standards] | ||
| style="padding:10px; background-color:white;" |New York State Department of Health Clinical Laboratory Evaluation Program | | style="padding:10px; background-color:white;" |New York State Department of Health Clinical Laboratory Evaluation Program | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.wadsworth.org/sites/default/files/WebDoc/MM%20guidance%20procedure%20for%20Micro%20iDOC-120320.pdf NYSDOH ELAP Medical Marijuana Microbiology Guidance] | | style="padding:10px; width:350px;" |[https://www.wadsworth.org/sites/default/files/WebDoc/MM%20guidance%20procedure%20for%20Micro%20iDOC-120320.pdf NYSDOH ELAP Medical Marijuana Microbiology Guidance] | ||
| style="padding:10px; background-color:white;" |New York State Department of Health Environmental Laboratory Approval Program | | style="padding:10px; background-color:white;" |New York State Department of Health Environmental Laboratory Approval Program | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final NIST 800-53, Rev. 5] | | style="padding:10px; width:350px;" |[https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final NIST 800-53, Rev. 5] | ||
| style="padding:10px; background-color:white;" |National Institute of Standards and Technology | | style="padding:10px; background-color:white;" |National Institute of Standards and Technology | ||
|- | |- | ||
Line 284: | Line 356: | ||
| style="padding:10px; background-color:white;" |Organisation for Economic Co-operation and Development Good Laboratory Practice | | style="padding:10px; background-color:white;" |Organisation for Economic Co-operation and Development Good Laboratory Practice | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi ONC United States Core Data for Interoperability (USCDI)] | | style="padding:10px; width:350px;" |[https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi ONC United States Core Data for Interoperability (USCDI)] | ||
| style="padding:10px; background-color:white;" |Office of the National Coordinator for Health Information Technology | | style="padding:10px; background-color:white;" |Office of the National Coordinator for Health Information Technology | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1020 OSHA 1910.1020] | | style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1020 OSHA 1910.1020] | ||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1020 - ''Access to employee exposure and medical records'' | | style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1020 - ''Access to employee exposure and medical records'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1020 OSHA 1910.1200] | | style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1020 OSHA 1910.1200] | ||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1200 - ''Hazard Communication'' | | style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1200 - ''Hazard Communication'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1450 OSHA 1910.1450] | | style="padding:10px; width:350px;" |[https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.1450 OSHA 1910.1450] | ||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1450 - ''Occupational exposure to hazardous chemicals in laboratories'' | | style="padding:10px; background-color:white;" |Occupational Safety and Health Administration 1910.1450 - ''Occupational exposure to hazardous chemicals in laboratories'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.pfp-ifss.org/ifss-resources/human-and-animal-food-testing-laboratories-best-practices-manual-december-2018/ PFP Human and Animal Food Testing Laboratories Best Practices Manual] | | style="padding:10px; width:350px;" |[https://www.pfp-ifss.org/ifss-resources/human-and-animal-food-testing-laboratories-best-practices-manual-december-2018/ PFP Human and Animal Food Testing Laboratories Best Practices Manual] | ||
| style="padding:10px; background-color:white;" |Partnership for Food Protection | | style="padding:10px; background-color:white;" |Partnership for Food Protection | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://ris.dls.virginia.gov/uploads/1VAC30/dibr/Microsoft%20Word%20-%20STD-ELV1-2016-Rev2.1_LabReqs_ANSIapp.doc-20210426142653.pdf TNI EL-V1-2016-Rev.2.1] | | style="padding:10px; width:350px;" |[https://laws-lois.justice.gc.ca/eng/regulations/SOR-2018-108/index.html Safe Food for Canadians Regulations SOR/2018-108]<sup>*</sup> | ||
| style="padding:10px; background-color:white;" |Government of Canada, Governor General of Canada | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.sqfi.com/wp-content/uploads/2020/11/20227FMIN_FoodManufacturing_v3-2-FINAL-w-links.pdf SQF FSC 9, Food Manufacturing]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |FMI, The Food Industry Association, SQF Institute's Food Safety Code: Manufacture of Food Packaging, Ninth Edition | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.sqfi.com/wp-content/uploads/2020/11/20227FMIN_PetFood_v3-2-Final-w-Links.pdf SQF FSC 9, Pet Food Manufacturing]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |FMI, The Food Industry Association, SQF Institute's Food Safety Code: Pet Food Manufacturing, Ninth Edition | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.sqfi.com/wp-content/uploads/2020/11/20227FMIN_FoodPackaging_v3-2-Final-w-Links.pdf SQF FSC 9, Manufacture of Food Packaging]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |FMI, The Food Industry Association, SQF Institute's Food Safety Code: Manufacture of Food Packaging, Ninth Edition | |||
|- | |||
| style="padding:10px; width:350px;" |[https://ris.dls.virginia.gov/uploads/1VAC30/dibr/Microsoft%20Word%20-%20STD-ELV1-2016-Rev2.1_LabReqs_ANSIapp.doc-20210426142653.pdf TNI EL-V1-2016-Rev.2.1] | |||
| style="padding:10px; background-color:white;" |The NELAC Institute ''Management and Technical Requirements for Laboratories Performing Environmental Analysis'', Volume 1 | | style="padding:10px; background-color:white;" |The NELAC Institute ''Management and Technical Requirements for Laboratories Performing Environmental Analysis'', Volume 1 | ||
|- | |- | ||
Line 308: | Line 392: | ||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | | style="padding:10px; background-color:white;" |U.S. Department of Agriculture | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/sites/default/files/media/TestingGuidelinesforHemp.pdf USDA Hemp Production Program Laboratory Testing Guidelines] | | style="padding:10px; width:350px;" |[https://www.ams.usda.gov/sites/default/files/media/TestingGuidelinesforHemp.pdf USDA Hemp Production Program Laboratory Testing Guidelines] | ||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | | style="padding:10px; background-color:white;" |U.S. Department of Agriculture | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/services/lab-testing/lab-approval USDA Laboratory Approval Service (LAS) Laboratory Approval Program (LAP) Policies and Procedures] | | style="padding:10px; width:350px;" |[https://www.ams.usda.gov/services/lab-testing/lab-approval USDA Laboratory Approval Service (LAS) Laboratory Approval Program (LAP) Policies and Procedures] | ||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | | style="padding:10px; background-color:white;" |U.S. Department of Agriculture | ||
|- | |- | ||
Line 329: | Line 413: | ||
| style="padding:10px; background-color:white;" |Veterinary International Conference on Harmonization GL53 ''Electronic Exchange of Documents: Electronic File Format'' | | style="padding:10px; background-color:white;" |Veterinary International Conference on Harmonization GL53 ''Electronic Exchange of Documents: Electronic File Format'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.wada-ama.org/en/resources/world-anti-doping-program/international-standard-laboratories-isl WADA International Standard for Laboratories (ISL)] | | style="padding:10px; width:350px;" |[https://www.wada-ama.org/en/resources/world-anti-doping-program/international-standard-laboratories-isl WADA International Standard for Laboratories (ISL)] | ||
| style="padding:10px; background-color:white;" |World Anti-Doping Agency | | style="padding:10px; background-color:white;" |World Anti-Doping Agency | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.wada-ama.org/en/resources/world-anti-doping-program/international-standard-protection-privacy-and-personal WADA International Standard for the Protection of Privacy and Personal Information (ISPPPI)] | | style="padding:10px; width:350px;" |[https://www.wada-ama.org/en/resources/world-anti-doping-program/international-standard-protection-privacy-and-personal WADA International Standard for the Protection of Privacy and Personal Information (ISPPPI)] | ||
| style="padding:10px; background-color:white;" |World Anti-Doping Agency | | style="padding:10px; background-color:white;" |World Anti-Doping Agency | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://extranet.who.int/pqweb/medicines/who-technical-report-series WHO Technical Report Series, #961, Annex 13] | | style="padding:10px; width:350px;" |[https://extranet.who.int/pqweb/medicines/who-technical-report-series WHO Technical Report Series, #961, Annex 13] | ||
| style="padding:10px; background-color:white;" |World Health Organization TRS, #961, Annex 13 ''Guidelines for preparing a laboratory information file'' | | style="padding:10px; background-color:white;" |World Health Organization TRS, #961, Annex 13 ''Guidelines for preparing a laboratory information file'' | ||
|- | |- | ||
Line 341: | Line 425: | ||
| style="padding:10px; background-color:white;" |World Health Organization TRS, #986, Annex 2 ''WHO good manufacturing practices for pharmaceutical products: main principles'' | | style="padding:10px; background-color:white;" |World Health Organization TRS, #986, Annex 2 ''WHO good manufacturing practices for pharmaceutical products: main principles'' | ||
|- | |- | ||
| style="padding:10px; width:350px;" |[https://www.gmp-compliance.org/guidelines/gmp-guideline/who-guidance-on-good-data-and-record-management-practices WHO Technical Report Series, #996, Annex 5] | | style="padding:10px; width:350px;" |[https://www.gmp-compliance.org/guidelines/gmp-guideline/who-guidance-on-good-data-and-record-management-practices WHO Technical Report Series, #996, Annex 5] | ||
| style="padding:10px; background-color:white;" |World Health Organization TRS, #996, Annex 5 ''Guidance on good data and record management practices'' | | style="padding:10px; background-color:white;" |World Health Organization TRS, #996, Annex 5 ''Guidance on good data and record management practices'' | ||
|- | |- |
Latest revision as of 18:48, 7 December 2022
Introduction
Merriam-Webster defines a "specification" as "a detailed precise presentation of something or of a plan or proposal for something."[1] In other words, an existing or theoretical product, concept, or idea is presented in detail for a particular audience. In a broad sense, detailing the specifics about a project, concept, or idea to others is just common sense. This applies just as well to the world of software development, where a software requirements specification is essential for preventing the second most commonly cited reason for project failure: poor requirements management.[2]
In fact, the ISO/IEC/IEEE 29148:2018 standard (a conglomeration of what was formerly IEEE 830 and other standards) is in place to help specify "the required processes implemented in the engineering activities that result in requirements for systems and software products" and provides guidelines for how to apply those requirements.[3] The standard describes the characteristics that make up quality software requirement development, including aspects such as[4]:
- correctly describing system behavior;
- effectively removing ambiguity from the language used;
- completely covering the system behavior and features;
- accurately prioritizing and ranking the requirements; and
- unequivocally ensuring the requirements are testable, modifiable, and traceable.
A requirement typically comes in the form of a statement that begins with "the system/user/vendor shall/should ..." and focuses on a provided service, reaction to input, or expected behavior in a given situation. The statement may be abstract (high-level) or specific and detailed to a precise function. The statement may also be of a functional nature, describing functionality or services in detail, or of a non-functional nature, describing the constraints of a given functionality or service and how it's rendered. An example of a functional software requirement could be "the user shall be able to query either all of the initial set of databases or select a subset from it." This statement describes specific functionality the system should have. On the other hand, a non-functional requirement, for example, may state "the system's query tool shall conform to the ABC 123-2014 standard." The statement describes a constraint placed upon the system's query functionality. Once compiled, a set of requirements can serve not only to strengthen the software requirements specification, but the requirements set can also be used for bidding on a contract or serve as the basis for a specific contract that is being finalized.[5]
Over the years, a wide variety of companies, consultants, and researchers have compiled public and private software requirements specifications for laboratory informatics systems. These compiled lists of requirements for how a given laboratory informatics solution should be developed, delivered, and maintained have changed as technology and user demand have evolved. Often times, these requirements documents turn into a mix of "wishlist" requirements from potential and active clients, as well as regulation-mandated requirements. The wishlist items aren't necessarily ignored by developers, but they do in fact have to be prioritized as "nice to have" or "essential to system operation," or something in between.[6][7][8] While this reasonable mix of requirements has served informatics software developers well[9], sometimes a fresh approach is required.
What follows is an attempt to look less at the wishlists of laboratories and more directly at what requirements current regulatory schemes, industry standards, and organizational guidelines place on the ever-evolving array of laboratory informatics systems being developed today. What does the United States' 21 CFR Part 11 have to say about how your laboratory information management system (LIMS), laboratory information system (LIS), electronic laboratory notebook (ELN), and other systems operate? What does the European Union's Annex 11 dictate in those same regards? The following five chapters list those requirements, supported by one or more regulations, standards, and guidelines. The final chapter discusses how to best put this requirements specification to use.
Methodology
At its core, this LIMSpec—which has seen several iterations over the years—is rooted in ASTM E1578-18 Standard Guide for Laboratory Informatics. The latest version was released in 2018, which includes an updated Laboratory Informatics Functional Requirements checklist in the appendix. That list of requirements "covers functionality common to the various laboratory informatics systems discussed throughout [the] guide as well as requirements recommended as part of [the] guide." It goes on to state that the checklist "is an example of typical requirements that can be used to guide the purchase, upgrade, or development of a laboratory informatics system," though it is certainly "not meant to be exhaustive."
This LIMSpec borrows from that requirements checklist and then adds more to it from a wide variety of sources. An attempt has been made to find the most relevant regulations, standards, and guidance that shape how a compliant laboratory informatics system is developed and maintained. However, this should definitely be considered a work in progress, with more to be added with additional public and private comment on missing sources.
That said, this fourth revision (December 2022) taps into more than 130 resources, including the following:
|
Each requirement statement has at least one linked regulation, standard, or guidance item. In some cases, the standards covered are proprietary. In those cases, the standard was either purchased for review or heavily researched using supporting documentation, and the link goes to the acquisition page for the standard. In other cases, some sources have been intentionally omitted. For example, the AOAC International Official Methods of Analysis and Guidelines for Laboratories Performing Microbiological and Chemical Analyses of Food, Dietary Supplements, and Pharmaceuticals are both proprietary and more or less prohibitively expensive. In other cases, such as with the U.S. Food Emergency Response Network and Laboratory Response Network, they simply don't make their standardized procedures open to the public and thus can't be included.
- ↑ "specification". Merriam-Webster. Merriam-Webster, Inc. https://www.merriam-webster.com/dictionary/specification. Retrieved 07 December 2022.
- ↑ Bieg, D.P. (August 2014). "Introduction" (PDF). Requirements Management: A Core Competency for Project and Program Success. Project Management Institute. p. 3. https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/requirements-management.pdf. Retrieved 07 December 2022.
- ↑ "ISO/IEC/IEEE 29148:2018". International Organization for Standardization. November 2018. https://www.iso.org/standard/72089.html. Retrieved 07 December 2022.
- ↑ Seibert, P. (28 July 2011). "How do you write software requirements? What are software requirements? What is a software requirement?". HubTechInsider. https://hubtechinsider.wordpress.com/2011/07/28/how-do-you-write-software-requirements-what-are-software-requirements-what-is-a-software-requirement/. Retrieved 07 December 2022.
- ↑ Memon, A. (Spring 2010). "Software Requirements: Descriptions and specifications of a system" (PDF). University of Maryland. https://www.cs.umd.edu/~atif/Teaching/Spring2010/Slides/3.pdf. Retrieved 07 December 2022.
- ↑ Aasem, M.; Ramzan, M.; Jaffar, A. (2010). "Analysis and optimization of software requirements prioritization techniques". Proceedings from the 2010 International Conference on Information and Emerging Technologies: 1–6. doi:10.1109/ICIET.2010.5625687.
- ↑ Hirsch, J. (22 November 2013). "10 Steps To Successful Requirements Gathering". Phase2 Technology, LLC. https://www.phase2technology.com/blog/successful-requirements-gathering. Retrieved 07 December 2022.
- ↑ Burris, E. (2007). "Requirements Specification". CS451R, University of Missouri–Kansas City. University of Missouri–Kansas City. Archived from the original on 24 July 2019. https://web.archive.org/web/20190724173601/http://sce2.umkc.edu/BIT/burrise/pl/requirements/. Retrieved 07 December 2022.
- ↑ Hofmann, H.F.; Lehner, F. (2001). "Requirements engineering as a success factor in software projects". IEEE Software 18 (4): 58–66. doi:10.1109/MS.2001.936219.