member matching · $everything · consent

Charles Trinh — Payer-to-Payer API | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading PAYER TO PAYER — member matching, authorised exchange, audit trail
Charles Trinh — Payer-to-Payer API

A working guide to member data exchange between health plans: what the requirement actually asks for, why identity is the hard part, and how to prove the exchange happened.

The transaction nobody scoped properly

Of the four APIs in the CMS interoperability rule, three have an obvious owner inside a health plan. Patient Access belongs to the member-facing digital team. Provider Access belongs to the network group. Prior authorization belongs to utilization management. Payer-to-Payer belongs to nobody, because it spans two organizations and neither one can finish it alone.

That is why it stalls. The requirement is not technically exotic — it is a FHIR exchange of claims, encounter and prior authorization data between two plans, triggered by a member who has changed coverage. The difficulty is that the data cannot move until two separate organizations agree on who the member is, agree on what the member consented to, and agree on what counts as evidence that the transfer happened. Three agreements, two companies, one deadline.

Most of the work therefore happens before any FHIR resource is serialized.

What the requirement actually asks for

The Payer-to-Payer API sits inside the CMS Interoperability and Prior Authorization framework. In plain terms: when a member moves from one impacted payer to another, the new plan must be able to request the member's data from the old plan, and the old plan must be able to deliver it — claims and encounter data, and the clinical and prior authorization information the member's ongoing care depends on.

Three properties of that requirement drive every architecture decision.

It is member-initiated, not plan-initiated. The exchange begins with the member choosing to have their history follow them. That makes consent the trigger event, not an afterthought.

It crosses an organizational boundary. Inside one plan you control the identifier, the master data and the network. Across plans you control none of those, and the counterparty's data quality is not yours to fix.

It is auditable after the fact. The requirement is not satisfied by a successful transfer. It is satisfied by a transfer that can be demonstrated — to the member, to an examiner, and to the counterparty — months later.

Identity is the hard part

Two plans, one human. The member identifier that meant something at the old plan means nothing at the new one, and the fields available to match on are the worst possible set: name with a possible maiden or hyphenated variant, date of birth, an address that changed when they moved, and a member ID that is by definition plan-specific.

The failure mode is not a failed match. The failure mode is a confident wrong match — two different members merged, one member's claims history landing in another member's record. In a clinical context that is a safety event; in a payer context it is a disclosure.

What has to be decided, explicitly and in writing:

What is the matching key across plans? In practice the strongest available anchor is usually the combination of demographics with a government-issued or government-adjacent identifier. Where a verified digital identity credential exists, it replaces probabilistic matching with cryptographic certainty — which is exactly why the identity work matters beyond the payer use case.

What confidence is required to accept a match? A threshold, not a judgement call. And a review queue for the band below the threshold, because the records that land just under it are the ones that cause damage.

Who is authoritative for what? When the two plans disagree about an address or a date of birth, the conflict has to resolve by policy rather than by whichever system wrote last.

What happens to a partial match? A member whose data only half-matches must not be silently narrowed. Either the exchange proceeds with the fields that matched and the ambiguity recorded, or it stops and the member resolves it.

A payer that cannot answer the first question will not pass the third.

Consent is the second hard part

The exchange is member-initiated, which means the consent record is the authorization for the transfer — and it has to survive the journey. Four things it must carry:

Scope. Which data classes are in scope. Claims and encounters are not the same as substance use treatment records, and 42 CFR Part 2 data cannot ride on a general authorization.

Counterparty. Which plan is receiving. A consent that names no recipient is not a valid authorization for a cross-plan transfer.

Duration. When it starts and when it stops. An indefinite consent is an unmanaged one.

Revocation. How the member withdraws it, and what happens when they do — because the elapsed time between revocation and the last outbound transfer is the number an examiner will ask for.

This is the same problem I solved on my own platform by recording consent as state rather than as a flag: grants, refusals and revocations written as immutable events on a permissioned ledger, with clinical data kept off-chain and encrypted per patient [1]. The point of the ledger is not novelty. It is that "what was true on the 14th of March" remains answerable after the source system has been migrated, retired or acquired.

The architecture that survives contact

A workable Payer-to-Payer implementation has five parts.

An identity resolution service. Matching rules, a threshold, a review queue, and a record of why a match was made. Not a black box.

