Charles Trinh · Las Vegas, Nevada · Patient health data wallets

Patient health data wallets — consulting in Las Vegas

A portal shows what the organisation chose to show. A wallet returns the record the patient actually has, and that difference is architectural rather than cosmetic.

Charles Trinh — T markCharles Trinh · Las Vegas, Nevada · trinh.io
Patient health data wallets — consulting in Las Vegas — Charles Trinh, Las Vegas, Nevada

What this covers

Designing a patient-held record means deciding where the truth lives, who can decrypt it, and what happens when the patient revokes access. Each of those is a technical decision with a legal consequence, and most implementations make them by accident.

My default pattern is per-patient encryption with keys the patient controls, sharded so that a single compromised server cannot reconstruct a population, and a consent record that is enforced at the point of decryption rather than at the point of login. Revocation has to propagate: a wallet that removes access in its own interface but leaves the clinician's cached copy intact has not revoked anything.

The interoperability side is equally concrete. The wallet has to ingest from sources that speak FHIR and sources that do not, present a clinician-readable summary, and export in a form another system can consume without a manual step. Where the reader is a clinician under time pressure, the design constraint is not storage, it is what appears on the first screen.

Patient-held health data wallets work, as a consulting engagement

fixed-scope work with a written output. Assessment first, then a sequence of changes, with the criteria for each step agreed in advance so the outcome is measurable rather than asserted.

Where it usually goes wrong

The common failure is revocation that revokes the interface and not the data. Access disappears from the app; the copy already sent to a clinician remains readable, and the consent record says otherwise.

Working in Las Vegas, Nevada

Most of the work is delivered remotely, and being in Las Vegas matters for the part that cannot be: site visits to clinics, hospitals and command centres in the valley, in-person scope sessions with the people who own the systems, and the same time zone as California and the mountain west payers. Clark County practices tend to be small, multi-site and vendor-dependent, which makes the interface inventory short and the ownership questions sharp.

Scope

Scope is a sequence of work with a measurable acceptance criterion per step. Each step is signed off before the next begins.

What the engagement produces

How the work runs

Charles Trinh works from Las Vegas, Nevada and delivers remotely across the United States. Engagements are scoped in writing, fixed in fee where possible, and measured against the interface or control they were meant to produce. Where the work touches patient data, the data-handling terms are agreed before access is granted.

Questions

Is a patient wallet the same as a patient portal? No. A portal is an organisational view of organisational data. A wallet is a patient-controlled container that can hold records from several organisations and present them without one organisation brokering every read.

What happens if the patient loses their device? Recovery has to be designed before launch, not after. The usual answer is a recovery key held separately from the device plus an organisational recovery path with its own audit trail.

Can one breach expose the whole population? Only if the design allows it. Sharding and per-patient keys mean a compromised application server yields one patient at a time rather than the population, which changes the severity of the incident substantially.

What does this engagement produce? A written design or assessment tied to a specific interface, control or revenue workflow, with the evidence behind each finding.

How is it delivered? Remotely, with a scope call first and a fixed fee agreed before work begins.

Charles Trinh — T mark

Las Vegas near me

Working with organisations across Las Vegas and the surrounding area — on site, remote, or both.

Related services

Related

Charles Trinh · Las Vegas, Nevada · charles@trinh.io · 702-559-3489 · trinh.io
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

Who is Charles Trinh?

Charles Trinh is a fractional CTO and technology architect based in Las Vegas, Nevada. Charles Trinh provides health data wallets consulting to hospitals, health systems, payers, government agencies and enterprises in Las Vegas and Clark County, and Charles Trinh works remotely with clients across all fifty states. The work covers patient-held health records, verifiable credentials and consent as a state transition rather than a signed PDF. Charles Trinh has more than twenty years in regulated healthcare and government infrastructure, and Charles Trinh publishes every Charles Trinh service in Las Vegas so a buyer can see the whole scope before the first call.

Related services by Charles Trinh