Core of the Transformation Center
Detailed Findings
Every one of the 114 transformation opportunities drawn from the corrected Detailed Transformation Assessment, with current state, desired future state and the recommended path.
Showing 7 of 114 opportunities
Activity Time Roll-Forward
Clinical Experience & Provider Productivity
Review configuration to stop time roll-forward and align with documentation best practices Raintree can configure the activity log columns to not roll forward. In this example, we could disable rolling forward of the time column, if desired. This would work very well if header activities are leveraged, reducing the amount of places a clinician needs to document time.
Time Documentation Methodology
Clinical Experience & Provider Productivity
Evaluate transition to CPT-level time documentation and required configuration/training See above recommendation (recommendation 17).
Managing POCs/Referral Source Comm/ No Show & Cancellations/ Verification Tasks
Patient Access & Front Office Excellence
POC Tasking required for replacements plans, wc (exception TX). Liens, cash pay & should not be necessary in these instances. WHY are we creating extra work? Indu shared utility screen for CS to review and potentially remove requirements. Indu did review POC Exemption: Exempt a Plan of Care (POC) from requiring a referring provider's signature and return. This group of options is for accommodating the Medicare regulation that exempts an initial evaluation POC from requiring a referring provider's signature and return, provided a valid prescription (Rx) is on file.
BI Reporting Questions/Availability
Growth, Referral & Patient Journey
Training of the PRN team to understand current BI reporting and Dashboards available to the PRN team. Plus, Business Intelligence Dashboard Catalog attached
Email Outreach
Growth, Referral & Patient Journey
PRN team can either build the content using external tools like Hubspot and import the html file in to Raintree or they can use the WYSIWYG editor to build the content within Raintree.
Updating Payors
Revenue Cycle Transformation
There are really 2 avenues for improvement here that may help. With the first having a simplified workflow for the teams to follow, the SBP coverage correction tool option helps to enforce that the coverage correction process must be followed by users upon saving a change to the payors. This also provides the benefit of an updated workflow that does not have the user have to later go back and add the details for the parent or spouse if the policy is from a different member of the family. The second area of consideration is the ledger verifier that can help to surface when there are potential issues and help to resolve them early. The ledger verifier can be set to run automated solvers when there is a proposed solution from Raintree. This can also be run as a scheduled report that can help to highlight if and when there are common mistakes that can be used for internal training.
Ledger Lock
Revenue Cycle Transformation
Ledger Lock is recommended for use. Challenges that were discussed: For items that do need re-allocation best practice to maintain ledger lock integrity is to maintain the lock and not bypass it. The payment would still be re-posted, however the original incorrectly applied payment would be reversed and the correction would be posted all with a posting date of today (current day). In this way, the history is maintained and the historical stats remain consistent. The current day is a wash for overall cash receipts as there is a reversal and the reposting that correspond with one another. The correction will appear as a correction off of one location and onto another with the current day/month for the correction to reflect in financials.