REGULATORY

Charles Trinh — Prior Authorization API under CMS-0057-F | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Sequence diagram showing a provider submitting a prior authorisation to a payer through a FHIR interface
Charles Trinh — Prior Authorization API under CMS-0057-F

CMS-0057-F requires payers to expose prior authorisation through a FHIR API and to answer inside stated timeframes. The deadline is public. Whether the API answers within them is the engineering problem.

The rule describes behaviour under load, not a feature list

CMS-0057-F asks payers to implement four related interfaces: patient access, provider access, payer-to-payer and the prior authorisation interface. The prior authorisation interface is the most operationally demanding because it sits on a provider's revenue cycle. A late response is a call from a surgical coordinator, and a series of late responses is a series of calls. I treat the rule as a service level description rather than a conformance checklist, because that is how providers experience it.

The obligation includes timelines for urgent and non-urgent decisions, transparency about the criteria behind a decision, and a means for a provider to see where a request has reached. Each part has an engineering equivalent. Criteria transparency becomes a service that returns the rule that applied; status visibility becomes a tracking resource with predictable outcomes; timeframes become a clock attached to each request from the moment it arrives.

I start a delivery programme with the operational map: which requests, from which provider types, at which volumes, and with what medical-necessity complexity. That map determines whether the implementation can afford a human in the loop on every request or needs automated traversal of the criteria for a substantial share.

The status resource is the provider's view of the payer

A provider's first contact with a pending authorisation is usually a status query. The status resource is therefore the first place providers form an opinion. If it returns pending when the case has been denied for a day, the provider will call. If it returns approved before the reviewer has signed off, the provider will schedule the case and the call comes a week later. Both are symptoms of a status model that is looser than the actual process.

I model the status against the internal workflow before building the endpoint. The workflow has states: received, validated, in medical review, approved, denied, pended for more information. The endpoint should map them, and it should tell the provider what the next action is, including what additional configuration or attachments are needed. The response should also be timestamped so that the provider can measure turnaround rather than infer it.

Where the provider is referred to a portal, I check that the portal displays the same status as the API. Divergent status between the two is worse than no API, because it undermines trust in both.

Automated decisions need a defensible rule path

A portion of prior authorisations can be settled automatically, based on the criteria and on data the provider already sent. Automating those cases is the difference between meeting the deadlines and missing them, especially for routine volumes. However, an automated decision that cannot be explained to the provider, or to an appeal, is a compliance risk. I design the automated path so that every decision writes the rule that fired, the data it evaluated, and the version of the rule set.

The rule set changes over time. I version it explicitly and attach the version to every decision. When a provider appeals, the appeal can be resolved by re-reading the rule version in force at the time, and by assessing whether the data was correct. Without versioned rules, appeals turn into archaeology.

The same design makes it possible to assess the automated path for bias, for drift from the clinical policy, and for the share of cases it settles versus escalates. Those measurements belong in a quarterly report rather than a launch checklist.

Da Vinci profiles accelerate the build and fix the meaning

The rule names the FHIR standards expected, and the Da Vinci implementation guides supply the profiles, the exchange pattern and the examples that make the interface unambiguous. Using them removes the argument about field names and about how a request should be presented. The guides also anticipate the usual complications, such as attachments, extensions for the provider's requested urgency, and the linkage between the authorisation and the eventual claim.

The profiles do not supply the business logic. I spend the early design time sorting workflow variation from canonical shape, because a payer with fifteen lines of business may have fifteen criteria sets behind one interface. Canonicalising those into a single decisioning service is a governance project as much as a software one. It involves medical policy, compliance, and the operations teams who currently interpret the criteria by hand.

I document the deviations from the guide, with reasons. Deviations are acceptable when required, but they must be visible to the receiving partners and to the audit trail. A silent deviation turns into an escalation.

Timeframes have to be measured by someone who can see both ends

The regulation sets timeframes within which prior authorisation decisions must be provided. Meeting them is only provable if the clock is captured at both ends: when the provider submitted and when the decision was issued. Many payers can report internal state, but cannot state reliably when the request was received, because the request may pass through a clearinghouse, a portal proxy and an intake service before reaching the decisioning system.

I instrument the pipeline to capture the receipt event and the decision event, and I keep them in a measurement store independent of the case management system. The report shows the distribution of turnaround at the percentile level, including the tail. Paying attention to the average, which is often comfortable, hides the urgent cases that make providers angry and the large cases that make them escalate.

I also measure the split between automated and manual decisions, because the mix changes behaviour. Automated decisions are usually fast. If the automated share falls after a rule update, complaints rise, and the measurement makes that visible before the complaint volume does.

Interoperability and the revenue cycle meet in the claim

The prior authorisation interface is useless in isolation. The authorisation obtained through it has to be reflected in the claim, and a mismatch between them is a denial waiting to happen. I map the identifier and the details of the authorisation through to the claim submission path, and I design a test that submits a claim for each authorisation class and confirms that it processes without a mismatch. This is where the API meets the organisations responsible for the X12 005010 transaction sets.

I make the mapping a shared artefact between the API team, the claims team and the revenue cycle team, and I require the same test to be run by each. That artefact is where most of the coordination cost in a CMS-0057-F programme lives. When it is missing, the API team ships conformant interfaces and the revenue cycle team sees denials in the weeks after.

Providers rely on the prior authorisation interface, but payers' revenue is affected by the claim outcome. Connecting the two is the difference between a compliant interface and a useful one.

Public tracking and communication keep programmes on schedule

The rule includes transparency obligations: payers publish data on their prior authorisation activity, including volumes and decisions. Preparing that data is not an afterthought. The same measurement pipeline that reports turnaround can produce the public dataset, provided the metric definitions are aligned, and misalignment produces figures that contradict the internal reports.

I define the public metrics next to the internal ones, with a single set of definitions. The result is one measurement system with two outputs. Reviewers can then trust that the internal figures and the public figures are describing the same thing, which is the outcome most payers want when they publish first and explain later.

The delivery programme keeps the operational map alive as well. Volumes, provider mix and decision mix change, and each change is a trigger to revisit the automation share and the staffing model.

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 — prior authorization api under cms-0057-f — the scope, the failure modes it prevents and how the work is measured. It sits in the Interoperability 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