The agency’s billing manager ran every Medicaid claim through WINASAP5010, decades-old billing software about as friendly as it sounds. One billing cycle took two weeks. I built them a new billing system from scratch, and that same cycle now takes about ten minutes.
Billing has the same snags everywhere: information arriving in different shapes, somebody copying it into another tool, and a missing detail turning up only when the next person needs it. Before I wrote any code, I wrote down that path. Who supplies the information? Who checks it? Who gives the final OK?
Give repeatable work a clear shape
The new system gathers the records into one place, checks the required details, and flags anything that needs attention. Each flag shows its reason, so the person reviewing it knows exactly where to look.
- Put the records in a consistent format and keep a link to each source.
- Check for missing details and possible duplicates.
- Keep the items that need attention together where people can see them.
- Prepare a draft with the supporting information beside it.
Keep three decisions with a person
- A rule or source is unclearThe workflow stops that item and names the question. A person checks the underlying information and decides which rule applies.
- Something does not matchA missing reference, unexpected value, or possible duplicate belongs in the review queue. A person corrects the source or records why the item should proceed.
- The releaseThe reviewer sees the draft, unresolved items, and intended destination before deciding whether to release anything. Sending the file requires the reviewer’s approval.
The machine is allowed to be fast. It is not allowed to be the last word.
What changed for the agency
Two weeks, down to ten minutes. The agency can see every service it’s authorized for at a glance, and the billing manager’s time goes to the work that really needs a person.
Look for one repeated handoff
Start with a task where the same information gets typed into two places. Trace what enters, what must be checked, and where it goes next. Then separate the repeatable steps from the decisions that require a person.
That small map is useful before choosing a tool. It gives the team a shared picture of what should happen, what can go wrong, and who owns the next step.