Difference between revisions of "Extending portals to enhance the claims processing experience"

From PegaWiki
Jump to navigation Jump to search
(Initial draft)
Tag: Visual edit
 
(Request for publishing.)
Tag: Visual edit
Line 1: Line 1:
 
{{New request
 
{{New request
|Request to Publish=
+
|Request to Publish=Yes
 
|Curator Assigned=
 
|Curator Assigned=
 
|Description=Concepts and considerations for extending claim processing portals.
 
|Description=Concepts and considerations for extending claim processing portals.
Line 18: Line 18:
 
SCE Portals are interfaces supplied with the application. The include common roles associated with claims processing systems. Common examples are business analyst, claims examiner, claims manager, and system manager. Review the SCE user guide for a more complete listing of portals and available features of each.
 
SCE Portals are interfaces supplied with the application. The include common roles associated with claims processing systems. Common examples are business analyst, claims examiner, claims manager, and system manager. Review the SCE user guide for a more complete listing of portals and available features of each.
  
Each portal provides access to features supporting the role common to processing systems. There is overlap between features, menu items, and functionality between portals. Careful consideration is given to features available in each portal but there they may not cover all business needs. SCE portals come with extension points to support custom user interface requirements.  
+
Each portal provides access to features supporting the role common to processing systems. There is overlap between features, menu items, and functionality between portals. Careful consideration is given to features available in each portal but there they may not cover all business needs. Content can be customized to display any data integrated into the application. SCE portals come with extension points to support custom user interface requirements.  
  
 
== Key considerations ==
 
== Key considerations ==
 
Always use predefined extension points when available. This reduces impact during upgrade.  
 
Always use predefined extension points when available. This reduces impact during upgrade.  
  
Use the screen space to maximum effect by focusing on the information required to do the task at hand. Too much or too little information will reduce productivity.
+
Use the screen space to maximum effect by focusing on the information required to complete the task at hand. Too much information may slow the screen performance or overwhelm the end user. Too little information will require the user look to external sources slowing productivity.  
  
Extension points for specific interface screens can be found by browsing the live UI. Review the implementation guide for detailed instructions.  
+
Review content of the included portals as a starting point. Sections can be added but the recommended approach is to update the extension sections with additional properties. 
 +
 
 +
Extension points for specific interface screens can be found by browsing the live UI. Review the implementation guide for additional instructions.  
 
[[File:Portal UI Image.png|none|thumb]]
 
[[File:Portal UI Image.png|none|thumb]]
 
Rules overridden in the implementation layer will take precedent over updated product rules. Review release notes to identify when new enhancements can be used in lieu of carrying forward custom code.  
 
Rules overridden in the implementation layer will take precedent over updated product rules. Review release notes to identify when new enhancements can be used in lieu of carrying forward custom code.  
  
== Use case example ==
+
== Reference materials on Community ==
...
+
[https://community.pega.com/knowledgebase/articles/pega-smart-claims-engine-healthcare-implementation-guide/85/extending-your-application Extending the application]
  
== Reference materials on Community ==
+
[https://community.pega.com/knowledgebase/documents/pega-smart-claims-engine-healthcare-85-user-guide SCE user guide]
...
 

Revision as of 00:19, 25 January 2021


Curator Assigned
Request to Publish Yes
Description Concepts and considerations for extending claim processing portals.
Version as of 8.5
Application Smart Claims Engine
Capability/Industry Area Healthcare

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.

When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Definition and concept[edit]

SCE Portals are interfaces supplied with the application. The include common roles associated with claims processing systems. Common examples are business analyst, claims examiner, claims manager, and system manager. Review the SCE user guide for a more complete listing of portals and available features of each.

Each portal provides access to features supporting the role common to processing systems. There is overlap between features, menu items, and functionality between portals. Careful consideration is given to features available in each portal but there they may not cover all business needs. Content can be customized to display any data integrated into the application. SCE portals come with extension points to support custom user interface requirements.

Key considerations[edit]

Always use predefined extension points when available. This reduces impact during upgrade.

Use the screen space to maximum effect by focusing on the information required to complete the task at hand. Too much information may slow the screen performance or overwhelm the end user. Too little information will require the user look to external sources slowing productivity.

Review content of the included portals as a starting point. Sections can be added but the recommended approach is to update the extension sections with additional properties.

Extension points for specific interface screens can be found by browsing the live UI. Review the implementation guide for additional instructions.

Portal UI Image.png

Rules overridden in the implementation layer will take precedent over updated product rules. Review release notes to identify when new enhancements can be used in lieu of carrying forward custom code.

Reference materials on Community[edit]

Extending the application

SCE user guide