Documentation
Start typing to search…

Pre-deployment Checklist

Customer requirements checklist for SaaS and on-premises Revenue Recovery deployments

This checklist outlines the requirements that your organization needs to fulfill before deploying the Revenue Recovery platform. The checklist is organized by deployment type, with clear indicators of your responsibilities versus services provided by [Ai]levate.

Common Requirements (All Deployments)

Technical Points of Contact

Customer must provide:

  • Primary technical contact
    • Name and Title
    • Email Address
    • Phone Number
    • Location
  • Backup technical contact
  • Preferred maintenance window schedule
  • Emergency escalation contacts

Relay Service Requirements

Customer must provide:

  • Virtual machine for Relay Service
    • Minimum 4 vCPUs
    • 16 GB RAM
    • 100 GB storage
  • Network connectivity to EHR system
  • Outbound internet access for Relay Service
    • No inbound firewall rules required
    • Minimum 100 Mbps bandwidth

Authentication Configuration

Customer must select and provide:

  • Identity provider configuration
    • Azure AD (EntraID)
    • Magic Link (Email Auth)
  • List of administrative users
  • User role assignments
  • IP or Domain allowlist (recommended for Email Auth)

SaaS Deployment Requirements

In a SaaS deployment, [Ai]levate manages the Cloud Services, Database Storage, and AI Warehouse layers. Your organization is responsible for the following requirements:

Network Connectivity

Customer must provide:

  • Preferred Azure region selection (currently East US, additional regions planned)
  • Network connectivity to Azure
    • Direct internet connectivity, or
    • Azure ExpressRoute (if required)
  • Firewall rules for Relay Service communication

EHR Integration

sequenceDiagram
    participant EHR as EHR System
    participant Relay as Relay Service
    participant Cloud as [Ai]levate Cloud Services
    
    Note over EHR,Relay: Customer Environment
    Note over Cloud: [Ai]levate Cloud
    
    EHR->>Relay: Denied claim data
    Relay->>Cloud: Secure outbound transmission
    Cloud-->>Relay: Remediation instructions
    Relay-->>EHR: Update claim

Secure outbound-only communication flow between EHR and [Ai]levate platform

Customer must provide:

  • EHR connectivity method and credentials
    • SQL connection strings and database user account with required permissions, or
    • API credentials and endpoints for API-based integration
  • Sample data for integration testing

[Ai]levate provides and manages:

  • Cloud Services Layer
  • Database Storage Layer (encrypted Elastic datastore)
  • AI Warehouse (Tenstorrent hardware in [Ai]levate colocation facility)
  • Security patches and updates
  • Backup and disaster recovery
  • Monitoring and alerting
  • Compliance controls

On-Premises Deployment Requirements

In an on-premises deployment, your organization manages the Database Storage and AI Warehouse layers, while [Ai]levate manages the Cloud Services layer.

Infrastructure Requirements

Customer must provide:

  • Elastic datastore environment
    • Hardware meeting performance requirements
    • Network capacity for expected workload
    • Backup infrastructure and procedures
    • Encryption at rest (AES-256)
  • AI Warehouse infrastructure (at customer site or customer colocation)
    • Tenstorrent hardware procurement
    • Network connectivity for AI services
    • Physical/virtual hosting environment
    • Monitoring and management tools

Security Configuration

Customer must configure:

  • Network segmentation for AI Warehouse
  • Inbound TLS access for [Ai]levate Cloud Services to connect to AI Warehouse and Elastic datastore
  • Data encryption standards
  • Access control policies
  • Security monitoring
  • Compliance controls

Database Environment

Customer must provide and manage:

  • Elastic datastore cluster
    • High availability configuration
    • Backup and recovery procedures
    • Performance monitoring
    • Maintenance schedules

[Ai]levate provides:

  • Cloud Services Layer
  • AI model images for Tenstorrent hardware
  • Technical guidance and best practices
  • Integration support

Administrative Access

For All Deployments

Customer must provide:

  • Relay Service access
    • SSH credentials for maintenance
    • Network access permissions
    • Monitoring access
  • Change management procedures
  • Support escalation process

Additional On-Premises Access

Customer must provide:

  • AI Warehouse management access
  • Elastic datastore administration access
  • Infrastructure monitoring access

Next Steps

After completing the requirements for your deployment type:

  1. For SaaS deployments:

  2. For on-premises deployments:

  3. Common next steps:

Copy-Pastable Checklist

Below is a plain text version of the checklist that can be easily copied and used in project planning tools if desired:

Revenue Recovery Pre-deployment Checklist

COMMON REQUIREMENTS (ALL DEPLOYMENTS)
Technical Points of Contact:
☐ Primary technical contact details captured (name, title, email, phone)
☐ Backup technical contact details captured
☐ Preferred maintenance window schedule defined
☐ Emergency escalation contacts documented

Relay Service Requirements:
☐ Virtual machine provisioned (4+ vCPUs, 16GB+ RAM, 100GB+ storage)
☐ Network connectivity to EHR system verified
☐ Outbound internet access configured (100+ Mbps)
☐ No inbound firewall rules required - confirmed

Authentication Setup:
☐ Identity provider selected and configured (Azure AD (EntraID) / Magic Link)
☐ Administrative users identified and documented
☐ User roles defined
☐ IP or Domain allowlist requirements documented (if utilized)

SaaS DEPLOYMENT REQUIREMENTS
Network Requirements:
☐ Azure region selected (East US, additional regions planned)
☐ Azure network connectivity confirmed
☐ ExpressRoute requirements evaluated (if needed)
☐ Relay Service firewall rules documented

EHR Integration:
☐ EHR connectivity method determined (SQL or API-based)
☐ SQL connection strings documented (if using SQL), or
☐ API credentials and endpoints documented (if using API)
☐ Access permissions configured
☐ Test data prepared

ON-PREMISES DEPLOYMENT REQUIREMENTS
Infrastructure:
☐ Elastic datastore environment prepared
☐ Hardware meets performance requirements
☐ Network capacity confirmed
☐ Backup infrastructure ready
☐ AES-256 encryption configured
☐ AI Warehouse infrastructure prepared (at customer site or colocation)
☐ Tenstorrent hardware procured
☐ Hosting location determined
☐ Network connectivity verified
☐ Monitoring tools configured

Security:
☐ Network segmentation implemented
☐ Inbound TLS access configured for [Ai]levate Cloud Services to connect to AI Warehouse and Elastic
☐ Encryption standards implemented
☐ Access control policies defined
☐ Security monitoring configured
☐ Compliance controls implemented

Database:
☐ Elastic cluster configured
☐ High availability setup complete
☐ Backup procedures documented
☐ Maintenance schedule established

ACCESS REQUIREMENTS
All Deployments:
☐ Relay Service access configured
☐ SSH credentials documented
☐ Network permissions set
☐ Monitoring access enabled
☐ Change management process documented
☐ Support procedures defined

Additional On-Premises Access:
☐ AI Warehouse management access configured
☐ Elastic datastore admin access configured
☐ Infrastructure monitoring access set up

Updated about 1 month ago