ADVISORY
Charles Trinh — Technical Due Diligence for Healthcare Acquisitions | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A healthcare acquisition's technology risk is mostly in the evidence the target cannot produce. I read the code, the cloud estate, the integrations and the compliance trail, and I report what a buyer is actually inheriting and what it will cost.
Start with the evidence that should already exist
Due diligence begins with the documents a functioning healthcare technology company should be able to produce without preparation: a system inventory, a data map of where protected health information lives, a record of when each BAA was last reviewed, an incident log, a list of live integrations and their owners. I ask for these before any access is granted and I note the response time for each. A target that cannot produce a system inventory in a week is telling me something about its operational maturity that no code review will contradict.
I compare the evidence to the cloud provider's own console. A cloud account that is claimed to be in one region often has resources in another. A backup policy claimed to be tested often has no restore record in the audit log. I run a short set of console queries rather than trusting screenshots, and I ask for read-only access to the accounts in a supervised session. When access is refused on reasonable grounds I note it as a finding rather than as a red flag; many small targets have not organised their access provisioning yet.
Every finding is written with a reference to the observation that supports it, a severity and a rough remediation cost. A finding without an evidence reference is not a finding, it is an opinion, and a banker will mark it down on the first pass. My report is built so that each material item can be read by a non-technical buyer and each evidence reference can be handed to their engineers to reproduce.
The code and its owners
Code quality in a target is less about style than about maintainability by anyone other than its authors. I look at the ratio of internal to external contributors, the age of the most recently touched files versus the age of the most frequently touched, the test coverage of the parts that extract or transmit protected health information, and the history of the applications that have no active maintainer. A single engineer who is the only one who understands the billing pipeline is a continuity risk that I price into the deal.
I read the parts of the code that handle identity, authorisation, audit logging and data extraction myself, because these are where compliance harm happens and where a superficial review misses the important defects. I check whether audit events are written with the user, the action, the record and the timestamp, and whether the logs are retained under the target's policy. Where the target has built on an AI component, I check how its outputs are governed and whether they are reviewed by a clinician before they reach a patient.
The code review also produces a list of the licences and open-source dependencies that could create an obligation on the buyer. The right time to find a licence problem is before funds transfer. The right person to find it is the buyer's counsel, and the technical review gives them the list.
Integrations are where the target's value actually lives
A healthcare technology company is mostly a set of integrations: the EHR, the clearinghouse, the laboratory, the payer portals, the identity provider and the data warehouse. Each integration is a contract and a dependency. I map them with the counterparty, the protocol, the volumes, the error rates and who on the target's side owns the relationship. Then I check which integrations are contractually assignable to the buyer, which need a consent and which will lapse on a change of control.
An integration that is lived-in is worth more than the software that consumes it. I look at the volume history, the recent failure record and the partnership terms. Where the target can show a change of payer rule or clearinghouse spec being handled in a short window, that is evidence of a working relationship the buyer is acquiring. Where it cannot, the integration is a liability with a value attached. I do not confuse a long-standing integration with a healthy one.
I map every integration to the data that flows across it and the data flow that the target's own privacy documentation says exists. Discrepancies between the two are the most common serious finding I make in diligence. A data flow that is documented but not implemented is easy to fix. An implemented data flow that is not documented is a compliance exposure that has been happening for months or years, and it is priced differently.
Cloud, backups and the operational reality on day one
The cloud estate is where a target's operational maturity is easiest to see. I look at the account structure, the identity model, the network boundaries, the key management and the backup and restore processes. A target with a single cloud account used by everyone has weak segregation. A target with backups that have never been restored has weak recovery. A target with root keys in a shared document has weak everything, and the buyer inherits that on completion.
I run a restore of a representative backup in a supervised session inside the target's cloud, and I check whether the restore produces a usable system or just files. Where the target is running on a platform with a service catalogue, the backup restore drill for backup and restore can be run as a joint exercise with the buyer's operations team. The result goes into the report with the measured restore time and the tests that failed.
I also test the target's monitoring and alerting by looking at what was alerted in the last quarter and what was missed. A target without a monitoring dashboard that any operations person can read on day one will not be running the new system safely on day one either. The report names the operational roles the buyer will have to fill, and how long it will take to fill them.
The report is a pricing tool, not a verdict
The final report is structured as a list of material findings with evidence, a list of items to verify further and a list of questions for the seller. It does not recommend whether to buy; that is the buyer's decision. It does say what the buyer will have to spend after completion to bring the estate to the standard implied in the deal price. That number is the most useful sentence in the report.
Each finding has a category, an evidence reference, a severity and a remediation range. Categories are structured to allow the buyer's counsel to allocate them between price, indemnity, specific warranty and post-completion work. I do not draft the legal terms; I hand counsel a clean list they can work from without having to ask an engineer what it means.
I run the diligence in a held-off format under an engagement letter with a defined scope, without claiming a certification or an insurance policy I do not carry. Where the target's data protection obligations require a specialist, I bring the buyer's own counsel to the table with the technical finding. The report and the findings log are handed to the buyer at the end of the engagement, and the conditions under which to re-run the review are recorded beside the findings.
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 due diligence for healthcare acquisitions — 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
- 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.