SECURITY
Charles Trinh — Breach Notification and Response | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

When ePHI is exposed the clock starts before anyone is sure it is a breach. I set up the HIPAA Breach Notification Rule determination, the notification calendar and the response playbook that keeps an organisation inside its windows.
The determination has to be documented
Under the HIPAA Breach Notification Rule, any impermissible acquisition, access, use or disclosure of unsecured ePHI is presumed a breach unless the organisation demonstrates a low probability that the information has been compromised. That demonstration rests on a four-factor assessment, and the assessment is a record the organisation will defend to OCR. A verbal conclusion that nothing bad happened is not a record and will not survive the first request.
The four factors are the nature and extent of the data, the identity of the recipient, whether the data was actually acquired or viewed and the extent to which the risk has been mitigated. Each factor is documented with facts rather than adjectives. Treating a lost unencrypted laptop as an exception without working through them is the most common way to fail. I help complete the worksheet before an incident so the answer is fast and consistent when one arrives.
The rule sets a 60-day outer limit for notification to affected individuals, and under the breach presumption the clock starts at discovery. A determination that drags past that limit without notification is a finding regardless of how sound the reasoning was. I build the worksheet so a determination can be completed inside a day or two for most incidents, leaving room for investigation and notice production instead of for deliberation.
The 60-day clock, and the four parties it touches
Discovery is not limited to when a technician notices. Under the rule, a breach is discovered when it is known, or would have been known by exercising reasonable diligence. An incident sitting on a firewall log nobody reviews does not stay hidden; it is simply missed. I ask for discovery triggers to be defined in the playbook so everyone uses the same starting line and the clock cannot quietly reset when a new person joins the investigation.
Individuals are notified first. Then, for a breach affecting more than 500 residents of one state or jurisdiction, the media in that jurisdiction are notified without unreasonable delay. OCR is notified through its portal within the same 60 days for breaches of 500 or more individuals, using a form that asks for the facts, the scope and the steps taken. Smaller breaches are reported to OCR annually in the March filing.
When the breach comes from a business associate, the associate notifies the covered entity without unreasonable delay and no later than 60 days after its own discovery, and the covered entity then runs its own clock. A contract that says the vendor will notify promptly without a specified deadline is an opening for dispute. I write the deadline into the BAA and check the notification channel reaches a monitored address with an out-of-hours answer.
Content of the notice that passes muster
The individual notice describes what happened and when, the types of unsecured ePHI involved, the steps affected people should take, what the organisation is doing and a contact for questions. Generic language that omits the data classes or the contact routes generates complaints and invites scrutiny of the whole programme. I write the template so the classes and the steps are specific enough that a recipient can decide what to do next, which is also what keeps call-centre volume manageable.
I build the template with placeholders filled at the time of the incident, reviewed by counsel and signed off before any mail room touches envelopes. I keep a state-notice annex for jurisdictions with their own content requirements, because a single national letter will not satisfy every one. California, Texas, New York and Florida are the usual places where the letter format differs materially, and the annex lists each requirement against the date it changed.
A notice must not overstate what is known. Saying the data was not used when the investigation is open is a false statement that survives long after the incident and makes every later statement suspect. I ask for the sentences about uncertainty to be reviewed word by word with counsel, because the temptation under pressure is always to soften the language, and the consequence of doing so is a credibility problem that outlasts the breach itself.
The response playbook, tested on a calendar
I write the playbook as a sequence with owners and times: who declares an incident, who decides the determination, who drafts the notices, who contacts counsel, who manages the call centre and who signs the final determination. Each step names a person and a backup, and a single number the whole chain dials. A playbook that names a role but not a person fails on the first weekend, and people do not call a role from a hospital car park.
The playbook covers the technical side too: evidence preservation before remediation, a forensic scope decision, the encryption status of affected media and the communication plan for staff answering patient questions. The most common delay in real incidents is not technical; it is a founder or operations lead unsure who has authority to send notices. I establish that authority in advance and write it down with the backup named in the same sentence.
I test the playbook in a tabletop exercise with a plausible incident and run the determination worksheet for a fictional breach to see how long it takes. A timeline that looks fine in plan is usually twice as long under stress, and the exercise exposes exactly where. That measurement is what converts the plan from a document into something the organisation can execute at any hour of the week.
State laws, exceptions and their limits
The HIPAA Breach Notification Rule is a floor, and many state laws impose additional deadlines, formats or thresholds. Some require law-enforcement notification, some require a specific notice to the attorney general and some require credit monitoring in defined circumstances. I review the organisation's operating states and document which jurisdictions add obligations and how each one is triggered. That review tends to uncover states where the organisation has patients but has never registered a notice.
The rule has a limited set of exceptions: encrypted data that is rendered unintelligible, a recipient whose access is limited by law enforcement or another process, and unintentional access by an internal employee within the scope of their authority. Each exception has to be applied carefully and documented with the same rigour as the breach determination, because an exception invoked broadly can itself become a finding when the facts later change in an examination.
The healthcare-specific risk sits at the edges. A misdirected fax, a lost backup tape, an exposed spreadsheet and a stolen laptop look different but each triggers the same analysis. I write the playbook to route by the data rather than by the technology, so a new failure mode is handled by the same process rather than arriving as a surprise with no owner and no path through the determination worksheet.
Learning without letting the file drift
After notification, the organisation has follow-on obligations: log the breach, update the risk analysis, retrain staff on the control that failed and prove the control now works. I build a closure checklist and keep one register of incidents, determinations and remediation so a recurring pattern becomes visible. Closure is not the notice mailing; closure is evidence the contributing cause no longer operates on the affected systems.
The register doubles as risk intelligence. Three lost devices in a year with unencrypted disks say something different from one misdirected fax. I report the pattern to leadership rather than reporting events individually, and I turn the pattern into a single programme change, such as device encryption, rather than a series of small corrections that never address the underlying cause and never reduce the number of incidents the organisation reports.
The closure also reviews the respondent experience. Did the organisation discover the incident through its own monitoring or because a patient complained? Did the vendor notify on time? Did counsel feel the facts arrived in time to advise? Those answers are the best evidence of whether the playbook in force is the playbook that operates, and they justify the next version of the plan to whoever holds the budget.
Procurement and contract language for breach terms
The speed of a breach response depends on terms agreed before the relationship exists. I write the vendor contract language that governs notification: a fixed window measured from the vendor's discovery, a named security contact with an out-of-hours route, a requirement to preserve evidence for the investigation and an obligation to cooperate with forensics and regulatory inquiries. A vendor that only promises prompt notice has given the organisation nothing it can enforce.
The BAA clauses that matter here concern the content of the notice, not just its delivery. I ask for the data classes affected, the time window of exposure and the mechanism of the incident. A vendor that reports a breach as an event at another of its customers, without saying whether the organisation's data was in scope, has not reported a breach in any useful way. The contract should make the content specific.
I also address the cost question in the contract: who pays for notification, credit monitoring and forensics. The answers are not always favourable to the organisation, and a vendor with a small balance sheet may be unable to cover the consequences of an incident. The contract exposes that risk before the incident instead of after, which lets the organisation decide whether to accept it or change vendor while it still can.
The evidence pack a regulator asks for
When OCR or a state regulator opens an inquiry after a notification, the first request is the risk determination. I assemble the four-factor worksheet, the facts supporting each factor, the decision and the date. That pack must show a reasoned decision, not a conclusion dressed with facts gathered after the decision was made. Examiners can tell the difference, and the timeline is the clearest signal they use when they look at a file.
The next request is the notification record: the letter sent, the date sent, the list of recipients and the method of notification. I keep those in one folder per incident, with a reconciliation between the number of affected individuals and the number of notices. A discrepancy between those two numbers is one of the most common follow-up questions, and I close it at the time of notification rather than after the inquiry begins.
The final request is the remediation record: the control that failed, the fix that was applied and the evidence the fix operates. A regulator wants to know the organisation learned, and the remediation record is the only proof. I keep it with the incident file from the beginning, so the file tells the whole story when it is opened months later and the person explaining it is not the one who ran the incident.
How the response links to everything else
Breach handling does not stand alone. It feeds the security risk analysis with new entries and with evidence that existing controls did or did not work. It informs vendor terms through vendor risk management, especially the notification window. It depends on access logs and audit trails that a hardened estate provides. Where those are missing, the determination cannot be completed quickly and the clock becomes the enemy.
The deliverable is a determination worksheet, a playbook with owners and a tested dry run, ready before the phone rings. I hand over an amendment log so each exercise produces changes to the plan, plus a calendar for the next exercise. The organisation should be able to show an investigator both the playbook and the most recent exercise record on top of it, which is what turns the document into an operating control rather than an aspiration.
Typical engagement length is three to five weeks: a week on the worksheet and playbook, a dry run, then a fortnight of amendments and training. The work is small compared with the cost of a slow response. A delayed notice triggers regulatory attention and legal exposure that dwarf the engagement effort, and that asymmetry is why I prefer to build the process before the incident rather than during it.
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 — breach notification and response — 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
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
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.