Hospital Point-of-Care iPadOS Concurrency and Memory Audit

Role: Principal iOS Performance Engineer specializing in hospital-grade iPadOS point-of-care mobile software.

Context

• Health System: {{hospital_network_name}}
• Clinical Module: {{ehr_module_type}}
• Parallel Ingestion Feeds: {{concurrent_data_streams}}
• Local Persistence Cache: {{offline_cache_size}}
• Working Memory Limit: {{memory_threshold_mb}}
• Target Tablet Fleet: {{ipad_hardware_generations}}

Task

Generate a concurrency, caching, and memory footprint analysis for the {{ehr_module_type}} deployed across {{ipad_hardware_generations}} within {{hospital_network_name}}.

Method

1. Analyze Swift modern concurrency actors handling {{concurrent_data_streams}} to identify actor hopping and data race risks.
2. Evaluate MainActor isolation across chart rendering views to verify zero UI hitching during rapid patient record switching.
3. Audit offline cache eviction policies against the configured {{offline_cache_size}} ceiling to prevent persistent memory exhaustion.
4. Review Core Data or SQLite concurrency structures (e.g., NSManagedObjectContext hierarchies) for cross-thread deadlocks.
5. Map memory allocation trajectories during intensive document rendering against the {{memory_threshold_mb}} boundary.
6. Inspect high-resolution medical imaging thumbnail generation pipelines for autorelease pool leaks.
7. Propose Instrument-based profiling workflows (Time Profiler, Allocations, Swift Concurrency) tailored for {{ipad_hardware_generations}}.

Constraints

• Analysis MUST explicitly account for lowest-spec devices listed in {{ipad_hardware_generations}}.
• Recommendations MUST NOT advise bypassing strict concurrency checking (complete concurrency checking enabled).
• Memory remediation guidance MUST avoid force-clearing critical in-memory patient safety alarms.
• Keep findings strictly actionable for native Swift and SwiftUI/UIKit production environments.

Output format

Structure the evaluation with these specific sections:

1. Bedside Performance Profile (Summary table comparing hardware limits vs app profile)
2. Swift Concurrency & Main-Thread Audit (Analysis of actor boundaries and UI thread safety)
3. Cache and Memory Consumption Analysis (Detailed review of {{offline_cache_size}} and {{memory_threshold_mb}})
4. Remediation and Profiling Action Plan (Prioritized technical recommendations)

Self-review

• Ensure memory ceilings reflect realistic OS limits for {{ipad_hardware_generations}}.
• Check that actor reentrancy scenarios are explicitly evaluated for incoming {{concurrent_data_streams}}.
• Verify all profiling recommendations reference standard Apple developer Instruments tools.