Data Warehouse User GroupApril 25, 2013

Infrastructure Upgrades

HB wRVU Correction

Apex AR Trends Cube Preview

Training / User Group Meeting Schedules

Cognos Infrastructure Upgrades

Why make the changes?Issues with Cognos 8.4 performance

QS - Latency in retrieving large amounts of data

AS – Nested reports take a while to render

One errant user had the potential to impact everyone elseIncrease in user base

Cognos 8 Initial Environment

Cognos 8 Upgraded Environment

APEX-HB wRVU Correction

Background Info Pre-APEX: 3 and 7 split

Many codes entered into TES “explode” and post to both billing systems:

3 IDX Pro component 7 SMS Tech component

APEX: PB and HB splitThe charge router does something similar.

Pro component Routed to Resolute PB Tech component Routed to Resolute HB

IMPORTANT - You only want to calculate wRVUs on the “Pro” portion of the split charge!

APEX-HB wRVU Correction

APEX: PB and HB split - How to we identify these split charges?Original methodology – HB Modifiers

HB Modifiers, new with Apex Increase the accuracy of wRVU values In practice, HB modifiers inconsistent and “dirty” (ex: 26 and TC

on same procedure) Revised methodology – Claim Type of Procedure

In APEX-HB there is a “Claim Type” for each procedure (EAP) Using this we can “weed out” the Tech components before take a

look at the modifiers

APEX-HB wRVU Correction

Pro/Tech Flag (calculated field)Pre-APEX Definition of “TECH”

Prefix = 7 or GL Comp Type = T

APEX Definition of “TECH” APEX-PB Procedure (EAP) Claim Type Flag = 2 APEX-HB Procedure (EAP) Claim Type Flag =

2AND Billing Category NOT IN (0,6)

Added Billing Category Dimension for Clarification

APEX-HB wRVU Correction

Departmental Impact / ScopeTwo cubes were affected

apex_utilization apex_idx_sms_utilzation

Isolated to APEX-HBModest reduction in overall wRVUsSome departments impacted more than othersThe correction only represents 0.4% of the wRVUs that have been generated since the APEX launch

APEX AR Trends Cube

Contains AR from APeX–PB only Similar in structure to the IDX AR

Trends Cube Added Proc Category/CPT dimension No drill through

AR Trends – Quick Facts Days in AR calculation (DAR)

Average Daily Charge = [Charges for 3 months ending current]/[Calendar Days in 3 months ending current]

DAR = [Month-end AR ]/[Average Daily Charge] First two months of Apex (June 2012 and July

2012) the Average Daily Charge calculation used 1 and 2 months respectively

Use Calendar days Aging buckets calculated using Charge Post

Date vs AR Reporting Month

APEX AR Trends Cube

DEMO

What’s next? An initial Apex Transaction

Framework Package for Query Studio - the detailed reporting environment you currently have for IDX, where elements are organized neatly into logical folders (dates, patient info, ASA units, etc.)

Reimbursement Cube

Upcoming Cognos Training Next Cognos 8.4 Training scheduled for May

23nd and 24rd (Thursday and Friday). Sign up deadline is May16

Minimum of 3 people needed We’re looking into recording and/or web-based

options so that training can be referenced online.

Latest Training Schedule can always be accessed by clicking on the “training and class information” link from the main data warehouse page, or by going to:

http://medgroup.ucsf.edu/data-warehouse/training-classes

User Group Meeting Schedule

Next Meeting – Thursday, May 16th User group meeting are being moved from

the 4th Thursday of the month to the 3rd Thursday of the month

Time change from 10:30AM to 2PM Recurring meeting invite will be sent out Topic suggestions welcome! New schedule will be posted on the Website

(scroll to the bottom):

http://medgroup.ucsf.edu/data-warehouse

Questions?