Care Management - Deploying and Using Declarative Pages
The Care Management Framework uses declarative pages to derive the benefits of easy deployment, improved performance, and reduction in memory requirements when multiple users of the application need to access static or slowly changing information at the same time.
The Declarative Page and Activity
At the thread level, the Declare Pages instance Declare_CM_ENV, loads the activity LOAD_CM_ENV.
Both rules are defined in the PegaClinical_CNFG RuleSet. Each step in the activity uses the Property-Set method to map commonly referenced data values into the Declare_CM_ENV page of the clipboard when a user signs in.
For more information about how declarative pages are configured and work, see the online help topic: About Declare Pages rules.
Declare Pages Instance
Load Activity
Configuration Tips
The declarative page cannot be copied to a different RuleSet, but it can be versioned if necessary. Since the content of the clipboard page is not changed in production, the configuration you implement in the declarative page (expiration settings for example) is identical for every user of the framework on the same node.
However, the LOAD_CM_ENV activity that populates the declarative page can be modified to meet your processing requirements.
Deployment of this functionality is simple for both work and organization-centric approaches. Because the declarative page is managed by a thread level page every user that signs into the framework can have their version of the page. To do this, deploy the activity LOAD_CM_ENV to the RuleSet that is unique to the group the user belongs to.
Default Property Settings
The following table lists the name, default values, and describes the properties that are set by the load activity when the framework is installed:
Property Name | Default Value | Description |
|---|---|---|
CM_RULESET | PegaCareTemplates | Template rule set name |
CM_RULESET_VERSION | 01-01-01 | Template rule set version |
RESET_TODAY | YES | If set to YES today’s date will reset be to RESET TODAY DATE. Use for testing with older data sources during implementation. No OOTB implementation. |
RESET_TODAY_DATE | 20060929 | Example: 20060929 |
CM_WORKPOOL_CLASS | PegaHC-Care-Work | Work Pool Class |
CM_WORKPOOL | PEGAHC-CARE-WORK | Work Pool |
ALERT_WORK_CLASS | PegaHC-Care-Work-Alert | Alert work class |
ASSESSMENT_WORK_CLASS | PegaHC-Care-Work-Assessment | Assessment work class |
CAREPLAN_WORK_CLASS | PegaHC-Care-Work-CarePlan | CarePlan work class |
CASE_WORK_CLASS | PegaHC-Care-Work-Case | Case work class |
GOAL_WORK_CLASS | PegaHC-Care-Work-Goal | Goal work class |
TASK_WORK_CLASS | PegaHC-Care-Work-Task | Task work class |
CAMPAIGN_WORK_CLASS | PegaHC-Care-Work-Campaign | Campaign work class |
CM_CAREPLAN_WORKBASKET | CarePlan@MyHealthPlan | Holds active care plans |
CM_GOAL_WORKBASKET | Goals@MyHealthPlan | Holds active goals |
CM_ALERT_WORKBASKET | Alerts@MyHealthPlan | Holds active alerts |
CM_DEFAULT_WORKBASKET | DiseaseManagement@MyHealthPlan | Default |
CM_FULFILLMENT_WORKBASKET | CM_Fulfillment@MyHealthPlan | Fulfillment work basket |
ALERT_WORK_MODEL | AlertWorkDefault | Model for new work of type alert |
ASSESSMENT_WORK_MODEL | AssessmentWorkDefault | Model for new work of type assessment |
CAREPLAN_WORK_MODEL | CarePlanWorkDefault | Model for new work of type care plan |
CASE_WORK_MODEL | CaseWorkDefault | Model for new work of type case |
GOAL_WORK_MODEL | GoalWorkDefault | Model for new work of type goal |
TASK_WORK_MODEL | TaskWorkDefault | Model for new work of type task |
ALERT_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-Alert | Alert wizard class |
CAREPLAN_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-CarePlan | Care Plan wizard class |
GOAL_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-Goal | Goal wizard class |
TASK_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-Task | Task wizard class |
DATASOURCE_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-DataSource | Data source wizard class |
MATERIALS_ACCEL_CLASS | PegaHC-Care-Work-CareAccel-Materials | Materials wizard class |
ALERT_RULE_CLASS | Rule-PegaCare-Alert | Alert template class |
CAREPLAN_RULE_CLASS | Rule-PegaCare-CarePlan | Care Plan template class |
DATASOURCE_RULE_CLASS | Rule-PegaCare-DataSource | Data source template class |
GOAL_RULE_CLASS | Rule-PegaCare-Goal | Goal template class |
TASK_RULE_CLASS | Rule-PegaCare-Task | Task template class |
QUESTIONNAIRE_RULE_CLASS | Rule-PegaQ-Questionnaire | Questionnaire rule class |
MATERIALS_RULE_CLASS | Rule-File-Binary | Materials template class |
PATIENT_DATA_CLASS | PegaHC-Data-Party-Member | Patient data class |
PCP_DATA_CLASS | PegaHC-Data-Party-Provider | PCP data class |
DATA_CONV_NOTES_CLASS | PegaHC-Data-ConversationLog | Note data class |
CODEGROUP_DATA_CLASS | PegaHC-Data-CodeGroup | Code group data class |
NDC_DATA_CLASS | PegaHC-Data-NDCCodes | NDC data class |
CPT_DATA_CLASS | PegaHC-Data-CPTCodes | CPT data class |
HCPCS_DATA_CLASS | PegaHC-Data-HCPCSCodes | HCPCS data class |
ICD9_DATA_CLASS | PegaHC-Data-Diagnosis | ICD9 data class |
PROVIDER_DATA_CLASS | PegaHC-Data-Party-Provider | Provider data class |
CLAIMS_DATA_CLASS | PegaHC-Data-Claim | Claim data class |
AUTHORIZATION_DATA_CLASS | PegaHC-Data-Authorization | Authorization data class |
POLICY_DATA_CLASS | PegaHC-Data-Policy | Policy data class |
CARE_CORR_CLASS | Rule-Obj-Corr-CM | Correspondence data class |
HCPCS_DATA_REP_REC_SIZE | 500 | Result set size in Code search |
CPT_DATA_REP_REC_SIZE | 500 | Result set size in Code search |
NDC_DATA_REP_REC_SIZE | 500 | Result set size in Code search |
ICD9_DATA_REP_REC_SIZE | 500 | Result set size in Code search |
ALERT_PROC_VERSION | 1.0 | Alert processor version |
ALERT_FORCE_RUNALL | YES | If set to YES processing of the alert will continue even if the alert has already been processed on the same day. Use this for testing during deployment. |
DATASOURCE_AUTH_CLASS | PegaHC-Data-Authorization | Not implemented |
DATASOURCE_MEDICALCLAIM_CLASS | PegaHC-Data-Claim | Medical claim data class |
DATASOURCE_PHARMACYCLAIM_CLASS | PegaHC-Data-Claim | Pharmacy claim data class |
DATASOURCE_CODEFILTER | NO | If set to NO matching based on the codes configured in the alert occurs in getMatch. If set to YES, no matching will occurr and buildMatchResultPage needs to get implemented to convert the resultset from the data source query into the expected format which may include custom matching procedures. |
DATASOURCE_DATEFILTER | NO | Not implemented |
DATASOURCE_MEDICALCLAIM_CLASS_ID | ClaimID | Property name of medical claim ID. Used for reporting matching events |
DATASOURCE_PHARMACYCLAIM_CLASS_ID | ClaimID | Property name of pharmacy claim ID. Used for reporting matching events |
ALERTSLA_DEADLINE_DEFAULT | 2 | Off set for deadline date from goal date |
TASKSLA_DEADLINE_DEFAULT | 2 | Off set for deadline date from goal date |
TASK_STATUS_RUNNING | Pending | Status after work item has been activated |
CAREPLAN_STATUS_RUNNING | Pending | Status after work item has been activated |
ALERT_STATUS_RUNNING | Pending | Status after work item has been activated. Only alerts with this status will be considered for processing. |
GOAL_STATUS_RUNNING | Pending | Status after work item has been activated |
TASK_PENDING_FULFILL_STATUS | Pending-FulFillment | Status after work item has been activated |
TASK_STATUS_DORMANT | Open | Status of work item after parent alert has been activated. Only goals with this status will be considered for processing after parent alert has fired. |
GOAL_STATUS_DORMANT | Open | Status of work item after parent alert has been activated. Only tasks with this status will be considered for processing after parent alert has fired. |
FLOW_NEW_WORK | NewWork | To create a new work item |
FLOW_CREATE_CASE | CreateCase | To create a new case |
NAVIGATION_STYLE | text | No other OOTB implementation |
TIMELINE_OFFSET_DAYS | 180 | Evaluated in getCaseTimeLine activity to artificially curtail timeline after x days if greater than zero |
INITIAL_CASE_TASK1 | Schedule_Call_Test | Not implemented |
INITIAL_CASE_TASK2 | Schedule_Call_Test | Not implemented |
INITIAL_CASE_TASK3 | Schedule_Call_Test | Not implemented |
POPULATION_TASK_FULFILLMENT | Send_Fulfillment | Used for testing only |
DEFAULT_CAMPAIGN | General | If member if not part of any population this value is used instead |
FULFILLMENT_PROVIDER | CARD1 | Used for testing only |
Return to About the Care Management Framework