Pats 0 Systems Management Guide

6.0 Business Objects XI (BOEXI)

Standard and ad hoc report structures are built and managed with Business Objects’ software. PATS was tested using Business Objects Enterprise XI edition, with Service Pack 1.

6.1 Repository and Central Management Console

The repository is populated during the Import of the Repository Items as described in the Patient Advocate Tracking (PATS) Installation Guide for HSI Staff. This section describes the structure of the repository after the import is complete.
After the BOEXI objects are imported onto your server, the database connection information for each of the standard reports must be edited to point to your database (see Section 6.1.2, Standard Report Database Source). Additional configuration is described in the PATS Installation Guide for HSI Staff, Chapter 6, Setting up Business Objects Enterprise Repository.
The repository contains all of the objects needed to manage both standard and ad hoc reports. It includes standard report templates, the universe and the universe connection to support ad hoc reporting, folder structure to organize reports, users and groups to control access to reports, and other objects. These objects are managed using the BOEXI Central Management Console (CMC).

6.1.1 Report Folder Structure

Standard Reports

The tables in this section show the report structure for standard reports.

Folder PATS – Top Level Public Reports Folder

Subfolder Ad Hoc – Holds all Public Ad Hoc (Site Created) Reports

Subfolder PATS Reports – Holds all Standard Reports

Subfolder Name: Employee
Report File Name	Description
Emp_Notifications_no_Response.rpt	Lists all Action Request Notifications (ARNs) where the employee has not responded
Employee_Contact_Totals.rpt	Lists ROCs by Employee
Report_by_Employee_Involved.rpt	Lists ROCs by Employee Involved

Subfolder Name: Facility Service Section
Report File Name	Description
Facility_Serv_Sect_Contact_Totals.rpt	Lists ROCs with issue codes and total ROC count by Facility Service or Section
Facility_Serv_Sect_Issue_Totals.rpt	Lists Issue categories and codes and total Issue count by Facility Service or Section

Subfolder Name: Issue Code
Report File Name	Description
Customer_Serv_Std_Detail.rpt	Lists the count of ROC issues at the Facilities Service or Section level
Customer_Serv_Std_Summary.rpt	Lists the count of ROC issues at the Division level
Issue_Totals_by_Gender.rpt	Lists Issue Codes and Issue counts for All, Male, or Female patients
Location_Issue_Totals.rpt	Lists Issue categories and codes and total Issue count by Hospital Location
SS_Count_Issues_by_FSOS.rpt	Display Issue Code counts for each Facility Service or Section
SS_Count_Issues_by_Institution.rpt	Display Issue Code counts for each Division
SS_Count_Issues_by_Issue_Cat.rpt	Displays Issue Code counts for each Issue Category
SS_Count_Issues_by_Location.rpt	Displays Issue Code count for each Hospital Location
SS_Count_Issues_by_Sex.rpt	Displays Issue Code count for all Males and all Females
SS_Count_Issues_by_TS.rpt	Displays Issue Code count for each Treatment Status

Subfolder Name: National
Report File Name	Description
Natl_Patient_Report.rpt	Lists all ROCs at all Divisions for a given Patient
Percent_of_ROCs_with_comps.rpt	National Report Lists Counts of Total ROCs and ROCs with Comps, and Percent of ROCs with Comps by Facility Service or Section

Subfolder Name: Patient
Report File Name	Description
Daily_List_of_Patient_Contacts.rpt	Lists the daily ROCs with patient data
Patient_Name_Brief_Data.rpt	Lists All ROCs for a single Patient

Subfolder Name: Report of Contact
Report File Name	Description
Contacts_No_Patient_Identified.rpt	Lists ROCs that have no patient involved
List_of_Open_Cases.rpt	Lists All Open ROCs by Information Taker
Report_of_Contact.rpt	Displays detailed information for a single Report of Contact
Rocs_w_Comps_by_Issue_code.rpt	Lists All ROCs with Comps by Issue Code
SS_Count_ROCs_by_Cont_Entity.rpt	Displays ROC count for each Contacting Entity
SS_Count_ROCs_by_Institution.rpt	Displays ROC count for each Division
SS_Count_ROCs_by_Issue_Code.rpt	Displays ROC counts for each Issue Code
SS_Count_ROCs_by_MOC.rpt	Displays ROC count for each Method of Contact
SS_Count_ROCs_by_TS.rpt	Displays ROC count for each Treatment Status

Ad Hoc Report Structure

Private Folders

Users are allowed to create ad hoc reports and store them in their private folders. Within the BOEXI Central Management Console, these private folders are stored within User Folders. Each user’s private folder is named the same as the user’s Account Name. When accessed from PATS or from the BOEXI InfoView portal, the users’ private folder is called their Favorites folder. A user’s private folder is automatically created when a user is added to the BOEXI repository. When a user logs on to PATS for the first time, the user is automatically added to the BOEXI repository by PATS (see Section 6.1.3, Users).

Public Folder

Users are allowed to create their own Ad Hoc reports from within the PATS application. After creating a report, if users wish to make the report public (available for all other site users), they can move the report into the public AD HOC folder described in the Report Folder Structure table above.

6.1.2 Standard Report Database Source

The database source for each of the standard reports is set up in the same way. Starting from the Folders, navigate to the report object. You can use the Folders structure documented in section 6.1.1 Report Folder Structure above to help you navigate to the standard reports. Then select the Process tab, Database option.

1. 
   Click the Use custom database logon information specified here button.
   
