tefca · qhin · permitted purposes
Charles Trinh — TEFCA and QHIN Readiness

A network is not a data source
A QHIN routes and establishes trust. It holds no records, and it cannot compensate for a matching failure at either end of a query.
Permitted purposes are gates that change what is returned, not labels attached to a log line after the fact.
Enablement is the work
The conformance phase is bounded and documentable. The operational phase is where programmes sit for months, because a connection with no enabled participants is a certificate and an invoice.
Enable participants individually and verify exchange, not connectivity.
Measurement
Queries issued against responses with clinical content, reported per source and per month. A low ratio is a matching problem, a data quality problem or an enablement problem, and per-source reporting tells you which.
Log match failures, because they are the only evidence a member's history did not transfer.
Consent asymmetry
The responder applies its own jurisdiction's rules to a request that arrived from another state, and the requester documents what it asked for.
Build the responder's segmentation properly and the requester's log thoroughly, because that asymmetry is not resolved by any national standard.
What readiness actually requires
Readiness is not a connection; it is the ability to answer the queries the network defines, for the purposes it permits, with the record that proves what was asked and what was returned. A QHIN onboarding checklist covers the first and sometimes the second, and almost never the third.
Build the evidence first: a log that records each query, its purpose, the requester, the responder and the outcome. Then a report that aggregates it per source per month. Without those two, the programme cannot answer the question its own sponsors will ask, which is whether it is producing exchange or merely connectivity.
Permitted purposes as gates
Each permitted purpose changes what may be returned, and the gate belongs at the query rather than at the audit. A system that returns everything and labels the purpose afterwards has inverted the control and will produce disclosures that are lawful on paper and wrong in fact.
Test each purpose with a request that should be refused under it. The refusal is the control operating, and a purpose that never refuses is a purpose that is not being enforced.
Matching at network scale
The network does not match patients; the participants do, on both sides. A query that returns nothing is usually a matching failure and occasionally a data quality failure, and the distinction matters because the fixes are different and the owners are different.
Report match failures explicitly rather than as empty results, because an empty result is indistinguishable from a member who has no history, and the second is rare. The count of empty results against requests is the number that tells you whether the network is delivering what it promised.
The consent asymmetry
The responder applies its own jurisdiction's rules to a request that arrived from another state, and the requester documents what it asked for. That asymmetry is not resolved by any national standard and it is where most of the legal analysis sits.
Build the responder's segmentation carefully and the requester's log thoroughly, and say plainly in the programme documentation which rules are being applied at which end. Ambiguity in that sentence is what produces a finding rather than a policy.
Operating it after go-live
The operational rhythm is a monthly review of volume, match rate and refusals, plus a quarterly review of enablement and a review on any change to the common agreement. Programs fail quietly when nobody owns the number, so name the owner and put the report in front of them on a schedule.
Keep the participant enablement list current, since a participant that was enabled and never activated is a row that suggests capability the organisation does not have.
The conformance phase
Conformance testing is bounded and documented, and it is the part of the programme that can be planned with confidence. The mistake is treating it as the whole programme, because passing it proves the exchange answers questions correctly in a test environment.
Record the suite version and the date. A conformance claim without them is a claim about a Tuesday, and the reviewer will ask.
Enablement and the long tail
Participants are enabled individually, and each enablement is a small project with its own contacts and its own timeline. A programme that reports connectivity rather than enabled participants is reporting infrastructure rather than capability.
Track enablement as a list with dates and owners, and review the list monthly, because the pace of enablement is the pace of the programme.
Refusals and the refusal log
A refusal is the control operating, and a programme with no refusals has either a very narrow population or a gate that is not enforced. Log the refusals with their purpose and review them monthly.
The log is also the evidence that the segmentation is real rather than described, which is the question asked after a disputed disclosure.
The quarterly review
Volume, match rate, refusals and enablement, per source, trended. Four numbers in one page, reviewed with the people who own the participants rather than with the people who own the infrastructure.
The trend is the point. A single quarter tells you what happened; four tell you whether the programme is working.
What readiness work produces
A query log that records every request with its purpose, requester and outcome, and a monthly report that aggregates it per source. Those two artefacts are what turn a connection into a measured programme.
An enablement register with dates, owners and current status, reviewed monthly with the people who own the participants rather than the people who own the network.
A written statement of which jurisdiction's rules are applied at which end of each exchange, because that sentence is what a reviewer will ask for and it is rarely written down.
The participant conversation
Each participant arrives with its own expectations about what the network will give it, and those expectations are usually set by the marketing of the network rather than by the specification. A short written note per participant, describing what will and will not be exchanged, prevents most of the disappointment that follows.
Update the note when the permitted purposes change, since the change is the moment a participant discovers its assumptions were wrong.
Keep the specification of what the network does and does not do in the participant onboarding pack, and have each participant acknowledge it in writing. The acknowledgement is the artefact that settles the argument after the first six months, when expectation and capability have drifted apart and nobody remembers what was originally agreed.
Review the pack annually against the common agreement, since the agreement changes and the pack does not unless somebody owns it.
The first year of a network programme is measured in enabled participants and exchanged records, not in connections. Report those two numbers to the programme sponsor every month, because they are the ones that justify the next year of work and the ones that are easiest to substitute with activity.
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.