A developer needs to modify the out-of-the-box Advanced Patient Card to display the Category, SubjectID,...

The Advanced Patient Card is an OmniStudio FlexCard pattern. To extend it safely, clone the parent card, create and activate a new child card for the Clinical Alert presentation, and use a DataRaptor/Data Mapper to retrieve Category, SubjectID, Date, and the data needed to filter active alerts. This preserves the delivered component while adding the required clinical information. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. DataRaptors, now also represented as Data Mappers in current OmniStudio terminology, declaratively extract, transform, and load Salesforce data for OmniStudio components. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach.

Study Guide references/topics:Implement - OmniStudio; DataRaptor

===============