SERVICES · LAS VEGAS NV

Charles Trinh — Board and Executive Advisory | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Charles Trinh — Board and Executive Advisory, Las Vegas NV
Charles Trinh — Board and Executive Advisory

Technical advisory to a board: translating architecture risk into the language of liability and capital, and telling directors what they are actually accepting.

The board needs consequences

Directors act on exposure and cost. A technical narrative without those two is noise at the wrong altitude, however accurate it is.

Frame each risk as what happens, what it costs, and who is accountable for accepting it.

Bring the register, not the diagram

Read the accepted risks aloud with their owners and expiry dates. A board that hears the accepted risks is making a decision; one that hears a status update is not.

Say plainly which risks are underfunded, because funding is the decision the board can actually make.

Incidents as written reviews

Present incidents as a review with a timeline, an owner and a date, not as a narrative of heroism.

The board's question is whether the same thing can happen again and what was changed, so answer that before it is asked.

Refuse to sign what you did not test

An advisor who signs an assessment they did not test is a liability with a title. The refusal protects the board more than the reassurance would.

Say what you did verify and what you took on trust, in writing, every time.

What the board can actually decide

Directors can approve funding, accept risk, and set the appetite that governs everything below them. They cannot design a control or choose a platform, and advice that asks them to do either is advice at the wrong altitude. The useful contribution is to express each technical question as one of those three decisions, with the consequence attached.

Bring three items per quarter at most. A board that receives a comprehensive technical report reads none of it, and the three items it would have acted on are buried in the fourth appendix.

Expressing risk in consequences

A finding becomes board-relevant when it is described as an event, a cost and an owner. Patient records exposed for six weeks by a misconfigured backup is an event; the notification cost, the regulatory exposure and the remediation spend are the cost; and the acceptance of the residual risk is the owner's decision. That structure survives a board meeting and produces a minute that can be quoted later.

Where the cost cannot be estimated, say so and give the range. A range with a stated basis is more useful than a single number that will be treated as precise and then argued about.

Incidents and the review the board sees

Present incidents as a written review with a timeline, the decision points, what changed and the owner and date of each change. The board's question is always whether it can happen again, so answer it before it is asked. A narrative of the response team's effort is informative about effort and silent about risk.

Where the same class of incident recurs, say so plainly. The second occurrence is a governance question rather than an operational one, and it is the board's responsibility to hear it framed that way.

The advice that is refused

Declining to sign an assessment you did not test protects the board more than reassurance would, and it is the behaviour that makes the rest of the advice credible. Say what you verified, what you took on trust and what you would need to verify before signing anything.

Record the refusal with the reason. A documented refusal is evidence that the board was told, and the record protects both parties when the question is asked later.

The quarterly rhythm

Four meetings a year with a fixed agenda is enough: the risk register with its acceptances, the incidents and their reviews, the funding decisions pending, and the one strategic technical question the board should be thinking about. The fixed agenda is what makes the advice comparable across quarters, and it is what lets a new director understand the position from the last two sets of papers.

When to say no

Some requests are outside the advisory role: signing an attestation, approving a control design, or providing a reference for a vendor relationship. Saying so plainly, with the reason, preserves the standing that makes the rest of the advice useful. An advisor who says yes to everything becomes a service provider, and the value of the independent voice disappears at the moment it is most needed.

Where the board wants a technical opinion on a decision it is about to take, give it with the uncertainty stated. Directors are used to uncertainty in their own fields and they are poorly served by an advisor who does not distinguish between what is known and what is believed.

Working with the executive team

The board's technical advisor is often the only person in the room with an independent view of the executive team's claims, and that position requires care. Contradict the chief executive in private before the meeting, and in the meeting only if the matter is material and the correction is unavoidable. An advisor who wins the argument and loses the relationship has done neither job.

Where the executive team is not supplying the information the board needs, say so to the board chair rather than to the board. The chair can require the information; a public complaint at a board meeting produces defensiveness rather than documents.

Keep a private note of what was said and what was decided, and share it with the chair. The note is the institutional memory of a role that is by design temporary.

Confidentiality and the paper trail

Advice given to a board is confidential in a way that ordinary consulting is not, and the paper trail should reflect that: a written note of the advice, who received it and the date. The note protects the advisor if the advice is later misdescribed, and it protects the board by making its reasoning findable during the next inquiry.

Where the request is for an opinion that will be quoted externally, decline unless the request comes with the context and the review the quote deserves. An isolated sentence is easy to misuse and difficult to correct.

The annual review of the advisory itself

Once a year, review the advisory against its own purpose: were the questions that mattered asked, was the board better prepared, and did the accepted risks change. A role that cannot describe its effect in terms the board recognises is a role that will be cut at the next budget round, and the review is the opportunity to make the case with evidence rather than with reputation.

Where the answer is that the advisory added little, say so. The honesty is worth more to the relationship than another year of attendance.

Keep the review short and specific: three questions, the answers given, and what changed because of them. That record is also the evidence the chair needs when the role is questioned, and it is more persuasive than any description of influence.

Record the date of that review alongside the register, so the two records together show what the board was told and when it was told.

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 — board and executive advisory — the scope, the failure modes it prevents and how the work is measured. It sits in the Advisory 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