AI Transparency & Ethics Policy
Effective Date: February 2026
Document Version: 1.0
Introduction
Rymeda, Inc. ("Rymeda," "we," "us") integrates artificial intelligence ("AI") and machine learning ("ML") systems into its healthcare technology platform to assist licensed healthcare providers with clinical documentation, transcription, decision support, and operational workflows. This AI Transparency & Ethics Policy describes the AI systems we use, how they process data, the safeguards we employ, and the rights of patients and providers.
This policy is guided by a core principle: AI assists healthcare providers — it does not replace them. Every AI-generated output on the Rymeda platform requires human review, validation, and approval by a licensed clinician before it becomes part of a patient's medical record or influences clinical decisions.
California AB 3030 Disclosure
In accordance with California Assembly Bill 3030 (Health & Safety Code §1279.06), Rymeda discloses that generative artificial intelligence is used in the generation of clinical communications, documentation, and decision support on this platform. All AI-generated content is clearly labeled, subject to human review by a licensed healthcare provider, and patients have the right to opt out of AI processing.
1. AI Systems Inventory
Rymeda employs the following AI systems in its platform. Each system is disclosed with its purpose, data inputs, and risk classification:
1.1 OpenAI Whisper — Voice Transcription
| Provider | OpenAI, Inc. |
| Purpose | Automatic speech recognition (ASR) for transcription of recorded clinical encounters |
| Data Input | Voice audio recordings (WebM, MP4, MPEG, WAV, OGG formats) uploaded by authorized clinical staff with verified credentials |
| Data Output | Text transcription of the clinical encounter |
| Human Review | Required — transcript is reviewed by the clinical provider before further processing |
| Risk Classification | High-risk (processes health-related biometric data per EU AI Act Annex III, §5(b)) |
1.2 OpenAI GPT (via LiteLLM) — Clinical Note Generation
| Provider | OpenAI, Inc. (accessed via LiteLLM abstraction layer) |
| Purpose | Generation of structured SOAP notes, visit summaries, suggested ICD-10 diagnosis codes with confidence scores, and follow-up recommendations from clinical encounter transcripts |
| Data Input | Transcribed clinical encounter text (output from Whisper) |
| Data Output | Structured SOAP note (Subjective, Objective, Assessment, Plan), visit summary, suggested diagnoses with ICD-10 codes and confidence scores, follow-up actions with timeframes |
| Human Review | Required — all output flagged as "AI_DRAFT — REQUIRES PROVIDER REVIEW" until signed by a licensed provider |
| Risk Classification | High-risk (generates clinical documentation that may influence medical decisions per EU AI Act Annex III, §5(b)) |
1.3 Google Gemini — Clinical Note Generation
| Provider | Google LLC |
| Purpose | Alternative AI model for clinical note generation and clinical decision support, providing model diversity and failover capability |
| Data Input | Transcribed clinical encounter text, de-identified clinical context |
| Data Output | Structured SOAP notes, clinical suggestions, decision support content |
| Human Review | Required — same human-in-the-loop requirements as OpenAI GPT outputs |
| Risk Classification | High-risk (same classification as OpenAI GPT — clinical documentation generation) |
1.4 Anthropic Claude (via LiteLLM) — Clinical Note Generation
| Provider | Anthropic, PBC (accessed via LiteLLM abstraction layer) |
| Purpose | Alternative AI model for clinical note generation, clinical decision support, and structured data extraction, providing model diversity and failover capability |
| Data Input | Transcribed clinical encounter text, de-identified clinical context |
| Data Output | Structured SOAP notes, clinical suggestions, decision support content |
| Human Review | Required — same human-in-the-loop requirements as OpenAI GPT and Google Gemini outputs |
| Risk Classification | High-risk (same classification as OpenAI GPT — clinical documentation generation per EU AI Act Annex III, §5(b)) |
1.5 ORIS — Healthcare AI Assistant
| Provider | ORIS (custom healthcare AI integration) |
| Purpose | Clinical decision support, task prioritization, daily runbook generation, and healthcare workflow optimization with Retrieval-Augmented Generation (RAG) |
| Data Input | User messages (max 5,000 characters), user context (role, page, session), healthcare knowledge base (via RAG) |
| Data Output | Conversational responses, task recommendations, clinical workflow guidance, prioritized daily task runbooks |
| Safety Guardrails | Emergency detection (redirects to 911), blocked content filtering, off-topic deflection, rate limiting |
| Risk Classification | High-risk (clinical decision support per EU AI Act Annex III, §5(b)) |
1.6 Trust & Safety AI — Content Moderation
| Provider | Rymeda internal system |
| Purpose | Automated content moderation, trust scoring, and community safety enforcement |
| Decision Threshold | Automated actions require 85% confidence; below-threshold cases are escalated to human moderators |
| Actions | Warning, muting, suspension, ban, rate limiting — all subject to human appeal |
| Risk Classification | Limited risk (content moderation with human oversight and appeal mechanisms) |
2. Training Data and Data Usage
Patient Data Training Prohibition
Rymeda does not use patient data, clinical records, voice recordings, or any Protected Health Information (PHI) to train, fine-tune, or improve AI models. This applies to all first-party and third-party AI systems used on the platform.
2.1 Third-Party No-Training Agreements
Rymeda maintains contractual agreements with all AI providers that prohibit the use of Rymeda customer data for model training:
- OpenAI: Data submitted through the API is not used to train or improve OpenAI models, per OpenAI's API Data Usage Policy and our Business Associate Agreement with OpenAI. Zero data retention (ZDR) is configured where available.
- Google Gemini: Processing under Google Cloud's enterprise terms, which prohibit use of customer data for model training. Data processed subject to Google Cloud HIPAA BAA.
- Anthropic: Data submitted through the API is not used to train or improve Anthropic models, per Anthropic's API Terms of Service and our Business Associate Agreement. API usage is covered under Anthropic's enterprise data handling commitments.
- ORIS: Healthcare-specific AI with contractual guarantees against using client data for training. API keys are kept server-side only and never exposed to clients.
2.2 Data Handling During AI Processing
- Voice recordings are transmitted to OpenAI Whisper via encrypted API calls (TLS 1.3) and are not retained by OpenAI after transcription
- Clinical note content sent to AI models passes through Rymeda's PHI redaction pipeline before reaching external processors where technically feasible
- All AI API communications use authenticated, encrypted channels with unique session identifiers for auditability
- AI processing is logged in Rymeda's immutable audit trail with model version, timestamp, and input/output metadata
3. Human-in-the-Loop Requirements
Rymeda enforces mandatory human oversight for all AI-generated clinical content. No AI output is automatically incorporated into a patient's medical record or used for clinical decisions without explicit human review and approval.
3.1 AI Draft Status
All AI-generated clinical content is assigned an "AI_DRAFT" status upon creation. This status is prominently displayed in the platform interface and persists until a licensed provider reviews and signs the content. The status lifecycle is:
| Status | Description | Clinical Use |
|---|---|---|
| draft | Manually created by provider, not yet finalized | Not permitted for clinical use |
| ai_draft | AI-generated content awaiting provider review — displays "AI_DRAFT — REQUIRES PROVIDER REVIEW" banner | Not permitted for clinical use |
| reviewed | Provider has reviewed and edited the content | Not permitted for clinical use until signed |
| signed | Provider has signed the content — this action is irreversible | Permitted — becomes part of medical record |
| amended | Signed content that has been amended with an addendum | Original preserved; amendment appended |
3.2 Provider Signature Requirements
Only providers with full clinical chart access may sign clinical documents. This is restricted to:
- Physicians (MD/DO)
- Nurse Practitioners (NP)
- Physician Assistants (PA)
The signing provider must have verified credentials (verification status: "verified") through Rymeda's NPI/NPPES validation system. Signing is an irreversible action — once signed, a clinical note cannot be deleted or unsigned, only amended with a documented addendum.
3.3 No Auto-Approval
Rymeda does not and will not implement any mechanism that automatically approves, signs, or incorporates AI-generated content into clinical records. There is no batch signing, no timed auto-approval, and no workflow that bypasses explicit human review. Each clinical document requires individual review and signature.
4. AI Labeling and Transparency
All AI-generated content on the Rymeda platform is labeled with the following metadata to ensure full transparency and traceability:
| Label | Description | Example |
|---|---|---|
| AI-Generated Flag | Boolean indicator that the content was generated by AI | ai_generated: true |
| Model Version | Identifier of the AI model and version used to generate the content | ai_model_version: "gpt-4-turbo-2024-04-09" |
| Generation Timestamp | UTC timestamp of when the AI content was generated | generated_at: "2026-02-10T14:30:00Z" |
| Confidence Scores | Numerical confidence for suggested diagnoses and ICD-10 codes | {code: "J06.9", confidence: 0.87} |
| Source Voice Note ID | Link to the original voice recording from which the content was derived | original_voice_note_id: "uuid" |
| Review Status | Current review state (ai_draft, reviewed, signed, amended) | status: "ai_draft" |
| Signing Provider | Identity of the provider who reviewed and signed the content | signed_by: "provider_uuid" |
The full provenance chain for every AI-generated document — from original voice recording through transcription, AI generation, human review, and signature — is recorded in Rymeda's immutable audit trail and available via the voice note audit trail endpoint.
5. Model Governance
5.1 Model Versioning
Every AI-generated output records the specific model version used (ai_model_version). This ensures traceability and enables retrospective analysis if model behavior changes. When AI providers release new model versions, Rymeda evaluates the new version in a staging environment before deploying to production.
5.2 Change Management
Changes to AI systems follow a structured change management process:
- Model upgrades: New model versions are tested against a validation dataset of representative clinical scenarios before production deployment
- Provider changes: Adding or replacing an AI provider requires a Data Protection Impact Assessment (DPIA), security review, BAA execution, and Sub-processor notification per the DPA
- Prompt engineering: Changes to system prompts and AI instructions undergo clinical review by licensed healthcare professionals
- Rollback capability: All AI system changes are reversible, with the ability to revert to a previous model version within 24 hours
5.3 Monitoring
Rymeda continuously monitors AI system performance, including:
- Transcription accuracy metrics and error rates
- Clinical note quality indicators (provider edit rates, rejection rates)
- ICD-10 suggestion acceptance rates and confidence calibration
- ORIS guardrail trigger rates (emergency, blocked, off-topic)
- AI system latency and availability (API response times, failure rates)
- Trust & Safety moderation accuracy and false positive/negative rates
6. Bias and Fairness
6.1 Commitment to Fairness
Rymeda is committed to ensuring that AI systems do not introduce or amplify bias in healthcare delivery. We acknowledge that AI models may reflect biases present in their training data and take active measures to monitor and mitigate such biases.
6.2 Demographic Monitoring
Where technically feasible and legally permissible, Rymeda monitors AI system outputs for disparities across demographic groups, including:
- Transcription accuracy across accents, dialects, and languages
- Clinical suggestion patterns across patient demographics (age, gender, ethnicity)
- ICD-10 code suggestion distributions for potential coding bias
- Trust & Safety moderation actions for disparate impact across user groups
6.3 Testing and Validation
Rymeda conducts periodic fairness assessments including:
- Pre-deployment bias testing for new AI models and model versions
- Regular audits of AI-generated clinical content for systematic errors or biases
- Analysis of provider override patterns (edits and rejections of AI suggestions) for potential bias indicators
- Review of false positive and false negative rates in automated moderation across user demographics
6.4 Reporting Bias
Healthcare providers and patients who identify potential AI bias in the platform may report it to legal@rymeda.com. All reports are investigated, and confirmed biases are addressed through model adjustments, prompt refinement, or provider changes.
7. Liability and Clinical Responsibility
Important Disclaimer
Rymeda is a technology platform, NOT a healthcare provider. Rymeda does not practice medicine, provide medical advice, diagnose conditions, or prescribe treatments. AI-generated content is a clinical productivity tool — not a substitute for professional medical judgment.
7.1 Provider Responsibility
The licensed healthcare provider who reviews and signs AI-generated clinical content assumes full clinical and legal responsibility for that content. By signing, the provider attests that they have:
- Reviewed the AI-generated content for accuracy and completeness
- Made any necessary corrections, additions, or modifications
- Confirmed that the content accurately reflects the clinical encounter
- Accepted the content as their own professional clinical documentation
7.2 Rymeda's Liability
Rymeda's liability with respect to AI systems is as follows:
- Platform availability: Rymeda is responsible for the availability and proper functioning of AI features per the Service Level Agreement
- Security: Rymeda is responsible for securing AI data pipelines and protecting PHI during AI processing per the BAA
- Transparency: Rymeda is responsible for disclosing AI use, labeling AI content, and maintaining this policy
- Clinical decisions: Rymeda explicitly disclaims liability for clinical decisions made by healthcare providers, including decisions informed by AI-generated content. The provider retains full clinical responsibility.
7.3 No Accuracy Warranty
AI-generated content (including transcriptions, SOAP notes, ICD-10 codes, diagnosis suggestions, and follow-up recommendations) is provided "as is" without warranty of accuracy, completeness, or fitness for a particular clinical purpose. Confidence scores are probabilistic estimates, not guarantees. This is why human review is mandatory.
8. Patient Rights
Patients have the following rights with respect to AI processing of their health data:
8.1 Right to AI Disclosure (California AB 3030)
Patients have the right to be informed when generative AI is used in their care. In compliance with California Health & Safety Code §1279.06 (AB 3030), Rymeda ensures that AI use is disclosed to patients before AI processing occurs. Covered entities using Rymeda are responsible for providing this disclosure at the point of care, using the Patient Consent Forms.
8.2 Right to Opt Out of AI Processing
Patients may opt out of AI processing of their clinical data at any time. Opting out means: voice recordings will not be transcribed by AI; clinical notes will be created manually by the provider; no AI-generated diagnosis suggestions or ICD-10 codes will be produced. Opt-out requests should be directed to the patient's healthcare provider or to legal@rymeda.com. Opting out does not affect the quality or availability of care.
8.3 Right to Request Manual Documentation
Patients may request that their clinical documentation be created manually (without AI assistance) for any or all encounters. This right may be exercised on a per-encounter basis and does not require a global opt-out.
8.4 Right to Contest AI-Generated Content
Patients may contest AI-generated content in their medical records. If a patient believes that AI-generated content is inaccurate, they may: (a) request the treating provider review and correct the content; (b) request an amendment to their medical record under 45 CFR §164.526; or (c) file a complaint with the Privacy Officer.
8.5 Right to Voice Recording Consent
Separate from AI processing consent, patients have the right to consent to or refuse voice recording of clinical encounters. Under California Penal Code §632, voice recording requires two-party consent, which must be obtained before recording begins. Consent for recording is separate from telehealth consent and HIPAA authorization — these three consents cannot be bundled. Patients may refuse recording on a per-encounter basis. See Patient Consent Forms.
8.6 Right to Human Review
Patients have the right to know that all AI-generated clinical content in their medical record has been reviewed and signed by a licensed healthcare provider. No AI-generated content is entered into a patient's record without human review.
9. Prohibited Uses of AI
Rymeda explicitly prohibits the following uses of AI on its platform:
9.1 No Autonomous Clinical Decisions
AI shall not make autonomous clinical decisions — including diagnosis, treatment selection, medication prescribing, or care plan determination — without explicit review and approval by a licensed healthcare provider. AI outputs are suggestions only.
9.2 No Insurance Denial Without Human Review
AI-generated content, including ICD-10 codes and diagnosis suggestions, shall not be used as the sole basis for insurance coverage determinations, claim denials, prior authorization decisions, or any adverse benefit determination without independent human review.
9.3 No Discriminatory Profiling
AI shall not be used for discriminatory profiling based on race, ethnicity, gender, age, disability, sexual orientation, socioeconomic status, or any other protected characteristic. This includes differential treatment recommendations, access restrictions, or resource allocation based on protected characteristics.
9.4 No Predictive Denial
AI shall not be used to predict or pre-determine patient outcomes for the purpose of denying care, limiting treatment options, or restricting access to services.
9.5 No Unauthorized Data Mining
AI shall not be used to mine patient data for marketing purposes, sell patient insights, or create patient profiles for non-clinical purposes without explicit patient authorization.
9.6 No Surveillance
AI shall not be used for patient surveillance, behavioral monitoring outside the clinical context, or tracking patient activities beyond what is necessary for the provision of healthcare services.
10. EU AI Act Compliance
10.1 Risk Classification
Under the European Union Artificial Intelligence Act (Regulation (EU) 2024/1689), Rymeda's AI systems are classified as follows:
| AI System | Classification | Basis |
|---|---|---|
| OpenAI Whisper (Transcription) | High-Risk | Annex III, §5(b) — AI in healthcare, processing biometric data |
| OpenAI GPT (Clinical Notes) | High-Risk | Annex III, §5(b) — AI in healthcare, clinical documentation generation |
| Google Gemini (Clinical Notes) | High-Risk | Annex III, §5(b) — AI in healthcare, clinical documentation generation |
| ORIS (Decision Support) | High-Risk | Annex III, §5(b) — AI in healthcare, clinical decision support |
| Trust & Safety (Moderation) | Limited Risk | Article 50 — transparency obligations for AI interacting with users |
10.2 High-Risk Compliance Measures
For high-risk AI systems, Rymeda implements the following measures in alignment with the EU AI Act:
- Risk Management (Article 9): Continuous risk assessment and mitigation for all AI systems
- Data Governance (Article 10): Quality controls on training data (managed by AI providers under no-training agreements)
- Technical Documentation (Article 11): This policy and the AI Systems Inventory (Section 1)
- Record-Keeping (Article 12): Immutable audit trails with 6-year retention for all AI operations
- Transparency (Article 13): AI labeling system (Section 4) and AB 3030 disclosure
- Human Oversight (Article 14): Mandatory human-in-the-loop for all clinical AI (Section 3)
- Accuracy and Robustness (Article 15): Model monitoring (Section 5.3) and bias testing (Section 6)
11. Policy Review and Updates
This AI Transparency & Ethics Policy is reviewed and updated:
- Annually: As part of Rymeda's regular compliance review cycle
- When AI systems change: Upon adding, replacing, or significantly modifying any AI system
- When regulations change: Upon the effective date of new AI regulations (EU AI Act implementation timeline, state-level AI healthcare laws, updated FDA guidance)
- When incidents occur: Following any AI-related safety incident, bias discovery, or material error
Material changes to this policy will be communicated to users with thirty (30) days' advance notice via email and in-platform notification.
12. Contact Information
For questions about AI transparency, to report AI bias, or to exercise AI-related rights:
Related Policies
Patient Consent Forms
AI processing consent, voice recording consent
HIPAA Notice of Privacy Practices
AI-assisted documentation disclosure
Privacy Policy
AI-generated data collection and processing
Business Associate Agreement
PHI handling during AI processing
Data Processing Agreement
AI Sub-processor management and DPIA
Terms of Service
AI content disclaimers and liability
Clinical Data Governance
AI draft review workflows and access controls
Security
AI data pipeline security measures