278 request · certification · 72-hour clock

Charles Trinh — X12 278 Prior Authorisation | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading X12 278 — prior authorisation with a clock and a record the claim can read
Charles Trinh — X12 278 Prior Authorisation

What the 278 is, and what it is not

The X12 005010 278 Health Care Services Review is a structured request for a determination about whether a payer will cover a service, paired with a structured response that carries the decision. It is not a fax alternative and it is not a portal convenience. It is a transaction with a request, a response, an authorisation number, and a decision a provider can act on before care is delivered.

It still matters in a world of FHIR prior authorisation APIs because the 278 is what the installed base speaks. CMS-0057-F requires a FHIR-based exchange and does not retire the 278 on the payer side. For most organisations the realistic architecture for the next several years is hybrid: FHIR for new integrations, 278 for the clearinghouse and payer connections that already exist and will keep existing.

The request, field by field

A 278 request carries the subscriber and the patient, the requesting provider, the rendering and service facility, the service type and procedure codes, the diagnosis, the requested dates or units, and whatever certification or attachment the payer requires. The response carries an authorisation or certification number, a decision code, and — the part organisations under-read — reason codes that explain the decision and define the appeal path.

Two fields are systematically mishandled. The service type code drives which rule set the payer applies, and a request submitted under the wrong type is evaluated against the wrong policy and denied for a reason that has nothing to do with the patient. The certification type code distinguishes an initial request from an extension or a concurrent review, and confusing them produces a duplicate determination or a coverage gap at the boundary between two admissions.

The inquiry is where tracking gets exposed

The 278 also supports an inquiry: a provider asking the status of an open request. That inquiry is where most revenue cycle teams discover their authorisation tracking is a spreadsheet, because the payer's answer and their own record disagree and nobody can say which is authoritative. The payer's answer is authoritative. Your record should reconcile to it daily, not when a claim denies.

Why implementations fail at the authorisation number

A 278 response returning an authorisation number is not resolution. The number has to reach the claim. If the 278 lives in one system and the 837 is built in another, the authorisation number becomes a value that must be carried, validated, and matched — and when it is not, the claim denies for a reason that takes three weeks to diagnose, because the denial code points at the claim and the cause is upstream.

The fix is unglamorous: treat the authorisation number as a first-class field on the encounter, populate it the moment the response arrives, and validate its presence before the 837 leaves. A claim submitted without an authorisation that was required is a denial you manufactured, and it is indistinguishable in the reporting from a payer error unless you validate at submission.

Attachment handling is where the useful hours go

Clinical documentation supporting a request travels as an attachment, and attachment handling is the least standardised part of the transaction. Some payers accept a 275 with embedded documentation. Some require a portal upload. Some require fax. Some require different paths for different service categories on the same payer.

Enumerate the requirement per payer and per service category, write it into a table, and route mechanically. Organisations that assume a single attachment path discover the variance per payer, per denial, at volume — and each discovery costs a resubmission cycle measured in days, occasionally past the clinical window in which the service was still appropriate.

The tracking problem is a state machine

Prior authorisation is a state machine with deadlines. Submitted, pending, pended for information, approved, partially approved, denied, appealed. Each state has an owner and the appealing states have a clock.

A request that sits in pend-for-information past its window is a denial created by inattention, and it is the most common source of avoidable prior authorisation denials I see. Track the state, the clock, and the owner for every open request, and escalate on the clock rather than on the calendar. The 278 inquiry exists so you can ask without a phone call — use it, and log the answer, because the log is the only evidence you will have when a payer asserts a different timeline.

Rejection taxonomy, so you route to the right team

Envelope. The interchange was malformed — a 999 with an error. Your EDI team, fixed in hours.

Credential. The payer does not recognise the submitter, the provider, or the enrolment for that service. Fixable, but on the payer's timeline, measured in weeks.

Business. The 278 was accepted and the determination is a denial on clinical or policy grounds. Fixable only with the documentation and the appeal path, which is a different department entirely.

Conflating the three is why prior authorisation work queues grow without resolving: each class has a different owner and a different clock, and a queue sorted by arrival date mixes them.

Where the 278 stops and FHIR begins

