SERVICES · LAS VEGAS NV
Charles Trinh — Taxonomy Mapping | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Mapping provider taxonomy to your own specialty model: why one provider has several codes, where directories rot, and how filters actually behave under load.
One provider, many codes
Taxonomy is a classification, not an identity. A clinician may hold several codes across training and practice, with one marked primary by self-report.
Treating the code as identity produces both false negatives in search and false positives in directory display.
Decide the search rule and state it
Choose whether search matches primary taxonomy only or any taxonomy, and put the rule where the search is executed rather than in a document.
Handle the null case and the unknown code case explicitly, because new codes appear continuously and older records lack them entirely.
Test with real clinicians
Test the mapping with ten real clinicians whose work crosses specialties. They are the cases that break naive mapping and the ones a synthetic dataset never produces.
Include at least one provider whose primary code does not match the work they are booked for, because that is the ordinary case in a hospital.
Make it answerable
Log which taxonomy produced a directory result so a complaint can be answered with data rather than an apology.
Review the mapping quarterly with the clinical owner, not with IT alone, since the authority on specialty is clinical.
Classification, not identity
Taxonomy describes what a provider is trained and credentialed to do, in a vocabulary that is coarse and self-reported. A clinician holds several codes because training, practice and board certifications accumulate, and the primary designation reflects a declaration rather than a rule. Treating the code as identity produces both false negatives in search, where a qualified clinician is omitted because their primary code does not match the filter, and false positives in display, where a code suggests a capability the individual does not offer.
The mapping to your internal specialty model is therefore a deliberate artefact with an owner and a review date. It should state, for each internal specialty, which taxonomy codes qualify and which are excluded with a reason. That statement is what makes the directory behaviour explicable when a member cannot find a provider, and it is what a clinical owner can actually review.
Decide the filter rule in one place
Whether search matches the primary code or any code is a product decision with a visible consequence, and it belongs in the query layer rather than in a document. If the rule is any code, the directory will surface providers whose primary work is elsewhere, which is usually correct for access and confusing for a member looking for a specialist. If the rule is primary only, the directory will omit clinicians who are perfectly qualified, which is usually the more expensive error.
Whichever rule is chosen, handle the null and the unknown explicitly. Records without a code exist, codes are added continuously, and a filter that silently drops both produces a directory that looks complete and is not. A visible unknown category with a count is more honest than an empty result.
Testing with real clinicians
The test set that finds mapping defects is ten real clinicians whose work crosses specialties, including at least one whose primary code does not match the work they are actually booked for. That case is ordinary in a hospital and it is the one synthetic data never produces. Run the test against the actual search interface rather than against the database, because the behaviour being tested is the one the member experiences.
Record the expected result for each case before running it, so the exercise is a comparison rather than an impression. The mapping defects that survive review are almost always the ones nobody wrote down an expectation for, because the reviewer's attention follows the expectations that exist.
Answering the complaint
Log which taxonomy produced a directory result so a complaint can be answered with the record rather than with an apology. The log also shows which codes are associated with failures, which is how the mapping improves without a project. Review it quarterly with the clinical owner, since the authority on whether a classification is right is clinical rather than technical.
Keep the review short. Ten minutes with a clinical lead looking at the failing cases changes the mapping more than a technical workshop, because the cases carry the judgement that the code list cannot.
New codes and the release cycle
Taxonomy codes are added and revised on a publication cycle, and a mapping that is not refreshed against it gradually loses coverage. Subscribe to the release and review the additions each cycle, deciding for each whether it belongs to an internal specialty, and record the decision even when the answer is not yet. A code with no decision is a code that will default to unclassified, which is where directory omissions begin.
Display versus matching
What the mapping does for matching and what it does for display are different requirements. Matching wants breadth so that qualified clinicians are found; display wants precision so that a member knows what to expect. Using one mapping for both produces a directory that is either confusing or incomplete, and separating them costs a second column in a table.
The clinical owner
Name a clinical owner for the mapping and give them the failing cases rather than the code list. Clinicians reason about cases and not about vocabularies, and a review that starts from ten real examples produces better decisions in fifteen minutes than a review of the mapping table produces in an hour. The technical team implements the decisions and records them, which is the division that keeps the mapping current.
Making the mapping auditable
Keep the mapping as data with a version and a date, not as logic in code. A mapping expressed as code is a mapping that no clinical reviewer can read, and one that changes as a side effect of unrelated releases. With the table as data, a change is a commit with a reviewer, and the history answers the question of why a provider appeared in a directory result three months ago.
Attach a test case to every mapping rule that matters, so a future change that breaks the directory does so in the pipeline rather than in a member's search.
Failures that look like bugs
A member who cannot find their clinician reports a broken search, and the defect is usually a taxonomy value that no rule recognised. Treating those reports as product defects rather than as data issues is what gets them fixed, because the fix is often a mapping rule rather than a code change and the ticket routing decides whether it is ever looked at. Route directory complaints to the mapping owner by default and let them reassign, since the default determines the first hour of diagnosis.
The mapping owner should also own the definition of what a specialty means in the product, because the two questions are the same question asked from different directions. Where they are owned separately, the directory drifts from the product and the drift is discovered in complaints rather than in review.
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 — taxonomy mapping — the scope, the failure modes it prevents and how the work is measured. It sits in the Identity and Consent 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.