SERVICES · LAS VEGAS NV

Charles Trinh — Claims Pipeline Build | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Charles Trinh — Claims Pipeline Build, Las Vegas NV
Charles Trinh — Claims Pipeline Build

Building a claims pipeline end to end: enrolment inventory, submission, acknowledgement triage, remittance posting, and the four numbers that prove the pipeline actually works.

Instrument before you optimise

A pipeline is only as good as its observability, and the observability is four counts: submitted, acknowledged, accepted and paid. Anything less is a file transfer with optimism attached, because the only feedback loop is cash arriving weeks later.

Build the counters before the optimisation work. They will find more defects in a fortnight than a code review finds in a quarter, and they cost a day.

Enrolment is inventory

Maintain effective date, last-verified date and the payer-assigned provider identifier for every provider-payer pair. Those three fields turn an unpredictable rejection stream into a list you can work through on a schedule.

Reconcile the inventory against eligibility responses quarterly, because enrolments lapse silently and the resulting denials point at the provider rather than the paperwork.

Triage by class, route by owner

Envelope, credential and business rejections have different owners and different clocks. A queue sorted by arrival date mixes them, so the items that cannot be resolved in that room sit in front of the ones that can.

Track median time to close per class rather than total volume, because total volume invites arguments about severity while per-class times tell you where the process actually stalls.

Posting and reconciliation

Post remittance weekly against expected amounts. Posting errors are silent: a denial attached to the wrong encounter is worked twice, and the real denial is never worked at all.

Audit the CARC and RARC mapping quarterly against actual 835s, since the mapping is usually maintained by one person, undocumented, and never reviewed.

The enrolment inventory is the foundation

Most claim rejections that look like software defects are enrolment problems wearing a technical costume. The payer does not recognise the provider identifier, or recognises it under a different TIN, or has the group affiliation recorded differently from the clearinghouse, and the rejection arrives with a code that sends the ticket to the wrong team. Build the inventory first: provider, payer, effective date, last verified date, payer-assigned identifier, and the person who verified it, per pair, and reconcile it quarterly against eligibility responses.

The reconciliation is where the inventory earns its cost, because it catches the pairs that have drifted apart between verification cycles. Where a pair has lapsed, the correct response is to stop submitting for it and fix the enrolment, not to resubmit into a rejection loop. A pipeline that treats enrolment state as a first-class input avoids the most expensive class of rework, which is work performed on claims that could never have been paid.

Acknowledgement triage by class

Envelope rejections, credential rejections and business rejections belong in different queues with different clocks and different owners. An envelope rejection is usually a configuration or transport fault and is fixed once; a business rejection is a claim content problem owned by coding or billing; a credential rejection is an enrolment problem that blocks everything for that pair. Sorting by arrival date mixes all three, and the predictable outcome is that the queue's oldest items are the ones nobody can fix and the newest are the ones that could have been resolved in an hour.

Route by class, measure by class, and report median time to close per class rather than the total volume. Total volume invites an argument about severity; per-class times show where the process is stuck and who is holding it. The report should name the owner of each class, because a queue without an owner is a list of things that will be discussed at the next meeting rather than worked today.

Posting, reconciliation and the denial that gets lost

Post the remittance weekly and reconcile it against the expected set, because posting errors are silent and expensive. A denial attached to the wrong encounter is worked twice, and the encounter it should have been attached to is never worked at all, which means the organisation pays the cost of the work and the cost of the missed appeal. The reconciliation that catches this compares three things: what was submitted, what was adjudicated and what was posted, per encounter.

Where the three disagree, the disagreement is a work item with an owner rather than a variance to be explained at month end. The most common cause is a patient identifier that resolved differently at each step, which is the same identity problem that affects every other integration in the estate, and it is worth fixing once at the source rather than repeatedly at the report.

The numbers that prove it works

Four counts describe the pipeline: submitted, acknowledged, accepted and paid, with the difference between each pair attributed to a cause. Those four are enough to find the leak in a week, and they are the only numbers a finance owner will actually use. Everything else, including volumes and average values, is context around them.

Trend median time from submission to payment per payer, because that number captures the combined effect of every other defect and it moves when something changes. A payer whose median jumps is a payer whose rules changed, and the trend is the earliest warning you will get. Compare it against the contracted expectation rather than against last month, since last month may itself have been slow.

Where the pipeline meets identity

Most reconciliation failures at posting time trace back to an identity decision made at submission. The patient reference, the member identifier and the encounter number have to agree across three systems, and when one of them resolves differently the claim is posted to the wrong place. Fixing that at the identity layer is a project; catching it at posting is a queue. Decide which one the organisation is funding, because the queue is the expensive option and it is the default.

Where a member identifier changes mid-month, which happens at plan changes and at re-enrolment, the pipeline has to carry the history rather than overwrite it. An identifier overwritten in place makes the earlier claims unattributable, and the reconciliation then fails for claims that were perfectly correct when they were submitted.

The clearinghouse relationship

The clearinghouse is a router, and its reports describe what it sent rather than what was paid. Reading the contract in those terms decides what you can delegate and what you cannot, and reconciliation is the part that cannot be delegated because its question is about money. Ask for the change history quarterly, since payer lists and format support move without notice and the notice is the thing you need.

Exception handling as a measured process

Every queue is an exception process, and the measurement that matters is the median time an item sits before somebody works it. Total volume invites arguments; median age shows whether the process is keeping up. Report it weekly per class with the owner named, and treat a rising median as an early warning rather than a reportable number.

Working the queue

A claims queue is worked in one direction, oldest first, per class, with a time box per item. The box exists because the expensive failures are the ones that consume an afternoon without resolution, and the discipline of stopping after twenty minutes and routing the item upward is what keeps the median age down. Where an item repeatedly exceeds the box, the pattern is a defect rather than a difficult claim, and it belongs in a finding rather than in the queue.

Record the disposition for every item, including the ones resolved without action. The dispositions are the data that tells you which rules are producing noise, and a queue where nothing is ever closed as no-action is a queue that is not being read carefully.

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

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.

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 — claims pipeline build — 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.

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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh