Release notes

Summary: The Balance Sheet and Cash Flow calculator has been disabled for this release so that we can prepare for an improved version of the calculator in an upcoming release.

Resolution: Corrected by temporarily removing the Balance Sheet and Cash Flow calculator from the product.

Summary: In the Deductions tab of the Deductions Model calculator, in OP Medicare, the quarterly per visit amounts appear to be summing the months instead of recalculating the sum of net revenue divided by the sum of visits for a weighted average.

Resolution: Corrected by updating the formulas to calculate the OP Medicare amounts correctly.

Summary: In the Deductions tab of the Deductions Model calculator, in OP Medicare, the quarterly “per visit” amounts appear to be summing the months instead of recalculating the sum of net revenue divided by the sum of visits for a weighted average.

Resolution: Corrected by updating the formulas to calculate the OP Medicare amounts correctly.

Summary: In the Deductions tab of the Deductions Model calculator, in the Bad Debt and Charity sections for the forecast periods, the calculation is using the wrong denominator. For both IP sections (IP Bad Debt %/IP Charity Care %), the denominator is Total Revenue but should be IP Gross Revenue. OP Bad Debt % / OP Charity Care % are also dividing by Total Revenue but should be dividing by OP Gross Revenue.

Resolution: Corrected by changing the denominator in the IP and OP sections of the forecast periods to reference the correct denominator.

Summary: In the plan file Forecast worksheet, the Salary calculation method in the first forecast month should be divided by a different amount than it is currently using, as should all the following forecast months.

Resolution: Corrected by adding the scaling factor divisor to the formula in each monthly forecast cell.

Summary: In the plan file Forecast worksheet, the Expense calculation method does not allocate the manual adjustments in the monthly entry columns to the Fixed expense based on Fixed/Variable percentages in the Fixed/Variable % column.

Resolution: Corrected by updating the calculation formula and by adding a total line that includes the adjustments.

Summary: In the plan file Forecast worksheet, in the Variable Hours Per Unit row, for the last period actuals column before the forecast columns, the Salary calc method formula is referencing the wrong cell.

Resolution: Corrected by updating the calc method formula to reference the right cell.

Summary: In the plan file Forecast worksheet, when a user makes a volume adjustment, they do not see the corresponding impact in the hidden section of the Variable Salary costs. The volume/statistics One Time Adjustment (OTA) is not affecting the FTEs and the Hours for the variable component.

Resolution: Corrected by updating the calc method formula to include the adjustment in the total.

Summary: In the plan file Forecast worksheet, when a user sets an expense to something other than 0% or 100% in the Fixed/Variable column, the variable rate calculates too low. When calculating the historical fixed and variable expense, it takes the fixed/variable ratio into account. Then the formula that calculates the variable rate multiplies the variable expense by the variable percentage again, which reduces the rate to half of what it should be.

Resolution: Corrected by adjusting the calculation to remove the multiplication of the variable ratio.

Summary: In the plan file Forecast worksheet under Patient Days, the informational line “Impact of Volume OTA” for the Salary calc method is supposed to display the effect of OTAs in the Volume calc method on the salary projections. However, the formula is missing the variable hours per unit factor so the amount displayed is not correct.

Resolution: Corrected by updating the formula to include the variable hours per unit adjusted for productivity changes.

Summary: In the plan file Forecast worksheet, the Rate per FTE calc method is summing the monthly FTEs in the quarterly columns. This is incorrect and is occurring in both actuals and forecast columns.

Resolution: Corrected by updating the Rate per FTE calc method to sum in the correct columns.

Summary: In the plan file Forecast worksheet, if a user adds a one-time adjustment in the Salary block, the value impact of that adjustment does not get picked up in the Benefits cal method, Pct of Salaries, and Rate per FTE.

Resolution: Corrected by adjusting the applicable formulas so that the OTA totals in the Salary blocks flow through to the Benefits sections and are included in the calculations.

Summary: In the plan file Forecast worksheet, the calculation for the IP Census is incorrectly summing the quarterly columns.

Resolution: Corrected by updating the formula so that the quarterly columns are calculated correctly.

Summary: In the plan file Forecast History worksheet, Axiom Query 2 (AQ2) is summarizing all Forecast items labeled ForecastFinal instead of selecting a specific RFPeriod. This results in the History table displaying incorrect amounts.

Resolution: Corrected by adjusting AQ2 to include the active period in the data filter.

