Charles Trinh · Nevada · Patient health data wallets

Patient health data wallets — contractor in Nevada

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 · Nevada · trinh.io
Patient health data wallets — contractor in Nevada — Charles Trinh, 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 contractor

hands-on delivery on a defined piece of work, at a committed number of hours, with the client's team owning the rest. The boundary is written down so that neither side is surprised about who is building what.

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 Nevada

Engagements run statewide from Las Vegas: Reno, Sparks, Carson City and the rural counties, where a critical-access hospital often has one IT director covering infrastructure, security and the EHR. Remote delivery is the default; travel is done when the work genuinely needs a room with the people in it. Statewide work usually involves the state Medicaid programme, which changes the interface requirements materially compared with commercial payers.

Scope

Scope is a defined piece of delivery at a committed number of hours per week, with the boundary of responsibility written into the agreement.

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

Nevada near me

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

Related services

Related

Charles Trinh · Nevada · charles@trinh.io · 702-559-3489 · trinh.io