Patient portal access
MSK MyChart is designed around patient portal access for people connected with Memorial Sloan Kettering services. A health portal can support appointments, messages, results, care-team communication, and account-based medical workflows.
Because this kind of app handles sensitive health information, users should make sure they are on the right device and understand the login process before entering credentials. Shared phones need extra care around notifications and saved sessions.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Protected onboarding flow
The visible launch path reached a protected pre-login or onboarding area that did not allow screen capture. That restriction is common in health apps because medical information, identity details, or portal setup screens can be sensitive.
The restriction limits what can be previewed from the package, but it also signals that privacy protection may be active in the interface. Users should proceed through onboarding only when they are ready to review patient portal terms and account security.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Health, device, and notification permissions
The package declares location, camera, microphone, phone, health and fitness data, Bluetooth, alarms and reminders, notifications, biometric access, storage, foreground services, and network behavior. These can support appointments, calls, telehealth-style features, device connections, reminders, and secure login.
Grant each permission only when a portal feature clearly needs it. Medical apps deserve a stricter review because notifications, microphone access, health data, and location may reveal sensitive personal context.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