Summary: In the plan file Initiatives worksheet, when the users adds an initiative Volume block after the 500th row in the worksheet, an error displays reading “Could not find data source named... .”

Resolution: Corrected by establishing dynamic logic for Volume option selections to account for Volume block row limit.

Summary: In the plan file Initiatives worksheet, after a user adds an initiative and saves, then processes the plan files using the Scheduler, the recalculation fails and produces a cell formula error message.

Resolution: Corrected by refactoring the formula for the Volume calc method in the affected column.

Summary: In the plan file Initiatives worksheet, when a forecast rolls to a new period, any periods that were forecasts but are now actuals should have their adjustments zeroed out and reset. Instead, the previous amounts are appearing in the Actuals columns and saving back to the database, causing errors.

Resolution: Corrected by incorporating the same roll logic as is used in the Forecast worksheet. Any adjustment from a period that was a forecast in the prior run and is now an actual is zeroed out.

Summary: In the plan file Initiatives worksheet, when a user adds an initiative block (RF Group or RF Project), and then adds an RFCode that uses the Line Item calc method such as Non-operating Revenue, and then saves, the plan file rebuilds with the last saved calc method or CalcMethodforRebuild. This requires associated AQs to correlate with refresh behavior.

Resolution: Corrected by adjusting the related Axiom Query on SupportingData tab (AQ2) to refresh after the user saves the new initiatives block.

Summary: For users with new RF 2.0 installations, the Executive Overview tab in the RF Manager Dashboard does not display data if there is no prior forecast period to compare current data to, and if the Data Display Options setting in the Rolling Forecasting Manager Dashboard Settings utility is set to Period; this does not occur when it is set to YTD data.

Resolution: Added a message to the dashboard that reads, “This dashboard will become active when you have at least two periods of data to compare.” This message will display when there are less than two forecast periods (includes current period).

Summary: In the EBIDA Summary report (EBIDA Details view), for a given month or quarter of actuals, the Margin amount and EBIDA % do not match the amounts in the corresponding month or quarter in the plan file Summary worksheet because setup data is missing from the ForecastStdLine column in the RFCODE table; fields in the column contain “NA” instead of a calc method.

Resolution: Corrected by making the following changes:

• Selected a calculation method instead of “NA” for the applicable fields in the RFCODE table.

• In the ForecastHistory worksheet, adjusted the Total Expenses formula to not include Total Non-Operating Revenue.

• In the EBIDA Summary report, updated the Refresh Variables filter for RFGROUP to be KHABgtCode compliant.

Summary: In the Month End Variance report, when a user with access to only specific RFGroups selects to add an Entity Exception to the Threshold Level table, the Choose an Entity to Add an Exception selection list includes entities to which the user should not have access, based on that user’s security settings.

Resolution: Corrected by adding a new entity exception required filter, and by making the primary table RF_Forecast_YYYY so that the security from that table applies to entities available for selection in the Month End Variance report. Also adjusted coding for applicable calculation methods and field definitions and set manual refresh to On.

Summary: In the Target Variance report, if a statistic with no history is added to the plan file Forecast tab and then the forecasted data is saved to the RF_ForecastYYYY table, the report does not query in this data because Axiom Query 1 expects the stat to also be in the ACT table.

Resolution: Corrected by separating AQ1 and AQ2 to remove unnecessary dependencies that were causing the issue.

Summary: In the Consolidated Summary report, in the current year total column for Average Daily Census and FTEs, the formula is referencing the wrong column cell, which is blank, resulting in a calculated value of zero.

Resolution: Corrected by updating the calculation formula to reference the correct cell.

Summary: In the Consolidated Summary report, for the current year total, when a user is in the 12th month of their fiscal year, the column name reads “Forecast” but it should read “Actual.”

Resolution: Corrected by changing the column label to be dynamic instead of hard coded.

Summary: In the Consolidated Summary report, when a user moves forward to the next month, if they have not built out their forecast for the new month, the forecast columns for the report will display zeros. This happens because, among other things, the forecast columns are not referencing the refresh variable for RFPeriod.

Resolution: Corrected by making the references to the previous RF period variable fixed, and by making the forecast columns dynamically reference the refresh variables. Additionally, set the Scenario variable to note the selected period.

Summary: After a user forecasts for a specific period, the VCC Setup utility is not allowing them to move forward and do a comparison report against that forecasted period. The Actual Period selection allows the user to go only as far as the Last Forecast period.

Resolution: Corrected by fixing the quarterly labels, which were off by a year where the calendar year is different from the fiscal year.

Summary: In the Target Variance report, under Operating Expenses, the calculation formula for the drug expense row is missing in the Current Month Target Column but is in all other Operating Expenses rows.

Resolution: Corrected by adding the calculation method formulas to the applicable rows.

Summary: In the Target Variance report, the statistic in Axiom Query 1 (AQ1) is hard coded as Acct.Acct when the user selects a filter method or RFGroup. This is causing RFGroups that have statistics to default to Calendar Days.

Resolution: Corrected by updating the AQ1 formula to reference the correct cell, and also changed the cell formatting to MMM-YYY. Also reconfigured the report so that its layout is similar to the Consolidated Summary report, including adding a non-operating revenue section at the end. For details, refer to the online help topic “Using the Target Variance report.”

Summary: In the Manager Dashboard, a number of issues are causing problems with the display of historical performance analysis data in some of the Executive Overview tab’s KPI cards. This occurs:

• On the Summary tab’s Net Income Over Expenses KPI card when the tab’s Data Display Options for Totals or Per Unit Data is set to Totals.

• On the Labor Overview tab’s Paid Hours per Unit KPI card when the tab’s Data Display Options for

Resolution: Corrected by disabling the display of historical analysis data in the affected KPI cards. The Historical Performance Analysis table will not display for these cards, nor will the Historical Analysis icon ().

Summary: After a rollforward period is finalized, in the plan file, suppose a user needs to change the RFCode calculation method for a given RFGroup. In the RFCODE table, the user changes the calculation method listed in the RFCode.ForecastStdLine or RFCode.InitStdLine column for the RFGroup. The user saves the table, opens the plan file Initiatives tab, saves the plan file, and then rebuilds the plan file. When the user opens the rebuilt plan file, they see that the RFGroup is still using the previous calculation method, not the new one.

Resolution: Corrected by updating the code in the Axiom Query to allow for the calculation method set in the RFCode.ForecastStdLine or RFCode.InitStdLine column to determine the calculation method for the rebuild instead of the calculation method last saved in the plan file.

Summary: In the Deductions Model calculator Deductions sheet, in the variable actual/forecast columns, Charity and Bad Debt are not calculating correctly because they are referencing the wrong cells.

Resolution: Corrected by updating the formulas to reference the right cells.

Summary: In the Deductions Model calculator Deductions sheet, for some of the Forecast columns, input is not allowed in the following payor sections:

• Medicare Outpatient – % of Charges, Per Visit

• All other Payors – % of Charges, Per Case, and Per Diem

Input for Per Member Per Month is allowed.

Resolution: Corrected by updating the worksheet so that for both the Medicare block and Other block, for both IP and OP, the relevant cells in columns IQ and IR are input cells when their periods are forecasts and protected when actuals.

Summary: In the Administrative Adjustments section of the RF Deductions Setup utility, when a user has selected Total in the drop-down, the Deductions Model calculator only calculates against the IP Gross Charges. The calculation in the calculator is only dividing by IP revenue regardless of what is selected in the setup utility.

Resolution: Corrected by modifying the formula to calculate correctly when Total is selected. Updated for all historical and actual columns, both months and quarters, and the quarterly forecast columns.

Summary: When users add a new driver forecast assumption in the Drivers tab of the Drivers setup utility, and then go to the Code Mapping tab to map the assumptions to driver codes, they are able to select adjustment codes from the Driver Codes menu. This should not be possible because it creates invalid drivers in the plan file.

Resolution: Corrected by adding a data filter to the Driver Code menu code that excludes adjustments.

Summary: The Benefits calculation methods Percent of Salaries and Rate per FTE are not saving the correct row to the RFDType ForecastFinal rows in the forecast tables. The values saving to this RFDType are incorrect, especially the FTE impact value. The plan file Forecast and Summary sheets are displaying incorrect amounts as a result.

Resolution: Corrected by moving the ForecastFinal save row to the correct final result row in the calculation methods.

Summary: In the plan file Forecast worksheet Expense sections, when a user makes a one-time adjustment to an Actual period, the adjustment is being included in the total line, which saves to the Forecast Final RFDType, which is then changing the actual values. Onetime adjustments should not affect the final total amount.

Resolution: Corrected by updating the formulas so that the one-time adjustments are not included in the final total amount for Actual periods.

Summary: In the plan file Forecast worksheet, in the forecasted columns of the current quarter, the Patient Revenue calculation method is double counting the inflation rate and the adjustments, causing the average rate per unit to be wrong.

