ÿþ<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><!-- InstanceBegin template="/Templates/Support.dwt.php" codeOutsideHTMLIsLocked="false" --> <head> <!-- InstanceBeginEditable name="doctitle" --> <title>Priority Dispatch - Software Support</title> <!-- InstanceEndEditable --> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <link href="support.css" rel="stylesheet" type="text/css"> <!-- InstanceBeginEditable name="head" --><!-- InstanceEndEditable --> <title>Priority Dispatch - Software Support</title> <style type="text/css" title="dropmenu.css"> @import "dropmenu.css"; </style> <script src="dropmenu.js" type="text/javascript"></script> </head> <body> <table width="90%" border="0" cellpadding="0" cellspacing="0"> <tr> <td width="122"><a href="http://www.prioritydispatch.net"><img name="navigation" src="images/hdr_pdclogo.jpg" width="122" height="60" border="0" align="left"></a></td> <td align="left" valign="top"><span style="color:white;font-size:14pt;font-weight:bold;">Software Support</span> <br /><br /><a href="http://www.prioritydispatch.net/support/" class="dropmenu">Home</a> | <a href="" class="dropmenu" onClick="return clickreturnvalue()" onMouseover="dropdownmenu(this, event, menu1, '150px')" onMouseout="delayhidemenu()">Knowledge Base</a> | <a href="" class="dropmenu" onClick="return clickreturnvalue()" onMouseover="dropdownmenu(this, event, menu2, '150px')" onMouseout="delayhidemenu()">Updates</a> | <a href="" class="dropmenu" onClick="return clickreturnvalue()" onMouseover="dropdownmenu(this, event, menu3, '150px')" onMouseout="delayhidemenu()">Documentation</a> | <a href="" class="dropmenu" onClick="return clickreturnvalue()" onMouseover="dropdownmenu(this, event, menu4, '150px')" onMouseout="delayhidemenu()">Interaction</a> | <a href="" class="dropmenu" onClick="return clickreturnvalue()" onMouseover="dropdownmenu(this, event, menu5, '150px')" onMouseout="delayhidemenu()">CAD</a> </td> </tr> </table> <table width="100%" border="0" cellspacing="0" cellpadding="5"> <tr> <td><!-- InstanceBeginEditable name="mainbody" --> <table width="90%" border="1" cellpadding="3" cellspacing="1" bordercolor="#333333" bgcolor="#FFFFFF"> <tr> <td bordercolor="#FFFFFF" bgcolor="#FFFFFF"><p class="header_proqa"> <a href="index.php">Home</a> &gt; <a href="cad_index.php">CAD</a> &gt; <strong>ProQA Certification Requirements </strong></p> <p>Below are the details of the information and processes in an interface that is required for each of the four levels of integration between ProQA and CAD, Telco or other dispatching software.</p> <p>For full details on all three levels of integration please download/view the .PDF file below:</p> <table > <tr> <td><img src="images/icon_pdf.gif" width="20" height="20"></td> <td><a href="pdf/ParamountCertificationRequirements9Aug2011.pdf">ProQA Certification Requirements </a></td> </tr> </table> <p> <h3>Tiers of Integration:</h3> <h4>Operative:</h4> <p>This level of integration supports all basic functions of the ProQA interface including the passing of ANI/ALI (CLI) information with minimal degradation in performance. This level of integration does not support new XML capabilities with ProQA Paramount. This level of integration requires the completion of all the items marked by an O.</p> <h4>Bronze:</h4> <p>This level of integration indicates that all of the functionality of an Operative Integration (see above) has been completed and additional enhancements that assist in the effective dispatch of response units. This level of integration requires the completion of all the items marked by an O and B.</p> <h4>Gold:</h4> <p>This level of integration indicates that all of the functionality of an Operative and Bronze integration (see above) has been completed as well as additional enhancements to assist in the successful implementation of a CAD/Telco system with ProQA. These additional features can be user/agency configurable, in fact PDC suggests these be configurable items to allow for comm center preferences and control, but they must be available. This level of integration requires the completion of all the items marked by an O, B and G.</p> <h4>Platinum:</h4> <p>This level of integration indicates that all of the functionality of Operative, Bronze and Gold (see above) has been completed as well as the as additional enhancements to assist in the successful implementation of a CAD/Telco system with ProQA. These additional features can be user/agency configurable, in fact PDC suggests these be configurable items to allow for comm center preferences and control, but they must be available. This level of integration requires the completion of all the items marked by an O, B, G and P.</p> </p> <p style="color:red"><em>Gold and Platinum are the only levels of integration that Priority Dispatch Corporation will support.</em></p> <p style="color:red"><em>Platinum is the only level of integration that Priority Dispatch Corporation will recommend, endorse and partner with.</em></p> <p> <h3>Functions of a Certified Interface:</h3> <p> <h4>Accessibility From CAD</h4> <ol> <li>CAD should perform the following tasks upon creation of each new case: gather information from ANI/ALI, verify caller location and callback number, record call-type (FIRE, PD, Medical Emergency, Non Emergent transport, etc.)</li> <li>CAD should have a defined function key or button that the calltaker will use to launch ProQA or an automatic shift to ProQA based on a call-type designator.</li> <li>Once the function key or button is pressed, focus needs to be given to ProQA.</li> </ol> </p> <p> <h4>ProQA Start-up and Operation</h4> <ol> <li>ProQA must open with fields Location and Callback preloaded</li> <li>When available, ProQA must open with the CAD ID of the calltaker and CAD incident number having been passed from CAD</li> <li>ProQA must be visually accessible  The window must be large enough to view all print sizes or operates at full screen height (ProQA cannot be maximized wider than it opens as)</li> <li>Workstation must operate with minimal speed degradation. ProQA should load in under 3 seconds</li> <li>Minimal hesitation between fields and screens. Calltaker should not be forced to wait for the computer to catch up or buffer keystrokes that may be in error.</li> </ol> </p> <p> <h4>Passage of Data</h4> <ol> <li><strong>Abort Function:</strong> Calltaker may choose to abort ProQA  CAD should regain focus with abort message/text or abort code.</li> <li><strong>Initial Dispatch:</strong> Calltaker selection of Send within ProQA <br />a. Retrieval of Dispatch Level by CAD <br />b. Retrieval of Suffix code by CAD <br />c. Reconcile Dispatch Determinant and Suffix to locally defined response code with alert or recommendation to dispatcher <br />d. Retrieval of Response Text by CAD <br />e. Retrieval of Key Questions Answer text by CAD <br />&nbsp;&nbsp;&nbsp;1. When KQ s are in bullet format, in the CAD screen, soft the Key Question Answer text with pertinent answers at the top <br />f. Retrieval of Suspect Descriptor info by CAD (Police and Fire) <br />&nbsp;&nbsp;&nbsp;1. CAD should have the ability to gather multiple Person entries and bold the type of each Person entry (Suspect, Victim, Witness, etc.) <br />&nbsp;&nbsp;&nbsp;2. Attach any updates or edits to appropriate Suspect Descriptor info and visually alert dispatcher that data has been updated. <br />g. Retrieval of Vehicle and Boat Descriptor info by CAD (Police and Fire) <br />&nbsp;&nbsp;&nbsp;1. CAD should have the ability to gather multiple Vehicle/Boat entries and bold the type of each entry (Suspect, Victim, Witness, etc.) <br />&nbsp;&nbsp;&nbsp;2. Attach any updates or edits to appropriate Vehicle/Boat Descriptor info and visually alert dispatcher that the data has been updated. <br />&nbsp;&nbsp;&nbsp;3. Where the CAD has functionality or an interface with the ability to do vehicle lookup, parse the vehicle descriptor info and automatically perform that lookup function (NCIC, NLETS, etc.) <br />&nbsp;&nbsp;&nbsp;a. Notification of any  hit information should be passed by CAD to ProQA </li> <li><strong>Reconfigure:</strong> change in case status  ProQA will update CAD with a new dispatch code. If the new code is an upgrade or change in response, an alert must be displayed in CAD for the dispatcher.</li> <li>ProQA Override Option: ProQA generates a default code when a calltaker overrides a particular dispatch to a higher level. CAD must recognize this code or provide a table to match.</li> <li>Dispatcher must be alerted to an Urgent Message. </li> </ol> </p> <p> <h4>Program Focus - CAD vs. ProQA</h4> <ol> <li>Vertical Dispatch  Return to CAD for u nit response assignment. ProQA case in pending, or non-focused window. Upon completion of unit assignment, return to ProQA (unpend case ore return focus to ProQA) for remaining Key Questions and PDIs or PAIs.</li> <li>Horizontal Dispatch  Remain focused in ProQA, send Dispatch Code to CAD and notify dispatcher of event.</li> <li>Calltaker should be able to easily toggle between programs during the calltaking process.</li> <li>When a calltaker requests a new case in ProQA from CAD, if ProQA still has a case open, CAD needs to pass focus to ProQA so the calltaker can finish the case then return to CAD to continue with the new case creation.</li> </ol> </p> <p> <h4>Supported Functionality</h4> <ol> <li>Any user from any position must be able to re-open a previously completed/closed ProQA case. Allow for callbacks and additional input by allowing the user to open the incident in CAD, and then have a function that will re-open the corresponding case in ProQA.</li> <li>Support the Pend (hold) and Unpend (unhold/re-open) functions of ProQA. Once the user Pends a case in ProQA, allow the user to Unpend from CAD.</li> <li>Support the Summary function of ProQA. Have a function key or button in CAD that will call for the Summary of a particular case in ProQA.</li> <li>Allow the CAD system to be configured (agency defined) to allow for the gather of Case Entry information on the display of Key Questions. </li> <li>Allow the CAD system to be configured (agency defined) to allow for the gathering of final Key Questions gathered after dispatch.</li> </ol> </p> <p> <h4>Completion of Case</h4> <ol> <li>ProQA completion by calltaker, return to CAD for next case and place ProQA in wait state.</li> </ol> </p> <p> <h4>Configuration and Options</h4> <ol> <li>1. Provide a  toggle within CAD to activate the KQ display in paragraph or bullet format within the incident notes</li> <li>2. Whatever information gets sent to the field responders (MDTs, Alpha page, mobile laptops, etc.)_ needs to have a configurable component to allow the information to be trimmed. There should be a method (utility, screen, config file - .ini, etc.) by which the following items can be chosen/activated: <br />a. Send only the Key Question Answer text with pertinent answers <br />b. Send only the Key Question Short Answer text with pertinent answers <br />c. Send all the Key Question Answer text except those without pertinent answers <br />d. Send all the Key Question Short Answer text except those without pertinent answers <br />e. Send the Suspect Descriptor info <br />f. Send the Vehicle Descriptor info </li> <li>Gather, parse, and display field labels and data entered from the Descriptor Information and Essential Information tools in Medical, Fire, and Police). Where appropriate, the type (i.e. Suspect, Victim, Witness, and Contact or Diagnostic Tool Used) must be bolded.</li> <li>Aspirin given notification must be displayed when received.</li> <li>Gather and display field labels and data entered from bomb info.</li> </ol> </p> <p>&copy;2011</p> </p> </td> </tr> </table> <!-- InstanceEndEditable --> <table width="90%" border="0" cellspacing="0" cellpadding="0"> <tr> <td><hr color="#333399" align="left" width="100%" size="2"> <p align="center" class="whiteout"><font size="1">&copy;2005 Priority Dispatch Corporation<br> Salt Lake City, Utah, USA<br> All Rights Reserved <br> - Evolved from Medical Priority Consultants -<br> For technical problems contact the <a href="mailto:webmaster@prioritydispatch.net" class="grey_webmaster">webmaster</a></font></p></td> </tr> </table> </td> </tr> </table> </body> <!-- InstanceEnd --></html>