US Core profiles · Must Support · USCDI

Charles Trinh — US Core Conformance | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading US CORE — profiles, Must Support and USCDI elements
Charles Trinh — US Core Conformance

US Core is a floor, and the floor is higher than the diagram suggests

US Core constrains the base FHIR resources: required elements, required terminology bindings, required search parameters, and required profile declarations. It is the minimum for United States exchange, and it is meaningfully stricter than the base specification in the places that catch teams late — usually during conformance testing rather than during design, which is the expensive order.

The profiles are not a suggestion and not a style. A resource that carries the right clinical content but does not declare the profile and does not satisfy the required bindings cannot be relied on by a counterparty, and will fail validation in their environment even if it passes in yours.

Declare the profile

Every resource instance that claims US Core conformance says so in meta.profile. This is the cheapest line of code in the entire project and the most commonly omitted. A validator that cannot tell which profile you intended cannot validate you, and a counterparty cannot know which constraints to expect.

The second-order effect matters more: once you declare a profile, your own CI can validate against it. Teams that omit the declaration also tend to have no continuous validation, because there was nothing to validate against.

Terminology is where projects quietly die

Required bindings to value sets you have not loaded, or have loaded at the wrong version. A Condition.code that is internally consistent and locked to a local code system does not satisfy a required binding, and the failure appears at validation time, long after the pipeline was built around the local codes.

Load the value sets at pinned versions, serve them from a terminology service, and record which version was in force at each release. When a binding changes, the release notes should tell you which elements are affected rather than which integrations broke.

Cardinality on elements nobody populated

Required meta.profile. Required identifier systems. Required categories on observations and documents. Required status fields. Each is trivial once and expensive late, and each one fails the same way: a validator error in someone else's test report, hundreds of messages deep, on a resource you believed was finished.

The pattern that prevents this is generating a profile-by-profile gap list from the resources you actually serve, with a source system, an owner, and a date per row. Not a RAG status. A row.

Search parameters are not optional extras

Conformance testing exercises the parameters the profile requires, not the ones you found useful. A server that implemented search where it was convenient passes its own tests and fails the suite, because the suite asks for the parameters a real client needs: patient plus category, patient plus date, identifier lookups, and the includes that make a result clinically readable.

Every advertised parameter needs a query plan someone has read. A parameter that works on a hundred records and times out on a million is not implemented; it is a latency bomb with a passing unit test.

Validate in the pipeline, not at the end

Run a FHIR validator against the profiles and the terminology server on every build. A conformance run at the end of a quarter produces a defect list measured in hundreds; the same validation per commit produces a list measured in ones, because each defect is caught where it was introduced and by the person who introduced it.

Treat validation failures as build failures. A warning that everyone has learned to ignore is not a control.

The external bar

For patient and population access the prescribed demonstration is the ONC (g)(10) criteria as exercised by Inferno. That suite is not a formality: it sequences US Core, SMART App Launch and Bulk Data in a way that exposes integration defects rather than unit defects. I have taken a platform to 317 of 317 subtests, and what that run teaches is that conformance is a discipline of small correct details repeated thousands of times rather than a feature you finish.

Schedule it early. Teams that run it in week two ship in month two, because they discover the shape of the problem while there is still room to design around it.

The five failures that recur

Missing meta.profile. Unpinned terminology. A required element left null because the source system never captured it. A search parameter implemented but unindexed. A _include that returns the resource and omits the referenced one, producing a result a clinician cannot read without a second call.

None of those are architectural. All of them are the difference between conformant and useful.

What I do

I run profile-by-profile conformance reviews against US Core, build the gap list, and fix the terminology and search layers that make conformance durable rather than a one-time pass. I have done this against a live clinical store with real data, not a reference server with synthetic patients, which is where the difference shows.

The gap list is the project

A conformance programme without a gap list is a series of conversations. The artefact that converts it into work is a table with a row per required capability: the profile, the element, the source system, the transformation, the owner, the date, and the current state.

Two rules make the table useful. The owner is a person rather than a team, because a team cannot be asked. And the state is evidence-based — either a validator run proves the element conforms today, or the row is open. A row marked done without a validation artefact is a row that will reopen during the external test, which is the most expensive time to discover it.

Run a terminology server, even a small one

Required bindings mean value sets must be loadable and expandable at validation time. Organisations that keep value sets in a shared drive discover that two teams are validating against different versions, and that the difference is invisible until a counterparty rejects a resource that passed locally.

A terminology service — even a modest internal one — gives you one version in force, one expansion behaviour, and one place to change when a binding updates. It also makes the validator's answers reproducible, which matters when you are arguing with a partner about whose defect it is.

Pin the versions and record them

US Core, the value sets, and the FHIR version all change. Record which combination was in force for each release. When a resource that validated in March fails in September, the release note should tell you whether the binding changed or the data did, and without a recorded pin you cannot distinguish them.

The five-minute weekly check

One synthetic request per resource type, every week, from outside the estate, validated against the current profiles. It costs almost nothing and it catches the class of failure that otherwise appears in a partner's ticket: a required element that stopped being populated because an upstream field was renamed.

What to do this week

Load the required value sets at pinned versions. Add meta.profile to every resource you serve. Generate the gap list from the resources you actually return rather than from the resources you intend to return. Schedule the external conformance run as a milestone with a date, and put it early enough that the findings can still change the design.

What I do

I run profile-by-profile conformance reviews against live data, build the gap list with owners and dates, and fix the terminology and search layers that make conformance durable. The difference between a one-time pass and a durable one is whether the validator runs in the pipeline, and that is the part I install.

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

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 — us core conformance — 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