Merge pull request #218835 from EXPEkesheth/patch-16

Update smart-on-fhir.md

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/smart-on-fhir.md

@@ -17,13 +17,13 @@ Substitutable Medical Applications and Reusable Technologies [SMART on FHIR](htt
 - Users accessing a FHIR repository with SMART on FHIR are restricted to resources associated with the user, rather than having access to all data in the repository
 - Users have the ability to grant applications access to a further limited set of their data by using SMART clinical scopes.
 
-<!---SMART Implementation Guide v1.0.0 is supported by Azure API for FHIR and Azure API Management (APIM). This is our recommended approach, as it enabled Health IT developers to comply with 21st Century Act Criterion §170.315(g)(10) Standardized API for patient and population services. 
+<!---SMART Implementation Guide v1.0.0 is supported by Azure Health Data Services and Azure API Management (APIM). This is our recommended approach, as it enabled Health IT developers to comply with 21st Century Act Criterion §170.315(g)(10) Standardized API for patient and population services. 
 
 Sample demonstrates and list steps that can be referenced to pass ONC G(10) with Inferno test suite.
 
 --->
 
-One of the main purposes of the specifications is to describe how an application should discover authentication endpoints for an FHIR server and start an authentication sequence. SMART on FHIR uses parameter naming conventions that aren’t immediately compatible with Azure Active Directory (Azure AD), the Azure API for FHIR has a built-in Azure AD SMART on FHIR proxy that enables a subset of the SMART on FHIR launch sequences. Specifically, the proxy enables the [EHR launch sequence](https://hl7.org/fhir/smart-app-launch/#ehr-launch-sequence).
+One of the main purposes of the specifications is to describe how an application should discover authentication endpoints for an FHIR server and start an authentication sequence. SMART on FHIR uses parameter naming conventions that aren’t immediately compatible with Azure Active Directory (Azure AD), the Azure Health Data Services (FHIR Service) has a built-in Azure AD SMART on FHIR proxy that enables a subset of the SMART on FHIR launch sequences. Specifically, the proxy enables the [EHR launch sequence](https://hl7.org/fhir/smart-app-launch/#ehr-launch-sequence).
 
 Below tutorial describes steps to enable SMART on FHIR applications with FHIR Service.
 
@@ -32,7 +32,7 @@ Below tutorial describes steps to enable SMART on FHIR applications with FHIR Se
 - An instance of the FHIR Service
 - .NET SDK 6.0
 - [Enable cross-origin resource sharing (CORS)](configure-cross-origin-resource-sharing.md)
-- [Register public client application in Azure AD](/register-public-azure-ad-client-app.md)
+- [Register public client application in Azure AD]([https://learn.microsoft.com/azure/healthcare-apis/azure-api-for-fhir/register-public-azure-ad-client-app]
      - After registering the application, make note of the applicationId for client application.
 
 <!--- Tutorial : To enable SMART on FHIR using APIM, follow below steps