REGULATORY

Charles Trinh — State HIE Connectivity | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Diagram of an organisation's systems connected to a state health information exchange
Charles Trinh — State HIE Connectivity

State health information exchanges enforce their own specifications on top of national profiles. Connecting an organisation means satisfying the state's exact query surface, consent rules and data-sharing agreements before a single patient record moves.

A state exchange is a conformance test with a contractual wrapper

Every state HIE publishes an implementation guide of its own. It selects profiles, fixes the shape of queries, and dictates the formats for admission, discharge and transfer notifications. The guide is often based on national standards but departs from them in ways that must be honoured, because the HIE's certification testing uses the state's version. An organisation connecting by mandate has to conform to the state's implementation rather than to a generic understanding of the standard.

I read the guide alongside the data use agreement, because the agreement defines what the organisation is permitted to query and submit, while the guide defines how. The two documents are combined into a specification summary that the engineering team can work from and the compliance team can approve. The summary is signed off before the build starts, which avoids the situation where an interface works technically but discloses data under a category the agreement never contemplated.

The artefact is the combined summary. It lists the queries the organisation will support, the data categories it will submit, the consent model in force, and the changes the organisation must make to its operational systems to support each item.

Notifications are push traffic with its own etiquette

Most state HIEs require participating organisations to send notifications when a patient presents at a facility or is discharged. On paper this is simple. In practice it is a stream of messages with significant volume, duplicate offenders and edge cases, and each message has to be right. A missed notification is a missed care-coordination event; a duplicate notification is a nuisance on the receiving side. Both matter to the HIE's quality-of-service metrics.

I design the notification pipeline separately from the query interface. It begins at the encounter's own event in the facility's system and travels through de-identification where required, de-duplication against a short window and final send. De-duplication is the part that tends to be missing: a patient may present twice in a weekend, be admitted once and discharged once, and the receiving providers need to see the right sequence without one event arriving four times.

I measure notification volume against a baseline over the first month, then against the same month of last year when available, and I compare against the HIE's own metrics for the organisation. Divergence is a finding, and I report it to the HIE rather than waiting for their report.

Consent logic is per state and often per organisation type

Consent models differ by state. Some exchanges operationalise opt-out, where all records are shared unless the patient objects. Others use opt-in, where a record is shared only after explicit consent. Some states have special rules for behavioural health, substance use or minors. Your organisation's obligation depends on the state's model and on the categories of data the organisation holds. Getting this wrong is not a user interface problem; it is a disclosing records without consent problem.

I model consent as data, not as logic. Each patient has a consent state, each request carries a consent purpose, and the query service evaluates one against the other. The model includes special categories and their own rules. I test the model with synthetic cases: a patient with opt-out but with an exception for substance use, a minor whose records are protected, a patient with consent for care coordination only. Each test case has an expected answer and a failure affects the schema rather than a particular branch.

The consent register is the artefact. It records, by category and by patient, the current state and the event trail that produced it. That trail is what a patient inquiry resolves against.

The query surface is narrower than the standard suggests

A state HIE typically supports a subset of the national queries. It may allow retrieve-patient by demographics, retrieve-documents, and specific query categories, while omitting others. Organisations that assume the full specification is available discover that a partner cannot retrieve a progress note in a particular format, or that admission, discharge and transfer notifications arrive only in a different message format. My work maps what the state supports, what each participating system must supply, and what the organisation decides to do for features the state omits.

The mapping also covers the support tier: which queries are mandatory, which are optional, and which are provided only for members of a particular programme. I label each item as must, should, or may, and I determine whether the organisation's own downstream workflows rely on the item. Anything depended on by a downstream workflow that the state omits is a gap with a mitigation plan.

The artefact is a supported-query matrix, one column per query, one row per participating system, with the operational owner and the downstream dependency for each.

Data quality failures are measured, not argued

HIE query quality is judged on matching. An organisation whose demographic records do not match the patient's appearance at another hospital will generate failed or misleading queries, and the organisation will hear about it. I build a matching diagnostics process that pulls a sample of the HIE's own match failure and success reports, compares them with the organisation's source data, and identifies the systematic causes. Most failures come from a small number of fields: name formatting, address normalisation, or a missing date of birth.

The diagnostics feed a remediation list. Each remediation is a change to an operational system, a change to the supply of data, or a change to the HIE's matching service where that is permitted. The list is owned and scheduled, and a follow-up sample after several weeks measures the improvement. This is not a one-time exercise; a new registration workflow or a new facility can reintroduce the same problem.

I present the findings as numbers with reasons rather than as anecdotes, so that remediation decisions are made on impact and not on the loudest complaint.

Agreement amendments follow every real change

The data use agreement is not frozen at signature. When the organisation adds a facility, changes a vendor's system, or begins to exchange a new category of data, the agreement needs to reflect the change. Many organisations amend the agreement retroactively, or not at all, and discover at an assessment that a HIE data category has been flowing without authorisation. I make the agreement a living document.

I build a change-request checklist that starts the agreement amendment in parallel with the technical change. Reviewers receive a short summary, the compliance officer signs off, and the HIE is notified within the timetable. The whole chain lives on a tracker, visible to the operations team so that the technical schedule absorbs the agreement timeline. Where the agreement is silent on a change, I ask the HIE to correct the record before any patient data is exchanged.

That single checklist has prevented more escalations than any technical change I have made to a HIE integration, because it puts the compliance team in step with the engineering team instead of after them.

The programme becomes routine, and then the state changes the guide

Once connected, the work settles into a routine: monitoring the notifications, reviewing the matching diagnostics, handling the HIE's own change notices and submitting regular reports. The routine is sustainable, provided the organisation reschedules its effort instead of letting it evaporate after go-live. A programme that scatters after go-live has no capacity for the next guide version.

The state's guide is revised periodically. The revision may be small or may change the query model. I retain the specification summary and the supported-query matrix as living artefacts, so that the revision is assessed against them without rebuilding the picture. Revision work becomes a delta exercise rather than a project.

The goal is an integration that is current after each revision, with the evidence already in place to show it. The first build of the programme takes months; the second takes weeks if the artefacts live.

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 — state hie connectivity — 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

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

(702) 559-3489 Email Charles Trinh