fractional cto · decisions · portfolio
Charles Trinh — Fractional CTO

What the role is
A fractional CTO makes the calls that need an accountable executive and unblocks the ones waiting on authority. The value is decision velocity rather than additional hands.
Scope it in decisions per month, not hours per week, because the deliverable is resolved questions.
The first month
Week one is a diagnostic trace of one real transaction. Week two is the gap list with owners and dates. Weeks three and four fix the two items that make everything after them cheaper.
By the end of the month you have a document, two fixed defects, and an answer to whether the rest is a quarter or a year.
Standing rhythm
One portfolio page with owners, dates and status, reviewed monthly, replacing status reporting with a decision instrument.
Vendor commitments and risk acceptance stay with the executive voice, which is the point of having one.
How it ends
The engagement ends when the decisions are being made without me. I would rather say that than be renewed for presence.
Handover is a written capability note and two sessions: one where I run the trace and narrate, one where somebody else does and I say nothing.
Why fractional works at a certain size
A company with three engineers and no executive technology voice needs decisions more than it needs another engineer. A fractional CTO supplies the voice at a fraction of the cost of a full-time hire, and the arrangement works when the decisions are the bottleneck rather than the delivery.
It stops working when the organisation needs somebody in the room every day for delivery, at which point the honest advice is to hire and to use the fractional role for the transition. Saying that early is the difference between a client who renews and one who feels sold.
The three decisions that matter in the first month
Which platform direction to commit to, which vendor commitments to make or defer, and which risks to accept in writing. Those three decide most of what follows, and each has a named owner once the decision is made.
The rest of the portfolio is sequencing. Sequencing is important and it is not a decision; it is the consequence of the three, and a fractional CTO who spends the first month sequencing has avoided the work.
Working with founders
A founder's technical intuition is usually right about the problem and wrong about the mechanism. The useful posture is to test the intuition against the estate and report where they diverge, rather than to correct it in the abstract. Founders accept evidence and resist authority.
Where the intuition is wrong and the evidence is not yet available, say so and name the experiment that would settle it. That is more useful than a recommendation and it keeps the decision with the person who will live with it.
The end of the engagement
The engagement ends when the decisions are being made without you. That is usually visible as a month in which you were consulted rather than asked, and it should be raised before the contract term rather than after.
Handover is a written capability note and two sessions, one where you run the cadence and narrate, one where somebody else does and you say nothing. The silence is the demonstration, and it is the part the organisation remembers.
The portfolio page
One page, owners, dates, status. It replaces status reporting with a decision instrument, and it is the artefact the executive team uses when the conversation is about priorities rather than progress.
Keep it current or stop producing it. A stale portfolio page is worse than none because it invites decisions made on old information.
Vendor commitments
Commitments outlive the engagement and the person who made them. Bring them to the executive voice deliberately, with the exit cost and the renewal date, and record the decision.
Where a commitment is made without the exit path, the record should say so, because the next person will inherit it without context.
Risk acceptance
A risk accepted in a meeting is a risk nobody owns. Put each acceptance in writing with a name, a reason and an expiry, and review the register monthly.
Expired acceptances are findings. The register is only a control if the expiry is enforced.
The transition
The end of the engagement is a deliverable, not an event. Plan the handover from the first month, hand each artefact to a named owner, and leave the organisation able to maintain what it has.
A fractional role that cannot be handed over has not produced a capability, only a dependency.
The first ninety days
Weeks one and two are the trace and the gap list with owners and dates. Weeks three and four fix the two items that make everything after them cheaper, and the organisation sees the difference before it is asked to believe anything.
Month two establishes the portfolio page and the decision rhythm. Month three is the first quarterly review with the executive team, where the three decisions of the quarter are recorded and their consequences stated.
By the end of the quarter the question is no longer whether the role is useful but whether it is still needed, which is the right question and the right time to ask it.
What the role does not do
It does not deliver the work, manage the engineers or stand in for a missing manager. Those are different roles with different measures, and conflating them is how a fractional executive becomes an expensive project manager.
Where the organisation needs delivery capacity, the honest answer is a hire or a partner, and saying that in the first conversation saves everyone a quarter.
Keep a written record of every decision taken during the engagement, with the alternatives considered and the reason for the choice. That record is what the organisation consults after the role ends, and it is what distinguishes an engagement that produced judgement from one that produced presence.
Where a decision is later reversed, record the reversal rather than editing the original. The history of the change is often more useful than the decision itself.
Where the organisation asks for a deliverable rather than a decision, name it as a different engagement. An advisory role that quietly becomes delivery is a role whose advice stops being independent, and the independence is the thing being purchased.
Set the reporting line explicitly at the start, and insist that it is the chief executive or the board rather than the technology team. A fractional executive reporting into the function they advise has neither the standing nor the independence the role requires, and the arrangement fails slowly in a way nobody can attribute.
Where the organisation wants the role to be permanent, say what a permanent hire should look like and help find them. The engagement that ends with a good hire is the one that gets referred, and the referral is worth more than the renewal.
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 cto — 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
- 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.