1. Data Warehouse User Group June 28, 2012  Transactions in Apex – a first look

2. 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

3. 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)

4. 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)

5. 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

7. Transactions in Clarity – what you don’t see (easily) from Hyperspace 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 ACCOUNT_IDTX_NUMTX_ID DETAIL TYPEDetail DescriptionPOST_DATE ORIG SVC DATEMATCH_TRX_ID AMOUNT INVOICE NUMBER VISIT NUMBER XXX999518481330092New Payment6/6/2012 ($20.00) XXX999518482825771New Charge6/9/20126/4/2012 $815.00 ZZ385936 XXX999518483826171New Charge6/9/20126/4/2012 $1,507.00 ZZ385936 XXX9995184838261750Claim6/13/20126/4/2012 Y2000108492ZZ385936 XXX9995184828257750Claim6/13/20126/4/2012 Y2000108502ZZ385936 XXX9995184813300932Match/Unmatch (Payment->Charge)6/13/20126/6/2012170537$20.00 XXX9995184841705371New Charge6/13/20126/6/2012 $391.00 ZZ386223 XXX99951848417053720Match/Unmatch (Charge->Payment)6/13/20126/6/201233009($20.00) ZZ386223 XXX99951848417053750Claim6/14/20126/6/2012 Y2000172902ZZ386223 XXX9995184852687931New Charge6/16/20126/14/2012 $410.00 ZZ386469 XXX99951848526879350Claim6/18/20126/14/2012 Y2000265602ZZ386469

8. 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)

9. (Future) Transaction Reporting from Cognos BILL_AGENT:MEDICAL GROUP BUSINESS SERVICES DETAIL_TYPEDETAIL_TYPE_DESC CHARGES PAYMENTS CONTRACT_ADJ CREDITS DEBITS REFUNDS DISCOUNTS BAD_DEBT CHARITY WRITE_OFF 1New Charge 24,804,302.96 - - - - - - - - - 2New Payment - 899,455.87 - - - - - - - - 3New Debit Adjustment - - - - - 25.00 - - - - 4New Credit Adjustment - - 258,908.82 - - - - - - - 5Payment Reversal - - - - - - (11,003.12) - - - 6Credit Adjustment Reversal - - - - - - (13,578.91) - - - 10Void Charge (1,000,450.76) - - - - - - - - - 11Void Payment - (29,897.63) - - - - - - - - 13Void Credit Adjustment - - (996.36) - - - - - - - 20Match/Unmatch (Charge->Payment) - 109,750.17 - - - - - - - - 21Match/Unmatch (Charge->Credit Adjustment) - - 244,333.55 - - - - - - - 22Match/Unmatch (Debit Adjustment->Payment) - 11,028.12 - - - - - - - - 23Match/Unmatch (Debit Adjustment->Credit Adjustment) - - 13,578.91 - - - - - - - 30Match/Unmatch (Credit Adjustment->Charge) - - (244,333.55) - - - - - - - 31Match/Unmatch (Credit Adjustment->Debit Adjustment) - - (13,578.91) - - - - - - - 32Match/Unmatch (Payment->Charge) - (109,750.17) - - - - - - - - 33Match/Unmatch (Payment->Debit Adjustment) - (11,028.12) - - - - - - - - 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