2. 
   Database Type: Use the default—Select a database driver. From the drop-down list, select Oracle. We use the Oracle Native Driver.
   
3. 
   Server: Enter the name of the server where the Oracle tables reside.
   
4. 
   Database: Enter the SID or service name for your database.
   
5. 
   User: Enter PATSRPTS, the name of the schema where the reports data resides.
   
6. 
   Password: Enter the password that you assigned to the PATSRPTS user.
   
7. 
   Table Prefix: Select PATSRPTS from the drop-down list. Select the Use default table prefix option.
   
8. 
   Verify that the Use same database logon as when report is run box is checked.
   

6.1.3 Users

When a user logs on to the PATS application, PATS automatically adds the user to the BOEXI repository. Their Account Name is set to the KAAJEE User Identifier. The password for every user is set to the value retrieved from the gov.va.med.pats.businessobjects.enterprise.properties file described in section 1.2 of this guide. This allows the PATS application to log a user on to the BOEXI software invisibly.
In addition, the PATS application automatically enrolls each user in the PATS_REPORTS_GROUP group. Members of this group automatically inherit certain rights that are described in detail in the Security section below.
NOTE: The PATS application also adds each user to the Oracle table user_station_list_for_ad_hoc in the PATSRPTS schema of the PATS Oracle database. This table is used by the WEBI Universe created for PATS ad hoc reporting. The table is used to control data filtering so that users are allowed to see only station data that they are allowed to access (See Universes below for details).

6.1.4 Groups

The Import creates a single User Group in the BOEXI repository. This group is used to control access to both standard and ad hoc reporting. The group is named PATS_REPORTS_GROUP. Users are automatically added to the BOEXI repository and are enrolled as members of this group when they log on to the PATS application. The Security section below describes details of the rights given to members of this group.

6.1.5 Instance Limits

Instance limits on standard reports

The instance limit for the PATS REPORT folder is set to 500. That means that, for example, there can be up to 500 instances of the Employee Contact Totals report stored in the PATS REPORTS folder at any one time. If any user creates a 501^st instance of that report, then the oldest instance of that report in the folder will be automatically deleted, regardless of who generated it.

Within the PATS REPORTS folder, the PATS_REPORTS_GROUP has an instance limit of 3. This means that any user who belongs to the group, which is all users of PATS, can have a maximum of 3 instances of any single report within the PATS REPORTS folder. So if a user already has 3 instances of the Employee Contact Totals report, and they generate a 4^th instance, their oldest instance is deleted.
Instance limits on ad hoc reports

The PATS system does not support multiple instances of ad hoc reports. For that reason, there are no instance limits on the Ad Hoc report folder, or on the individual user’s folders.

6.1.6 Security

Along with bringing the folders and the user group, the import brings in the rights assigned to users who are members of the PATS_REPORTS_GROUP group as described in this section.
Folder and Report Access Assigned to the PATS_REPORTS_GROUP
Standard Reports Folders

Advanced Rights are assigned to the group PATS_REPORTS_GROUP for the PATS Folder. The PATS Reports subfolder and all the subfolders within it, inherit all rights from the PATS Folder. This controls user access to the standard reports. The rights that the group PATS_REPORTS_GROUP has for the folder PATS are set up as shown on the next page.

Ad Hoc Reports Folder

Advanced Rights are assigned to the group PATS_REPORTS_GROUP for the AD HOC subfolder. Though this subfolder descends from the PATS folder, these advanced rights override the rights given to the PATS folder. This controls user access to ad hoc reporting. The rights that the group PATS_REPORTS_GROUP has for the folder AD HOC are set up as shown:

User Access to Ad Hoc Data

Users belonging to the PATS_REPORTS_GROUP group are granted View on Demand access to the Web Intelligence universe named PATS Universe, built to support Ad Hoc reporting, and to the universe connection named PATS Oracle 10g used to connect to the PATS data in the underlying Oracle database.

Data in the Ad Hoc Universe is filtered by user. Each user is allowed to access only data for the sites to which that user has access. Details are described in the Universe Data Filtering section within the WebIntelligence section below.

6.1.7 Universe Connections

The universe connection, PATS Oracle 10g, is used to make the database connection between the Web Intelligence Universe used for Ad Hoc reporting, and the underlying PATS data in the Oracle 10g database. The Import installs this universe connection in the BOEXI repository The universe connection is created and maintained by the PATS developer using the BOEXI Universe Designer rich client application. See the Universe Connection section 6.2.2 for details on how the PATS Oracle 10g connection was designed, as well as how to change it to reference a different database if necessary.

6.1.8 Universes

The Web Intelligence universe that supports ad hoc reporting is called the PATS Universe. The Import installs this universe in the BOEXI repository. A universe is a meta-data mapping that hides the complexity of the underlying PATS data used for ad hoc reporting. This structure provides end users with user-friendly field names that can be used to create ad hoc reports. The universe is created and maintained using the BOEXI Universe Designer rich client application. This tool is also used to connect the Universe with its Universe Connection to the database. There is no Object Level Security associated with the PATS Universe. The PATS_REPORTS_GROUP, to which all PATS users belong, is given View on Demand rights to the PATS Universe. See section 6.2.3 for details on how the developer designed the PATS Universe.

6.1.9 Licensing

Production will run with a CPU license for BOEXI. The CMC is used to add the license key. When the license key is entered, the associated items on the screen are automatically updated (i.e. Named Users, Concurrent Users, Processors and Expires). Note that the licensing information is not installed by the Import, but must be added manually by the server Administrator.