Merge pull request #219603 from EXPEkesheth/patch-19

Update smart-on-fhir.md

Author: prmerger-automator[bot]

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

@@ -19,8 +19,6 @@ Substitutable Medical Applications and Reusable Technologies([SMART on FHIR](htt
 
 <!---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 specification 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). 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).
 
@@ -40,7 +38,14 @@ As a pre-requisite , ensure you have access to Azure Subscription of FHIR servic
 Step 1 : Set up FHIR SMART user role 
 Follow the steps listed under section [Manage Users: Assign Users to Role](https://learn.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal). Any user added to this role will be able to access the FHIR Service if their requests comply with the SMART on FHIR implementation Guide, such as request having access token which includes a fhirUser claim and a clinical scopes claim.  The access granted to the users in this role will then be limited by the resources associated to their fhirUser compartment and the restrictions in the clinical scopes.
 
-Step 2 : [Follow the steps](https://github.com/microsoft/fhir-server/tree/feature/smart-onc-g10-sample/samples/smart) for setting up the FHIR server integrated with APIM in production. ---> 
+Step 2 : [Follow the steps](https://github.com/microsoft/fhir-server/tree/feature/smart-onc-g10-sample/samples/smart) for setting up the FHIR server integrated with APIM in production. 
+
+This link provides sample code, which enables integration with FHIR server and other Azure Services (such as APIM, Azure functions and more).
+
+[!Note]
+Samples are released under the MIT License and are not supported by Microsoft Support. Samples are provided to demonstrate how Azure Health Data Services can be used to pass the Inferno test for ONC (g)(10) compliance, using Azure Active Directory as the identity provider workflow. 
+
+---> 
 
 Lets go over individual steps to enable SMART on FHIR 
 ## Step 1 : Set admin consent for your client application