XDS · XCA · PIX · PDQ · MHD · ATNA

Charles Trinh — IHE Profiles | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading IHE — XDS, XCA and the transactions behind an HIE
Charles Trinh — IHE Profiles

IHE profiles define the transactions that make an HIE work: how a document is registered, where it is stored, how a query finds it, and how the whole exchange is audited.

What this is

IHE takes a different approach from FHIR: it specifies actors and transactions, and profiles combine them into a capability. Cross-Enterprise Document Sharing defines a document registry and one or more repositories, with a submitting actor that provides documents and a consuming actor that queries and retrieves them. Cross-Community Access extends the same model across communities. PIX and PDQ handle patient identity and demographics queries. MHD is the FHIR-facing equivalent of the document sharing transactions, and ATNA defines the audit trail every actor must write.

The model is durable because it separates the index from the content. A registry holds metadata — patient identifier, document type, author, class, availability status — and the repositories hold the documents. That separation is what makes a query over millions of documents fast, and it is also what makes registration metadata the most important thing to get right: a document that is stored but registered with the wrong patient identifier is effectively lost.

Where exchanges fail is usually at the seams: an identifier assigned by one assigning authority and interpreted by another, an availability status that never moves from deprecated to approved, an audit record written by the repository but not the registry. Each is a small configuration error with a large consequence, and each is invisible until a consumer queries and gets nothing.

The testing culture in IHE is the useful part. Connectathons force implementations from different vendors to prove the transactions against each other, which surfaces the interpretation differences that a spec reading cannot. I use the same method: a transaction matrix, tested peer to peer, with the audit evidence checked at each step.

The FHIR bridge is the modern constraint. MHD expresses document submission and retrieval as FHIR resources, so an exchange that runs classical XDS and a FHIR front end needs a mapping layer that keeps the two representations consistent. I treat the registry as the source of truth and the FHIR facade as a view over it, which prevents the two from drifting into separate answers to the same query.

How I do it

The work begins with an actor matrix: which system plays which actor, in which profile, and which transactions connect them. Every actor-transaction pair gets a test, and the tests are ordered so that identity comes first — PIX and PDQ before document sharing, because a document registered to the wrong patient cannot be fixed by a better registry.

Then the metadata. I define the document entry attributes the registry requires, the code lists used for type and class, the assigning authorities in play and the availability status lifecycle. That definition is a contract with every submitting system, and it is validated by submitting a document and querying it back as a different consumer would.

Audit is treated as a transaction, not a log line. Every actor writes its own ATNA record, and I verify that a single document submission produces the full set of records across the actors involved, because an audit trail with holes is worse than none in an investigation. The check is a query, not an inspection: given a document identifier, the whole history must come back in order. When it does not, the missing actor is the finding, and the fix is almost always a configuration line nobody owned. That discipline also makes the Connectathon useful rather than ceremonial: the failure is found by a peer, on a schedule, instead of by a patient.

Artifacts you keep

  • An actor and transaction matrix per profile in use
  • A registry metadata contract covering identifiers, class and status
  • A peer-to-peer transaction test record
  • An ATNA audit verification across every actor in a submission
  • An availability-status lifecycle with the owning system named

IHE solved problems FHIR is rediscovering

Integrating the Healthcare Enterprise produced profiles for cross-enterprise document sharing, patient identity cross-referencing, and query-retrieve long before FHIR existed. Those profiles still govern a large share of real health information exchange.

XDS, XCA, PIX and PDQ describe capabilities that FHIR later described again as MHD and PDQm. The mechanics differ; the problems are identical. Understanding the older description is often the fastest route to understanding why the newer one is shaped the way it is.

There is also a plain commercial reason to know them: the installed base runs them, and a strategy that assumes they will be replaced before your procurement cycle ends is a strategy that has not looked at the procurement cycle.

The profiles worth knowing

XDS and XCA cover document registration, discovery and retrieval, with XCA extending across communities. The metadata model is the hard part; the transport is straightforward and rarely the cause of failure.

PIX and PDQ are the older answer to patient matching. PIX is worth studying because it named the problem correctly decades ago: you need an authority rather than an algorithm, and a cross-reference registry rather than a scoring function.

MHD and PDQm are the FHIR rendering of the same capabilities. Cleaner to implement and only useful where the counterparty supports them, which is the constraint that matters and the one vendor decks omit.

Conformance testing is the deliverable

IHE runs a formal testing process through Connectathons and the Gazelle tooling. Passing it is not academic decoration; it is the shared vocabulary that lets two organisations which have never spoken integrate in weeks rather than quarters.

Organisations that skip it and claim conformance discover the difference in production, usually as a metadata field that two systems interpreted differently and neither validated.

If a partner claims IHE conformance, ask which profiles, which version, and when they last tested. A named profile with a test date is an answer. A general claim is a belief.

Where the two worlds meet

The realistic architecture is a facade: FHIR on the outside for new consumers, XDS or XCA underneath for the document fabric, and a translation layer keeping metadata consistent across the boundary.

The failure mode is a facade that loses metadata. A document arriving without its class, its author or its event time cannot be filed correctly, and the receiving clinician cannot find it even though it is technically present.

Treat metadata as the contract and validate it as strictly as content. In registry-based exchange, discovery is the product, and a document nobody can find has the same clinical value as one that was never sent.

The question to ask before choosing

Which profiles does your exchange partner actually conform to, at which version, tested when? Answer that and the architecture often decides itself, because the constraint is not which standard is better but which one the counterparty has demonstrated.

Then ask what your own metadata population looks like today. That is the defect you control, and fixing it is usually cheaper than any migration.

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

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

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 — ihe profiles — 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.

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