Configuring elements on the patient timeline in Care Management
Configuring elements on the patient timeline in Care Management
Pega Care Management is built on top of Pega Customer Service for Healthcare (CSHC). CSHC offers a patient timeline as part of a core CRM feature. For more information, see Timeline view of customer events. Pega Care Management inherits this timeline and extends it to show care management activities on the timeline. This design pattern describes how you can update the timeline for Pega Care Management.
Out-of-the-box, Pega Care Management includes timeline events for the following activities:
- Admissions
- Program referral
- Visits, authorizations
- Tasks
- Case conferences
- Medication Therapy Management reviews
Use case examples
Two primary use cases involve the following scenarios:
- A client wants to add data elements to the timeline.
- A client wants to remove elements from the timeline.
You can accomplish both of these use cases by updating the Care Management Configuration page.
Before you begin
Before updating the Patient 360 timeline, review the following topics topics in the implementation guides:
- Timeline view of customer events in the Pega Customer Service for Healthcare Implementation Guide.
- Information about the patient timeline and extensions in the Configuration and details for the History tab in the Pega Care Management Implementation Guide.
Updating the patient timeline
After you review the topics, update your patient timeline:
- Confirm that the when rule for personas is up-to-date. For more information, see Configuring access to the patient timeline in the Configuration and details for the History tab.
- Update the Patient Events tab on the configuration page. The timeline component is built for the display historical events. Any changes that you make in the configured properties of the respective service cases or data instances are not reflected in the timeline component.
In PCM, declare triggers are used to create events. If you are using decision nodes, the EventDetails data transform is used to populate the case/data instance date to the data store event page.
3. For the new service cases or data instances that are added in the configuration page, to create timeline events (Cassandra data store events), call the CaptureEventWrapper activity in the create flow.
4. If decision nodes are not enabled, the component displays the events based on relevant class instances. For any data instances that are added to the configuration page, add the relevant logic to the FetchInteractionsForContactExt activity which is used for rendering care events.
Results
- Developers can update the events that are available on the Care Management timeline.
- Users can select the updated events on the patient timeline.