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.
depth in one discipline rather than breadth across many. The engagement is usually short and pointed: a specific interface, a specific control, a specific failure that has resisted the generalist approach.
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.
Engagements run statewide from Las Vegas: Reno, Sparks, Carson City and the rural counties, where a critical-access hospital often has one IT director covering infrastructure, security and the EHR. Remote delivery is the default; travel is done when the work genuinely needs a room with the people in it. Statewide work usually involves the state Medicaid programme, which changes the interface requirements materially compared with commercial payers.
Scope is narrow and deep: a single interface, control or failure, worked until it is understood and fixed.
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 Nevada and the surrounding area — on site, remote, or both.