**WSS 2/15/23

What it Does:
Appends missing encounter header data at the consumer level which facilitates costing at clinical level.

When to Run:
After importing ADT and other header data, this process will append missing header records from other clinical sources such as Med2020 Intake Header

Requirements:
Fiscal year and entities to exclude from processing



Audit Utilization RVU Match

What it Does:

Compares Product Utilization to Relative Value Units (RVU) for selected fiscal year. Sets Boolean values for:
1) rvu_matched: Is utilization is matched to rvu?
2) rvu_no_value: Utilization has rvu match but does it have a value set or not?
3) case_costed: Is Utilization record case costed? (Is it in the node of cost centre tree as case costed)

When to Run:
Typically run after importing or updating of either product utilization or RVU.

Requirements:
Fiscal year along with the Cost Centre tree that is used for Case Costing.
Please note that the standard labels are assumed to be set correctly
NODEPT – Non Operating Department
OHDEPT – Overhead Department
PCDEPTCC – Patient Care – Case costed
PCDEPTNOCC – Patient Care NOT case costed



Load And Calculate Patient Activity Costing

Steps 1 to 5 require Actuals, Utilization & Relative Value units
ACTUALS 1 Actuals Considered for PAC
ACTCOMP 2 Actuals assigned to Cost Components
ACTCOMPGRP 3 Actuals Cost Component Groups
ACTRECLASS 4 Actuals after reclass
ACTRECOV 5 Actuals with Reclass and Recoveries applied

The next steps require PAC detailed records to exist
ACTPAC 6 Actuals with Overhead applied
ACTWOHEAD 7 Actuals with Reclass /Recov to PAC Detail
ACTPACFIN 8 Final:Overhead applied Reclass/Recov by weight

When to Run:
When actuals, Utilization & RVU have been verified.  For complete run, need to ensure PAC detail exists which is a merge of Utilization and RVU data.

Requirements:
Fiscal year & GL period to include in calculations (1..12)
Cost Centre Tree & Secondary Trees used for case costing
Stop after step.  Optional to process to set point to review progress when starting process for that period.

Load Patient Episode Detail

What it Does:
Loads patient episode data which includes the diagnosis. Draws on the ADS header along with detailed clinical sources.

When to Run:
Once header and clinical data have been imported/refreshed.

Requirements:
Fiscal year. Requires the Admissions, Discharge and other services header to be populated along with clinical data available to pull that level of data.



Load Patient Episode Cost

What it Does:
Draws from the episode detailed data (including diagnosis if available) and integrates the cost data by episode.

When to Run:
Once PAC costing is complete and Patient episode detail data has been loaded.

Requirements:
Fiscal year.



Refresh Patient Episode Cost Centre Summary – Materialized Table

What it Does:
After updating the primary cost materialized table, the cost centre summary is a subset of
that table

When to Run:
After changing Patient Episode Cost

Requirements:
None

Notes:




Refresh Patient Diagnosis Summary

What it Does:
Updates the diagnosis focused materialized table.

When to Run:
After running the Episode cost and cost centre focus summaries.

Requirements:
None

Notes:




Update Patient Specific Drugs Translation

What it Does:


When to Run:


Requirements:



Update Reclass Account Translation

What it Does:

Builds the detailed administrative reclass utilizing the Reclass mask tables (expands them)

Requirements:

Reclass account translation master, current year PAC Cost Centre Tree and fiscal year.



Update Recoveries Account Translation

What it Does:

Utilizes the PAC_RECOVERIES translate master (detailed filters) to obtain the financial accounts matching that filter and maps it to its default target cost component

Requirements:

Recoveries account translation master, current year PAC Cost Centre Tree and fiscal year.




Update Tree Cost Components From Translation

What it Does:
Update the tree cost components using the value translation type

When to Run:
As needed

Requirements:
– Value Translation Type
– Secondary Tree



Utilization RVU Auto Match

What it Does:

Explores records in RVU that match on product and cost component, but not on cost centre.
Any record that is auto-updated is date stamped with current user.

When to Run:
Typically after running audit and want to try and auto-correct missing RVU’s.

Requirements:
Fiscal year along with the Cost Centre tree that is used for Case Costing.