Difference between revisions of "User:Shawndouglas/sandbox/sublevel12"
Shawndouglas (talk | contribs) Tag: Reverted |
Shawndouglas (talk | contribs) Tag: Reverted |
||
| Line 22: | Line 22: | ||
A [[laboratory information management system]] (LIMS) can be purpose-built to a specific industry or designed to broadly meet the base needs of most any lab. As such, given different vendor approaches and different industry needs, functionality may vary among LIMS, sometimes significantly. But what are the most important features of these systems? | A [[laboratory information management system]] (LIMS) can be purpose-built to a specific industry or designed to broadly meet the base needs of most any lab. As such, given different vendor approaches and different industry needs, functionality may vary among LIMS, sometimes significantly. But what are the most important features of these systems? | ||
To be fair, asking a question about "most important features" makes it tough to come up with something other than a subjective answer. On one hand, important to who? The laboratory seeking a LIMS is of course going to have its own [[workflow]]s and other unique requirements, and that lab will want a LIMS that can address those needs and requirements. On the other, some iteration of the LIMS has been around for decades, and while the way laboratory work has been conducted has changed over time, some LIMS requirements have remained the same. | To be fair, asking a question about "most important features" makes it tough to come up with something other than a subjective answer. On one hand, important to who? The laboratory seeking a LIMS is of course going to have its own [[workflow]]s and other unique requirements, and that lab will want a LIMS that can address those needs and requirements. On the other, some iteration of the LIMS has been around for decades, and while the way laboratory work has been conducted has changed over time, some LIMS requirements have remained the same. Dating back to the 1970s, LIMS has had the automation of laboratory workflows, reporting, and data management at its core<ref name="GibbonABrief96">{{cite journal |title=A brief history of LIMS |journal=Laboratory Automation and Information Management |author=Gibbon, G.A. |volume=32 |issue=1 |pages=1–5 |year=1996 |doi=10.1016/1381-141X(95)00024-K}}</ref>, and that is no different today. The birth of LIMS in the 1970s into the early 1980s saw focus placed upon needs such as<ref name="GibbonABrief96" />: | ||
* data processing and management, | |||
* sample management, | |||
* inventory management, | |||
* document management, | |||
* quality control, | |||
* reporting, and | |||
* interfacing and networking. | |||
If one looks carefully at that list, they will notice that those needs essentially follow the sample's path throughout the lab, from acquisition to results reporting and disposal. | |||
Revision as of 16:03, 20 March 2024
 |
This is sublevel12 of my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see my discussion page instead. |
Sandbox begins below
[[File:|right|350px]] Title: What are the most important features of a laboratory information management system (LIMS)?
Author for citation: Shawn E. Douglas
License for content: Creative Commons Attribution-ShareAlike 4.0 International
Publication date: March 2024
Introduction
Blah blah
A laboratory information management system (LIMS) can be purpose-built to a specific industry or designed to broadly meet the base needs of most any lab. As such, given different vendor approaches and different industry needs, functionality may vary among LIMS, sometimes significantly. But what are the most important features of these systems?
To be fair, asking a question about "most important features" makes it tough to come up with something other than a subjective answer. On one hand, important to who? The laboratory seeking a LIMS is of course going to have its own workflows and other unique requirements, and that lab will want a LIMS that can address those needs and requirements. On the other, some iteration of the LIMS has been around for decades, and while the way laboratory work has been conducted has changed over time, some LIMS requirements have remained the same. Dating back to the 1970s, LIMS has had the automation of laboratory workflows, reporting, and data management at its core[1], and that is no different today. The birth of LIMS in the 1970s into the early 1980s saw focus placed upon needs such as[1]:
- data processing and management,
- sample management,
- inventory management,
- document management,
- quality control,
- reporting, and
- interfacing and networking.
If one looks carefully at that list, they will notice that those needs essentially follow the sample's path throughout the lab, from acquisition to results reporting and disposal.
Conclusion
References
- ↑ 1.0 1.1 Gibbon, G.A. (1996). "A brief history of LIMS". Laboratory Automation and Information Management 32 (1): 1–5. doi:10.1016/1381-141X(95)00024-K.
