Practitioner · Organization · Location · Plan-Net

Charles Trinh — Provider Directory API | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading PROVIDER DIRECTORY — the network as FHIR, with a source of truth behind it
Charles Trinh — Provider Directory API

Why provider directories are wrong

A provider directory is a claim about the present: this clinician is accepting new patients, at this address, under this contract, with these hours. Every one of those facts changes without notifying the directory. The directory is therefore always stale, and the only question is by how much and whether anyone can tell.

The regulatory floor

Payer directories are held to accuracy requirements with attestation cycles and removal timelines for providers who cannot be verified. Meeting the floor is not the same as being accurate, but it defines the evidence you must be able to produce: when the record was last confirmed, by what method, and by whom. Build the schema around that evidence rather than bolting it on later.

Attestation is a workflow problem

Most directory inaccuracy traces to attestation being hard. If confirming a record requires a portal login, a form and a phone call, providers will not do it, and the directory decays. The fix is a low-friction path: a signed link, a small number of fields, and a clear statement of what happens if the record is not confirmed. Measure completion rate, not invitation rate.

Modelling the entities

A provider is not a location and a location is not a network. Model practitioner, organisation, location, and the network or plan participation that joins them, as separate entities with their own identifiers and their own validity periods. Directories that flatten these into one row cannot represent a clinician who practises at three sites under two contracts, which is most of them.

FHIR-shaped, not FHIR-only

The Plan-Net and PractitionerRole resources describe this domain well enough to use as an internal model even if the public interface is a custom JSON API. Adopting the shape early makes a future FHIR facade cheap and forces you to separate the entities properly. Adopting the shape late means a rewrite.

Search that behaves

Consumers search by name, specialty, location and plan, and they expect results that are correct rather than complete. Rank by confidence in the record, not by recency of update alone. A record confirmed last week outranks one confirmed two years ago even if the latter was edited more recently.

The staleness signal

Every record needs a machine-readable confidence: last confirmed date, method, and a decay rule. Expose it. A consumer that knows a record is eighteen months old can decide to call ahead; a consumer that does not know will send a patient to a closed practice and blame the directory.

What to measure

Measure the proportion of records confirmed within the required window, the attestation completion rate per cycle, the rate of patient-reported inaccuracy, and the median age of records returned in search. The last two are the ones that reflect actual harm.

The adversarial test

Pick twenty records at random and call the practices. Compare what you are told against what the directory says. The gap is your real accuracy rate, and it is almost always worse than the internal metric. Do this quarterly and publish the number internally.

Integration with credentialing

Directory data and credentialing data describe overlapping facts from different sources. Where they disagree, someone must decide which is authoritative and record the decision. Leaving both live and unreconciled guarantees that a consumer will eventually see the wrong one.

Sequencing

Model the entities first, then build attestation, then expose confidence, then tune search. Building search first produces a fast interface over data nobody has confirmed, which is the most common and most expensive order.

The outcome

A directory that reports its own confidence, confirms records on a schedule it can evidence, and separates practitioner from location from network. That is a directory a consumer can act on, and it is the only kind that survives an accuracy audit.

Who is allowed to change a record

Every field needs a named authoritative source. Practice hours come from the practice, network participation comes from the contract system, and credentials come from the credentialing system. When two sources disagree, the directory must know which one wins and record that it did. A directory that accepts edits from anywhere becomes a directory that reflects whoever edited last.

The consumer contract

Publish what the API guarantees: field semantics, update latency, confidence semantics, and what a consumer should do when confidence is low. Consumers build against the contract, and an undocumented field is a field they will interpret differently from you. Version the contract and give notice before changing it.

Bulk versus query

Payers and aggregators want bulk extracts; apps and patients want queries. These are different products with different freshness requirements and different rate limits. Serving both from one endpoint produces an interface that is slow for queries and incomplete for extracts. Separate them and document the freshness of each.

The removal path

A provider who has left a network must disappear from results within the required window, and the removal must be evidenced. Design removal as a first-class operation with a timestamp and an audit record, not as a side effect of an update. Removal is the operation most likely to be missed and the one most likely to cause patient harm when it is.

What good looks like

A directory where every record carries a confirmation date and method, where attestation completes at a measured rate, where removal is evidenced, and where a sampled phone audit matches the published data most of the time. That is a directory that can be defended in an audit and trusted by a patient.

Search relevance is a correctness problem

A patient searching for a cardiologist near a postcode and receiving a dermatologist twenty miles away has been failed by relevance, not by data. Rank by distance, specialty match and confidence together, and make the ranking explainable so a consumer can tell why a result appeared. Opaque ranking makes inaccuracy impossible to diagnose.

The attestation message

The single biggest determinant of attestation completion is what the message says. State plainly which fields are being confirmed, what happens if the provider does not respond, and how long it takes. Providers ignore attestation requests that look like marketing and respond to ones that look like a deadline with a consequence.

The data you should not publish

Not every field belongs in a public directory. Personal contact details, home addresses and unlisted numbers must be excluded by default, and inclusion must be an explicit choice. A directory that publishes a clinician personal mobile number because it was in the source system has created a safety problem, not a data-quality one.

The audit you should run on yourself

Before an external auditor asks, run the accuracy test yourself and write down the result. An organisation that knows its own accuracy rate and can show the method is in a completely different position from one that is asked and has to guess. The number matters less than the fact that you measured it and can repeat the measurement.

Staleness is the metric

Measure the interval between a change in the source system and that change appearing in the API, per field and per source. A directory that is correct but published monthly is wrong for most of the month, and the measured interval is the only honest statement of quality.

Publish change notifications for material network changes, and test them: change a network tier, confirm the API reflects it, and confirm a consumer who subscribed was told. A notification path that has never been exercised is a promise.

Then reconcile against claims. Where a provider rendered a service the directory says they are not in network for, one of the two is wrong, and that discrepancy list is the highest-value input the directory team will ever receive.

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 — provider directory api — the scope, the failure modes it prevents and how the work is measured. It sits in the X12 and EDI 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