ADVISORY

Charles Trinh — Fractional CTO for Healthcare Companies | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Decision calendar showing the fractional CTO's weekly cadence and quarterly deliverables
Charles Trinh — Fractional CTO for Healthcare Companies

A healthcare company needs technical leadership before it can afford a full-time CTO, and the gap is usually in decisions rather than in code. I take the seat part-time, own the technical decisions and leave behind a team and a written record that survive my departure.

What a fractional CTO actually does in a week

A fractional CTO does not write the product backlog and does not attend every stand-up. The week is split across a small number of high-stakes decisions, a steady cadence with the engineering lead and a written output. In a typical healthcare company I hold one decision session on the platform and infrastructure choices, one with the compliance lead and the HIPAA security owner, one with the engineering lead on people and process, and one hour of unblocking for whatever is on fire. Everything else is email and a record.

The decisions I own are the ones that are hardest to reverse: the choice of cloud platform and region, the identity and access model, the selection of the clearinghouse or EHR partner, the build-versus-buy calls that define the product for the next two years, and the staffing model. I write each decision with the reasoning, the alternatives and the conditions under which it would change. The engineering lead runs everything below that line without my hand on the wheel, which is the point of the arrangement.

A fractional CTO needs one reliable weekly meeting with the founder or CEO. Without it I am guessing about priority and the founder is guessing about technology. I ask for thirty minutes a week and I use it purely to confirm what must be decided in the coming week. Every other interaction with the founder goes through email or a written message, because the founder's time is the company's scarcest resource and mine is paid by the hour.

Hiring the team that will outlast the engagement

The most valuable thing a fractional CTO does is hire the engineering lead who will take over when the engagement ends. I write the role, run the search, and sit in on the first three interviews before handing the process to the founder. The role is usually a hands-on lead who can also manage a small group, and the job description is specific: what the person owns, what they must decide, and what they can escalate to me. Vague descriptions produce a hire who is surprised three months in.

I set the interview structure for technical roles so that it tests what the job requires rather than general cleverness. For a developer who will build clinical features, the exercise involves a small piece of work with a protected health information boundary, and the candidate is asked how they would test it. For an operations hire, the exercise is reading a runbook and finding the defect. I interview for judgement, not for language knowledge, and I write the scoring criteria before the candidates arrive so the standard does not drift.

Where an organisation cannot afford to hire several senior engineers at once, I help sequence the hires so each one adds a capability the team lacks. The typical order for a healthcare startup is a senior backend developer, an integration developer, a quality and release engineer and a clinical informatics specialist. I do not insist on specialists at the start, but I do insist that the first senior hire understands that patient safety is part of the definition of done, not a regulatory afterthought.

Vendor and platform calls that compound

Every vendor decision a young healthcare company makes is multiplied by the products built on it. The clearinghouse, the EHR partner, the identity provider and the cloud platform each determine how quickly the company can respond to a payer rule change, a customer's data retention requirement or a new market. I run those selections with a structured comparison and I put the evidence in writing, so that when the supplier changes its pricing, the organisation knows what it would cost to leave.

I keep a vendor register with the contract owner on the client side, the contract dates, the data protection terms and the integration state. On a multi-market company this register is the difference between knowing where the data lives and believing you do. The register is updated at every renewal and each renewal is a trigger to re-read the build-versus-buy analysis for the relevant product.

On platform, I am firmly in favour of standard cloud infrastructure with the compliance obligations handled explicitly. The cloud platform decision should be made once and held. Switching clouds once the product is in market is one of the most expensive operations a young company can run, and it rarely returns the money that started the conversation.

How the seat hands over

Every engagement has a planned end and I write the handover into the engagement letter on day one. The handover is a named person, a documented decision log, a staffing plan and an audit trail of what I decided and why. I aim to be running one day a fortnight by the final quarter, and I am not surprised when the engagement ends earlier than planned because the team is ready. A fractional CTO who cannot be replaced is a liability, not an asset.

The content of the handover is concrete. The decision log carries every decision with its trigger. The staffing plan names the open roles and the timeline. The architecture record shows the current design and the pending decisions. The list of open items names the owners and the next review. I walk the whole pack with the incoming lead and the founder in a single session and leave nothing in my head that is not in the documents.

The founder is usually asked whether to hire full-time or to keep the fractional arrangement. My answer is driven by the number of decisions the company will face in the next year and the number of senior people who can make them. When the company will face more than twelve significant technical decisions a year, it needs a full-time CTO. When it will face five or six, a fractional arrangement is cheaper and better, provided the decision record is kept.

What the engagement costs and what it is not

The engagement is charged as a retained part-time service with a stated monthly ceiling on hours. I do not sign a retainer that includes unlimited access, because that produces a consultant who is always available and never finishes anything. The ceiling protects the client as much as me: it forces prioritisation of the decisions that matter and makes the cost predictable for the finance lead. Any work beyond the ceiling is quoted separately and approved in writing before it starts.

I am a sole proprietor, and I say so openly on the engagement letter. I do not claim certifications, insurance cover or a team of consultants that do not exist. Where a client needs a specific assurance I do not hold, I tell them before the contract is signed and we agree how the work will be handled. The founder of MyRxWallet is one of the clients I have served this way, and that company's decisions were kept on exactly this discipline.

A fractional CTO is not a stopgap for an absent technical founder and not a substitute for an engineering manager. The work is the decisions a team cannot make alone and the structure a team needs to make its own. The engagements I run are designed to leave the company with both. When the engagement ends, the test is whether nobody needs me, and if the test fails I say so at the handover.

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 for healthcare companies — 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