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

From LIMSWiki
Jump to navigationJump to search
Tag: Reverted
Tag: Reverted
Line 1: Line 1:
First, note that this LIMSpec is still an evolving entity. Standards change. Regulations change. Procedures also change with such standards and regulations. That means that as those foundational characteristics shift, this set of requirements will have to also evolve. As such, do your homework and don't take everything you see here as fixed law. If you're responsible for investigating and/or purchasing a laboratory informatics system, be sure you have at least some familiarity with the primary industry your laboratory serves, and by extension the regulations and standards that affect it.
What does that mean for you? How can you best use this document? If you're a software developer for the laboratory industry, many of the sources referenced in these requirements should already be familiar to you. However, some of them may not be, and you'll probably want to at least familiarize yourself with them. Additionally, if you're developing a generic [[laboratory information management system]] (LIMS) or some other informatics solution, not tailored to a particular industry, most everything in chapters two, three, five, and six should largely be applicable to what you're doing with your commercial off-the-shelf (COTS) software solution. Definitely review the requirements items listed there and make sure the most important ones are part of your own software requirements specification. If the software solution you're developing is tailored to a particular industry (e.g., clinical or public health, pharmaceutical development, or heavy metals testing), you'll also want to examine chapter four. If you don't see many requirements for your industry listed (see the "Caveats" section later), you'll probably have additional research to conduct to see what additional sources will affect how you develop the functional and, particularly, non-functional requirements.
 
Second, the number of industry-specific applications of laboratory informatics software continues to grow, and with it also the regulations and standards that affect those specialty laboratories. As such, some industry-specific requirements may have been missed for lack of or too expensive public-facing sources. As mentioned with the first caveat, this version of LIMSpec is evolving, and as industry experts and researchers are able to provide additional feedback on this document, it will surely grow with more relevant sources. In other words, don't consider this complete, particularly if you're in a specialized laboratory industry. You may have to add more items based on you industry knowledge and insights.

Revision as of 20:39, 15 August 2022

What does that mean for you? How can you best use this document? If you're a software developer for the laboratory industry, many of the sources referenced in these requirements should already be familiar to you. However, some of them may not be, and you'll probably want to at least familiarize yourself with them. Additionally, if you're developing a generic laboratory information management system (LIMS) or some other informatics solution, not tailored to a particular industry, most everything in chapters two, three, five, and six should largely be applicable to what you're doing with your commercial off-the-shelf (COTS) software solution. Definitely review the requirements items listed there and make sure the most important ones are part of your own software requirements specification. If the software solution you're developing is tailored to a particular industry (e.g., clinical or public health, pharmaceutical development, or heavy metals testing), you'll also want to examine chapter four. If you don't see many requirements for your industry listed (see the "Caveats" section later), you'll probably have additional research to conduct to see what additional sources will affect how you develop the functional and, particularly, non-functional requirements.