The issue is that the FlexCard is displaying an extra line whenever Address Line 2 has data. The requirement is to fix the display formatting without changing the underlying data model.
* In OmniStudio DataRaptors, you can add formula fields during data extraction.
* By concatenating Address Line 1 + Address Line 2 into a single formatted field inside the Extract DataRaptor, you can pass the clean, properly formatted address to the FlexCard.
* This approach ensures:
* No changes to underlying data structure.
* No need to create new fields.
* Controlled formatting at the data transformation layer.
Why not the others?
* A. Add a Load DataRaptor to write the data into one new custom field.
* This changes the data model by writing into a new custom field, which the requirement prohibits.
* B. Replace the Extract DataRaptor with a Transform DataRaptor.
* Transform DataRaptors are typically used for complex JSON-to-JSON mapping or orchestration, not needed here since a simple formula in the Extract DataRaptor suffices.
* D. Create a new Turbo Extract DataRaptor to trim the Address data in both fields.
* Turbo Extracts are used for high-performance, single-object extracts but do not support formulas or transformations.
* They wouldn't solve the concatenation/formatting issue.
Salesforce OmniStudio Reference:
# OmniStudio DataRaptor Guide:
* "Use formulas in Extract DataRaptors to concatenate or transform fields before passing data to a UI component."
* "Turbo Extract DataRaptors don't support formulas or transformations."

When organization-wide default access to patient data is set to Private,Care Team functionalityin Health Cloud is the standard, out-of-the-box method to manage individual access to patient records.
Step-by-Step Reference:
* Health Cloud uses Care Teams to manage access to patient records.
* Extract:
"Add care team members (users, contacts, or person accounts) to the patient's care team and assign appropriate access (Read or Read/Write) to patient records." (Source: Administer Health Cloud - Manage Care Teams)
* Administrators can specify the access level(Read or Read/Write) for each care team member, allowing for precise control as per role requirements.
* Extract:
"Assign record access levels for care team members when adding them to a patient's care team. This is especially important when the OWD is set to Private." (Source: Administer Health Cloud - Care Team Access)
* This ensures compliance and proper segmentation of data, as required by healthcare regulations.

Step-by-Step Explanation:
* Salesforce Health Cloud Best Practice for Person Accounts Access:
* Person Accounts in Salesforce are a combination of an Account and a Contact.
* To ensure that access to the person account (patient record) gives access to all data on the record , Salesforce recommends setting the Contact sharing setting to " Controlled by Parent
" .
* This means the sharing and visibility of the Contact (patient details) will follow the sharing settings of the parent Account (the Person Account).
* Salesforce Documentation Reference:
* "For Person Account sharing and access, set the Contact object sharing setting to Controlled by Parent. This ensures that users with access to the Account (Person Account) also have access to the associated Contact data." - Reference: Health Cloud Implementation Guide, Sharing and Access
* Why Not the Other Options?
* A. Set Modify All on the Account object at the Profile level: Too broad; not recommended due to least privilege principle.
* C. Set Private for the Contact object: Would prevent access to the Contact, even if user has access to the Account.
* D. Set the organization-wide default to Public Read Write for the Account object: Not best practice for healthcare, as it risks overexposing sensitive data.
References:
Health Cloud Implementation Guide - Sharing and Access