Coverage appeal AI
Fight Health Insurance
Fight Health Insurance encourages patients to revise appeal drafts and check citations. Its AI page and terms give conflicting training descriptions. Useful AI disclosures support scrutiny, but the current privacy policy could not be retrieved.
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: Fight Health Insurance hosted site: AI-drafted insurance appeal letters for patients (open-source code)
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.
- Unverified questions: 11. Current answers contribute to provisional arithmetic only.
- Public statements and terms conflict on training.
- October 30 follow-up: Q11 has public installation and backend documentation. Independent confirmation and runtime behavior remain unverified. Azure OpenAI is a documented backend option; actual production routing was not observed.
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 | Fight Health Insurance uses AI to help you draft health insurance appeal letters.Source Also ToS: outputs 'created by using machine learning technologies'. |
| 2. Operator and model maker named | Yes | documented Confirmed at document level | we use fine-tuned medical language models (like MedGemma)Source Operator Fight Health Insurance, Inc. is named in ToS and privacy. MedGemma links to Google's ai.google.dev page, but the text does not say 'Google'. Privacy names Anthropic, Microsoft Azure, DeepInfra, Perplexity and TypeSafe as AI providers users may direct data to. Reviewer should confirm this meets 'maker named'. |
| 3. Patient chooses to use it | Yes | documented Confirmed at document level | Upload denial letterSource Homepage 'How It Works' starts with the patient uploading a denial letter. Patient initiates; no care depends on it. |
| 4. Patient sets the task | Yes | documented Confirmed at document level | Our AI is a tool to assist youSource Patient supplies the denial and decides what to send. Donations are optional ('$0 I need this free'). |
| 5. Patient can decline or stop | Yes | documented Confirmed at document level | Upload denial letterSource Self-started rule applied (cites question 3 source). About AI: 'You should always review and customize any generated appeal before submitting it.' |
| 6. Patient sees the AI output | Yes | documented Confirmed at document level | You should always review and customize any generated appeal before submitting it.Source Patient sees the draft. |
| 7. Patient can correct or challenge | Yes | documented Confirmed at document level | You should always review and customize any generated appeal before submitting it.Source Patient edits the draft; page also tells users to verify citations and add personal details. Privacy also lists a correction right. |
| 8. Patient can get a copy | Yes | documented Confirmed at document level | The right to request access to and obtain a copy of any Personal Information we may have about youSource Request route in privacy policy. Patient also holds the generated letter. Code is open source. |
| 9. Patient can delete | Yes | documented Confirmed at document level | You can also request deletion of your data at any time.Source Also /remove_data request page referenced in the ToS. |
| 10. Training or sale does not override patient choice | No | documented Confirmed at document level | We also use the information you submit through the Services to train large language models that are used in providing the Services.Source ToS section on outputs says user input is used for training. About AI says 'No real patient appeal letters are used in training', which conflicts. Answered by the binding ToS. No training opt-out documented (privacy opt-outs cover advertising and sale/sharing). |
| 11. Patient can run it or take it elsewhere | Yes | documented Document follow-up supported; conflicted; independent confirmation incomplete | The majority of this code is released under an Apache 2.0 license.Source Generating an appeal needs a model backendSource Self-hosted model.Source The public distribution documents local installation and the model backend required to generate appeals, with both hosted and self-hosted backend options. Retain yes at document level. No installation, appeal generation or production-parity test was performed. The backend documentation also names an Azure OpenAI option; that creates a reviewer conflict for that configuration, not proof that every production request uses it. |
| 12. No advertising or data business | No | documented Confirmed at document level | We also use Personal Information to conduct interest-based advertisingSource Privacy: 'we do share Personal Information for other benefits that could be deemed a sale or sharing' and 'Business Partners' disclosure for third-party products of interest; Google Analytics and session replay. Applied the same standard as for commercial tools. |
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, with unresolved data-use terms
Legacy editorial placement, pre-method: 90
No eligible reviewer. This tool uses AI models from both companies whose models code HugoScore reviews, Anthropic and OpenAI, so neither may review it. 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: 90
Method v1.3. The control line is evidence for how the agency finding arose, not a quality score. Legacy editorial placement, pre-method: 90. Not comparable with v1.3 positions.
Potentially agency-expanding, with unresolved data-use terms
Fight Health Insurance encourages patients to revise appeal drafts and check citations. Its AI page and terms give conflicting training descriptions. Useful AI disclosures support scrutiny, but the current privacy policy could not be retrieved.
Patient agency
How this tool changes agency
the concrete instructions to inspect evidence are more informative than a generic assurance of accuracy. They support a qualified positive finding. They do not prove lasting gains in understanding or an independently validated advantage over competitors.
Actual training practice, current privacy terms, output reuse, production/code correspondence, and deletion.
Patient agency assessment
Who sets and changes the goal?
the consumer workflow assigns the patient responsibility for deciding what to send. A specialty appeal goal is compatible with patient direction. Whether the system supports broader goal changes is untested.
What can the patient understand, question, or do?
the concrete instructions to inspect evidence are more informative than a generic assurance of accuracy. They support a qualified positive finding. They do not prove lasting gains in understanding or an independently validated advantage over competitors.
Can the patient evaluate the conditions of use?
conflicting training descriptions prevent a clear account of the conditions under which a patient can rely on the service. Open source enables outside scrutiny, but is not evidence of production parity or effective patient contestability. The baseline's on-device OCR description must not be read as proof that appeal generation stays on-device.
Text findings
Conditions of use
Published controls and their limits
conflicting training descriptions prevent a clear account of the conditions under which a patient can rely on the service. Open source enables outside scrutiny, but is not evidence of production parity or effective patient contestability. The baseline's on-device OCR description must not be read as proof that appeal generation stays on-device.
What remains unknown?
Not tested or not established
Actual training practice, current privacy terms, output reuse, production/code correspondence, and deletion.
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
- https://www.fighthealthinsurance.com/about-ai
- https://www.fighthealthinsurance.com/tos
- https://www.fighthealthinsurance.com/privacy_policy
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 training practice, current privacy terms, output reuse, production/code correspondence, and deletion. 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 · Medium for published documentation, low for implementation (AI-assisted draft)