x12 278 · prior authorization · tracking

Charles Trinh — X12 278 Prior Authorization

Charles Trinh — X12 278 Prior Authorization
Charles Trinh — X12 278 Prior Authorization

The transaction

A 278 is a structured request for a determination and a structured response carrying the decision, and it remains the rail the installed base actually speaks.

Two fields decide the outcome: the service type code, which selects the rule set applied, and the certification type code, which distinguishes an initial request from an extension.

Where it breaks

The authorisation number has to reach the claim. If the 278 lives in one system and the 837 is built in another, the denial that follows points at the claim while the cause is upstream.

Attachment routing is unstandardised across payers and service categories, and an unenumerated requirement is paid for in resubmission cycles.

Tracking and measurement

Prior authorisation is a state machine with clocks, not a spreadsheet with dates. A request pending for information past its window is a denial created by inattention.

Four numbers weekly: submitted, approved without a pend, pends inside the window, denials decomposed by class.

Las Vegas practice

Health Plan of Nevada among others varies by payer ID, product line and delegated reviewer, and a request validated against published policy can still be denied by the delegate.

I build the table first and the test second, because a prior authorisation process never tested against real responses is a description of intent.

The payer's side of a 278

A 278 is a request for a determination, and the determination is made by a reviewer applying a rule set that is only partly published. The service type code selects the rule set, which is why two requests that look identical to a clinician can be treated differently: one falls inside a code with an automated approval pathway and the other routes to a human. Understanding which codes route to which pathway, per payer, is the difference between a process with predictable turnaround and one that surprises the billing office every month.

The delegate adds a second layer. Where a payer delegates utilisation review, the delegate may apply its own policies and its own turnaround, and the request that was validated against the payer's published policy can still be denied by the delegate. Recording which payer, which product and which delegate handles each service category is the table that makes the process predictable, and building that table is the first task in any prior authorisation engagement.

Where the number gets lost

An authorisation number that never reaches the claim is the most expensive defect in the process, because it produces a denial that points at the claim while the cause is upstream. The 278 lives in one system, the 837 is built in another, and between them the number is either dropped or associated with a different encounter. The correction cycle costs more than the authorisation did, and the pattern repeats until somebody instruments the join.

The join worth building compares three things per encounter: whether an authorisation was required, whether one was obtained, and whether the claim that was submitted carried the number. Every case where the three disagree is a work item, and the count of them per week is the number that tells you whether the process is under control. It is a small piece of engineering in front of a large class of denials, and it is almost always absent.

Attachments and the unstandardised part

Attachment routing is where the standard stops helping. The 275 carries additional information, but how a payer wants it delivered, whether it must be associated with a specific request and what format is accepted vary by payer and by service category. An organisation that has not enumerated those requirements is paying for the gap in resubmission cycles, and the cost is hidden because each cycle is small.

Enumerate the requirements per payer and per service category, write them into the system that assembles the submission, and record the date each was confirmed. Where a payer changes its requirement, the change is then a data correction rather than an investigation, and the resubmission rate becomes a number you can watch rather than a pattern you notice.

Measurement that changes behaviour

Four numbers, weekly: requests submitted, requests approved without a pend, pends closed inside the payer's stated window, and denials decomposed by cause. Those four are enough to see whether the process is improving, and each has a different owner. A rising pend count is a submission quality problem; a rising denial count in one class is a rule change at the payer; a flat approval rate with rising volume is an eligibility or coding issue upstream.

Report them with the same definitions every week and keep the history. The value is in the trend rather than the value, because a process that is drifting and a process that is stable look identical in a single week and completely different across eight.

The FHIR layer arriving behind it

The standards work around prior authorisation has moved toward FHIR-based exchange: coverage requirements discovery, documentation templates and rules, and the prior authorisation API. Those guides are worth understanding because they change where the information lives and who asks for it, but they do not remove the 278 from the installed base, and a programme that assumes replacement will run two processes for years.

The practical position is to build the tracking state machine in a way that is independent of the transport, so that a 278 today and a FHIR exchange next year feed the same clocks and the same measurements. Organisations that tie the process to the transaction rebuild it when the transaction changes, which is exactly what is happening now.

The authorisation as a commitment

A pending authorisation is a commitment the organisation has made to a payer and a clinician has made to a patient, and the tracking exists to keep that commitment visible. A spreadsheet with dates does not carry the commitment; a state machine with clocks does, because it can tell you which requests are waiting on you rather than on the payer.

Build the clocks first. The categories that matter are waiting on us, waiting on the payer, waiting on the clinician, and expired, and every request is in exactly one of them at any moment. That single classification turns a list into a queue with owners, and it is the difference between managing prior authorisation and reporting on it.

Where the standard stops and the payer starts

The 278 defines the structure of a request and a response; it does not define what a payer will approve, how long it will take or what it will consider adequate documentation. Those are payer policies, and they are published unevenly. The practical response is a per-payer table that records the rule, the source and the date it was confirmed, because a rule recalled from memory and a rule read from a policy look identical until a denial arrives.

Where a payer publishes nothing, the table records that too, with the date of the request and the name of the person who asked. That record is what turns an undocumented rule into a known risk rather than an assumption, and it is what the organisation will wish it had when the denial is appealed.

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 authorization — 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