Tuesday, July 19, 2016

Encounter Data Filtering Logic Updates

As you probably know, CMS has provided guidance regarding the filtering of encounter data for risk adjustment purposes.  This doesn't mean that either Medical Groups or Health Plans should not submit certain encounters- CMS requires that ALL encounter data must be submitted to them.

Currently, encounter data represents 25% of the calculation of risk scores.  CMS plans to increase the weighting of encounter data-based risk scores over the next couple of years by moving to a risk score incorporating 50% of the encounter data/FFS-based risk score in 2018, a risk score incorporating 75% of the encounter data/FFS-based risk score for 2019, and a risk score of 100% encounter data/FFS-based risk score in 2020,

The logic that they use to determine what encounters are included is laid out in this 2015 memo from CMS to health plans.  At the same time, CMS released a list of procedure codes that would be used for filtering professional and outpatient hospital encounters.  

Recently, CMS released the list of 2015 codes and preliminary 2016 codes to be used for encounter data filtering.

When determining which encounters may be used in calculating risk scores, health plans and provider groups should refer to these documents, as well as reports received from CMS and health plans.  As CMS moves forward with using only encounter data for risk score calculation it will become more important than ever that your encounter data be accepted by the health plan and ultimately by CMS.  We will continue to provide you as much information as possible on our Encounter Data/ICD-10 Page.  CMS is currently hosting teleconferences with health plans, to keep them informed about changes to encounter data processing.  We'll post webinar slides like these, on duplicate record and demographic data fields processing, so you can stay up to date as well.

What other tools would be helpful to you?  Remember, if you have suggestions for HCC University, or the blog, you can contact us at coding@scanhealthplan.com.

No comments:

Post a Comment