REGULATORY

Charles Trinh — Quality Payment Programmes | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Dashboard showing quality measure scores and penalty and earning thresholds for a reporting year
Charles Trinh — Quality Payment Programmes

The Quality Payment Programme turns clinical measures into money. Whether a practice earns, breaks even or pays a penalty depends on measure selection, data integrity and submission mechanics agreed long before the reporting window closes.

Measure selection is a strategic decision, not a menu

The performance categories in the programme are scored against a threshold each year. The threshold moves, and the mix of measures that earn full credit changes. A practice that selects the same measures every year risks falling below the threshold as the scoring floor rises, or scoring poorly against peers as the national average improves. I treat measure selection as a portfolio decision: which measures the practice is likely to score well on, which can be improved by changes within its control, and which are almost certainly weak.

The decision involves the clinical leadership and the practice's data, because the measure with the highest potential return is usually the one where the practice already has a plausible path to a higher score. The decision record names the measures chosen, the reasons, the expected points for each and the fallback measure if the primary one proves impossible. That record is signed and dated so the strategy is visible when a year's results are reviewed.

The artefact is the measure-selection plan, a single page per year. Practices that skip the artefact often select by habit, then discover the issue mid-reporting-year when it is too late to change.

Data integrity determines whether a high score stands up

Scores can be high and still be rejected. The programme validates submissions against the measure's own logic. A measure that expects a numerator and denominator built from specified code sets fails when the code is missing, and a failure cascades. I build an integrity test that runs in the practice's own data before submission and checks for the conditions the programme's validator will flag: missing structured fields, unmapped codes, records outside the reporting period, and inconsistent attribution of the servicing provider.

The data-integrity work runs monthly during the reporting year, not before the deadline. Monthly is frequent enough to catch a workflow change that broke a measure and infrequent enough not to swamp the operations team. Each monthly run produces a short report: measures that are on target, measures below target and the reasons, and the remediation owner per finding. The reports accumulate into the submission readiness folder.

Data integrity extends to the electronic record itself. I have seen practices lose points because a clinical workflow was swapped to free text for a single facility. Monthly monitoring catches the change on the next run and the practice can restore the structured workflow before the quarter closes.

Attribution is where score calculation becomes complex

A measure is often attributed to a specific provider or entity. Attribution rules decide which practice receives credit, and exceptions decide which patients should be removed from a measure's denominator. Getting attribution right is not a technicality: a patient attributed to the wrong provider can count against a practice's score when the care was delivered elsewhere. I model the attribution rules in the practice's data before submission, then reconcile against the programme's own attribution where available.

I build a query that shows the patients by measure and by provider, so that the operations team can review subsets and identify both mistakes and clinically sensible exclusions. A patient with advanced disease may be eligible for an exclusion the practice has not taken. Reviewing those exclusions properly improves the score honestly and also improves the practice's understanding of who its chronic-care population actually is.

The review is documented per measure. The record is not simply an output; it is the practice's rationale for its denominator, and it matters if the programme reviews the submission.

Submission pathways are chosen for resilience, not just convenience

There are several routes to submit data: through qualified registries, through the certified electronic health record, through a health IT vendor and through a manual attestation. Each has different failure modes. Registries are generally robust, but they add a dependency on a third party who has its own submission day. Record-based submissions vary by product and by version. Manual attestation is the simplest and the most exposed to human error.

I select the submission path based on three criteria: the organisation's control over the data pipeline, the vendor's track record and the organisation's ability to test before submission day. I require a full dress rehearsal against a test environment of the validator or the registry. The rehearsal is scheduled weeks before the submission window, and the data used is the same data that will be submitted. When the rehearsal produces a failure, the practice has time to fix the root cause and re-submit before the window closes.

A backup submission route is essential. I maintain the ability to submit a secondary pathway, even if it produces partial credit, so the practice is never in the position of missing the deadline because its primary route failed. That ability is a small amount of preparation and a large amount of risk reduction.

The cost of a bad year is a penalty applied to future earnings

Failure to meet the programme's thresholds produces a penalty applied to future Medicare payments, calculated against a formula that has grown steeper over time. The penalty is not a one-off bill; it is a percentage reduction applied repeatedly to future payable amounts. A practice that falls below the threshold by a small margin can lose the equivalent of a full-time employee's salary in a year, announced a full cycle later.

I model the exposure before the reporting year begins, using the practice's historical scores and volume. The model names the gap between what the practice is likely to earn and what the threshold requires, so the practice can decide how much investment in data workflows and measure selection is justified. The answer is often that a single additional measure, selected and monitored well, moves the practice from a penalty to a positive adjustment.

The model is reviewed with the practice's finance lead so that the exposure is understood where it is felt. Practices that treat the programme as a clinical governance issue alone often underinvest in the data workflow side, where the penalty actually accrues.

Peer comparison shows where the practice stands

The programme publishes performance data that allows a practice to compare itself against its peers. The comparison is useful for calibrating expectations. A measure that scores well in a rural practice may score poorly against a specialty-heavy cohort. I build the comparison into the measure-selection review so that the practice knows when it is at the national average and when it is behind.

The comparison is also a signal for clinical quality. Where a measure is low because the practice's care process is genuinely weaker, the answer is a care improvement programme rather than an exclusion strategy. I separate measures that are low for care reasons from those that are low for data reasons, because the remedies are completely different and the practice's effort should go where it changes care as well as scores.

The practice should review the peer data annually, accept the peer group that reflects its own mix and avoid cherry-picking a favourable cohort. A peer group chosen for appearance of proficiency rarely survives an honest look at the trend line.

What a healthy programme looks like between reporting cycles

Between cycles, the programme runs monthly data checks, quarterly reviews of the measure portfolio and an annual peer review. The cycle itself is a check box inside that rhythm. Teams that have gone through a loss year restructure into this rhythm. The practice gets a durable habit out of the programme, not a crash project.

I hand over the measure plan, the data-integrity routine, the attribution review and the rehearsal calendar, all owned by named roles. The finance lead carries the exposure model, the clinical lead carries the measure portfolio and the data lead carries the routine. When a programme criterion changes, the practice reads it against the plan and decides whether to adjust the portfolio rather than starting over.

The programme is unforgiving to practices that treat it as an annual event. The practices that do well treat it as a seasonal rhythm, where each season has its own work and no season has all of it.

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 — quality payment programmes — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance 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

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