CMS-0057-F · January 1, 2027

A fractional architecture engagement for the 2027 deadlines | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

TRINH — fractional CTO and technology architect, Las Vegas NV
Charles Trinh — Fractional Architecture

Most healthcare organisations do not need a full-time architect

They need one at specific moments: before an integration decision that will be expensive to reverse, during a certification push with a date attached, ahead of a diligence process where the technical story has to survive scrutiny, or when a programme has stalled and nobody can say precisely why.

A fractional engagement is the right shape for those moments and the wrong shape for steady-state delivery, and being honest about which one you are in is the first useful thing I do.

What a first week looks like

I read the architecture and the code paths that matter, then trace one real transaction end to end with a timestamp on every hop. One patient through the patient-access API. One claim through submission to remittance. One authorisation through the 278 exchange.

That trace takes about a week and it tells you more than a quarter of steering-committee meetings, because the failure is almost never where the team believes it is. It is in the entitlement check, the attribution table, the match that returned nothing and logged nothing, or the interface that has been silently replaying a backlog since Tuesday.

What the deliverable actually is

A document that names the defect, the system it lives in, the person who owns it, and the date it will be fixed. Not a slide deck about a framework. Not a maturity model with coloured cells.

Then I check whether the date held, because a remediation plan nobody revisits is a document that was produced for a purpose and abandoned. The revisiting is the part that makes it management rather than reporting.

Where I am useful, specifically

Interoperability architecture. FHIR R4, US Core, SMART on FHIR, HL7 v2, C-CDA, X12 005010, TEFCA and the QHIN model. I have run the ONC (g)(10) Standardized API suite to 317 of 317 subtests against a platform I built, which means I know what the last five percent of those integrations costs.

Identity and consent. Patient matching, MPI strategy, consent as directives rather than a boolean, and segment-level enforcement for the categories that legally require it. I filed a proposed USCDI v7 data element for a Patient Digital Identity Credential with ONC.

Security and compliance evidence. HIPAA Security Risk Analysis under 45 CFR §164.308(a)(1)(ii)(A), control mapping, incident-response authoring with a worked precedent, 42 CFR Part 2 handling.

Cloud and estate operations. A 51-hostname estate on a single AWS account under an active business associate agreement, a 337-table clinical store, Hyperledger Fabric and EVM ledgers, self-hosted mail, and vendor-exit architecture that does not depend on any one supplier surviving.

Diligence. Technical diligence for acquirers and investors where the question is not what the architecture diagram says but what the last ninety days of production error rates say.

How I work

Directly, in writing, with evidence. I do not run a team you never meet, and I do not hand work to a junior and review it. If I am engaged, I am the one reading the code and writing the finding.

I will tell you when the problem is not technical. It usually is not — it is a contract clause nobody read, a workflow nobody owns, or a decision that has been deferred until it became an incident.

Rate card

$195 per hour standard. $165 per hour committed at twenty or more hours per week for three months or more. $1,600 standard day, $1,350 committed day. $2,500 for a diligence day. $10,000 per month retainer at twelve to fourteen hours per week. $550 per hour for expert-network consultations.

No E&O insurance, by choice, and I say so before an engagement rather than after. If your procurement requires it, I am the wrong supplier and you should know on day one.

What I will not do

Sign an assessment I did not perform. Write a document I have not verified against the actual system. Recommend a vendor I have not run. Claim vendor experience I do not have — I have no Epic or MEDITECH implementation background, and pretending otherwise would waste your first month.

Credentials, briefly

Sole proprietor operating as Charles Trinh from Las Vegas, Nevada. SAM.gov UEI MVKQW9DKKGB8, CAGE 20KM5, NPI 1194645564. Eight X12 005010 transaction sets, 104 clearinghouse enrolments across 53 jurisdictions. Founder of MyRxWallet. LinkedIn is the canonical profile.

How to start

Send the thing that is bothering you and the diagram you have. I will tell you within a day whether it is a week of work or a quarter, and whether I am the right person for it. If I am not, I will say that instead of proposing a retainer.

Three engagement shapes

The diagnostic week. One week, one trace, one document naming the defect, the owner and the date. Useful when a programme has stalled and nobody agrees on why. It is the cheapest way to find out whether the rest is worth buying.

The build engagement. A defined scope — an API surface, a consent model, a conformance push — with a start and an end. Priced by the day at the committed rate when it runs twenty hours a week or more.

The retainer. Twelve to fourteen hours a week across whatever is most likely to hurt next. It suits organisations with a small team and a large surface, where the value is having someone who already knows the estate when the question arrives.

What the first month looks like

Week one is the trace. Week two is the gap list with owners and dates. Weeks three and four are the first two items on that list, chosen because they are the ones that make everything after them cheaper.

By the end of the month you have a document, two fixed defects, and a clear answer to whether the rest of the list is a quarter or a year.

What I need from you

Read access to the code, the infrastructure description, one production log stream, and thirty minutes with the person who knows where the bodies are buried. Everything else I can find.

What a retainer actually replaces

It replaces the consultant you would otherwise hire in a panic, the architecture review that arrives four months after the decision, and the vendor evaluation run by the person the vendor is trying to sell to.

Twelve to fourteen hours a week is enough to hold the technical thread on a small estate, provided the organisation can produce decisions. Most of the value is in being present when the question is asked rather than being briefed afterwards, because the expensive choices are usually made in a forty-minute conversation nobody scheduled.

If the engagement is going well, it gets smaller. An external architect whose hours stay flat for a year has either become part of the team or has stopped transferring anything, and those two outcomes need different conversations.

How engagements end

An engagement ends when the organisation can hold the thread without it, and that should be a stated outcome at the start rather than a thing discovered in a renewal conversation.

What handover includes

What it does not include

Dependence on me. An arrangement where the outside architect is the only person who knows why a control exists is a continuity risk dressed as a service, and it is the failure mode most likely to be discovered during an incident at the least convenient moment.

The measure I use is whether a competent engineer, arriving cold, can answer the mover question from what is on disk. If they cannot, the handover has not happened yet regardless of what the calendar says.

The engagement should leave behind something a successor can operate: a decision log that says what was chosen and why, a gap list whose dates survived a review, and the tests that prove the identity model does what the documentation claims. If none of that exists when the hours stop, the work was performed rather than delivered, and the organisation is in the same position it was in before the first invoice with less budget to fix it. The test I apply at handover is deliberately unglamorous: could a competent engineer arriving cold answer the mover question, the revocation question and the trace question from what is on disk, without calling anyone? If the answer is yes, the engagement succeeded whether or not the slides were ever finished. If the answer is no, the engagement produced activity, which is not the same thing and is considerably more expensive to discover later. That is the whole discipline: leave the estate legible to the next person, and leave the decisions written down where the next person will actually find them.

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

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.

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.

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

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 a fractional architecture engagement for the 2027 deadlines — the scope, the failure modes it prevents and how the work is measured. It sits in the Advisory 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.