risk analysis · 45 cfr 164.308 · evidence

Charles Trinh — HIPAA Security Risk Analysis

Charles Trinh — HIPAA Security Risk Analysis
Charles Trinh — HIPAA Security Risk Analysis

What the rule asks

Accurate, thorough, potential and held. The analysis has to survive being read by someone who was not in the room, and most documents fail on the last word.

Most analyses restate the rule and conclude controls exist, with no threat, no score, no owner and no date.

What a real one contains

Scope, data-flow mapping drawn from the infrastructure rather than the diagram, threats named against components, likelihood by precondition count, and impact by regulatory consequence.

Control mapping with artefacts rather than assertions, owners who can be asked, and dates that can be missed.

The worked precedent

One scenario traced from detection through containment, notification decision and closure. A misdirected outbound payload is the best choice: common, not obviously a breach, and exactly where organisations stall.

The authority question usually breaks first, because organisations answer every technical question and still have nobody empowered to stop the workflow.

What I do

I wrote the risk analysis for the platform I built and operate, under a signed AWS business associate agreement, while owning the systems it covers.

I do not sell a template, and I will not sign a document I did not write.

What an examiner actually reads

The risk analysis is not read as prose; it is read as a set of claims that can be checked against the estate. For each claim the reader asks whether the system named exists, whether the threat is plausible for that component, whether the control operates and whether anyone owns the gap. A document that answers those four questions is short and intimidating; a document that restates the rule is long and reassuring and answers none of them.

That difference is why the accurate and thorough standard is worth taking literally. The analysis has to describe the systems that are running rather than the systems that were designed, and the only reliable way to know which is which is to look at the infrastructure rather than at the diagram from the last acquisition.

The entries that carry weight

Twelve specific threats beat a hundred generic ones. A shared clinician login used by four people. An unauthenticated webhook that writes to the patient record. A backup bucket without a documented owner. A support engineer with standing production credentials and no session recording. Each is a sentence somebody can act on, and each is invisible in a document that speaks in categories rather than components.

Score those by precondition count rather than by how nervous the room feels. A threat that needs three independent failures is genuinely rarer than one that needs a misconfiguration, and the difference matters when the remediation budget is finite. Impact is scored by regulatory consequence and record count, because that is what drives notification and what an examiner will ask about.

Control mapping as evidence

For each control, name how you know it operates: the configuration export with a timestamp, the review with recorded decisions, the log query that answered a specific question, the exception that was handled and closed. MFA is enforced is an assertion; MFA enforced for all forty-one accounts, verified by an export dated the third, is evidence. The gap between those two sentences is the whole of the compliance problem in most estates.

Where a control operates inconsistently, say so and date the fix. An honest partial control is stronger than an unevidenced claim, because the first survives sampling and the second invites it. The instinct to describe the intended state rather than the observed one is what turns a risk analysis into a liability.

The worked precedent

A completed analysis should be accompanied by one scenario traced end to end: detection, declaration, containment, the four-factor assessment, the notification decision and closure. The best choice is usually a misdirected outbound payload, because it is common, it is not obviously a breach, and it is precisely where organisations stall. Writing it forces every question the plan does not answer into view.

What the trace usually reveals is that authority breaks before technology does. Organisations answer every technical question about containment and still have nobody empowered to stop the clinical workflow mid-shift, which means the decision that mattered was never made. Naming that person in advance is the cheapest remediation a risk analysis can recommend.

What I do differently

I wrote the risk analysis for the platform I built and operate, while owning the systems it covers and under a signed business associate agreement. That is the opposite of the usual arrangement, in which an analyst with no operational stake produces a document that describes somebody else's estate, and the difference shows in the specificity of every entry.

I do not sell a template and I will not sign a document I did not write or test. Where the answer is that the estate is not ready for a defensible analysis, the deliverable is the gap list and the sequence to close it, which is more useful than a document that will not survive its first reading.

Where the analysis goes after it is written

A risk analysis that is written once and filed is a document about a year that has ended. The useful version is reviewed on change rather than on a calendar, because the estate changes when it ships and the analysis is either current or decorative. Record each review with its date and what changed, so the next reader can see the estate's history rather than a snapshot.

Assign every open item to a person and a date, and review the list monthly with the same attention the incident register gets. The slippage is the information: an item that has moved three times is a decision that the organisation does not intend to fund, and saying so is more useful than moving it a fourth time.

Small estates, same standard

A five-person organisation is held to the same standard as a hospital, and the analysis that satisfies it is smaller but not shallower. The difference is that the component list is short enough to enumerate completely, which makes a genuinely thorough analysis achievable in weeks rather than quarters. The failure mode is not the size of the estate; it is the assumption that a small estate can rely on the same restatement of the rule that a large one cannot.

Where a component is outsourced, the analysis covers the agreement and the evidence of what the vendor does, not a disclaimer. Outsourcing moves the operation and leaves the obligation, and an analysis that treats the vendor as a boundary rather than a risk path has excluded the thing it was written to examine.

Keep the superseded version of each analysis. The comparison between two years of analysis is where an examiner sees whether the programme operates or merely restates, and the superseded document is the only evidence of the first.

Review the analysis after every incident, because the incident is the only evidence that the threat list missed something, and the review is where that evidence is folded back in rather than filed separately.

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 — hipaa security risk analysis — 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