In the Pega Care Management portals, you can search for patients and view their details. Supported criteria include first name, last name, and the patient ID. The elastic search is used to retrieve the data based on the member ID and enables you to load the Patient 360 view, which is the review harness of PegaHC-Care-Work-Member class.
The D_PatientSearchResults data page holds the retrieved results. For each PegaHC-Data-Party-Member instance, a corresponding case is created in the application. The pyCustomer property contains the member ID. This property is used to associate a member case with a member instance. The member case references the patient data through an auto-referenced property, which loads the data by using the D_Member data page.
Because look-up data pages do not support dynamic class referencing, you need to save the D_Member rule in the appropriate implementation-layer class context so that the data page can fetch the implementation-layer specific data. Otherwise, the look-up fails and the data page does not return any data.