|
|
| (76 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | | #REDIRECT [[User:Shawndouglas/Sandbox]] |
| {{ombox
| |
| | type = notice
| |
| | style = width: 960px;
| |
| | text = This is my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see [[User_talk:Shawndouglas|my discussion page]] instead.<p></p>
| |
| }}
| |
| | |
| ==Sandbox begins below==
| |
| | |
| :1.1 '''Evaluation demonstration requirements'''
| |
| ::a. The solution must be available for full demonstration (preferably online), and the provider must be able to conduct an on-site demonstration. Explain your ability to meet these conditions.
| |
| :1.2 '''IT requirements'''
| |
| ::1.2.1 IT General
| |
| :::a. Single database that supports multiple laboratory sites and laboratory departments
| |
| | |
| | |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.1 '''Vendor requirements'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Vendor offers full demonstration (preferably online) and can conduct an on-site demonstration
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Vendor provides optional comprehensive set of test codes suitable for use by the purchasing facility
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Vendor provides a support schedule for the implementation process, including optional levels
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Vendor can detail the amount of time and staff that purchaser will have to provide for the implementation process
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Vendor can explain function and availability of additional support capabilities
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Vendor has a consistent training methodology for training new users
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Vendor provides support during the "go-live" period between system validation/operational deployment and final acceptance/beginning of maintenance and support agreements
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Vendor provides design qualification documentation
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Vendor provides installation qualification documentation
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Vendor provides operation qualification documentation
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Vendor provides performance qualification documentation during implementation
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Vendor provides user, administrator, developer, installation, and reference manuals
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Vendor provides a gap analysis after initial system installation, identifying the deliverables or tasks remaining
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Vendor provides description of maintenance and support offered during and after implementation, including times and methods of availability, issue escalation and management, etc.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Vendor provides a detailed project approach and project plan that includes the project team, timeline, deliverables, and risk and issue management procedures
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Vendor provides a table linking each deliverable to the corresponding user requirement specification it fulfills
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Vendor provides a reliable cost estimates and pricing schedules, including all products and services included in the scope of work
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Vendor supplies LIMS-specific training program curricula
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Vendor supplies information about their overall project approach, acknowledgement of the deliverables, time/schedule constraints, and any other criteria for the project
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.2 '''IT requirements'''
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.2.1 '''IT general'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Single database that supports multiple laboratory sites and laboratory departments
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Client passwords encrypted in database with support for multi-case and special characters
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Secured Socket Layer (SSL) encryption on web client interface
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' System designed so upgrades to back-end database do not require extensive reconfiguration or effectively cripple the system
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' System provides all secured users access to its data via the Internet, LAN, or direct modem connection
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' LIMS database conforms to [[ODBC|Open Database Connectivity Standard]] (ODBC)
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' All LIMS system files capable of having security applied to them
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' All servers and workstations accessing LIMS system have login security
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' LIMS able to use TCP/IP as its network transport
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Sized to not be impacted by multiple users or failover processes
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Archive utility without off-line
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' System provides a workstation and server authentication mechanism
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' System provides local restore capability without support intervention
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' System Interfaces with database using ASP/ASP.net
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' System able to maintain transactional history
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.2 '''Hardware environment'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' System compatible with the hardware environment
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.3 '''Software environment'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' System utilizes a non-proprietary database such as Oracle or Microsoft SQL Server
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' System compatible with the software environment
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.3 '''Regulatory compliance requirements'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' LIMS has security consistent with [[21 CFR Part 11]] and [[40 CFR Part 3]]; system has security to enter the system, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature; provides a single point of access for all programs associated with the system for ease of administration and use
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' [[Audit trail]] and specifications violation trails maintained; audit trail includes result changes, header information changes, as well as the user, date/time, and a required reason for the changes as a standard part of the application
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' System maintains an audit trail of all data manipulation, consistent with all applicable regulations and standards
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' System provides user selectable [[The NELAC Institute|NELAP]]-compliant internal [[chain of custody]] that tracks all samples and associated containers from the time they are collected until disposed of
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' System meets all standards of [[The NELAC Institute]]
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' System provides persistent auditing capabilities
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' System meets government requirements for handling classified information and documents
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' System includes automatic date and time stamping
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' System provides the ability to insert/manage secure electronic and/or digital signatures
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' System supports [[ISO/IEC 17025]]
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' System supports [[21 CFR Part 11]]
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' System supports [[40 CFR Part 3]]
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' System supports [[HIPAA]] requirements
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' System supports [[GALP]] and/or [[GAMP]] standards
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.4 '''General functional requirements'''
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.4.1 '''General'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' System supports barcoded specimen labeling and tracking
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' System supports multiple customer payment sources (e.g. grants}
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' System can track current status of diagnostic tests in an accession
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' System contains spell-check dictionary that allows authorized users to add, edit, or remove entries
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' LIMS includes system administration ability to reset user passwords
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' LIMS can interface with or import existing data
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' LIMS can be configured to meet the characteristics of the laboratory
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' System capable of storing multiple sample-related objects such as pictures, documents, PDF files, etc., including any instrument-generated format outputs from equipment
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' System provides for application-based security by limiting external users to functions they are password-privileged to perform
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' System provides sample tracking from login through final reporting and invoicing
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' System produces internal chain of custody data to track individual sample containers and test results
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' System eliminates (or significantly reduces) redundant data entry and paper trail
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' System manages archived, paper-based laboratory records
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' System has a screen print function
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' System has an analyst communication log
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' System has configurable role-based security
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' System utilizes role-based presentation of menus and functions
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''v.''' System has supervisor override of chain of custody
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''w.''' System provides automatic logout based on keyboard or mouse inactivity
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''x.''' System prompts users for a reason for changes to database record
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''y.''' System allows authorized personnel to review audit logs
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''z.''' System's numbering scheme allows for sub-numbering while maintaining parent-child relationships
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aa.''' Chain of custody is printable for items, cases, projects, and batches
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ab.''' System has inter-lab transfer function
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ac.''' System allows queries of legacy data
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ad.''' Audit log retains all data, prohibits any deletions, and allows user comments
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ae.''' System search engine permits multiple search criteria
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''af.''' System permits remote access for users, system admins, and support agents
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ag.''' System supports the definition and maintenance of edit tables and lists
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ah.''' System allows modification of records by system admins, with audit trail
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ai.''' System allows entry, maintenance, and administration of customers, suppliers, and other outside entities
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aj.''' System links or embeds standard operation procedure (SOP) access
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''al.''' System provides an intuitive, user-friendly graphical user interface (GUI), consistent with Microsoft products
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''am.''' System captures data from all laboratory processes, ensuring uniformity of statistical reporting and other electronic data shared with designated users of the data
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''an.''' System provides data archival and retention functionality
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ao.''' System efficiently utilizes standardized data input points and enhanced individual workload tracking
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ap.''' System provides full database keyword and field search capability
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aq.''' System provides read-only access to contract laboratory results
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ar.''' System allows use of navigation keys to freely move from field to field
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''as.''' System allows data tables to be sorted
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''at.''' System issues sequential numbers for chain of custody
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''au.''' System allows multiple users to connect simultaneously to contract lab
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''av.''' System notifies users of events like the scheduling, receipt, and completion of tasks
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aw.''' System includes the ability to set up alerts via email
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ax.''' System includes the ability to search multiple databases
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ay.''' System supports multiple users entering data simultaneously
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''az.''' Data migrated into system converts cleanly to allow for reporting of historical sample collection
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.2 '''Configuration and customization'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' User can independently add fields without requiring reconfiguration of the system after routine upgrades and maintenance
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' System supports customized screens with user-definable information specific to an analysis
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' System can expand to accommodate a new discipline
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' System can integrate additional printers and scanners
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' System allows the system admin to create custom screens, apps, and reports
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' System dynamically changes captions (labels) on system fields
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' System has dynamically configurable limit periods and notification hierarchy
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' System can be easily and efficiently modified to meet lab growth and changing business needs
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.3 '''Receiving and scheduling'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' System creates and maintains an electronic accession record for each accession received
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Electronic accession records support digital picture and document uploads in standard formats
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' System allows users to handle billable and non-billable tests on the same accession
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' System supports tracking of shipping and receiving
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' System can receive accession/analysis request information from web-enabled forms
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' System can process automated uploading of field-derived sample collection data
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' System supports a user-configurable, spreadsheet-style, templated multi-sample login without requiring additional programming
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Multi-sample login supports the modification of sample or sample batch information prior to actual login
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Multi-sample login supports ad-hoc samples not predefined in the sample point list
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' System can print user-definable chain of custodies, worksheets, routing sheets, and custom labels upon login
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' System creates, saves, and recalls pre-login groups for routine samples to simplify recurring logins
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' System includes comprehensive sample scheduling, tracking, and sample flow management
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''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
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' System schedules routine samples on an hourly, daily, weekly, or monthly basis, allowing them to be enabled and disabled as a group
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' System streamlines login of recurring sampling projects
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' System supports automatic assignment of analysis requests
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' System can generate a monthly sampling schedule from a schedule database
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' System can generate labels for recurring samples and sample groups
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
