Solution Blueprint – Solution Standards

Reporting Dashboards – HIM Operations I Package

V3.0

May 16, 2018

 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

Table of Contents
1 Solution Overview ......................................................................................................................4
1.1 Solution Summary ......................................................................................................................... 4
1.2 Assumptions .................................................................................................................................. 4
2 Solution Design ..........................................................................................................................5
2.1 Capture.......................................................................................................................................... 5
2.2 Access ............................................................................................................................................ 5
3 Solution Questions .....................................................................................................................6
3.1 Discovery Questions...................................................................................................................... 6
3.2 Solution Deviations ....................................................................................................................... 7
3.2.1 Minor Deviations................................................................................................................... 7
3.2.2 Major Deviations ................................................................................................................... 7
4 Implementation Instructions .......................................................................................................8
4.1 Prerequisites ................................................................................................................................. 8
4.1.1 Modules ................................................................................................................................ 8
4.1.2 Software Versions ................................................................................................................. 8
4.1.3 Software ................................................................................................................................ 8
4.2 Installation & Configuration .......................................................................................................... 8
4.2.1 Required: Import Dashboards ............................................................................................... 8
4.2.2 Optional: Install Dashboard Web Viewer ........................................................................... 10
4.2.2.1 Enable the Creation of Links ........................................................................................... 12
4.2.2.2 Create the Link ................................................................................................................ 14
4.2.2.3 Scripting of Web Links ..................................................................................................... 15
4.2.3 Optional: Automating Reporting Dashboards to Send to Users ......................................... 16
4.3 Troubleshooting Implementation ............................................................................................... 17
4.3.1 Import Error: Exception has been thrown by the target of an invocation ......................... 17
5 Usage ....................................................................................................................................... 17
5.1 Navigating the Dashboard .......................................................................................................... 18
5.2 Productivity by User Group ......................................................................................................... 19
5.3 Productivity by Current User ...................................................................................................... 20

2 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
5.4 Document Type Summary........................................................................................................... 21
5.5 Batch Snapshot ........................................................................................................................... 22
6 Technical Design ....................................................................................................................... 24
6.1 Data Providers and Dashboards.................................................................................................. 24
6.1.1 Document Query Provider .................................................................................................. 24
6.1.2 Custom SQL Data Providers ................................................................................................ 25
6.1.3 Parameters .......................................................................................................................... 34

3 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

1 Solution Overview
OnBase Reporting Dashboard solutions allow the leadership of paper scanning
departments to monitor their team’s performance through real-time graphical
representations of team activity. This reporting is available through pre-packaged
reports designed to monitor indexing, scanning, quality analysis and more functions that
scanning teams use as performance metrics on a daily basis.

The HIM Operations I Package is designed to provide up to the minute data allowing
management the opportunity to track batch scanning and processing productivity in
completing their team’s daily workload. This reporting allows for the identification of
success against daily metrics and identify opportunities for improvement. Additionally,
leadership can use this data to accurately project team staffing in real-time, thus making
decisions to assure all work is completed successfully and on time.

1.1 Solution Summary

For a high level overview of this solution reference Dashboard Reporting HIM
Operations I Package - Solution Requirements

1.2 Assumptions
The remainder of this document assumes the following to be true prior to beginning
implementation of this solution.

1. Customer is either using:

a. OnBase 15.0.0.57 or higher with Unity Client batch scanning
b. OnBase 16.0.1.66 or higher with Thick Client batch scanning

2. Customer is licensed for Unity (for viewing Dashboards) and Reporting Dashboards.

3. Only one copy of each Dashboard will be installed for each environment by the
Hyland resource. Copies of the Dashboards can be made by customer System
Admins.

4 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

2 Solution Design
2.1 Capture
Documents are scanned through Unity or thick client Batch Scanning scan queues. A log date
and time is recorded in the database when scanning for the batch is initiated. A log date and
time is also recorded when scanning for the batch is complete. Similar start and stop log dates
and times are recorded for indexing and QA. Reporting Dashboards and the subsequent
Reporting Package use these start and stop times to determine productivity measurements.

2.2 Access
Dashboards are accessed and viewed via the Unity Client. Users must be granted the
appropriate privileges to access the Reporting Dashboards module and the HIM Operations I
Package Dashboards. Dashboards can be configured to report on a specific user group or
multiple user groups.

There are 8 Dashboards in the HIM Operations I Package:

– Scanning Productivity by User Group
– Indexing Productivity by User Group
– QA Productivity by User Group
– Document Type Summary
– My Scanning Productivity
– My Indexing Productivity
– My QA Productivity
– Batch Snapshot

5 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

3 Solution Questions
The following set of questions will help the project team to identify appropriate configuration
changes that fall within the scope of the HIM Operations I Package.

3.1 Discovery Questions

1) Q: Is the customer using Unity Batch Scanning or Thick Client Batch Scanning?
A. The client being used will determine the minimum version and build required.

2) Q: What version of OnBase is the customer on?

A. The minimum build is 15.0.0.57 for this solution with Unity Batch Scanning. This is the
first build with the appropriate database logging that makes these Dashboards possible.
If on a lower build and using the Unity Client for batch scanning, an upgrade is required.
B. The minimum build is 16.0.1.66 for this solution with Thick Client Batch Scanning. This is
the first build with the appropriate database logging that makes these Dashboards
possible. If on a lower build and using the Thick Client for batch scanning, an upgrade is
required.

The build version will also determine what export files will need to be used due to a change
in the software after 16 service pack 1.

3) Q: Are there multiple HIM departments or scanning locations that are each overseeing
their own scanning operations?
A. If yes, then investigate with the customer how they want their Dashboards to be
configured for user groups.

