Ideas2IT Diagnosed and Stabilized a Behavioral Health EHR Generating Recurring Critical Incidents and Built the Roadmap That Cleared Its Path to AWS

Full-Stack Assessment: Mapping Every Bottleneck Before Any Fix Was Attempted

The first decision was diagnostic: assess the entire stack before scoping any remediation. Ideas2IT analyzed CPU utilization patterns across 20 application containers using New Relic telemetry, identifying the spike behavior that had been triggering manual restarts.

Oracle AWR reports surfaced the database-layer problems: DBMS_SCHEDULER jobs running throughout the day, high log file sync wait times across database servers, elevated parse SQL counts indicating the need for query tuning, and claim engine jobs requiring further analysis.

The connection pool gap was confirmed: the platform had no pooling configured, and session connect and disconnect cycles were consuming 15.04% of total database activity. The UI audit identified 3,023 elements with excessive DOM size, render-blocking JavaScript, inefficient static asset caching across 79 resources, missing image dimensions causing layout reflow, and broken screen flows generating 404, 401, and 5xx errors.

This Phase Produced

• Infrastructure configuration analysis across compute, OS, DB, and load balancer ·
• Oracle AWR database assessment ·
• CPU utilization spike analysis across 20 application containers ·
• Connection pool gap analysis ·
• UI assessment covering DOM size, static asset caching, render-blocking JS, and screen flow errors ·
• Batch job performance analysis

Performance Remediation: Closing the Gaps That Were Generating Incidents

Remediation followed the assessment findings in order of confirmed impact. Tomcat JDBC connection pooling was introduced, eliminating the session churn that had consumed 15.04% of total database activity.

Appointment scheduling and record fetching were rebuilt with parallel processing, and CDC-based event-driven sync replaced the sequential data operations that had been compressing batch processing windows.

Hibernate ORM was optimized alongside data processing logic, the JDK was upgraded to the latest version, and Oracle Procedures were revised to use the oracle_loader driver for XML processing, resolving the claim engine performance issues identified in the AWR assessment.

On the frontend, full-page reloads were replaced with dynamic loading for EMAR and other high-traffic screens, static asset caching was corrected, and DOM structure was reduced to eliminate the layout reflow behavior caused by missing image dimensions.

This Phase Produced

• Tomcat JDBC connection pool configuration ·
• Parallel processing for appointment scheduling and record fetching ·
• Event-driven CDC for data sync ·
• Hibernate ORM and data processing logic optimization ·
• JDK upgrade ·
• Oracle Procedures revised for oracle_loader XML processing ·
• Dynamic loading implementation replacing full-page reload patterns ·
• Static asset caching and DOM optimization

Cloud Readiness and Migration Roadmap: Building the Path to AWS

With the platform stable, Ideas2IT assessed CareLogic's readiness for cloud migration. The assessment covered the full architecture: compute, database, network and security, and storage layers, mapped against the requirements of a HIPAA-compliant AWS deployment.

Gap analysis identified what needed to change between the current on-premises architecture and the AWS target state.

The output was a sequenced migration roadmap that gave the Qualifacts engineering team a structured, compliance-aware path to AWS, designed to move a platform serving live behavioral health organizations without disrupting the clinical operations running on it.

This Phase Produced

• Cloud readiness assessment
• Architecture gap analysis
• AWS target-state architectural recommendation
• Sequenced cloud migration roadmap