ADVISORY
Charles Trinh — Technology Roadmap Planning | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A roadmap that lists what the team will build in order is a project plan, not a roadmap. I build roadmaps that name the capability being built, the decision it lets the company make, the dependency it depends on and what happens if it slips.
The roadmap is the decisions the company will make
I ask the executive team a simple question at the start of every roadmap: which business decisions will this roadmap let you make that you cannot make today? If the answer is a list of features, the roadmap will fill with activity and the people who paid for it will not know whether it worked. I rebuild the roadmap around capabilities: the patient identity and consent layer, the claims eligibility check, the reporting extract for a payer's provider programme. Each capability is defined by the decision it supports and the evidence that the decision is working, not by the tickets under it.
Every capability in the roadmap has a named business owner alongside the technical lead. The business owner is accountable for the decision; the technical lead is accountable for the delivery. When they disagree, the roadmap cannot hide the disagreement; it records it as a decision point with a date. Boards and executive teams get a roadmap where the disagreement is visible and resolvable, rather than a slide that implies a smooth path.
The roadmap has three horizons and no more. The next quarter is committed and resourced; the next three quarters are planned but not committed; the rest is a rough direction. Anything beyond a year is a trend line, not a plan. The single biggest harm in healthcare roadmaps is pretending that the far end is known when new regulations, payer policies and vendor changes will rewrite it. The horizon names that honestly and keeps it in view.
Dependencies are drawn before dates are set
Dates come from capacity and dependencies. Dependencies are usually invisible because they sit outside the team's control: a vendor integration, a customer's data access approval, a certification timeline, a clearinghouse's response to a new transaction request. I draw those dependencies first, then estimate how long the work takes once each dependency is resolved, then set dates. Reversing that order produces roadmaps that look energetic and are reliably wrong at the end.
The dependency list is kept alongside the roadmap and reviewed monthly by the delivery lead I work with. Where a dependency is a person's approval, the request goes out early with a written name and date. Where the dependency is a vendor, the contract or statement of work is checked against the roadmap's timing. In one case I am proud of, a roadmap with eight capabilities proved that three of them depended on the same external approval; that finding let the company negotiate a single package rather than three.
For organisations running a large programme alongside the roadmap, I align the two using the programme dependency register. A roadmap that conflicts with the programme's live dependencies is worse than no roadmap: it gives the executive team confidence that the engineering lead cannot deliver. Alignment is a two-hour exercise once a quarter, and it saves weeks.
Capacity is a budget, not an aspiration
The roadmap is planned against the capacity that actually exists, not the capacity the company wishes it had. I build the capacity estimate from the team's actual delivery record with a buffer for the unplanned work that always arrives. In healthcare that unplanned work is predictable: a customer asks for a change, a payer changes a rule, a security finding requires remediation. I reserve between 20 and 30 per cent of engineering capacity for that class of work, and I am explicit with the executive team that the reserve is not slack, it is operational load.
When a capability is requested that does not fit the remaining capacity, the conversation is about what is dropped, not about whether the team can stretch. I bring the capacity chart to the planning meeting and I ask the executive team the same week to choose which capability to defer. That choice is recorded with the owner's name, and the deferral does not reappear as a surprise later. A roadmap that does not have this conversation is a roadmap where the team quietly loses the buffer and then the schedule.
The capacity estimate also has to account for the skills in the team. A capability that requires a specialty the team lacks, such as healthcare interoperability or clinical decision support in a regulated AI, takes longer than the raw delivery record suggests. I name the specialty in the roadmap and plan the hire or the partner alongside it. Specialist capacity in healthcare is scarce, and a plan that assumes it will appear when needed will slip by a quarter at least.
Quarterly re-plan with written stop conditions
The roadmap is reviewed at the start of each quarter with the executive team, the programme manager and the business owners. The review starts with what was actually delivered, then the dependencies that changed, then the next quarter's commit. The review is not a status meeting; it is a re-plan, and the roadmap changes on the day. A roadmap that does not change at a quarterly review has stopped informing anyone.
Every committed capability has a stop condition: a date by which, if the dependency or delivery is not where it should be, the team pauses and the executive team reconsiders. The stop condition is agreed at the start and recorded with the capability. Without it, the team has no permission to stop and the executive team has no signal that the plan is wrong. Over the course of the delivery the stop condition helps the team avoid the sunk-cost pattern that has ended more healthcare starts than any other pattern I have seen.
The roadmap is a living document owned by the business lead and maintained by the delivery lead and me. It is kept in the same tooling as the work, updated monthly, and archived quarterly. The archived copies are the evidence for a later decision review, and they show what was planned and what was learned. This is the same discipline I apply across my own delivery record, which includes 51 hostnames in a single AWS estate planned and re-planned from the same document.
Roadmaps for regulated change
In healthcare, part of every roadmap should be regulatory change that is already visible: a certified standard update, a new payer transaction, a required security improvement. Those items are not optional and they consume capacity regardless of the product plan. I put them on a separate capacity line that the executive team sees separately, so the product capability plan does not hide behind the regulatory work. The regulatory line is not a wish list, it is the commitment required to keep operations legal.
Where a roadmap requires a certification effort such as the ONC (g)(10) readiness work, the roadmap should treat it as a capability with an evidence chain. The evidence needs months to assemble and the roadmap schedule must include the assembly time, not just the technical effort. I have seen certification work planned as if the technical change was the whole job, and it is almost never the whole job.
The final test of a roadmap is whether it can be explained to the executive team in ten minutes and then used without me in the room. The document that passes that test is rarely the most detailed one. The most useful roadmaps I have delivered fit on one page and answer, in order, what the company can do because of them, which decisions they unlock and what has to happen first.
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 roadmap planning — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance 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.