sam.gov · uei · fedramp · contracting

Charles Trinh — Federal Agency Integration, Las Vegas NV

Charles Trinh — Federal Agency Integration, Las Vegas NV
Charles Trinh — Federal Agency Integration, Las Vegas NV

Working with federal buyers: entity registration, the identifiers that gate payment, security posture expectations, and the paperwork that decides whether you can be paid.

The identifiers gate everything

UEI in SAM.gov, CAGE code, and the banking details in the System for Award Management must agree with each other and with your invoices.

A mismatch does not fail loudly; it fails as a payment that never arrives, three months later, with no owner.

Review entity registration before every submission, because expiration is silent and disqualifying.

Registration as a living record

Renew annually, keep the NAICS codes aligned to what you actually bid, and keep the points of contact current.

The representations and certifications are legally binding statements; treat them as such rather than as form-filling.

Assign one person to own the record and record when it was last verified.

Security posture expectations

Federal work increasingly expects a defined posture; FedRAMP for cloud services, or a documented equivalent for smaller engagements.

Know which requirement applies to which contract vehicle before you bid, because discovering it after award is a schedule problem you cannot fix.

Where you cannot meet a requirement, say so in the proposal rather than discovering it in a security review.

Invoicing and payment mechanics

Wide Area Workflow or the agency's equivalent, proper invoice elements, and a receiving official who will accept it.

An invoice that is correct but not in the system is an invoice that does not exist.

Track invoice status as a first-class work item with an age column.

Subcontracting and teaming

As a prime you carry flow-down obligations; as a sub you inherit them.

Read the flow-down clause list before signing, because the obligations do not shrink because your contract is small.

Keep the teaming agreement and the subcontract aligned on scope and payment terms.

What actually wins work

A capability statement that names the specific requirement, past performance that is checkable, and a price that reflects a real cost model.

Vague capability statements lose to specific ones even when the underlying capability is stronger.

Keep the statement to one page and make it about the buyer's problem rather than your history.

How I do it

One trace of a real case with timestamps at every hop, before any document is written.

A findings list naming the defect, the system, the owner and the date, reviewed monthly.

No attestation I did not test, and no template sold as an assessment.

Finding the opportunity

Opportunities are published with identifiers and attachment sets; reading them properly is the difference between a responsive bid and a disqualified one.

Track the deadline in the timezone the notice names, and the question deadline separately, because the second one passes earlier and quietly.

Keep a log of every notice read and every decision made, because the audit trail matters when a bid is challenged.

Response structure

Federal evaluators read in sections; organise to their structure and answer each evaluation factor explicitly rather than weaving answers into prose.

Use the required font, page limit and header, because a response that ignores the instructions is scored as non-responsive regardless of quality.

State limitations plainly, since an overstated claim becomes a performance issue after award.

Costs and pricing

Build the price from a cost model rather than from a competitor's guess, and keep the model after submission.

Separate labour categories clearly, because the evaluator compares them and a blended rate hides what they are buying.

Where a requirement drives cost, say so in the price narrative rather than inflating the rate.

After award

Read the contract before celebrating, because the flow-down obligations are the operating rules for the next year.

Set up invoicing, reporting and security requirements as calendar items with owners, not as intentions.

Report problems early and in writing, since the relationship survives a disclosed delay and does not survive an undisclosed one.

Small business programmes and set-asides

Many federal opportunities are set aside for specific categories, and eligibility depends on representations that must be true and current. The rules around affiliation and size change what counts, so the analysis is a genuine exercise rather than a checkbox, and an ineligible bid is a loss with an administrative consequence. Knowing which set-asides you qualify for narrows the market usefully and prevents wasted preparation on opportunities you cannot win.

Where you do not qualify now, the same analysis tells you what would change it, which is more actionable than a general intention to grow. Record the analysis and revisit it annually rather than reconstructing it for each bid, and keep the supporting documents with it so the claim is checkable.

Security and information handling

Work that touches federal systems or data brings handling requirements that are specific to the agency and the contract, and meeting them is a precondition rather than a differentiator. Read the clauses before pricing, because the cost of compliance is part of the bid and not an overhead you discover later. Where the requirement is beyond your current posture, the honest option is to decline or to team, not to discover it in a review after award.

For cloud services, the compliance path is documented and takes time; for smaller engagements, the equivalent is evidence of controls rather than a certification. Either way, the artefacts exist before they are requested, and the person who would produce them is named. That preparation is what makes a bid credible rather than optimistic.

Debriefs and the next bid

Ask for a debrief after every loss, and write down what was said while it is fresh. The scoring reveals what the evaluator valued, which is rarely what the proposal team assumed, and the information is the cheapest improvement available. Bids that never ask repeat the same mistake with more words.

Keep a bid library of approved narratives, past performance write-ups and pricing models, updated after each submission. The library is what makes the tenth bid faster than the first, and it is also what keeps the statements consistent when different people write different sections.

Teaming as a route in

Where a requirement is beyond your current posture, teaming with a prime that already meets it is a legitimate way to build past performance rather than something to apologise for. The value of the relationship is the flow-down clauses you must meet and the references you can cite afterwards, both of which need to be written down at the start. A teaming agreement that names the work and the payment terms protects the relationship when the schedule slips.

Choose the partner for the capability you lack rather than for the logo, and ask for the names of two customers who can be called. A short conversation with a reference resolves more risk than a longer conversation with a business development lead. The same questions, asked of yourself by a future partner, are a useful check on whether you are ready to be subcontracted to.

What a first bid should be

A first federal bid should be small, narrowly scoped and squarely inside work you have already done commercially, because the evaluator is buying evidence of performance rather than a promise of capability. A small award that is delivered well produces the past-performance reference that every later bid needs, and the reference is worth more than the margin on a larger attempt you are not yet positioned to win. Choose the opportunity for the reference it produces as much as for the work it contains.

The preparation before that bid is unglamorous: entity registration verified, capability statement written for the specific requirement, pricing built from a cost model, and a named person who owns the submission. Each takes a day, and together they convert a hope into a response that can be evaluated on its merits. The organisations that lose repeatedly usually lose before writing, because one of those four was left to the week of the deadline.

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 — federal agency integration, las vegas nv — 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