REGULATORY

Charles Trinh — Medicaid Interoperability Rule Compliance | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Matrix of Medicaid plan types against the interoperability interfaces each owes
Charles Trinh — Medicaid Interoperability Rule Compliance

Medicaid programmes inherit the same interoperability obligations as commercial plans, on staged compliance dates that vary by state contract. The work is mapping which interfaces each managed care plan owes, and when.

The contract sits above the regulation and can change the scope

A Medicaid plan is bound by federal interoperability obligations and by the contract it signed with a state agency. The two rarely mean the same thing. The contract can extend the scope to a programme the regulation never contemplated, or leave an interface to a sister entity such as a state fiscal agent or a delegated pharmacy benefits manager. I always start by reading the state contract alongside the federal rule, because the governing document for a given plan in a given state is the one the state enforced at procurement.

Contract language is also where the dates live. States stagger their requirements by plan type, by programme and by the size of the membership. The plan's compliance calendar is a union of every obligation on the contract, with each item assigned to an owner inside the plan and, where a vendor is involved, to the vendor's counterpart with a note on who inherits the risk. A test that passes at the vendor does not satisfy the plan's obligation unless the contract says it does.

The artefact is a contract obligations register: one row per clause that creates an interoperability duty, with the interface affected, the deadline, the owner, and the state of evidence. The register is reviewed against each amendment and each renewal, because the obligation moves with the contract.

Delegation changes who does the work but not who is accountable

Large Medicaid programmes expect the health plan to delegate segments of the interoperability work, particularly pharmacy, behavioural health and long-term services. Delegation is common and reasonable. What is not reasonable is treating delegation as a transfer of accountability. The plan remains responsible to the state for the quality of the interface, and remains responsible to members for access to their data.

I build the delegation agreement checklist to include monitoring rights, evidence obligations and remediation timelines. The vendor must give the plan a route to test its interfaces independently, and a defined escalation path when a test fails. Where the contract has these provisions, the work is assembly. Where it does not, I design an amendment or a side letter, because without it the plan is dependent on the vendor's word.

The plan is usually a composite of several vendors, each of which operates one piece of its data. Mapping the interface to the vendor and the vendor to the contract makes it obvious which gaps carry the largest exposure, and it is how I decide where to spend the limited testing capacity.

Member access is a public-facing duty with high visibility

Member access to health information through a third-party application attracts the most attention of any obligation in the rule. For Medicaid, the population is large and the demographics differ from commercial plans: more mobile-only users, more language variation, more reliance on community organisations for help. The access interface is tested by application developers, by advocates and by the state. A failure is not an internal incident.

I test the interface with the population's realities: an application that requests on behalf of a parent's account, an application whose developer support is weak, and the variations in identity verification a state contract may require. Each of these reveals something about the user experience. I report findings to the plan alongside the technical test results, because the state will ask about the member experience and not just the endpoint.

The plan should keep evidence of the interface's behaviour over time, not only at certification. A quarterly run of the interface against a representative sample of members gives that evidence, and I design that run so it can be executed by the plan's own staff.

Provider look-up and claims status carry plan-specific expectations

A managed care plan sits in the middle of a provider's network. The provider directory interface is therefore read by providers trying to confirm coverage under a specific plan, and it needs to reflect the plan's network truthfully. State contracts often add a requirement to update the directory when the plan changes network status, and to publish it on the state's own portal. That is a second integration that many plans forget until the state tests it.

Claims status is similar. The regulation requires a status interface; the contract may require it to mirror what the state's claims system shows for the same plan. I map the interface to the plan's own processing system, then map that system to the state's expectations. Any gap in the chain is a defect, even if the plan's system works fine on its own.

The artefact is a network-to-interface reconciliation that runs monthly and flags divergence with reasons. It is the report the state will ask for when a provider disputes the directory.

Prior authorisation under Medicaid has its own rules

The prior authorisation interface owed by a Medicaid plan often runs in parallel with a state authorisation system, a delegated utilisation management vendor, and the plan's own criteria. The interface is one component of a complex authorisation workflow. I start with the workflow, then design the interface so that each step is visible to the referring provider and each step is pushed to the available channels rather than being held until the plan's own system reflects it.

Authorisation windows are handled as exceptions. The plan will define classes of authorisation by urgency and by service, and each class has a deadline. I build the deadline reports into the interface's own tracking, so the plan can see which requests are at risk of breaching a window before they do. This has a side effect: it surfaces the cases that require clinical escalation, which improves the plan's operational picture as much as it improves compliance.

The test plan covers urgent and non-urgent classes, with volume assumptions agreed with the plan's operations team. Volumes drive the automation share, which drives the staffing model.

Quality of reporting drives the renewal rather than the first go-live

State agencies review plan performance on data. Interoperability performance is one of the measures the agency will use at renewal. Plans that approach the interface as a point-in-time compliance item often find the renewal conversation harder than the launch, because the agency asks for trend data that they do not collect. I define the metrics the agency is likely to request and set the routines so that data for those metrics is captured from the start.

The definitions matter as much as the collection. Volume counted before and after de-duplication produces different numbers, and the difference is the sort of discrepancy that costs a plan credibility at a hearing. I ensure that the metric definitions are written and accepted by the state's own programme team at the start of the contract year, so that there is a record of what was agreed.

The reporting rhythm follows the contract reporting cycle, with a quarterly internal review that occurs before the state submission so that the plan has time to fix issues rather than report them.

What a plan should see when the programme is healthy

A healthy Medicaid interoperability programme has a register that is current, delegations that are tested independently, interfaces that produce measurement reports the state can corroborate, and an operational rhythm that anticipates the renewal. The programme does not feel like a compliance project. It feels like a set of services with owners, and the compliance file is the byproduct.

I hand over with the register, the reconciliation routine and the state reporting calendar populated. I also hand over with the internal owners trained: the plan's contract managers, its interface owners and its analytics team. Those roles carry the programme forward between contract amendments and turnover.

When the state changes the contract, the programme absorbs it because the register and the interfaces are organised around obligations. That is the test of whether the work was designed for compliance or merely dressed up as compliance.

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 — medicaid interoperability rule compliance — the scope, the failure modes it prevents and how the work is measured. It sits in the Interoperability 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