A provider uses an external appointment management system. The default solution provided by Health Cloud is not viable for the provider. How should a…

When a default Salesforce Health Cloud solution like Intelligent Appointment Management is not viable, the recommended best practice is to evaluate pre-built, specialized applications from the AppExchange. Using a package created by an Independent Software Vendor (ISV) is often the most robust and efficient approach. These solutions are vetted by Salesforce, specifically designed for Health Cloud, and provide a supported, maintainable, and often faster implementation path for integrating with specific external systems compared to building a custom solution from scratch.

A. Create a custom FHIR Adapter to make calls to Health Cloud. While technically feasible, this "build" approach requires significant development and maintenance resources. It is typically considered only after a suitable "buy" option, like an ISV package, has been ruled out.
C. Use an electronic health record (EHR) routing system to book the appointment in Health Cloud. An EHR routing system is a middleware component for data exchange, not the primary implementation method for integrating an appointment system directly into the Salesforce platform.
D. Create an Apex class and leverage Intelligent Appointment Management. This is incorrect because the scenario explicitly states that the default solution, which includes Intelligent Appointment Management, is not viable for the provider. ---

1. Salesforce AppExchange Overview: The official documentation emphasizes the AppExchange as the primary marketplace for extending Salesforce functionality. "The AppExchange is the leading enterprise cloud marketplace with ready-to-install solutions, apps, and consultants to help you extend Salesforce." This supports the principle of looking for an ISV solution first.

Source: Salesforce Help, "AppExchange," Section: "What is AppExchange?"

2. Health Cloud Developer Guide - Extend Health Cloud: The guide discusses various methods for extending Health Cloud, including using AppExchange packages and building custom solutions with APIs. The ecosystem of partners is presented as a key asset. "The Salesforce Platform provides a rich ecosystem of partners who offer pre-integrated applications on AppExchange."

Source: Salesforce Health Cloud Developer Guide, "Extend Health Cloud," Section: "AppExchange for Health Cloud."

3. Health Cloud Administrator Guide - Intelligent Appointment Management: This documentation details the native scheduling feature. Its unsuitability in the scenario necessitates an alternative, such as an external system integrated via an ISV package or custom API work.

Source: Salesforce Health Cloud Administrator Guide, "Set Up Intelligent Appointment Management."

4. Architect's Guide to Building on the Salesforce Platform: While not specific to Health Cloud, this guide for solution architects outlines the "Buy-vs-Build" decision framework. It consistently recommends evaluating existing AppExchange solutions before committing to custom development to reduce total cost of ownership and accelerate time-to-value.

Source: Salesforce Architects, "Architect's Guide to Building on the Salesforce Platform," Chapter: "Application Lifecycle," Section: "Buy-vs-Build Decisions."