CMS-0057-F · January 1, 2027
Charles Trinh — CMS-0057-F | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

The deadlines are the least interesting part
CMS-0057-F is discussed as a compliance calendar. It is not one. It is four API obligations with four different commercial consequences, and the operative question for a payer is not when but which of these changes how we operate.
Patient access, provider access, payer-to-payer exchange, and prior authorisation. The first three are data-movement problems an organisation of any competence can solve with money and time. The fourth changes how a health plan runs its clinical review operation, and that is where programmes fail.
Patient access: the member is the client
The least controversial and the most frequently under-built. The trap is implementing it as a claims export behind a login. The expectation is a member-facing surface a third-party application can consume without a bespoke integration — SMART on FHIR authorisation, a real consent decision by the member, and a token model that holds up under audit.
Members do not care that you shipped an endpoint. They care that their app of choice can read it without calling support.
Provider access: attribution is the project
You cannot serve a provider-facing API if you cannot resolve which provider is asking and which members they are entitled to see. An NPI is an identifier, not an authorisation model. Groups, delegations, locums, and the change on the first of the month all need handling, effective-dated.
Build the entitlement check as its own service with its own tests before touching the data layer. Every plan I have worked with has an attribution table that is correct on paper and wrong in practice by several percent, and that percentage is where the support tickets originate.
Payer-to-payer: the obligation with no commercial analogue
A member moves from plan A to plan B, and plan B must be able to request that member's data, with authorisation, and plan A must serve it. Three things make it different. It is peer-to-peer, so your counterparty's quality becomes your defect rate. It is consent-gated per member, so the authorisation artefact matters as much as the data. And it is bidirectional — every plan is requester and responder, and most plans build the requester and stub the responder.
The failure I see repeatedly: a beautiful request flow and a responder that returns a 200 with an empty bundle because the member-match step silently found nothing and nobody logged it. Log your match failures. They are the only evidence you will have when a member says their history did not transfer.
Prior authorisation: where the rule stops being plumbing
A documented list of covered items requiring authorisation, an advertised turnaround for each, and a FHIR exchange supporting the full decision lifecycle including denial and appeal.
The operational consequence is that medical necessity criteria have to be machine-readable enough to populate a ClaimResponse with a decision and a reason. Most plans have criteria in a document management system and a reviewer's head. Neither is an API.
Scope it honestly: pick the ten highest-volume service categories, build those completely — criteria, decision, denial reason, appeal path — and be explicit that the rest are in progress. Ten categories that work beat a hundred that return pending review.
What a readiness programme contains
A conformance map — every required capability, its profile, its state, its owner, its gap. Not a RAG status; a profile-by-profile mapping against the actual implementation guides.
A data lineage view — which source system feeds which profile element, transformed how, refreshed when. An element you cannot trace is an element that will be wrong and you will not know why.
An attribution and consent service, separately owned and tested, with its own runbook.
A counterparty register for payer-to-payer: which plans, which contacts, which known quirks, and the date of the last successful end-to-end test with each.
A public disclosure surface naming which items require authorisation and your turnaround times. That page is a compliance artefact, not marketing.
Where I start
With the conformance map and a live trace of one member through all four APIs. One member, end to end, timestamps on every hop. It takes a week and it tells you more than a quarter of steering meetings, because the failure is almost never in the code. It is in the entitlement check, the attribution table, or the match that returned nothing and logged nothing.
What I do
I have run the ONC (g)(10) Standardized API suite to 317 of 317 subtests against a platform I built, and operated eight X12 005010 transaction sets across 104 clearinghouse enrolments in 53 jurisdictions. I know what the last five percent of these integrations feels like, which is the part that decides the timeline nobody believes.
If your conformance map exists and your member journey has never been traced, that trace is the first thing I would run.
Payer-to-payer: the details that decide whether it works
The obligation is stated simply — a member moves from plan A to plan B, and plan B can request that member's data with the member's authorisation, and plan A must serve it. The implementation is four separate problems that most programmes discover in the wrong order.
Member matching across plans. Plan B knows the member by its own identifier. Plan A knows them by a different one. Between them sits a demographic match that fails silently and returns an empty bundle with a 200 status. Every payer-to-payer programme I have seen has this failure in the first month and almost none of them logged it, which means the member experience is indistinguishable from a plan that never received their history.
The authorisation artefact. The request is consent-gated, and the consent is the member's, held by the requesting plan. The responder must be able to verify that the authorisation is real, current, and covers the data requested. Most implementations verify existence rather than scope, which means a request for the full record passes on an authorisation the member granted for a narrower purpose.
The responder. Every plan builds the requester and stubs the responder, because the requester is the visible half. A responder that returns an empty bundle, or times out, or returns data without the provenance the requester needs, is the reason peer-to-peer programmes stall. Build the responder first and test it against a real counterparty before building the requester at all.
The counterparty register. Which plans you exchange with, their technical contacts, their known quirks, and the date of the last successful end-to-end test with each. Without this the programme's actual coverage is unknown, and "we support payer-to-payer" becomes a claim that cannot be defended under questioning.
Prior authorisation readiness, operationally
The rule requires a documented list of items and services requiring authorisation, an advertised turnaround for each, and a FHIR exchange supporting the decision lifecycle including denial and appeal. The compliance artefacts are straightforward. The operational change is not.
Medical necessity criteria have to become machine-readable enough to populate a ClaimResponse with a decision and a structured reason. Most plans hold criteria in a document management system and in a reviewer's judgement. Neither is an API. Converting them is a clinical-operations project with a technical surface, and it is the item that consumes the budget nobody allocated.
Scope it in categories. Pick the ten highest-volume service categories, build those completely — criteria, questionnaire, decision, denial reason, appeal path — and be explicit in the public disclosure about which categories are live and which are in progress. Ten categories that return a real decision beat a hundred that return pending review, and the disclosure surface is what makes the honest scoping defensible.
The evidence pack a regulator or auditor will ask for
Four artefacts, each of which should exist before it is requested. A conformance map at profile granularity with owners and dates. A member journey trace from registration through patient access, provider access and payer-to-payer, with timestamps. A counterparty register with test dates. And an availability record, measured externally, because an internal dashboard showing 100% while a certificate expiry took the surface down is a record that damages rather than helps you.
The question that separates a prepared programme from a rehearsed one: can you produce the trace of one member through all four APIs within a day, without contacting anyone who built it?
Timeline discipline
Work backwards from the deadline, and the deadlines have already started arriving. The sequence that works: conformance map in month one, entitlement and consent service in months two and three, patient and provider access live in months three to five, payer-to-payer responder in months four to six, prior authorisation categories in months six onward with public scoping.
The sequence that fails starts with prior authorisation, because it is the most interesting problem and the largest budget line, and leaves the identity and entitlement foundation until it is too late to build it properly.
What a readiness programme costs when it is late
Not the fine — the reputational and operational cost of a rushed implementation. A patient access surface that exists and no member uses. A provider API that returns the wrong member's data because entitlement was never built. A payer-to-payer responder that returns empty bundles and nobody knows. Each is worse than being visibly behind, because each is invisible until someone external discovers it.
What I do
I start with the conformance map and a live trace of one member through all four APIs, timestamps on every hop. That takes a week, and the failure it surfaces is almost never in the code — it is in entitlement, attribution, or a match that returned nothing and logged nothing. I have run the ONC (g)(10) suite to 317 of 317 against a platform I built, and operated eight X12 005010 transaction sets across 104 clearinghouse enrolments in 53 jurisdictions.
What the programme looks like from the inside
Six months in, the work is not architecture. It is a standing list of profile-by-profile gaps, a counterparty register with test dates, and a weekly trace of one member through the APIs you have shipped.
The organisation that succeeds has one person who can answer, on any given day, which of the four obligations are live, which counterparties have tested successfully, and what the last member journey looked like end to end. That person is not a programme manager with a Gantt chart. They are the one who has run the trace themselves.
The organisation that struggles has four workstreams, four dashboards, and nobody who can produce that answer in under a day. The difference is not talent. It is whether the conformance map was built at profile granularity or at the level of a coloured cell.
The test of a readiness programme is not the conformance map. It is whether one named person can produce, on a Tuesday, the current state of all four obligations, the counterparties that have tested successfully this quarter, and the trace of one member through every API the plan has shipped. Everything else is scaffolding around that answer.
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
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
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 — 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.
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.