SERVICES · LAS VEGAS NV
Charles Trinh — Non-Transferable Credentials | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Credentials that cannot be handed on: holder binding, proof of possession, and the revocation and recovery design that makes non-transferability real rather than nominal.
Transferability is the default failure
A credential that can be copied is a bearer token wearing a nicer name. The value depends entirely on binding it to a holder who can prove possession of a key that never leaves their control.
Binding means the presentation proves possession at the moment of use, not merely that the credential is valid at that timestamp.
Revocation with a stated latency
Design revocation as a state with latency you can quote: short validity windows, status lists, or both. What does not work is neither, because that produces a permanent grant.
Status lists give near-immediate revocation and leak a query at verification. Short windows give bounded staleness and no query. Both are defensible; picking neither is not.
Recovery defines operability
Test the recovery path before enrolment. The answer to a lost key determines whether the model can actually run, and retrofitting recovery means re-enrolling everyone who already holds a credential.
Where a device holds the key, treat device loss as credential loss and make replacement a routine operation with a documented delegate set.
Log the presentation
Record every presentation with the verifier, the credential type, the timestamp and the outcome, so an audit can reconstruct who proved what to whom without interviewing anyone.
That log is also how you measure refusal. A federation where nothing is ever rejected is a federation where nobody is checking.
Binding is a property of the presentation
The question a verifier must be able to answer is not whether the credential is authentic but whether the person presenting it is the person it was issued to. That requires the presentation to include proof of possession of a key that only the holder controls, checked at the moment of use, with a challenge that cannot be replayed. A credential that carries a signature from the issuer and no binding is a digital certificate on a piece of paper: valid, copied, and worthless for the purpose.
Design the challenge so that a captured presentation cannot be reused. Short-lived challenges tied to the session, bound to the verifier's identifier, are simple and sufficient; anything more elaborate is usually solving a threat that is not present in the deployment. The property to test is that a presentation recorded and replayed five minutes later fails, and that the failure is logged rather than silently accepted.
Recovery is where the model meets reality
Every holder-bound credential has a loss scenario, and the design of the recovery path determines whether the deployment is operable. A lost device with no recovery means a re-enrolment, which in a clinical setting means a clinician cannot work until an administrator is available. A recovery path that bypasses binding converts the credential into a transferable one at exactly the moment the attacker would want, which is why recovery is the part of the design that deserves the most scrutiny rather than the least.
Test the recovery path with a real scenario before any holder is enrolled: the device is destroyed on a Friday evening, and the clinician needs to work on Saturday morning. The answer defines the delegate set, the identity proofing that substitutes for the lost key, and the audit record that the recovery leaves. Where the answer is unacceptable, the credential model is wrong for that population and the honest move is to say so rather than to deploy it and discover the problem at the worst moment.
Revocation must reach the verifier
A revocation mechanism that the verifier does not check is a policy, not a control. Decide whether revocation propagates through a status list queried at verification or through short validity windows that bound the exposure, and state the latency you are accepting in a sentence a compliance officer can repeat. Both models are defensible and they fail differently: status lists leak the fact of a check to the issuer, and short windows mean a revoked credential remains usable until it expires.
Whichever is chosen, test that revocation actually takes effect at the verifier and record the elapsed time. The test is simple and almost never performed, which is why organisations discover during an incident that their revocation path was never wired to the verifier they actually deployed.
What the audit needs
The record of presentations is the evidence that the model operates. Log the verifier, the credential type, the subject reference in a form that is not itself identifying, the timestamp, the outcome and the reason for a refusal. That record answers the question an examiner asks after a disputed disclosure, which is who proved what to whom, and it answers it without interviewing anybody.
Retain the log for the period the disclosure obligations require, which is generally longer than the credential's own lifetime, and protect it from modification. A presentation log that can be edited by the system that writes it is an assertion rather than evidence, and the distinction is the entire value of the mechanism.
Deployment populations are not uniform
A credential model that suits a power user with a managed phone is a different proposition for a clinician on a shared workstation and for a patient on a ten-year-old handset. Segment the population before choosing the binding mechanism, because a design that requires a device capability the majority lacks will be worked around by exactly the people who most need assurance, and the workaround will be a screenshot shared over messaging. Where a segment cannot meet the model, give it a different assurance path with its own name, rather than lowering the bar for everyone.
The assurance levels should be visible in the record so that a verifier knows which path a credential came from. A verifier who cannot distinguish a hardware-bound credential from a soft one is making an assumption about assurance that the record does not support.
Testing refusal
The health of a verification federation is visible in its refusals. A deployment where every presentation is accepted has either a very narrow population or a verifier that is not checking, and the two look identical from the outside. Instrument refusals with a reason and review them monthly, because a refusal rate that drops to zero is a signal that the check has been disabled or bypassed rather than a signal of improved quality.
Integrating with existing identity
Most organisations already have a directory and a set of identity providers, and a credential programme that ignores them creates a second source of truth for the same people. Decide where the authoritative identity lives, make the credential a projection of it, and ensure revocation in the directory propagates. Programmes that skip that step produce credentials held by people who have left, which is the failure the whole design was supposed to prevent.
Interop with verifiers you do not control
A verifier outside your organisation will accept your credential only if it recognises the issuer, and that recognition is a governance decision rather than a technical one. Publish the trust list, state what the credential asserts and what it does not, and be prepared to answer the question every counterparty asks first: what happens when the issuer makes a mistake. An answer that includes revocation, a correction process and a named contact is what turns a pilot into a production acceptance.
Test refusal with a verifier you do not control before claiming interoperability. A credential accepted only by your own test harness has demonstrated your harness, not the federation.
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 — non-transferable 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
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
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.