CHARLES TRINH · TECHNOLOGY ARCHITECT · LAS VEGAS, NEVADA
Charles Trinh — Technology Architect, Las Vegas NV

Independent 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.
What I do
I am an independent technology architect in Las Vegas, Nevada, working where federal regulation becomes production infrastructure. The work is healthcare identity, consent and interoperability: the systems that decide whose record is in front of a clinician, what they were permitted to see, and whether anything can prove afterwards that the disclosure was authorised.
I built and operate a clinical platform that passes the ONC (g)(10) Standardized API test suite at 317 of 317 subtests, covering US Core, SMART App Launch and Bulk Data. The same estate runs eight X12 005010 transaction sets, 104 clearinghouse enrolments across 53 jurisdictions, and a consent ledger that records grant, refusal and revocation as immutable events with no PHI on chain.
That combination — the FHIR surface, the claims rail, the identity layer and the audit trail — is the part most organisations buy separately and then discover does not join up. I work on the joins.
What I am not
I am not a physician, not a radiologist, and not a medical practice. I am not affiliated with any other individual named Charles Trinh, including Charles C. Trinh, MD, an interventional radiologist in Houston, Texas. There is no photograph of me on this site by choice: the TRINH mark is the identity image.
I am a sole proprietor. No LLC, no E&O insurance, and I say so before an engagement rather than after. If your procurement requires either, I am the wrong supplier and you should know on day one.
Where the work concentrates
Interoperability architecture. FHIR R4, US Core, SMART on FHIR, HL7 v2, C-CDA, X12 005010, TEFCA and the QHIN model, the Da Vinci guides, IHE profiles. The engineering question is rarely the standard; it is which system owns patient identity and where a terminology map lives.
Identity and consent. Deterministic-first matching, an enterprise index with survivorship rules and a working unmerge path, consent modelled as directives with periods and categories rather than a boolean, and segment-level enforcement for the categories that legally require it.
Security and compliance evidence. HIPAA Security Risk Analysis under 45 CFR §164.308(a)(1)(ii)(A), control mapping with artefacts rather than assertions, incident-response authoring with a worked precedent, and 42 CFR Part 2 handling.
Cloud and estate operations. A 51-hostname estate on a single AWS account under an active business associate agreement, a 337-table clinical store, Hyperledger Fabric and EVM ledgers, self-hosted mail, and vendor-exit architecture that does not depend on any one supplier surviving.
Technical diligence. For acquirers and investors, where the question is not what the diagram says but what the last ninety days of production error rates say.
How I work
Directly, in writing, with evidence. One week of diagnosis usually produces more than a quarter of steering meetings, because the failure is almost never where the team believes it is — it is in the entitlement check, the attribution table, or a match that returned nothing and logged nothing.
The deliverable is a document that names the defect, the system it lives in, the person who owns it, and the date it will be fixed. Then I check whether the date held, because a remediation plan nobody revisits is a document produced for a purpose and abandoned.
Credentials
Sole proprietor operating as Charles Trinh from Las Vegas, Nevada. ONC (g)(10) Standardized API suite: 317 of 317 subtests passed, US Core, SMART App Launch and Bulk Data included. Eight X12 005010 transaction sets, 104 clearinghouse enrolments across 53 jurisdictions. SAM.gov UEI MVKQW9DKKGB8, CAGE 20KM5, NPI 1194645564. AWS business associate agreement active since 18 August 2026. Founder of MyRxWallet. A proposed USCDI v7 data element for a Patient Digital Identity Credential filed with ONC.
Engagement
Three shapes: a one-week diagnostic that ends in a written defect list with owners and dates; a build engagement with a defined scope and a start and end; or a standing seat at twelve to fourteen hours a week across whatever is most likely to hurt next. 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; $2,500 diligence day; $10,000 per month retainer.
Talk to Charles
Phone 702-559-3489, email charles@trinh.io. Send the thing that is bothering you and the diagram you have; I will tell you within a day whether it is a week of work or a quarter, and whether I am the right person for it.
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. Las Vegas, Nevada 89101.
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
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.
Services in Las Vegas NV
- Technology Architecture for Healthcare, by Charles Trinh
- X12 005010 278 Prior Authorization Architecture
- FHIR R4 Interoperability Architecture in Practice
- Patient Identity and Consent Architecture
- HIPAA Security Risk Analysis Under 45 CFR 164.308
- AWS Architecture for Healthcare Workloads
- TEFCA and QHIN Readiness Work
- Technical Diligence for Healthcare Deals
- Fractional CTO for Healthcare Technology
- MyRxWallet and the USCDI Proposal