Difference between revisions of "Template:LIMSpec/Introduction and methodology"
Shawndouglas (talk | contribs) |
Shawndouglas (talk | contribs) (Updated content for 2022.) |
||
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 | [[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=27 April 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=27 April 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 | 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=27 April 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=27 April 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=27 April 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 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=27 April 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=27 April 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. | ||
===Methodology=== | ===Methodology=== | ||
At its core, this LIMSpec—which has seen several iterations over the years—is rooted in [[ASTM E1578|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. | At its core, this LIMSpec—which has seen several iterations over the years—is rooted in [[ASTM E1578|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. | 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 third revision (2022) taps into more than 100 resources, including the following: | ||
{| | |||
* | | STYLE="vertical-align:top;"| | ||
{| 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. | |||
|- | |||
* | ! style="color:brown; background-color:#ffffee; width:500px;"| Regulation, Specification, or Guidance | ||
! style="color:brown; background-color:#ffffee; width:700px;"| Familiar Name and/or Responsible Entity | |||
* | |- | ||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/5/930.301 5 CFR Part 930.301] | |||
| 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]<sup>*</sup> | |||
| 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; width:350px;" |[https://www.law.cornell.edu/cfr/text/7/part-331 7 CFR Part 331] | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Animal and Plant Health Inspection Service, Department of Agriculture > Animal Welfare > Regulations | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/9/part-121 9 CFR Part 121] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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-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; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-11 21 CFR Part 11] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > General > Electronic Records; Electronic Signatures | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-58 21 CFR Part 58] | |||
| 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-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; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-212 21 CFR Part 212] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs: General > Current Good Manufacturing Practice for Positron Emission Tomography Drugs | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-225 21 CFR Part 225] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs: General > Current Good Manufacturing Practice for Medicated Feeds | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-226 21 CFR Part 226] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Drugs: General > Current Good Manufacturing Practice for Type A Medicated Articles | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-312 21 CFR Part 312] | |||
| 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-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; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-810 21 CFR Part 810] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Medical Devices > Medical Device Recall Authority | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-812 21 CFR Part 812] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Medical Devices > Investigational Device Exemptions | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/21/part-820 21 CFR Part 820] | |||
| style="padding:10px; background-color:white;" |Food and Drug Administration, Department of Health and Human Services > Medical Devices > Quality System Regulation | |||
|- | |||
* | | style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.120 29 CFR Part 1910.120] | ||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Hazardous Materials > Hazardous waste operations and emergency response | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.134 29 CFR Part 1910.134] | |||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Personal Protective Equipment > Respiratory protection | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.1030 29 CFR Part 1910.1030] | |||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Toxic and Hazardous Substances > Bloodborne pathogens | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.1096 29 CFR Part 1910.1096] | |||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Toxic and Hazardous Substances > Ionizing radiation | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.1200 29 CFR Part 1910.1200] | |||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Toxic and Hazardous Substances > Hazard communication | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/29/1910.1450 29 CFR Part 1910.1450] | |||
| style="padding:10px; background-color:white;" |Occupational Safety and Health Standards > Toxic and Hazardous Substances > Occupational exposure to hazardous chemicals in laboratories | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-3 40 CFR Part 3] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > General > Cross-media Electronic Reporting | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-60 40 CFR Part 60] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Air Programs > Standards of Performance for New Stationary Sources | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-62 40 CFR Part 62] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Air Programs > Approval and Promulgation of State Plans for Designated Facilities and Pollutants | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-63 40 CFR Part 63] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Air Programs > National Emission Standards for Hazardous Air Pollutants for Source Categories | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-141 40 CFR Part 141] | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Solid Wastes > Standards Applicable to Generators of Hazardous Waste | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-370 40 CFR Part 370] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Superfund, Emergency Planning, and Community Right-to-know Programs > Hazardous Chemical Reporting: Community Right-to-know | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-372 40 CFR Part 372] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Superfund, Emergency Planning, and Community Right-to-know Programs > Toxic Chemical Release Reporting: Community Right-to-know | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-704 40 CFR Part 704] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Toxic Substances Control Act > Reporting and Recordkeeping Requirements | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-717 40 CFR Part 717] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Toxic Substances Control Act > Records and Reports of Allegations that Chemical Substances Cause Significant Adverse Reactions to Health or the Environment | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/40/part-720 40 CFR Part 720] | |||
| style="padding:10px; background-color:white;" |Environmental Protection Agency > Toxic Substances Control Act > Premanufacture Notification | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/42/part-73 42 CFR Part 73] | |||
| 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]<sup>*</sup> | |||
| 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; width:350px;" |[https://www.law.cornell.edu/cfr/text/42/part-493 42 CFR Part 493] | |||
| style="padding:10px; background-color:white;" |Centers for Medicare & Medicaid Services, Department of Health and Human Services > Standards and Certification > Laboratory Requirements | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/45/part-160 45 CFR Part 160] | |||
| style="padding:10px; background-color:white;" |Department of Health and Human Services > Administrative Data Standards and Related Requirements > General Administrative Requirements | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/45/part-162 45 CFR Part 162] | |||
| style="padding:10px; background-color:white;" |Department of Health and Human Services > Administrative Data Standards and Related Requirements > Administrative Requirements | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/45/part-164 45 CFR Part 164] | |||
| style="padding:10px; background-color:white;" |Department of Health and Human Services > Administrative Data Standards and Related Requirements > Security and Privacy | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.law.cornell.edu/cfr/text/45/part-170 45 CFR Part 170] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |American Association for Laboratory Accreditation | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.aafco.org/Publications/QA-QC-Guidelines-for-Feed-Laboratories AAFCO QA/QC Guidelines for Feed Laboratories] | |||
| style="padding:10px; background-color:white;" |Association of American Feed Control Officials | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.aavld.org/accreditation-requirements-page AAVLD Requirements for an AVMDL] | |||
| style="padding:10px; background-color:white;" |American Association of Veterinary Laboratory Diagnosticians | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.abft.org/files/ABFT_LAP_Standards_May_31_2013.pdf ABFT Accreditation Manual] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Association of Public Health Laboratories | |||
|- | |||
| style="padding:10px; width:350px;" |[https://des.wa.gov/sites/default/files/public/documents/About/1063/RFP/Add7_Item4ASCLD.pdf ASCLD/LAB Supp. Reqs. for the Accreditation of Forensic Science Testing Laboratories] | |||
| style="padding:10px; background-color:white;" |American Society of Crime Laboratory Directors/Laboratory Accreditation Board; note that ASCLD/LAB merged with ANAB (ANSI National Accreditation Board) in 2016, and their requirements for Forensic Service Provider Accreditation are not made public. As such, this serves as a proxy for ANAB. | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.astm.org/e1188-11r17.html ASTM E1188-11] | |||
| style="padding:10px; background-color:white;" |ASTM E1188-11(2017) ''Standard Practice for Collection and Preservation of Information and Physical Items by a Technical Investigator'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.astm.org/e1459-13r18.html ASTM E1459-13] | |||
| style="padding:10px; background-color:white;" |ASTM E1459-13(2018) ''Standard Guide for Physical Evidence Labeling and Related Documentation'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.astm.org/e1492-11r17.html ASTM E1492-11] | |||
| style="padding:10px; background-color:white;" |ASTM E1492-11(2017) ''Standard Practice for Receiving, Documenting, Storing, and Retrieving Evidence in a Forensic Science Laboratory'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.astm.org/e1578-18.html ASTM E1578-18] | |||
| 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]<sup>*</sup> | |||
| 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)]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |U.S. Centers for Disease Control and Prevention | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.cdc.gov/phin/tools/phinms/index.html CDC PHIN Messaging System] | |||
| style="padding:10px; background-color:white;" |U.S. Centers for Disease Control and Prevention | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.fbi.gov/services/cjis/cjis-security-policy-resource-center CJIS Security Policy] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |Clinical and Laboratory Standards Institute | |||
|- | |||
| style="padding:10px; width:350px;" |[https://denix.osd.mil/edqw/documents/documents/gen-data-validation-rev1/ DoD General Data Validation Guidelines]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |U.S. Department of Defense | |||
|- | |||
| 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://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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.epa.gov/emergency-response/environmental-response-laboratory-network-erln-laboratory-requirements EPA ERLN Laboratory Requirements v1.6] | |||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency, Environmental Response Laboratory Network | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.epa.gov/geospatial/epa-metadata-technical-specification EPA Metadata Technical Specification] | |||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.epa.gov/quality/guidance-quality-assurance-project-plans-epa-qag-5 EPA QA/G-5] | |||
| style="padding:10px; background-color:white;" |U.S. Environmental Protection Agency Guidance for Quality Assurance Project Plans | |||
|- | |||
| style="padding:10px; width:350px;" |[https://nepis.epa.gov/Exe/ZyPDF.cgi/P100WP4J.PDF?Dockey=P100WP4J.PDF EPA SEDD Specification and Data Element Dictionary v5.2] | |||
| 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]<sup>*</sup> | |||
| 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; background-color:white;" |U.S. Food and Drug Administration | |||
|- | |||
| 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; width:350px;" |[https://ichgcp.net/ ICH GCP]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |International Council for Harmonisation Good Clinical Practice | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.iso.org/standard/56115.html ISO 15189:2012] | |||
| style="padding:10px; background-color:white;" |ISO 15189:2012 ''Medical laboratories — Requirements for quality and competence'' | |||
|- | |||
| 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; width:350px;" |[https://www.aphis.usda.gov/animal_health/nahln/downloads/MessagingQuickGuide.pdf NAHLN HL7 Messaging Quick User Guide] | |||
| style="padding:10px; background-color:white;" |National Animal Health Laboratory Network | |||
|- | |||
| style="padding:10px; width:350px;" |[https://web.archive.org/web/20170509221853/https://www.aphis.usda.gov/aphis/ourfocus/animalhealth/lab-info-services/nahln/ct_nahln_it NAHLN Information Technology System] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |National Institute of Standards and Technology | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.oecd.org/chemicalsafety/testing/oecdseriesonprinciplesofgoodlaboratorypracticeglpandcompliancemonitoring.htm OECD GLP Principles] | |||
| 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)]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |The NELAC Institute ''Management and Technical Requirements for Laboratories Performing Environmental Analysis'', Volume 1 | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the Pesticide Data Program (PDP)] | |||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Data and Instrumentation for Pesticide Data Program] | |||
| 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]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Sample Processing and Analysis Procedures for Pesticide Data Program] | |||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | |||
|- | |||
| style="padding:10px; width:350px;" |[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Sampling Procedures for Pesticide Data Program] | |||
| style="padding:10px; background-color:white;" |U.S. Department of Agriculture | |||
|- | |||
| style="padding:10px; width:350px;" |[https://venomcoding.org/ VeNom Coding Group terminology] | |||
| style="padding:10px; background-color:white;" |Veterinary Nomenclature | |||
|- | |||
| style="padding:10px; width:350px;" |[https://vtsl.vetmed.vt.edu/ VTSL terminology] | |||
| style="padding:10px; background-color:white;" |Veterinary Terminology Services Laboratory at Virginia-Maryland College of Veterinary Medicine | |||
|- | |||
| style="padding:10px; width:350px;" |[https://vichsec.org/en/guidelines/general VICH GL53] | |||
| 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)]<sup>*</sup> | |||
| 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)]<sup>*</sup> | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |World Health Organization TRS, #961, Annex 13 ''Guidelines for preparing a laboratory information file'' | |||
|- | |||
| style="padding:10px; width:350px;" |[https://extranet.who.int/pqweb/medicines/who-technical-report-series WHO Technical Report Series, #986, Annex 2] | |||
| 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]<sup>*</sup> | |||
| style="padding:10px; background-color:white;" |World Health Organization TRS, #996, Annex 5 ''Guidance on good data and record management practices'' | |||
|- | |||
|} | |||
|} | |||
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 are both proprietary and more or less prohibitively expensive. In other cases such as the U.S. Food Emergency Response Network and Laboratory Response Network, they simply don't make their standardized procedures open to the public. | 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. |
Revision as of 20:14, 5 May 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 third revision (2022) taps into more than 100 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 27 April 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 27 April 2022.
- ↑ "ISO/IEC/IEEE 29148:2018". International Organization for Standardization. November 2018. https://www.iso.org/standard/72089.html. Retrieved 27 April 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 27 April 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 27 April 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 27 April 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 27 April 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.