Hospital Bedside iPad Security and Local Data Governance Framework

Role: Lead iOS Security and Privacy Architect specializing in acute care hospital deployments.

Context

• EHR Integration Partner: {{ehr_system_provider}}
• Target FHIR Resources: {{fhir_resource_types}}
• Network Environment: {{hospital_network_security}}
• Clinical User Roles: {{user_role_hierarchy}}
• Local Storage Policy: {{local_storage_policy}}

Task

Establish a comprehensive iOS sandbox security and local data governance framework that protects {{fhir_resource_types}} when accessed via {{ehr_system_provider}} across multi-user ward workflows.

Method

1. Define Secure Enclave-backed key generation routines for encrypting local SQLite/CoreData stores.
2. Design biometric authentication (Face ID/Touch ID) workflows paired with role authorization for {{user_role_hierarchy}}.
3. Establish session termination and cache eviction triggers based on device lock, inactivity, and ward transition.
4. Map App Transport Security (ATS) exceptions and certificate pinning strategies for {{hospital_network_security}}.
5. Structure temporary memory handling to prevent {{fhir_resource_types}} leaking into iOS crash reports or snapshots.
6. Specify Data Protection class assignments (NSFileProtectionComplete) across all app container directories.
7. Detail secure inter-app communication boundaries preventing unapproved URL scheme triggers or pasteboard sharing.

Constraints

• MUST enforce NSFileProtectionComplete on every file containing clinical records or patient identifiers.
• MUST clear all in-memory patient data within 1 second of app backgrounding.
• MUST NOT store authentication tokens or API secrets in standard UserDefaults or unencrypted plists.
• Keep all authentication flows compatible with Managed Apple IDs and Shared iPad configuration profiles.

Output format

Generate the governance framework formatted under the following headings:

1. Sandboxing & Enclave Architecture (Key management, Keychain accessibility classes)
2. Session Lifecycle & Purge Policy (Matrix of triggers, timeouts, and memory-clearing rules)
3. Network Boundary & Certificate Protocol (TLS pinning, proxy traversal for {{hospital_network_security}})
4. Role-Based Access Control Spec (Role mapping for {{user_role_hierarchy}} to {{fhir_resource_types}})

Self-review

• Verify that the memory eviction protocol specifically covers {{fhir_resource_types}}.
• Check that the session purge triggers account for Shared iPad workflows and {{local_storage_policy}}.
• Validate that all cryptographic recommendations strictly utilize native iOS CryptoKit and Keychain APIs.