CR: AthenaPractice Datacenter Migration
Jira: HM-8461 Status: Completed Executed: 2026-03-26 Owner: Leon Geldenhuys Risk: LOW | Estimate: 3 story points
Summary
AthenaPractice migrated their data center on March 26, 2026. This potentially affected any eSHARS integration points connecting to AthenaPractice services (SFTP, login URLs, API endpoints). A full audit found no hardcoded references to AthenaPractice in any eSHARS repository — all connection details are database-stored or managed in Azure Portal.
Result: No code changes or deployments were required. Purely operational.
Audit Results
Code Repositories
| Repo | References Found |
|---|---|
| HISD (main app) | None |
| eshars-devops | None |
| eshars-mobile-api | None |
| eshars-mobile-ui | None |
| All other repos | None |
Search terms: athena, athenaPractice, athenahealth, cloudcent, 208.78
SFTP Integration
SFTP hostnames are database-stored via GetDistrictValue<string>() in:
| Settings Class | DB Key |
|---|---|
DistrictFileProcessorSettings | SFTP Host Name (District File Processor) |
LogFileManagementSettings | SFTP Host Name |
SuccessEdSettings | SFTP Host Name (SuccessED) |
EdiCategorySettings | Billing Transaction SFtp HostName, TMHP Imported files SFTP Host Name |
Infrastructure-as-Code
No AthenaPractice IPs found in any Bicep or Terraform files. NSG rules, SQL firewall rules, and App Service IP restrictions are managed directly in Azure Portal (not in IaC).
Scope
| Resource | Change | Result |
|---|---|---|
DB: GlobalSetting — SFTP hostnames | UPDATE if hostname changed | Verified / updated as needed |
| NSG rules | Remove old IPs, add new 208.78.143.0/24 | Audited and updated |
| VPN configuration | Update AthenaPractice peer IP to 208.78.143.253 | Updated |
| BillTransactionJob triggers | Pause before migration, resume after confirmation | Completed |
New AthenaPractice Endpoints
| Item | Value |
|---|---|
| Login URL | cloudcent.athenahealth.com |
| IP Range | 208.78.143.0/24 |
| Specific IP | 208.78.140.115/32 |
| VPN Peer IP | 208.78.143.253 |
Procedure Executed
Phase 1: Pre-Migration
- Audited all NSG rules, SQL firewall rules, App Service restrictions for old AthenaPractice IPs
- Ran
01-audit-nsg-rules.ps1fromeshars-ops/scripts/athena-migration/ - Identified districts using AthenaPractice SFTP via DB query
- Prepared UPDATE statements for new SFTP hostname
- Completed attestation form to AthenaPractice
- Communicated timeline to Akhil/Kisha/Luis
Phase 2: Migration Day (March 26)
- Paused BillTransactionJob triggers at 2:00 PM CDT (see Job Scheduler: Pause & Resume)
- Executed DB SFTP hostname updates
- Updated NSG rules with new IP range
- Updated VPN configuration
- Resumed BillTransactionJob triggers after Luis confirmed visits flowing to new endpoint
- Monitored first execution of each job
Phase 3: Post-Migration
- Verified SFTP connectivity to new AthenaPractice endpoints
- Confirmed login URL works
- Monitored job logs — no errors related to AthenaPractice connectivity
- Closed HM-8461
Outcome
Executed: 2026-03-26
Result: Success — no issues. AthenaPractice DNS hostname (apsftp.athenahealth.com) was updated by AthenaPractice to point to the new data center, so the SFTP hostname in the database required no changes. NSG rule updates were applied, VPN config updated.
Notes: The pre-migration audit scripts (01-audit-nsg-rules.ps1, 02-migrate-athena-ips.ps1) are in eshars-ops/scripts/athena-migration/ for reference if a similar migration occurs in future.