trading partners · connectivity · reconciliation
Charles Trinh — Clearinghouse Integration | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A clearinghouse sits between a provider and its payers, translating, routing and acknowledging. Integrating with one is mostly about understanding what it does not do.
What this is
A clearinghouse accepts claims, validates them against payer rules, routes them, and returns acknowledgements and remittances. It also enrols providers, holds trading partner agreements, and provides a portal that becomes the de facto system of record for anything the integration does not cover.
The first problem is that a clearinghouse is not a payer. A claim accepted by the clearinghouse has been validated, not adjudicated. Teams that treat clearinghouse acceptance as success stop watching the claim, and the denial arrives weeks later with nobody tracking it.
The second is the acknowledgement chain. A clearinghouse returns its own acknowledgement, then the payer's 999, then the 277CA. Each has a different meaning and a different timing. A system that reads only the first will report success for claims that were rejected downstream.
The third is enrolment. A clearinghouse will not route to a payer until the provider is enrolled with both. The clearinghouse enrolment and the payer enrolment are separate tracks with separate lead times, and treating them as one is the most common cause of a delayed go-live.
The fourth is the portal. Anything done in the clearinghouse portal rather than through the API is invisible to the integration, and the two drift. Deciding which operations are API-only and which are portal-only, and documenting that boundary, is what keeps the integration authoritative.
Finally, a clearinghouse is a commercial relationship. Per-transaction pricing, contract terms and exit provisions determine how much of the architecture should depend on it. A design that cannot move to a direct connection is a design with a single point of commercial failure.
Validation is the clearinghouse's main value and its main source of confusion. A claim rejected at the clearinghouse has failed a rule the clearinghouse applies, which may be a payer rule, a clearinghouse rule or a standard rule. The rejection code usually says which, but not always, and a team that treats every rejection as a payer rejection will spend time on the wrong problem.
Reporting is the second value. A clearinghouse sees claims across payers, which means it can report on patterns a single provider cannot see. Using that reporting rather than only the transaction pipe is where a clearinghouse relationship earns its fee, and most organisations never open the reports.
The third is the data model. A clearinghouse holds its own identifiers for claims, providers and payers, and those identifiers are not the ones the organisation uses. A mapping between the two is required, and a system that assumes they are the same will lose the ability to reconcile.
Finally, the clearinghouse is a dependency with an availability profile. When it is down, claims do not flow, and the organisation needs a documented behaviour for that: queue locally, retry, and communicate. A dependency without a documented failure behaviour is an outage waiting for a trigger.
There is also a reconciliation question that sits between the clearinghouse and the payer. A claim can be accepted by the clearinghouse, acknowledged by the payer, and still never adjudicated. The only way to know is to track the claim to a remittance, and a system that stops at the acknowledgement will carry a growing population of claims whose fate is unknown. Tracking to remittance is the only state that means anything.
The final consideration is the relationship between the clearinghouse and the payer portals. Many payers expose their own portals for status, appeals and eligibility, and those portals hold information the clearinghouse does not. A revenue cycle that relies only on the clearinghouse will miss the payer-side detail, and a revenue cycle that relies only on portals will drown in manual work. The workable pattern is the clearinghouse for transactions and the portals for exceptions, with the boundary documented.
A last point on cost: per-transaction pricing means the volume of transactions is a budget line, and a design that sends unnecessary inquiries or duplicate claims is a design that costs money every day. Reviewing transaction volume against claim volume is a simple check that catches waste early.
How I do it
I start with the transaction inventory: which transactions go through the clearinghouse, which payers, which acknowledgements, and which operations still require the portal. That inventory defines the integration surface.
From there I build the acknowledgement chain as a single tracked state per claim, joining the clearinghouse acknowledgement, the payer 999 and the 277CA. A claim is not successful until the payer has acknowledged it, and the state machine reflects that.
Enrolment is tracked as two parallel tracks with their own lead times, and the go-live date is set by the later of the two rather than by the optimistic one.
The portal boundary is documented explicitly, with the operations that remain manual listed and owned, so the gap is visible rather than discovered.
Finally, the exit path is documented: what it would take to move a transaction to a direct connection, and what would have to change. That documentation is cheap and it changes the negotiating position.
Rejections are classified by source: standard, clearinghouse or payer. That classification determines who investigates, and it prevents the most common waste of time in a billing operation.
Clearinghouse reporting is reviewed on a schedule, with the patterns it reveals fed back into the claim build rather than left in a portal nobody opens.
Identifiers are mapped explicitly between the organisation and the clearinghouse, with the mapping maintained as part of the integration rather than reconstructed when a reconciliation fails.
A documented failure behaviour exists for clearinghouse unavailability: local queueing, retry policy and communication path, tested rather than assumed.
Every claim is tracked to a remittance rather than to an acknowledgement. A claim with no remittance after a defined period is escalated, because an acknowledged claim that never adjudicates is a silent loss.
The portal boundary is reviewed quarterly, because payers add and remove portal capabilities and the boundary that was right last year is rarely right this year.
The handover includes the transaction inventory, the acknowledgement state machine, the identifier mapping and the failure runbook. Those four artefacts let an operator answer what happened to a claim without calling the clearinghouse, which is the measure of a working integration.
Artifacts you keep
- A transaction inventory covering payers, acknowledgements and portal-only operations
- A single tracked state per claim joining clearinghouse and payer acknowledgements
- Parallel enrolment tracks with independent lead times
- A documented portal boundary with named owners for manual operations
- A documented exit path to direct connections
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 clearinghouse is a router, not a partner
A clearinghouse routes claims to payers, normalises some format differences, and returns acknowledgements and remittances. It does not adjudicate, it does not correct data, and its service levels cover transmission rather than payment. Organisations that assume otherwise discover the gap at month end, when the file moved successfully and the cash did not arrive.
Reading the contract in those terms is the first useful act. What is covered is the path from submission to the payer's door; what is not covered is anything that happens after, and the failure modes that matter live in the after.
The practical consequence is that reconciliation is your job and cannot be delegated, because the clearinghouse's report describes what it sent and your question is what got paid.
The four surfaces and their owners
Submission moves claims out and acknowledgements back. Retrieval pulls remittances and status responses. Configuration holds the payer list, routing rules and companion-guide variants. Reconciliation proves that what was sent matches what was acknowledged and what was paid.
Each surface needs a named owner and a metric. A retrieval job that silently stops looks exactly like a quiet week, and a routing rule pointed at the wrong payer identifier produces rejections that read like data errors.
When those four are owned separately, the failures localise. When they are owned by nobody, every incident begins with an hour of discovering who set up the connection.
The daily join nobody runs
Claims built, claims transmitted, claims acknowledged, claims paid. Four counts, joined on the claim identifier, refreshed daily. Every claim not in the expected state is a worklist entry with an owner, and the list is the operational heartbeat of the whole revenue cycle.
The join is where the clearinghouse stops being a black box. A claim that was built and never transmitted is a translator problem. Transmitted and never acknowledged is a routing or connectivity problem. Acknowledged and never paid is adjudication, and each of those three looks identical from a monthly report.
Run it before the payer's correction window closes, which is why daily matters and monthly does not.
Vendor change and the quiet drift
Clearinghouses change their payer lists, their supported formats and their retrieval cadence. None of those changes break your integration; all of them break your assumptions. A monthly diff of the payer list against the one you configured catches drift before it produces rejections.
Ask for the change history rather than the current state. A vendor that cannot produce a list of what changed in the last quarter is a vendor whose changes will arrive as rejections.
And keep the exit path: a claim pipeline that can be re-pointed at another clearinghouse within a week is a negotiating position, and one that cannot is a dependency priced by the counterparty.
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 — clearinghouse integration — 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
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
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.