W3C VC · DIDs · selective disclosure

Charles Trinh — Verifiable Credentials | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading VERIFIABLE CREDENTIALS — signed claims, selective disclosure and real revocation
Charles Trinh — Verifiable Credentials

A verifiable credential is a claim signed by an issuer that a holder can present and a verifier can check without calling the issuer. In healthcare that pattern is the basis of a patient-controlled identity.

What this is

The model has three roles. An issuer signs a credential about a subject. A holder stores it and presents it. A verifier checks the signature and the claims without contacting the issuer. The absence of that call is the point: verification works offline, at the edge, and without a central directory of everyone who has ever been verified.

The first design decision is what the credential asserts. A credential that asserts a fact about a person is different from one that asserts a relationship, and healthcare needs both: this person is who they say they are, and this person is entitled to act for that patient. Conflating the two produces a credential that is either too broad or too narrow.

The second is revocation. A credential that cannot be revoked is a credential that is valid forever, which is unacceptable for anything that can change. Revocation lists, short expiry and status endpoints are the three mechanisms, and each has a different privacy profile. Choosing one is a design decision with consequences for both security and privacy.

The third is selective disclosure. A patient presenting proof of insurance should not have to disclose their diagnosis. Credential formats that support selective disclosure allow the holder to reveal only the claims the verifier needs, and formats that do not force an all-or-nothing presentation.

The fourth is the wallet. A credential is only useful if the holder can store and present it, which means a wallet on a device the holder controls. That wallet is a security boundary, and its compromise is the compromise of every credential in it.

Finally, verifiable credentials are a standards area in motion. Formats, transports and trust frameworks are still converging, and a design that commits to one implementation without an abstraction layer will be expensive to change.

Interoperability between wallets is the practical constraint. A credential issued in one format may not be presentable in a wallet that supports another, and a verifier may only accept one. The abstraction layer is not architectural purity; it is the thing that lets a patient present the credential they have to the verifier they are standing in front of.

Privacy is a design property rather than a compliance checkbox. A verifier that learns the issuer, the subject and the full claim set on every presentation is building a record of who was verified where. Selective disclosure, unlinkable presentations and minimal claim sets are the mechanisms that prevent that, and each one has a cost in complexity that has to be weighed deliberately.

Trust in the issuer is the foundation. A verifier accepts a credential because it trusts the issuer, and that trust is expressed through a registry, a certificate chain or a governance agreement. Without a trust framework, a verifiable credential is a signed assertion by an unknown party, which is worth very little.

Finally, the patient experience determines adoption. A credential that requires a wallet, a PIN, a network connection and a specific app will not be used at a front desk under time pressure. Designing for the worst-case presentation environment, rather than the ideal one, is what makes the credential real.

There is also a governance question about who may issue. A credential asserting a clinical fact carries weight only if the issuer is entitled to assert it, and the trust framework has to say so explicitly. An issuer registry with a defined admission process is what prevents a credential ecosystem from becoming a collection of assertions nobody can evaluate.

The final consideration is the relationship between verifiable credentials and the existing identity infrastructure. A credential does not replace a directory; it complements one by allowing a claim to be verified without a lookup. Designing the two to coexist, rather than treating the credential as a replacement, is what allows adoption to be incremental rather than a cutover.

How I do it

I start with the trust framework: who issues, who verifies, what each credential asserts, and what the verifier is entitled to learn. That framework is a governance document before it is a technical one.

From there I choose the credential format against the requirements that matter: selective disclosure, revocation mechanism, offline verification and wallet support. The choice is documented with its trade-offs rather than made by default.

Revocation is designed explicitly, with the mechanism, the propagation delay and the privacy implications stated. A credential with no revocation story is not deployed.

Selective disclosure is tested with real presentations, because the failure mode is a verifier receiving more than it asked for and nobody noticing.

Finally, the implementation is kept behind an abstraction so that a change of format or transport is a configuration change rather than a rewrite.

Wallet interoperability is tested with the wallets the population actually uses, not with a reference implementation. A credential that only works in one wallet is a credential with a limited audience.

Presentations are designed to disclose the minimum claim set, with the verifier's request and the holder's disclosure both logged so that over-disclosure is detectable.

The trust framework is documented as a governance artefact: who may issue, who may verify, and how trust is established and withdrawn.

The presentation flow is tested under realistic conditions, including poor connectivity and time pressure, because those are the conditions under which it will be used.

The issuer registry is maintained with an admission process and a withdrawal process, so trust can be granted and removed deliberately rather than accumulating by default.

The credential layer is deployed alongside the existing directory rather than in place of it, with the two reconciled at the points where a claim must be authoritative. That sequencing lets adoption proceed one use case at a time.

The handover includes the trust framework, the format decision with its trade-offs, the revocation design and the tested presentation flows. Those four artefacts let a verifier be onboarded without a bespoke conversation, which is what makes an ecosystem scale beyond its first few participants.

Revocation propagation is measured rather than assumed, because a revocation that takes a day to reach a verifier is a day in which a withdrawn credential still works. The measured delay is documented and accepted explicitly.

Artifacts you keep

  • A trust framework naming issuers, verifiers and what each credential asserts
  • A documented format choice with its trade-offs
  • An explicit revocation mechanism with propagation and privacy stated
  • Tested selective disclosure with real presentations
  • An abstraction layer insulating the implementation from format change

Proof

  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 104 clearinghouse enrolments across 53 jurisdictions
  • 67 public hostnames, 51 serving, one AWS account
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564

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

A credential is a claim someone can hold

A conventional lookup asks the issuer whether a claim is true, and the issuer learns about every check. A verifiable credential inverts that: the issuer signs a set of claims once, the holder stores it, and the holder presents it to a verifier who checks the signature without contacting the issuer.

For healthcare the useful cases are specific. A clinician proving a licence at a new facility. A patient proving vaccination for a return to work. A staff member proving a completed training module. Each replaces a step where a human currently collects information that already exists somewhere.

The cryptography is mature and uninteresting. What decides whether a deployment works is issuance policy — who may assert what, on what evidence — and the trust list a verifier is willing to accept.

Three properties that matter clinically

Holder binding: the credential proves the presenter is the subject, not merely that the claims are valid. Without it, a credential is a bearer token and a screenshot is an attack.

Selective disclosure: a pharmacy verifying coverage should not receive the patient's full clinical consent state. Minimum disclosure is a privacy control and, in practice, the only version a privacy officer will approve.

Revocation that reaches: status lists or short validity windows. A credential that cannot be revoked is a permanent grant, which is incompatible with how consent actually works.

The governance question that decides adoption

Why should a payer accept a consent or identity credential it did not issue, and what does acceptance cost them in liability? Every organisation has a prepared argument for declining, and no key format addresses it.

The workable path is narrower than the ambition: start where the same party issues and verifies, prove the operational saving on one workflow, and extend from there. 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 standards meetings.

Instrument refusal as well as acceptance. A pilot where every credential presented is accepted is a pilot where nobody is checking, and the trust model is untested rather than proven.

What to build first

One issuer, one verifier, one workflow, and a written recovery process before the first credential is issued. Measure minutes saved per instance multiplied by instances per month, because that is the only number that survives a budget review.

Then publish the trust list, test expiry and revocation deliberately, and only afterwards consider a second issuer. Most programmes do this in reverse and produce a pilot that demonstrates interoperability between organisations that had already agreed to trust each other.

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 — verifiable credentials — the scope, the failure modes it prevents and how the work is measured. It sits in the Identity and Consent 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