Knowledge Base

AI EHR Documentation

Complete guides, tutorials, and references for deploying, configuring, and maximizing your AI EHR platform.

Getting Started with AI EHR

Welcome to the AI EHR documentation. This platform is an AI-native Electronic Health Records system designed for modern healthcare organizations — from single-practice clinics to multi-site health systems. Built on FHIR R4+ standards with ONC 2020 Edition certification and full HIPAA compliance.

In This Article

  1. Prerequisites
  2. Installation Methods
  3. Activation & Licensing
  4. Initial Configuration
  5. Importing Patient Data
  6. AI Model Training
  7. First Patient Record

1. Prerequisites

Before installing AI EHR, ensure your environment meets the following requirements:

  • Server: Linux (Ubuntu 22.04 LTS or RHEL 9) with minimum 32GB RAM, 8 CPU cores, 500GB NVMe SSD
  • Database: PostgreSQL 16+ with PostGIS extension (required for FHIR indexing)
  • Network: Outbound HTTPS (443), inbound HTTPS (443), optional Redis 7.0+ for caching
  • Browser Support: Chrome 120+, Firefox 115+, Safari 17+, Edge 120+
  • Mobile: iOS 17+ or Android 14+ for patient portal and provider mobile app
  • Certifications: ONC 2020 Edition ABCs certification (included with Enterprise tier)

Pro Tip: For health systems with 500+ providers, we recommend a dedicated PostgreSQL cluster with read replicas and a dedicated Elasticsearch instance for FHIR search performance. Contact our solutions team for architecture guidance.

2. Installation Methods

AI EHR supports three deployment methods based on your security, compliance, and data sovereignty requirements:

2.1 SaaS (Cloud-Hosted)

The fastest path to deployment. Our managed infrastructure handles all scaling, backups, HIPAA compliance, and security patches. Your data resides in US-based AWS regions (us-east-1, us-west-2).

# SaaS access is provided upon license activation # No server setup required — login at: https://app.aiehr.net # Initial admin credentials sent via encrypted email # Enable SSO/SAML per your identity provider

2.2 Private Cloud

Deploy on your preferred cloud provider (AWS, Azure, GCP) with our Terraform modules. Full HIPAA coverage including BAA, encryption at rest, and audit controls.

# Deploy to AWS using our Terraform module module "aiehr" { source = "the-madhacker/aiehr/aws" version = "4.2.0" region = "us-east-1" seats = 500 tier = "enterprise" # HIPAA mode automatically configures BAA + KMS hipaa_mode = true onc_certified = true encryption_key_arn = "arn:aws:kms:..." # Enable AI WFM workforce integration wfm_integration = true wfm_api_key = "aiwfm-xxxx-xxxx" }

2.3 On-Premise

Full air-gapped deployment for maximum data sovereignty. Includes Docker Compose and Kubernetes manifests. Ideal for VA facilities, DoD installations, and organizations with strict data residency requirements.

# On-premise deployment with Docker Compose git clone https://github.com/the-madhacker/aiehr-deploy.git cd aiehr-deploy # Configure environment variables cp .env.example .env # Edit .env with your license key and settings # Set HIPAA_MODE=true for full compliance docker compose up -d # Access at https://your-domain.local # Initial setup wizard at /admin/setup

3. Activation & Licensing

Upon installation, activate your perpetual license using your license key:

# Activate your license key curl -X POST https://app.aiehr.net/api/v2/license/activate \ -H "Content-Type: application/json" \ -d '{ "license_key": "AIEHR-XXXX-XXXX-XXXX", "organization": "Your Health System", "admin_email": "[email protected]", "tier": "enterprise", "hipaa_mode": true, "onc_certified": true }'

4. Initial Configuration

After activation, complete the setup wizard to configure your organization:

  1. Organization Profile: Name, NPI, tax ID, timezone, default language
  2. Certification: ONC 2020 Edition ABCs configuration (clinics) or Full Edition (hospitals)
  3. Sites/Locations: Add each physical site with address, NPI, and state licensing info
  4. Departments: Create clinical departments, divisions, and service lines
  5. CDS Hooks: Configure clinical decision support rules and SMART on FHIR apps
  6. ePrescribing: Connect to Surescripts and configure DEA registration
  7. SSO/SAML: Configure identity provider for single sign-on

Critical: ONC Certification requires specific configuration of health IT capabilities including ePrescribing, clinical decision support, and patient access. Our setup wizard walks you through each certification criterion. Failure to complete certification configuration will prevent MIPS reporting eligibility.

5. Importing Patient Data

Import existing patient records via CSV upload, FHIR Bundle, or through integrations with legacy EHR systems:

# Bulk patient import via FHIR Bundle POST /api/v2/fhir/Batch Content-Type: application/fhir+json { "resourceType": "Bundle", "type": "batch", "entry": [ { "resource": { "resourceType": "Patient", "name": [{"family": "Johnson", "given": ["Maria"]}], "gender": "female", "birthDate": "1985-03-15", "address": [{"line": ["123 Main St"], "city": "Nashville", "state": "TN", "postalCode": "37211"}] } } ] }

6. AI Model Training

The clinical NLP engine and predictive risk models require historical patient data to calibrate. We recommend importing at least 12 months of clinical documentation:

  • Minimum: 3 months of clinical notes for basic NLP calibration
  • Recommended: 12–24 months for optimal accuracy (96.8% on structured extraction)
  • Training Time: Typically 4–12 hours depending on dataset size
  • Data De-identification: All training data is de-identified per HIPAA Safe Harbor method before model training

AI WFM Workforce Integration: When enabled, AI EHR can automatically sync staffing data from AI WFM to ensure clinical documentation requirements align with actual staffing levels. Nurse-to-patient ratios, shift assignments, and coverage gaps all flow between platforms in real-time.

7. Creating Your First Patient Record

Once your organization is configured, create your first patient record:

AI EHR — Patient Record | Dr. Sarah Chen
Patient: Maria Johnson
Active Patient
Demographics

DOB: 03/15/1985 (41y)
Gender: Female
NPI: 1234567890
Mrn: 20260001

Recent Activity

Visit: 09/08/2026 — Annual Physical
Lab: 09/05/2026 — CBC, CMP
Med: 09/01/2026 — Lisinopril 10mg

AI Risk Score

Risk Level: Low (12/100)
Next Review: 09/15/2026
NLP Notes: 3 documents processed

Staffing Assignment

Primary: Dr. Sarah Chen
Shift: 09/10 — Day Shift (0700-1900)
Coverage: AI WFM Verified ✓

Navigate to Clinical → New Patient or use the Quick Add button. The AI Scribe will automatically populate fields from uploaded documents, and the AI WFM module will verify staffing coverage before the visit is finalized.