# Health Risk Thresholds

JARVIS must not invent personal medical thresholds.

## Policy

- Thresholds are configurable.
- Personal thresholds must be confirmed by the user and/or physician.
- Defaults are conservative demo categories or `unknown`.
- JARVIS shows traffic-light status and safe action category, not a diagnosis.
- Exact lab values stay in HealthManager / protected Health dashboard.

## Example Rule Families

### CRP / inflammation

- `green`: within personal baseline.
- `yellow`: above baseline, rising, or stale trend.
- `red`: high plus symptoms, or physician-defined red threshold.

### Eye risk

- `red`: sudden blurred vision, sudden vision loss, painful red eye, or new severe floaters.
- `yellow`: unclear status or overdue eye check.
- `green`: no warning signs plus current check.

### Thrombosis / vascular risk

- `red`: suspected DVT/CVT/PE emergency symptoms such as unilateral leg swelling with pain/warmth, chest pain, shortness of breath, hemoptysis, severe new headache, or neurological symptoms.
- `yellow`: new mild vascular signs requiring review.
- `green`: stable with no warning signs.

### Medication safety

- `red`: bleeding signs while on Eliquis/Apixaban, or severe infection symptoms while immunosuppressed.
- `yellow`: possible side effects or intolerance signals.
- `green`: no warning signs.

## Implementation Notes

The Phase 8E adapter uses synthetic safe flags only. A later HealthManager producer may provide a safe summary API/marker with precomputed categories after explicit approval. That producer must not expose reports, OCR text, raw symptoms, raw labs, filenames, paths, Drive IDs, or PDFs to JARVIS.