The 278 has no native representation for a machine-readable coverage requirement, which CRD solves. It has no questionnaire mechanism, which DTR solves. It has no structured denial vocabulary a provider system can act on automatically, which PAS solves.

So the hybrid is a division of labour rather than a compromise: the 278 keeps the clearinghouse rail running, and the FHIR guides progressively take the parts of the workflow where structure buys something. Build the seam deliberately, keep one canonical representation of an authorisation inside your own system, and translate outward to both.

Las Vegas, specifically

For plans operating here — Health Plan of Nevada among them — verification practice varies by payer ID, by product line, and by delegated reviewer. Some categories route through a delegated entity whose rules differ from the parent plan's published policy, and a request validated against the published rules can still be denied by the delegate.

The local work is enumeration: which payer, which product, which delegate, which service categories, which attachment path, and which turnaround is actually observed as opposed to published. I build that as a table first and a test second, because a prior authorisation process that has never been tested against real responses is a description of intent.

How to measure whether it works

Four numbers, weekly. Requests submitted. Requests approved without a pend. Pends resolved inside the window. Denials decomposed by class. An organisation that can produce those four can find its own leak; one that cannot is managing by denial volume, which tells you the outcome and nothing about the cause.

What I do about it

I design and build the integration between the clinical workflow and the 278 exchange — the state machine, the authorisation capture, the attachment routing, and the tracking that closes the loop to the 837. I have operated eight X12 005010 transaction sets across 104 clearinghouse enrolments in 53 jurisdictions, and run the ONC (g)(10) suite to 317 of 317 subtests, so the FHIR half of the hybrid is not a separate conversation.

If your prior authorisation denials are a number you cannot decompose by category, that is the first thing I look at, and it usually takes a week.

What changes when the payer is also the pharmacy benefit manager

Some plans administer both lines, and the authorisation for a drug can sit with the pharmacy benefit while the authorisation for the office visit sits with the medical benefit. The same patient, the same day, two determinations, two numbers, and two systems that do not know about each other.

For the practice, that means a 278 that returns an approval for the administration can still leave the medication unpaid, because the drug was adjudicated on a different rail entirely. The denial that follows cites a benefit determination and reads like a clinical denial, and the team working it routes it to utilisation management where nobody has the pharmacy contract in front of them.

The fix is structural rather than procedural: maintain a mapping from service category to benefit line to authorisation channel, and validate at scheduling time that every line requiring a determination has one. A patient arriving for an infusion with the facility approved and the drug unapproved is a same-day cancellation, and it is discoverable a week earlier by a single check.

Where the plan delegates one line and retains the other, the mapping needs a delegate column for the same reason it needs one everywhere else. Two payers in the same organisation, applying different criteria to the same episode, is not an unusual arrangement; it is the common one in markets with vertically integrated plans.

The contract clause that decides who pays for the denial

Most payer contracts contain a clause about timely authorisation, and most provider organisations have never read it in the context of their own process failures. The clause usually says the payer will not pay for services that required authorisation and did not receive it, and it is written to survive the argument that the request was submitted and simply not answered.

The practical consequence is that a request lost in a pend-for-information state is not a payer failure you can appeal. It is your failure, and the evidence that would win the argument is the inquiry log showing you chased it, which most organisations do not keep because the inquiry was made by telephone.

So the contract makes the logging mandatory rather than optional. Every inquiry, timestamped, with the payer's response, attached to the authorisation record. It costs an interface and a table, and it converts an unwinnable dispute into a documented one.

What the weekly report should say

A one-page report, produced every Monday, with four rows and one column of owners. Requests submitted, requests approved without a pend, pends resolved inside the window, and denials decomposed by class. Each row carries the name of the person who owns that class of failure.

The value is not the numbers. It is that the report cannot be produced without a state machine that records state, clock and owner per request, so the act of producing it builds the mechanism. Organisations that cannot produce it are, by definition, not tracking.

Circulate it to the three owners rather than to a steering group. The steering group will discuss it; the owners will fix it, and the disagreements that surface between them are where the handoffs actually break.

Review the owner column quarterly rather than annually. The person who owned credential rejections in January is not always the person who owns them in July, and an owner column that has not been checked is a name that redirects a question nobody answers.

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 278 prior authorisation — 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