837 · 835 · 270/271 · 278 · 277CA · 999

Charles Trinh — X12 EDI | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading 837 · 835 · 278 — claims in both directions
Charles Trinh — X12 EDI

X12 EDI is the language of the American revenue cycle. It is also a family of standards that share a syntax and almost nothing else, which is why so many integrations fail at the seams between transactions rather than inside any one of them.

What this is

The 837 claims, the 835 remittance, the 270 and 271 eligibility pair, the 276 and 277 status pair, the 278 prior authorisation, and the 999 and 277CA acknowledgements are separate implementation guides over a common envelope. They share delimiters, control segments and a loop structure. They do not share semantics, error handling or versioning behaviour, and treating them as one protocol is the root of most integration debt.

The envelope is where the first real decisions live. ISA and GS control numbers, the interchange and group structure, and the acknowledgement chain determine whether a trading partner can tell what you sent and whether it arrived. A partner that receives a file and cannot reconcile it against an acknowledgement will call, and the call is the cost of a design that ignored the envelope.

Version drift is the second problem. A payer on 005010X222A1 and a clearinghouse on a later erratum will disagree about a segment that looks identical in both documents. The disagreement surfaces as a rejection with a code that points at the segment rather than at the version, and the fix is a version matrix rather than a code change.

Character encoding and delimiters are the third. A file that uses a non-standard element separator, or that carries a character in a name field which collides with a delimiter, will fail at the partner's parser before any business rule is evaluated. Validation at the point of generation is cheaper than diagnosis at the point of rejection.

Finally, EDI is a contract surface. The companion guide a payer publishes is the actual specification, and it routinely narrows or contradicts the base implementation guide. Reading the companion guide before writing the mapper is the single highest-return hour in any EDI project.

There is a commercial dimension too. Clearinghouses price per transaction and per enrolment, and the routing decision — direct to payer or through a clearinghouse — changes both cost and control. Direct connections give visibility and remove a margin, but they multiply the number of trading partner relationships to maintain. Most organisations end up with a hybrid, and the architecture has to support both without duplicating the mapper layer.

Finally, EDI is where audit lives. The 835 is the record of what was paid and why, the 837 is the record of what was claimed, and the acknowledgements are the record of what was received. An organisation that cannot reconstruct that chain for a given claim on a given date has an audit problem regardless of how well its integrations run day to day.

The most common failure is a mapper written against the base implementation guide rather than the partner's companion guide. The base guide is a starting point; the companion guide is the specification, and the deviations are where every rejection lives.

A second failure is unhandled acknowledgements. A file that is sent and never reconciled against its 999 is a file whose fate is unknown, and the organisation discovers the gap when a payer asserts non-receipt weeks later.

A third is version drift across partners. A single mapper serving partners on different errata will produce rejections that look like content errors and are actually version errors. The version matrix is what makes the difference visible.

One further consideration is worth stating plainly: EDI work is judged by the trading partners, not by the codebase. A mapper that is elegant and a partner that cannot reconcile the file is a failed integration. Designing to the partner's companion guide, closing the acknowledgement loop and keeping the version matrix current are unglamorous and they are what the partner experiences. That is the standard the work should be held to.

How I do it

I begin with the trading partner inventory: which transactions, which versions, which companion guides, which acknowledgement expectations, and who is called when a file fails. That inventory is the specification the project actually runs on.

From there I build a shared envelope layer that handles control numbers, acknowledgements and reconciliation once, so each transaction mapper only has to deal with its own business content. That separation is what keeps a fifth transaction from costing as much as the first four combined.

Each mapper is written against the partner's companion guide, with the deviations from the base guide recorded explicitly. Those records become the test cases, because the deviations are where the failures happen.

Validation runs at generation, not at rejection. Delimiters, encoding, required segments and version-specific rules are checked before the file leaves, and a file that fails validation is not sent.

Finally, the acknowledgement chain is closed. Every 999 and 277CA is parsed, matched to the file it acknowledges, and surfaced as a status, so the organisation knows what arrived rather than assuming it did.

Where both direct and clearinghouse routes exist, the routing decision is made per transaction and per payer in configuration rather than in code, so a change of route does not require a release.

The handover includes the partner inventory, the companion guide deviations, the routing configuration and the acknowledgement reconciliation report. Together those four artefacts let a new engineer answer the question of what happened to a specific claim without asking anyone.

The measure of an EDI build is the proportion of files whose fate is known without asking anyone. When the envelope layer handles acknowledgements once, the mappers are written against companion guides, validation runs at generation and the acknowledgement chain is closed, that proportion approaches all of them. The transactions are the visible part; the reconciliation is what makes them trustworthy.

The final point is about evidence. Every file sent, every acknowledgement received and every rejection recorded forms a chain that can be reconstructed for any claim on any date. Organisations that retain that chain resolve disputes in hours; organisations that do not resolve them by recollection. The retention decision is cheap and the absence of it is expensive.

Artifacts you keep

  • A trading partner inventory with versions, companion guides and escalation contacts
  • A shared envelope layer handling control numbers and acknowledgements once
  • Per-transaction mappers with recorded deviations from the base guide
  • Generation-time validation for delimiters, encoding and required segments
  • A closed acknowledgement chain linking every 999 and 277CA to its file

Proof

  • X12 005010 transactions built across 104 clearinghouse enrolments
  • 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

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

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 — x12 edi — 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.

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