AP-211 Sample Questions & Answers

This combination is designed for this exact use case. The Care Program object defines the program and its stages. The Care Program Enrollee links a patient (Account/Contact) to a specific program. Care Program Provider links practitioners to the program. This structure allows tracking enrollment, progress, and associated activities in a structured, reportable way.

This is the best practice. Health Cloud's data model is aligned with the FHIR (Fast Healthcare Interoperability Resources) standard. Using FHIR APIs, mediated by an integration platform like MuleSoft, allows for a standards-based, robust, and maintainable near real-time synchronization with modern EHR systems.

True. The Individual data model, which uses separate Account and Contact records, is recommended over the Person Account model when an individual can have multiple roles in the healthcare ecosystem (e.g., a doctor who is also a patient). This model provides the flexibility to create different record types on the Account object to represent these distinct roles.

This is the recommended best practice. The Health Cloud Consent Management data model is purpose-built for this scenario. By creating a Data Use Purpose record for each distinct service (e.g., 'Adherence Reminders', 'Copay Assistance'), the company can associate specific Authorization Form Consent records for each patient to each purpose. This provides a detailed, auditable, and scalable way to manage granular consent.

This design is suboptimal because Health Cloud provides a standard object, Healthcare Practitioner Facility, specifically to create the many-to-many relationship between a practitioner and a facility. Using this standard object ensures compatibility with other Health Cloud features like Provider Search and maintains alignment with the canonical data model.

A robust Provider Data Model is the foundation. It must accurately store practitioner details, specialties, facility locations, and network affiliations to power the search.

Experience Cloud (formerly Community Cloud) is the Salesforce platform for creating external-facing portals and websites, making it the correct choice for the member self-service portal.

The out-of-the-box Provider Search feature is designed to query the provider data model based on various criteria like specialty and location. It provides the core search logic and can be exposed in an Experience Cloud site.

An ETL process is the best practice for complex migrations with data quality issues. It allows data to be extracted from the source, transformed (cleansed, deduplicated, standardized) in a staging environment, and then loaded into the target system. This ensures that only clean, high-quality data enters Health Cloud.

The primary advantage of the Care Plan data model is its structure. It allows for the definition of patient problems (diagnoses), the establishment of measurable goals to address those problems, and the creation of specific tasks to achieve those goals. This provides a clinically relevant, hierarchical view that is far superior for tracking and reporting on patient outcomes compared to a flat list of tasks.

The Enhanced Timeline is the purpose-built Health Cloud feature for this requirement. It is designed to provide a configurable, chronological view of a patient's journey. It can be configured to display records from standard objects, custom objects, and data from external systems, making it the ideal centerpiece for visualizing events from both Salesforce and the EHR.

This is the correct data modeling approach. Creating separate custom objects for each distinct activity type allows for the storage of structured data (e.g., publication date, trial phase, event location). These objects would have a master-detail or lookup relationship to the physician's Contact record, enabling robust reporting, analysis, and a comprehensive 360-degree view of the KOL's activities.