A Loss Formula for Estimating the Cost of a PHI Leak Through an LLM Prompt
Estimate PHI leak LLM prompt cost as an expected loss: the annual frequency of leak events multiplied by the sum of six cost components (detection and containment, notification, regulatory, legal, provider remediation, and operational disruption). Each component depends on record count, detection time, provider retention, or severity. Runtime controls reduce the terms they act on, so you can compare their value to their cost.
The formula
The estimate treats a PHI leak through an LLM prompt as an expected loss. Multiply the annual frequency of leak events by the combined cost of a single event, built from six components.
Frequency × (Detection and containment + Notification + Regulatory + Legal + Provider remediation + Operational disruption)
Keeping the cost of a single event separate from how often events occur lets you change one input at a time and see how the total responds.
What each variable needs
The six cost components are:
- Detection and containment
- Notification
- Regulatory
- Legal
- Provider remediation
- Operational disruption
Each component depends on one or more of four inputs: record count, detection time, provider retention, or severity. Define each variable and state your assumptions before you calculate, so the result can be reviewed and reproduced.
Mapping variables to control points in the request path
Runtime controls reduce the terms they act on. To compare a control's value to its cost, identify which variable it affects and where in the request path it operates.
Loss formula variables and where they are controlled
| Variable | Description |
|---|---|
| Frequency | How often PHI-bearing prompts, context, or tool calls reach a model path |
| Record count | How many individuals' records a single event can expose |
| Detection time | How long exposed data stays unnoticed and uncontained |
| Severity | Contract status, retention behavior, and data sensitivity |
Worked example with explicit assumptions
A worked example applies the formula end to end. Each assumption is stated explicitly, so you can replace it with a value from your own environment and see how the expected loss changes.
Sourcing inputs and handling HIPAA uncertainty
Define each variable, state where its value comes from, and record any assumption you cannot confirm. Where HIPAA uncertainty affects an input, state it as an assumption in the model rather than leaving it implicit.
Using the output to evaluate control investment
Because runtime controls reduce the terms they act on, you can recalculate the expected loss with a control in place and compare the reduction to the control's cost.
Apply the formula to your own data paths
Talk with our team about mapping runtime controls to the variables in your PHI leak loss model.
Talk to an Expert