SERVICES · LAS VEGAS NV
Charles Trinh — Interim Architecture Lead | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Stepping in as interim architecture lead: stabilising a stalled programme, running the review board, and leaving the artefacts that let a permanent hire succeed.
Stabilise before redesign
The first month is diagnosis and unblocking, not a new target architecture. A stalled programme usually has three defects and two decisions nobody would make.
Ship the defect list with owners and dates before proposing anything structural, because credibility comes from the first three things that actually get fixed.
Run the board with a written log
Convene the review board with a standing agenda and a decision log from the first session. Decisions that are not written down are re-litigated by whoever missed the meeting.
Name what is above your authority and route it explicitly rather than absorbing it silently.
Document the current state honestly
The incoming lead inherits whatever you leave. An honest current-state document is worth more than an aspirational target diagram.
Include the things that are wrong, with dates, because discovering them later costs the successor their first quarter.
Hand over with overlap
Plan a two-week overlap and a written capability note covering decisions, contacts and open risks.
Leave the queue in a state where the next person's first week is execution rather than archaeology.
The first two weeks
The first two weeks are interviews and evidence rather than documents. Talk to the people who are blocked, read the last three incident reviews, and look at what the pipeline says about the deployment cadence. The picture that emerges is usually different from the one in the programme's status report, and the difference is the engagement.
Write a one-page current state at the end of week two and circulate it for correction rather than for approval. Corrections are the fastest way to learn what the organisation believes, and the document becomes shared ground for everything that follows.
Unblocking without redesign
Most stalled programmes are waiting on two or three decisions and one piece of work nobody owns. Resolving those in the first month produces more momentum than a new architecture, and it earns the standing to propose one afterwards. Track the unblocking as a list with owners and dates, and report it weekly in the same format every week.
Where a decision belongs above your authority, route it with a recommendation and a deadline. An escalation without a proposal is a complaint, and it will be treated as one.
The review board
Run the board with a standing agenda, a decision log and a rule that anything not written down did not happen. The log is the artefact that makes the architecture function work, because it converts a series of discussions into a record that can be cited when a team proposes something the board already rejected.
Keep the board small and keep the decisions reversible where they can be. A board that decides everything becomes a bottleneck, and a board that decides nothing becomes a forum.
Leaving it operable
The handover is a current-state document, a decision log, an open-risk list and a named successor with two weeks of overlap. Include the things that are still wrong and the reasons they have not been fixed, because the successor will otherwise rediscover them at the cost of their first quarter.
End by reviewing your own decisions with the successor. The ones that look wrong in hindsight are the most useful thing you can leave behind.
The judgement calls
An interim lead is judged on the decisions taken in the first ninety days, not on the documents produced. The judgement calls that matter are which programmes to stop, which to fund and which to leave alone, and each of them will be contested by somebody whose work is affected. Making those calls explicitly, with the reasoning written down, is what distinguishes leadership from facilitation.
What good looks like at handover
The successor should be able to answer four questions from the artefacts alone: what is running, who owns it, what is broken and what is planned. If any of the four requires a conversation to answer, the handover is incomplete and the first month of the permanent lead will be spent rebuilding context rather than delivering. Test it by asking the successor to answer the four before the overlap ends, and fix whatever they cannot answer.
Keep the handover document short enough to be read in an hour. A comprehensive handover is a document nobody reads, and the four questions are the whole requirement.
Working with the programme office
The programme office usually holds the schedule and the risk register, and an interim architecture lead who ignores it produces a second set of both. Work through the existing instruments where they exist, and where they are not fit for purpose, fix them rather than replacing them. The fix is visible, the replacement is a political act, and only one of the two is likely to survive your departure.
Where the office reports green on a programme that is not, the disagreement is the first finding. Raise it in writing with the evidence rather than in a status meeting, because the written record is what changes the report and the meeting is what changes the relationship.
Setting the bar for evidence
The interim role sets a standard by what it accepts. A board that accepts a status report without numbers will receive reports without numbers, and the acceptance is the precedent. Ask for the metric, the date and the owner on the first report that lacks them, and the second report will include them.
Ending well
The final month should be quieter than the first, not busier. If the successor is still asking daily questions at the end, the handover failed earlier and the overlap should be extended rather than compressed. Plan the end at the start, and tell the organisation what the quiet final month means, so it is read as success rather than disengagement.
Leaving the standard behind
The most durable thing an interim lead leaves is the standard for what counts as a decision, an owner and a date. If the organisation keeps that after the engagement, the architecture function survives changes of personnel; if it does not, the next investigation rediscovers the same three problems. Write the standard down as a one-page template for decisions and reports, and use it consistently in every meeting you chair.
A template that is used is a template; one that is filed is a suggestion. The consistency is the mechanism.
The decisions you should not make
Some decisions belong to the organisation rather than the interim lead: the choice of permanent leadership, the strategic bet, the level of risk appetite. Making them on the organisation's behalf produces a decision nobody owns after you leave, and the ownership is what makes it stick. Name them explicitly at the start, and route them to the body that should decide.
Where the organisation asks you to decide anyway, decide and record that the authority was delegated, with the date and by whom. The record is the difference between leadership and assumption.
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 — interim architecture lead — 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
- 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.