Azure VM Naming Convention

Standardized naming convention for Azure virtual machines supporting OHEMR Epic healthcare infrastructure.

---

🎯 Overview

A consistent naming convention is critical for healthcare infrastructure management, enabling rapid identification of resources during clinical incidents, audit reviews, and Epic maintenance windows.

Benefits

• Rapid Incident Response: Quickly identify impacted systems during clinical emergencies
• Epic Maintenance Coordination: Clear identification of Epic application servers for planned downtime
• Compliance Auditing: Simplified resource tracking for HIPAA and SOX audits
• Operational Efficiency: Automated monitoring and alerting based on naming patterns

---

📋 Naming Convention Structure

Format: [Platform][Region][Environment][OS][Purpose][Role][Series]

Length: 13-15 characters depending on role and purpose

---

🏥 Healthcare-Specific Examples

Epic Production Environment

Infrastructure Support

Non-Production Examples

---

🔧 Implementation Guidelines

Required Validation

Before deploying any VM, verify:

1. Naming Convention Compliance: Use the 7-position format exactly
2. Uniqueness Check: Ensure no duplicate names in the subscription
3. Environment Alignment: Match naming to actual deployment environment
4. Epic Stamp Coordination: Align with Epic environment designations

Terraform Implementation

# Example Terraform variable validation
variable "vm_name" {
  description = "VM name following OHEMR naming convention"
  type        = string

  validation {
    condition = can(regex("^[ZAGOP][ECW][PNDR][WL][A-Z]{2,3}[A-Z]{2,3}[0-9]{3}$", var.vm_name))
    error_message = "VM name must follow OHEMR naming convention: [Platform][Region][Environment][OS][Purpose][Role][Series]"
  }
}

# Standard naming for Epic production VDA
locals {
  vm_names = {
    epic_prod_vda     = "ZWPWEPSEP"
    epic_training_vda = "ZWPWEPSET"
    citrix_storefront = "ZWPWCTXSF"
  }
}

Azure Policy Enforcement

{
  "policyRule": {
    "if": {
      "allOf": [
        {
          "field": "type",
          "equals": "Microsoft.Compute/virtualMachines"
        },
        {
          "not": {
            "field": "name",
            "match": "[ZAGOP][ECW][PNDR][WL][A-Z]*[0-9][0-9][0-9]"
          }
        }
      ]
    },
    "then": {
      "effect": "deny"
    }
  }
}

---

🚨 Troubleshooting

Common Issues

Problem: VM name too long for Azure limits

Resolution: Use abbreviated purpose codes (max 3 characters)

Problem: Conflicting names between environments

Resolution: Verify environment code matches actual deployment

Problem: Epic-specific naming conflicts

Resolution: Coordinate with Epic team for stamp-specific naming

Validation Commands

# PowerShell validation script
function Test-OHEMRVMName {
    param([string]$VMName)

    if ($VMName -match "^[ZAGOP][ECW][PNDR][WL][A-Z]{2,3}[A-Z]{2,3}[0-9]{3}$") {
        Write-Output "✅ Valid OHEMR VM name: $VMName"
        return $true
    } else {
        Write-Output "❌ Invalid OHEMR VM name: $VMName"
        return $false
    }
}

---

🔗 Related Documentation

• Security Guidelines: Security controls and compliance requirements
• Operations Procedures: Day-to-day operations and maintenance
• Epic Architecture Requirements: Epic-specific infrastructure standards

---

📞 Support & Contacts

Naming Approval Process

Emergency Contacts

• Epic Production Issues: [email protected]
• Infrastructure Emergency: [email protected]
• Naming Conflicts: [email protected]

---

🏷️ Naming Excellence: Consistent VM naming enables efficient healthcare infrastructure management and rapid incident response.