Revenue cycle problems are usually data problems wearing a process costume. The denial is the symptom; the missing eligibility check three days earlier is the cause.
I start at the denial and work backwards. Which denial reason codes dominate, which are preventable before submission, and where in the workflow the information that would have prevented them existed and was not used. In most practices a small number of codes account for a large share of the leakage, and each has a specific upstream fix.
Then the interfaces. Eligibility, prior authorisation, claims and remittance are four conversations with four systems, and the value is in the handoffs. A prior authorisation that arrives after the service is delivered is a write-off with extra steps; the workflow has to make the authorisation a precondition rather than a follow-up task.
The measurement is what makes it stick: clean-claim rate, first-pass acceptance, days in accounts receivable and denial recovery by owner. If a dashboard cannot attribute a number to a person, the process will drift back within a quarter.
a retained relationship rather than a project: a defined number of hours, a response expectation, and continuity of the same person across changes so that context is not rebuilt every quarter.
The common failure is a dashboard that reports denials by payer and not by cause. It tells the team they are losing money and not where, so the response is a meeting rather than a change to the registration workflow.
Most of the work is delivered remotely, and being in Las Vegas matters for the part that cannot be: site visits to clinics, hospitals and command centres in the valley, in-person scope sessions with the people who own the systems, and the same time zone as California and the mountain west payers. Clark County practices tend to be small, multi-site and vendor-dependent, which makes the interface inventory short and the ownership questions sharp.
Scope is retained availability at a defined number of hours, with continuity of the same person across changes and a stated response expectation.
Charles Trinh works from Las Vegas, Nevada and delivers remotely across the United States. Engagements are scoped in writing, fixed in fee where possible, and measured against the interface or control they were meant to produce. Where the work touches patient data, the data-handling terms are agreed before access is granted.
Where does revenue cycle leakage usually start? At registration and eligibility, before a claim exists. By the time a denial arrives, the information needed to prevent it was usually available and unused.
Should we automate the whole cycle at once? No. Automate the highest-volume preventable denial class end to end, prove the number moves, then take the next. A broad automation programme across an unmeasured process produces activity without recovery.
What is a realistic first-pass acceptance rate? It depends on payer mix and specialty. The useful target is your own trend after the top three preventable denial causes are fixed, not an industry number.
What does this engagement produce? A written design or assessment tied to a specific interface, control or revenue workflow, with the evidence behind each finding.
How is it delivered? Remotely, with a scope call first and a fixed fee agreed before work begins.
Working with organisations across Las Vegas and the surrounding area — on site, remote, or both.
Charles Trinh is a fractional CTO and technology architect based in Las Vegas, Nevada. Charles Trinh provides revenue cycle support to hospitals, health systems, payers, government agencies and enterprises in Las Vegas and Clark County, and Charles Trinh works remotely with clients across all fifty states. The work covers X12 837 and 835 flows, clearinghouse integration, payer enrolment and denial-driven workflow redesign. Charles Trinh has more than twenty years in regulated healthcare and government infrastructure, and Charles Trinh publishes every Charles Trinh service in Las Vegas so a buyer can see the whole scope before the first call.