If it is acceptable to show the productivity across the enterprise, then the Dashboards
can be configured to report on all the scanning/indexing/QA user groups in the
organization.

However, it is more likely that each HIM department/scanning location will want their
own Dashboards that only show the productivity for their users. If this is the case, then
the TC will need to instruct and train the customer System Admin how to copy a
Dashboard from the Package. Refer to the Implementation Instructions on how to copy
for additional users.

Assigning of user groups to the copied Dashboard is best done by the customer System
Administrator as he or she will be most familiar with the existing user groups and their
alignment to the various departments. It also provides a training point for the system
admins to become familiar with the Dashboards and minor changes.

6 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
4) Q: Does the customer want to receive regular emails with a link to a Dashboard? For
example, every Friday, send an email to the HIM manager for that week’s scanning
productivity and results.
A. If yes, refer to the Implementation Instruction settings for how to set this up using
Workflow timers and a URL.

3.2 Solution Deviations

3.2.1 Minor Deviations
These are acceptable deviations for the solutions that can be done by the TC or System Admin
and still adhere to the defined solution.
 Adding, removing, or modifying the user groups as a run parameter for the Data Providers
for the Dashboards.
 Modifying the default parameters.
 User permissions, sharing of Dashboards to users, or marking the Dashboards as public.
 Color changes, renaming items or titles

3.2.2 Major Deviations

These are major changes or deviations from the standard solution. These are generally not
supported and fall outside of the defined solution. The Solution Standards team should be
consulted before performing any of these actions.
 Customization of any SQL or the built-in Data Providers that power the Dashboards.
 Building any additional Dashboards or Data Providers outside of those delivered in the HIM
Operations I Package.
 Major UI changes to the Dashboards such as adding additional reporting items or modifying
the Data Provider items for a particular Dashboard Item.

7 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

4 Implementation Instructions
4.1 Prerequisites
4.1.1 Modules
License Required Minimum Suggested
Unity Client Yes 1 Number of users
viewing Dashboards
Reporting Yes 1 1 (Enterprise license)
Dashboards

4.1.2 Software Versions

This solution can be used in the following versions. It is expected that full regression testing will
be performed in all customer implementations.
Software Configuration Minimum Build
OnBase Unity Batch Scanning OnBase 15.0.0.57
OnBase Thick Client Batch Scanning OnBase 16.0.1.66

4.1.3 Software
The following software must be installed prior to the installation of this solution.
Software Required Purpose
Application Server Yes Unity Connection
Unity Client Yes Access to
Dashboards
Dashboard Viewer No Viewing Dashboard
in a web browser.

4.2 Installation & Configuration

This segment addresses all implementation steps including prerequisites to give the
implementer a concise checklist of what they need to do.

4.2.1 Required: Import Dashboards

1. Download the appropriate vesion file of the Dashboard Reporting HIM Operations I
Package exports from GHS SharePoint.
a. If you are on build prior to OnBase Service Pack 1 (16.0.1+), then the files titled
with “(15.0.0.57)” should be used.
b. If you are on 16.0.1 or higher, then the file titled with “(16.0.1)” should be used.
The need to import Dashboards taken from an appropriate build is due to an
SCR and change in the import utility beginning in 16 service pack 1. There are no
other changes in functionality.
2. Launch Unity. Navigate to Reporting Dashboards button in the ribbon.

8 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
a. Dashboard Privileges must be assigned in the Configuration | Users | User
Groups & Rights | Dashboards. You will need Administrator Access to import
the HIM Operations I Package
3. Cancel out of the initial prompt (if applicable). Navigate to Administration in the lower
left of the window.
4. Select Import Configuration… Browse to the Dashboard Package file that you
downloaded earlier. Click Upload.
5. Once you see “Upload Successful”, click Next.
6. You will need to create or map all of the items that are being imported.

Dashboard Category
Name Import Action Notes
Batch Processing Snapshots Create
Document Type Reports Create
Indexing Productivity Create
QA Productivity Create
Scanning Productivity Create
Dashboards
Batch Snapshot Create
Document Type Summary Create
Indexing Productivity – [User Group] Create
My Indexing Productivity Create
My QA Productivity Create
My Scanning Productivity Create
QA Productivity – [User Group] Create
Scanning Productivity – [User Group] Create
Data Provider
Batch Snapshot – Current Status Create
Batch Snapshot – Scan to Commit Create
Document Count Summary Create
Indexing Productivity – [User Group] (SQL) Create
Indexing Productivity – Current User (SQL) Create
QA Productivity – [User Group] (SQL) Create
QA Productivity – Current User (SQL) Create
Scanning Productivity – [User Group] (SQL) Create
Scanning Productivity – Current User (SQL) Create
Keyword Types
Facility Name Map Facility Name (or similar)
HBI – Import Source Map HBI – Import Source, DC –
Import Source, or Import
Source
User Groups
MANAGER Map Version 17. Map to MANAGER
TEST Map Version 15 and 16 only. Map to
anything except the MANAGER
user group

9 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Dashboard Category
Users
MANAGER Map Version 17. Map to MANAGER
TEST Map Version 15 and 16. Map to
anything except the Manager
user

7. Click Verify Resolutions or Run Verification. If there are no errors, click Next or Review
Import.
8. Click Start Import. If the import was successful, click Commit. Finish.
a. Note that in some imports of 17, you will receive a “Partially Successful” for
mapping the MANAGER user group. This is acceptable and you can continue to
commit.
9. Configure User Groups and Rename
a. In Administration, you will need to select Configuration for each imported [User
Group] Data Provider and select a default user group(s). Once the user group is
set, Save the Data Provider. Rename the Data Provider by clicking Properties.
Replace “[User Group]” with the selected user group name for that Data
Provider.
b. Also rename the corresponding Dashboard that uses the Data Provider with the
correct user name.
10. Assign Privileges to Users or User Groups.
a. Discuss with the customer the user groups that should have access to these
Dashboards. Users will need access to both the Data Provider and the
Dashboard. This can be done either though the Assign Dashboards or Assign
Users button in the ribbon for each Data Provider and Dashboards in
Administration.

4.2.2 Optional: Install Dashboard Web Viewer

To view dashboards from a web browser using a hyperlink, a separate server needs to be
installed. This can be installed using the Dashboard Viewer installer found from the regular
build directory or in the software repository created from the Repository Creator utility. This
should be installed on the customer’s web server.

Use the Standard naming convention when creating this web server:
OnBaseWebDashboards[ENV]

A separate App Server should be created for this web server (OnBaseAppDashboards[ENV])

10 of 35
Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

11 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

Once the Dashboard Viewer is installed, you will need to update its web.config file to accept
Http Dashboard Parameters. Set <acceptHttpDashboardParams> value to “true”.

Dashboard web.config:

<Hyland.Web.DashboardViewer>
<username value="" />
<passowrd value="" />
<useTheme value="dark" />
<enableExportDashboard value="true" />
<enableExportDashboardItems value="true" />
<acceptHttpDashboardParams value="true" />
<enableAutoLogin value="false" />
<sessionTraceLevel value="0" />
</Hyland.Web.DashboardViewer>

4.2.2.1 Enable the Creation of Links

There are 2 types of links that can be created for a dashboard, a Unity Pop link or a web link. The
type of link that is generated depends on how the user's Unity Client is configured for sending
links. Weblinks can be viewed from any web browser. Unity Pop links require Unity to be
installed on the workstation that the link is launched from and launch directly to the Dashboard
in Unity.

12 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Dashboard Unity Pop Links
To create links that utilize the Unity Pop framework, the app setting "emailLinkAs" must be set
to upop in the Unity Client configuration file. Since Unity Pop links require a signature on the
link, the parameter values are encoded and the signature prevents any changing of the URL.
onbase://dashboard/db/?dashboardId=293&Sig=FzTncvK7XOjFfrSQ9LQJBxEYQbd1uhCRN
Qd0D3zBvyQ~&enc=AWlyWkm3CcDy%2...

The 2 configuration settings that need to be set are:

1. URI Protocol Handler must be set to true. NOTE: ServiceMode does not need to be enabled.
2. emailLinkAs must be set to upop.

<Hyland.Canvas.Client>
<ServiceMode enabled="false" allowExit="true" autoLaunch="false">
<Feature name="URI Protocol Handler" enabled="true"/>

<appSettings>
<!--Uncomment the next line to enable sending links from the
client.
Valid values include "disabled", "weblink", "upop" and "upop-
file"-->
<add key="emailLinkAs" value="upop"/>

Dashboard Web Links

To create links that are accessible from the web, the app setting "emailLinkAs" must be set to
weblink. Also, the "dashboardWebViewerUrl" will need to be corrected to point to your
dashboard web viewer. Dashboard web links also give users the ability to script weblinks.

The 3 configuration settings that need to be set are:

1. URI Protocol Handler must be set to true. NOTE: ServiceMode does not need to be enabled.
2. emailLinkAs must be set to weblink.
3. dashboardWebViewerUrl will need to be corrected to point to your dashboard web viewer
(Viewer.aspx page)

<appSettings>
<!--Uncomment the next line to enable sending links from the
client.
Valid values include "disabled", "weblink", "upop" and "upop-
file"-->
<add key="emailLinkAs" value="weblink"/>

<!-- When using web links for dashboards make sure that you update
the server and
the virtual directory in the line below. -->
13 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
<add key="dashboardWebViewerUrl" value=" http://[Web Server
Name]/OnBaseWebDashboardsTST/Viewer.aspx "/>

Privileges
In order to create the link, the user group must have the Create Integration Hyperlink in the
{Configuration | Users | User Groups / Rights | Privileges} menu.

4.2.2.2 Create the Link

To create a link to a dashboard, the dashboard must first be opened in the dashboard viewer.
Then select "Copy to Clipboard" -> "Copy Hyperlink" from the ribbon menu.

NOTE: In order to enable to Copy Hyperlink and Send To | Clipboard (as Shortcut) options, to
allow users to copy the URLs of dashboards to the clipboard so they can be pasted into
other applications, the Unity Client configuration file needs to be updated. The Create
Integration Hyperlink privilege is also required to use the Copy Hyperlink
option. See the previous section or the Reporting Dashboards MRG (page 309) for details.

If there are any input parameters on the dashboard, a dialog will be prompted to see if the user
wishes to change the parameters before creating the dashboard link.

NOTE: The input parameters and their values are part of the link that is generated, to have
different parameter values, a new link will need to be generated.

14 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

The following is an example link that can be generated:

Indexing Productivity - [User Group]

http://inst-
019435/OnBaseWebDashboardsTST/Viewer.aspx?dashboard=126&ds=Sandbox%20Beta&dp128
-DateRange-eq=1003%3a0%3a0

4.2.2.3 Scripting of Web Links

The dashboard web server can be configured so that it accepts URLs that do not contain
encrypted parameters. Thus, a customer can create scripts to generate these links or modify
existing links, without having to do it from the Reporting Dashboards layout in the Unity Client.
This is not necessary if creating the web link through the Unity Client. For visibility, the Unity
Client has an app setting, that allows the dashboard URLs to be unencrypted. This way,
administrators can see exactly what all the parameters on the URL are.

Unity Client Configuration:

<appSettings>
<add key="encryptDashboardUrls" value="false" />

15 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
The dashboard web viewer will need to be configured to accept the scripted URLs. By default
the dashboard web viewer only accepts URLs that are encrypted:

<!-- DashboardViewer Vars -->

<!-- acceptHttpDashboardParams - Set to true to allow setting the
dashboard parameters
from HTTP request query string (default false) -->
<Hyland.Web.DashboardViewer>
<acceptHttpDashboardParams value="true" />

There are 7 different parameters that the Dashboard Web Viewer respects. Please view the
Reporting Dashboards MRG or the Dev Wiki for a complete description of the parameters.

4.2.3 Optional: Automating Reporting Dashboards to Send to Users

Automatically emailing a URL for a Dashboard on a regular basis can be accomplished using a
combination of web links to Dashboards and a Workflow process with a timer. The following is a
general introduction on how to create the web links and setup the web server to be able to view
the Dashboards in a web browser. Configuring a workflow is also discussed. Details are in the
Dev Wiki and in the Reporting Dashboards MRG (starting on page 309).

There are several steps to configure this process:

1. Install the “Dashboard Viewer” on the Web Server. This is an installer. This is only
necessary if creating “weblinks” to view the Dashboard in a web browser. If using
“upop” to create a link that launches the Dashboard in Unity, then this step is not
needed.
2. Enable the creation of links from Unity.
a. Modify the obunity.exe.config file for the configuration of Unity to allow the
creation of hyperlinks from Dashboards. You will need to choose which type of
link to use (upop or weblinks)
b. Give your user the “Create Integration Hyperlink” privilege
3. Generate a link for the Dashboard with the appropriate parameters in the URL for date
ranges.
4. Create a Workflow lifecycle with a timer. Configure the time to send a notification to the
desired user/email address at the desired interval. The notification should contain the
generated link for the Dashboard.
5. Add the timer to Workflow Timer Service to send the notification.

16 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Create a Workflow Life Cycle to Send Notifications
Once a URL for a Dashboard has been created with the appropriate parameters, a Workflow
Lifecycle can be created to send an email notification with that link. The Distribution Server
needs to be installed and configured in order for OnBase to send emails.

Create the Workflow and configure a timer to send notifications at the desired interval. In the
notification that is sent, paste the hyperlink that was generated from Unity for the Dashboard.

There is currently no Standard workflow created for this solution. However, contact the
Standards team with any questions or difficulties creating the workflow.

4.3 Troubleshooting Implementation

4.3.1 Import Error: Exception has been thrown by the target of an invocation
Details: Unable to perform action (Create) on object: (table dashboardxuser)

Resolution: Map users to any other user except “MANAGER”

This is known error with OnBase 15 and 16 imports. The import utility is automatically mapping
already to the MANAGER user group. Any additional mappings to that user name creates a
conflict and duplication in the database tables during the import. Do not map the users that are
attempting to be brought to the MANAGER user name. Map them to any other user name that
is appropriate for the customer.

5 Usage
Complete details on the feature and functionality of Reporting Dashboards can be found in the
MRG. A Training Guide exist outside of this document that can be given to customers. This
section will explain general information on Dashboards in the HIM Operations I Package.

The following are brief summaries of each of Dashboard included in the HIM Operations I
Package.

Scanning Productivity by User Group

Provides visibility into the number of pages being scanned across a defined amount of
time for the Scanning User Group.
Indexing Productivity by User Group
Provides visibility into the number of pages being indexed across a defined amount of
time for the Indexing User Group.
Quality Assurance Productivity by User Group

17 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Provides visibility into the number of pages being QA’d across a defined amount of time
for the QA User Group.
Document Counts by Document Type
Provides visibility into the number of documents scanned into OnBase that are indexed
to a specific document type.
My Scanning Productivity
Provides visibility into the number of pages being scanned across a defined amount of
time for the individual scanning user.
My Indexing Productivity
Provides visibility into the number of pages being indexed across a defined amount of
time for the individual indexing user.
My Quality Assurance Productivity
Provides visibility into the number of pages being QA’d across a defined amount of time
for the individual QA user.
Batch Snapshot
Provides visibility into the current status of all batches for the entire environment or
specific scan queues. Also provides visibility on the average time to process a batch from
the time scanned until committed for the given time range.

5.1 Navigating the Dashboard

There are several areas for reports on each Dashboard. Each dashboard for productivity has a
similar look and feel with the same general reports appearing in the same locations on the
dashboard. For example, the bar chart showing the totals each user always appears at the top of
the dashboard. The Document Counts by Document Type and Batch Snapshot dashboards have
different layouts.

18 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

5.2 Productivity by User Group

Dashboard Item
Name Description
Total Scans/Indexes/QA Reviews Per User for Shows the number of pages and documents that each user
Defined Date Range has scanned/indexed/QA reviewed for the given date range
and user group in a bar chart. NOTE: This does not include
deleted or appended documents in its calculations. It does
however include deleted pages in it calculations.

Total Scans/Indexes/QA Review Shows the total number of pages and documents that have
been scanned/indexed/QA’d for the given date range and
user group.
Pages scanned/Indexed/QA by Scan Queue Shows a pie chart indicating the breakdown of pages
processed for each scan queue for the given date range and
user group.
Scanning/Indexing/QA Statistics Per Scan Queue Shows a grid with data for each scan queue on the total
pages, total documents, and average pages processed per
hour.
Average Pages Scanned/Indexed/QA’d Per Hour Shows a gauge indicating the average number of pages
scanned/indexed/QA’d per hour by each user.
For each batch that is processed, the rate to process that
batch is individually calculated. The average from all the
batches that were processed is then calculated per user and
reported in the gauge. I.e. Number of pages that were
indexed in batch divided by the time the user spent to index
those pages, then averaged across all batches the user
processed. This is a “rate” calculated individually for each
batch and does not include the length or total time that a
user is logged into the system in any of its calculations.

19 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

Average Seconds Per Page Shows a gauge indicating the average seconds to
Scanned/Indexed/QA’d scan/index/QA review a page for each user. Calculates the
time to processed a page divided by the number of pages for
each batch, then averages over all the batches per user.

5.3 Productivity by Current User

Dashboard Items
Name Description
Total Scans/Indexes/QA Reviews Shows the number of pages and documents that the current
user that is viewing the dashboard has scanned/indexed/QA
reviewed for the given date range. NOTE: This does not
include deleted or appended documents in its calculations.
It does however include deleted pages in it calculations.

Average Number of Pages Scanned/Indexed/QA’d Shows a gauge indicating the average number of pages
Per Hour scanned/indexed/QA’d per hour by the current user viewing
the dashboard.

For each batch that is processed, the rate to process that

batch is individually calculated. The average from all the
batches that were processed is then calculated per user and

20 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
reported in the gauge. I.e. Number of pages that were
indexed in batch divided by the time the user spent to index
those pages, then averaged across all batches the user
processed. This is a “rate” calculated individually for each
batch and does not include the length or total time that a
user is logged into the system in any of its calculations.
Average Seconds Per Page Scanned/Indexed/QA’d Shows a gauge indicating the average seconds to
scan/index/QA review a page for the current user viewing
the dashboard. Calculates the time to processed a page
divided by the number of pages for each batch, then
averages over all the batches for the user.
Timeline Shows a range filter indicating the pages
scanned/indexed/QA’d over a date and time range for the
current user viewing the dashboard.

5.4 Document Type Summary

Dashboard Items
Name Description
Timeline Shows a range filter indicating the count of documents that
entered the system over a date and time range for the given
document types entered as a parameter.
21 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Total Documents Shows a card indicating the total number of documents in the
system for the given document types entered as a parameter.

Document Type Counts Shows a pie chart indicating the number and percentage
breakdown of the documents into document types for the
given document types entered as a parameter.
Document Types by Import Source Shows a grid of the number of documents for each document
type for each indexed Import Source (or other keyword)
value.
Document Types Per Facility Shows a grid of the number of documents for each Facility (or
other keyword) that is indexed on the documents.

5.5 Batch Snapshot

Dashboard Items
Name Description
Scan Queue A list of all Scan Queues configured that can be selected as
parameters to filter the other items on the Dashboards.
These can be defaulted to specific scan queues if desired.
Average Time From Scan to Commit Per Batch Shows a gauge indicating the average number of hours to
process a document from scan to commit for all committed
batches from the Scan Queues selected in parameters.
Average Time in Status A grid of the statuses that currently have batches for the
selected Scan Queues. For example, if a Scan Queue has only
2 batches they are both in “Awaiting Index” then Awaiting
22 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
Index is the only status that will be shown when that Scan
Queue is selected. The average number of hours that those
batches have been in that status shown. This report does not
retroactively report on the average length of time that
batches are in any given status. This reports only on batches
that are currently in that status and the average length of
time that they have been in that status.
Current Scan Queue Batches Per Status A grid showing a count of batches that were scanned per
Scan Queue and their current status.
Batch Details A grid showing the details for each batch that are in the
selected Scan Queue parameters. Details include the batch
number, Scan Queue Name for the batch, the batch’s current
status, date/time the batch was scanned, date/time the
batch entered its current status, number of hours from the
time the batch was scanned until it entered its current status
(how long it took for the batch to get to current status,
number of hours since the batch was scanned (how old the
batch is), number of hours in current status (how long has
the batch been in this status), and the number of documents
that were originally scanned in the batch.

23 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

6 Technical Design
6.1 Data Providers and Dashboards
Data providers return data from a data source to be displayed in a dashboard. Different types of
data providers are used in the HIM Operations I Package depending on the build of OnBase.
There are also slight differences in some of the Dashboards between the versions.

Version 15
Dashboard Name Data Provider Name Data Provider Type
Scanning Productivity by User Group Scanning Productivity - [User Group] Custom SQL Query
Indexing Productivity by User Group Indexing Productivity - [User Group] Custom SQL Query
QA Productivity by User Group QA Productivity - [User Group] Custom SQL Query
Document Type Summary Document Counts by Doc Type Document Query
My Scanning Productivity Scanning Productivity – Current User Custom SQL Query
My Indexing Productivity Indexing Productivity – Current User Custom SQL Query
My QA Productivity QA Productivity – Current User Custom SQL Query
Batch Snapshot Batch Summary Custom SQL Query

Version 16+
Dashboard Name Data Provider Name Data Provider Type
Scanning Productivity by User Group Scanning Productivity - [User Group] Custom SQL Query
Indexing Productivity by User Group Indexing Productivity - [User Group] Custom SQL Query
QA Productivity by User Group QA Productivity - [User Group] Custom SQL Query
Document Type Summary Document Counts by Doc Type Document Query
My Scanning Productivity Scanning Productivity – Current User Custom SQL Query
My Indexing Productivity Indexing Productivity – Current User Custom SQL Query
My QA Productivity QA Productivity – Current User Custom SQL Query
Batch Snapshot Batch Snapshot – Current Status Custom SQL Query
Batch Snapshot Batch Snapshot – Scan to Commit Custom SQL Query

6.1.1 Document Query Provider

The Document Type Summary using the Document Counts by Doc Type data provider reports on
the number of documents for each document type in the system. This is an internal data
provider.

This only reports on documents that have been committed. Documents that are still in batch
processing in “Awaiting Index” or “Awaiting QA Review” are not included in these counts.

24 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
6.1.2 Custom SQL Data Providers
The version HIM Operations I Package utilizes Custom SQL Data Providers. Below is the custom
SQL for each of these Data Providers.

Note that the count or tallying of pages and documents indexing and QA differs in the current
version of OnBase for deletions and appending documents.
For Deletions:
 Users do not get credit for a deleted document since the extrainfo1 does not tally the
deleted document.
 Users get credit for a deleted page(s) since extrainfo2 does include the deleted pages in
its count.

For Appends:
 Users do not get credit for an appended document since extrainfo1 does not include the
appended document in its tally for the stop action.
 Users do not get credit for an appended page since extrainfo2 does not include
appended pages in its tally for the stop action.

Another way to conceptualize this is via counts of pages and documents.

For Documents (extrainfo1):
 Deleted document are not counted in extrainfo1. Thus, users do not get credit for a
deleted document.
 Appended documents are not counted in extrainfo1. Thus, users do not get credit for an
appended document.

For Pages (extrainfo2):

 Deleted pages are counted in extrainfo2. Thus, users get credit for a deleted page.
 Appended pages are not counted in extrainfo2. Thus, users do not get credit for an
appended page.

Scanning Productivity - [User Group]

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT,(DATEDIFF(SECOND,sl1.logdate,sl2.logdate)))/NULLIF(sl2.extrain
fo2,0),2) AS [SecondsPerPageScanned],

