---
title: "$16M+ in Medicaid Revenue Recovered | Smart Data"
url: https://www.smartdata.net/case-studies/nfloc-platform-rewrite
description: "Hired for a Medicaid code update, Smart Data spotted a nursing facility file process losing revenue. $16M+ was recovered and the process rewritten."
source: "Smart Data (smartdata.net). Markdown copy of the page; the HTML page is canonical."
---

# A routine Medicaid code update that surfaced $16M+ in lost revenue

Hired to add a state-mandated code to a health plan’s nursing facility file, our team noticed the process was mishandling records. The plan confirmed it, filed corrections with the state and recovered $16M+. We then rewrote the process to stop the loss.

Built on SQL Server

Industry

Healthcare

Engagement

Custom Development

A Medicaid health plan brought Smart Data in for a narrow job: update its Nursing Facility Level of Care (NFLOC) historic file process to handle a new retroactive code from the Ohio Department of Medicaid. That process sends nursing facility records for the plan’s members to the state, and what reaches the state shapes what the plan is paid.

While making the change, our team noticed records that did not add up. The process was mishandling some cases, and we believed it had been costing the plan revenue for some time. We said so.

## The challenge

The file had been running for years, and nothing flagged the problem because nothing was technically failing. Records went out, some came back rejected and the gaps stayed quiet.

- Records went to the state for members who were not eligible on the dates that mattered, so the state rejected them
- Duplicate records with missing admission dates were sent again and again
- Updates and deletes for members the state had no record of were resent on every file, and rejected every time

## The solution

- A small Smart Data team, a developer and a business analyst with senior technical oversight, reviewed and reconciled the historical file
- We showed the health plan where the process was mishandling records and why it was likely losing revenue
- The plan’s own analysis confirmed it, and it sent adjusting files to the state
- The plan then brought Smart Data back for an initial rewrite of the process in SQL Server, to stop the ongoing loss

## The results

**$16M+**in lost revenue returned to the health plan

Eligibility is checked against each member’s threshold and discharge dates before a record goes to the state

Duplicate records with missing admission dates are removed before the file is sent

Records the state has rejected as having nothing to update are no longer resent

Client

Healthcare Insurance

Platform and technology

- SQL Server

## Working on something similar?

Tell us what you are building and what it has to connect to. Here is what happens after you reach out.

### A short call about the work

What runs today, what needs to change and the date you are working toward.

### An engineer looks at what’s running

Scope comes from your systems as they are, before anything is priced.

### You get a written proposal

Covering scope, team, approach and price.

[info@smartdata.net](mailto:info@smartdata.net) [(937) 886-9166](tel:+19378869166)