DATA
Charles Trinh — HEDIS Quality Measure Reporting | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

HEDIS rates that move by two points without anyone touching care are almost always a specification or data-source problem. I trace the numerator, the denominator and the exclusion logic before the measure is reported.
The specification is the contract
Every HEDIS measure is a document with a denominator, a numerator, exclusions, and specification versions that change year on year. A team that writes measure logic from a summary slide rather than the current specification will produce plausible-looking numbers that fail audit. I start by loading the current technical specification into a working document and tracing each clause to the tables and fields that will supply it. Where a clause is ambiguous, I raise it in writing rather than guess.
Specification versioning is where most organisations quietly break. Measures that share an anchor date and an age band are implemented once, and when the version changes mid-year the change is applied in a rolling window. I keep a versioned implementation with the version applied to each reporting period recorded alongside the results. When the payer reproduces the measure from their own data, the version they are using is visible in the answer, which resolves most disputes in a single exchange.
The artefact that proves the work is a mapping document from each clause of the specification to the SQL that supplies it, with a test case per clause. If a payer disputes a rate, the mapping and the test cases are what gets sent, and they usually answer the question before it becomes a disagreement about data quality in general.
Denominators that match what the contract says
A HEDIS rate that cannot be reconciled to the contract population is a financial and a compliance risk in equal measure. I build the denominator from the membership files with the specification's age anchors and continuous-enrolment rules applied as written, not as remembered. The difference between an 18-month continuous-enrolment window and a 12-month one, or an age anchor at 31 December and 1 January, changes the rate by more than the improvement the programme was attempting.
Membership history is generally messier than it looks on the file. Mid-year changes, retroactive terminations, overlapping products and carve-outs all need a rule, and the rule is taken from the payer's contract and the specification. I encode it once, test it against a sample the payer has verified, and then the denominator stops changing every time someone re-derives it from a different extract.
Every denominator carries the source of the member's enrolment and its effective dates as audit rows. When an audit asks why a member is in or out, the answer is in the data rather than in someone's memory. This is the single most useful artefact during a payer data-validation audit, and it is the one that most commonly does not exist in organisations that chase improvement without checking the base first.
Numerator evidence that holds up
The numerator is where clinical data and claims data meet. A measure like CDC_Hba1c_Tests can be satisfied by a lab claim, a clinical encounter, a supplemental data file, or, in some versions, a pharmacy fill. The implementation must accept all qualifying sources, and it must exclude the data that does not qualify. An out-of-network lab result confirmed only by patient report, for instance, does not satisfy most versions of the measure and it is tempting to accept as one.
Each numerator hit carries the source, the date, the value, and the code system used. That evidence chain is the artefact I hand to the payer when the numerator rate is challenged. The audit trail is also what lets a clinician see that their patient was already compliant, which is often the reason an intervention is unnecessary and a call to the patient can stop.
Supplemental data feeds from systems outside the hospital are often the biggest gap in HEDIS numerator capture. The healthcare interoperability work covers the mechanics of ingesting them. The critical part in HEDIS terms is that each supplemental file is versioned and the measure implementation records which versions were included for each reporting period, so a rerun is reproducible., and each clause of the specification has a matching test case in the suite that runs before every build.
Exclusions and medical record review
Reconciliation includes the payer's own data where they share it, because a preliminary rate from the payer is the fastest way to see where the two sides differ. I rank the measures by gap size, attach each figure's source, and use that ranking to set the next quarter's priorities. In practice three or four causes account for most of the gap, and closing those moves more distance than any general improvement programme. The comparison is rerun each cycle and archived with the submission, so next year's team sees what was fixed and what was not.
Medical record review is the bridge between what is in the data and what actually happened. Some measures depend on findings recorded only in a scanned document, an out-of-network record, or a portal note. I build a sample-and-review queue that the clinical team works through, with reviewer identity, timestamp, the finding captured, and the excerpt. The queue is auditable; the reviewed records enter the numerator with the review trail attached.
Where a record can be pulled through a clinical data feed instead, the C-CDA exchange work is often the route. The advantage of pulling the record rather than reviewing it is scale: review is linear in records, ingestion is not. I favour ingestion where the specification permits it and reserve review for the records that genuinely can only be read by a human.
Reconciliation before reporting
Before any rate is submitted, I run reconciliation against the prior period. A rate that has moved by more than the expected band routes to a review before submission. The review asks three questions: did the specification change, did the membership change, did the clinical data change. Each answer is testable from the warehouse and each test is recorded. A rate that moved because of a data problem is caught before it becomes an audit finding.
Reconciliation includes the payer's own data where they share it, because a preliminary rate from the payer is the fastest way to see where the two sides differ. The comparison table names the measures where the gap is largest, with the source of each side's figure attached, and that table drives the priorities for the following quarter rather than a general push on every measure. In practice three or four causes account for most of the gap, and fixing those raises rates far more reliably than generic improvement campaigns.
The reconciliation workbook with its comparison lines, its top-cause list, and the version of every source is the artefact the quality committee signs before submission. The signature matters, because it converts the rate from an analytics output into a reported number that carries an owner. A rate with no signatory is the kind of number that waits for an audit to be discovered.
Reporting cycle and the audit trail
HEDIS is not a single event. Claims run out, supplemental files close, corrections arrive after submission. I build the cycle as a set of versioned runs with the source cut-offs recorded, the differences between runs summarised, and the rate reported as the signed run for the period. The last run of the year is the one submitted and the one archived with its inputs, so a reproduction is a query on stored evidence rather than a re-run of a pipeline whose code has since changed.
The archive is retained to the schedule the regulator and the payer require. I read the retention requirement rather than assume it, and the archive lives on write-once storage with a checksum per file. The archive is not the same as a database backup and treating it as one is a common mistake that surfaces when an audit asks for a three-year-old submission and the backup tape has been recycled.
The team that runs the cycle is trained on the specification, the reconciliation process and the archive procedure. I run one full cycle alongside them and one under observation before handover. The observed cycle is when most organisations discover an undocumented step, and finding it while the person who built the step is still on the call costs less than rediscovering it during a payer review the following year.
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 — hedis quality measure reporting — 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.
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.