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

Designing for the ability to leave: export formats, contract clauses that make exit possible, and the test that proves the exit path works before you need it.
Exit is an architecture property
A system you cannot leave is not resilient regardless of how many regions it spans. The dependency is the risk, not the availability zone count.
Exit cost is set by the vendor after you commit unless the clauses exist before you sign.
Get a sample export, not a promise
Require a documented export format and a real sample during evaluation. A slide promising portability is not portability, and the difference is discovered at the worst time.
Test one full export and a re-import annually, because an untested exit path is a belief.
Keep what only you can hold
Retain the identifiers you would need to operate elsewhere: domains, certificates, phone numbers, IP ranges and API credentials you founded.
Where the vendor controls those, negotiate control or a documented transfer process at renewal.
Write the runbook while things are good
Document the exit sequence while the relationship is healthy, because it will be needed when it is not and the people who knew will have moved.
Name who authorises the exit and who signs off completion, since an exit without an owner drifts.
Exit cost is a design input
Every vendor dependency has an exit cost, and the design decision is whether that cost is known and bounded or unknown and open-ended. A dependency whose data can be exported in a documented format and re-imported elsewhere has a bounded cost; one whose data exists only in the vendor's model has a cost the vendor sets after you commit. Naming the cost in the architecture makes it a decision rather than a discovery.
Rank the dependencies by what leaving would cost in time and money, and review the ranking when a contract renews. The top of that list is where the negotiation effort belongs, because that is where the leverage is worth the most.
Export formats and samples
The format matters more than the promise. Ask for a sample export during evaluation and compare it to what you would need to operate elsewhere: identifiers, relationships and history, not just the current state. An export that loses the relationships between records is a backup, not a migration path, and the difference is discovered when the model has to be rebuilt.
Record the sample and the date with the contract. When the vendor changes the export format, the comparison is a fact rather than a memory, and the change is visible before it is urgent.
Identifiers only you can hold
Domains, certificates, telephone numbers, IP ranges and API credentials are the assets that make an exit possible, and each can be held by a vendor by default. Found them in your own name where possible, or negotiate a documented transfer process, and record where each one currently lives. An exit that cannot take the identifiers is an exit that leaves the customers behind.
Review the custody of those identifiers at every renewal, since a vendor absorbed by another may quietly move registrations. The check takes an afternoon and it is the difference between an exit and a new company.
The runbook while the relationship is good
Write the exit sequence while the relationship is healthy, because it will be needed when it is not and the people who knew the details will have moved. The runbook names the data, the format, the dependencies, the identifiers, the people to contact and the order of operations, and it names who authorises the exit and who signs off completion.
Review it annually against the current contract and the current architecture. A runbook that describes last year's integration is a document that will cost a week at exactly the moment a week is unavailable.
Testing the exit
Test one full export and a re-import annually, into an environment that is not the vendor's. The test proves the format, the time and the gaps, and it produces a number that can be quoted in a negotiation. An untested exit path is a belief, and beliefs are what vendors price against.
Record the result with the date. A documented successful test is also an argument at renewal, because the vendor knows the customer can leave and prices accordingly.
The contract clauses that decide it
Exit lives in four clauses: the data return obligation, the format and timescale for return, the transition assistance period, and the price of each. Read them together, because a generous return obligation at an unspecified price is not generous. Negotiate the format and the timescale as scheduled items with dates rather than as prose, since a clause with a date is enforceable and a clause with an intention is not.
Where the vendor will not agree, that refusal tells you what the dependency costs, and the number should go into the register with the date of the conversation. A known cost is a decision; an unknown one is a surprise, and the whole discipline is about converting the second into the first.
Re-read the clauses at renewal, because terms are updated by incorporation and the version that governs may not be the one you signed.
Portability in the architecture itself
Keep the vendor-specific code in one adapter with a documented interface, so the system that depends on it depends on the interface rather than on the vendor's SDK. That single decision is what makes an exit a translation exercise rather than a rewrite, and it costs little when made early and a great deal when retrofitted.
Test the adapter against a second implementation once, even a trivial one. The test proves the interface is real and not merely named after the vendor it wraps.
The people who know how to leave
An exit needs somebody who knows the data model, somebody who knows the contract, and somebody with authority to commit the spend. Those are usually three people, and the runbook should name them with a deputy each. A plan that depends on the person who wrote the integration is a plan with an unstated expiry date.
Run the exit once as an exercise, at a small scale, with those three people. The exercise produces the timeline, the cost and the list of things nobody expected, and it is the only rehearsal that counts.
Keep the exit runbook with the contract rather than with the architecture notes, because the person who needs it is usually reading the contract.
Where the vendor is the only holder of a format definition, obtain it in writing. A format documented only in the vendor's documentation is a format that will be described differently at exit.
Keep the exit test result with the contract renewal file, since the renewal is when it is most useful.
Review the adapter's interface once a year against the vendor API you actually use, since the two drift and the drift is the first sign that an upgrade is about to become an exit.
Store the exit plan with the contract and review it at each renewal; a plan filed under architecture is a plan nobody reads when the renewal arrives.
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 — vendor exit architecture — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations 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.