EXPERT NETWORKS · DILIGENCE · BRIEFINGS
Charles Trinh — Expert Network Consultations | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Working as an expert in diligence consultations: what the formats require, how to separate opinion from fact, and the conflict and confidentiality discipline that keeps the engagement clean.
What the format actually is
An expert consultation is a structured conversation, typically an hour, between an investor or acquirer and someone with operating experience in a sector. The purpose is to test an investment thesis or a diligence hypothesis against someone who has run the thing, and the value is in the specifics: what actually happens, what fails, what the numbers look like in practice, and where the commonly held view is wrong.
The format rewards preparation and penalises performance. A consultant who arrives with a strong general narrative and no specifics is less useful than one who can describe three concrete situations and what they cost. The investor is not buying your biography; they are buying a shorter learning curve.
Ask for the topic areas in advance and prepare around them, including the parts where you will say you do not know. A clearly stated boundary is more useful than a confident answer that turns out to be wrong, because the investor will act on it.
Fact, experience and opinion, kept apart
The most valuable discipline in this work is labelling what kind of statement you are making. A fact about a regulation, an experience from a system you ran, and an opinion about how a market will develop are three different things, and mixing them produces a briefing that reads as authoritative and carries no weight when checked.
State the source for facts, the context for experience and the reasoning for opinions, and say plainly when the answer is that you do not know. Investors are used to being told what someone thinks; they are less used to being told what is unknown, and the latter is often what changes a decision.
Where an experience is from a single organisation, say so. Generalising from one company to a market is the most common way a briefing misleads, and it is rarely intentional.
Confidentiality and the materials you bring
Expert consultations carry confidentiality obligations in both directions, and the discipline is straightforward: do not disclose material non-public information about a current or former employer, do not use documents you do not have the right to use, and do not name customers or patients. The value of the briefing does not depend on those disclosures and the risk is disproportionate.
Prepare from your own knowledge rather than from documents, and where a document would help, describe it rather than produce it. If a question can only be answered from confidential material, say that and explain the reason rather than answering around it.
Keep the record of what you were asked and what you said. It protects both sides and it is useful when a later question arises about what was disclosed.
Conflicts and the honest decline
Decline when there is a conflict: a current employer whose competitive position is at issue, a relationship with the target company, or a role that would make the disclosure improper. The networks usually ask for a conflict check and the answer should be considered rather than quick, because a conflict discovered later damages the consultant's standing more than a declined call.
Where the conflict is partial, disclose it and let the network decide. A disclosed relationship is usually acceptable; an undisclosed one is not, and the distinction is the whole point of asking.
The same applies to opinions that are commercially inconvenient. A consultant whose every answer supports the thesis becomes less useful over time, because the investor learns to discount the confirmation and to look elsewhere for the test.
Making the briefing useful
Structure the hour around the decisions the investor is trying to make. Ask what would change their view, and spend the time on that rather than on a tour of the sector. The best briefings produce two or three specific things the investor did not know, and the way to get there is to ask rather than to lecture.
Use numbers where numbers exist, and give the ranges rather than the point estimate, because a range communicates uncertainty honestly and a point estimate invites false precision. Where the number is from memory, say so.
Close with the questions the investor should ask the company. That list is often the most valuable output of the hour, because it converts the conversation into diligence work and it demonstrates the kind of judgement the engagement was meant to buy.
The preparation that makes the hour work
Preparation for a consultation is short and specific: read the materials the network provides, identify the three or four questions the investor is likely testing, and assemble the concrete examples that bear on each. An hour of preparation produces a substantially better hour of conversation, and the consultants who are invited back are usually the ones who arrived prepared rather than the ones with the most impressive title.
Keep a personal record of the examples you use, because the same situations recur across calls and a well-told specific example is more useful than a fresh one that is vague. Anonymise as you record, so the example can be used without disclosing anything identifiable, and keep the detail that makes it concrete: the size of the organisation, the system involved, the failure mode and the cost.
After the call, note the questions you could not answer and research them. The next investor will ask a version of the same question, and the accumulation of answered questions is what makes the consulting practice valuable rather than repetitive.
Building the practice over time
Expert consultations are a practice rather than a series of one-off calls, and the practice improves when the consultant keeps a record of what was asked, what was useful and where the answers were thin. The record is the basis for preparation on the next call, the source of the examples that make a briefing concrete, and the discipline that prevents the same anecdote being told four times to four investors who compare notes. It also creates a feedback loop on the consultant's own knowledge: the questions that recur across investors are the questions the sector is genuinely puzzling over, and the answers that have stood up are the ones worth writing down. Consultants who build the record are invited back more often, because their briefings are denser and their answers consistent, and consistency is what makes a briefing something an investor can act on.
Keep the boundary between consulting and advisory relationships. A consultation is a bounded conversation with a confidentiality obligation, and an advisory relationship is an ongoing engagement with different terms, different conflicts and different disclosure requirements. Consultants who blur the two create situations where an investor relies on something said in a call as if it were advice, and the absence of a written scope is where that ambiguity lives. Naming the engagement for what it is, at the outset, costs a sentence and prevents a dispute that would otherwise be settled on the strength of recollection.
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 — expert network consultations — 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.