myrxwallet · uscdi v7 · identity credential

Charles Trinh — MyRxWallet and the USCDI Proposal

Charles Trinh — MyRxWallet and the USCDI Proposal
Charles Trinh — MyRxWallet and the USCDI Proposal

The proposal

I filed a proposed USCDI v7 data element for a Patient Digital Identity Credential with ONC. The argument is structural rather than technical.

Consent stored at each covered entity must be re-obtained at each covered entity, and re-obtained again when the patient changes providers. The patient's intent does not change when they move; the storage model does.

What it changes

A credential the patient holds moves where consent lives, not what consent means. The format is mature: W3C verifiable credentials with selective disclosure and holder binding.

Selective disclosure matters clinically, because a pharmacy verifying coverage should not receive the patient's full consent state.

What it does not solve

Cryptography was never the blocker. The open question is why a payer should accept a credential it did not issue, and what that acceptance costs them in liability.

Every organisation has a prepared argument for declining, and no key format addresses a commercial and legal question wearing a technical costume.

Where it is useful now

Workforce and organisational identity inside a federation you control, where issuance, verification, recovery and revocation are all yours and the governance question is already answered.

Start there, prove the removed step, and extend. A credential that removes a re-collection step for one workflow is fundable; a credential that proposes to replace industry governance is a decade of meetings.

The structural argument

Consent is stored at each covered entity and re-obtained at each one, so the patient's stated intent is fragmented by the storage model rather than by the patient's wishes. That fragmentation is not a technology defect and no exchange fixes it, because the exchange is asking each holder in turn.

The proposal is that the intent should travel with the patient. That is a statement about where the record lives, not about what the record means, and the distinction is what makes it a data element proposal rather than a policy position.

What a credential provides

A verifiable credential with holder binding and selective disclosure lets a patient present a claim without the verifier learning more than the claim. For consent, that means a pharmacy verifying coverage receives the coverage and not the patient's full consent state, which is the minimum-disclosure property a privacy officer will require.

Revocation is the part that decides whether it is operable. A credential that cannot be revoked is a permanent grant, and the revocation mechanism has to reach the verifier, which is a design and governance question rather than a cryptographic one.

The governance question

The reason a payer should accept a credential it did not issue is not technical. It is a question about liability, trust and who bears the cost of a bad assertion, and every organisation has a prepared argument for declining.

That is why the useful path is narrower than the ambition: start where the same party issues and verifies, prove the operational saving on a single workflow, then extend to a second issuer. A credential that removes a re-collection step is fundable; a credential that proposes to replace the governance of consent across an industry is a decade of meetings.

What the platform demonstrates

MyRxWallet is the environment the proposal came from: a clinical platform with a consent ledger, a FHIR surface, a claims rail and an identity layer, operated under a business associate agreement. The proposal is grounded in operating the thing rather than in imagining it.

The honest limitation is that a demonstration platform is not a federation. What it can show is the mechanism and the operational cost; what it cannot show is the acceptance, which is the part the industry has to decide.

Why identity first

Every other interoperability obligation assumes the organisation knows who the patient is. Matching defects, consent scope and disclosure records all rest on identity that is correct at the moment of use, and the storage model is where that correctness is decided.

That is why the proposal is a data element rather than a platform. A standard element can be adopted by parties that share nothing else, which is the only way the problem is solved at scale.

What the operator sees

Operating the platform produces the operational facts that a proposal needs: how many enrolments lapse, how often matches fail, how long revocation takes to propagate. Those numbers are the argument, and they are unavailable to anyone who has not run the system.

The honest limit is that one platform is not an industry. What operating it can show is the cost and the mechanism; what it cannot show is the acceptance.

The recovery problem

A credential held by a patient fails when the patient loses the device, and the recovery path decides whether the model is operable. The answer cannot be a bypass of the binding, or the credential becomes transferable at the moment it matters most.

Design the delegate set and the identity proofing before enrolment, and test the Friday-evening scenario with real people.

What to do next

Publish the element, run a narrow pilot with one issuer and one verifier, and measure the removed step. Then extend to a second issuer, having proved that acceptance is possible rather than assuming it.

Anything wider than that is a standards campaign, and standards campaigns are worth participating in rather than leading before the mechanism is demonstrated.

The record behind the proposal

A clinical platform under a business associate agreement, with a 337-table store, a consent ledger on Fabric and EVM, eight X12 005010 transaction sets across 104 clearinghouse enrolments, and an ONC (g)(10) result of 317 of 317 subtests.

The numbers are the environment the proposal came from rather than a claim about it, and each of them was produced by operating the system rather than by describing it.

What the element would change

If consent intent travelled with the patient, a new provider would not have to re-obtain what the patient already decided, and the patient would not have to repeat themselves at every move. The saving is administrative and the effect is continuity.

The cost is a governance model that has to be agreed before the mechanism is useful, and that agreement is the part that takes years.

Keep the proposal documentation with the platform record, including the submission and the date, so the claim on this site can be checked rather than believed. A proposal cited without a date is a rumour with a citation.

Where ONC publishes a decision, record it, whichever way it goes, because the record of what was submitted and what was decided is the whole value of participating.

The same discipline applies to every claim on this site: a number without a source is a marketing sentence, and the record behind it is what makes the difference between an introduction and a reference.

Read the proposal itself rather than a summary of it. The argument is short, and the summary is the part that tends to survive in circulation while the substance is lost.

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 — myrxwallet and the uscdi proposal — 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