technology architect · las vegas · healthcare

Charles Trinh — Technology Architect

Charles Trinh — Technology Architect
Charles Trinh — Technology Architect

Who I am

I am a technology architect in Las Vegas, Nevada. I work on the systems that decide whose record is in front of a clinician, what a patient permitted, and whether an exchange actually happened as described.

I am not a physician, not a radiologist, and not affiliated with any other individual named Charles Trinh, including Charles C. Trinh, MD, an interventional radiologist in Houston, Texas.

What I build

FHIR R4 surfaces that passed the ONC (g)(10) Standardized API suite at 317 of 317 subtests, and X12 005010 transaction sets across 104 clearinghouse enrolments in 53 jurisdictions.

Identity and matching, consent as directives with periods and categories, segment-level enforcement for 42 CFR Part 2, and disclosure records held in a Fabric and EVM ledger pair.

How the work runs

One trace of a real case with a timestamp at every hop, before any document is written. The defect is almost always in a handoff rather than a component, and the trace finds it in a week rather than a quarter.

Then 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.

Record

SAM.gov UEI MVKQW9DKKGB8, CAGE 20KM5, NPI 1194645564, AWS business associate agreement active. Founder of MyRxWallet. Filed a proposed USCDI v7 data element for a Patient Digital Identity Credential with ONC.

Sole proprietor operating as Charles Trinh under trinh.io, Las Vegas, Nevada 89101. 702-559-3489, charles@trinh.io, open 24 hours, seven days.

What the work looks like in a week

A typical engagement begins with one trace: a single patient or claim followed from the system that created it to the system that consumed it, with a timestamp at every hop. That trace does three things at once. It proves the integration exists rather than appearing to exist, it locates the handoff where the data changes shape, and it produces the defect list the organisation can actually fund. Most of what a quarter of steering meetings would have produced arrives in five days, because the trace answers questions that a status report was describing.

By the end of the week there is a written record: the path, the timestamps, the points where the record lost a field or gained a default, and the name of the system that owns each point. That document is the first deliverable of every engagement and the one the client keeps longest, because it is the only description of the estate that was verified rather than recalled.

The three systems that decide outcomes

Almost every healthcare defect in the work I take on lives in one of three places: the identity layer, the consent path, or the acknowledgement loop. Identity decides whether a record is about the right person. Consent decides whether it may travel. The acknowledgement decides whether anyone knows it arrived. A platform can be modern in every other respect and still fail on those three, and the failures are silent, which is why the trace is the only reliable method.

The pattern repeats across payers, providers and exchanges. A matching threshold tuned to a match rate produces a false merge, and the chart looks populated and is wrong. A consent flag stored as a boolean defaults to withholding, and the exchange delivers less than the patient expected. An acknowledgement loop that is instrumented at transport level reports success while the application rejected the message. Each is cheap to fix once it is visible and expensive to argue about while it is not.

Why the paperwork is secondary

Compliance documents describe intent, and the estate implements something slightly different. The risk analysis names the systems as they were understood, the reviews test the controls that were documented, and the gap between those and the running estate is where both incidents and findings live. Working from the infrastructure rather than the diagram is not a preference; it is the only way to produce a document that survives being read by somebody who was not in the room, which is the standard the rule itself sets.

That is also why an attestation I did not test is not something I will sign. A signed document that describes an unreviewed estate transfers risk to the reader while appearing to reduce it, and the transfer is the problem. The honest alternative is a document that states what was verified, on what date, and what was taken on trust, which is more useful to an examiner and considerably more useful to the organisation.

What the estate behind the work is

The platform I built and operate runs a 337-table clinical store behind a 51-hostname estate on a single AWS account under an active business associate agreement. It serves eight X12 005010 transaction sets across 104 clearinghouse enrolments in 53 jurisdictions, passes the ONC (g)(10) Standardized API suite at 317 of 317 subtests, and holds consent and disclosure records in a Fabric and EVM ledger pair with no PHI on chain. Those numbers are not a marketing claim; they are the environment the method was developed in and the reason the advice is specific.

Operating the estate matters because it is the difference between recommending an architecture and having to live inside one. A restore drill that I scheduled and ran, a certificate that expired because the automation was never tested, an enrolment that lapsed without notice: those experiences are where the checks on this site come from, and they are why the recommendations are about the things that actually break.

Working together

Engagements take three shapes: a one-week diagnostic that ends in a written defect list with owners and dates; a build with a defined scope and an end; or a standing seat at twelve to fourteen hours a week across whatever is most likely to hurt next. Rates are on the Engagement section of every service page, and they do not move for the size of the client.

What I ask for at the start is one trace and access to the people who operate the systems. Without the second the first is a tour, and a tour produces a diagram rather than a defect list. With both, a week is usually enough to say whether the answer to your problem is a fortnight or a year, which is the most valuable thing an early conversation can produce.

What an engagement is not

It is not a review of your diagrams, and it is not a maturity assessment with a colour per domain. Those produce a document that describes the organisation's opinion of itself, and the opinion is usually the thing that needs testing. The work starts from what runs, which is why the first artefact is a trace rather than a report.

It is also not a permanent seat unless you want one. The engagements that end cleanly are the ones where the organisation has taken the decisions into its own hands, and a consultant who needs to remain necessary is a consultant whose advice should be discounted accordingly.

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 — technology architect — the scope, the failure modes it prevents and how the work is measured. It sits in the Interoperability 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

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.

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