This document provides an overview of the REACTOR application which consists of a web component integrated with SharePoint, a database component, and a handheld component. The web component gives users a graphical interface to access all functions. The database is the central data repository and enables reporting and synchronization between SharePoint and handhelds. The handheld component allows users to enter animal health data using a simple form on a handheld device without an internet connection. The document then describes the SharePoint user interface including viewing and editing cases, responses, and discussions as well as reporting functionality.

1. REACTOR Overview
This document provides an overview of the user interface and basic functions for the REACTOR application.
REACTOR consists of Web, database and handheld components:
• The Web component, which can be integrated with SharePoint 2007 or 2010, gives users a flexible and powerful
graphical interface to access all of REACTOR’s functions.
• The database component is the central repository for data and enables REACTOR to perform reporting.
Additionally, it synchronizes data between SharePoint and the handheld. The database component works
behind-the-scene and cannot be interacted with directly.
• The handheld component, based on Pendragon Forms, allows users to enter animal health data into a handheld
device via a simple form while working off-site. With Pendragon Forms, the handheld device does not need to
be constantly connected.
This document describes the SharePoint user interface.
Case grid
1. Paging controls
2. Case ID. Click to open the case edit window for that case.
3. Quick view box. Type a case ID to instantaneously open the Case Edit Window for the case.

2. 4. Clinical outcome. For pending cases, color code indicates when the case was last modified: Green=since
yesterday, Yellow=between 1 and 3 days, Red=more than 3 days ago.
5. Field header. Click to sort by field in descending or ascending order.
6. Response status: None, Created or Sent
7. Toolbar
8. Filter, in this case by Open cases only. Most fields are filterable.
9. Quick links to discussion lists for case.
Case edit window
1. Links to discussion lists for case
2. Textbox to edit case data
3. Add a custom lab contact for the case
4. Quick view of subjective observations without having to browse to discussion list
5. Select a response template
6. Click to merge the template with case data. Use this option to edit the response before sending.
7. Select an Exchange distribution list. Each investigator can have multiple distribution lists.
8. Recipients in the distribution list, which are retrieved from Exchange. Check or uncheck recipients as desired.
9. Click to generate and send the response at the same time. Use this option if the response doesn’t need to be
edited before being sent.

3. 1. Message box indicating success or failure
2. Response status. Here the status is changed to Created after the response is generated.
3. Click to open the response in Word for editing
4. Click to mark the case as Sent without using REACTOR. Use this option when sending the response using an
external email client, such as Outlook.
5. Click to send the response using REACTOR.

4. 1. Response status. Here the status is changed to Sent after the response is sent.
2. Click to open the response in Word for viewing.
3. Response history showing distribution list and recipients.
Creating a new case

5. Re-opening closed cases
Discussion list window

6. The discussion list is synchronized with the database, so that all discussions are viewable from the handheld device.
1. Click to return to Case Edit Window
2. View of conditions for quick reference
3. Text extracted from the response (via a bookmarked section in the Word document) is pasted here
Reporting
REACTOR currently implements 2 SQL Server Reporting Services reports. Similar as well as more advanced reports are
planned for a future phase.
The Case Report aggregates data and discussions belonging to the case

7. The summary report provides some overall statistics.