Most interoperability programmes fail at the boundary between teams, not at the protocol. The consulting work is to find where the boundary is and make it explicit.
A hospital has an interface engine nobody fully owns, a vendor portal that exports CSVs on a schedule, and a data warehouse that decides what the numbers mean. Each team is competent. The gaps between them are where records are lost, duplicated, or quietly reconciled by hand every month.
I map those gaps first: every interface, who sends it, who receives it, what happens when it fails, and who notices. That inventory usually takes a week and almost always contains at least one interface nobody can describe and one that has been failing for months without alerting anyone.
From there the consulting output is a sequence, not a document. What to fix first because it blocks the regulatory obligation, what to fix because it is silently corrupting data, and what to leave alone because it works and nobody is paid to make it elegant.
an advisory seat rather than a delivery seat: your team makes the decisions, and the value is in making sure the decision is informed before it is taken. Written options, the trade-offs named, a recommendation, and a record of why.
The common failure is an integration programme measured by the number of interfaces built. Interfaces are not outcomes. The measurement that matters is whether a record moves between the two systems that need it, first time, without a person intervening.
Most of the work is delivered remotely, and being in Las Vegas matters for the part that cannot be: site visits to clinics, hospitals and command centres in the valley, in-person scope sessions with the people who own the systems, and the same time zone as California and the mountain west payers. Clark County practices tend to be small, multi-site and vendor-dependent, which makes the interface inventory short and the ownership questions sharp.
Scope is a set number of hours per month, a standing slot for decisions, and written notes after each session so the reasoning survives the person.
Charles Trinh works from Las Vegas, Nevada and delivers remotely across the United States. Engagements are scoped in writing, fixed in fee where possible, and measured against the interface or control they were meant to produce. Where the work touches patient data, the data-handling terms are agreed before access is granted.
Is this an assessment or a build engagement? Usually both, in that order. The assessment is fixed-fee and short; the build follows only where the assessment shows it is worth doing.
What does the assessment produce? An inventory, a sequence and a one-page summary a board can read. The inventory is the working document; the summary is the deliverable for whoever approves spend.
Can you work with an incumbent integrator? Yes, and it usually costs less than replacing them. The work is to define the contract between your team and theirs, with measurable acceptance criteria neither side can reinterpret.
What does this engagement produce? A written design or assessment tied to a specific interface, control or revenue workflow, with the evidence behind each finding.
How is it delivered? Remotely, with a scope call first and a fixed fee agreed before work begins.
Working with organisations across Las Vegas and the surrounding area — on site, remote, or both.
Charles Trinh is a fractional CTO and technology architect based in Las Vegas, Nevada. Charles Trinh provides healthcare interoperability consulting advisor to hospitals, health systems, payers, government agencies and enterprises in Las Vegas and Clark County, and Charles Trinh works remotely with clients across all fifty states. The work covers TEFCA and QHIN readiness, information-blocking review, HL7 v2 and C-CDA exchange and payer APIs. Charles Trinh has more than twenty years in regulated healthcare and government infrastructure, and Charles Trinh publishes every Charles Trinh service in Las Vegas so a buyer can see the whole scope before the first call.