270 request · 271 response · real-time
Charles Trinh — X12 270/271 Eligibility | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

The 270 asks whether a patient is covered on a date. The 271 answers with a benefit structure that is richer, and more frequently misread, than most systems that consume it.
What this is
A 270 eligibility inquiry carries a subscriber, a patient, a service type code and a date of service. The 271 response returns coverage status, and then a benefit segment for each benefit the payer chooses to describe: deductible, co-insurance, co-payment, out-of-pocket maximum, remaining amounts, and the in-network or out-of-network context for each.
The first mistake is asking the wrong question. A 270 sent with a generic service type returns a generic answer. A 270 sent with the specific service type the patient is actually presenting for returns the benefit that applies to that service. The difference between those two responses is often the difference between a quoted patient responsibility of forty dollars and four hundred.
The second mistake is treating the 271 as authoritative for the date of service. Eligibility is checked at scheduling and the patient arrives weeks later, possibly after a plan change. A 271 that is not re-checked on the day of service is a historical document, and quoting from it produces the balance surprises that generate complaints.
The third mistake is ignoring the coverage-level detail. A patient may have primary coverage through a commercial plan and secondary through Medicare, or be a dependent on one plan and a subscriber on another. The 271 describes one payer's view. Coordination of benefits requires assembling several 271s and knowing the order, and a system that reads only the first response will bill the wrong payer first.
Finally, the 271 is verbose and the useful part is small. A response can run to hundreds of segments, most of which describe benefits irrelevant to the encounter. The engineering problem is not parsing it but selecting from it, and that selection has to be driven by the service being rendered rather than by whatever the payer happened to return first.
There is also a timing dimension that the standard does not address. Payers differ in how current their eligibility data is: some reflect a termination on the same day, others lag by a billing cycle. A response that says active is therefore a statement about the payer's record, not about the patient's coverage, and the difference matters most in the cases where it is most expensive.
Finally, the 271 is not a price quote. It describes benefits, not allowed amounts. A patient responsibility estimate built from a 271 alone will be wrong whenever the contracted rate differs from billed charges, which is almost always. The estimate needs the fee schedule and the claim history as well, and a system that presents a 271-derived number as a quote is setting up a conversation nobody wants to have at the front desk.
The most common failure is quoting from a stale response. Eligibility checked at scheduling and not re-checked on the day of service produces a patient responsibility figure that is wrong by the time the patient arrives, and the conversation at the front desk is the cost.
A second failure is reading only the first response. Where coordination of benefits applies, the first payer queried is not necessarily the primary, and a claim sent to the wrong payer first costs a full adjudication cycle before it is redirected.
A third is treating the 271 as a price. Benefits are not allowed amounts, and an estimate built from benefits alone will be wrong whenever the contracted rate differs from charges. The estimate needs the fee schedule as well.
One further consideration is worth stating plainly: eligibility is a conversation with the patient as much as a transaction with the payer. The 271 tells the organisation what the plan says; the patient tells the organisation what they understand their plan to be. Where those two disagree, the disagreement is resolved before the service rather than after the statement, and the eligibility check is the moment that conversation becomes possible.
How I do it
I start with the encounter types the organisation actually bills and the service type codes that map to each. That mapping is the core artefact, because it determines which question gets asked and therefore which answer comes back.
From there I build the inquiry so it always carries a specific service type, a specific date of service and the strongest patient identifier available. Responses are stored raw and parsed into a normalised benefit structure that separates in-network from out-of-network and remaining from total amounts.
Re-checking is built in rather than remembered. The eligibility check runs at scheduling and again on the day of service, and a change between the two raises a task rather than silently overwriting the earlier answer.
Coordination of benefits is handled explicitly. Where multiple payers are known, the system queries each and records the order, so the claim goes to the right primary payer with the right secondary information attached.
Testing uses captured real 271 responses across payers, because the variation between payers is far greater than the standard suggests and no sandbox reproduces it.
Where the organisation quotes patient responsibility, I connect the eligibility result to the contracted rate and to prior claim history for the same service, so the number presented is an estimate with a stated basis rather than a benefit maximum read aloud.
The handover includes a payer behaviour log: which payers return which segments, which ones require a specific service type to return anything useful, and which ones lag on terminations. That log is accumulated knowledge that no standard document contains.
The measure of an eligibility build is the number of balance surprises at the front desk, and the honest target is a small, explainable number. That is achievable when the right question is asked, the answer is re-checked on the day of service, coordination of benefits is resolved explicitly and the estimate is built from the fee schedule rather than from benefits alone. The 271 is the input; the conversation with the patient is the output that matters.
The final point is about evidence. Every 271 received is a record of what the payer said on a date, and retaining the raw response alongside the parsed result is what allows the organisation to reconstruct a decision later. When a patient disputes a balance, the response from the day of service is the document that settles the question, and it exists only if someone chose to keep it.
Artifacts you keep
- A service-type-code map from encounter type to the question asked
- Normalised benefit structures separating in-network, out-of-network and remaining amounts
- Day-of-service re-check with a task raised on change
- Coordination of benefits ordering across multiple payers
- A captured-response test suite covering payer variation
Proof
- Eligibility handling built against real payer 271 responses 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
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 270/271 eligibility — 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.