Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Step 6: Customize the user experience

Updated on May 18, 2016

While Care Management Application is fully functional immediately upon installation, you will want to change portions of the user experience (UX) to meet the needs of the users at your site.

Follow these steps to design the user experience:

  1. Design the portals.
  2. Design application skins.
  3. Design for screen performance.

Designing the portals

Review the content of the Service Manager, and Business Analyst portals to ensure that only relevant data is presented.

  1. Log in to the application using the following credentials:

User Name: CMSysAdmin@MyHealthPlan

Password: install

  1. From the Launch menu, select CM Care Manager Portal.
  2. Review each of the portal sections:
    • Dashboard
    • My Reports
    • Manager Tools
    • Pulse
  1. Record your decision in the Portals planning worksheet.
  2. Repeat this process for the Service Manager portal.

Designing application skin and styles

Your site very likely has standards for the appearance of your application. Your task is to determine which styles have to change to adhere to those standards.

  1. Click Designer Studio > User Interface > Skins & Portals.
  2. On the Skins tab, double-click the pyEndUser71 skin.
  3. Click the Component Styles tab.
  4. Review each component.
  5. Record your decision in the Skinning planning worksheet.
As you are planning your application styles, you want to consider using mixin to provide incremental style changes. For more information, read the article Using mixins in the skin to drive consistency and efficiency.

 

Designing for screen performance

You want your application to respond immediately as your end users interact with customers. As you design your user interface, determine:

  1. Which business service level agreements exist. For example, the customer details must be available in one second or less while a representative is on the phone with the customer.
  2. How long it takes backend systems to gather the data needed to display customer details.
  3. Which fields the representatives absolutely need for the task that they need to perform.
  4. If any network configuration could cause latency; for example, if there are representatives logged in through a corporate VPN or in a remote location.
  • Previous topic Step 5: Define the security model and organization structure
  • Next topic Step 7: Define the Care Management Application components

Tags

System Architect Lead System Architect Healthcare and Life Sciences

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us