ADVISORY
Charles Trinh — Build versus Buy in Healthcare | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Healthcare software decisions are rarely about features. They are about who owns the compliance evidence, who carries the integration cost and who is liable when a payer rule changes. I make that comparison explicit before the procurement runs.
Features are the least useful comparison axis
Vendor demos show the features the vendor built for someone else. Build proposals show the features the team wants. Neither tells the decision maker what will decide whether the system is still working in three years. In healthcare the deciding axes are different: who owns the compliance evidence, who absorbs the integration cost with the clearinghouse and the EHR, how a regulatory change reaches the software, and what it costs to leave. A build-versus-buy analysis that does not put those first is a decoration.
I start the analysis by writing the four or five operational questions the system has to answer, in the language of the operations team. Coverage verification, eligibility, claim status, patient statement generation: each question is on one line with the data it needs and the system of record that supplies it. The features follow from the questions. The comparison then scores each option on whether it can answer the questions under the organisation's actual constraints, which are usually fewer staff than the feature list assumes and a compliance team that cannot take on a new evidence obligation.
I score options separately for the first six months and for years two to five. Software that looks cheap on a three-month pilot often costs multiples of that once it is in daily use and the integration, training and support are counted. Most of the cost of a held decision comes in the second and third year, and the decision paper argues those years explicitly.
Who holds the compliance evidence
For a vendor, compliance evidence is their product. For a build team, it is one more thing to produce, and it is usually the first thing dropped when delivery pressure rises. I ask every vendor for the exact artefacts I would need to rely on them: their HIPAA policy set, their BAA wording, their SOC 2 report if available, the scope of their security assurance and the evidence they would hand over if a covered entity audited the relationship. For an internal build, I write the same list and ask who inside the organisation will produce and maintain each item.
Where a vendor holds the evidence, the organisation is buying a compliance posture and should price it as such. It is also buying a dependency: a change of vendor means re-negotiating the BAA, re-validating the integration, and re-proofing the posture. Where the build team holds the evidence, the organisation keeps control but carries the maintenance burden forever. On a HIPAA security programme this question is the central one, and getting it wrong is expensive in both directions.
I never accept a vendor's answer to 'what if the payer rule changes' without an example. Ask them to show the changes they made last year, the dates, and who paid. The build team has the same obligation: show the changes they made last year and how long each took. A vendor that has absorbed several annual payment rule changes has demonstrated a competence the build team may not have yet; a build team that has shipped a rule change in three weeks has demonstrated the opposite.
Integration cost is where the estimate usually breaks
The integration between the candidate system and the rest of the estate is usually the largest single cost in a build-versus-buy decision, and the one most often rendered as a single line in the business case. I break it into the contracts, the message formats, the error handling, the retry behaviour and the operational support. For healthcare systems that touch clearinghouses or the EHR, the integration work is rarely less than the bulk of the build work, and for a vendor it is rarely zero because the vendor will charge for it too.
I ask each side for an integration estimate with assumptions listed. The classic assumption is that the existing system already has the interface; it usually does not, or it exists only in a format only one vendor supports. I check by reading the existing interface definitions and asking the operations team who they ring when a transaction fails. If the answer is a person in another department with no formal responsibility for it, the integration cost is not in the estimate and the estimate is wrong.
In the build option, the integration is the team's problem. In the vendor option, it is the vendor's problem, but the vendor's contract usually limits liability to a support credit, not to the operational impact. A claims feed that fails on a Friday evening costs the organisation its weekend. I put that scenario in the decision paper explicitly with the contractual route to recovery for each option, and I put it in front of the finance lead, not just the technical team.
Lock-in is the cost of the exit, priced today
Lock-in is not a feeling. It is a number with a date. I quote it as the cost and duration of leaving an option in year three: the data export formats the vendor supports, the migration work to move to an alternative, the contract notice periods and the staffing to run the system in the interim. Where the vendor supplies a standard, check it against the standard rather than the vendor's claim. An X12 005010 export that omits the response codes is not a standard export.
The build option has its own lock-in: the team's skills, the architecture and the operational knowledge. A small organisation that builds and then loses its two principal engineers carries that cost in its own exit. I price that in the same terms: who would maintain it, how long it takes them to become productive and what they cost. Where the built system is in a standard cloud platform with ordinary tooling, the cost is lower than where it relies on bespoke infrastructure only one engineer understands.
For an organisation deciding its first system, the eight X12 005010 transaction sets I have worked with across claims and remittance are the eventual integration scope, and the decision paper should state which of them the option handles today, which it can add and at what cost, and where none of them are handled without work. A build team that can name this set on day one is more credible than a vendor whose feature list does not mention it.
Who decides and how the decision gets recorded
The build-versus-buy decision has an executive owner, a technical leader and an operations leader, and each signs a specific section of the paper. The executive signs the cost and lock-in section. The technical leader signs the integration and build feasibility section. The operations leader signs the compliance evidence and the ability to answer the questions section. Where one person signs everything, the decision is being made on incomplete information and the paper does not reflect it.
I write the decision as a recommendation with the reasons that would change it. The paper, no longer than four pages, records the options considered, the scores, the assumptions and the conditions under which the recommendation should be reopened. If the payer rules change, the vendor exits, or the build team loses its lead engineer, the paper says what to do. That is how the decision keeps its validity past the meeting in which it was made.
The decision is recorded in the same decision log as the rest of the programme, and the programme manager and the architect both contribute evidence. The cost of getting this wrong is not a failed project, it is a system in production that nobody can price, leave or evidence. The paper exists to make that cost visible before anyone is committed.
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 — build versus buy in healthcare — 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.