Transcript Transactions in APeX - A first look.ppt

Data Warehouse User Group
June 28, 2012

Transactions in Apex – a first look
Transactions in Apex


Transactions were at the core of our
old data mart built on IDX – the
same will be true in Apex
However, the Transaction Paradigm
is *very different* in Apex
Transactions in Apex



Transactions are posted to Guarantor
Accounts, not specific Invoices, as in our
IDX system; i.e. Guarantor Account is the
“wrapper”
Transaction lines increment for the
Account, not for specific encounters.
One Guarantor Account will have many
Dates of Service (DOS)
Transactions in Apex


When looking at a Transaction (specific
Tx_Num) in Hyperspace, what’s shown is a
Snapshot of that Transaction, reflecting
the current, calculated balances
What’s often not obvious is all the activity
going on behind the scenes that
contributes to those balances (voids,
matching records, actions). These are
called Transaction Detail records (TDL)
To understand Transactions, we need to
understand their Detail Types (TDL)
slkjdf
Only New Transactions
(with their Running
Totals) appear in the
upper window of Prof
Tx Inquiry
“Matching” and
other detail Types of
can be viewed by
clicking on the tabs
in the lower window
of Prof Tx Inquiry, or
switching to a
different view, like
Prof Inv Inquiry
Transactions in Clarity – what you
don’t see (easily) from Hyperspace
ACCOUNT_ID
TX_NUM
DETAIL
TYPE Detail Description
TX_ID
POST_DATE
ORIG SVC
DATE
MATCH_TRX_ID
AMOUNT
INVOICE
NUMBER
VISIT
NUMBER
XXX99951848
1
33009
2
New Payment
6/6/2012
6/6/2012
XXX99951848
2
82577
1
New Charge
6/9/2012
6/4/2012
$815.00
ZZ385936
XXX99951848
3
82617
1
New Charge
6/9/2012
6/4/2012
$1,507.00
ZZ385936
XXX99951848
3
82617
50
Claim
6/13/2012
6/4/2012
Y2000108492
ZZ385936
XXX99951848
2
82577
50
Claim
6/13/2012
6/4/2012
Y2000108502
ZZ385936
XXX99951848
1
33009
32
Match/Unmatch (Payment->Charge)
6/13/2012
6/6/2012
XXX99951848
4
170537
1
New Charge
6/13/2012
6/6/2012
XXX99951848
4
170537
20
Match/Unmatch (Charge->Payment)
6/13/2012
6/6/2012
XXX99951848
4
170537
50
Claim
6/14/2012
6/6/2012
XXX99951848
5
268793
1
New Charge
6/16/2012
6/14/2012
XXX99951848
5
268793
50
Claim
6/18/2012
6/14/2012

($20.00)
170537
$20.00
$391.00
ZZ386223
33009
($20.00)
ZZ386223
Y2000172902
$410.00
ZZ386223
ZZ386469
Y2000265602
ZZ386469
Couple of things to note:




Our 5 “New” Transaction Lines have at least 11 associated transaction detail lines, many
of them doing the heavy lifting
All “New” transactions are basically stand-alone until “matched” to another transaction
for the same Account
Transactions point to each other, but don’t always contain the same column information
From Hyperspace, the relationships look obvious; on the back end, it’s messy
Transaction Reporting from
Hyperspace/Clarity
Good for…..helping us tie
our warehouse totals to the
Clarity/Chronicles Totals
Not so good for.....helping us
make sense of how our
Division/DEP/Provider is doing
(unless you’re an accountant)
(Future) Transaction
Reporting from Cognos
BILL_AGENT:
DETAIL_TYPE
MEDICAL GROUP BUSINESS SERVICES
DETAIL_TYPE_DESC
1 New Charge
2 New Payment
3 New Debit Adjustment
4 New Credit Adjustment
5 Payment Reversal
6 Credit Adjustment Reversal
10 Void Charge
11 Void Payment
13 Void Credit Adjustment
20 Match/Unmatch (Charge->Payment)
21 Match/Unmatch (Charge->Credit Adjustment)
22 Match/Unmatch (Debit Adjustment->Payment)
23 Match/Unmatch (Debit Adjustment->Credit Adjustment)
30 Match/Unmatch (Credit Adjustment->Charge)
31 Match/Unmatch (Credit Adjustment->Debit Adjustment)
32 Match/Unmatch (Payment->Charge)
33 Match/Unmatch (Payment->Debit Adjustment)

CHARGES
24,804,302.96
(1,000,450.76)
-
PAYMENTS
899,455.87
(29,897.63)
109,750.17
11,028.12
(109,750.17)
(11,028.12)
CONTRACT_ADJ
258,908.82
(996.36)
244,333.55
13,578.91
(244,333.55)
(13,578.91)
-
CREDITS
-
DEBITS
-
REFUNDS
25.00
-
DISCOUNTS
(11,003.12)
(13,578.91)
-
BAD_DEBT
-
CHARITY
-
WRITE_OFF
-
Our Goal is to strike the right balance



To keep enough of the detail to allow you to tie back to live system, and the reports you
tend to run out of Hyperspace (Workbench or Clarity)
To remove or hide any excess detail that doesn’t help in your understanding
To restate the same data in ways that make more sense from a business perspective