Healthcare organizations can extend FDI data with Procedure-level clinical and CDM data without moving patient-identifiable information into the analytics layer. The recommended enterprise pattern is to land governed, aggregated healthcare data in a custom ADW extension layer, reconcile it to FDI ERP finance facts, extend the semantic model, and expose the result in OAC workbooks for finance and operational leaders.
Why this Reporting Angle?
A regional referral center or hospital network often needs to explain revenue not only through the financial chart of accounts, but also through the clinical activity that generated the financial signal. Finance leaders may ask why revenue changed, while operational leaders ask where volume pressure is building. CDM procedure analytics connects those two conversations.
The demo workbook focuses on procedure-level charge and volume reporting. It intentionally avoids patient-level details. Instead, it uses aggregated procedure activity that can be joined to finance dimensions such as fiscal period, balancing segment, operating unit, and cost center.
The Level 1 – Exploring Pattern
This DVA contains integration with Procedures as an external dataset. This pattern is quick and easy as the join is configured at the workbook level. It can be the first level of exploration to understand how your FDI data can be extended further with industry drivers.
FDI Enterprise Pattern
The preferred and recommended enterprise pattern remains the integration of healthcare data into a custom ADW extension layer, extending the semantic model, and exposing the result in OAC workbooks:
This allows the external Healthcare data to coexist with the Oracle modeled ERP ADW content. This way the Procedure becomes a genuine reusable dimension.
You can also leverage any other possible options available within FDI to augment / load data into the warehouse.
We won’t be explaining here all the possible options but know that you might consider different approaches depending on your current landscape, data-analytics maturity, time and cost.
Workbook Story –Procedure Level Reporting
This workbook focuses primarily on answering questions around:
- Which procedures and procedure families drive the most charge amount and procedure volume.
- Where volume is concentrated by cost center, operating unit, and balancing segment.
- Whether some units are seeing volume growth without proportional charge growth.
- Which procedure/cost-center combinations create operational pressure.
- Where finance or revenue integrity teams should focus validation and follow-up.
If we look at the changes over time, comparing current and prior years for Orthopedic Surgery cost center, we observe that the workload grew faster than revenue, creating revenue-per-procedure pressure:
Volume +13.3% = growth / workload pressure
Revenue +5.5% = moderate growth, but behind volume
Revenue per Procedure -6.9% = yield pressure
Procedures portfolio view:
If we want to explore this angle further, we bring in also the charge per procedure fact and create a clustering with different variables.
The below Scatter Plot shows how much volume did we have, how much charge amount did it generate, and what type of pattern does it belong to?
We can also observe that cluster 4 is the cluster of procedures which are more frequently performed like blood and other lab analysis. It represents over 75% of the total charge amount, but the charge per procedure is less than those with less volume and overall higher charge amount.
These are very high-volume procedure/cost center combinations. They may create operational pressure even if charge per procedure is not very high.
FDI comes with a Content Catalog with the subject area and KPI definitions. You can also extend your custom workbooks with your definitions and documentation of your industry KPIs. Here is an example in this dashboard, we have included a small Data Dictionary on the last Canvas:
This DVA is downloadable, but note that the underlying data is a demo dataset.
To make it reusable, update the joins and the Procedure content to reflect your FDI GL Profitability data.
NOTE: This workbook does not consider any data level security, as that is outside the scope of the usecase and artefact. You need to leverage the possible options available to secure your data based on your organizational goals and needs
