Skip to main content

Personal Community Mobile Application Product Guide





1. Overview

Personal Community is designed with a mobile-first approach , providing a responsive patient experience across devices. Organizations can choose how to deliver that experience to their patients based on their engagement strategy and the needs of their patient population.

Personal Community is by default installed as a  web application , allowing patients to access their care through a supported browser. Additionally, organizations can choose to deploy Personal Community as a mobile application distributed through the Apple App Store and Google Play Store. Organizations may use the deployment option that best supports how their patients access digital services and engage with their care.

For organizations choosing a mobile application deployment, the responsive Personal Community application is packaged for iOS and Android while maintaining the core functionality and configuration of the Personal Community experience. This provides patients with a familiar app-based experience and allows for supported native mobile capabilities, such as push notifications.

Each organization builds and publishes its own Personal Community mobile application, allowing it to maintain its own application identity, branding, app store presence, and mobile services while leveraging the standard Personal Community mobile framework.

2. Mobile Application Deployment Considerations

Organizations choosing to offer Personal Community as a mobile application should plan for additional activities beyond a standard web deployment.

These include:

  • Building the iOS and Android applications
  • Establishing and maintaining the required Apple and Google developer accounts
  • Configuring organization-specific application identifiers and credentials
  • Publishing and maintaining the application in the appropriate app stores
  • Rebuilding and republishing the application as part of Personal Community upgrades
  • Configuring and maintaining additional mobile services, such as push notifications, when implemented

The organization and implementation team should agree on ownership of these activities as part of deployment planning.

3. Push Notification Considerations

Organizations implementing push notifications require additional mobile platform configuration.

Push notifications use the native notification services provided for iOS and Android. Because each organization owns and publishes its own Personal Community mobile application, the associated notification services and credentials are also specific to that organization's application deployment.

The customer and implementation team should determine responsibility for creating and maintaining the required Firebase project and related mobile notification configuration before enabling push notifications.

4. Business Decisions

Organizations considering a Personal Community mobile deployment should determine:

Mobile Application Deployment
Whether Personal Community will be offered as a mobile application in addition to the responsive web experience.

App Store Ownership
Who will own and maintain the Apple and Google developer accounts and manage ongoing app store submissions.

Push Notifications
Whether push notifications will be implemented.

Who will own and maintain the associated Firebase project and mobile notification credentials.






FeedbackOpens in a new tab