REGULATORY
Charles Trinh — TEFCA and QHIN Readiness | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

TEFCA is a network of networks with a certification queue behind it. QHIN readiness is the work of proving your exchange service can answer every query pattern the Common Agreement defines, before an assessor asks for it.
The network contract is written before any code moves
A QHIN does not sign a treaty with one partner. It signs a Common Agreement with RCE, then flows the same obligations down to every participant it connects. Readiness therefore begins in the contract layer, because the agreement fixes which purposes of use you will carry, how you handle an exchange request from a node you have never met, and what you owe when a transaction fails. I map those obligations against the services the organisation already runs before a single endpoint is touched.
Most teams start at the technical layer and discover the contract gap six weeks later, when counsel reads the participation terms and finds a flow that was never implemented or one that was implemented but never authorised. The two readings must agree. I build a matrix that lists each purpose of use, the endpoint that will serve it, the HIPAA basis for the disclosure, and the evidence to be filed when a request travels through it. Gaps are defects, not negotiation points.
The artefact that proves this section is a signed scope: purposes of use in, purposes out, with the rationale recorded by named owners. That document is what you return to when a participant disputes a refusal, and it is the first thing an assessor reads.
Exchange endpoints must answer the patterns they never see in testing
A QHIN query is not a single call. A request arrives for a document, an element, or a message, and your service must route it to the correct participant's record, honour the consent state that travels with it, and return either the clinical data or a structured answer that explains why not. Each of those branches is a separate obligation. A service that handles only the happy path will pass a friendly partner and fail a stratified assessment, because the assessor injects requests for the portions that matter least in demonstrations.
I design the test plan around the patterns rather than the flows: a patient with records at three participants, a patient who has revoked consent at one, a request for a participant that is offline, and a duplicate query arriving moments after the first. Each scenario states the expected response code, the expected structure, and where the log entry lands. The plan is run before the assessor arrives, against the same environment and the same credentials, so that the evidence already exists when asked for.
Portions of the query surface are easy to overlook. I enumerate them explicitly and mark each in or out of scope, so that the decision sits on the record rather than being discovered in a delivery meeting.
Directory service registration is a moving obligation
QHIN readiness does not end at go-live. A node is registered in the national directory with the endpoint addresses, certificates and supported operations that make it reachable. When a certificate rotates, an endpoint moves, or an organisation stops supporting an operation, the directory must reflect it promptly, or peer nodes will send traffic that silently fails. I treat directory maintenance as an operational control with an owner, a schedule and a verification step, not a project task that finishes at launch.
The verification is simple to run and embarrassing to skip: a periodic check from outside the organisation that resolves your node, reads its advertised endpoints, and reaches them with a harmless request. If that check fails, participants are losing referrals they never knew they attempted. I have watched a certificate expiry take a node effectively dark for two days while every internal dashboard reported green, because nothing inside the network tested the outside view.
Registration data also carries the technical statement of what operations you support. That statement is a commitment. Publishing an operation you cannot yet staff honestly is worse than delaying its registration, because a participant who believes you support it will plan work around it.
Consent and patient matching are where the network will test you
The Common Agreement lets participants attach restrictions to their exchanges. Your service has to honour those restrictions at query time, not reconcile them overnight. When a patient revokes access for a specific participant, the revocation has to travel with the next request and be applied before any data is returned from that participant's records. Building this as a lookup against a table that refreshes hourly leaves a window that an evening audit can open.
Matching is the other soft spot. QHIN traffic carries demographics that may not match your participant's patient index. A query for a patient whose name is punctuated differently, or whose date of birth is recorded in a legacy format, must not silently return an empty result that reads as no records found. I define the matching policy, test it with deliberately corrupted demographics, and require that unmatched queries produce a distinguishable outcome from genuinely absent records.
Both controls need a known artefact: a query log that shows the request, the consent decision, the match outcome and the response. Without that artefact an assessor's question about a specific date becomes unanswerable.
Operational monitoring is part of the answer, not an afterthought
Once the node is live, the standing question is whether it is serving the network honestly. I instrument the exchange service so that each request produces a measured outcome: succeeded, refused for a stated reason, failed for a technical reason, or timed out. These counts become the evidence that the node behaves, and they also expose the failures participants will complain about before they do.
The monitor needs a baseline. I capture the first month of measurements and use them as the reference against which later deviations are judged. A refusal rate that jumps after a deployment is a finding worth a page of analysis, and it is only visible if the baseline existed before the change. Without it, every incident begins with an argument about whether the behaviour is new.
Alerts need owners. A page that fires into a channel nobody watches is not monitoring. I require a named individual per alert class, a response time, and a documented path to the participant communication that follows an outage.
The recognition process is paperwork with teeth
Recognition involves an application, a demonstrated assessment, and a vetting function that examines whether your organisation can carry the obligations it signed for. The assessor is not simply checking that an endpoint returns a document. They are checking that the organisation behind the endpoint has governance, incident handling and an audit trail that would survive a serious incident. That means policies with owners and dates, not templates from a consultant's library.
I prepare the evidence bundle as a living document during the readiness work rather than at the end. Every control maps to a file path, a named owner, a test result and a date. When the assessment window opens, the bundle is assembled by selection, not by scramble. Where an obligation is only partly evidenced, it is recorded as such with a remediation date, so that the conversation with the assessor is about a plan rather than a surprise.
I would rather delay an application by a quarter than send an assessor after partial evidence. A refusal is recoverable; a reputation for overstating readiness in a national directory is not quick to repair.
What readiness actually changes for an organisation
QEUs and QHINs that go live find that the change is organisational as much as technical. The exchange function acquires a service desk, a change board that understands clinical impact, and a reporting ritual that shows participants the node's health. I design those functions before go-live, because retrofitting them after the first participant escalates a referral is expensive and visible.
For a health system joining through a partner, the work is shorter but the stakes are similar: the partner inherits the obligation, but the data risk stays with the organisation whose records are being exchanged. I work both sides of that boundary to make sure the partner's assessment covers the flows that actually carry the organisation's data, and that the organisation retains the ability to prove its own behaviour when asked.
The end state is a stable, monitored node and a shelf of evidence that answers an auditor's questions without a fresh project. I have walked organisations through this sequence, and I build the mapping and the evidence alongside the engineering rather than after it, so the programme and the technical work finish on the same timeline.
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 — tefca and qhin readiness — the scope, the failure modes it prevents and how the work is measured. It sits in the Interoperability 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.