Resolution: Corrected by modifying the formulas in the Patient Revenue calculation method to remove double counting.

Summary: In the Patient Revenue, Patient Revenue IP Census, and Patient Revenue Net Per Unit calc methods, a circular reference is being introduced when a user selects the CMI Adjusted Admits\Discharges or the CMI Inpatient Admits\Discharges to calculate the per unit ratio.

Resolution: Corrected by removing the CMI Adjusted Admits\Discharges or the CMI Inpatient Admits\Discharges as options used to calculate the per unit ratio.

Summary: In the Multi Scenario Comparison report, the headers for Forecast type are displaying quarters beyond the current quarter as “Projected” instead of “Forecast.” Headers for Forecast Quarterly are dynamic instead of defaulting to Actual data.

Resolution: Corrected by adjusting the headers in the report to be consistent with those used in the plan files. Only the Current quarter should be labeled “Projected” if it includes both Actual and Forecast periods.

Summary: In the Multi Scenario Comparison report, misaligned references in 2-5 of the scenarios selected for comparison are resulting in incorrect FTE calculations. For O perating EBIDA Margin %, found formatting difference for percentage.

Resolution: Corrected by adjusting reference alignment for scenarios 2-5 in the current quarter. Adjusted the Operating EBIDA Margin % formatting to match similar sections for monthly quarters.

Summary: In the Multi Scenario Comparison report, incorrect references in scenarios 3-5 are resulting in incorrect calculations for multiple sections.

Resolution: Corrected by adjusting references and cleaning up inconsistent formatting.

Summary: In the Manager Dashboard, when the current period and prior period fall in different calendar years, the wrong year displays in the dashboard sub header. The Previous Forecast Period in the report sub header is derived using logic different from the other date displays.

Resolution: Corrected by updating the logic for the Previous Forecast Period so that it displays the correct date.

Summary: In the VCC Setup Utility, the set Actual and Forecast periods do not match the periods displayed in the Month End Variance report, and the report column labels do not match the ones set in the VCC Setup Utility.

Resolution: Corrected by adding logic that determines the Forecast RFPeriod date and then referenced this in the report column headers.

Summary: In the RFCODE Dimension table, standard RFCodes that have the calculation type “Deduction” or “Other Deduction” in the RFType column are being delivered with the wrong calculation type in the corresponding InitStdLine column. The delivered calculation type is “Revenue” or “Line Item,” but it should be “Deduction.” This is causing issues in the plan file Initiatives worksheet.

Resolution: Corrected by updating the calculation method to “Deduction” in the InitStdLine column for the affected RFCODEs.

Summary: In the plan file Forecast worksheet, on the Employee Benefit Rate per FTE line, the Actuals quarter columns are summing the three months, which is incorrect, while the forecast quarter columns are calculating the Rate per FTE for the quarter, which is correct.

Resolution: Corrected by changing the quarterly results in forecast periods to reflect the total benefits for the quarter/FTEs for the quarter. Also changed the labels to reflect Benefits per FTE rather than Rate per FTE.

Summary: When the global data calculation method is used in a plan file, the data coming from the driver is not KHABgtCode compliant.

Resolution: Corrected by updating the Global Data calculation method to be RFCode.KHABgtCode compliant. It now only allows insertion of RFCodes where ForecastStdLine = Global Data and RFCodes that exist in KHABgtCode column. If data in the Global Data driver was stored at the RFCode level, the plan file was updated to bring consolidated results from the driver table at the KHABgtCode level. Subsequently, we updated the Update Global Data utility to consolidate records and save data at the RFCode.KHABgtCode level, and to delete orphaned records (where RFCode does not equal KHABgtCode).

Summary: In the plan file Forecast worksheet, the Pct of Salaries calculation method and the Rate per FTE calculation method use the total Salary/FTE values to compute the benefits. Users want the option to exclude contractual labor from the total salaries calculation.

Resolution: Corrected by updating the calculation methods so that the user does not need to select a benefits code when the selected Salary code is E_Salaries_Contract.

Summary: In the Summary tab of the Manager Dashboard’s Executive Overview tab, when Data Display options are set to Totals, initiatives data is not populating or being included in the Historical Performance Analysis drill tables, so the historical analysis data does not match what is displayed on the KPI card.

Resolution: Corrected by adjusting the Axiom Query filters to allow for initiatives data to display.