ADVISORY
Charles Trinh — Technical Programme Management | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Programme management on clinical and financial systems is failed mostly at dependency boundaries, not inside teams. I run the dependency register, the decision log and the release calendar that keep a multi-team programme moving without weekly escalation.
The dependency register is the programme
When I take over a large programme, the first document I open is the dependency register, and it is usually a spreadsheet that stopped being true six weeks ago. Every item needs an owning team, a delivering team, a date, a status that is updated weekly, and a named person accountable for chasing it. I rebuild it with those five fields and one rule: an item is closed only when the consuming team confirms it, never when the producing team says it is done. That single change exposes the gaps that programme reports were hiding.
Dependencies between a patient experience team, a claims engine and a platform team are not tidy. The claims team waits for a member eligibility feed, the platform team waits for the claims team's data contract, and the contract waits for a decision nobody scheduled. I draw those chains out on one page and walk it with each team lead. Most programmes have between fifteen and forty live external dependencies, and in my experience roughly a fifth of them are not started a fortnight before they are needed. Knowing that number is the difference between a re-plan and an incident.
The register lives in the same tool as the work, not in a separate programme tracker. I have watched two-tracker programmes where the delivery board was green and the integration environment was empty. When the register and the tickets are the same objects, a dependency cannot go red in one place and stay green in the other. I set the weekly cadence with the relevant leads around the register rather than a status meeting, so the conversation is about the specific item and the specific blocker.
Decision logs stop the same argument from returning
Programmes re-decide the same questions because the decision was never written down or, worse, was written down by the wrong person. I keep a decision log with one row per decision: date, question, options considered, decision taken, decision maker, and the trigger that would reopen it. The decision maker is a person, not a committee. When the log lacks a name, the decision will drift within a fortnight, and the drift will show up as two teams building incompatible things.
I introduce the log at the kickoff of a new phase and ask each workstream to contribute the ten decisions they think will matter most. That exercise usually reveals disagreements that have not surfaced yet. The log is reviewed at the start of every release planning session, and open decisions without a deadline get one assigned in the meeting. On programmes with regulatory dependencies, the log also captures which decisions touch a compliance obligation, so the evidence trail can be assembled without a second pass.
Where a decision genuinely needs a technical opinion rather than a management one, I bring in the fractional architect for a short written recommendation. That keeps the programme decision log a management artefact with technical inputs, rather than a place where technical opinions are argued by veto. The log and the dependency register together are what a new team member reads on day one to understand where the programme actually is.
One release calendar, one person who owns it
Multi-team programmes fail at release time because the release calendar is an aggregation of each team's plan rather than a plan. I own one calendar that names every external release, its consuming teams, its rollback window and its freeze periods. It is published a quarter ahead and locked a fortnight before each date. Any change after the lock requires the programme lead's approval and a written reason, and the reason is logged. The calendar is the only place a release date is authoritative; team documents defer to it.
Release readiness checks are run from the calendar, not from memory. Each release gets a checklist: environment availability, data migration status, training for any clinician-facing change, on-call cover for the window and a tested rollback. I run the first three or four of these checklists myself alongside the team lead, then step back and audit one per quarter. The failure mode I see most is a migration that ran in staging but was never rehearsed against production volumes.
Freeze periods matter more in healthcare than in most industries. Clinical users are on shift over weekends and holidays, and a failed release at 2 a.m. on a Saturday makes its way straight into patient care. The calendar makes those periods visible to the whole programme, which is harder than it sounds when the programme has vendors who plan on their own schedule. I negotiate the freeze windows with those vendors in writing before the quarter begins, and the calendar carries the contract reference.
Risk register with named owners and a revision cadence
A programme risk register without owners is a list of worries. Every risk I enter has a named owner, a current score, a mitigation with dates and a trigger that escalates it. The score is reviewed at a fixed fortnightly rhythm, and a risk whose score rises gets its owner into the next steering session rather than waiting for the monthly report. Owners rotate with personnel changes and the handover is logged so a new owner cannot inherit an unowned risk.
The risks I watch most carefully are the quiet ones. A vendor integration whose test keys never arrived, a data contract that has never been validated against real records, a team that has been told to start without a documented interface. These rarely appear at the top of any scorecard; they surface as surprises a week before go-live. I probe them in the weekly register, ask each team lead what they are least confident about, and log the answer. The person who answers that question honestly is the person I trust to flag the next one.
I bring the risk register and the dependency register together into a one-page programme summary for the executive sponsor every month, with a short list of the three things that need their attention. The programme summary is a page, not a deck, and the sponsor's calendar is preserved. That is how the programme keeps its escalation path open without turning the sponsor into a second programme manager, and it is how a 51-hostname AWS estate lands on production without a release-night scramble.
When the programme has to be re-planned
Almost every multi-team programme is re-planned at least once, and the re-plan is usually triggered by a dependency that moved or a decision that reversed. I treat that as normal. The re-plan uses the dependency register, the remaining decisions and the resource calendar, and it produces a revised release calendar with the same format as the original. Re-planning on the same artefacts is what makes the change legible to the people who need to adjust their own work.
In a re-plan I do not pretend the work is unchanged. Teams have to drop scope, and the sponsor has to choose what is deferred. The choice is documented in the decision log with the sponsor's name against it, so the deferral does not reappear later as a missing feature discovered at go-live. The programme should not hide its trade-offs, and the decision log is the record that a trade-off was made and by whom.
When the programme ends, I hand over the register, the decision log, the calendar and the risk register as living documents with named owners. A programme that leaves these documents behind as a tidy archive is a programme whose successor will rebuild them from scratch. My delivery record inside MyRxWallet covers 104 clearinghouse enrolments across 53 jurisdictions, and that work ran on exactly this discipline: one calendar, one decision log, one register that never went stale on the release owners' watch.
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 — technical programme management — 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.