104 enrolments · 53 jurisdictions · one pipeline
Charles Trinh — Revenue Cycle | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

The revenue cycle is the path from a scheduled appointment to a settled balance. Every step on that path has an owner, a measure and a failure mode, and most organisations can name the steps but not the owners.
What this is
The cycle begins before the encounter. Eligibility, prior authorisation and patient responsibility estimation all happen before the service, and each one determines whether the claim will pay. A revenue cycle that begins at claim submission has already lost most of the money it will spend the rest of the cycle chasing.
The middle of the cycle is claim generation and submission. Coding accuracy, charge capture and the claim build determine whether the claim is clean, and a clean claim rate below ninety-five percent is a signal that something upstream is broken rather than that the billing team is slow.
The back of the cycle is adjudication and posting. Remittance processing, denial management and patient billing all live here, and the measure that matters is days in accounts receivable rather than the denial rate alone. A denial rate that looks stable while AR days climb is a cycle that is quietly failing.
The fourth element is the patient. Patient responsibility has grown as a share of revenue, and a cycle that treats the patient as an afterthought produces statements nobody understands and calls nobody can answer. Estimating responsibility before the service and explaining it afterwards is the cheapest improvement available.
Finally, the cycle is a data problem. Every step produces data that can be used to improve the step before it. Denial reasons feed coding, coding feeds documentation, documentation feeds scheduling. An organisation that does not close that loop is paying for the same lesson repeatedly.
Denial management deserves its own treatment because it is where most cycles leak. A denial is not a billing event; it is a signal about an upstream step. A denial for missing authorisation points at scheduling, a denial for coding points at documentation, a denial for eligibility points at registration. Categorising denials by cause and routing each category to the step that caused it is what turns denial management from a cost centre into a feedback loop.
Underpayment is the quieter leak. A claim that pays less than the contracted rate is not a denial and does not appear in denial reports, but it is money lost. Comparing allowed amounts to the fee schedule is a simple join and it is the audit that pays for itself fastest.
Charge capture is the third leak. A service rendered and not charged is revenue that never enters the cycle, and it is invisible because nothing fails. Periodic reconciliation between the clinical record and the charge record is the only way to find it.
Finally, the cycle has a cash-flow dimension that is separate from its accuracy. A perfectly accurate cycle that takes ninety days to collect is a cycle that is financing the payer. Measuring days in AR by payer and by service line is what makes the cash conversation concrete.
There is also a staffing dimension that is easy to miss. A cycle that depends on experienced people remembering exceptions is a cycle that degrades when they leave. Documenting the exceptions, and automating the ones that recur, is what converts institutional knowledge into a system property rather than a personnel dependency.
The final consideration is the relationship between the revenue cycle and the clinical workflow. Every improvement that requires a clinician to do something different will be adopted slowly unless it saves them time. Designing the front of the cycle so that it reduces clinical friction, rather than adding a step, is what makes the improvement stick.
A last point on measurement: the cycle should be measured by outcome rather than by activity. Claims submitted is an activity; clean claim rate is an outcome. Denials worked is an activity; denial rate by cause is an outcome. Choosing outcome measures is what prevents a team from being busy while the cycle deteriorates.
How I do it
I begin by mapping the cycle end to end with an owner and a measure per step. That map is usually the first time anyone has seen the whole path, and the gaps in ownership are the first finding.
From there I measure the front of the cycle: eligibility coverage, authorisation capture and estimate accuracy. Improvements here reduce work everywhere downstream.
Claim generation is measured by clean claim rate and by the reasons for the unclean ones, with the reasons fed back to the step that caused them rather than to the billing team.
Adjudication is measured by AR days and by denial category, with each category assigned to an owner who can change the upstream cause.
Finally, the patient-facing layer is designed with the same care as the payer-facing one, because an unexplained balance is a collection problem and an explained one is usually not.
Denials are categorised by cause and routed to the step that caused them, with a named owner per category and a measure of whether the cause is falling.
Underpayments are identified by comparing allowed amounts to the contracted fee schedule, with the comparison run on a schedule rather than as a one-off audit.
Charge capture is reconciled against the clinical record periodically, so services rendered and not charged are found rather than assumed absent.
Days in AR is measured by payer and by service line, so the cash conversation is about specific relationships rather than an aggregate.
Recurring exceptions are documented and then automated in order of frequency, so the cycle depends less on individual memory each quarter rather than more.
Front-of-cycle changes are designed with the clinical workflow rather than around it, and measured by whether they reduce work at the point of care as well as improving the claim.
The handover is the cycle map with owners and measures, the denial category report, the underpayment audit and the AR view. Those four artefacts let an operations lead see where the money is stuck without asking anyone, which is the difference between a managed cycle and a monitored one.
Outcome measures are reviewed monthly with the owners of the steps they describe, so a deteriorating measure produces a conversation with the right person rather than a report nobody reads.
Artifacts you keep
- An end-to-end cycle map with an owner and a measure per step
- Front-of-cycle measures for eligibility, authorisation and estimate accuracy
- Clean claim rate with reasons fed back to the causing step
- AR days and denial categories with an owner per category
- A patient-facing explanation designed alongside the payer-facing one
Proof
- 104 clearinghouse enrolments across 53 jurisdictions
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 104 clearinghouse enrolments across 53 jurisdictions
- 67 public hostnames, 51 serving, one AWS account
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
The chain, and where it breaks
Eligibility before the visit, authorisation where required, the claim after it, the acknowledgement, the remittance, the appeal. Each link has a standard format and a standard failure mode, and the failures are not distributed evenly — most of the money is lost at two of them.
The first is eligibility. A visit against inactive coverage produces a claim that will be denied for reasons unrelated to care, and the denial arrives after the service. The second is the acknowledgement, because a claim that was never accepted never becomes a denial and never appears in a denial report.
Both share a property that makes them expensive: the failure is silent at the point it occurs and loud only at remittance, by which time the correction window is narrower and the patient has already been seen.
Instrument the chain link by link
For a single day's volume, count encounters that produced claims, claims transmitted, claims acknowledged, claims accepted, payments posted and denials with a reason. Refresh weekly. The link with the largest unaccounted difference is the one to fix, and it is usually not the one the team believes.
Decompose denials by cause rather than by count. Contractual, eligibility, authorisation, coding, timely filing, patient responsibility. Each has a different owner, a different fix, and a different prevention point, and a single denial number mixes all six into a figure nobody can act on.
Track the proportion of denials whose cause was knowable before submission. That share is preventable work, and it is almost always larger than expected because nobody had separated the categories before.
Prevention beats appeals
An appeal costs the work of the appeal plus the delay in the cash. A preventive check costs a rule. The economics are so one-sided that the only reason prevention is neglected is that appeals are visible and prevention is not.
The three checks with the highest return: coverage verified within a day of the visit, authorisation tracked to expiry with the number attached to the encounter, and the claim validated against the payer's published edits before transmission.
Each of those is a small piece of engineering in front of a large class of denials, and each produces a number that can be reported to the person who owns the denial rate.
What to measure and report
Cash posted within thirty days of service, by payer, against the contracted expectation. Days in A/R by payer. Denial rate decomposed by cause. Clean-claim rate before transmission, not after adjudication.
Four numbers, weekly, with the same definitions every week. An organisation that can produce them can find its own leak; one that cannot is managing by the number that gets reported upward, which is always the one least useful for action.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — revenue cycle — the scope, the failure modes it prevents and how the work is measured. It sits in the X12 and EDI category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.