Salus
Local-first health operations for capture, summary, and appointment preparation.
Salus is a personal health chief-of-staff system operated by Alexander Ball. It is designed to capture, normalize, summarize, and prepare health information from user-provided records and authorized data sources, including Oura, so the user can review patterns and prepare for clinician conversations.
Salus is not a doctor. It does not diagnose, prescribe, change medications, or replace licensed medical care. It is a records, preparation, and escalation-support layer only.
Operating scope
What Salus is designed to do
Salus is meant to reduce operational sprawl around personal health information while keeping the authoritative record local and the public website limited to policy and disclosure pages.
Core function
Capture and normalize
Salus stores immutable source imports locally, normalizes them into stable flat-file records, and prepares derived summaries for personal review.
Core function
Prepare for appointments
Salus can assemble concise packets, weekly summaries, and question lists so the user can walk into appointments with organized context.
Core function
Watch for escalation cues
Salus can highlight unresolved items or red-flag patterns that should be escalated to a clinician or emergency service, but it does not make clinical decisions itself.
Hard boundaries
What Salus is not allowed to become
The system is intentionally constrained so that organization, summary, and escalation support do not collapse into diagnosis or treatment advice.
Boundary
No diagnosis
Salus does not diagnose medical conditions, interpret symptoms as a substitute for a clinician, or present itself as medical judgment.
Boundary
No treatment or medication changes
Salus does not recommend treatment plans, alter medication regimens, or provide dosing advice.
Boundary
Local-first handling
Raw imports and derived artifacts are intended to stay under the user's local control. Secrets and tokens are kept outside the public repository.
Boundary
Downstream summaries only
If a downstream channel such as Telegram is used, it is for concise summaries or reminders rather than raw health-record dumps.
Public policies
Policy pages for integrations and public review
These routes exist so external integrations such as Oura can review the privacy and operating limits of Salus without exposing the local health records themselves.