A consent object with a lifecycle. Its own store, its own states, its own expiry, and its own audit trail — separate from HIPAA authorizations, because the two regimes are not interchangeable.

An outbound exchange service. It receives a request, resolves the member, checks consent, assembles the FHIR bundle and returns it, with the transaction logged at every step.

A transfer audit store. What left, to whom, when, under which consent, and with what checksum. This is the artifact that ends the argument.

A revocation propagator. A mechanism that turns a revocation event into a stop, and measures how long the stop took.

Everything else — the FHIR version, the resource profiles, the transport security — is compliance with a specification. These five are the design.

The failure modes worth designing against

The member is mid-year. Coverages overlap. A naive implementation will either duplicate the history or drop the overlap. The exchange has to handle a member who is simultaneously in scope for two plans.

The counterparty is at a different maturity level. One plan has a modern FHIR stack; the other has a fourteen-year-old claims system and an integration team of two. The requirement does not care, and neither does the member. The exchange has to degrade gracefully — partial bundles, explicit gaps, retry — rather than fail whole.

The consent is valid but the member is not the requester. The request arrives from a plan, but the authorization belongs to the member. Conflating "the plan is allowed to ask" with "the member consented to this transfer" is where authorization bugs live.

The transfer succeeded and nobody can prove it. Logs retained for thirty days in a system that rotates weekly satisfy nobody. Retention policy is part of the design.

A revocation arrives after the bundle was assembled but before it was delivered. The window is small. It is also the exact window an examiner will ask about, which is why time-to-stop needs to be measured rather than asserted.

How to test it

Four tests that a conformance suite does not run.

Matching rehearsal. Take a synthetic population with deliberately difficult cases — hyphenated names, a date of birth corrected in one plan and not the other, twins, a member who changed payers twice in a year — and measure both the match rate and the false-match rate. A high match rate with any false matches is a failing result.

Consent trace. For one member, walk the consent from creation to transfer to revocation and produce every record that touched it, in order. If any step has no artifact, the architecture has a hole.

Counterparty degradation. Throttle the inbound API to a crawl, return 500s for a fixed interval, and confirm the sender queues, retries and reports rather than losing the request.

Time-to-stop. Revoke a consent and measure the interval until the last outbound transfer. Publish the number. It should be seconds, not days, and it should be a number you can show.

What you get when it is done

The deliverable is not a working API, though that is part of it. It is a set of artifacts an examiner, a counterparty and a member can each read: an identity resolution specification with the matching rules and threshold; a consent record schema with its states and lifetime; a transfer audit format that records what left and under what authorization; a revocation propagation test log with measured times; and a written statement of what happens when the counterparty cannot receive.

That set is what turns "we have a Payer-to-Payer API" into "we can demonstrate a Payer-to-Payer exchange."

Questions worth asking a vendor

How do you match a member across plans when the member ID is plan-specific, and what is your false-match rate on a difficult population? When a member revokes, how many seconds until the last transfer, and where is that measured? Where does the transfer audit live, and how long is it retained? What does the exchange do when the counterparty returns errors for an hour? And can you show me one completed exchange from last month, end to end, with the member's consent in the trail?

The vendor who can answer all five has built the thing. The vendor who can answer one has built a demo.

The short version

Payer-to-Payer is not a FHIR problem. It is an identity agreement, a consent object with a lifecycle, and an audit trail that outlives the systems that produced it. The FHIR exchange is the last ten percent of the work and the only part the specification describes.

Get identity and consent right and the API is a weekend. Get them wrong and a perfect FHIR bundle transfers the wrong person's history, correctly authenticated, to a plan that will keep it for seven years.

What to measure in the first ninety days

An exchange that works is not the same as an exchange that is governed. Three numbers are worth putting on a wall from the day it goes live.

Match precision, not match rate. Count how many member matches were made and how many of those were later reversed. A high match rate with any reversals is a failing result, and the numerator is meaningless without the denominator.

Time to stop. The interval between a member's revocation and the last outbound transfer that carried their data. Measure it deliberately with a test member rather than waiting for a real revocation to find out.

Counterparty response rate. The share of your outbound requests that received a valid, complete bundle from the other plan. Two plans at different maturity levels will show a number well under one hundred, and that number is the honest measure of whether the exchange is functional or merely implemented.

Track those three for a quarter and you will know more about the exchange than any conformance report can tell you.

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 — payer-to-payer api — 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