On March 20, 2013 the Supreme Court released its decision in Wos v. EMA, a federal case determining the legality of North Carolina’s Medicaid recovery statute. The Court held that the anti-lien provision of the federal Medicaid Act prevents a state from taking any portion of a judgment or settlement not designated as medical care.
More simply, Medicaid can only recover for the portion of the settlement that represents medical bills.
North Carolina’s statute stated that it could recover for Medicaid payments up to one-third the total amount of settlement. The Court ruled that this statute is preempted by the federal anti-lien provision because it permits the state to “take a portion of a Medicaid beneficiary’s tort judgment or settlement not designated for medical care. The Court continued by noting North Carolina’s statute failed to provide a scheme for determining if the one-third is a reasonable limit.
This decision has both positive and negative effects for Medicaid lien resolution. The positive is that it provides more mechanisms for reducing Medicaid liens. Unfortunately, those mechanisms may be more costly than simply applying a formula such as North Carolina’s now illegal one-third maximum. The negatives continue where, in some cases, it might be possible for Medicaid to now take more than one-third of the settlement.
In order to take full advantage of Wos v. EMA you should consult a Medicaid lien specialist and work with Medicaid representatives throughout the settlement process. Always be sure to “show your work” in calculating settlements.
The negatives of this decision will only apply where you fail to account for Medicaid’s reimbursement in your settlement preparations.
If you need help with any type of lien resolution we can assist you with Medicare lien resolution, Medicaid lien resolution, ERISA liens, private insurance liens, and more. We’ll take care of getting you the “lien” and reducing it too.Ryan J. Weiner Lien Resolution Services www.lienresolutionusa.com https://lienblog.wordpress.com email@example.com