AWS BAA REVIEW
AWS BAA Scope Review, Las Vegas NV

What the AWS business associate agreement actually covers, where a workload drifts outside it, and how to evidence the boundary before an examiner asks.
What the BAA covers
The agreement covers eligible services used in eligible ways; the second condition is the one that quietly fails.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Drift outside scope
A new managed service adopted for convenience can place PHI in a context the agreement does not describe, and nobody notices because nothing broke.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Service-by-service evidence
The defensible position is a table of services, each with its eligibility reference and the date it was checked.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Subprocessor chains
Anything the workload depends on that itself depends on another processor extends the chain your analysis has to name.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Region and residency
Where the data rests is a business decision and a contractual one; both need to agree rather than one being assumed from the other.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Exit and portability
A BAA you cannot exit is a dependency priced by the counterparty after you commit.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Review cadence
Scope review is not a one-time exercise; it follows every architecture change and every new service adoption.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
What an examiner asks
They ask which services hold PHI and how you know; the answer is the table, not the diagram.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Eligible means two things
The AWS business associate agreement covers eligible services used in eligible ways. The first condition is documented and searchable; the second is the one that quietly fails, because "used in an eligible way" depends on how the workload is assembled rather than on which service was chosen.
A managed service adopted for convenience can place PHI in a context the agreement does not describe — a shared queue, an analytics surface, a support channel — and nobody notices because nothing broke.
The defensible position is a table: service, eligibility reference, date checked, and the person who checked it. That table is the artefact an examiner reads, and it takes a day to build the first time.
The chain your analysis has to name
Anything the workload depends on that itself depends on another processor extends the chain. Subprocessors, region choices and support access all belong in the picture, and the subprocessor list is the gap most organisations discover last.
Region and residency are a business decision and a contractual one; both must agree rather than one being assumed from the other. An architecture that stores in a region the contract does not name is a finding regardless of whether the customer cared.
And review the scope on change, not on a calendar. Every new service adoption is a scope question, and the review that follows the architecture is the one that catches drift while it is still reversible.
The review is a recurring calendar item
Scope review follows every architecture change and every new service adoption, which in practice means it is reviewed on change rather than annually. An annual review of a system that ships monthly is a review of a system that no longer exists.
Keep the table current enough to answer the examiner's question without an investigation: which services hold PHI, how you know, and when it was checked. That is a twenty-minute answer when the table exists and a two-week project when it does not.
And when a service turns out to be outside the agreement, say so in writing with the remediation date. A documented gap with a date is defensible; an undeclared one is the finding itself.
What to hand the examiner
A one-page scope statement, the service-by-service table with dates, the subprocessor list with the review date, and a written note on any service outside the agreement with its remediation date. Four pages, and each one answers a question that otherwise becomes a follow-up.
Keep the dates honest. A table where every row was "checked" on the same day is a table that was produced for the meeting rather than maintained, and the examiner will notice.
Review the exit path at the same time. A BAA you cannot leave is a dependency whose price is set after you commit, and the question belongs in the review rather than in the post-mortem.
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. Las Vegas, Nevada 89101.
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 aws baa scope 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
Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.
Talk to Charles
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.