276 inquiry · 277 response · status categories

Charles Trinh — X12 276/277 Claim Status | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading X12 276/277 — claim status resolved by transaction, not by phone
Charles Trinh — X12 276/277 Claim Status

The 276 asks a payer what happened to a claim. The 277 answers. Between those two messages sits the entire status-tracking problem of a revenue cycle, and most organisations solve it by having someone call.

What this is

A 276 claim status inquiry names a claim — by payer claim control number, by patient and provider, or by the clearinghouse trace — and asks the payer to report its state. The 277 response returns a category code, a status code, and optionally the amount paid and the date. The pair is a query protocol, not a notification: nothing arrives unless someone asks, which is the first thing teams get wrong.

The status categories are coarse by design. A claim is accepted, pending, or finalised, and the detail lives in the status code beneath it. A team that reports on the category alone will see a claim sitting in pending for forty days and conclude the payer is slow, when the status code has been saying additional information requested since day nine and nobody read it.

The second trap is the trace number. A 276 sent without the payer's own claim identifier forces the payer to search, and a search that fails returns a status of not found that is indistinguishable from a claim that was never received. That ambiguity is where denials age. The correct design always carries the strongest identifier available and treats not found as a distinct outcome requiring its own follow-up path, not as a pending state.

Volume is the third problem. A hospital with sixty thousand open claims cannot send sixty thousand inquiries a day; payers rate-limit, and the clearinghouse charges per transaction. The workable pattern is a queue ordered by money at risk and age, with a per-payer concurrency cap and a backoff that respects the payer's own response time. That queue is a piece of software, and building it is cheaper than the phone calls it replaces.

Finally, the 277 is evidence. A status response with a timestamp is proof of what the payer knew and when, which matters in a timely-filing dispute. Storing the raw response alongside the parsed status turns a support conversation into a documented record.

The interaction with the 277CA matters here and is often missed. The 277CA acknowledges receipt of a claim; the 277 reports its adjudication state. They are different messages with different triggers, and a tracking system that conflates them will report a claim as acknowledged when it has actually been rejected at the front end. Keeping the two streams separate, and joining them only on the payer control number, is what makes the timeline trustworthy.

The most common operational failure is a tracking system that reports on the category and not the code. It looks healthy because most claims are finalised, and it hides the subset that is stuck. The fix is to report on the code, with the category as a grouping rather than as the unit of measurement.

A second failure is inquiry volume without prioritisation. Sending every open claim every day exhausts the payer's rate limit and the clearinghouse budget, and the claims that matter are buried in the queue behind the ones that do not. Ordering by expected recovery is what makes the volume affordable.

A third is the missing audit trail. When a payer asserts that an inquiry was never received, the only defence is the recorded request. Systems that log only the parsed result cannot produce that defence, and the dispute becomes a matter of recollection.

One further consideration is worth stating plainly: the 276 and 277 are only as good as the payer's willingness to answer them. Some payers respond fully, some respond with a category and nothing else, and some do not respond at all within a reasonable window. The design has to accommodate all three, which means a timeout is a state rather than an error, and a payer that never answers is escalated through a documented channel rather than retried indefinitely. Building that tolerance in from the start is what keeps the queue from becoming a source of noise.

How I do it

I begin by pulling the open claims and grouping them by payer and by the identifier each payer actually accepts. That grouping determines the inquiry strategy far more than any standard does, because a payer that only matches on its own control number cannot be queried until that number is known.

From there I build the inquiry queue with three properties: it orders by expected recovery, it caps concurrency per payer, and it records every request and response verbatim. The parser then maps status codes to an internal state machine with named owners, so a claim in additional information requested routes to the person who can supply the information rather than sitting in a report.

The state machine is the part that outlives the engagement. It is a document listing every status code the payers in scope actually return, what each one means operationally, who owns it, and what action clears it. Codes that appear in the standard but never in practice are listed as unused rather than omitted, so the next person knows the difference between not handled and not seen.

Testing follows the same discipline. The fixtures are captured real 277 responses, anonymised, covering the awkward cases: a claim found by trace but not by control number, a response with a category but no status code, a payer that returns the same claim twice with different states. The suite runs without a payer sandbox, which means it runs in CI on every change rather than on the day someone remembers to test.

Reporting is the last piece and the one that decides whether the work sticks. A weekly view of open claims by state, age and dollars, with the not-found bucket broken out separately, tells an operations lead where to put people. Without that view the queue is technically correct and organisationally invisible.

The measure of a status-tracking build is not how many inquiries it sends but how few phone calls the billing office makes. When the queue is ordered by money at risk, the state machine has named owners, and the raw responses are retained, the calls stop because the answers are already on a screen. That is the outcome worth scoping for, and it is achievable in weeks rather than quarters when the payer matrix is built first.

Artifacts you keep

  • A payer-by-payer matrix of accepted inquiry identifiers and rate limits
  • An inquiry queue ordered by money at risk, with per-payer concurrency caps
  • A status-code to internal-state map with a named owner per state
  • Raw 277 responses retained as timestamped evidence
  • A dashboard separating not found from pending from finalised
  • A captured-response test suite that runs without payer sandboxes

Proof

  • A 276/277 tracking layer built against real payer responses, not sandbox fixtures
  • 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

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 276/277 claim status — 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