837I · UB-04 · institutional claims

Charles Trinh — X12 837I Claims | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading X12 837I — institutional claims, revenue codes and cross-edits
Charles Trinh — X12 837I Claims

The 837I is the institutional claim: a hospital bill expressed as revenue codes, type of bill and a structure that assumes a facility rather than a clinician.

What this is

The 837I carries UB-04 data in X12 form. Where the professional claim describes services rendered by a provider, the institutional claim describes a stay or an encounter at a facility, organised by revenue code rather than by procedure code. The type of bill encodes the facility type, the care setting and the frequency of the claim, and it is the single field most often wrong.

The first trap is the type of bill. A three-digit code that says hospital inpatient, original claim, is different from one that says hospital outpatient, replacement. A claim submitted with the wrong frequency is either rejected or, worse, accepted and paid twice. The mapping from the organisation's own encounter types to the type of bill is a document that should exist and usually does not.

The second is revenue code granularity. A facility bills by revenue code, and the same service can be represented at different levels of detail. A payer that expects a specific granularity will reject a claim that is technically valid. The companion guide is the authority here, not the base implementation guide.

The third is the relationship between the institutional claim and the professional claim for the same encounter. A patient may generate both, and the two must agree on the diagnosis, the dates and the patient identity. A system that builds them independently will produce a pair that disagrees, and the disagreement surfaces as a denial on one side and a write-off on the other.

Finally, the 837I is where present-on-admission indicators, condition codes and occurrence spans live. These are not decoration: they determine payment under many payer rules, and a claim missing a present-on-admission indicator can be paid as a hospital-acquired condition rather than as a covered stay.

Diagnosis coding on the institutional claim has its own rules. The principal diagnosis drives the payment grouping, and the sequence of secondary diagnoses affects severity adjustment. A claim with the right codes in the wrong order is a claim that pays at the wrong rate, and the error is invisible unless someone compares the expected grouping to the actual payment.

Occurrence and value codes carry information that is easy to omit and expensive to omit. A value code that reports a covered charge, an occurrence code that reports a date, a condition code that reports a circumstance: each is a small field with a payment consequence. A claim builder that treats them as optional will produce claims that are valid and underpaid.

The relationship between the institutional claim and the remittance is also worth stating. The 835 for an institutional claim reports payment at the claim level and at the revenue code level, and a reconciliation that only looks at the claim level will miss line-level denials that are buried inside a paid claim. Reading the remittance at the same granularity the claim was submitted is what makes the reconciliation meaningful.

Finally, the institutional claim is where the coordination of benefits information lives. Whether the payer is primary, secondary or tertiary, and what the prior payer paid, determines the expected payment. A claim that omits that information will be adjudicated as primary and paid at the wrong rate, and the correction is a replacement claim rather than an adjustment.

A final consideration is the audit trail. An institutional claim is a financial assertion about a stay, and the record that supports it is the medical record. When a payer audits, the question is whether the claim matches the documentation, and a claim builder that cannot trace each line back to a source record is a claim builder that cannot support an audit. Building that trace at generation time is far cheaper than reconstructing it later.

The last point is about volume. An institutional claim is generated per encounter, and a hospital generates them continuously. A claim builder that requires manual intervention on a meaningful fraction of encounters is a staffing problem disguised as a technical one. Automating the common case completely, and routing only the genuinely ambiguous cases to a person, is what makes the volume manageable.

How I do it

I start with the type-of-bill matrix: every encounter type the organisation produces, mapped to the correct type of bill and frequency code, reviewed against each payer companion guide. That matrix is the first artefact and it prevents the most expensive class of error.

From there I build the claim so that the institutional and professional sides are generated from the same encounter record, with shared diagnosis, dates and patient identity. Agreement is enforced by construction rather than by reconciliation.

Revenue code granularity is set per payer from the companion guide, with the deviations recorded. A claim that fails on granularity is a configuration change rather than a code change.

Present-on-admission, condition codes and occurrence spans are validated before submission, with the payer rules that depend on them documented alongside.

Testing uses captured real claims and the payer rejections they produced, so the suite covers the cases that actually occur rather than the cases the standard describes.

Diagnosis sequencing is validated against the payer rules before submission, with the principal diagnosis and the severity-relevant secondaries checked explicitly rather than left to the coder.

Occurrence, value and condition codes are treated as required where the payer rules require them, with the rules documented per payer rather than assumed from the standard.

Reconciliation reads the 835 at revenue code granularity, so a line-level denial inside a paid claim is visible rather than averaged away.

Coordination of benefits information is carried on the claim where a prior payer exists, with the prior payment amount included so the payer adjudicates in the right position.

Each claim line carries a reference to the source record that supports it, so an audit can follow the claim back to the documentation rather than starting from the chart and working forward.

The handover includes the type-of-bill matrix, the per-payer revenue code configuration, the validation rules and the reconciliation report. Those four artefacts let a billing team diagnose a rejection without escalating to engineering, which is the difference between a system that is operated and one that is maintained.

Artifacts you keep

  • A type-of-bill matrix mapping every encounter type to the correct code and frequency
  • Institutional and professional claims generated from one encounter record
  • Per-payer revenue code granularity from the companion guide
  • Validation of present-on-admission, condition and occurrence data
  • A captured-claim test suite built from real payer rejections

Proof

  • X12 005010 institutional claims 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

Institutional claims fail on codes, not on amounts

A facility claim is a description of an encounter as much as a bill: what type of bill it is, which departments provided care and under which revenue codes, what conditions applied, and what happened during the stay that the payer should know about before paying. The dollar figures follow from those, and the rejections cluster there too.

The type of bill is the first thing to get right and the first thing to go wrong. It encodes both the facility type and the frequency of the bill, so a corrected claim submitted with the original frequency indicator arrives as a duplicate, and a duplicate denial points at the claim number rather than at the indicator that caused it.

Revenue codes are the second. A code that does not map to the billed procedure makes the line unpriceable, and an unpriceable line produces an adjudication that stalls rather than fails — which is worse, because nothing appears in a rejection report and the claim simply sits.

The codes nobody's system captures

Condition and occurrence codes are required for specific services, and they are almost never captured by the system that builds the claim. They live in the clinical record, in a case management note, or in the head of the coder who knows that a particular payer expects them for a particular procedure.

That knowledge leaves with the coder. What retains it is a rule: this service type, this payer, these codes required, checked before submission. The rule is cheap to write and it converts a class of denial from invisible to prevented.

The diagnosis related group is the third layer. Whether the group is computed by the provider or the payer changes what the claim must contain, and a claim that omits an expected group produces adjudication that is slow rather than wrong. Slow is harder to find, because it is not an error, it is a queue.

Cross-edits belong before submission

The facility claim and the professional claims for the same encounter will be cross-edited by the payer on patient, dates and diagnosis. A mismatch produces a denial on one side that the other side cannot explain, and the correction cycle restarts the clock on both.

Running the cross-edit before transmission is a pair comparison rather than a claim review: same patient, same dates, diagnosis consistent, the facility and the physicians describing the same encounter. When they disagree, the claim not sent is always cheaper than the denial produced.

The same applies to the payer's own edit set. Most payers publish enough of their logic to test against, and the ones that do not publish it are the ones where a test submission in a sandbox pays for itself within a week.

What to measure

Institutional volume is lower than professional volume and each claim is worth more, so a percentage rate hides the money. Measure rejection rate by type of bill, by payer and by revenue code family, and weight each by the average allowed amount for that family.

The number that changes behaviour is the share of rejections caused by a code the organisation could have validated before submission. That share is not a payer problem, and reporting it separately is what moves it from a monthly argument into a build ticket.

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 — x12 837i claims — 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