Pegasystems Certified Lead System Architect (CLSA) PEGACPLSA23V1 Question # 12 Topic 2 Discussion

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s data modeling and case management principles, as outlined in Pega Academy’sCase DesignandData Modeling Mission, emphasize storing and propagating data within case hierarchies to ensure consistency and accessibility. The goal is to maintain a single source of truth for critical data, such as patient details, and make it available to related processes efficiently.

Option A (Incorrect): Pre-loading patient data for each appointment or treatment based on initial consultation outcomes is inefficient and error-prone. It risks data inconsistency if the initial data changes, and Pega does not natively support “pre-loading” as a standard mechanism for case data management, per theData Modelingguidelines.

Option B (Incorrect): The snapshot data access pattern is used to capture a point-in-time view of data, typically for reporting or auditing, not for ongoing access to current data. Using it for appointments and treatments would not ensure data currency, which is critical for patient management, as noted in theData Access Patternsmodule.

Option C (Correct): Storing patient data within Consultation cases and using data propagation to transfer it to subsequent appointment or treatment cases is the optimal solution. Pega’s case management supports data propagation from parent to child cases or across related cases, ensuring that patient details remain current and accessible. This aligns with Pega’s best practices for case-centric data management, as described in theCase Design Mission.

Option D (Incorrect): The System of Record (SOR) data access pattern involves retrieving data directly from an external system, which may introduce latency and dependency issues. While SOR is useful for integrations, it’s less suitable for managing case-specific data like patient details, which should be stored within the Pega application for performance and consistency, per theIntegrationmodule.