| 1.4 General functional requirements
 | 
| 1.4.1 General
 | 
| Functional requirement
 | 
Requirement code
 | 
Notes
 | 
| a. System 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. System capable of storing multiple sample-related objects such as pictures, documents, PDF files, etc., including any instrument-generated format outputs from equipment
 | 
 | 
 | 
| j. 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
 | 
 | 
 | 
| k. 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
 | 
 | 
 | 
| l. 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
 | 
 | 
 | 
| m. System provides for application-based security by limiting external users to functions they are password-privileged to perform
 | 
 | 
 | 
| n. System provides sample tracking from login through final reporting and invoicing
 | 
 | 
 | 
| o. System produces internal chain of custody data to track individual sample containers and test results
 | 
 | 
 | 
| p. System eliminates (or significantly reduces) redundant data entry and paper trail
 | 
 | 
 | 
| q. System manages archived, paper-based laboratory records
 | 
 | 
 | 
| r. System has a screen print function
 | 
 | 
 | 
| s. System has an analyst communication log
 | 
 | 
 | 
| t. System has configurable role-based security
 | 
 | 
 | 
| u. System utilizes role-based presentation of menus and functions
 | 
 | 
 | 
| v. System has supervisor override of chain of custody
 | 
 | 
 | 
| w. System provides automatic logout based on keyboard or mouse inactivity
 | 
 | 
 | 
| x. System prompts users for a reason for changes to database record
 | 
 | 
 | 
| y. System allows authorized personnel to review audit logs
 | 
 | 
 | 
| z. System's numbering scheme allows for sub-numbering while maintaining parent-child relationships
 | 
 | 
 | 
| aa. Chain of custody is printable for items, cases, projects, and batches
 | 
 | 
 | 
| ab. System has inter-lab transfer function
 | 
 | 
 | 
| ac. System allows queries of legacy data
 | 
 | 
 | 
| ad. Audit log retains all data, prohibits any deletions, and allows user comments
 | 
 | 
 | 
| ae. System search engine permits multiple search criteria
 | 
 | 
 | 
| af. System permits remote access for users, system admins, and support agents
 | 
 | 
 | 
| ag. System supports the definition and maintenance of edit tables and lists
 | 
 | 
 | 
| ah. System allows modification of records by system admins, with audit trail
 | 
 | 
 | 
| ai. System allows entry, maintenance, and administration of customers, suppliers, and other outside entities
 | 
 | 
 | 
| aj. System links or embeds standard operation procedure (SOP) access
 | 
 | 
 | 
| ak. System provides single data entry, automatically populates other data fields, and remembers pertinent and relevant data so it doesn't need to be re-entered, selected, or searched for
 | 
 | 
 | 
| al. System provides an intuitive, user-friendly graphical user interface (GUI), consistent with Microsoft products
 | 
 | 
 | 
| am. System captures data from all laboratory processes, ensuring uniformity of statistical reporting and other electronic data shared with designated users of the data
 | 
 | 
 | 
| an. System provides data archival and retention functionality
 | 
 | 
 | 
| ao. System efficiently utilizes standardized data input points and enhanced individual workload tracking
 | 
 | 
 | 
| ap. System provides full database keyword and field search capability
 | 
 | 
 | 
| aq. System provides read-only access to contract laboratory results
 | 
 | 
 | 
| ar. System allows use of navigation keys to freely move from field to field
 | 
 | 
 | 
| as. System allows data tables to be sorted
 | 
 | 
 | 
| at. System issues sequential numbers for chain of custody
 | 
 | 
 | 
| au. System allows multiple users to connect simultaneously to contract lab
 | 
 | 
 | 
| av. System notifies users of events like the scheduling, receipt, and completion of tasks
 | 
 | 
 | 
| aw. System includes the ability to set up alerts via email
 | 
 | 
 | 
| ax. System includes the ability to search multiple databases
 | 
 | 
 | 
| ay. System supports multiple users entering data simultaneously
 | 
 | 
 | 
| az. Data migrated into system converts cleanly to allow for reporting of historical sample collection
 | 
 | 
 | 
| 1.4.2 Configuration and customization
 | 
| Functional requirement
 | 
Requirement code
 | 
Notes
 | 
| a. User can independently add fields without requiring reconfiguration of the system after routine upgrades and maintenance
 | 
 | 
 | 
| b. System supports customized screens with user-definable information specific to an analysis
 | 
 | 
 | 
| c. System allows addition of universal fields on all samples logged into the system at any time during or after implementation, while neither voiding the warranty nor requiring vendor review at a later date
 | 
 | 
 | 
| d. System can expand to accommodate a new discipline
 | 
 | 
 | 
| e. System can integrate additional printers and scanners
 | 
 | 
 | 
| f. System allows the system admin to create custom screens, apps, and reports
 | 
 | 
 | 
| g. System dynamically changes captions (labels) on system fields
 | 
 | 
 | 
| h. System has dynamically configurable limit periods and notification hierarchy
 | 
 | 
 | 
| i. System can be easily and efficiently modified to meet lab growth and changing business needs
 | 
 | 
 | 
| 1.4.3 Receiving and scheduling
 | 
| Functional requirement
 | 
Requirement code
 | 
Notes
 | 
| a. System creates and maintains an electronic accession record for each accession received
 | 
 | 
 | 
| b. Electronic accession records support digital picture and document uploads in standard formats
 | 
 | 
 | 
| c. System allows users to handle billable and non-billable tests on the same accession
 | 
 | 
 | 
| d. System supports tracking of shipping and receiving
 | 
 | 
 | 
| e. System can receive accession/analysis request information from web-enabled forms
 | 
 | 
 | 
| f. System can process automated uploading of field-derived sample collection data
 | 
 | 
 | 
| g. System supports a user-configurable, spreadsheet-style, templated multi-sample login without requiring additional programming
 | 
 | 
 | 
| h. Multi-sample login supports the modification of sample or sample batch information prior to actual login
 | 
 | 
 | 
| i. Multi-sample login supports ad-hoc samples not predefined in the sample point list
 | 
 | 
 | 
| j. System can print user-definable chain of custodies, worksheets, routing sheets, and custom labels upon login
 | 
 | 
 | 
| k. System creates, saves, and recalls pre-login groups for routine samples to simplify recurring logins
 | 
 | 
 | 
| l. System includes comprehensive sample scheduling, tracking, and sample flow management
 | 
 | 
 | 
| m. System provides a comprehensive view of all samples and projects in the system using a color-coded status view of the current and scheduled samples via user configurable templates without requiring additional programming
 | 
 | 
 | 
| n. System schedules routine samples on an hourly, daily, weekly, or monthly basis, allowing them to be enabled and disabled as a group
 | 
 | 
 | 
| o. System streamlines login of recurring sampling projects
 | 
 | 
 | 
| p. System supports automatic assignment of analysis requests
 | 
 | 
 | 
| q. System can generate a monthly sampling schedule from a schedule database
 | 
 | 
 | 
| q. System can generate labels for recurring samples and sample groups
 | 
 | 
 |