25 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageScanned],
--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between
start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesScannedPerHour],
ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsScanned],
ISNULL((SELECT sl2.extrainfo2),0) AS [PagesScanned]

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 260)
LEFT JOIN hsi.useraccount ua ON ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum
INNER JOIN
(SELECT DISTINCT uxg.usernum
FROM hsi.userxusergroup uxg
INNER JOIN hsi.usergroup ug ON uxg.usergroupnum = ug.usergroupnum
WHERE ug.usergroupnum IN (@{UserGroup})) ugs ON ua.usernum =
ugs.usernum

WHERE sl1.actionnum = 200 --begin scanning

AND sl2.actionnum = 260 --end scanning
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate BETWEEN @{LogRange} --Reporting Dashboards parameter

Key Calculations
Output Description
[DeltaSecondsPerBatch] For each batch that was scanned,
𝐸𝑛𝑑 𝑆𝑐𝑎𝑛𝑛𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠) − 𝑆𝑡𝑎𝑟𝑡 𝑆𝑐𝑎𝑛𝑛𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠)

[SecondsPerPageScanned] [DeltaSecondsPerBatch]
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesScanned]

[MinutesPerPageScanned] [DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒

×
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesScanned] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠

[PagesScannedPerHour] 𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesScanned] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 60 𝑚𝑖𝑛𝑢𝑡𝑒𝑠

× ×
[DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒 1 ℎ𝑜𝑢𝑟
[DocumentsScanned] For each batch the was scanned, the number of documents in that batch. NOTE: This
does not include deleted blank documents.
[PagesScanned] For each batch the was scanned, the number of pages in that batch. NOTE: This does not
include deleted blank pages.

26 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

Indexing Productivity - [User Group]

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT,(DATEDIFF(SECOND,sl1.logdate,sl2.logdate)))/NULLIF(sl2.extrain
fo2,0),2) AS [SecondsPerPageIndexed],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageIndexed],
--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between
start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesIndexedPerHour],
ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsIndexed],
ISNULL((SELECT sl2.extrainfo2),0) AS [PagesIndexed]

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 266)
LEFT JOIN hsi.useraccount ua ON ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum
INNER JOIN
(SELECT DISTINCT uxg.usernum
FROM hsi.userxusergroup uxg
INNER JOIN hsi.usergroup ug ON uxg.usergroupnum = ug.usergroupnum
WHERE ug.usergroupnum IN (@{UserGroup})) ugs ON ua.usernum =
ugs.usernum

WHERE sl1.actionnum = 202 --begin indexing

AND sl2.actionnum = 266 --end scanning
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate BETWEEN @{LogRange} --Reporting Dashboards parameter

Key Calculations
Output Description

27 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
[DeltaSecondsPerBatch] For each batch that was indexed,
𝐸𝑛𝑑 𝐼𝑛𝑑𝑒𝑥𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠) − 𝑆𝑡𝑎𝑟𝑡 𝐼𝑛𝑑𝑒𝑥𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠)

[SecondsPerPageIndexed] [DeltaSecondsPerBatch]
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesIndexed]

[MinutesPerPageIndexed] [DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒

×
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesIndexed] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠
[PagesIndexedPerHour] 𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesIndexed] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 60 𝑚𝑖𝑛𝑢𝑡𝑒𝑠
× ×
[DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒 1 ℎ𝑜𝑢𝑟
[DocumentsIndexed] For each batch the was indexed, the number of documents in that batch. NOTE: This
DOES NOT include documents deleted by the user. This DOES NOT include documents
appended by the user.
[PagesIndexed] For each batch the was indexed, the number of pages in that batch. NOTE: This DOES
include pages deleted by the user. This DOES NOT include pages appended by the user.

QA Productivity - [User Group]

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT,(DATEDIFF(SECOND,sl1.logdate,sl2.logdate)))/NULLIF(sl2.extrain
fo2,0),2) AS [SecondsPerPageQAReviewed],

ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,

sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageQAReviewed],

--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between

start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesQAReviewedPerHour],

ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsQAReviewed],

ISNULL((SELECT sl2.extrainfo2),0) AS [PagesQAReviewed],

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum

28 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 269)
LEFT JOIN hsi.useraccount ua ON ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum
INNER JOIN
(SELECT DISTINCT uxg.usernum
FROM hsi.userxusergroup uxg
INNER JOIN hsi.usergroup ug ON uxg.usergroupnum = ug.usergroupnum
WHERE ug.usergroupnum IN (@{UserGroup})) ugs ON ua.usernum =
ugs.usernum

