QStatim

The following questions are frequently asked.   If you have a question that is not listed, please let us know.

Questions
1.  How many facilities does the application support?
2.  Is the application browser-based?  Can it be accessed via our intranet?
3.  Does the application allow you to notify specific employees when an incident is entered?
4.  Does the application allow multiple users to enter follow-up comments?
5.  Can users who are late entering their follow-up comments be identified and sent a reminder notification?
6.  Can an administrator make changes to incident reports that are already submitted?
7.  Does the application capture Contributing Factors? If so, who enters them?
8.  Can I create reports and graphs?
9.  Is a logon required to enter an incident?
10.  Can documents, spreadsheets, pictures, etc.  be uploaded and saved with the incident?
11.  Does the application "time out" if the user steps away from the computer while entering an incident?
12.  Does the application track sentinel events?
13.  What hardware is required?
14.  How long does it take to install and implement the application?
15.  Describe the application architecture.
  
 
Answers
1.  How many facilities does the application support?
The application will support an endless number of facilities. 
 
2.  Is the application browser-based?  Can it be accessed via our intranet?
Yes.  The application is completely browser-based and does not require any software to be loaded on the desktop.   This allows for rapid deployment and requires less support. 
 
3. Does the application allow you to notify specific employees when an incident is entered?
Yes.  Any user can be setup to receive email and/or pager notification when a new incident is entered. 
 
4.  Does the application allow multiple users to enter follow-up comments?
Yes.  Multiple users are able to review and enter follow-up comments on the incident report.  However, only those users who have been identified on a "need to know" basis will be able to review and enter follow-up.
 
5.  Can users who are late entering their follow-up comments be identified and sent a reminder notification?
Yes.  The application can display all users who have not completed their follow-up comments.   Any of these users can be selected and sent an email notification.
 
6.  Can an administrator make changes to incident reports that are already submitted?
Yes.  The data captured on the incident report when it was originally entered can be changed at any time by the administrator or user with appropriate permissions.
 
7.  Does the application capture Contributing Factors?  If so, who enters them?
Yes.  When the incident is initially entered, the person entering the event can specify their selections for the factors that contributed to the incident.   However, these factors can be changed afterwards by the appropriate administrator or user with the appropriate permissions.
 
8.  Can I create reports and graphs?
Yes.  Reports can be created that will output the data to various formats including PDF, Excel, Word, and HTML.   Graphs can also be created that will allow the incident data to be analyzed for effectively.   Each graph provides "drill-down" functionality that will allow more detailed data to be shown.   Graphs can be produced in pareto, bar, line, and pie formats.   OLAP Data "cubes" can also be created and distributed that allow flexible ad-hoc analysis.
 
9.  Is a logon required to enter an incident?
Yes and No, depending upon the user setting.  The design of the application allows the logon to be required or not required at any time.   A flag that within the application can be updated at any time to require the logon or not require the logon.
 
10.  Can documents, spreadsheets, pictures, etc.  be uploaded and saved with the incident?
Yes.  Any electronic file that is stored on your PC or your network can be uploaded to the server and saved with the incident.   Those with the permission to do so can view the file that has been uploaded. 
 
11.  Does the application "time out" if the user steps away from the computer while entering an incident?
Yes.  The application provides a user-defined setting that determines the number of inactive minutes that will trigger the application to time out.
 
12.  Does the application track sentinel events? 
Yes.  The administrator, or other user with appropriate permissions, has the ability to flag an incident as a "sentinel event". 
 

13.  What hardware is required?

Web Server
• Pentium or Xeon Processor
CD/DVD-ROM
10/100/1000 Ethernet Card
2 SCSI Hard Drives - 100 GB capacity
1 GB RAM or higher
Microsoft IIS 6.0

MSXML
• Microsoft Windows 2000 Server SP4 or 2003 SP2
• Microsoft Internet Information Server
Adequate backup capability 

Database Server
Pentium or Xeon Processor
CD/DVD-ROM
10/100/1000 Ethernet Card
2 SCSI Hard Drives - 100 GB capacity

1 GB RAM or higher
• Microsoft Windows 2000 Server SP4 or 2003 SP2
• Microsoft SQL Server 2000 or 2003 (smaller databases can use SQL Express)
Adequate backup capability

Workstation/Client
• Pentium III or higher
512 MB RAM or higher
• Microsoft Windows 98, 2000, XP Professional, Windows Vista Business
• Microsoft Internet Explorer 6.0 or higher

 
14.  How long does it take to install and implement the application?
The time required to install and implement the application depends on several factors, such as  1) How many facilities will be using the application  2) How much training you would like for us to perform  3) Is there existing data that needs to be converted.   On average, the time required is approximately four to six weeks.
 
15.  Describe the application architecture.
The application is built using a combination of Active Server Pages (ASP), Microsoft® XML Parser (MSXML), Visual Basic® 6.0, COM+, ActiveX® Data Objects (ADO), and SQL Server™ 2000.  The HTML presentation layer is implemented in Active Server Pages. The business layers are implemented as COM+ components written in Visual Basic® 6.0 to access data in a disconnected manner through ADO.  The database layer is implemented using Microsoft® SQL Server. The SQL Server™ 2000 database uses stored procedures for best performance and maintainability.

  


HOMEOVERVIEWBENEFITSDEMOFAQSUPPORTNEWSCONTACT

COPYRIGHT © 1999-2008 - Q Solutions, Inc. All rights reserved

Q Solutions, Inc.
8363 Wolf Lake Drive
Memphis, Tennessee 38133
1 (866) QSTATIM (778-2846)

You are visiter #101311