In OmniStudio FlexCards, when you want to change the visual styling of a field element (e.g., font type, font color, formatting), you have two main options:
A . Write custom CSS
OmniStudio FlexCards allow applying custom CSS classes for fine-grained control of styles.
This is how you can specify a font like Times New Roman or apply a red color.
B . Make edits to Field Style
The Field Style editor within the FlexCard Designer lets you directly configure basic styling properties (like text color, background, alignment, etc.) without needing custom CSS.
Why not the others?
C . Make edits to Setup Panel - The Setup Panel is for data source, conditions, and layout configuration, not for styling individual fields.
D . Make edits to Field Properties - Field Properties are used to configure which data is displayed and how it behaves (like label, formatting rules, or conditional display), but styling is handled through Field Style or CSS, not properties.
Salesforce OmniStudio Reference:
* Salesforce OmniStudio FlexCard Designer Guide
"You can use the Field Style editor to set basic styles, such as font color and alignment."
"For advanced customization, apply custom CSS classes to field elements."

In Salesforce Health Cloud, when dealing with prior authorizations, the correct data model objects are:
* Service Preauth # Represents the overall prior authorization request (at the header level).
* Preauth Detail # Captures the individual service line items or outcomes associated with the prior authorization.
This structure allows Health Cloud to integrate with an external utilization management system that handles the full prior authorization process. The Service Preauth object acts as the container for the request, while Preauth Detail records capture outcomes, decisions, and details returned from the external system.
This is exactly suited to the requirement:
"The provider requires a display of preauthorization outcomes from its external system which manages the end-to-end prior authorization process." Why not the others?
* A. Plan Benefit and Plan Benefit Item - These are used to model insurance plan coverage and benefits, not authorization workflows.
* B. Care Preauth and Care Preauth Item - These are older, deprecated objects in favor of the Service Preauth data model.
* D. Care Request and Care Request Item - These are used to track referrals and service requests (e.g., a doctor requesting lab work), but not prior authorization outcomes.
Salesforce Health Cloud Reference:
# Salesforce Health Cloud Developer Guide - Utilization Management Data Model:
"The Service Preauth object represents the prior authorization request and its details. The Preauth Detail object contains service line items and outcomes for the prior authorization request."
* Salesforce Help: Utilization Management Data Model
* Salesforce Health Cloud Implementation Guide - Prior Authorizations

Comprehensive Detailed Step by Step Explanation with exact Extracts from Salesforce Health Cloud documents that you have with References
* Experience Builder and Component Access:
* Add the Provider Search component to the Experience Cloud site page for external user access.
* Extract:
"Use Experience Builder to add Provider Search components to your site to enable external users to search for providers."
-Provider Search in Experience Cloud
* Read Access:
* Granting Read access to theCare Provider Searchable Fieldobject is required for site users to access search results.
* Extract:
"Grant the site user profile Read access to the Care Provider Searchable Field object to allow them to view provider search results."
-Provider Search Security
* Other Options:
* B:Sharing rules not typically required; object-level access is key.
* D:Data Pipeline object access is not relevant for provider search results.
References:
Provider Search in Experience Cloud