[Data Modeling] In a hospital's patient management Pega application, patient details are gathered during the initial consultation process. This…

The scenario requires patient data to be centrally managed, consistently up-to-date, and accessible by multiple, independent case types (appointments, treatments). The System of Record (SOR) data access pattern is the correct Pega design for this requirement. This pattern, often implemented using data pages, ensures that all processes reference a single, authoritative source for patient data. By fetching data on-demand from the SOR, the application guarantees that the information displayed and used in any process is always the most current version, avoiding the data staleness and integrity issues associated with copying data.

A: Pre-loading data creates a copy that will not update if the original patient record changes, failing the requirement for the data to remain "current."

B: The snapshot pattern is explicitly designed to copy data at a specific point in time, which is the opposite of the requirement to have continuously current information.

C: Storing master data (Patient) within a transactional case (Consultation) is a poor architectural choice. Data propagation also copies data, leading to stale information in child cases.

1. Pega Academy

Lead System Architect (23) Mission

"Data and Integration" Module

"Data virtualization" Lesson. This lesson contrasts the two primary data virtualization patterns. It explicitly states that the "Reference" pattern (SOR pattern) should be used when data must be up-to-date

while the "Copy" pattern (Snapshot) is for data that is valid at a specific point in time. The hospital scenario clearly requires the former.

2. Pega Documentation

"Data Pages

" Section: "Data page definition." This documentation describes how data pages are the primary mechanism for implementing data access patterns. For an SOR pattern

a data page is configured to source data from the appropriate system (e.g.

a patient database table) and can be set with a refresh strategy to ensure the data remains current whenever accessed.

3. Pega Documentation

"Data access patterns

" Section: "System of Record (SOR) pattern." This section defines the SOR pattern as the practice of accessing data directly from the source where it is maintained. It highlights the key benefit as ensuring data is always current and accurate

which directly addresses the core requirement of the question.