AI Safety
Vytherix takes a conservative approach to AI in care operations: limited scope, approved data flows, human review, and clear boundaries.
Last updated: June 5, 2026. This page describes current website safety practices and should be reviewed as part of any formal compliance or security program.
Local, self-hosted by design
Vytherix is designed for local, self-hosted deployment: LLMs run on hardware the user controls, and no patient data is sent to a third-party model provider by default. Because the software is open source and runs on your machine, you — not Vytherix — are responsible for how it's configured, which models are used, and whether that setup meets your compliance obligations.
Website chat scope
The lower-right AI chat is limited to questions about Vytherix, this website, our services, workflow fit, privacy, terms, and AI safety. It is not a clinical, legal, compliance, emergency, or customer-support system for existing client operations.
Information you should not enter
Do not enter protected health information, patient records, medical facts about an individual, credentials, payment data, API keys, confidential client material, or other sensitive information into the public chat.
Guardrails we use
- Local screening for off-topic, sensitive, and emergency-style prompts.
- Server-side model calls so Gemini API keys are not exposed in the browser.
- System instructions that restrict answers to Vytherix and website topics.
- Refusals for medical, clinical, legal, financial, emergency, or PHI-related requests.
- Short conversation history and message-length limits.
Human review remains required
AI can support workflow discovery, drafting, triage, and repetitive administrative steps, but care organizations should keep humans responsible for care decisions, compliance decisions, staffing approvals, vendor approvals, and final operational judgment.
Client implementation principles
- Start with a workflow audit before selecting tools.
- Use approved systems and documented access controls.
- Minimize data sent to vendors and avoid unnecessary PHI exposure.
- Use BAAs and vendor review when health data may be involved.
- Pilot narrowly, measure outcomes, train staff, and document handoff procedures.
Emergency and care decisions
The website and chat cannot help with emergencies, urgent patient care, clinical decisions, or crisis situations. Use emergency services, licensed clinicians, internal escalation policies, or the appropriate local authority.
Not legal, medical, or compliance advice
Nothing on this site is legal, medical, or compliance advice. For compliance, legal, or clinical questions, consult qualified counsel, licensed clinicians, and your applicable regulators.