incident response · notification · precedent
Charles Trinh — Incident Response Authoring, Las Vegas NV

Writing the plan that survives 2 a.m.: detection, declaration authority, containment, the four-factor assessment, notification and closure, with one worked precedent.
A procedure is a hypothesis until exercised
An unexercised plan describes intent; a written precedent describes capability.
The gap between the two is discovered during the first real incident.
Write the plan, then trace one scenario and rewrite what the trace disproves.
Detection and declaration
Who notices, through which channel, and who has authority to declare at two in the morning.
Authority is usually the first thing that breaks, not the technical response.
Name a primary and a deputy, and make the deputy reachable without escalation.
Containment without breaking care
The containment action frequently requires stopping a clinical workflow mid-shift.
Decide in advance who can authorise that and what the clinical fallback is.
Organisations answer every technical question and still have nobody empowered to stop the workflow.
The four-factor assessment
Document the risk assessment contemporaneously, including the factors considered and who concluded.
Reconstructing it weeks later produces a document that looks like an afterthought because it is.
Keep the template ready with the decision points pre-written.
Notification decisions
Who drafts, who signs, who is told first, and the state-by-state variation that applies.
Prepare the timeline and the media threshold logic before the event.
The clock starts at discovery, not at certainty.
Closure and review
Define a closure criterion and a review that produces an artefact rather than a meeting.
The review is the control; without it the same failure recurs with a different trigger.
Assign each corrective action an owner and a date.
The worked precedent
Trace one scenario end to end: a misdirected outbound payload is the best choice for most organisations.
Write what happened at each step, including the parts that were improvised.
The improvised parts are your real procedure.
Roles beyond technology
Legal, communications, clinical leadership and the executive sponsor each have a decision to make.
Write their decisions down with names, not titles.
An incident plan missing those four roles is a technical runbook.
What I write
The plan, the assessment template, the notification decision tree and one worked precedent.
I do not write generic templates; the plan references your systems and your people.
The deliverable is a document that a stranger can execute from.
Testing cadence
One tabletop per quarter with a written output, and one live exercise per year.
Tabletops without written output are meetings; live exercises without a rollback plan are incidents.
Review the plan after each and version it.
How I do it
- One trace of a real case, 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.
The first hour
The first hour decides the record, and the record decides everything that follows, because the assessment clock starts at discovery.
Write the first-hour checklist as five verbs: detect, log, declare, contain, notify the four named roles.
Anything requiring a judgement not covered by the checklist should escalate rather than improvise, and the plan should say so.
Communications before facts
A statement that precedes the facts is a second incident, and the plan should constrain who may speak rather than encourage responsiveness.
Prepare an initial holding statement and the list of people who must approve it, and test the approval path in the tabletop.
Clinical leadership speaks to clinical impact; legal speaks to obligation; one person speaks for the organisation.
Post-incident changes that stick
The review produces a list, and the list decays unless each item carries an owner and a date that somebody checks.
Review the list at the next tabletop, and report the completion rate rather than the count of actions.
The control is the follow-through, because an incident reviewed and not fixed will recur with a different trigger.
Detection sources and their blind spots
Every detection source has a blind spot, and the plan should name them so the first hour is not spent assuming coverage.
List the sources, what each would miss and how a miss would eventually surface.
The most common blind spot is a workflow that fails silently and is noticed by a patient rather than by monitoring.
The decision log
An incident produces decisions faster than it produces documents, and the log is what makes the timeline reconstructable.
Log the time, the decider, the decision and the reason, in one place, as it happens.
Reconstructing the log afterwards produces a narrative that is true in outline and wrong in detail.
Exercising the plan without breaking production
A tabletop exercises decisions; a live exercise exercises recovery, and the two should not be confused.
Run tabletops quarterly and one recovery exercise annually against a non-production copy.
Every exercise ends with a written result and a change to the plan, or it produced nothing.
The evidence you will need and will not have
After containment the organisation needs the access logs, the affected records and the timeline, and the third is usually the one missing.
Turn on the retention that covers the investigation window before the incident, because it cannot be recovered afterwards.
The plan should name which logs answer which question, so the first hour is spent collecting rather than deciding what to collect.
Tabletop design that finds something
A tabletop that follows the plan produces agreement; one that departs from it produces findings.
Inject a scenario the plan does not cover, such as a breach caused by a vendor, and watch where the roles break.
Record the departure points, because they are the plan's real gaps and they are cheap to fix on paper.
What the plan must contain to be executable
An executable plan has four properties. It names people rather than roles, because a role can be vacant at two in the morning. It states decisions in the form of a condition and an action rather than a discussion. It names the systems it refers to by the names the team uses, not the names in the asset register. And it fits on a page at the point of use, with the detail behind it, because a document that requires reading during an incident is a document that will be skimmed badly.
The conditions and actions are the part most plans lack. Declare an incident when the following is true is a sentence that removes an argument; contain by taking this action is a sentence that removes a delay. Where a decision genuinely requires judgement, the plan should say who makes it and how to reach them rather than leaving the decision to whoever is present. That single change converts a plan from a description into a procedure, and it is usually the difference found in the first tabletop.
The last property is maintenance. A plan that is not exercised becomes inaccurate within two releases, because systems are renamed, teams reorganise and the person named as the deputy leaves. The quarterly tabletop is not a training exercise, it is the maintenance mechanism, and its output is the corrected plan rather than the confidence of the participants. Organisations that treat it as training keep a plan that reads well and fails at the first real use, which is the failure mode the whole document was written to prevent.
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 — incident response authoring, 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
- 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.