CCD · templates · Direct · XDR
Charles Trinh — C-CDA Exchange | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Documents and resources answer different questions
CDA and C-CDA carry a clinical document — a discharge summary, a progress note, a continuity-of-care record — as structured XML with a human-readable rendering. FHIR carries discrete data. Both are legitimate and the choice is not stylistic: a document preserves narrative and attestation, and a resource enables computation and query.
Most real exchange needs both. A discharge summary that exists only as resources loses the narrative a receiving clinician reads. The same summary as a document alone cannot be queried, aggregated, or used to drive a workflow.
C-CDA on FHIR is the synthesis
A Composition with sections and contained resources: queryable like data, renderable like a document, and attributable to an author. It is the pattern worth designing toward, and it is also the pattern worth not assuming your counterparties support yet.
The narrative is the legal artefact
The human-readable section is what a clinician reads and what survives an audit. Implementations that generate structure and stub the narrative produce documents that validate perfectly and cannot be used, which is the worst of both outcomes: the conformance check passes and the clinical purpose fails.
Generate the narrative from the structured content, in the same build, from the same source. Hand-writing it is not sustainable and diverges immediately.
Templates on templates
C-CDA relies on template identifiers at document, section and entry level. Missing an entry-level template does not break your parser; it breaks the receiving system's, silently, and the receiving system is one you will never test against.
Treat template identifiers as required fields with a validation rule, not as optional metadata. The cost of getting this right is a lookup table. The cost of getting it wrong is a support relationship with every partner you send to.
Code system consistency
The same concept expressed in LOINC, SNOMED CT, and a local code, inconsistently across sections of the same document. Consistency matters more than which system you choose: a document that says the same thing two ways is a document a downstream system will interpret two ways.
Pick the system per concept, write it down, and validate against the choice. The local code remains as a secondary identifier and never as the primary meaning.
Empty sections are assertions
A section that is declared and unpopulated is a clinical statement that nothing was found. If you did not look, do not declare the section. This is the single most common source of clinically misleading C-CDA in production, and it is invisible in validation because an empty section is structurally valid.
Validate, and treat it as a blocker
Use the published schemas and the reference validator, and treat a validation error as a release blocker rather than a warning. Documents travel to systems you will never test against, and their tolerance for your defect is not something you can predict or negotiate.
Run the validator in the pipeline against real documents, not fixtures. Fixtures validate; production documents are the ones with an unexpected null in a required field.
Transport is a separate problem
Getting the document there — XDS, XCA, Direct, or a FHIR document bundle — is a different concern with different failure modes. A document that validates and cannot be retrieved has solved nothing. Test registration and retrieval as one path, with the metadata that makes it discoverable.
Migration without a flag day
Do not stop producing documents when you start producing resources. Publish both from the same source of truth and let a consumer choose. Organisations that attempted a cutover discovered that half their trading partners had no roadmap and no intention of building one, and the documents were still the only thing that travelled.
What I do
I have built C-CDA generation and consumption alongside a FHIR surface in the same platform, which is the only arrangement in which the shared source of truth is actually achievable rather than aspirational. I fix the narrative and template layers first, because those are the defects that reach a clinician.
Metadata is the discoverability problem
A document that validates and cannot be found has solved nothing. In any registry-based exchange — XDS, XCA — the document is discovered through metadata, not through its content: the patient identifier, the class and type, the author, the facility, the event time, the format code.
The failure mode is metadata that is technically present and practically useless. A class of "other" for everything, an event time populated with the submission time rather than the clinical time, an author recorded as a system account rather than a clinician. Each makes the document invisible to the query a receiving clinician would actually run.
Validate metadata as strictly as content, and test discovery as its own journey: submit, query the way a clinician would, retrieve what comes back, and confirm it is the right document for the right patient.
Restrictions and confidentiality inside a document
C-CDA can express confidentiality codes at the section and entry level, and can carry consent references. Whether a receiving system enforces them is a separate question and frequently the answer is no.
So do not rely on in-document restriction as your only control for sensitive categories. Apply enforcement where the document crosses a boundary — at the exchange interface, before transmission, against the requester and the purpose. In-document codes are a signal to a cooperating system, not a security boundary.
What the receiving system actually does with it
Most receivers do not parse your document into structured data. They render it. A clinician reads the narrative, the structured content is retained for future use or discarded, and the discharge summary becomes a PDF with better provenance.
That has a design consequence people find uncomfortable: the narrative is not a legacy artefact to be generated once the structure is right. For most receivers, the narrative is the product. Write it accordingly, and generate it from the structured content so the two cannot diverge.
The three tests worth running
Round-trip a document through the reference validator and confirm zero errors, not zero warnings. Render it exactly as a receiving system would and read it as a clinician — the failures that matter are visible on screen and invisible in the XML. And submit two documents for the same patient with different event times and confirm a query returns both in the right order, because a timeline that is silently wrong is worse than a document that is missing.
What I do
I have built C-CDA generation and consumption alongside a FHIR surface inside the same platform, which is the only arrangement where a shared source of truth is achievable rather than aspirational. I fix the narrative and template layers first, because those are the defects that reach a clinician's screen.
What to ask a document-exchange vendor
Four questions decide whether a vendor's C-CDA support is real. Which document-level and entry-level templates do you emit, and at which version? Is the narrative generated from the structured content in the same build, or composed separately? What metadata do you populate for discovery, and on which field do you set the clinical event time? And can you show me a document you sent to a partner that validated on their validator, not yours?
A vendor that answers all four with specifics has built this before. A vendor that answers the first two and redirects on the last two has built a renderer and called it exchange. The fourth question is the only one that cannot be answered without a real partner, which is exactly why it discriminates.
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.
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
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 — c-cda exchange — 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.