1.4 General functional requirements
|
1.4.1 General
|
Functional requirement
|
Requirement code
|
Notes
|
a. Tracks status and workflow of the accession throughout the laboratory lifecycle, from submission to final analysis, including receiving, diagnostic testing, diagnostic test result reporting, and billing
|
|
|
b. System supports barcoded specimen labeling and tracking
|
|
|
c. System supports multiple customer payment sources (e.g. grants}
|
|
|
d. System can track current status of diagnostic tests in an accession
|
|
|
e. System contains spell-check dictionary that allows authorized users to add, edit, or remove entries
|
|
|
f. LIMS includes system administration ability to reset user passwords
|
|
|
g. LIMS can interface with or import existing data
|
|
|
h. LIMS can be configured to meet the characteristics of the laboratory
|
|
|
i. Optional comprehensive set of test codes suitable for use by the purchasing facility
|
|
|
j. Vendor provides a support schedule for the implementation process, including optional levels
|
|
|
k. Vendor can detail the amount of time and staff that purchaser will have to provide for the implementation process
|
|
|
l. Vendor can explain function and availability of additional support capabilities
|
|
|
m. System capable of storing multiple sample-related objects such as pictures, documents, PDF files, etc., including any instrument-generated format outputs from equipment
|
|
|
n. System capable of storing sample comments, special information fields which are project- or sample-specific, user defined fields, data objects like scanned chain of custodies and digital photos of such items as sample events, bitmaps, movies, .wav audio files, and Word documents
|
|
|
o. User able to store object files such as pictures from microscopes, GCMS scans of peaks, or even raw data files from instrument runs for later processing
|
|
|
p. LIMS provides non-LIMS trained personnel access to the LIMS data via a simple Windows-type browser interface which permits the display of data from sample points, projects, or user-defined queries
|
|
|
q. System provides for application-based security by limiting external users to functions they are password-privileged to perform
|
|
|
r. System provides sample tracking from login through final reporting and invoicing
|
|
|