Brian Truax Open to new roles

Builds · X-Ray Mobile Texas · 2026

Claims bridge, no more retyping.

The billing team stopped retyping claims. About $160K a month of insurance, Medicare and Medicaid claims now move from the imaging system into AdvancedMD through its API, checked line by line, from a review page I designed for them.

Revenue cycle · AdvancedMD API · EDI

~$160KClaims moving into billing each month
2.5 hrs → 20 minOne batch, hand-keyed vs. the bridge
38 of 38Bad subscriber records caught before any claim went out
0Claims sent without a person approving them

The problem

Every claim was keyed into AdvancedMD by hand from the order and imaging system. One batch of about 73 lines took roughly two and a half hours, and every retyped field was a chance for a denial.

Rather than pay for a custom integration, I built the bridge from data the company already exported every night.

What I built

A bridge that reads that nightly export, turns each completed order into a validated charge, and posts claims into AdvancedMD through its API.

  • On real data, 98% of completed orders (158 of 161) validated into a clean billable charge on the first proof run
  • A procedure-code master of 115 clean codes covering 99.7% of exams, built from more than 44,000 archived exams
  • After posting, every line is read back from AdvancedMD: line count, fee, and subscriber details

The review page

The part that matters most is the page the billing specialist works from. I rewrote it around how the specialist reads a batch, with plain statuses: Will post, Needs your OK, Skipped, Cannot post, Needs a check.

An approval is tied to the exact version of the batch the specialist saw. If anything changes, the page asks for a reload before approving. Nothing goes to a payer without a person approving it.

What it caught

  • Read-back found 38 of 38 charts carrying a wrong subscriber sex and no date of birth. They were repaired the same day, and none were transmitted.
  • Claims missing a member ID went from 0 of 13 to 13 of 13 complete before the first live batch
  • Claims resolving a carrier and fee schedule went from 0 of 22 to 22 of 22

Results

The first production batch posted 24 of 24 claims. The next posted 12 claims in about five minutes with zero defects and nothing left stranded.

How I built it

With my agentic team: a spec first, tests that check business outcomes, and a human review before release. An adversarial review before go-live took the suite from 63 to 1,491 passing tests and caught a deploy-blocker that would have taken billing down on day one. HIPAA is part of the design: patient data minimized, access role-based at the API layer, and a person reviews before anything goes live.

One of six systems I built at X-Ray Mobile Texas, my family's mobile diagnostics company, during its turnaround. Shared with the owners' permission; patient, staff, client and vendor details are withheld. More operational case studies from my practice are at actional.us.