Page 1

Ad-Hoc Reporting


Agenda Day 1:

Day 2:

Introduction to Ad-Hoc Reporting Oracle Discoverer Plus Basic Reporting Exercises Data Dictionary and Business Area Documentation Advanced Reporting Exercises

2

Copyright Š 2007, Anthem. All rights reserved.


Anthem Solutions Overview

3

Copyright Š 2007, Anthem. All rights reserved.


Reporting Tools Overview

4

Applications & Tools •Service Line-Discoverer Plus Relational •Financial Analytics-Discoverer Plus OLAP and Excel Addin •Portal graphs-Either

Copyright © 2007, Anthem. All rights reserved.


What is End User Layer? Business Area? • • • • •

EUL is the metadata EUL is created and maintained by Administrators EUL reduces complexity Each EUL can have multiple business areas Power users need to know which Business Areas they need for reporting Anthem Discoverer EUL

Busines s Area 1: Daily Indicato rs

Busines s Area 2: Product ivity

Busines s Area 3: PL Analytic s

Busines s Area 4: Product Line

Busines s Area 5: AR Monitor

Busines s Area 6: NR Model

Contents in Business Areas: Simple Folders (Tables directly from database) Complex Folders (Multiple tables displayed in one folder) Custom folders( Columns created by SQL) Items (Columns from database) Calculated Items Joins

5

•The End User Layer (EUL) is the metadata (i.e. data about the actual data in a database) that is simple and easy for Discoverer end users to understand. •You use Discoverer Administrator to create, customize, and maintain this view for your users so they can easily access data in Discoverer. You must have access to at least one EUL in order to use Discoverer. Why is the End User Layer useful? The EUL insulates Discoverer end users from the complexity usually associated with databases. It provides an intuitive, business-focused view of the database using terms that Discoverer end users are familiar with and can easily understand. This enables Discoverer end users to focus on business issues instead of data access issues.

Copyright © 2007, Anthem. All rights reserved.


EUL & Business Areas-Another View

Data Warehouse

EUL Business Area 1

Business Area 2

DB Tables

6

A single EUL may consist of multiple business areas.

A single Business Area is a collection of multiple folders.

Data is almost always delivered from the database tables

Data base tables and columns may have different names in the business area

Business areas can have calculated items that don’t exists in the database

Copyright © 2007, Anthem. All rights reserved.


3 Tier Architecture

7

Copyright Š 2007, Anthem. All rights reserved.


Discoverer Viewer vs. Plus •End users use discoverer viewer when running reports from portal •Limited flexibility on viewer to layout and format •Changes cannot be saved from viewer •Some differences exists between Discoverer for OLAP vs. Relational •Discoverer Plus is to be used by • Administrators to create standard reports and graphs • Power users to create ad-hoc reports

8

Features of viewer: •

Layout

Format

Print

Send e-mail

Export

Sort (on tabular reports)

Stop light

Copyright © 2007, Anthem. All rights reserved.


Relevant Information •

Training Scope: This training covers Discoverer Plus relational only Available reference documents for power users (available online through portal also)

– Training Manual – Data Dictionary – Table Relationship Diagrams

Ad hoc Reports vs. standard reports

9

Ad hoc Reports vs. Standard Reports •Reports available through portal are considered standard reports •Power users should save the reports in their own folders •Contact Anthem if you would like a particular report to be set as a standard report •Contact Anthem if you would like a particular standard report be available as a staring point

Copyright © 2007, Anthem. All rights reserved.


Important Considerations •

Database tables are related to each other under three possible ways – One to many (e.g Patient master has one record per encounter-charge details has multiple records for the same encounter – Many to one (e.g Patient master has many diagnoses codes sometimes repeating again and again for different patientsDiagnosis lookup table has only one entry for that diagnosis code) – One to one (Patient master and patient master supplemental info tables have one record each for each encounter

Prior to creating new reports, understand how tables are related to avoid unexpected results such as duplication of records and hidden items When designing a new report, avoid using unrelated items on the same report.

10

Copyright © 2007, Anthem. All rights reserved.


Important Considerations •

Examples of unrelated items include a combination of diagnoses codes and charge details. Asking for these in the same query may result in duplicate or unpredictable answers. The query performance may be negatively affected also. When using patient master items, apply a discharge date based condition to improve performance When using charge details and transaction details, apply a posting date condition Detail charges can be reported by department or rev code if available while transaction details can be reported by transaction codes or transaction types

• • •

11

Copyright © 2007, Anthem. All rights reserved.

Intro to Adhoc Reporting  

Adhoc Reporting - Intro

Read more
Read more
Similar to
Popular now
Just for you