evm · smart contracts · auditable records
Charles Trinh — EVM Ledger Integration, Las Vegas NV

Using an EVM chain where it earns its cost: anchoring hashes of regulated records, proving existence and order without putting PHI on-chain, and keeping the contract surface small.
What belongs on-chain and what does not
Put hashes, identifiers and timestamps on-chain; put nothing that could identify a patient, because a chain is the one database you cannot delete from.
The useful pattern is an anchor: the record lives in your store, its digest is written to the chain, and the chain proves it existed in that form at that time.
Anything you would have to redact later must never be on-chain, and the first design question is what the minimum provable fact is.
Contract surface discipline
Every line of contract code is immutable risk; write the smallest contract that satisfies the proof requirement and nothing more.
Anchor registries need a write function, a read function and an event; anything beyond that is surface area that will eventually need an upgrade you cannot perform.
If you genuinely need upgradeability, plan the proxy pattern before deployment, because retrofitting it means redeploying and losing continuity of address.
Keys, signers and operational control
The signer key is the authority to write; treat it like a production credential, because that is what it is.
Use a dedicated signer service with an allowlist, rate limits and an audit log rather than an environment variable in an application container.
Rotation needs a documented path: a lost signer key with no replacement mechanism is an outage with no remedy.
Gas, cost and failure modes
Cost per write is a design input; batch anchors where the business allows and never put one transaction per small event.
Decide what happens when a write fails or is delayed: the record must remain usable and the anchor must be retryable, because chain congestion is not an exception you can surface to a clinician.
Track pending anchors as first-class work items rather than as background noise.
Verification and dispute
Verification is reading the anchor and recomputing the digest from the stored record; that check belongs in your own tooling, not in a third-party explorer.
When two parties dispute what a record said, the digest plus the stored copy settles it without either party trusting the other.
Publish the verification method, because a proof nobody can independently check is a claim.
Where this is genuinely worth it
Cross-organisation consent and disclosure records, where neither party can be trusted to hold the only copy of the history.
Not internal audit trails, where a write-once table with proper controls is cheaper and easier to operate.
The test is whether an independent party needs to verify the history without access to your database.
How I do it
One trace of a real case with timestamps at every hop, before any document is written.
A findings list naming the defect, the system, the owner and the date, reviewed monthly.
No attestation I did not test, and no template sold as an assessment.
The anchor record schema
An anchor needs four fields to be useful years later: the digest, the record type, the subject identifier in a form that is not PHI, and the moment of anchoring with its transaction reference.
Store the same four in your own database, keyed to the record they describe, so verification needs one lookup rather than a chain scan.
Without the local table the chain is an immutable list nobody can join to a patient, which is the most common way an anchor design fails quietly.
Choosing a chain
A private chain you operate removes cost volatility and gives control of finality; a public chain gives independent verifiability and a permanent cost model.
The decision follows the counterparty: if the other side will not trust your chain, the public option is the only one that answers the question.
Whichever you choose, write the assumption down, because migrating anchors later is a re-anchoring exercise rather than a configuration change.
Reorganisation and finality
A transaction that appears confirmed can in principle be replaced, and the depth at which that becomes impossible depends on the chain.
Wait for a defined confirmation depth before treating an anchor as final, and record the depth in the verification procedure.
For clinical consent records the wait is cheap; for a live workflow it is not, which is why anchors should trail the transaction rather than gate it.
Audit of the anchor path
The signer service, the queue in front of it and the retry logic are all in scope for the audit, not just the contract.
Log each anchor attempt with its digest, its outcome and its transaction hash, and keep that log for as long as the anchor itself matters.
A gap in the anchor log is indistinguishable from a record that was never anchored, which is the one failure the design exists to prevent.
Operating the chain you depend on
If you run a private chain, you have taken on a service operation: nodes, monitoring, backups, upgrades and a key ceremony. That is not an argument against it, but it is a staffing decision that belongs in the design rather than in the incident log six months later. Two independent nodes with an automated failover, a documented genesis and a tested recovery are the minimum honest setup; a single node on the same host as the application is a database with a decentralised vocabulary.
A public chain avoids the operations and imports the uncertainty: fees move, congestion happens, and the block explorer is not your monitoring. Treat confirmation as asynchronous and design the application so that a record is usable before its anchor lands, with the anchor status visible to whoever needs to know. The worst pattern is a synchronous write path that waits for finality, because it converts someone else's congestion into your outage at the exact moment a clinician is waiting.
Key management for a single signer
A signer key is a bearer credential with no second factor, so the controls around it carry the whole weight of the design. Generate it in a service that never exposes it, restrict the service to a defined set of operations and destinations, and log every signature with the digest it covered. Rotation is a network operation rather than a configuration change: a new address must be authorised before the old one stops writing, and the window where both are valid should be short and deliberate.
The failure to plan for is a lost key with no replacement path, which leaves the anchor history verifiable but the forward path dead. Rehearsing rotation once, on a test chain, with the same people who would have to do it under pressure, produces the runbook and the confidence that a runbook written from documentation never does. It also reveals which of your systems hard-coded the address, which is usually at least one.
Reconciling anchors with records
Anchors and records drift in both directions: a record may exist without an anchor because a write failed, and an anchor may exist without a visible record because the local copy was lost or moved. A reconciler that compares the two sets daily and reports both directions is the operational control, and it is far more useful than a dashboard of successful transactions. The report should be short and named, with each discrepancy carrying an owner and a date.
The reconciler also catches the subtler problem of digest drift, where a record was edited after anchoring in a system that permits it. That is exactly the event the design exists to make impossible, so finding it should page somebody rather than appear in a weekly summary. The three states worth distinguishing are anchored and matching, anchored and mismatched, and unanchored, because each needs a different response and only the second suggests the anchor was worth having.
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 — evm ledger integration, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Data and Ledgers 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.