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

PECOS enrolment and revalidation: the record that must stay current, the change reporting that is easy to miss, and the timeline that stops a claim batch mid-quarter.
Enrolment is a live record
PECOS is not a one-time application. It is a record that must be updated within stated windows when ownership, address or practice scope changes, and the obligation does not lapse because nobody reminded you.
A missed reporting obligation becomes a payment suspension that arrives without warning and stops a quarter of revenue.
Own the revalidation calendar
Track revalidation due dates as inventory with named owners, and start each cycle early enough to survive a rejection and a resubmission.
Keep the supporting documentation that produced the original record, because revalidation asks for it again and the people who assembled it have often moved on.
Reconcile against the clearinghouse
PECOS identifiers and clearinghouse enrolments drift apart silently. Reconcile them quarterly, since a mismatch produces rejections that look like data errors and route to the wrong team.
Record every change you submit with a date and a confirmation reference, because disputes are settled by evidence rather than recollection.
Evidence for the reviewer
Keep a single table: entity, enrolment type, effective date, last verified, next action, owner. It answers the reviewer's question in one lookup and shows you the gaps before they ask.
Review it monthly rather than annually, because enrolment problems compound quietly until they surface as a payment event.
The record, not the application
An enrolment is a state that must remain true, and the obligations attached to it are continuing: report changes within stated windows, respond to revalidation, keep the supporting documentation available. Organisations tend to treat enrolment as a form they completed once, and the consequence is discovered when a payment is suspended for a change that was never reported, often a change somebody in operations considered administrative rather than regulatory.
Assign the record to a named owner and put the review on a calendar. The owner is responsible for the change-reporting question, which means they need to know when ownership, address or practice scope changes, so their contact list matters as much as their diligence. Where the owner is in operations rather than compliance, the reporting obligations need to be in their runbook in plain language.
Revalidation as a project
Revalidation cycles arrive on the payer's schedule, and starting late turns a routine exercise into an emergency. Start each cycle early enough to survive a rejection and a resubmission, because the resubmission is the normal case rather than the exception and the clock does not pause while it happens. Keep the documentation that produced the original record in a retrievable form, since revalidation asks for the same evidence and the people who assembled it have often moved on.
Track due dates as inventory with owners and status, not as a reminder in somebody's calendar. The inventory is also the report that answers the question when a suspension arrives, because it shows whether the cycle was started, what was submitted and when the confirmation came back.
Reconciling against the clearinghouse
PECOS identifiers and clearinghouse enrolments drift apart, and the drift produces rejections that look like data errors and route to the wrong team. Reconcile them quarterly against the inventory, and treat every mismatch as either a data correction or an enrolment gap rather than as an unexplained rejection pattern. The reconciliation takes an afternoon and removes a recurring class of ticket.
Record every change submitted with a date and a confirmation reference. Disputes about whether a change was reported are settled by the confirmation rather than by recollection, and the reference is the difference between an organisation that can prove its position and one that can only describe it.
Evidence for the reviewer
A single table answers most questions: entity, enrolment type, effective date, last verified, next action, owner. It is short enough to review monthly and complete enough to answer an examiner without an investigation. Reviewing it monthly rather than annually is what keeps the gaps small, because enrolment problems compound quietly until they surface as a payment event that nobody can trace.
When the table shows a gap, the gap is a project with a date rather than a note. The most common are an address change reported nowhere and a taxonomy that does not match the services being billed, and both are cheap to fix before a suspension and expensive afterwards.
Change reporting in practice
The reporting obligations cover changes that operations does not always consider changes: a new practice location, a change of ownership percentage, a new billing agent. Each requires the record to be updated within a window, and the window does not care whether the change was announced internally. Publishing the list of reportable changes in the operations runbook, in plain language, is the cheapest control available, because the person who knows about the change is the one who has to recognise it.
Where a change is reported late, document it with the date and the reason rather than quietly correcting the record. The disclosure is usually survivable and the concealment is not, and a record of late reporting demonstrates a process rather than the absence of one.
The supporting evidence file
Keep a file per entity that contains the documents behind the enrolment, the correspondence, the confirmations and the dates. When a reviewer asks for the basis of a record, the file answers in minutes, and when a revalidation arrives, the same file supplies the evidence without a search. The discipline is a filing convention and a named owner, and it is the difference between an answer and an investigation.
Working with a billing agent
Where a billing agent submits on the entity's behalf, the enrolment record and the agent's authorisation have to agree, and the agent's own enrolment can lapse independently. Check both annually and whenever the relationship changes, because a lapse on either side produces a rejection that neither party initially understands.
The monthly review, in ten minutes
Open the inventory, read the rows whose next action is in the past, and assign or close each one. The review is short because the table is short, and the shortness is the point: a review that takes an hour is a review that gets postponed, and the gap that matters is always the one that was postponed twice. Record the review date and the person who performed it, because the record is what turns a habit into a control.
Escalate anything that has been carried three months. Three months of carrying is a decision that the item will not be done, and it should be made explicitly rather than by attrition.
What a lapse costs
A lapsed enrolment does not present as an error; it presents as a rejection with a code that points at the claim or the provider record, and the team that receives it usually does not own the enrolment. The elapsed time between the lapse and the suspension is spent on the wrong system, and the cost is measured in days of billing rather than in the correction itself. Knowing that, the review cadence should be set against the volume of claims per provider-payer pair, not against a calendar, because a high-volume pair can lose a week before anyone notices.
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 — pecos enrollment — 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.