CAPABILITY STATEMENT · FEDERAL · ONE PAGE

Charles Trinh — Capability Statements | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading Capability Statements — one page written for the buyer
Charles Trinh — Capability Statements

Writing a capability statement that federal buyers actually read: the mandatory elements, the differentiators that survive a skim, and the one page that is checked against the solicitation rather than against the company's history.

The page has elements, and they are checked

A capability statement is a one-page document with recognised sections: identification with the UEI and CAGE code, core competencies, past performance, differentiators, company data and contact points. Buyers and contracting officers read it against those headings, which means a statement in an unfamiliar format is read as an incomplete submission rather than as a creative one. The headings are not a suggestion; they are the index the reader uses.

Each section has a failure mode. Core competencies are too generic, past performance is unverifiable, differentiators are adjectives, and the company data omits the identifiers the buyer needs to look you up. Writing against the failure modes is faster than writing an aspirational statement and editing it down.

Keep the identifiers current. A statement carrying an expired registration or the wrong points of contact is worse than no statement, because it communicates that the record is not maintained.

Core competencies are specific or they are nothing

A competency phrased as a category tells the reader what you say you do; a competency phrased as a delivered outcome tells them what you have done. The second is longer and it is the one that survives a skim. Three to five competencies, each specific enough that a reader could ask a follow-up question about it, beats ten that could describe any company in the industry.

Map each competency to the work the buyer actually procures, using the buyer's vocabulary rather than yours. Where the buyer's vocabulary is prescribed by a standard or a regulation, use it exactly, because a reader looking for the phrase will not search for a synonym.

Where a competency is new rather than delivered, describe the underlying capability honestly and let the past performance section carry the evidence. Overstating a competency is discovered during the first conversation and costs the relationship.

Past performance that can be verified

Past performance entries need a customer, a period, a value, a contact and a description of what was delivered, and the contact is the part that makes it performance rather than a claim. A reference who can be called is worth more than a paragraph of description, and the statement should make that obvious by naming the customer and the period rather than describing the relationship in general terms.

Where a reference cannot be named, describe the work and say the reference is available on request; buyers understand confidentiality and they do not understand vagueness. Where the work was for a commercial customer, say so, because commercial performance is acceptable evidence in many evaluations and pretending otherwise wastes the entry.

Keep the references warm: tell each customer that they may be called, and tell them what they might be asked. A surprised reference is a poor reference, and the courtesy is small.

Differentiators that are not adjectives

Differentiators are where most statements collapse into words like experienced and trusted, which describe nothing and appear in every competitor's document. A useful differentiator names a specific capability, a specific credential, a specific outcome or a specific constraint the company can meet that others cannot, and it is checkable.

Three specific differentiators are enough. Where a differentiator is a certification or a credential, state it and its date; where it is a capability, describe the evidence; where it is a cost or schedule advantage, explain the mechanism rather than the benefit.

Avoid superlatives entirely. The reader is comparing several statements and the one with the fewest adjectives usually reads as the most credible.

Keeping it current

A capability statement ages quickly: identifiers expire, references change jobs, competencies acquire new evidence and old claims become stale. Review it quarterly against the current registration and the last three engagements, and rewrite rather than patch, because a statement assembled from successive edits accumulates contradictions.

Keep the source material separately: the reference list, the credential list, the past performance write-ups and the identifiers. The statement is a rendering of that material, and maintaining the material is what makes the quarterly review take an hour rather than a day.

Finally, version it. When a buyer asks why a statement said something different last year, the version history is the answer, and it is also the record of the judgement that was made at the time.

Matching the statement to the opportunity

One statement for every occasion is efficient and weaker than three tailored versions for the sectors a company actually sells to. The competencies, the past performance and the differentiators should be chosen to match the buyer's requirement, which means keeping the underlying material in a library and rendering a statement per sector rather than rewriting from scratch. The library approach takes an afternoon to set up and a quarter of the time per statement afterwards.

Where the company pursues a specific opportunity, render a version that names the requirement in the buyer's words and leads with the evidence closest to it. That version is not a different document; it is the same material ordered for the reader, which is exactly what the one-page format rewards. Buyers can tell the difference between a statement written for them and a statement written for everyone, and the difference shows up in whether they call.

Keep every version with the date and the opportunity it was written for, so the library grows into a record of what has been submitted rather than a folder of near-duplicates.

The statement as a sales instrument

The capability statement is used in two places: a formal submission where it is one of many documents, and a short conversation where someone asks what the company does. The same document serves both only if it is written in plain language that a non-specialist can follow in thirty seconds, which is a harder standard than it sounds and the one that produces the most value. A reader who understands what the company does in half a minute can decide whether to ask a second question, and the second question is where the engagement begins. That is why the statement should avoid the industry's internal vocabulary, describe the outcome rather than the technology, and put the one thing that distinguishes the company where a skimming reader will see it first. The document is not a brochure; it is a decision aid, and the standard is whether the reader knows what to do next.

A statement should also survive the reader who is not a buyer: a programme manager circulating it internally, an analyst scanning vendors, a partner considering a bid. That reader uses it to categorise the company, and the categorisation determines whether a request for information arrives six months later. This is why the first sentence matters more than the layout, and why the document should open with what the company does rather than with who founded it. The reader's next action is the only measure of whether the statement worked, and the next action is almost always a request for more detail, which the statement should make easy by making the company findable.

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 — capability statements — the scope, the failure modes it prevents and how the work is measured. It sits in the Regulatory and Capital Markets 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