Patient and Member searches in Pega Care Management

In the Pega Care Management™ portals, depending on how your organization's application perspective is set, you can search for patients or members and view their details. Supported search criteria include first name, last name, and patient/member ID. Elastic search is used to retrieve data based on the member ID and enables you to load the Patient 360 view, which is the review harness of the PegaHC-Care-Work-Member case.

As shown in the figure above, the D_PatientSearchResults data page holds the retrieved results. The Member ID link in the search results section enables the user to load the Patient 360 view, which is the review harness of the PegaHC-Care-Work-Member case. 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.

The following figure shows an example of the D_PatientSearchResults data page for member data by the member ID. 

Check your knowledge with the following interaction: