diligence · claims · measurement

Charles Trinh — M&A Technical Diligence

Charles Trinh — M&A Technical Diligence
Charles Trinh — M&A Technical Diligence

Claims versus measurements

Every architecture claim in a data room is directionally true and materially incomplete. The diligence job is to convert it into a number.

The first number is always the error rate on the last ninety days of production exchange, per counterparty.

What to ask for

The capability statement, conformance results with suite version and date, a production endpoint with test credentials, and the count of partners who have exchanged clinical data in the last thirty days.

Announcements describe intent. Those four describe reality.

The three defects that cost most

A matching layer producing silent false positives, a consent model that is a boolean pretending to be a directive, and an acknowledgement loop that has never been instrumented.

Each is invisible in a diagram and obvious in a week of access.

Pricing the fix

Remediation is a work plan with people, weeks and dependencies, not a risk factor on a slide. Interoperability debt converts to cost unusually cleanly because the fix is usually three named services.

Trace one patient live with timestamps in the first meeting. An organisation that can do that knows its architecture; one that offers a diagram has answered the question.

What a data room cannot tell you

A data room contains documents the seller selected, and the selection is itself information. The absence of an uptime report, a conformance result or a list of production counterparties is not an oversight; it is usually an answer. The diligence job is to notice the absence and price it.

Ask for the four things that cannot be fabricated: a production endpoint with test credentials, the error rate per counterparty for the last ninety days, the count of partners who exchanged clinical data last month, and the name of the person who would take the call at two in the morning. Each produces a fact rather than a narrative.

The claims that deserve a week

Interoperability claims deserve the most time, because they are the hardest to verify quickly and the easiest to overstate. A claim of FHIR conformance should come with a suite version and a date; a claim of payer connectivity should come with enrolments and evidence that claims were paid; a claim of identity matching should come with a duplicate rate and a merge policy.

Where the claim cannot be supported with an artefact, treat it as unproven rather than false. Unproven claims are common and they are not fraud; they are the organisation repeating what it believed when it built the thing. The diligence question is what it would cost to make the claim true.

Pricing remediation as work

Remediation estimates that are expressed as percentages are not estimates. The useful form is a list: this service, this many weeks, this dependency, this owner. Interoperability debt converts unusually cleanly into that form because the fixes cluster in three named services, which means the estimate can be defended line by line.

Include the people in the estimate. Most remediation fails on capacity rather than on design, and the capacity question, who will do this while running the estate, is the one that changes the price.

The diligence opinion

The output is not a score; it is a list of findings with consequences and a recommendation on price or condition. Each finding names the system, the defect, what it would cost to fix and what happens if it is not fixed within a stated period.

Where the acquirer intends to keep the team, say so and price the knowledge transfer, because an integration estate is held together by people and the people leave after a sale unless something is done about it.

The contract questions

Contracts that terminate on change of control, data-return obligations and the identity of the counterparties are the three that most often change the price. Read them before the financial model, because they decide whether the assets transfer at all.

Where a consent is required, the timeline is the diligence finding, since consents take longer than closings and the sequence determines the date.

The people question

An integration estate is held together by two or three people whose knowledge is not written down. Identify them, and price what happens if they leave, because after a sale they often do.

Ask what the last person who left took with them. The answer describes the documentation culture better than any repository review.

The remediation plan shape

A defensible plan has a list, a sequence, dependencies and a capacity assumption. The capacity assumption, who does this work while running the estate, is the one that is most often optimistic and most often decisive.

Price the plan with the people in it. A design-only estimate is a lower bound and it will be quoted as if it were the cost.

The diligence report

Findings with consequences, a recommendation on price or condition, and a stated list of what was not examined. The last one protects both parties and it is almost always omitted.

Write the unexamined list before the findings, because it disciplines the findings and it is what the acquirer will rely on a year later.

How the week works

Day one is the four requests: production endpoint, error rate, partner count and the on-call name. Days two and three trace one transaction end to end with the target's own engineers present.

Day four is contracts and people. Day five is a written findings list with consequences, a price or condition recommendation, and an explicit list of what was not examined.

The judgment the buyer is buying

Diligence is not a checklist outcome; it is a judgement about whether the asset can be operated and what it will cost to make it operable. That judgement depends on having seen a transaction work, which is why the live trace matters more than any document review.

Where the judgement is that the asset cannot be operated without the seller's team, say so plainly and price the transfer of knowledge as the primary remediation item.

Keep the unexamined list with the report and give it to the acquirer in writing. The items that were not examined are the ones the acquirer will discover later, and a document that names them in advance converts a surprise into a known cost.

Where the acquirer declines to fund an examination, record the decision. A diligence opinion that covers what was permitted to be examined is a fair opinion, and the record is what makes that clear.

Where the target's leadership cannot describe its own error rates, that inability is a finding rather than a gap in the answers. An organisation that runs an integration estate and does not measure it is an organisation whose risks are unknown to itself, and the price should reflect that.

Deliver the findings before the exclusivity period ends. Diligence delivered after the deadline is advice about a transaction that has already been priced, and the usefulness of the work is measured by whether it changes a number rather than by whether it is correct.

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 — m&a technical diligence — the scope, the failure modes it prevents and how the work is measured. It sits in the Regulatory and Capital Markets 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh