business associates · agreements · exit

Charles Trinh — Business Associate Agreement Review, Las Vegas NV

A service card reading Business Associate Agreement Review — Charles Trinh, technology architect in Las Vegas
Charles Trinh — Business Associate Agreement Review

Reading the agreements that actually govern your PHI: scope, notification windows, subprocessor chains, and the exit terms nobody negotiates until it is too late.

What the agreement controls

The BAA sets scope, permitted uses, safeguards, breach notification timing and downstream obligations.

Most reviews stop at the signature page and never test whether the operational reality matches the text.

The useful review compares the agreement against what the vendor actually does with your data.

Notification windows

Contractual notification windows are frequently shorter than the vendor's internal detection capability.

Ask how they would know, not how fast they would tell you, because the second answer depends on the first.

Record the window and the detection mechanism side by side in the vendor register.

Subprocessor chains

The vendor's subprocessors are your risk paths; a list that is undated is not a control.

Request the list annually and compare it to the previous one, because undisclosed additions are the norm.

Where the vendor resists, that resistance is itself information about the relationship.

Scope drift

A vendor's service catalogue changes faster than its agreements; new modules may fall outside the existing terms.

Review scope at renewal and after any material product change.

A vendor holding PHI under an agreement that does not cover the current service is a finding waiting for an incident.

Security obligations that mean something

Encryption, access control and incident cooperation are only meaningful with specificity.

Vague commitments are unenforceable in practice, because there is nothing to test against.

Push for named standards where the vendor will accept them.

Exit and data return

Terms covering return or destruction of data at termination are often absent or aspirational.

Ask for the format, the timeline and the confirmation mechanism before you need them.

A vendor who cannot describe the exit has not designed one.

The register

One line per vendor: what data, which agreement, expiry, notification window, subprocessor list date, exit terms.

The register is the artefact that answers the question after an incident.

Review it quarterly and treat missing fields as open findings.

What I do

I read the agreements against the operational reality and produce the register with the gaps marked.

I do not provide legal advice; where the question is legal I say so and stop.

The deliverable is a table and a short list of changes worth negotiating.

Negotiation leverage

You have more leverage at renewal and before a migration than at any other moment.

Time the requests accordingly rather than raising them during an incident.

A short list asked early gets a better answer than a long list asked under pressure.

Where to start

Pull every agreement covering PHI and check three fields: expiry, notification window and subprocessor list date.

Any blank field is the first conversation, and it takes an afternoon.

The rest of the review is detail on a structure you will already have.

How I do it

Indemnity and insurance clauses

The indemnity clause decides who funds the response, and it is frequently narrower than the breach it is meant to cover.

Read it against the notification obligations, because a thirty-day notice combined with a sixty-day indemnity deadline is a trap.

Ask for the certificate of insurance and check that cyber coverage exists, since general liability does not respond to a data event.

Audit rights that never get used

A right to audit that has never been exercised is a clause, not a control, and the vendor knows which of the two it is.

Exercise it once, minimally, and record what the exercise produced; the first request is usually the one that reveals the difference.

Where a right is limited to a report, ask for the report annually and record the exceptions section rather than the conclusion.

Termination assistance

The moment you need the termination terms is the moment you have no leverage to negotiate them.

Ask for the format, the timeline, the cost and the confirmation mechanism, and get the answer in writing before renewal.

A vendor who cannot describe the exit has not designed one, and that absence belongs in the risk register with a date.

The register is the artefact

One row per vendor with six fields answers most questions an examiner will ask about the supply chain.

Populate it from the agreements rather than from memory, and date each field when it was checked.

Review the register quarterly and mark every blank as an open item rather than leaving it empty.

Renewal as the negotiating moment

Renewal is when a vendor will discuss terms, and the request should arrive thirty days early rather than on the final week.

Bring a short list of three changes rather than twelve, because a short list gets answered and a long list gets deferred.

Record what was asked and what was granted, so the next renewal starts from an accurate position.

What to do with a refusal

A vendor refusing a reasonable term is information about concentration risk rather than a negotiation failure.

Record the refusal, the reason and the compensating step you will take internally.

If the compensating step is impossible, that is the moment to begin the exit plan rather than to accept and forget.

Mapping agreements to services

A vendor with several products may hold PHI under one agreement and not another, and the mapping is rarely written down.

List each service you use from that vendor and the agreement that covers it, then look for the service with no line.

The unmapped service is the finding, and it usually arrived through a procurement nobody routed to compliance.

Reviewing what the vendor changed

Vendors update their standard terms quietly, and the update may be incorporated by reference without your signature.

Ask each year for the terms in force, and diff them against the version you have on file.

Where the diff changes scope or notification, treat it as a new agreement and review it as one.

Turning the review into a schedule

A review that produces a document has produced understanding; a review that produces a schedule has produced a control. The difference is whether each finding leaves the table with a name and a date, or with a paragraph explaining why it is difficult. In practice most findings are small, and the reason they survive is not complexity but the absence of anybody whose calendar contains the fix. Naming a person and a month converts the review into three or four items that either happen or visibly do not.

The schedule should be reviewed at the same meeting as the vendor register, because they answer the same question from two directions. The register says what the relationship is; the schedule says what is changing about it. When the two disagree, the disagreement is usually an agreement that has moved ahead of the operational reality, which is exactly the condition that produces the surprise during an incident. Aligning them costs a single meeting a quarter.

The last element is evidence of the change. When a notification window is renegotiated or a subprocessor list is updated, the new document replaces the old one in the register with a date and the previous version is retained. That archive is what lets the organisation answer a question about last year's arrangement without relying on memory, and it is the difference between a register that is a list and one that is a record of a relationship over time.

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 — business associate agreement review, las vegas nv — 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

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