SERVICES · LAS VEGAS NV

Charles Trinh — Fractional CIO | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Charles Trinh — Fractional CIO, Las Vegas NV
Charles Trinh — Fractional CIO

Fractional CIO work: owning the technology portfolio without owning the org chart, the decisions that need an executive voice, and how the engagement ends.

What the role actually is

A fractional CIO makes the calls that require an accountable executive: platform direction, vendor commitments, risk acceptance and budget. The value is decision velocity, not additional hands.

Scope it in decisions per month rather than hours per week, because the deliverable is resolved questions rather than presence.

Start with the decision backlog

The first task is a list of what has been waiting for someone with authority to say no. That list is usually short, senior and expensive.

Resolve the top five in the first month and the organisation will tell you what the next five are.

Establish the portfolio view

One page with owners, dates and status, reviewed monthly. It replaces status reporting with a decision instrument.

Publish it where the accountable people see it without asking, because a portfolio nobody opens is a report.

Ending it properly

The engagement ends when the decisions are being made without you, and you should say so before the contract term rather than after.

Hand over with a written capability note and a two-week overlap where the successor runs it and you say nothing.

The first month

The first month produces three artefacts: a decision backlog with owners, a portfolio view with dates, and a short list of risks nobody has accepted in writing. Those three are the diagnostic, and they are also the thing that shows the organisation what a decision actually looks like when it is recorded. Without them the engagement becomes advice, and advice without a record is indistinguishable from conversation.

Resist the temptation to reorganise. A new executive voice that begins by changing structure spends its credibility on something that will be judged in a year, when the value was supposed to be visible in a quarter. Structure follows decisions, and the decisions are the first month's work.

Working with the existing technical leadership

A fractional CIO who competes with the existing technology lead creates a second authority and an organisation that routes around whichever is easier. The arrangement that works is explicit: the fractional role owns the portfolio and the vendor relationships, the internal lead owns delivery, and the boundary is written down and reviewed monthly. Where the internal lead wants the executive role, say so and plan for it, because a role held by somebody who does not want it is a role that will be performed badly.

Coach rather than replace where the capability exists. The deliverable at the end of the engagement is an organisation that makes the same decisions without you, and the measure of success is that the meetings run the same way after you leave.

Vendor and contract decisions

The executive voice matters most at renewal, because vendors price against the authority in the room. Bring a position rather than an opinion: what the dependency is worth, what the exit costs, and what the organisation will accept. Record the decision and the reasoning, because the next renewal starts from that record rather than from a blank page.

Where the organisation has no exit path, the negotiation is a formality. Building one, even at modest scale, changes the conversation more than any argument about price.

How the engagement ends

End it when the decisions are being made without you, and say so before the contract term rather than after. The handover is a written capability note and a two-week overlap where the successor runs the cadence and you attend without speaking. The silence is the demonstration, and it is more convincing than any summary.

Measuring the engagement

Four numbers describe whether the role is working: decisions closed per month, the age of the oldest open decision, vendor commitments renegotiated or deferred, and the number of risks accepted in writing. All four are cheap to produce and none of them is a proxy for activity, which is what makes them useful in a review. An engagement that reports meetings attended is reporting effort rather than outcome.

Where the numbers stall, the cause is usually authority rather than effort. The honest response is to say which decisions are not being made and by whom, rather than to add more reporting to compensate for the absence of a decision.

The exit criteria, written down at the start

Write the conditions under which the engagement should end before it begins: the decisions being made without you, a permanent hire in place, or the portfolio in a state the organisation can run. Without those criteria, the engagement either ends abruptly when the budget moves or persists beyond its usefulness, and both outcomes cost the organisation more than the work was worth. Revisit the criteria quarterly, because the organisation's needs change and the criteria should change with them.

What the organisation keeps

The artefacts are the deliverable: the decision backlog, the portfolio view, the risk acceptances and the vendor register. Each is a document the organisation can maintain without the role, and each is written in the organisation's language rather than a consultant's. An engagement that ends with a slide deck leaves nothing; one that ends with four maintained documents leaves a capability.

Hand each artefact to a named owner before the engagement ends, and confirm they can maintain it. A document handed to nobody is a document that will be archived within a quarter, and the work that produced it will have to be repeated.

When the organisation is not ready for the role

A fractional CIO needs a counterpart who can execute, because the role makes decisions rather than delivering them. Where the organisation has no one to carry those decisions into delivery, the engagement produces a portfolio that does not move, and the failure looks like the role rather than the gap. Say so at the start, and where the gap cannot be filled, take a narrower engagement that produces artefacts the eventual hire can use.

The relationship with the finance function

Most technology decisions have a finance component, and an advisory role that ignores it produces recommendations the organisation cannot fund. Work with the finance lead on the cost model for each major decision, so the number that reaches the board has been through the person who owns the budget. The resulting proposal is slower to produce and far more likely to be approved.

What the board should hear

Three items per quarter: what the portfolio costs, what is at risk and what decision is pending. The same three every time, in the same order, so the board can compare across quarters rather than reconstruct the story each meeting. An update that varies in shape is read as activity; one that varies in content only is read as a position.

Where a decision is pending, state the options, the recommendation and the consequence of deferral. Deferral is a decision, and naming its cost is what stops it happening by default.

Keep the three items in a standing paper rather than in slides; a paper that is filed with the board papers becomes the record the next chair inherits.

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 — fractional cio — 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