REGULATORY
Charles Trinh — Medicare Advantage Interoperability | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Medicare Advantage plans carry interoperability obligations across enrollee, provider and payer-to-payer interfaces. The plan types, delegated functions and star-rating pressures make the engineering problem narrower and the reporting pressure larger.
The plan gets a second set of rules from the annual notice
A Medicare Advantage plan is subject to the interoperability rules it shares with commercial insurance and to the annual instructions published by CMS in advance of each contract year. The annual notice often restates the rules, adds reporting requirements and clarifies the interface scope. I read the annual notice alongside the rule every year, because the instructions interpret the rule in ways that only the annual notice covers.
The instruction set is not a light read, but it is the specific source for deadlines, reporting content and the data definitions the agency expects. Where the rule is silent on an operational detail, the notice usually fills it in. I build an interpretation register that lists the notice's items, the rule text they relate to, and the implementation approach chosen. The register is signed by the plan's compliance lead and the technology lead, so the decisions are visible before they are tested.
Without the register, the plan's engineering decisions become invisible until the annual review. By then the plan has lived with its own interpretation for a year, discovered a mismatch and must argue about it under pressure.
Enrollee-facing access carries star-rating sensitivity
The enrollee access interface allows a member to retrieve claims, coverage and clinical data through a third-party app. For Medicare Advantage, the interface runs alongside the plan's own member portal and its customer service channels. Star ratings include measures around member experience, and a member who struggles with an application receives help through the plan's channels. The interface and the member experience are connected even when they are delivered by different parts of the organisation.
I map the interface's failure modes onto the member experience path. When an application cannot retrieve a claim because the interface returns an error, where does the member go, what does the plan's customer service see and what does the plan tell the member. A gap in that path becomes a customer service call, and enough of them become a star-rating issue the plan did not anticipate in its interface project.
The artefact is a member-facing access journey with the interface at its centre. The plan owns the journey even where the application is developed by a third party.
Provider access must reflect provider reality
The provider access interface enables a provider to check a member's coverage and authorisation through the plan's own systems. For Medicare Advantage, providers are often the same systems that serve the plan's other lines of business, and the interface may be implemented at the enterprise level. The plan's own provider directory also feeds the interface, and the accuracy of the directory is measured by CMS through its online directory tool.
I check the interface output against the plan's provider directory and against the provider's own experience. A provider listed as in-network who is out-of-network in the directory is an issue the plan must resolve, regardless of which system asserted the truth. I build a periodic reconciliation from the directory through the interface to the member system and flag divergence with reasons. The reconciliation is published to the plan's network management team and owned by the network manager, not by the interface owner.
The provider experience matters for access and for network adequacy, and the interface can expose problems that the plan's own dashboards have not surfaced. A quarterly report of the reconciliation is the artefact I hand over.
Payer-to-payer exchange is smaller in volume but higher in complexity
The payer-to-payer exchange allows plans to request data from another plan when a member changes plans, with the member's permission. Each request requires an authorisation that identifies the requester and the member, and it must be honoured within the rule's timelines, which are short. The complexity arises from the multi-dimensional coordination: the requester does not know the responder's internal systems, and the responder may have delegated data sources that must contribute before the response is complete.
I design the exchange so each request produces a traceable id, the request's authorisation evidence, and a record of the sources that supplied data. The response may be assembled from multiple internal systems. I require the assembly to produce a coherent document rather than a set of disparate extracts. Requests that cannot be fully answered are reported with reasons and a route for the requester to follow up.
The volume is small enough that manual handling is a temptation. I resist it. The exchange record is a data artefact that gets audited and it must be machine-generated, or the plan cannot reproduce its own behaviour consistently.
Delegated functions shift the engineering work, not the obligation
Medicare Advantage plans commonly delegate pharmacy benefit management, utilisation management and care coordination to vendors. Each delegated function may carry its own portions of the interoperability obligations. The plan's contract with the vendor determines the engineering work. CMS expects the plan to demonstrate that the delegated work is consistent with its own compliance obligations.
I map each delegated function to the interfaces it must supply, and I test each vendor's delivery independently. Where the contract gives the plan the right to inspect and test, I exercise it. Where it does not, I build a monitoring arrangement that depends on observable data, because testing is impossible without a clause. The arrangement produces evidence to the plan and the plan presents it to CMS in the same form it presents for its own interfaces.
I document every vendor's contribution and every gap in the contract. When the plan's annual compliance review happens, the register is the evidence base. It answers the question the agency always asks: how do you know the vendor is behaving as required. The answer is a test result, not a contract signature.
Reporting is measured against the agency's definitions
CMS requires plans to report on their interoperability activities. The reporting covers the interfaces, the volumes and the enrollee and provider experiences. The plan's report is judged against the agency's own definitions, and these are specific. A plan that uses its own methods and then reconciles to the agency's definitions risks appearing non-compliant even when it is not.
I build the report from the measurement pipeline. The pipeline collects interface outcomes, volumes and member complaints. Where the agency's definitions differ from the plan's internal metrics, the pipeline provides both columns and reconciles between them. The reconciliation is the artefact that protects the plan when questioned. It shows that a difference is a definitional difference and not a data error.
The reporting rhythm should be quarterly, with an annual report that consolidates them. The plan's data team reviews the reconciliation, and the compliance lead signs the report before submission.
Interoperability and the plan's star ratings are linked in practice
Star ratings depend on member experience, health outcomes and performance measures. Interoperability supports all three: enrollee access through apps, provider access to coverage and authorisation, and exchange between plans. A plan that invests in interoperability support for the provider's experience can influence provider satisfaction, which in turn influences member experience and, indirectly, the plan's star rating. The connection is not mechanical, but the plan should treat the interoperability programme as part of its member experience investment.
I present the interface programme results alongside the plan's star-rating metrics, with an explicit note that the link is indirect. The aim is not to claim causality. It is to let the plan see the whole picture when deciding where its effort goes. Plans that treat interoperability as a compliance cost tend to under-invest in the provider experience, and providers notice.
The programme closes with a written handover: the interpretation register, the reconciliation reports, the delegated-function evidence and the reporting pipeline. The plan's team can run the rhythm without me, and it can produce the annual report in days rather than months.
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 — medicare advantage interoperability — 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
- 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.