REGULATORY
Charles Trinh — USCDI Version Implementation | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Each annual USCDI version adds data elements your certification and exchange commitments depend on. Implementing a version is a data mapping exercise with a clinical meaning attached to every row, not a schema upgrade.
A version is a list of data elements, not a release note
The standard publishes a list of data elements grouped by category. Each element has a defined vocabulary, an expected clinical meaning and a place in the interoperability specification. When the axis of the list moves, organisations invent the difference in their own systems unless they map it. I begin by bringing the list into a spreadsheet with one row per element and a column for the source system, the field in that source, the transformation that applies and the FHIR resource and profile the element will appear in at the edge.
That spreadsheet is the programme. It tells the organisation what the new version requires, what the organisation already holds, and what has to be created. Rows are assigned owners. Rows where the source operational system records the data in a free text field are flagged as conversion work, because free text has to be structured before it can be shared as a standard element. Rows where two systems hold different values are flagged for clinical agreement.
The most common failure mode is treating the mapping as an engineering sprint. A version change usually involves decisions that only clinicians can make, like what counts as an allergy in the organisation's data and how soon a new medication order should surface. Those decisions deserve a written record.
Data provenance is where versions expose reality
When a data element is requested, the answer has to come from somewhere and the requesters want to know where. Some elements are recorded natively: a blood pressure taken in the clinic is a measurement with a date, an operator and a unit. Others are inferred or aggregated: a care team assembled from billing records, a problem list assembled from notes and orders. The new version tests both kinds, and inferred elements are where the implementation becomes visible to clinicians.
I produce a provenance statement for every element regardless of whether the current specification requires one. Each statement names the system of record, the process by which the value arrives at the edge, and the confidence the organisation is prepared to stand behind. Once written, the statement is also useful during certification, because a test failure can be traced to a source rather than chased through the whole pipeline. I have found latent inconsistencies this way that had been quietly producing mismatched answers for years.
Where an element cannot be produced with the expected meaning, the sensible option is to record the gap honestly and plan its closure. Presenting a placeholder as a patient-reported observation, for instance, is a defect that the next audit will find.
Vocabulary decisions precede interface decisions
Many elements come with vocabularies: codes for problems, allergens, procedures, units and demographics. A version change may add elements without new codes, but it can also align an element with a newer vocabulary release or ask for a code set your systems do not currently maintain. The vocabulary decision determines the size of the interface work. A code set you maintain in an edge service is a small change; one you replace at the source is a migration.
I get the vocabulary picture in front of the organisation early. The question is specific for each element: what codes does the operational system store, which codes does the version expect, and what will happen to values that have no mapping. I run the mapping and measure the unmapped rate, because the rate is the operational burden. Anything above a small percentage needs a clinical decision about how unknown values should be represented rather than a blanket fallback.
Maintaining vocabulary is a standing function. Each update cycle brings vocabulary releases and I set up the process that reads them, scores them against current usage and brings decisions to the right clinician before the next version is due.
Extensibility gives you a way to carry what the version omits
Every version of the list leaves things out. An organisation may have a critical data element that is not in the current version, and it will still need to exchange it with the systems that rely on it. The specification provides an extension mechanism for that purpose. Using it well is a skill: the extension must be defined in a way that other parties can interpret, documented publicly if the data is exchanged outside the organisation, and tested as carefully as the core elements.
I design extensions with the receiving systems in mind. A receiving partner will either ignore the extension or attempt to render it, and a poorly shaped extension in a clinical viewer is a usability problem. I test with a viewer in front of the data, and I ask whether the extension makes sense without a phone call to the sender. If it does not, it needs a description in the profile, not a note in the integration specification.
The extension register is the artefact. Each extension has an identifier, a scope, an owner and a review date. Without that list, extensions accumulate until the edge specification is larger than the standard it was built on.
Adoption still requires a regression harness
When an element moves from one version to the next, the evidence that the organisation serves it is a test run against the version in question, not against the version it was certified for. I keep a regression harness that runs the same canonical patient through each version of the specification, so that the gap between them is visible as data rather than as a comparison exercise. A patient with entries for the affected elements exposes the difference in minutes.
I run the harness before each change to the edge service, not only when a version is adopted. Version work tends to touch the same code paths as ordinary work, so an organisation that adopts the new version and then loses it through an unrelated deployment has the appearance of progress without the substance. The harness runs in continuous integration and reports a pass or a fail against the specific version targeted.
The report is the artefact. It lives with the release notes and the certification materials, so anyone can see which version was served on which date.
Edge services need a lifecycle for each version
Multiple versions will be live at any time. Partners move at different speeds, and some will remain on an older version for years because their certification is tied to it. That means the edge service must serve both, from the same source data, with clear labelling and separate conformance where the semantics differ. I build a version-aware layer that states which version each request is answered in, and log that version so that later analysis can attribute behaviour to the version it belonged to.
The temptation is to define one edge implementation and accept whatever the partner says at the point of integration. That leads to silent differences in meaning between versions that surface as clinical disputes. I document the semantic difference between versions, element by element, and require the partner integration to acknowledge it.
I have proposed a USCDI data element for a Patient Digital Identity Credential to ONC, so I understand the mechanics by which elements enter and leave the list. The work is designed for that reality: a mapping that can absorb a new version quarterly rather than a year of preparation per version.
What adoption should look like when it is done
A finished adoption cycle produces a mapping spreadsheet with every row owned and closed, a written provenance statement per element, a vocabulary register, an extension register, and a regression harness that runs against the version in question on every change. Those artefacts let the organisation answer the questions that follow adoption: what do we hold, where does it come from, and can we prove it at any given date.
Adoption also produces a working group that lives on, because the next version arrives before the organisation has finished reading the current one. I hand over with the group and its calendar intact, the artefacts filed, and the first sweep of the next version already scheduled. I would rather the organisation start the next cycle with a checklist than with a blank page.
This is the difference between implementation and habit. The habit is cheap to maintain once it exists, and expensive to build from nothing each time.
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 — uscdi version implementation — 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.