Risk Adjustment coding reviews can take many different shapes and forms. When starting a new project/review, there are many things to consider. A “Project Management” approach is key to success. Project Management includes four phases: Project Planning Phase; Project Build-up Phase; Project Implementation Phase; and Project Completion & Closure Phase. In this article we will address the Risk Adjustment Review best practices using a Project Management approach.
Project Planning Phase: In this phase it’s important to lay out the why’s and how’s to the project. Why are we doing it and how are we going to get it done. Below is an outline:
- Identify Stakeholders: Stakeholders can be various depending on the size of the organization and the anticipated benefits or results from the review. They are the individuals in an organization that will be impacted by the outcome of this review, or whose resources are necessary to perform the review (staff, tools, information and money).
- Define Objectives: Simply why are we doing this review? For overall compliance? To find errors in codes that were submitted? To find diagnoses not previously submitted? To educate Providers in HCC code capture? To find missing revenue?
- Define Project Scope: The below items are typically needed to define the project scope:
- Dates of service – What dates of service (or timeframe) for charts will be reviewed
- Payors – Which payors (insurance type) will be reviewed
- Volume -- How many charts/patients will be reviewed
- Review Approach – This part is very important and can vary immensely but is necessary to delineate. What specifically will be reviewed, what capture points or items will be gathered. Additionally, what other tasks that will be required of the team? It is important to know exactly what the project entails, as this will enable planning for staffing and training.
- Staffing requirements – This can be calculated using an estimated charts per hour or patients per hour calculation. Knowing staffing requirements is important because if understaffed, the job will not get completed on schedule.
- Completion due date – When is the project to be completed? After lining out the volume of work to be audited, and the productivity anticipated, it will be clear how many Auditors will be needed to complete the project on time.
- Cost/Budget - Estimated cost for such review can be made based upon the volume to be reviewed, divided by the estimated productivity, multiplied by the average cost per hour of the auditors. In estimating cost, also include costs of individuals who run reports, perform quality reviews, organize and prepare final reports of findings, and presenting or education to staff.
- Scaling of Project – Depending on the budget, scaling of the project may be in order. Rescoping of volumes to review would be the initial area to analyze.
Project Build-Up Phase: In this phase, the Audit Team is assembled, approach and timelines are solidified.
- Assemble Audit Team: It is important that the Auditors are the right fit for the review. Having Coding Auditors that are experienced and credentialed will ensure they have top notch knowledge and skills to perform the review. Depending on the size of the Team, quality control must be considered, and who will perform these quality reviews. Additionally, Team oversight and management must be considered as well.
- Audit Approach: A thorough, and well thought out audit approach is also critical to the success of a review. Below are the steps to ensure a successful review:
- Patient/Chart to Review: To identify patients/charts to be included in a review, a comprehensive report typically can be created by Information Technology. This report will show the entire universe of claims or patients enrolled in a given timeframe. From this report, patients/charts can be selected to be reviewed (or a sampling can be selected for the review).
- Review Tools: Review tools or software are critical to the capture and storage of review results. Software or technology can be used to gather data, but also, a simple excel report can be utilized.
- Anticipated Final reports: What does leadership or the stakeholders want to see in the final reports. Be sure the information wanted in final reports is extracted during the review process and in the capture of results.
- Patient Records: To perform all coding related risk adjustment reviews, access to patient record is necessary. If within the organization – access to records can be done via electronic access (assuming the organization has an Electronic Health Record). If records are from entities outside of the organization, that is a bit more tricky as request for records will be required. Access for auditors will need to be performed, and/or copies of records requested.
- Coding Review Instructions/Guidelines: Even if there are experienced and credentialed auditors, detailed written instructions are important to have in place. Also written coding guidelines, specific to the organization are critically important. There are many gray areas in coding – an organizations interpretation and stance on these issues is important for consistent coding review results.
- Project Timelines: Timelines, mid-point completion goals and completion goals are all important to have delineated. To know an end date or completion goal is key to staffing (you will hire more/less auditors depending on the timeline). The timeline ties in with the budget. Typically, a review with a shorter timeline (with large volume) will be a higher rate per chart than a longer timeline (due to potential of required overtime to hit goals).
Project Implementation Phase: Starting the reviews, ensuring quality, and staying on target.
- Starting the Reviews: We have lined up the Team, delineated the scope of the review, lined out the review approach and guidelines (as well as other necessary items). We are now ready to start the Review. All reviews must start with initial orientation and training of auditors to assure all are prepared to start the review and perform work consistently. Work should be distributed based upon expected productivity.
- Ensuring Quality: Quality Control (reviews) of audits performed should be done at initiation of work, and then on a regular basis. No auditors will consistently perform at 100%, a threshold of 95% is acceptable and sustainable. Quality Control logs should be maintained on each Auditor and plans in place for staff that fall below 95% (audit, educate, reaudit, etc.). Weekly reminders on quality matters supports a quality program. Weekly or regular meetings with the Audit Team also contributes to improved overall quality and cohesiveness of the Audit Team.
- Staying on Target: Completing the Review on time is very important for many factors. Leadership expectations of results, and reprocessing or submitting of data are the two major factors for completing reviews/audits on time. Below are some best practices to ensure on-time completion:
- Team Oversight – A Project Manager will be assigned for overall Project success. A “Team Lead” should be appointed that will monitor individual daily productivity (to ensure individuals hit expectations), individual quality review scores (to ensure individuals are performing at 95% or higher quality level). This can be one individual or multiple “Team Leads” depending on the size of the project. This individual will work with the Project Manager to solve problems related to quality and/or productivity.
- Weekly Progress Reports (or Monthly) – Progress Reports showing various key performance indicators (KPI) are a quick snapshot as to where the Review is at, at any given time. Examples of items to be included are as follows:
- Number of Charts/Patients TOTAL to be Reviewed =
- Number of Charts/Patients Review Completed=
- Number of Charts/Patients Not Reviewed =
- Percentage Review Completed =
- Overall Quality Score =
- Overall Productivity =
- Productivity Goal =
- Estimated Cost to date =
- Original Cost to date =
- Over/under Budget =
- Estimated Completion Date =
- Original Completion Date Goal =
- Narrative addressing over/under budget; areas of concerns, issues encountered etc.
Project Completion & Closing Phase: Completing a project correctly, and tying up loose ends, evaluating the project, and lessons learned are useful for moving forward and will benefit future projects.
- Completing a Project: It is important, once a project is complete, to perform various quality checks of final reports assuring that all data abstracted is in a format requested, and consistently noted. Summary Reports should be gathered to give all high level statistics, and data which can be impactful across the organization, including educational information as desired. Patient records should be organized and stored in a retrievable format. If this data will be given to another organization or department, orientation to the reporting and formats is encouraged.
- Evaluating the Project: At the conclusion of the project, the Stakeholders and other key players, should be engaged to evaluate the overall success of the Project. This should be an objective look at the project in the early conception stages, through to the completion of the project. Constructive criticism should be welcomed, as well as analyzing shortfalls, and issues or challenges that were encountered.
- Lessons Learned: At conclusion of the project, and preferably after the “Evaluating the Project” has been completed. The Project Manager and the Team Leads should convene to review the entire project to decipher “Lessons Learned”. Thee lessons learned should outline the issues encountered and how best to avoid in the future. This is a pure “how can we do this better next time” endeavor, not a negative experience.
Benjamin Franklin once said “If you fail to plan, you are planning to fail!”. And Project Management is all about planning. In Risk Adjustment reviews – Having a project management plan in place is key to success. From the delineation of the goals of the review, to scope of the review, to having the appropriate staff, to assuring Auditor staff are provided tools needed to perform reviews, and down to the final reports, all are necessary for the project to be successful.
Leave a Reply
Your email address will not be published. Required fields are marked *