While most changes involve Responsible Reporting Entity (“RRE”) requirements, some of those changes will have a trickle down effect on plaintiffs, their Medicare liens, and plaintiffs’ attorneys. For example, on page six of the User Guide it states,
The requirements for reporting ICD-9 diagnosis codes in Section 11.2.5 were updated to clarify that ICD-9 diagnosis codes submitted should be those that reflect the illnesses/injuries claimed and/or released by the settlement, judgment, award, or for which ORM is assumed.
This language is somewhat concerning. Consider that most complaints will list every body part as a potential injury. At the same time, most settlements are limited in language discussing the injuries. So what happens when the RRE reports everything in the complaint, yet the case was really regarding just one, limited injury? Obviously, lien resolution gets more difficult.
First, report the case on your own, prior to the RRE reporting and as soon as possible. We recommend reporting the day you file a case. You should do so even earlier if you suspect a pre-suit settlement. This allows you to inform Medicare of its lien on your own terms. The Medicare lien will then be based on the injuries you report.
Second, work with the defense attorney. As plaintiff’s attorney, you can give the defense ICD-9 codes in advance so that their client, the insurance company and thus the RRE includes only those relevant codes. Additionally, you can include the relevant ICD-9 codes in the settlement release.
These ideas are simply suggestions based on theory. No one is sure how Medicare will react to the influx of information it will receive beginning January 1, 2011. If Medicare does claim excessive liens on your clients’ cases LRS is here to help. We dispute, appeal, compromise, and use any other Medicare lien negotiation tactics to successfully reduce your Medicare liens.
Contact us for assistance.Ryan J. Weiner Co-Founder Lien Resolution Services www.lienresolutionusa.com https://lienblog.wordpress.com firstname.lastname@example.org