decentralized identifiers · key custody · recovery
Charles Trinh — DID Patient Identity | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A decentralized identifier gives a patient a durable handle they control, rather than one issued per organisation. The design question is custody: who holds the key, and what happens when it is lost.
What this is
A DID is an identifier that resolves to a document containing public keys and service endpoints. The patient holds the private key, the verifier resolves the DID to check a signature, and no central registry has to authorise each presentation. That is attractive in healthcare precisely because patients move between organisations that do not share an identifier.
Custody is where the model meets reality. A patient who loses a phone must not lose access to their health identity, and a patient who is incapacitated must have someone who can act for them. Both cases are common in healthcare and both are solved outside the cryptography: recovery methods, guardianship models and the organisational fallback when a patient cannot present a key.
Binding is the second problem. A DID is only useful if it can be linked, under consent and with controls, to the records an organisation holds. That binding is itself an identity assertion — the same matching problem as an MPI — and pretending otherwise produces a decentralised identifier that is either useless or dangerous.
I design DIDs as one layer in patient identity rather than a replacement for the index: the DID is the patient's handle, the index is the organisation's cross-reference, and the binding between them is explicit, consented and auditable.
Interoperability with the rest of the estate is the practical constraint. A DID that five organisations accept and a sixth cannot resolve is a pilot, not infrastructure. Resolution methods, key algorithms and document formats all have to be supported by the parties in the exchange before the design is agreed.Privacy has a specific shape here. A DID that is presented to every organisation becomes a correlating identifier across the patient's whole care history. Using pairwise identifiers per relationship, or credentials that reveal no identifier, is the difference between a privacy-preserving design and a more convenient central registry.
The honest limit is that decentralised identity is still young in healthcare, and a design that assumes every organisation will support it in year one is a design that will sit unused. A phased model, with one credential and a handful of partners, is how the model earns the trust list it needs.
How I do it
First the DID method: which resolution method fits the deployment, where the identifier document lives, and how key rotation works. The choice has operational consequences that outlast the pilot.
Then custody and recovery: device-bound keys, a recovery factor the patient controls, a guardian path for incapacity, and an organisational fallback with a documented approval step.
Finally the binding. Linking a DID to an MPI record is a consent-mediated operation with an audit record, tested for the case where a patient presents a DID that is not yet bound.
The pilot scope is deliberately narrow: one credential, one issuer, one verifier and one recovery path, all tested end to end. Expanding afterwards is a matter of adding issuers and verifiers to a model that has already been proven.The acceptable failure modes are written down and tested: a lost device with recovery, a compromised key with rotation and revocation, and an incapacitated patient with a guardian path. Each is exercised before launch, because these are the cases where an identity system either holds or becomes the incident.
Artifacts you keep
- A DID method decision with its operational consequences written down
- A custody and recovery model covering loss and incapacity
- A consent-mediated binding between DID and index record
- A key rotation procedure tested against a live credential
- An audit record of every binding, rotation and recovery event
What the mechanism actually does
A DID resolves to a document containing public keys and service endpoints, and verification uses those keys to check a proof. That is the whole mechanism, and understanding it removes most of the mystique around the surrounding vocabulary.
Credentials, presentations, selective disclosure and status lists all layer on that resolve-then-verify primitive. When a vendor describes something far larger, ask which part is the primitive and which part is a policy they have assumed into existence.
For patients the point is ownership: an identifier the subject controls survives a change of health system, while one issued by a hospital does not, and every downstream match becomes an inference from demographics that were never designed to be keys.
Recovery is where these die
Lose the keys, lose the identity. Unlike a password there is no support desk with authority to reset it, so recovery is social and organisational rather than technical, and it is the least discussed part of every deployment.
The workable pattern is a recovery committee defined at enrolment: two or three parties who together can re-issue, none alone. That is governance as code, and it must exist before the first patient enrols because retrofitting means re-enrolling everyone.
Guardianship belongs here too. A parent controls a child's identity until a legal event transfers it, and that transition has to be auditable because it is exactly the kind of event that gets disputed.
Rotation, revocation, and the governance wall
Credentials signed last year must verify after a key rotation, which means retaining prior keys within a window and honouring the key valid at signing time rather than the key valid now.
Revocation must reach the verifier. Short validity windows and status lists both work; a credential with neither is a permanent grant, the one thing consent architecture exists to prevent.
And the honest limit: none of this answers why a payer should accept a credential it did not issue. Start where you are both issuer and verifier, prove the benefit on one workflow, and measure the time saved removing a step a human performs today.
What to build in the first ninety days
One issuer, one verifier, one workflow, and a written recovery process before the first credential is issued. The workflow should be internal: a system you operate issuing a credential another system you operate verifies, so the governance question is answered by ownership rather than by negotiation.
Measure the step you removed. If the credential replaces a form a human currently collects, the number that matters is minutes saved per instance multiplied by instances per month, and that number is what survives a budget review.
Then instrument refusal. The count of credentials presented and rejected tells you whether the trust model is real or whether everyone is accepting everything to avoid a support call. An acceptance rate near one hundred percent in a federation you control means nobody is checking.
The measure that matters
One number: the time removed from a workflow a human currently performs, multiplied by instances per month. Everything else about a credential deployment is a means to that figure, and a pilot that cannot produce it is a demonstration rather than a deployment.
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 — did patient identity — 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.