WHERE sl1.actionnum = 218 --begin QA review

AND sl2.actionnum = 269 --end QA review
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate between @{LogRange} --Reporting Dashboards parameter

Key Calculations
Output Description
[DeltaSecondsPerBatch] For each batch that was QA Reviewed,
𝐸𝑛𝑑 𝐼𝑛𝑑𝑒𝑥𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠) − 𝑆𝑡𝑎𝑟𝑡 𝐼𝑛𝑑𝑒𝑥𝑖𝑛𝑔 𝑇𝑖𝑚𝑒 (𝑠𝑒𝑐𝑜𝑛𝑑𝑠)

[SecondsPerPageQAReviewed] [DeltaSecondsPerBatch]
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesQAReviewed]

[MinutesPerPageQAReviewed] [DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒

×
𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesQAReviewed] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠
[PagesQAReviewedPerHour] 𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑔𝑒𝑠 𝑖𝑛 𝑡ℎ𝑒 𝑏𝑎𝑡𝑐ℎ [PagesQAReviewed] 60 𝑠𝑒𝑐𝑜𝑛𝑑𝑠 60 𝑚𝑖𝑛𝑢𝑡𝑒𝑠
× ×
[DeltaSecondsPerBatch] 1 𝑚𝑖𝑛𝑢𝑡𝑒 1 ℎ𝑜𝑢𝑟
[DocumentsQAReviewed] For each batch the was QA Reviewed, the number of documents in that batch. NOTE:
This DOES NOT include documents deleted by the user. This DOES NOT include
documents appended by the user.
[PagesQAReviewed] For each batch the was QA Reviewed, the number of pages in that batch. NOTE: This
DOES include pages deleted by the user. This DOES NOT include pages appended by
the user.

Scanning Productivity – Current User

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/NULLIF(sl2.extrainfo2,0),2) AS [SecondsPerPageScanned],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageScanned],
29 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between
start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesScannedPerHour],
ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsScanned],
ISNULL((SELECT sl2.extrainfo2),0) AS [PagesScanned]

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 260)
LEFT JOIN hsi.useraccount ua ON ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum

WHERE sl1.actionnum = 200 --begin scanning

AND sl2.actionnum = 260 --end scanning
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate BETWEEN @{LogRange} --Reporting Dashboards parameter
AND ua.usernum = ##OB_CURRENTUSER_ID --report for the current user

Indexing Productivity – Current User

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/NULLIF(sl2.extrainfo2,0),2) AS [SecondsPerPageIndexed],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageIndexed],
--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between
start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesIndexedPerHour],
ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsIndexed],
ISNULL((SELECT sl2.extrainfo2),0) AS [PagesIndexed]

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

30 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 266)
LEFT JOIN hsi.useraccount ua ON ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum

WHERE sl1.actionnum = 202 --begin indexing

AND sl2.actionnum = 266 --end indexing
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate BETWEEN @{LogRange} --Reporting Dashboards parameter
AND ua.usernum = ##OB_CURRENTUSER_ID --report for the current user

QA Productivity – Current User

SELECT

sl1.usernum AS [Usernum],
ua.username AS [Username],
sl1.batchnum AS [Batchnum],
sl1.logdate AS [StartDate],
sl2.logdate AS [EndDate],
sq.queuename AS [QueueName],
DATEDIFF(SECOND, sl1.logdate, sl2.logdate) AS [DeltaSecondsPerBatch],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/NULLIF(sl2.extrainfo2,0),2) AS [SecondsPerPageQAReviewed],
ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND, sl1.logdate,
sl2.logdate)))/60/NULLIF(sl2.extrainfo2,0),2) AS [MinutesPerPageQAReviewed],
--DATEDIFF(SECOND, sl1.logdate, sl2.logdate) is the delta time between
start to stop for a batch
--divide by 60 to convert to minutes
--divide by NULLIF(sl2.extrainfo2, 0) to convert from documents to pages
ISNULL((SELECT sl2.extrainfo2),0)/NULLIF(ROUND(CONVERT(FLOAT, (DATEDIFF(SECOND,
sl1.logdate, sl2.logdate)))/60/60,3),0) AS [PagesQAReviewedPerHour],
ISNULL((SELECT sl2.extrainfo1),0) AS [DocumentsQAReviewed],
ISNULL((SELECT sl2.extrainfo2),0) AS [PagesQAReviewed]

FROM hsi.scanninglog sl1

LEFT JOIN hsi.scanninglog sl2 ON sl1.usernum = sl2.usernum AND sl1.batchnum =
sl2.batchnum AND sl1.logdate < sl2.logdate AND sl2.logdate = (SELECT MIN(sl3.logdate)

FROM hsi.scanninglog sl3

WHERE sl1.usernum = sl3.usernum
AND sl1.batchnum = sl3.batchnum
AND sl1.logdate < sl3.logdate
AND sl3.actionnum = 269)
LEFT JOIN hsi.useraccount ua on ua.usernum = sl1.usernum
LEFT JOIN hsi.scanqueue sq ON sl1.queuenum = sq.queuenum

WHERE sl1.actionnum = 218 --begin QA review

AND sl2.actionnum = 269 --end QA review
AND sl2.extrainfo2 > 0 --use entries with more than 0 page
AND sl1.logdate BETWEEN @{LogRange} --Reporting Dashboards parameter
31 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
AND ua.usernum = ##OB_CURRENTUSER_ID --report for the current user

Batch Snapshot – Current Status

