Difference between revisions of "LIMSwiki mission"
Shawndouglas (talk | contribs) m (Wording and mention of the LII) |
Shawndouglas (talk | contribs) |
||
| Line 2: | Line 2: | ||
The explosion of the laboratory and health informatics fields paired with the vast number of [[LIMS vendor|LIMS vendors]] and products — as well as [[LIMS]]' increased scope well beyond its original purpose of [[sample]] management to just about all facets of [[laboratory]] operations — has resulted in a wealth of [[information]] not easily comprehended. This potential confusion frustrates informatics customers and makes the already challenging task of successfully implementing and managing a LIMS, [[ELN]], or other informatics software even more difficult. In that regard, the [[Laboratory Informatics Institute]] (which is responsible for this wiki) believes the community (including vendors, users, and [[LIMS consultant|consultants]]) will benefit from a common vocabulary and understanding to facilitate communication, comparison, and product integration, providing maximum value to buyers and maximum opportunity to vendors and consultants. | The explosion of the laboratory and health informatics fields paired with the vast number of [[LIMS vendor|LIMS vendors]] and products — as well as [[LIMS]]' increased scope well beyond its original purpose of [[sample]] management to just about all facets of [[laboratory]] operations — has resulted in a wealth of [[information]] not easily comprehended. This potential confusion frustrates informatics customers and makes the already challenging task of successfully implementing and managing a LIMS, [[ELN]], or other informatics software even more difficult. In that regard, the [[Laboratory Informatics Institute]] (which is responsible for this wiki) believes the community (including vendors, users, and [[LIMS consultant|consultants]]) will benefit from a common vocabulary and understanding to facilitate communication, comparison, and product integration, providing maximum value to buyers and maximum opportunity to vendors and consultants. | ||
{{Datasheet 021102 System architecture | |||
|021102_desc = | |||
}} | |||
{{Specification | |||
|idnumber = P1.1 | |||
|title = Easy registration/accession | |||
|funcdesc = Registration of specimens and their assays, patient information and other necessary information should be easy, quick and available to whomever the POL assigns that duty - including in some cases even the patients themselves (e.g. some urine, fecal, mucous/fluid or swab specimens, entered online). Accession numbers should be unique and assigned automatically, and link to all related information for easy retrieval. Test request information meets NCCLS LIS3-A 6.3. Accessions should be quickly and easily retrievable by authorized users. Registration should be independent of instrument availability. There should be no limit to the number of registrations, per patient or generally. | |||
|standregref = ASTM E1578-13 C-1-14, C-1-15, MU2, NCCLS LIS3-A 6.2, 6.3.3, CLSI Auto13-A2, API LIS-FAT | |||
|description = | |||
}} | |||
Revision as of 16:05, 4 June 2015
The mission and goal of the 'Laboratory Informatics Encyclopedia', otherwise known as LIMSwiki, is to provide the laboratory community and LIMS community with an organized, documented, up-to-date, standardized body of knowledge (BoK) regarding all aspects of laboratory informatics, bioinformatics, and health informatics. The value and success of LIMSwiki (like any community wiki) is dependent upon the laboratory community contributing their vast knowledge through the creation of relevant articles and editing of existing articles where knowledge is absent.
The explosion of the laboratory and health informatics fields paired with the vast number of LIMS vendors and products — as well as LIMS' increased scope well beyond its original purpose of sample management to just about all facets of laboratory operations — has resulted in a wealth of information not easily comprehended. This potential confusion frustrates informatics customers and makes the already challenging task of successfully implementing and managing a LIMS, ELN, or other informatics software even more difficult. In that regard, the Laboratory Informatics Institute (which is responsible for this wiki) believes the community (including vendors, users, and consultants) will benefit from a common vocabulary and understanding to facilitate communication, comparison, and product integration, providing maximum value to buyers and maximum opportunity to vendors and consultants.
Template:Datasheet 021102 System architecture
ID: P1.1
Title: Easy registration/accession
Functional Description: Registration of specimens and their assays, patient information and other necessary information should be easy, quick and available to whomever the POL assigns that duty - including in some cases even the patients themselves (e.g. some urine, fecal, mucous/fluid or swab specimens, entered online). Accession numbers should be unique and assigned automatically, and link to all related information for easy retrieval. Test request information meets NCCLS LIS3-A 6.3. Accessions should be quickly and easily retrievable by authorized users. Registration should be independent of instrument availability. There should be no limit to the number of registrations, per patient or generally.
Standards and Regulatory References: ASTM E1578-13 C-1-14, C-1-15, MU2, NCCLS LIS3-A 6.2, 6.3.3, CLSI Auto13-A2, API LIS-FAT
Application Functional Description:
