To customize the out-of-the-box advanced Patient Card in Health Cloud, a developer must follow the standard procedure for modifying managed OmniStudio components. The first step is to clone the parent FlexCard (HealthCloudPatientCardParent) to create a customizable version, ensuring the original remains intact for future upgrades. Next, a DataRaptor Extract is required to query the ClinicalAlertc object, filtering for active records and retrieving the specified fields (Category, SubjectID, Date). Finally, a new child FlexCard must be created to display this data, configured to use the new DataRaptor as its data source, and then activated so it becomes visible within the cloned parent card.

D. Define session variables to control visibility of clinical data.

Session variables are not the primary mechanism for filtering data records; this logic is correctly handled within the DataRaptor's query filters.

E. Change the child card state to show active.

Activating the card itself makes it visible. A card's "state" is for defining different layouts or conditional UI displays, not for the initial data filtering.

1. Salesforce Health Cloud Developer Guide: Customize the Advanced Patient Card

Reference: The guide explicitly states, "To customize the patient card, first clone the HealthCloudPatientCardParent FlexCard." It then details adding child cards and configuring their properties, which includes setting up a data source. This supports options A and B.

2. Salesforce OmniStudio Documentation: FlexCards Data Source Properties

Reference: This documentation specifies that FlexCards use data sources like DataRaptors, SOQL queries, or Apex to retrieve data. For extracting and filtering records from a Salesforce object as required in the question, a DataRaptor Extract is the standard and recommended method. This supports option C.

3. Salesforce Trailhead: FlexCard Basics > Create a FlexCard

Reference: The "Activate a FlexCard" unit explains that a FlexCard (including child cards) must be activated to be used or displayed within another component or Lightning page. This confirms the "activate" part of option B is a necessary step.