SELECT aq.batchname AS [BatchName],
aq.batchnum AS [BatchNum],
aq.totaldocuments AS [BeginningDocumentsPerBatch],
aq.totalpages AS [BeginningPagePerBatch],
sq.queuename AS [QueueName],
aq.usernum as [UserNum],
aq.datestarted AS [DateScanned],
aq.dateended [DateEnteredCurrentStatus],
CASE
WHEN aq.status = 0 THEN 'Awaiting Indexing'
WHEN aq.status = 1 THEN 'Index In Progress'
WHEN aq.status = 2 THEN 'Awaiting Commit'
WHEN aq.status IN (3,4,5,6) THEN 'Incomplete Commit'
WHEN aq.status = 8 THEN 'Committed'
WHEN aq.status = 9 THEN 'Incomplete Purge'
WHEN aq.status = 14 THEN 'Awating OCR'
WHEN aq.status = 17 THEN 'Check Out Disconnected Scanning'
WHEN aq.status = 18 THEN 'Disconnected Scan Incomplete Upload'
WHEN aq.status = 19 THEN 'Incomplete Archive'
WHEN aq.status = 20 THEN 'Secondary Awaiting Index'
WHEN aq.status = 21 THEN 'Secondary Index in Progress'
WHEN aq.status = 22 THEN 'Failed Automatic OCR'
WHEN aq.status = 23 THEN 'Awating Doc Separation'
WHEN aq.status = 24 THEN 'Line Item Separation (Image Segment Archiver Queue)'
WHEN aq.status = 25 THEN 'ADF Error Queue'
WHEN aq.status = 26 THEN 'Awating Re-Index'
WHEN aq.status = 27 THEN 'Re-Index in Progress'
WHEN aq.status = 28 THEN 'Check Error Queue'
WHEN aq.status = 29 THEN 'ADF Decisioning Queue'
WHEN aq.status = 30 THEN 'Administrator Repair'
WHEN aq.status = 31 THEN 'Awating QA Image Quality Review'
WHEN aq.status = 32 THEN 'Awaiting QA Review'
WHEN aq.status = 33 THEN 'Awating QA Rescan'
WHEN aq.status = 34 THEN 'Awating Manager Resolution'
WHEN aq.status = 35 THEN 'Awating QA Re-Index'
WHEN aq.status = 36 THEN 'QA Re-Index in Progress'
WHEN aq.status = 37 THEN 'In Process'
WHEN aq.status = 38 THEN 'Awaiting PDF Conversion'
WHEN aq.status = 39 THEN 'Scheduled Processes'
WHEN aq.status = 40 THEN 'Error Correction Queue'
WHEN aq.status = 41 THEN 'Awaiting Transfer to Host (SAP Early Archiving)'
WHEN aq.status = 43 THEN 'Awaiting External Index'
WHEN aq.status = 44 THEN 'Awating Barcode Processing'
WHEN aq.status = 45 THEN 'ADF Decision Error Queue'
WHEN aq.status = 46 THEN 'Awaiting Image Process'
WHEN aq.status = 47 THEN 'Custom Process'
WHEN aq.status = 48 THEN 'Ad Hoc Re-scan'
WHEN aq.status = 49 THEN 'Branch Capture Balancing Queue'
WHEN aq.status = 50 THEN 'Branch Capture In Process Queue'
WHEN aq.status = 51 THEN 'Awaiting Zonal OCR'
32 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
WHEN aq.status = 52 THEN 'Awaiting Ad Hoc Zonal OCR'
WHEN aq.status = 53 THEN 'Pull Slips'
WHEN aq.status = 54 THEN 'Awaiting Ad Hoc Verification'
WHEN aq.status = 55 THEN 'QA Review In Progress'
WHEN aq.status = 56 THEN 'Synchronizaton Pending'
WHEN aq.status = 57 THEN 'Synchronizaton Complete'
WHEN aq.status = 58 THEN 'Synchronizaton Failed'
WHEN aq.status = 59 THEN 'Synchronizaton Queued'
WHEN aq.status = 60 THEN 'Synchronizaton Processed'
WHEN aq.status = 61 THEN 'Export Awaiting Transfer'
WHEN aq.status = 62 THEN 'Export Pending Verification'
WHEN aq.status = 63 THEN 'Export Complete'
WHEN aq.status = 64 THEN 'Export Error'
WHEN aq.status = 65 THEN 'Synchronization History'
WHEN aq.status = 66 THEN 'Doc Transfer Export History'
WHEN aq.status = 67 THEN 'Awaiting Formless Indexing'
WHEN aq.status = 68 THEN 'Awaiting Queue Sorting'
ELSE 'Other'
END AS [Status]
FROM hsi.archivedqueue aq
JOIN hsi.scanqueue sq
ON aq.queuenum = sq.queuenum
WHERE sq.queuenum IN (@{ScanQueue})

Batch Snapshot – Scan To Commit

SELECT aq.batchname AS [BatchName],
aq.batchnum AS [BatchNum],
aq.totaldocuments AS [DocumentsPerBatch],
sq.queuename AS [QueueName],
aq.usernum as [UserNum],
aq.datestarted AS [DateScanned],
aq.dateended [DateCommitted],
aq.status as [StatusQueue]
FROM hsi.archivedqueue aq
JOIN hsi.scanqueue sq
ON aq.queuenum = sq.queuenum

WHERE DATEDIFF(SECOND, aq.datestarted, aq.dateended) != 0

AND aq.status = 8
AND sq.queuenum IN (@{ScanQueue})

33 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
6.1.3 Parameters

@{LogRange}

@{UserGroup}

SQL Query:
SELECT usergroupname, usergroupnum
FROM hsi.usergroup
ORDER BY usergroupname

34 of 35
 Solution Blueprint – Solution Standards
HIM Operations I Package – May 2018 – Version 3.0
@{ScanQueue}

SQL Query:
SELECT queuename, queuenum
FROM hsi.scanqueue
ORDER BY queuename

35 of 35