What is the best practice when transitioning an org from Service Cloud to HC?
Answer(s): A
According to the Health Cloud Implementation Guide, the best practice when transitioning an org from Service Cloud to Health Cloud is to approach it depending on how each customer uses their org. There is no one-size-fits-all solution for migrating from Service Cloud to Health Cloud, as each customer may have different requirements, use cases, and data models. Therefore, any of the other options may be used depending on the customer's needs and preferences.
A Payer Service Cloud org uses Accounts and contacts to model Health Insurance Members. While all teams within the organization Work with all members, only some teams require HC capabilities. What is the recommended best practice for modeling members in HC for this organization?
Answer(s): B
According to the Health Cloud Implementation Guide, the recommended best practice for modeling members in Health Cloud for a payer service cloud org that uses accounts and contacts to model health insurance members is to model them as person accounts, whether they are using Health Cloud capabilities or not. Person accounts are a type of account that combines account and contact information in a single record. They are suitable for representing individual consumers in healthcare and life sciences. Using person accounts for all members can simplify data management and avoid data duplication. Only groups needing Health Cloud capabilities need to use person accounts is not a recommended best practice, as it can create inconsistency and complexity in data modeling. Account record types for existing members can remain as-is is not a recommended best practice, as it can limit the functionality and integration of Health Cloud features. Using the individual model with Health Cloud is not a valid option, as the individual model is not supported by Health Cloud.
In which two ways can a Data Architect ensure PHI/PII data visibility is minimized during the migration of Patient Data from an existing Service Cloud org to a new HC org?(Choose 2)
Answer(s): A,B
According to the Health Cloud Data Model Developer Guide, two ways that a data architect can ensure PHI/PII data visibility is minimized during the migration of patient data from an existing Service Cloud org to a new Health Cloud org are:Use Salesforce Data Masking when moving data to a sandbox. Data Masking is a tool that helps you protect sensitive data in sandboxes by masking it with anonymized values. Use Data Templates to exclude PHI/PII data from being added to partial copy sandboxes. Data Templates are files that specify which objects and fields to include or exclude when creating a partial copy sandbox. Exporting data to a spreadsheet to remove PHI before importing it into a sandbox is not a recommended way, as it can introduce errors and security risks. Ensuring sandboxes have Platform Shield enabled is not a valid way, as Platform Shield is not a feature of sandboxes. Platform Shield is a product that allows encryption of data at rest in production orgs.
What is the recommended approach to create patients' records used in HC?
Answer(s): D
Which step is recommended to be completed before migrating from Service Cloud to HC?
Share your comments for Salesforce HEALTH CLOUD ACCREDITED PROFESSIONAL exam with other users:
question 11: https://help.salesforce.com/s/articleview?id=sf.admin_lead_to_patient_setup_overview.htm&type=5
question 16: https://help.salesforce.com/s/articleview?id=sf.care_console_overview.htm&type=5
question 5, it seems a instead of d, because: - care plan = case - patient = person account - product = product2;
for this question - "which three type of basic patient or member information is displayed on the patient info component? (choose three.)", list of conditions is not displayed (it is displayed in patient card, not patient info). so should be thumbnail of chatter photo