LII:LIMSpec/Putting LIMSpec to use - Revision history

Shawndouglas at 19:38, 22 January 2022

2022-01-22T19:38:42Z

← Older revision		Revision as of 19:38, 22 January 2022
Line 1:		Line 1:
			==Putting those requirements to practical use==
	{{LIMSpec/Putting LIMSpec to use}}		{{LIMSpec/Putting LIMSpec to use}}

	==References==		==References==
	{{Reflist\|colwidth=30em}}		{{Reflist\|colwidth=30em}}

Shawndouglas: Turned into a template

2022-01-20T00:48:20Z

Turned into a template

← Older revision		Revision as of 00:48, 20 January 2022
Line 1:		Line 1:
			{{LIMSpec/Putting LIMSpec to use}}
	==Putting ~~those requirements to practical use==~~
	[[File:Requirements Allocation Sheet.jpg\|600px\|right]]The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].

	~~===Software developer considerations===~~
	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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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.

	~~===Buyer considerations===~~
	~~If you're a potential buyer of a laboratory informatics solution, this~~ LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to ~~what a laboratory informatics solution should be capable of. Additionally, you can then~~ use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements. As you review the various options available to you and narrow down your search, your own list of requirements can be used as both as a personal checklist and as a requirements list you hand over to the vendor you query.

	~~====Software vendor selection====~~
	That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a tedious yet necessary process, one which requires careful planning and best practices. This topic has been written about by both software developers and end users alike, and their experiences should play a role in how you select a vendor. What follows is bullet-pointed advise as offered by some of those developers and end users.<ref name="PearceSoftware16">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-defining-your-requirements \|title=Software Vendor Selection: How to Define Your Requirements \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=21 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-2">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-finding-the-right-vendor \|title=Software Vendor Selection: Finding the Right Vendor \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=23 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-3">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-conducting-demonstrations \|title=Software Vendor Selection: The Pitfalls and Successes of Vendor Demos \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=28 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-4">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-requesting-proposals-quotes \|title=Software Vendor Selection: Requesting Proposals & Quotes \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=05 July 2016 \|accessdate=20 September 2019}}</ref><ref name="PersaudBusiness16">{{cite web \|url=https://selecthub.com/technology-selection/business-requirements-gathering-enterprise-software-selection/ \|title=Business Requirements Gathering for Enterprise Software Selection \|author=Persaud, D. \|work=SelectHub Blog \|publisher=Abuyo, Inc \|date=04 February 2016 \|accessdate=20 September 2019}}</ref><ref name="LichtenbergerSix12">{{cite web \|url=https://blog.itil.org/2012/07/allgemein/six-steps-for-a-successful-vendor-selection/ \|title=Six Steps for a Successful Vendor Selection \|author=Lichtenberger, A. \|work=ITIL.org \|date=23 July 2012 \|accessdate=20 September 2019}}</ref><ref name="PoonInsider15">{{cite web \|url=https://www.genologics.com/blog/insiders-guide-to-lims-selection/ \|title=Insider’s Guide to LIMS Selection \|author=Poon, L. \|work=Genologics Blog \|publisher=GenoLogics Life Sciences Software Inc \|date=29 May 2015 \|accessdate=20 September 2019}}</ref><ref name="BenchlingHowTo">{{cite web \|url=https://benchling.com/static/docs/resources/eln-for-biology-rnd.pdf \|title=How to Select an ELN for Biology R&D \|publisher=Benchling, Inc \|accessdate=20 September 2019}}</ref>

	* Have a clear business case and build your business needs into your laboratory's requirements.
	* Be mindful of how detailed you get with your own business-based requirements and what you initially hand off to a vendor. If you're too specific with too many requirements, you may have trouble finding a vendor that matches up. Start with the essentials that involve your laboratory's processes, regulations, integrations, reporting, service needs, etc. As this LIMSpec is foundation-based, you have a good starting point in that regard. You can always get more detailed with requirements as you narrow down vendors.
	* As discussed briefly in the introduction, you'll need to prioritize your needs somewhere between "critical" and "nice to have." The LIMSpec's requirements are largely critical for most purposes and can be marked as such. The requirements you add will have to be prioritized more carefully.
	* You'll also want to perform some informal third-party information gathering about the vendors. Are reviews of the vendors trustworthy? Have peers had any interactions and success with the vendor? Does the vendor have the ability to scale to meet your needs?
	* Schedule demonstrations of programs that seem like strong initial candidates. Make sure there is a question and answer session afterwards, and perform a post-demo evaluation.
	* A formal request for proposal (RFP) may or may not be necessary, depending on the level of information you acquire prior. However, formally requesting pricing and clarification of maintenance and additional service costs is useful. Just don't let price be the only thing that guides you.
	* Consider some of the intangibles. Does the vendor genuinely seem interested in your business and its needs? Do they communicate well and promptly? Do they seem flexible and able to accommodate a few special case requirements?
	* Be sure to consider future needs as you anticipate potential laboratory expansion.
	* Don't be afraid to choose a consultant to help you with the vendor selection process.


	~~==Caveats==~~
	First, note that this LIMSpec is still an evolving entity. Standards change. Regulations change. Procedures change too with such changes. 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.

	Second, the number of industry-specific applications of laboratory informatics software continues to grow, and with them also the regulations and standards that affect those specialty laboratories. As such, this first time compiling these requirements surely missed some public-facing sources that affect how laboratories run, and by extension how their laboratory informatics applications should run. 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.

	==References==		==References==
	{{Reflist\|colwidth=30em}}		{{Reflist\|colwidth=30em}}

Shawndouglas at 20:17, 4 December 2021

2021-12-04T20:17:13Z

← Older revision		Revision as of 20:17, 4 December 2021
Line 21:		Line 21:
	* Be sure to consider future needs as you anticipate potential laboratory expansion.		* Be sure to consider future needs as you anticipate potential laboratory expansion.
	* Don't be afraid to choose a consultant to help you with the vendor selection process.		* Don't be afraid to choose a consultant to help you with the vendor selection process.


	==Caveats==		==Caveats==

Shawndouglas at 21:24, 20 September 2019

2019-09-20T21:24:35Z

← Older revision		Revision as of 21:24, 20 September 2019
Line 10:		Line 10:

	====Software vendor selection====		====Software vendor selection====
	That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a tedious yet necessary process, one which requires careful planning and best practices. This topic has been written about by both software developers and end users alike, and their experiences should play a role in how you select a vendor. What follows is bullet-pointed advise as offered by some of those developers and end users.<ref name="PearceSoftware16">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-defining-your-requirements \|title=Software Vendor Selection: How to Define Your Requirements \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=21 June 2016 \|accessdate=20 September 2019}}</ref>		That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a tedious yet necessary process, one which requires careful planning and best practices. This topic has been written about by both software developers and end users alike, and their experiences should play a role in how you select a vendor. What follows is bullet-pointed advise as offered by some of those developers and end users.<ref name="PearceSoftware16">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-defining-your-requirements \|title=Software Vendor Selection: How to Define Your Requirements \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=21 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-2">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-finding-the-right-vendor \|title=Software Vendor Selection: Finding the Right Vendor \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=23 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-3">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-conducting-demonstrations \|title=Software Vendor Selection: The Pitfalls and Successes of Vendor Demos \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=28 June 2016 \|accessdate=20 September 2019}}</ref><ref name="PearceSoftware16-4">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-requesting-proposals-quotes \|title=Software Vendor Selection: Requesting Proposals & Quotes \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=05 July 2016 \|accessdate=20 September 2019}}</ref><ref name="PersaudBusiness16">{{cite web \|url=https://selecthub.com/technology-selection/business-requirements-gathering-enterprise-software-selection/ \|title=Business Requirements Gathering for Enterprise Software Selection \|author=Persaud, D. \|work=SelectHub Blog \|publisher=Abuyo, Inc \|date=04 February 2016 \|accessdate=20 September 2019}}</ref><ref name="LichtenbergerSix12">{{cite web \|url=https://blog.itil.org/2012/07/allgemein/six-steps-for-a-successful-vendor-selection/ \|title=Six Steps for a Successful Vendor Selection \|author=Lichtenberger, A. \|work=ITIL.org \|date=23 July 2012 \|accessdate=20 September 2019}}</ref><ref name="PoonInsider15">{{cite web \|url=https://www.genologics.com/blog/insiders-guide-to-lims-selection/ \|title=Insider’s Guide to LIMS Selection \|author=Poon, L. \|work=Genologics Blog \|publisher=GenoLogics Life Sciences Software Inc \|date=29 May 2015 \|accessdate=20 September 2019}}</ref><ref name="BenchlingHowTo">{{cite web \|url=https://benchling.com/static/docs/resources/eln-for-biology-rnd.pdf \|title=How to Select an ELN for Biology R&D \|publisher=Benchling, Inc \|accessdate=20 September 2019}}</ref>

			* Have a clear business case and build your business needs into your laboratory's requirements.
			* Be mindful of how detailed you get with your own business-based requirements and what you initially hand off to a vendor. If you're too specific with too many requirements, you may have trouble finding a vendor that matches up. Start with the essentials that involve your laboratory's processes, regulations, integrations, reporting, service needs, etc. As this LIMSpec is foundation-based, you have a good starting point in that regard. You can always get more detailed with requirements as you narrow down vendors.
			* As discussed briefly in the introduction, you'll need to prioritize your needs somewhere between "critical" and "nice to have." The LIMSpec's requirements are largely critical for most purposes and can be marked as such. The requirements you add will have to be prioritized more carefully.
			* You'll also want to perform some informal third-party information gathering about the vendors. Are reviews of the vendors trustworthy? Have peers had any interactions and success with the vendor? Does the vendor have the ability to scale to meet your needs?
			* Schedule demonstrations of programs that seem like strong initial candidates. Make sure there is a question and answer session afterwards, and perform a post-demo evaluation.
			* A formal request for proposal (RFP) may or may not be necessary, depending on the level of information you acquire prior. However, formally requesting pricing and clarification of maintenance and additional service costs is useful. Just don't let price be the only thing that guides you.
			* Consider some of the intangibles. Does the vendor genuinely seem interested in your business and its needs? Do they communicate well and promptly? Do they seem flexible and able to accommodate a few special case requirements?
			* Be sure to consider future needs as you anticipate potential laboratory expansion.
			* Don't be afraid to choose a consultant to help you with the vendor selection process.

	==Caveats==		==Caveats==

Shawndouglas at 19:59, 20 September 2019

2019-09-20T19:59:55Z

← Older revision		Revision as of 19:59, 20 September 2019
Line 10:		Line 10:

	====Software vendor selection====		====Software vendor selection====
	That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a ~~somewhat~~ tedious yet necessary process.		That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a tedious yet necessary process, one which requires careful planning and best practices. This topic has been written about by both software developers and end users alike, and their experiences should play a role in how you select a vendor. What follows is bullet-pointed advise as offered by some of those developers and end users.<ref name="PearceSoftware16">{{cite web \|url=https://blog.montrium.com/blog/software-vendor-selection-defining-your-requirements \|title=Software Vendor Selection: How to Define Your Requirements \|work=Montrium Blog \|author=Pearce, O. \|publisher=Montrium, Inc \|date=21 June 2016 \|accessdate=20 September 2019}}</ref>

	==Caveats==		==Caveats==

Shawndouglas at 19:53, 20 September 2019

2019-09-20T19:53:36Z

← Older revision		Revision as of 19:53, 20 September 2019
Line 3:		Line 3:
	[[File:Requirements Allocation Sheet.jpg\|600px\|right]]The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].		[[File:Requirements Allocation Sheet.jpg\|600px\|right]]The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].

	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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 ~~after this~~), 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.		===Software developer considerations===
			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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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.

			===Buyer considerations===
	If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to what a laboratory informatics solution should be capable of. Additionally, you can then use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements. As you review the various options available to you and narrow down your search, your own list of requirements can be used as both as a personal checklist and as a requirements list you hand over to the vendor you query.		If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to what a laboratory informatics solution should be capable of. Additionally, you can then use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements. As you review the various options available to you and narrow down your search, your own list of requirements can be used as both as a personal checklist and as a requirements list you hand over to the vendor you query.

	That said, the requirements you hand off to the vendor should be discussed a bit more.		====Software vendor selection====
			That said, the requirements you hand off to the vendor should be discussed a bit more. Software vendor selection can at times be a somewhat tedious yet necessary process.

	===Caveats===		==Caveats==
	First, note that this LIMSpec is still an evolving entity. Standards change. Regulations change. Procedures change too with such changes. 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.		First, note that this LIMSpec is still an evolving entity. Standards change. Regulations change. Procedures change too with such changes. 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.

Shawndouglas at 19:50, 20 September 2019

2019-09-20T19:50:18Z

← Older revision		Revision as of 19:50, 20 September 2019
Line 5:		Line 5:
	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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.		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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.

	If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to what a laboratory informatics solution should be capable of. Additionally, you can then use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements.		If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to what a laboratory informatics solution should be capable of. Additionally, you can then use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements. As you review the various options available to you and narrow down your search, your own list of requirements can be used as both as a personal checklist and as a requirements list you hand over to the vendor you query.

			That said, the requirements you hand off to the vendor should be discussed a bit more.

	===Caveats===		===Caveats===

Shawndouglas at 19:45, 20 September 2019

2019-09-20T19:45:53Z

← Older revision		Revision as of 19:45, 20 September 2019
Line 5:		Line 5:
	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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.		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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.

	If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you.		If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you. Perhaps you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed. Reviewing the five broad categories of requirements may be necessary to help further inform you regarding what's vital in regards to what a laboratory informatics solution should be capable of. Additionally, you can then use these requirements as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the LIMSpec requirements.

	===Caveats===		===Caveats===

Shawndouglas at 19:40, 20 September 2019

2019-09-20T19:40:29Z

← Older revision		Revision as of 19:40, 20 September 2019
Line 1:		Line 1:

	==Putting those requirements to practical use==		==Putting those requirements to practical use==
	The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].		[[File:Requirements Allocation Sheet.jpg\|600px\|right]]The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].

	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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.		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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.

Shawndouglas at 19:33, 20 September 2019

2019-09-20T19:33:29Z

← Older revision		Revision as of 19:33, 20 September 2019
Line 3:		Line 3:
	The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].		The LIMSpec covered [[laboratory informatics]] requirements organized into five broad categories, which are heavily influenced by the functional requirements checklist and Figure 3 of [[ASTM E1578\|ASTM E1578-18]] ''Standard Guide for Laboratory Informatics''. However, the requirements listed prior are all based on not just the ASTM E1578 standard but also a wide variety of other standards, regulations, guidance documents, and standardized procedures (hereon out referred to as "sources"). That ultimately means a foundational reasoning is provided for each requirement, not necessarily a "just because I want it" reasoning. As foundational requirements, this LIMSpec should thus operate as an excellent starting point for building your own software requirements specification or for researching the best laboratory informatics solution for your [[laboratory]].

	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 making 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 they are part of your own software requirements specification.		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 making 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 they are part of your own software requirements specification. If the software solution you're developing hits a particular industry (e.g., clinical diagnostics, 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 after this), 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.

			If you're a potential buyer of a laboratory informatics solution, this LIMSpec is also useful to you.

	===Caveats===		===Caveats===