Charles Trinh · Las Vegas, Nevada · TEFCA and QHIN

Charles Trinh - TEFCA and QHIN readiness in Las Vegas, Nevada

TEFCA is a governance programme with a technical surface. Organisations fail onboarding on policy and identity proofing far more often than on message format.

Charles Trinh prepares organisations for TEFCA and QHIN participation from Las Vegas, Nevada: the participant and sub-participant model, identity proofing, permitted purposes, consent handling and the evidence a QHIN reviews before admitting a node.

Charles Trinh - T markCharles Trinh · Las Vegas, Nevada · trinh.io
TEFCA and QHIN readiness, identity and consent, Las Vegas Nevada

The model

TEFCA defines a hierarchy: QHINs connect to each other, participants connect through a QHIN, and sub-participants connect through a participant. Each layer carries obligations, and the obligations are contractual before they are technical.

The first useful exercise is to place the organisation on that map and name what it is actually applying to be. Many organisations need participant status through an existing QHIN, not QHIN status of their own.

Identity proofing is the gate

Before any exchange, the organisation and its users have to be identity-proofed to the standard the network requires. That is a process with evidence, not a checkbox in a portal.

The work is to prepare the evidence package: legal identity, authority, roles, and the record of who was verified and when.

Permitted purposes and consent

Exchange happens for a stated purpose, and consent rules vary by state and by data class. A design that treats consent as a boolean will fail on the first complex case.

The pattern that holds is a consent registry: a record per patient per purpose, with revocation as an event rather than a deletion, so the history can be reconstructed.

Operational readiness

A QHIN wants to know the node will behave: response times, error handling, downtime notification, incident procedure and a named contact at two in the morning.

Those are operational documents, and they are usually the last to be written. Writing them early shortens onboarding more than any technical change.

Choosing the route to the network

Almost no organisation should become a QHIN. The practical choice is between joining through an existing QHIN as a participant, or joining through a participant as a sub-participant, and the difference is who carries the obligations.

That decision is a contract question with a technical consequence: which identity proofing applies, which directory the organisation appears in, and who is called when an exchange fails at two in the morning. Naming that before the application is filed saves a rewrite later.

How an engagement runs

It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.

If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.

Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.

Pricing and terms

Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.

Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.

What to prepare before the first call

Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.

If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.

Why the written record matters

Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.

The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.

Working in Las Vegas, Nevada

Nevada providers connect to national networks through a small number of intermediaries, so the practical question is usually which intermediary and under what terms rather than how to become a network.

Scope and terms

Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.

What the engagement produces

Services and expertise in Las Vegas, Nevada

Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.

The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.

TRINH - Charles Trinh, technology architect
Charles Trinh

Charles Trinh

Fractional CTO/CIO and Technology Architect - Las Vegas, NV

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

(702) 559-3489 Email Charles Trinh

TRINH

Services near me — Las Vegas, Nevada, the United States and worldwide

Serving customers in Columbus, Ohio, United States and worldwide.

Organisations searching for TEFCA readiness help near Las Vegas usually need the map, the evidence list and someone who has read the onboarding requirements.

Questions about TEFCA and QHIN readiness

Do we need to become a QHIN?

Almost never. Most organisations participate through an existing QHIN.

How long does onboarding take?

Three to nine months, driven mostly by identity proofing and legal review.

Do you handle the legal agreements?

No. The design and evidence are prepared for counsel to review.

What about state consent law?

It is mapped per state and per data class before the design is fixed.

Can you work with our existing HIE?

Yes, and usually that is the fastest route.

trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489