Difference between revisions of "User:Shawndouglas/sandbox/sublevel3"

From LIMSWiki
Jump to navigationJump to search
(Updated format)
(Fixed some of the table code.)
Line 52: Line 52:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.101''' The system operates with a web-based interface, hosted on a server and accessed via a web browser on most any machine.  
   | style="padding:5px; width:1200px;" |'''1.1.101''' The system operates with a web-based interface, hosted on a server and accessed via a web browser on most any machine.  
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 58: Line 58:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.102''' The system contains a single, centralized database that supports multiple sites and departments.
   | style="padding:5px; width:1200px;" |'''1.1.102''' The system contains a single, centralized database that supports multiple sites and departments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 64: Line 64:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.103''' The system's database conforms to the [[ODBC|Open Database Connectivity Standard]] (ODBC).
   | style="padding:5px; width:1200px;" |'''1.1.103''' The system's database conforms to the [[ODBC|Open Database Connectivity Standard]] (ODBC).
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 70: Line 70:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.104''' The system is designed so upgrades to the back-end database do not require extensive reconfiguration or effectively cripple the system.
   | style="padding:5px; width:1200px;" |'''1.1.104''' The system is designed so upgrades to the back-end database do not require extensive reconfiguration or effectively cripple the system.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 76: Line 76:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.105''' The system is designed to not be impacted by multiple users or failover processes.
   | style="padding:5px; width:1200px;" |'''1.1.105''' The system is designed to not be impacted by multiple users or failover processes.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 82: Line 82:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.106''' The system applies security features to all system files.
   | style="padding:5px; width:1200px;" |'''1.1.106''' The system applies security features to all system files.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 88: Line 88:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.107''' The system applies log-in security to all servers and workstations accessing it.
   | style="padding:5px; width:1200px;" |'''1.1.107''' The system applies log-in security to all servers and workstations accessing it.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 94: Line 94:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.108''' The system provides a workstation and server authentication mechanism.
   | style="padding:5px; width:1200px;" |'''1.1.108''' The system provides a workstation and server authentication mechanism.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 100: Line 100:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.109''' The system applies Secured Socket Layer (SSL) encryption on the web client interface.
   | style="padding:5px; width:1200px;" |'''1.1.109''' The system applies Secured Socket Layer (SSL) encryption on the web client interface.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 106: Line 106:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.110''' The system encrypts client passwords in a database, with support for multi-case and special characters.
   | style="padding:5px; width:1200px;" |'''1.1.110''' The system encrypts client passwords in a database, with support for multi-case and special characters.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 112: Line 112:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.111''' The system uses TCP/IP as its network transport.
   | style="padding:5px; width:1200px;" |'''1.1.111''' The system uses TCP/IP as its network transport.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 118: Line 118:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.112''' The system allows automated backup and restore capability without support intervention, as well as manual backups.
   | style="padding:5px; width:1200px;" |'''1.1.112''' The system allows automated backup and restore capability without support intervention, as well as manual backups.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 124: Line 124:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.113''' The system maintains the transactional history of system administrators.
   | style="padding:5px; width:1200px;" |'''1.1.113''' The system maintains the transactional history of system administrators.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 140: Line 140:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.200''' The system proves compatible with a variety of hardware environments.
   | style="padding:5px; width:1200px;" |'''1.1.200''' The system proves compatible with a variety of hardware environments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 146: Line 146:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.201''' The system can be utilized with a touch-screen.|
   | style="padding:5px; width:1200px;" |'''1.1.201''' The system can be utilized with a touch-screen.|
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 162: Line 162:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.300''' The system proves compatible with a variety of software environments.
   | style="padding:5px; width:1200px;" |'''1.1.300''' The system proves compatible with a variety of software environments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 168: Line 168:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.1.301''' The system utilizes a non-proprietary database such as Oracle or Microsoft SQL Server.
   | style="padding:5px; width:1200px;" |'''1.1.301''' The system utilizes a non-proprietary database such as Oracle or Microsoft SQL Server.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 188: Line 188:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.100''' The system can generate accurate and complete copies of records in both a human-readable and original electronic format for review and copying.
   | style="padding:5px; width:1200px;" |'''1.2.100''' The system can generate accurate and complete copies of records in both a human-readable and original electronic format for review and copying.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 194: Line 194:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.101''' The system supports [[21 CFR Part 11]] and [[EU Annex 11]] requirements, including log-in security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature.
   | style="padding:5px; width:1200px;" |'''1.2.101''' The system supports [[21 CFR Part 11]] and [[EU Annex 11]] requirements, including log-in security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 200: Line 200:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.102''' The system supports USP <232>/<233> requirements.
   | style="padding:5px; width:1200px;" |'''1.2.102''' The system supports USP <232>/<233> requirements.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 206: Line 206:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.103''' The system supports [[GALP]] and/or [[GAMP]] standards.
   | style="padding:5px; width:1200px;" |'''1.2.103''' The system supports [[GALP]] and/or [[GAMP]] standards.
  |-   
  |-   
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 212: Line 212:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.104''' The system supports the U.S. DoD 5015.2 Standard.
   | style="padding:5px; width:1200px;" |'''1.2.104''' The system supports the U.S. DoD 5015.2 Standard.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 218: Line 218:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.105''' The system maintains date- and time-stamped [[audit trail|audit trails]] of all data manipulation — such as changes to results, data analysis parameters, and methods — as consistent with all applicable regulations and standards, making the information available for review, copying, and reporting to authorized users.
   | style="padding:5px; width:1200px;" |'''1.2.105''' The system maintains date- and time-stamped [[audit trail|audit trails]] of all data manipulation — such as changes to results, data analysis parameters, and methods — as consistent with all applicable regulations and standards, making the information available for review, copying, and reporting to authorized users.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 224: Line 224:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.106''' The system audit log retains all data, prohibits any deletions, and allows user comments.
   | style="padding:5px; width:1200px;" |'''1.2.106''' The system audit log retains all data, prohibits any deletions, and allows user comments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 230: Line 230:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.107''' The system maintains audit trails at least as long as the records to which they pertain.
   | style="padding:5px; width:1200px;" |'''1.2.107''' The system maintains audit trails at least as long as the records to which they pertain.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 236: Line 236:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.108''' The system provides additional persistent auditing capabilities, such as the audit of cancelled uploads and scheduled system functions.
   | style="padding:5px; width:1200px;" |'''1.2.108''' The system provides additional persistent auditing capabilities, such as the audit of cancelled uploads and scheduled system functions.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 242: Line 242:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.109''' The system provides the ability to both automatically and manually add secure [[ELN feature#Electronic signatures|electronic signatures]] to documents and other data.
   | style="padding:5px; width:1200px;" |'''1.2.109''' The system provides the ability to both automatically and manually add secure [[ELN feature#Electronic signatures|electronic signatures]] to documents and other data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 248: Line 248:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.110''' The system can automatically validate and approve data prior to being moved to the main database.
   | style="padding:5px; width:1200px;" |'''1.2.110''' The system can automatically validate and approve data prior to being moved to the main database.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 264: Line 264:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.200''' The system allows administrators and other authorized users to configure multiple levels of user rights and security by site location, department, group, [[LIMS feature#Configurable roles and security|role]], and/or specific function.
   | style="padding:5px; width:1200px;" |'''1.2.200''' The system allows administrators and other authorized users to configure multiple levels of user rights and security by site location, department, group, [[LIMS feature#Configurable roles and security|role]], and/or specific function.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 270: Line 270:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.201''' The system allows administrators and users to reset user passwords.
   | style="padding:5px; width:1200px;" |'''1.2.201''' The system allows administrators and users to reset user passwords.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 276: Line 276:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.202''' The system features and enforces adjustable rules concerning password complexity, reuse, and expiration.
   | style="padding:5px; width:1200px;" |'''1.2.202''' The system features and enforces adjustable rules concerning password complexity, reuse, and expiration.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 282: Line 282:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.203''' The system can lock a user out after a specified number of consecutive failed log-in attempts.
   | style="padding:5px; width:1200px;" |'''1.2.203''' The system can lock a user out after a specified number of consecutive failed log-in attempts.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 288: Line 288:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.204''' The system provides the option for automatic user logout based on keyboard or mouse inactivity.
   | style="padding:5px; width:1200px;" |'''1.2.204''' The system provides the option for automatic user logout based on keyboard or mouse inactivity.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 294: Line 294:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.205''' The system makes authority checks to ensure only authorized individuals can use the system to perform an operation.
   | style="padding:5px; width:1200px;" |'''1.2.205''' The system makes authority checks to ensure only authorized individuals can use the system to perform an operation.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 300: Line 300:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.206''' The system allows authorized users to modify records, while also maintaining an audit trail of such actions.
   | style="padding:5px; width:1200px;" |'''1.2.206''' The system allows authorized users to modify records, while also maintaining an audit trail of such actions.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 306: Line 306:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.207''' The system allows authorized users to manually delete records, while also maintaining an audit trail of such actions.
   | style="padding:5px; width:1200px;" |'''1.2.207''' The system allows authorized users to manually delete records, while also maintaining an audit trail of such actions.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 312: Line 312:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.208''' The system prompts users to declare a reason for making changes to or deleting data in the system.
   | style="padding:5px; width:1200px;" |'''1.2.208''' The system prompts users to declare a reason for making changes to or deleting data in the system.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 318: Line 318:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.209''' The system allows authorized users to generate a detailed user access record.
   | style="padding:5px; width:1200px;" |'''1.2.209''' The system allows authorized users to generate a detailed user access record.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 324: Line 324:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.210''' The system provides email notification of lockout, security access, and improper workstation access.
   | style="padding:5px; width:1200px;" |'''1.2.210''' The system provides email notification of lockout, security access, and improper workstation access.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 330: Line 330:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.211''' The system provides a mechanism to allow a user read-only access to stored data.
   | style="padding:5px; width:1200px;" |'''1.2.211''' The system provides a mechanism to allow a user read-only access to stored data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 336: Line 336:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.212''' The system allows automatic and/or manual holds or locks to be placed on data to ensure it goes unaltered or remains retrievable during a retention period.
   | style="padding:5px; width:1200px;" |'''1.2.212''' The system allows automatic and/or manual holds or locks to be placed on data to ensure it goes unaltered or remains retrievable during a retention period.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 342: Line 342:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.213''' The system can first feed data from connected non-CFR-compliant instruments through a virtual environment that is compliant (audit trailed, secure, versioned, etc.) before being stored.
   | style="padding:5px; width:1200px;" |'''1.2.213''' The system can first feed data from connected non-CFR-compliant instruments through a virtual environment that is compliant (audit trailed, secure, versioned, etc.) before being stored.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 348: Line 348:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.214''' The system can control whether users are able to export data to portable long-term storage media like a USB flash drive or recordable DVD.
   | style="padding:5px; width:1200px;" |'''1.2.214''' The system can control whether users are able to export data to portable long-term storage media like a USB flash drive or recordable DVD.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 354: Line 354:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.215''' The system employs automatic file encryption on stored data.
   | style="padding:5px; width:1200px;" |'''1.2.215''' The system employs automatic file encryption on stored data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 360: Line 360:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.2.216''' The system employs checks to enforce permitted sequencing of steps and events.
   | style="padding:5px; width:1200px;" |'''1.2.216''' The system employs checks to enforce permitted sequencing of steps and events.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 380: Line 380:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.100''' The system offers non-SDMS 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 stored data.
   | style="padding:5px; width:1200px;" |'''1.3.100''' The system offers non-SDMS 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 stored data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 386: Line 386:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.101''' The system allows authorized users to configure their GUI to a specific language, character set, and time zone.
   | style="padding:5px; width:1200px;" |'''1.3.101''' The system allows authorized users to configure their GUI to a specific language, character set, and time zone.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 392: Line 392:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.102''' The system permits remote access for users, system admins, and support agents.
   | style="padding:5px; width:1200px;" |'''1.3.102''' The system permits remote access for users, system admins, and support agents.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 398: Line 398:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.103''' The system allows for the use of navigation keys to freely move from field to field.
   | style="padding:5px; width:1200px;" |'''1.3.103''' The system allows for the use of navigation keys to freely move from field to field.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 404: Line 404:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.104''' The system allows tabular data to be sorted and filtered.
   | style="padding:5px; width:1200px;" |'''1.3.104''' The system allows tabular data to be sorted and filtered.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 410: Line 410:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.105''' The system can send on-screen output to a printer or file without contradicting view-only statuses.
   | style="padding:5px; width:1200px;" |'''1.3.105''' The system can send on-screen output to a printer or file without contradicting view-only statuses.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 416: Line 416:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.106''' The system contains one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries.
   | style="padding:5px; width:1200px;" |'''1.3.106''' The system contains one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 422: Line 422:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.107''' The system uses human-readable metadata tags to better describe, index, and store all captured and archived data.
   | style="padding:5px; width:1200px;" |'''1.3.107''' The system uses human-readable metadata tags to better describe, index, and store all captured and archived data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 428: Line 428:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.108''' The system can generate metadata tags via derived value rules.
   | style="padding:5px; width:1200px;" |'''1.3.108''' The system can generate metadata tags via derived value rules.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 434: Line 434:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.109''' The system allows users to manually add metadata tags to files.
   | style="padding:5px; width:1200px;" |'''1.3.109''' The system allows users to manually add metadata tags to files.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 440: Line 440:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.110''' The system provides full metadata, keyword, and field [[LIMS feature#Query capability|search capability]], including the use of multiple search criteria.
   | style="padding:5px; width:1200px;" |'''1.3.110''' The system provides full metadata, keyword, and field [[LIMS feature#Query capability|search capability]], including the use of multiple search criteria.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 446: Line 446:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.111''' The system allows users to search for similar records based upon a set of metadata tag values.
   | style="padding:5px; width:1200px;" |'''1.3.111''' The system allows users to search for similar records based upon a set of metadata tag values.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 452: Line 452:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.112''' The system allows users to build, save, and edit queries for future use.
   | style="padding:5px; width:1200px;" |'''1.3.112''' The system allows users to build, save, and edit queries for future use.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 458: Line 458:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.113''' The system can automate the search for and extraction of pertinent data, including the export of that data to external applications for additional processing and calculation.
   | style="padding:5px; width:1200px;" |'''1.3.113''' The system can automate the search for and extraction of pertinent data, including the export of that data to external applications for additional processing and calculation.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 464: Line 464:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.114''' The system allows users to attach comments to data and files.
   | style="padding:5px; width:1200px;" |'''1.3.114''' The system allows users to attach comments to data and files.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 470: Line 470:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.115''' The system's file viewer/explorer allow users to view native, processed, and archived data in its native file structure.
   | style="padding:5px; width:1200px;" |'''1.3.115''' The system's file viewer/explorer allow users to view native, processed, and archived data in its native file structure.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 476: Line 476:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.116''' The system can link objects to other objects, e.g. linking a standard operating procedure (SOP) to a test result.
   | style="padding:5px; width:1200px;" |'''1.3.116''' The system can link objects to other objects, e.g. linking a standard operating procedure (SOP) to a test result.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 482: Line 482:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.117''' The system [[LIMS feature#Alarms and/or alerts|notifies users]] of events like the scheduling and completion of tasks.
   | style="padding:5px; width:1200px;" |'''1.3.117''' The system [[LIMS feature#Alarms and/or alerts|notifies users]] of events like the scheduling and completion of tasks.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 488: Line 488:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.118''' The system includes the ability to set up alerts via email.
   | style="padding:5px; width:1200px;" |'''1.3.118''' The system includes the ability to set up alerts via email.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 494: Line 494:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.119''' The system offers integrated or online user help screens.
   | style="padding:5px; width:1200px;" |'''1.3.119''' The system offers integrated or online user help screens.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 500: Line 500:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.120''' The system includes data analysis and calculation tools.
   | style="padding:5px; width:1200px;" |'''1.3.120''' The system includes data analysis and calculation tools.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 516: Line 516:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.200''' The system architecture is modular or extensible and can easily and efficiently be modified to facilitate the addition of new functionality as business needs change.
   | style="padding:5px; width:1200px;" |'''1.3.200''' The system architecture is modular or extensible and can easily and efficiently be modified to facilitate the addition of new functionality as business needs change.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 522: Line 522:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.201''' The system has an application programming interface (API) or a similar software development toolkit (SDK). If web-based, the API should support Simple Object Access Protocol (SOAP), representational state transfer (REST), or both.
   | style="padding:5px; width:1200px;" |'''1.3.201''' The system has an application programming interface (API) or a similar software development toolkit (SDK). If web-based, the API should support Simple Object Access Protocol (SOAP), representational state transfer (REST), or both.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 528: Line 528:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.202''' The system allows a user to [[LIMS feature#Customizable fields and/or interface|independently add fields]] without requiring reconfiguration of the system, even after routine upgrades and maintenance.  
   | style="padding:5px; width:1200px;" |'''1.3.202''' The system allows a user to [[LIMS feature#Customizable fields and/or interface|independently add fields]] without requiring reconfiguration of the system, even after routine upgrades and maintenance.  
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 534: Line 534:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.203''' The system allows for the integration of additional printers and scanners both locally and externally.
   | style="padding:5px; width:1200px;" |'''1.3.203''' The system allows for the integration of additional printers and scanners both locally and externally.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 550: Line 550:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.300''' The system can manage and store both sample- and non-sample-related data, including images from microscopes, GCMS scans of peaks, PDF files, spreadsheets, or even raw data files from instrument runs for later processing.
   | style="padding:5px; width:1200px;" |'''1.3.300''' The system can manage and store both sample- and non-sample-related data, including images from microscopes, GCMS scans of peaks, PDF files, spreadsheets, or even raw data files from instrument runs for later processing.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 556: Line 556:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.301''' The system can manage and store media objects like digital photos, bitmaps, movies, and audio files.
   | style="padding:5px; width:1200px;" |'''1.3.301''' The system can manage and store media objects like digital photos, bitmaps, movies, and audio files.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 562: Line 562:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.302''' The system allows multiple native instruments and users to enter data into the system simultaneously without disruption.
   | style="padding:5px; width:1200px;" |'''1.3.302''' The system allows multiple native instruments and users to enter data into the system simultaneously without disruption.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 568: Line 568:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.303''' The system can interface with and [[LIMS feature#Import data|import existing data]] from other databases and file shares.
   | style="padding:5px; width:1200px;" |'''1.3.303''' The system can interface with and [[LIMS feature#Import data|import existing data]] from other databases and file shares.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 574: Line 574:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.304''' The system supports data capture from a Citrix-based environment.
   | style="padding:5px; width:1200px;" |'''1.3.304''' The system supports data capture from a Citrix-based environment.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 580: Line 580:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.305''' The system allows file indexes to be stored centrally while associated files are stored geographically.
   | style="padding:5px; width:1200px;" |'''1.3.305''' The system allows file indexes to be stored centrally while associated files are stored geographically.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 586: Line 586:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.306''' The system allows users to organize captured data by project, date, location, instrument, etc.
   | style="padding:5px; width:1200px;" |'''1.3.306''' The system allows users to organize captured data by project, date, location, instrument, etc.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 592: Line 592:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.307''' The system can route captured data based upon specified metadata tags.
   | style="padding:5px; width:1200px;" |'''1.3.307''' The system can route captured data based upon specified metadata tags.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 598: Line 598:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.308''' The system allows full on-screen review and approval of native instrument data prior to database commitment.
   | style="padding:5px; width:1200px;" |'''1.3.308''' The system allows full on-screen review and approval of native instrument data prior to database commitment.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 604: Line 604:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.309''' The system keeps all captured data and its format intact and captures modifications of that data as a version, including date and time of those modifications, for regulatory purposes.
   | style="padding:5px; width:1200px;" |'''1.3.309''' The system keeps all captured data and its format intact and captures modifications of that data as a version, including date and time of those modifications, for regulatory purposes.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 610: Line 610:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.310''' The system has a tool that allows users to capture data printed to it as a searchable PDF file.
   | style="padding:5px; width:1200px;" |'''1.3.310''' The system has a tool that allows users to capture data printed to it as a searchable PDF file.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 616: Line 616:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.311''' The system can automatically normalize and store incoming data to a technology-neutral format like XML.
   | style="padding:5px; width:1200px;" |'''1.3.311''' The system can automatically normalize and store incoming data to a technology-neutral format like XML.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 622: Line 622:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.312''' The system allows incoming and entered files to be converted into other open formats like JCAMP-DX, TraML, mzML, mzXML, AnIML, pepXML, and protXML.
   | style="padding:5px; width:1200px;" |'''1.3.312''' The system allows incoming and entered files to be converted into other open formats like JCAMP-DX, TraML, mzML, mzXML, AnIML, pepXML, and protXML.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 628: Line 628:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.313''' The system can capture and store native instrument and processed data based on a scheduled time or a real-time event, such as upon file creation.
   | style="padding:5px; width:1200px;" |'''1.3.313''' The system can capture and store native instrument and processed data based on a scheduled time or a real-time event, such as upon file creation.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 634: Line 634:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.314''' The system allows users to manually upload instrument data files that are not part of a scheduled upload.
   | style="padding:5px; width:1200px;" |'''1.3.314''' The system allows users to manually upload instrument data files that are not part of a scheduled upload.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 640: Line 640:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.315''' The system allows for the specification of a retention period for captured native instrument and processed data and can enact it based on date-based metadata fields or a future event.
   | style="padding:5px; width:1200px;" |'''1.3.315''' The system allows for the specification of a retention period for captured native instrument and processed data and can enact it based on date-based metadata fields or a future event.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 646: Line 646:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.316''' The system can remove data from client machines upon upload and/or backup, based on a schedule or retention policy.
   | style="padding:5px; width:1200px;" |'''1.3.316''' The system can remove data from client machines upon upload and/or backup, based on a schedule or retention policy.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 652: Line 652:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.317''' The system allows users to review, restore, and reprocess original native instrument data on the original instrument acquisition software.
   | style="padding:5px; width:1200px;" |'''1.3.317''' The system allows users to review, restore, and reprocess original native instrument data on the original instrument acquisition software.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 658: Line 658:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.318''' The system allows users to open and view captured native instrument files without restoring them.
   | style="padding:5px; width:1200px;" |'''1.3.318''' The system allows users to open and view captured native instrument files without restoring them.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 664: Line 664:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.319''' The system allows captured processed data to be reused by other applications without having to reprocess it.
   | style="padding:5px; width:1200px;" |'''1.3.319''' The system allows captured processed data to be reused by other applications without having to reprocess it.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 670: Line 670:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.320''' The system provides a method to extract data points from captured processed data and present it in a human-readable format.
   | style="padding:5px; width:1200px;" |'''1.3.320''' The system provides a method to extract data points from captured processed data and present it in a human-readable format.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 676: Line 676:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.321''' The system can parse captured data files containing specified metadata into a live results table.
   | style="padding:5px; width:1200px;" |'''1.3.321''' The system can parse captured data files containing specified metadata into a live results table.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 692: Line 692:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.400''' The system provides data archiving functionality for all contained data, without requiring an off-line mode.
   | style="padding:5px; width:1200px;" |'''1.3.400''' The system provides data archiving functionality for all contained data, without requiring an off-line mode.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 698: Line 698:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.401''' The system allows for a configurable scheduled archive, not requiring human interaction with the data to be archived.
   | style="padding:5px; width:1200px;" |'''1.3.401''' The system allows for a configurable scheduled archive, not requiring human interaction with the data to be archived.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 704: Line 704:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.402''' The system allows for a scheduled archive of data directly captured from a specific native instrument.
   | style="padding:5px; width:1200px;" |'''1.3.402''' The system allows for a scheduled archive of data directly captured from a specific native instrument.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 710: Line 710:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.403''' The system permits native instrument data to be archived and restored with its original directory structure.
   | style="padding:5px; width:1200px;" |'''1.3.403''' The system permits native instrument data to be archived and restored with its original directory structure.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 716: Line 716:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.404''' The system allows for the specification of a retention period for archived and migrated data and can enact it based on date-based metadata fields or a future event.
   | style="padding:5px; width:1200px;" |'''1.3.404''' The system allows for the specification of a retention period for archived and migrated data and can enact it based on date-based metadata fields or a future event.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 722: Line 722:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.405''' The system ensures that held or locked native instrument data not captured during a scheduled archive will be captured during the next scheduled archive.
   | style="padding:5px; width:1200px;" |'''1.3.405''' The system ensures that held or locked native instrument data not captured during a scheduled archive will be captured during the next scheduled archive.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 728: Line 728:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.406''' The system can perform archive and restore functions simultaneously with data capture and viewing functions, without disruption.
   | style="padding:5px; width:1200px;" |'''1.3.406''' The system can perform archive and restore functions simultaneously with data capture and viewing functions, without disruption.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 734: Line 734:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.407''' The system allows native instrument and processed data migrated from an old SDMS version to be backed up and restored without alteration.
   | style="padding:5px; width:1200px;" |'''1.3.407''' The system allows native instrument and processed data migrated from an old SDMS version to be backed up and restored without alteration.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 750: Line 750:
  |-   
  |-   
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.500''' The system bilaterally [[LIMS feature#Instrument interfacing and management|interfaces]] with instruments and related software based on the Unix and Windows platforms.
   | style="padding:5px; width:1200px;" |'''1.3.500''' The system bilaterally [[LIMS feature#Instrument interfacing and management|interfaces]] with instruments and related software based on the Unix and Windows platforms.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 756: Line 756:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.501''' The system can download data directly from laboratory instruments.
   | style="padding:5px; width:1200px;" |'''1.3.501''' The system can download data directly from laboratory instruments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 762: Line 762:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.502''' The system can track and report on the usage of attached laboratory instruments.
   | style="padding:5px; width:1200px;" |'''1.3.502''' The system can track and report on the usage of attached laboratory instruments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 768: Line 768:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.503''' The system can automatically (or manually allow an authorized user to) remove an instrument from potential use when it falls out of tolerance limit or requires scheduled calibration.
   | style="padding:5px; width:1200px;" |'''1.3.503''' The system can automatically (or manually allow an authorized user to) remove an instrument from potential use when it falls out of tolerance limit or requires scheduled calibration.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 774: Line 774:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.504''' The system maintains a reportable database of preventative maintenance, calibration, and repair records for attached laboratory instruments.
   | style="padding:5px; width:1200px;" |'''1.3.504''' The system maintains a reportable database of preventative maintenance, calibration, and repair records for attached laboratory instruments.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 780: Line 780:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.505''' The system can schedule calibration, verification, and maintenance tasks on attached instruments and make that schedule available for viewing.
   | style="padding:5px; width:1200px;" |'''1.3.505''' The system can schedule calibration, verification, and maintenance tasks on attached instruments and make that schedule available for viewing.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 786: Line 786:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.506''' The system allows users to create and edit instrument maintenance profiles.
   | style="padding:5px; width:1200px;" |'''1.3.506''' The system allows users to create and edit instrument maintenance profiles.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 802: Line 802:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.600.''' The system supports a library of common electronic data deliverable (EDD) formats.
   | style="padding:5px; width:1200px;" |'''1.3.600.''' The system supports a library of common electronic data deliverable (EDD) formats.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 808: Line 808:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.601''' The system can transfer data to and from other record management systems.
   | style="padding:5px; width:1200px;" |'''1.3.601''' The system can transfer data to and from other record management systems.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 814: Line 814:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.602''' The system [[LIS feature#Third-party software integration|integrates]] with Microsoft Exchange services.
   | style="padding:5px; width:1200px;" |'''1.3.602''' The system [[LIS feature#Third-party software integration|integrates]] with Microsoft Exchange services.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 820: Line 820:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.603''' The system can [[LIMS feature#Import data|import data]] from and export data to Microsoft Word, Excel, Access, and/or Powerpoint.
   | style="padding:5px; width:1200px;" |'''1.3.603''' The system can [[LIMS feature#Import data|import data]] from and export data to Microsoft Word, Excel, Access, and/or Powerpoint.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 826: Line 826:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.604''' The system can interface with non-Microsoft programs.
   | style="padding:5px; width:1200px;" |'''1.3.604''' The system can interface with non-Microsoft programs.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 832: Line 832:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.605''' The system can interface with enterprise resource planning (ERP) systems.
   | style="padding:5px; width:1200px;" |'''1.3.605''' The system can interface with enterprise resource planning (ERP) systems.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 838: Line 838:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.606''' The system can interface with internal and external laboratory systems like laboratory information management systems (LIMS) and electronic laboratory notebooks (ELNs).
   | style="padding:5px; width:1200px;" |'''1.3.606''' The system can interface with internal and external laboratory systems like laboratory information management systems (LIMS) and electronic laboratory notebooks (ELNs).
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 844: Line 844:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.607''' The system can leverage the application programming interface (API) of other systems to establish integration between systems.
   | style="padding:5px; width:1200px;" |'''1.3.607''' The system can leverage the application programming interface (API) of other systems to establish integration between systems.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 850: Line 850:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.608''' The system provides a real-time interface for viewing live and stored data transactions and errors generated by interfaced instruments and systems.
   | style="padding:5px; width:1200px;" |'''1.3.608''' The system provides a real-time interface for viewing live and stored data transactions and errors generated by interfaced instruments and systems.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 856: Line 856:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.609''' The system supports [[LIMS feature#Mobile device integration|dockable mobile devices]] and handles information exchange between them and the system.
   | style="padding:5px; width:1200px;" |'''1.3.609''' The system supports [[LIMS feature#Mobile device integration|dockable mobile devices]] and handles information exchange between them and the system.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 862: Line 862:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.610''' The system supports the use of optical character recognition (OCR) software.
   | style="padding:5px; width:1200px;" |'''1.3.610''' The system supports the use of optical character recognition (OCR) software.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 878: Line 878:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.700''' The system includes a versatile report writer and forms generator that can generate reports from any data in the system.
   | style="padding:5px; width:1200px;" |'''1.3.700''' The system includes a versatile report writer and forms generator that can generate reports from any data in the system.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 884: Line 884:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.701''' The system can interface with a third-party reporting application.
   | style="padding:5px; width:1200px;" |'''1.3.701''' The system can interface with a third-party reporting application.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 890: Line 890:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.702''' The system allows the development of [[LIMS feature#Custom reporting|custom templates]] for different types of reports.
   | style="padding:5px; width:1200px;" |'''1.3.702''' The system allows the development of [[LIMS feature#Custom reporting|custom templates]] for different types of reports.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 896: Line 896:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.703''' The system maintains template versions and renditions, allowing management and tracking of the template over time.
   | style="padding:5px; width:1200px;" |'''1.3.703''' The system maintains template versions and renditions, allowing management and tracking of the template over time.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 902: Line 902:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.704''' The system uses Microsoft Office tools for formatting reports.
   | style="padding:5px; width:1200px;" |'''1.3.704''' The system uses Microsoft Office tools for formatting reports.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 908: Line 908:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.705''' The system provides multiple ways to visualize data in reports, including graphs, trend bars, pie charts, spectrum, etc. for the purpose of presenting information and identifying trends.
   | style="padding:5px; width:1200px;" |'''1.3.705''' The system provides multiple ways to visualize data in reports, including graphs, trend bars, pie charts, spectrum, etc. for the purpose of presenting information and identifying trends.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 914: Line 914:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.706''' The system makes graphic and tabular data vector-scalable in reports.
   | style="padding:5px; width:1200px;" |'''1.3.706''' The system makes graphic and tabular data vector-scalable in reports.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 920: Line 920:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.707''' The system allows for internal hyperlinking to source data in reports.
   | style="padding:5px; width:1200px;" |'''1.3.707''' The system allows for internal hyperlinking to source data in reports.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 926: Line 926:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.708''' The system allows users to manually adjust inaccurate data parsing routines for reports.
   | style="padding:5px; width:1200px;" |'''1.3.708''' The system allows users to manually adjust inaccurate data parsing routines for reports.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 932: Line 932:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.709''' The system can indicate whether a report is preliminary, amended, corrected, or final while retaining revision history.
   | style="padding:5px; width:1200px;" |'''1.3.709''' The system can indicate whether a report is preliminary, amended, corrected, or final while retaining revision history.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 938: Line 938:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.710''' The system can automatically generate laboratory reports of findings and other written documents.
   | style="padding:5px; width:1200px;" |'''1.3.710''' The system can automatically generate laboratory reports of findings and other written documents.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 944: Line 944:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.711''' The system provides an ad-hoc web reporting interface to report on user-selected criteria.
   | style="padding:5px; width:1200px;" |'''1.3.711''' The system provides an ad-hoc web reporting interface to report on user-selected criteria.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 950: Line 950:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.712''' The system can automatically generate and post periodic static summary reports on an internal web server.
   | style="padding:5px; width:1200px;" |'''1.3.712''' The system can automatically generate and post periodic static summary reports on an internal web server.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 956: Line 956:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.713''' The system can transmit reports in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT.
   | style="padding:5px; width:1200px;" |'''1.3.713''' The system can transmit reports in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 962: Line 962:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.714''' The system supports PDF/A, an ISO-standardized version of the Portable Document Format (PDF).
   | style="padding:5px; width:1200px;" |'''1.3.714''' The system supports PDF/A, an ISO-standardized version of the Portable Document Format (PDF).
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 968: Line 968:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.715''' The system includes a rules engine to determine the recipients of reports and other documents based on definable parameters.
   | style="padding:5px; width:1200px;" |'''1.3.715''' The system includes a rules engine to determine the recipients of reports and other documents based on definable parameters.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 974: Line 974:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.716''' The system provides printer-friendly audit trails for cleaner reporting of audit data.
   | style="padding:5px; width:1200px;" |'''1.3.716''' The system provides printer-friendly audit trails for cleaner reporting of audit data.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 980: Line 980:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.717''' The system provides an interface for external clients to search, generate, and view processed data reports based on metadata tags.
   | style="padding:5px; width:1200px;" |'''1.3.717''' The system provides an interface for external clients to search, generate, and view processed data reports based on metadata tags.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:
Line 986: Line 986:
  |-  
  |-  
   | style="padding:5px;" |
   | style="padding:5px;" |
   | style="padding:5px; width:500px;" |'''1.3.718''' The system provides document workflow management tools for streamlining their creation, review, modification, and approval.
   | style="padding:5px; width:1200px;" |'''1.3.718''' The system provides document workflow management tools for streamlining their creation, review, modification, and approval.
  |-
  |-
   ! style="background-color:white; width:100px;"| Response:
   ! style="background-color:white; width:100px;"| Response:

Revision as of 18:18, 22 October 2014

This is sublevel3 of my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see my discussion page instead.

Sandbox begins below

  • Y: Meets requirement in commercial off-the-shelf solution as delivered/configured (or vendor provides service)
  • YC: Meets requirement only with customization (additional code, using a third-party application, etc.)
  • N: Does not meet requirement
  • I: Informational response only, N/A


1.0 Demonstration

1.0 Demonstration
Requirement code Requirement # and requirement
1.0.000 The system can be tried via an online and/or on-site demonstration.
Response:

1.1 Information technology

1.1.1 General IT

1.1.1 General IT
Requirement code Requirement # and requirement
1.1.100 The system operates with a traditional client-server architecture, with software installed on each machine that needs to access the system.
Response:
1.1.101 The system operates with a web-based interface, hosted on a server and accessed via a web browser on most any machine.
Response:
1.1.102 The system contains a single, centralized database that supports multiple sites and departments.
Response:
1.1.103 The system's database conforms to the Open Database Connectivity Standard (ODBC).
Response:
1.1.104 The system is designed so upgrades to the back-end database do not require extensive reconfiguration or effectively cripple the system.
Response:
1.1.105 The system is designed to not be impacted by multiple users or failover processes.
Response:
1.1.106 The system applies security features to all system files.
Response:
1.1.107 The system applies log-in security to all servers and workstations accessing it.
Response:
1.1.108 The system provides a workstation and server authentication mechanism.
Response:
1.1.109 The system applies Secured Socket Layer (SSL) encryption on the web client interface.
Response:
1.1.110 The system encrypts client passwords in a database, with support for multi-case and special characters.
Response:
1.1.111 The system uses TCP/IP as its network transport.
Response:
1.1.112 The system allows automated backup and restore capability without support intervention, as well as manual backups.
Response:
1.1.113 The system maintains the transactional history of system administrators.
Response:

1.1.2 Hardware environment

1.1.2 Hardware environment
Requirement code Requirement # and requirement
1.1.200 The system proves compatible with a variety of hardware environments.
Response:
1.1.201 The system can be utilized with a touch-screen.|
Response:

1.1.3 Software environment

1.1.3 Software environment
Requirement code Requirement # and requirement
1.1.300 The system proves compatible with a variety of software environments.
Response:
1.1.301 The system utilizes a non-proprietary database such as Oracle or Microsoft SQL Server.
Response:

1.2 Regulatory compliance and security

1.2.1 Regulatory compliance

1.2.1 Regulatory compliance
Requirement code Requirement # and requirement
1.2.100 The system can generate accurate and complete copies of records in both a human-readable and original electronic format for review and copying.
Response:
1.2.101 The system supports 21 CFR Part 11 and EU Annex 11 requirements, including log-in security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature.
Response:
1.2.102 The system supports USP <232>/<233> requirements.
Response:
1.2.103 The system supports GALP and/or GAMP standards.
Response:
1.2.104 The system supports the U.S. DoD 5015.2 Standard.
Response:
1.2.105 The system maintains date- and time-stamped audit trails of all data manipulation — such as changes to results, data analysis parameters, and methods — as consistent with all applicable regulations and standards, making the information available for review, copying, and reporting to authorized users.
Response:
1.2.106 The system audit log retains all data, prohibits any deletions, and allows user comments.
Response:
1.2.107 The system maintains audit trails at least as long as the records to which they pertain.
Response:
1.2.108 The system provides additional persistent auditing capabilities, such as the audit of cancelled uploads and scheduled system functions.
Response:
1.2.109 The system provides the ability to both automatically and manually add secure electronic signatures to documents and other data.
Response:
1.2.110 The system can automatically validate and approve data prior to being moved to the main database.
Response:

1.2.2 Security

1.2.2 Security
Requirement code Requirement # and requirement
1.2.200 The system allows administrators and other authorized users to configure multiple levels of user rights and security by site location, department, group, role, and/or specific function.
Response:
1.2.201 The system allows administrators and users to reset user passwords.
Response:
1.2.202 The system features and enforces adjustable rules concerning password complexity, reuse, and expiration.
Response:
1.2.203 The system can lock a user out after a specified number of consecutive failed log-in attempts.
Response:
1.2.204 The system provides the option for automatic user logout based on keyboard or mouse inactivity.
Response:
1.2.205 The system makes authority checks to ensure only authorized individuals can use the system to perform an operation.
Response:
1.2.206 The system allows authorized users to modify records, while also maintaining an audit trail of such actions.
Response:
1.2.207 The system allows authorized users to manually delete records, while also maintaining an audit trail of such actions.
Response:
1.2.208 The system prompts users to declare a reason for making changes to or deleting data in the system.
Response:
1.2.209 The system allows authorized users to generate a detailed user access record.
Response:
1.2.210 The system provides email notification of lockout, security access, and improper workstation access.
Response:
1.2.211 The system provides a mechanism to allow a user read-only access to stored data.
Response:
1.2.212 The system allows automatic and/or manual holds or locks to be placed on data to ensure it goes unaltered or remains retrievable during a retention period.
Response:
1.2.213 The system can first feed data from connected non-CFR-compliant instruments through a virtual environment that is compliant (audit trailed, secure, versioned, etc.) before being stored.
Response:
1.2.214 The system can control whether users are able to export data to portable long-term storage media like a USB flash drive or recordable DVD.
Response:
1.2.215 The system employs automatic file encryption on stored data.
Response:
1.2.216 The system employs checks to enforce permitted sequencing of steps and events.
Response:

1.3 General system functions

1.3.1 General functions

1.3.1 General functions
Requirement code Requirement # and requirement
1.3.100 The system offers non-SDMS 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 stored data.
Response:
1.3.101 The system allows authorized users to configure their GUI to a specific language, character set, and time zone.
Response:
1.3.102 The system permits remote access for users, system admins, and support agents.
Response:
1.3.103 The system allows for the use of navigation keys to freely move from field to field.
Response:
1.3.104 The system allows tabular data to be sorted and filtered.
Response:
1.3.105 The system can send on-screen output to a printer or file without contradicting view-only statuses.
Response:
1.3.106 The system contains one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries.
Response:
1.3.107 The system uses human-readable metadata tags to better describe, index, and store all captured and archived data.
Response:
1.3.108 The system can generate metadata tags via derived value rules.
Response:
1.3.109 The system allows users to manually add metadata tags to files.
Response:
1.3.110 The system provides full metadata, keyword, and field search capability, including the use of multiple search criteria.
Response:
1.3.111 The system allows users to search for similar records based upon a set of metadata tag values.
Response:
1.3.112 The system allows users to build, save, and edit queries for future use.
Response:
1.3.113 The system can automate the search for and extraction of pertinent data, including the export of that data to external applications for additional processing and calculation.
Response:
1.3.114 The system allows users to attach comments to data and files.
Response:
1.3.115 The system's file viewer/explorer allow users to view native, processed, and archived data in its native file structure.
Response:
1.3.116 The system can link objects to other objects, e.g. linking a standard operating procedure (SOP) to a test result.
Response:
1.3.117 The system notifies users of events like the scheduling and completion of tasks.
Response:
1.3.118 The system includes the ability to set up alerts via email.
Response:
1.3.119 The system offers integrated or online user help screens.
Response:
1.3.120 The system includes data analysis and calculation tools.
Response:

1.3.2 Configuration and customization

1.3.2 Configuration and customization
Requirement code Requirement # and requirement
1.3.200 The system architecture is modular or extensible and can easily and efficiently be modified to facilitate the addition of new functionality as business needs change.
Response:
1.3.201 The system has an application programming interface (API) or a similar software development toolkit (SDK). If web-based, the API should support Simple Object Access Protocol (SOAP), representational state transfer (REST), or both.
Response:
1.3.202 The system allows a user to independently add fields without requiring reconfiguration of the system, even after routine upgrades and maintenance.
Response:
1.3.203 The system allows for the integration of additional printers and scanners both locally and externally.
Response:

1.3.3 Data capture

1.3.3 Data capture
Requirement code Requirement # and requirement
1.3.300 The system can manage and store both sample- and non-sample-related data, including images from microscopes, GCMS scans of peaks, PDF files, spreadsheets, or even raw data files from instrument runs for later processing.
Response:
1.3.301 The system can manage and store media objects like digital photos, bitmaps, movies, and audio files.
Response:
1.3.302 The system allows multiple native instruments and users to enter data into the system simultaneously without disruption.
Response:
1.3.303 The system can interface with and import existing data from other databases and file shares.
Response:
1.3.304 The system supports data capture from a Citrix-based environment.
Response:
1.3.305 The system allows file indexes to be stored centrally while associated files are stored geographically.
Response:
1.3.306 The system allows users to organize captured data by project, date, location, instrument, etc.
Response:
1.3.307 The system can route captured data based upon specified metadata tags.
Response:
1.3.308 The system allows full on-screen review and approval of native instrument data prior to database commitment.
Response:
1.3.309 The system keeps all captured data and its format intact and captures modifications of that data as a version, including date and time of those modifications, for regulatory purposes.
Response:
1.3.310 The system has a tool that allows users to capture data printed to it as a searchable PDF file.
Response:
1.3.311 The system can automatically normalize and store incoming data to a technology-neutral format like XML.
Response:
1.3.312 The system allows incoming and entered files to be converted into other open formats like JCAMP-DX, TraML, mzML, mzXML, AnIML, pepXML, and protXML.
Response:
1.3.313 The system can capture and store native instrument and processed data based on a scheduled time or a real-time event, such as upon file creation.
Response:
1.3.314 The system allows users to manually upload instrument data files that are not part of a scheduled upload.
Response:
1.3.315 The system allows for the specification of a retention period for captured native instrument and processed data and can enact it based on date-based metadata fields or a future event.
Response:
1.3.316 The system can remove data from client machines upon upload and/or backup, based on a schedule or retention policy.
Response:
1.3.317 The system allows users to review, restore, and reprocess original native instrument data on the original instrument acquisition software.
Response:
1.3.318 The system allows users to open and view captured native instrument files without restoring them.
Response:
1.3.319 The system allows captured processed data to be reused by other applications without having to reprocess it.
Response:
1.3.320 The system provides a method to extract data points from captured processed data and present it in a human-readable format.
Response:
1.3.321 The system can parse captured data files containing specified metadata into a live results table.
Response:

1.3.4 Data archiving and migration

1.3.4 Data archiving and migration
Requirement code Requirement # and requirement
1.3.400 The system provides data archiving functionality for all contained data, without requiring an off-line mode.
Response:
1.3.401 The system allows for a configurable scheduled archive, not requiring human interaction with the data to be archived.
Response:
1.3.402 The system allows for a scheduled archive of data directly captured from a specific native instrument.
Response:
1.3.403 The system permits native instrument data to be archived and restored with its original directory structure.
Response:
1.3.404 The system allows for the specification of a retention period for archived and migrated data and can enact it based on date-based metadata fields or a future event.
Response:
1.3.405 The system ensures that held or locked native instrument data not captured during a scheduled archive will be captured during the next scheduled archive.
Response:
1.3.406 The system can perform archive and restore functions simultaneously with data capture and viewing functions, without disruption.
Response:
1.3.407 The system allows native instrument and processed data migrated from an old SDMS version to be backed up and restored without alteration.
Response:

1.3.5 Instruments

1.3.5 Instruments
Requirement code Requirement # and requirement
1.3.500 The system bilaterally interfaces with instruments and related software based on the Unix and Windows platforms.
Response:
1.3.501 The system can download data directly from laboratory instruments.
Response:
1.3.502 The system can track and report on the usage of attached laboratory instruments.
Response:
1.3.503 The system can automatically (or manually allow an authorized user to) remove an instrument from potential use when it falls out of tolerance limit or requires scheduled calibration.
Response:
1.3.504 The system maintains a reportable database of preventative maintenance, calibration, and repair records for attached laboratory instruments.
Response:
1.3.505 The system can schedule calibration, verification, and maintenance tasks on attached instruments and make that schedule available for viewing.
Response:
1.3.506 The system allows users to create and edit instrument maintenance profiles.
Response:

1.3.6 External system interfaces

1.3.6 External system interfaces
Requirement code Requirement # and requirement
1.3.600. The system supports a library of common electronic data deliverable (EDD) formats.
Response:
1.3.601 The system can transfer data to and from other record management systems.
Response:
1.3.602 The system integrates with Microsoft Exchange services.
Response:
1.3.603 The system can import data from and export data to Microsoft Word, Excel, Access, and/or Powerpoint.
Response:
1.3.604 The system can interface with non-Microsoft programs.
Response:
1.3.605 The system can interface with enterprise resource planning (ERP) systems.
Response:
1.3.606 The system can interface with internal and external laboratory systems like laboratory information management systems (LIMS) and electronic laboratory notebooks (ELNs).
Response:
1.3.607 The system can leverage the application programming interface (API) of other systems to establish integration between systems.
Response:
1.3.608 The system provides a real-time interface for viewing live and stored data transactions and errors generated by interfaced instruments and systems.
Response:
1.3.609 The system supports dockable mobile devices and handles information exchange between them and the system.
Response:
1.3.610 The system supports the use of optical character recognition (OCR) software.
Response:

1.3.7 Reporting

1.3.7 Reporting
Requirement code Requirement # and requirement
1.3.700 The system includes a versatile report writer and forms generator that can generate reports from any data in the system.
Response:
1.3.701 The system can interface with a third-party reporting application.
Response:
1.3.702 The system allows the development of custom templates for different types of reports.
Response:
1.3.703 The system maintains template versions and renditions, allowing management and tracking of the template over time.
Response:
1.3.704 The system uses Microsoft Office tools for formatting reports.
Response:
1.3.705 The system provides multiple ways to visualize data in reports, including graphs, trend bars, pie charts, spectrum, etc. for the purpose of presenting information and identifying trends.
Response:
1.3.706 The system makes graphic and tabular data vector-scalable in reports.
Response:
1.3.707 The system allows for internal hyperlinking to source data in reports.
Response:
1.3.708 The system allows users to manually adjust inaccurate data parsing routines for reports.
Response:
1.3.709 The system can indicate whether a report is preliminary, amended, corrected, or final while retaining revision history.
Response:
1.3.710 The system can automatically generate laboratory reports of findings and other written documents.
Response:
1.3.711 The system provides an ad-hoc web reporting interface to report on user-selected criteria.
Response:
1.3.712 The system can automatically generate and post periodic static summary reports on an internal web server.
Response:
1.3.713 The system can transmit reports in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT.
Response:
1.3.714 The system supports PDF/A, an ISO-standardized version of the Portable Document Format (PDF).
Response:
1.3.715 The system includes a rules engine to determine the recipients of reports and other documents based on definable parameters.
Response:
1.3.716 The system provides printer-friendly audit trails for cleaner reporting of audit data.
Response:
1.3.717 The system provides an interface for external clients to search, generate, and view processed data reports based on metadata tags.
Response:
1.3.718 The system provides document workflow management tools for streamlining their creation, review, modification, and approval.
Response:
Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel3&oldid=16252"