1.4 General system functions
|
1.4.1 General
|
Request for information
|
Requirement code
|
Vendor response
|
a. Does your system offer non-LIMS trained personnel the ability to easily access system data via an intuitive, user-friendly Windows-type graphical user interface (GUI) which permits the display of data from sample points, projects, or user-defined queries?
|
|
|
b. Does your system permit remote access for users, system admins, and support agents?
|
|
|
c. Does your system utilize role-based presentation of menus and functions?
|
|
|
d. Does your system allow for the use of navigation keys to freely move from field to field?
|
|
|
e. Does your system allow data tables to be sorted?
|
|
|
f. Does your system have a screen print function?
|
|
|
g. Does your system provide single data entry, automatically populate other data fields, and remember pertinent and relevant data so it doesn't need to be re-entered, selected, or searched for?
|
|
|
h. Does your system support multiple users entering data simultaneously?
|
|
|
i. Does your system eliminate (or significantly reduce) redundant data entry and paper trails? If so, how?
|
|
|
j. Does your system contain one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries?
|
|
|
k. Does your system provide full database keyword and field search capability?
|
|
|
l. Does your system's search engine permit multiple search criteria?
|
|
|
m. Does your system include the ability to search multiple databases, including those containing legacy data?
|
|
|
n. Does your system interface with or import existing data from other systems and/or databases?
|
|
|
o. Does you system cleanly convert migrated data to allow for reporting of historical sample collections? If so, how?
|
|
|
p. Does your system provide data archival and retention functionality?
|
|
|
q. Does your system manage archived, paper-based laboratory records?
|
|
|
r. Does your system allow users to associate and store non-sample-related objects such as pictures from microscopes, GCMS scans of peaks, or even raw data files from instrument runs for later processing?
|
|
|
s. Does your system allow users to associate and store sample-related objects such as pictures, spreadsheets, PDF files, etc., including any instrument-generated format outputs from equipment?
|
|
|
t. Does your system store more non-traditional information and objects like project- or sample-specific special information fields, user-defined fields, scanned chain of custodies and digital photos of such items as sample events, bitmaps, movies, and .wav audio files?
|
|
|
u. Does your system's numbering scheme allow for sub-numbering while maintaining parent-child relationships?
|
|
|
v. Does your system efficiently utilize standardized data input points and enhanced individual workload tracking?
|
|
|
w. Does your system capture data from all laboratory processes, ensuring uniformity of statistical reporting and other electronic data shared with designated users of the data?
|
|
|
x. Does your system track 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?
|
|
|
y. Does your system support barcoded specimen labeling and tracking?
|
|
|
z. Does your system have an inter-lab transfer function?
|
|
|
aa. Does your system support the definition and maintenance of edit tables and lists?
|
|
|
ab. Does your system issue sequential numbers for chain of custody?
|
|
|
ac. Does your system allow authorized users to print chain of custody for items, cases, projects, and batches?
|
|
|
ad. Does your system allow entry, maintenance, and administration of customers, suppliers, and other outside entities?
|
|
|
ae. Does your system support multiple customer payment sources (e.g. grants}?
|
|
|
af. Does your system link or embed standard operation procedures (SOPs) to/in other objects like analysis requests and test results?
|
|
|
ag. Does your system allow multiple users to connect simultaneously to a contract lab?
|
|
|
ah. Does your system provide read-only access to contract laboratory results?
|
|
|
ai. Does your system notify users of events like the scheduling, receipt, and completion of tasks?
|
|
|
aj. Does yout system include the ability to set up alerts via email?
|
|
|
ak. Does your system maintain an analyst communication log?
|
|
|
1.4.2 Configuration and customization
|
Request for information
|
Requirement code
|
Vendor response
|
a. Can your system can be configured to meet the characteristics of a laboratory? Please explain how.
|
|
|
b. Can your system easily and efficiently be modified to meet lab growth and changing business needs? Please explain how.
|
|
|
c. Can your system expand to accommodate a new discipline? If so, how?
|
|
|
d. Can your system support customized screens with user-definable information specific to a customer, department, analysis, etc.?
|
|
|
e. Does your system allow the administrator to create custom screens, applications, and reports? Please give details.
|
|
|
f. Does the system allow a user to independently add fields without requiring reconfiguration of the system, even after routine upgrades and maintenance?
|
|
|
g. Does your system allow a user to independently add 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?
|
|
|
h. Does your system dynamically change captions (labels) on system fields?
|
|
|
i. Does your system have dynamically configurable limit periods and notification hierarchy?
|
|
|
j. Does your system allow for the integration of additional printers and scanners both locally and externally?
|
|
|
1.4.3 Receiving and scheduling
|
Request for information
|
Requirement code
|
Vendor response
|
a. Does your system create and maintain an electronic accession record for each accession received?
|
|
|
b. Does your system support standard-format digital picture and document upload and attachment to electronic accession records?
|
|
|
c. Does your system support a user-configurable, spreadsheet-style, templated multi-sample (batch) login without requiring additional programming?
|
|
|
d. Does your system support the modification of sample or sample batch information prior to actual multi-sample (batch) login?
|
|
|
e. Does your system support ad-hoc samples not predefined in the sample point list during multi-sample (batch) login?
|
|
|
f. Does your system create, save, and recall pre-login groups for routine samples to simplify recurring logins?
|
|
|
g. Does your system streamline the login of recurring sampling projects?
|
|
|
h. Does your system automatically generate labels for recurring samples and sample groups?
|
|
|
i. Does your system allow authorized users to generate user-definable chain of custodies, worksheets, routing sheets, and custom labels upon sample login?
|
|
|
j. Does your system provide 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, all without requiring additional programming?
|
|
|
k. Does your system include comprehensive sample scheduling, tracking, and sample flow management?
|
|
|
l. Does your system allow authorized users to schedule routine samples on an hourly, daily, weekly, or monthly basis, allowing them to be enabled and disabled as a group?
|
|
|
m. Does your system generate an hourly, daily, weekly, or monthly sampling schedule from a schedule database?
|
|
|
n. Does your system support automatic assignment and scheduling of analysis requests?
|
|
|
o. Can your system receive accession/analysis request information from web-enabled forms?
|
|
|
p. Can your system process automated uploading of field-derived sample collection data?
|
|
|
q. Does your system allows users to handle billable and non-billable tests on the same accession?
|
|
|
r. Does your system support tracking of shipping and receiving?
|
|
|
1.4.4 Analysis and data entry
|
Request for information
|
Requirement code
|
Vendor response
|
a. Does your system support a variety of test protocols, each capable of storing test comments, test required, and special information like GCMS conditions or special objects associated with the test? Please give details.
|
|
|
b. Does your system provide normal data range values for diagnostic tests?
|
|
|
c. Does your system includes default input values for diagnostic tests?
|
|
|
d. Does your system provide for a single test code requiring multiple analytes as targets?
|
|
|
e. Does your system limit test code authorization to only qualified personnel and maintain their certification(s) to run assigned tests?
|
|
|
f. Does your system support and qualify text-based tests?
|
|
|
g. Does your system support single-component tests such as pH, BOD, CD, etc.?
|
|
|
h. Does your system allow users to specify a single-component, multi-component, or narrative text test or group of tests, which represent all tests required?
|
|
|
i. Does your system permit user-generated and modifiable Excel calculations to be applied to all tests?
|
|
|
j. Does your system distinguish between routine and duplicate analysis?
|
|
|
k. Does your system provide an overview of all outstanding tests/analyses for better coordination of work schedules?
|
|
|
l. Does your system electronically transfer an item during testing from one functional area to another?
|
|
|
m. Does your system's user interface display visual indicators such as status icons to indicate a sample's status in the workflow?
|
|
|
n. Does your system update sample/item status when tests are completed?
|
|
|
o. Does your system read results from previously entered tests to calculate a final result and immediately display the calculated result?
|
|
|
p. Does your system allow authorized users to review all analytical results, including pricing, spec violations, history or trend analysis by analyte, and comments?
|
|
|
q. Does your system allow on-screen review of the stored test result, diluted result with corrected method detection limits (MDLs), and qualifiers after running samples for multiple dilutions as in gas chromatography–mass spectrometry (GC-MS)?
|
|
|
r. Does your system display the standard operating procedure (SOP) associated with each test result to ensure proper techniques were used?
|
|
|
s. Does your system store test-related analysis comments with the test?
|
|
|
t. Does your system provide for high-volume multi-component transfers of test results, with the ability to automatically match samples to data files in either a backlog mode or a designated file mode, to parse the data, and to review and commit the sample data?
|
|
|
u. Does your system's results validation process access all information about a sample or group of samples, including comments or special information about the sample?
|
|
|
v. Does your system's results validation process check each result against its individual sample location specifications (both warning and specification limits)?
|
|
|
w. Does your system support validation at the analysis and sample level, while also prohibiting sample validation when analysis validation is incomplete?
|
|
|
x. Does your system use a menu-driven process for results validation?
|
|
|
y. Does your system provide secure electronic peer review of results?
|
|
|
z. Does your system validate/approve data prior to being moved to the main database?
|
|
|
aa. Does your system fully manage all aspects of laboratory quality control, including the reporting and charting of all quality control data captured in the lab? Please explain how.
|
|
|
ab. Does your system provide a base for a quality assurance program, including proficiency testing, scheduled maintenance of equipment, etc.? Please explain how.
|
|
|
ac. Does your system distinguishe between QA/QC duplicates and normal samples?
|
|
|
ad. Does your system allow QA/QC tests to be easily created and associated with the primary analytical test?
|
|
|
ae. Does your system calculate monthly QA/QC percentages for testing?
|
|
|
af. Does your system automatically flag out-of-range quality control limits?
|
|
|
ag. Does your system check data files for specification and corrects them for specific reporting and analyte limits and qualifiers like dilution factor, automatically assigning qualifiers based on project analyte limiting?
|
|
|
ah. Does your system allow file transfer of data from instrument or user-generated files, with full on-screen review prior to database commitment?
|
|
|
ai. Does your system permit manual data entry into an electronic worksheet of test measurements and results?
|
|
|
aj. Does your system allow incorrectly inputted data to be manually corrected?
|
|
|
ak. Does your system provide colored visual indication of previously entered data as well as new data associated with a single sample when a result is entered, with the indicator changing color if the value is out of specification?
|
|
|
al. Does your system permit result entry via intelligent instrument interfaces or multi-sample/multi-test ASCII files?
|
|
|
am. Does your system allow automated or semi-automated data insertion?
|
|
|
an. Does your system provide auto-commenting for common laboratory result comments?
|
|
|
ao. Does your system store non-narrative textual results in searchable fields?
|
|
|
1.4.5 Instruments
|
Request for information
|
Requirement code
|
Vendor response
|
a. Does your system bilaterally interface with instruments and related software? If so, please provide details.
|
|
|
b. Can your system download data directly from laboratory instruments?
|
|
|
c. Does your system permit the defining and exporting of sequences to instruments?
|
|
|
d. Does your system provide a database of preventative maintenance, calibration, and repair records for laboratory equipment, preferably supported by standardized reporting?
|
|
|
e. Can your system schedule calibration/verification tasks in the worksheets or work flow process?
|
|
|
1.4.6 External system interfaces
|
Request for information
|
Requirement code
|
Vendor response
|
a. Does your system support a library of common and/or basic electronic data deliverable (EDD) formats? If so, which?
|
|
|
b. Can your system transfer data to and from another record management system?
|
|
|
c. Does your system integrate with Microsoft Exchange services?
|
|
|
d. Can your system import data from and export data to Microsoft Word, Excel, and/or Access?
|
|
|
e. Can your system interface with non-Microsoft programs? If so, which?
|
|
|
f. Can your system interface with contract laboratories to electronically retrieve datasheets, sample analysis, and other related information?
|
|
|
g. Can your system exchange data with National Identification System (NAIS) tracking systems?
|
|
|
h. Can your system direct output from ad-hoc queries to a computer file for subsequent analysis by other software?
|
|
|
i. Does your system support dockable mobile devices and handle information exchange between them and the system?
|
|
|
1.4.7 Reporting
|
Request for information
|
Requirement code
|
Vendor response
|
a. System clearly differentiates released preliminary data from fully validated results
|
|
|
b. System electronically transmits results via final report only when all case reviews have been completed by the case coordinator
|
|
|
c. System can automatically post periodic static summary reports on an internal web server
|
|
|
d. System provides ad-hoc web reporting interface to report on user-selected criteria
|
|
|
e. System can transmit results in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT
|
|
|
f. System supports multiple web browsers when viewing online reports
|
|
|
g. System capable of creating QA/QC charts for all recovery, precision, and lab control samples via a full statistics package
|
|
|
h. System includes several standard reports and query routines to access all samples with the pending status through a backlog report that includes the following criteria: all laboratory, department, analysis, submittal date, collection date, prep test complete, location, project, sample delivery group, and other user-selectable options
|
|
|
i. System produces a read-only progress report that allows printed reports of sample status and data collected to date
|
|
|
j. System automatically creates and transmits a separate exception report for all stored out-of-specification data
|
|
|
k. System displays history of previous results for an analyte's sample point in a tabular report, graphic trend chart, and statistical summary
|
|
|
l. System creates and transmits exception trails and reporting for all entered out-of-specification results
|
|
|
m. System permits sample progress reports to be viewed locally or remotely based on security application limits and/or sample ownership
|
|
|
n. System prevents a sample from being placed in a report queue until approved
|
|
|
o. System includes a versatile report writer and forms generator
|
|
|
p. System includes a custom graphic generator for forms
|
|
|
q. System allows development of specific templates for different types of reports
|
|
|
r. System can produce management and turn-around time reports and graphs
|
|
|
s. System can produce customized final reports
|
|
|
t. System can create and automatically update control charts
|
|
|
u. System generates, stores, reproduces, and displays laboratory reports on demand, including narrative
|
|
|
v. System generates, stores, reproduces, and displays laboratory, statistical, and inventory reports on demand, including narrative
|
|
|
w. System can send on-screen output to printer or file
|
|
|
x. System allow users to query and print chain of custody
|
|
|
y. System supports report queries by fields/keys, status, completion, or other variables
|
|
|
z. System prohibits issuing reports outside of qualified areas
|
|
|
aa. System can generate reports from any data in tables
|
|
|
ab. System uses Microsoft Office tools for formatting reports
|
|
|
ac. System can automatically produce laboratory reports of findings and other written documents
|
|
|
ad. System can automatically produce individual and aggregate workload and productivity reports on all operational and administrative activities
|
|
|
ae. System can generate template letters for semi-annual reports
|
|
|
af. System permits database access using user-friendly report writing and inquiry tools
|
|
|
ag. System maintains template versions and renditions, allowing management and tracking of the template over time
|
|
|
1.4.8 Laboratory management
|
Request for information
|
Requirement code
|
Vendor response
|
a. System allows search of invoice information by invoice number, account number, accession, payment types, client, or requested diagnostic test(s)
|
|
|
c. System allows management of documents like SOPs, MSDS, etc. to better ensure they are current and traceable
|
|
|
d. System provides email notification of lockout, security access, and improper workstation access
|
|
|
e. System includes a performance assessment tracking method
|
|
|
f. System allows users to monitor reagent use and chemical expirations
|
|
|
g. System monitors proficiency test assignment, completion, and casework qualification for analytical staff
|
|
|
h. System allows authorized persons to assign work to analysts
|
|
|
i. System allows authorized persons to review pending work by analyst prior to assigning additional work
|
|
|
j. System allows authorized persons to review unassigned work by discipline and lab
|
|
|
k. System permits the management of information workflow, including notifications for requests and exigencies
|
|
|
l. System allows authorized persons to select and assign tasks by analysts, work group, instrument, test, sample, and priority
|
|
|
m. System permits records management and monitors resources by analyst, priority, analysis, and instrument
|
|
|
n. System provides analysis tools for laboratory operations to better support resource planning, productivity projections, workload distribution, and work scheduling
|
|
|
o. System calculates administrative and lab cost
|
|
|
p. System tracks number of visits per specific industry
|
|
|
p. System allows creation, modification, and duplication of user profiles
|
|
|
|