Patient-controlled health records AI
Savva
Savva offers local models and separately selected cloud-provider queries, with model and context choices. Shared API keys do not make record contents anonymous. Optional cloud processing and metadata retention qualify broader local-only and anonymity claims.
Checklist assessment dated October 30, 2026. Independent confirmation is incomplete. Hugo has not personally verified this service.
Agency checklist · October 30, 2026
Expands 10 of 12 yes
Document-based draft. Independent confirmation is incomplete. Hugo has not personally verified this service.
Assessed function: Local record app with on-device AI and separately selected cloud-provider queries. Shared API credentials do not make record contents anonymous.
Initial Anthropic coding has an Anthropic model in the role record. Astra review conflicted: OpenAI model in role record.
A no can mean missing documentation or institution-dependent control; it does not by itself establish harmful behavior. These categories are not clinical safety or product-quality ratings.
- Public documents do not establish actual product behavior.
See all twelve answers and their evidence
| Question | Answer | Evidence / review | Source and reasoning |
|---|---|---|---|
| 1. Told it is AI | Yes | documented Confirmed at document level | the app shows you what will be sent, names the provider, and asks you to agreeSource Privacy policy section 12: cloud AI is off until turned on, and a first-use consent screen names the provider. The home page also labels responses as AI-generated. |
| 2. Operator and model maker named | Yes | documented Confirmed at document level | The available providers are OpenAI, Anthropic, Google, xAI, Alibaba Cloud, Mistral AI, DeepSeek, and Moonshot AI.Source Operator is named as Vircode, Inc. (Savva) in the same policy. Cloud model makers are listed by company. On-device models named on the how-it-works page are Llama and Gemma. |
| 3. Patient chooses to use it | Yes | documented Confirmed at document level | Cloud AI is off until you turn it on.Source The user installs the app and opts in to each cloud provider. No clinician, insurer or employer applies it. |
| 4. Patient sets the task | Yes | documented Confirmed at document level | 12+ AI models on tap. Ask any of them anything.Source The patient types the question and chooses the model. The Pro tier also uses the chosen AI to structure imported records, which is a fixed operator-side step. |
| 5. Patient can decline or stop | Yes | documented Confirmed at document level | Cloud AI is off until you turn it on.Source Self-started tool rule: Q3 is yes and no care or service depends on it. The free tier works without AI. Source is the Q3 source. |
| 6. Patient sees the AI output | Yes | documented Confirmed at document level | AI-powered medical record summariesSource Listed Pro feature. AI chat answers are shown to the user in the app. Privacy policy says the generated answer is held encrypted for a few minutes so an interrupted reply can be completed. |
| 7. Patient can correct or challenge | No | not-documented Confirmed at document level | Quotation not recorded; evidence repair pending. No documented route to correct or contest an AI answer or summary. The privacy policy lists a generic right to correct inaccuracies, but Savva holds no health data to correct, and it is not tied to AI output. |
| 8. Patient can get a copy | Yes | documented Confirmed at document level | All charts, all goals, all exports.Source Free tier includes exports. Privacy policy fn 2 says the only copy is on the device in a portable format. |
| 9. Patient can delete | Yes | documented Confirmed at document level | You can request that we delete your personal data.Source Health data lives only on the phone, so the patient deletes it by removing the app. The policy says the cloud AI path keeps no questions, conversations or attachments, and the answer is deleted after a few minutes. Billing records are kept up to 10 years. |
| 10. Training or sale does not override patient choice | Yes | documented Confirmed at document level | we do not permit the providers to use it to train their modelsSource Policy section 12 also says Savva does not use the data for advertising, profiling or sale, and every provider has a DPA with a no-training prohibition. Contractual claim, not independently verified. |
| 11. Patient can run it or take it elsewhere | Yes | documented Confirmed at document level | Run models like Llama and Gemma entirely on-device with zero cloud exposureSource Local app. Records and on-device AI run on the phone and work offline. The app is proprietary, not open source, and cloud AI needs Savva's relay and API key. |
| 12. No advertising or data business | No | documented Corrected after independent review; accepted by editor | product news or offers from time to timeSource Optional promotional SMS offers count as advertising under the written rule, including with consent. |
Initial coding: Claude Sonnet helpers, compiled by Claude Opus 5.5 (Anthropic). Selective review and corrections: GPT-6 Astra (OpenAI). Editor: Hugo Campos. Acceptance of corrections is not product verification.
Checklist rules · Independent review and limitations · Later evidence follow-up
Earlier v1.3 assessment and control finding
Historical assessment under different rules. It does not set the current checklist zone.
Agency finding, before method v1.3
Potentially agency-expanding
Legacy editorial placement, pre-method: 78
This profile has not yet been reviewed under the published method. Its finding and any number are editorial placements made before the method existed.
- Evidence
- Documentary review. Public sources only, no hands-on testing by HugoScore.
- Review status
- AI draft. No person has settled the findings.
Earlier evidence and assessment
The sections below preserve the earlier review. Its classifications and provenance are historical; the checklist above gives the current draft classification.
Earlier finding · Legacy editorial placement, pre-method: 78
Method v1.3. The control line is evidence for how the agency finding arose, not a quality score. Legacy editorial placement, pre-method: 78. Not comparable with v1.3 positions.
Potentially agency-expanding
Savva offers local models and separately selected cloud-provider queries, with model and context choices. Shared API keys do not make record contents anonymous. Optional cloud processing and metadata retention qualify broader local-only and anonymity claims.
Patient agency
How this tool changes agency
Comparing interpretations can prompt useful questions when users can inspect original records. Agreement between models is not validation.
Actual local/cloud boundaries, export, derived-data correction and provider retention remain unverified
Patient agency assessment
Who sets and changes the goal?
Choice of models, local execution and context size give users meaningful control over analysis. Switching models does not itself establish a way to correct extracted records or resolve conflicting advice.
What can the patient understand, question, or do?
Comparing interpretations can prompt useful questions when users can inspect original records. Agreement between models is not validation.
Can the patient evaluate the conditions of use?
An API key identifies the application, not necessarily the patient, but health-record content may identify them. Provider choice must include that distinction and policy retention exceptions.
Text findings
Conditions of use
Published controls and their limits
An API key identifies the application, not necessarily the patient, but health-record content may identify them. Provider choice must include that distinction and policy retention exceptions.
What remains unknown?
Not tested or not established
Actual local/cloud boundaries, export, derived-data correction and provider retention remain unverified
Who evaluated this?
AI-assisted public-source draft
Vendor statements describe published conditions, not independently verified behavior. No clinical, security, accessibility, or legal validation is claimed. Earlier evidence remains dated in the report and history.
Sources checked
Source-specific findings and retrieval limitations are recorded in the full report.
Earlier review provenance
Criteria
CAIHL-derived HugoScore framework and September 7 qualitative review priorities. Draft v1.2 numerical anchors remain unadopted.
Reviewer
AI-assisted public-source reassessment prepared in OpenAI Codex.
AI / model
OpenAI Codex / GPT-6
Human review
Hugo Campos authorized publication of these AI-assisted draft reassessments on September 8, 2026. This does not claim comprehensive human verification of every finding.
Review date
2026-09-08
Limitations
Actual local/cloud boundaries, export, derived-data correction and provider retention remain unverified No live product use, patient-data upload, account creation, code audit, clinical evaluation, or independent implementation validation.
Earlier review method
Focused public-source reassessment using CAIHL: patient authority, critical capacity, and informed control. Existing evidence plus one focused primary-source pass and at most one targeted follow-up. No live product testing. Numerical scores remain provisional editorial placements, not a new calculation.
Document-based draft · Moderate for current documented choices, limited for runtime behavior (AI-assisted draft)