REGULATORY
Charles Trinh — ACA Marketplace Integration | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Marketplace plans depend on real-time accuracy between eligibility, plan comparisons and enrolment. Integration failures show up as rejected applications, mispriced premiums and members discovering problems after they have signed up.
The marketplace is a moving target by design
The federal marketplace and the state-based marketplaces revise their technical specifications, data requirements and business rules regularly. Carriers that build once and hope for the best are the carriers that get caught by a change in plan-year requirements the week before open enrolment. The integration has to absorb changes without a rebuild each time, which begins with separating stable business concepts from volatile implementation details.
I model the plan's own business objects: plans, rates, plan comparison inputs, enrolment requests, eligibility determinations and effectuation events. Each object has a contract, and the contract is the place where the marketplace's requirements enter. When the marketplace changes a field, the change is absorbed inside the contract rather than across the codebase. That discipline is what allows a carrier to begin open enrolment with confidence even after a busy specification year.
The artefacts are the object contracts and a specification register that tracks each marketplace requirement against its implementation. The register is reviewed at the start of each plan year, before the first integration test, so the delta is understood early.
Eligibility determinations drive the commercial outcome
The eligibility assessment at the marketplace determines the premium tax credit, the cost-sharing reduction tier, the benchmark plan and the net premium. An integration that gets the determination right for an average applicant can still fail for the applicant whose household income is unusual or whose citizenship status is verified through a document trail. Those failures are the ones that appear in a member complaint, and the ones that can cost a plan its relationships with brokers.
I build a testing programme that uses the widest variety of applicant profiles the marketplace will allow, including the profiles that trigger verification, ineligibility, and special enrolment periods. Each profile is checked through the integration and through the plan's own downstream processing. Where the integration's answer differs from the marketplace's recorded answer, the difference is a defect with a named owner.
I keep the profile set as a living test artefact. At each plan year, the profile set is extended with any new rules the marketplace has introduced, and the suite is run before open enrolment begins, not during it.
Enrolment and effectuation involve more events than candidates assume
An enrolment is not a single event. It is an application, a plan choice, a transmission to the marketplace, an effectuation confirmation and a member record in the plan's own systems. Each of those events has to be reflected across channels and reconciled, and errors can occur at any of them. An enrolment that is accepted by the marketplace but not effectuated in the plan's system creates a member who believes they are covered, and who learns otherwise when they see a provider.
I build a reconciliation routine that compares the marketplace's own record of effectuation with the plan's own record of member creation. The routine is scheduled daily during open enrolment and weekly in the rest of the year, and it produces a list of exceptions for operations. Each exception has a cause code and a resolution path. Common causes include duplicate enrolments, address changes between application and effectuation, and marketplace corrections that arrive after the plan has posted its own record.
The routine is the artefact that keeps a plan honest during open enrolment, when volume overwhelms the manual process. I have worked with plans that discovered thousands of unmatched enrolments at the end of January, which had been silently compounding since November.
Plan comparison data has a hard deadline and a public contract
The plan comparison data that drives the marketplace's shopping experience is generated by the carriers and published by the marketplace. The data is deep: networks, drug lists, cost-sharing, service areas, and plan designs. Each field has a deadline by which the data must be submitted, and after that deadline the data is visible to the public. Errors are visible, and correcting them requires a correction request with the marketplace.
I build the process around the data's own lifecycle. The plan's actuarial and product teams own the truth of each field; the integration team owns the mapping to the marketplace's format and the submission mechanics. We implement a pre-submission review that renders the plan's data through the marketplace's own display logic using a test environment, so the team can see what shoppers will see. That review catches issues that the technical submission does not.
The plan-year calendar is built around the data deadlines and their public display. The process repeats every year with the same rigour, because the deadline is absolute and the error is publicly visible.
Special enrolment periods and broker channels require separate pathways
A meaningful share of enrolments occurs through broker-facilitated applications, and through special enrolment periods that require verification of a qualifying event. These paths have their own rules. A broker's application has to reconcile with marketplace records; a special enrolment period application has to verify the event before the enrolment is accepted. Each path is a potential integration gap if it is treated as a variation of the standard path.
I map each path to its rules and test each one. The broker path typically has more application-level complexity, because the broker's software submits on the member's behalf, and a failure in the broker's tool shows up as a plan-side complaint. I include the broker channel in the plan's own reconciliation reports, even where the broker is technically responsible for the failure, because the plan is the party the member calls.
For special enrolment periods, I test the specific events the marketplace's rules support and record the plan's processing of each. That record is what the plan uses in disputes about eligibility and in any marketplace audit of the plan's own records.
Exchange failures must be recovered, not merely logged
No integration is perfect. The question is how the integration behaves when a system on the other side is slow, down or responding with an error. An enrolment request that is retried can produce a duplicate. A request that is not retried can leave a member unenrolled. Each case requires a recovery strategy, and the strategy should differ per scenario. I design each call with an explicit handling strategy: idempotency keys, verification after failure, and escalation at defined timelines.
I test failure handling deliberately, with fault injection in a test environment. Each fault type is associated with an expected handling path, and the path is checked for recovery completeness. When the environment supports it, faults are injected during the plan's own testing so that operations teams have seen the failure before production. That works far better than documentation in a runbook.
The artefact is a failure-handling matrix, one row per integration call, with the strategy, the test result and the operational owner. The matrix is reviewed before each plan year.
Open enrolment is a season, not a date
Open enrolment is a defined window in which volume reaches a peak, errors become visible and operations teams meet their busiest period of the year. The plan should be ready before it starts, and the readiness has to include the people side as well as the technical side. Members assume that if the plan's website says they are enrolled, they are enrolled. If they are not, they discover it when they call.
I focus every winter on the things that lose members in January: unmatched effectuations, brokers whose applications did not carry across, and marketplace corrections that never made it into the plan's own record. The remedies are rarely software. They are reconciliation routines, exception queues and clear ownership for a short, intensive period.
I prepare them, run them through rehearsal, and hand over before the season begins. The result is a plan that starts January with the same enrolment count it started enrol ment with, and does not spend February explaining the difference.
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 — aca marketplace integration — 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
- 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.