User Manual Overview

This section provides practical guides for healthcare providers using Oneliac to verify insurance eligibility, validate prescriptions, and participate in federated learning.

Who Should Use This Manual?

Healthcare Provider System Administrators

• Setting up Oneliac integration with your hospital systems
• Configuring API credentials and endpoints
• Managing encryption keys and security

Clinical Software Developers

• Integrating eligibility verification into your EHR
• Implementing prescription validation workflows
• Connecting to Oneliac APIs

Hospital Operations Teams

• Understanding system workflows
• Troubleshooting common issues
• Monitoring system health and performance

Oneliac Components

Oneliac provides three main agents for healthcare operations:

1. Eligibility Checker

Check patient insurance coverage for procedures before treatment.

Use Case: Verify if a patient is covered for an MRI scan before scheduling.

Patient Information
    ↓
Eligibility Checker (with ZK Proofs)
    ↓
Coverage Result: 80% covered, pre-auth required

Benefits:

• Prevent billing surprises
• Automate authorization workflows
• Protect patient privacy during verification

2. Prescription Validator

Validate medications against patient medical history and insurance coverage.

Use Case: Verify a prescription for Warfarin is safe and covered.

Drug Code: DRUG001
    ↓
Prescription Validator
    ↓
Check drug interactions
Check insurance coverage
Query pharmacy system
    ↓
Result: Safe, covered, available at network pharmacies

Benefits:

• Prevent dangerous drug interactions
• Reduce medication errors
• Streamline prescription workflows

3. Federated Learning Coordinator

Participate in privacy-preserving training of diagnosis models.

Use Case: Improve diagnosis accuracy by sharing data in federated learning without exposing patient records.

Patient Medical Data (encrypted)
    ↓
Compute encrypted gradients
Add differential privacy noise
    ↓
Federated Learning Coordinator
    ↓
Aggregate with other hospitals
Update diagnosis model
    ↓
Get improved model weights

Benefits:

• Improve diagnosis AI across all participants
• Keep patient data private
• HIPAA/GDPR compliant

System Architecture for Users

Your Hospital System
    ↓
EHR (Electronic Health Records)
    ↓
Oneliac Integration Layer
    ├─→ Eligibility Verification API
    ├─→ Prescription Validation API
    └─→ Federated Learning API
    ↓
Oneliac Platform (Hosted or Self-Hosted)
    ├─→ Patient Data Encryption
    ├─→ Zero-Knowledge Proofs
    ├─→ IPFS Storage
    └─→ Solana Blockchain
    ↓
Insurance Systems, Pharmacy Networks, etc.

Quick Reference

Agent	Endpoint	Input	Output
Eligibility	POST /verify-eligibility	Patient ID, Procedure Code	Coverage %, Authorization Required
Prescription	POST /validate-prescription	Patient ID, Drug Code	Valid/Invalid, Interactions
Federated	POST /submit-federated-update	Patient Data List	Round #, Model Hash

Getting Started

Choose your use case:

1. Eligibility Checker - Verify insurance coverage
2. Prescription Validator - Validate medications
3. Federated Learning - Train diagnosis models

How Data Flows Through Oneliac

Privacy-Preserving Process

1. Your System sends patient data
2. Encryption Layer converts to ciphertext
3. IPFS Storage records encrypted data
4. ZK Proof Generator creates proof without revealing data
5. Solana Smart Contract verifies proof
6. Agent performs healthcare logic
7. Result returned to you (without exposing raw data)

Privacy Guarantees

• ✅ Patient data is encrypted end-to-end
• ✅ Oneliac system only handles encrypted data
• ✅ Medical information revealed only through cryptographic proofs
• ✅ Audit trail recorded on immutable blockchain
• ✅ Differential privacy prevents individual patient identification

Security Checklist

Before using Oneliac in production:

• API keys and credentials stored securely
• HTTPS/TLS used for all communications
• Patient data encrypted before transmission
• Firewall rules limiting API access
• Regular security audits scheduled
• Incident response plan in place
• HIPAA Business Associate Agreement signed
• Staff training on data protection completed

Support and Resources

Resource	Link
API Documentation	Endpoints Reference
Integration Guide	Setup Instructions
Troubleshooting	FAQ & Troubleshooting
Security Best Practices	Security Guide
GitHub Organization	https://github.com/orgs/Oneliac
Telegram Support	https://t.me/oneliac_bot
Website	https://www.oneliac.xyz

Common Workflows

Workflow 1: Daily Eligibility Checks

1. Patient arrives at hospital
2. Registration system triggers eligibility check
3. Oneliac returns coverage info
4. Staff informs patient of cost

Workflow 2: E-Prescribing with Validation

1. Doctor writes prescription in EHR
2. System sends to Oneliac for validation
3. Oneliac checks interactions and coverage
4. If safe, prescription sent to pharmacy
5. Pharmacy confirms drug availability

Workflow 3: Federated Learning Participation

1. Monthly training round scheduled
2. Encrypted patient batches submitted
3. Hospital's local model trains
4. Gradients securely aggregated
5. Improved global model distributed

Compliance Considerations

• HIPAA: Oneliac ensures patient data privacy
• GDPR: Data minimization through encryption
• CCPA: Patient consent mechanisms
• State Laws: Varies by state regulations

Consult with your compliance officer before deployment.

Next Steps

1. Review Getting Started for installation
2. Choose your use case from the manual sections
3. Follow Integration Guide for setup
4. Test with sample data in development environment
5. Plan deployment strategy

---

Questions? Check FAQ, visit GitHub, or reach out on Telegram.