Resolved PR comments.

Author: v-aljagtap

articles/healthcare-apis/azure-api-for-fhir/customer-managed-key.md

@@ -150,7 +150,7 @@ New-AzResourceGroupDeployment `
 
 **Is the 'cosmosdb_key_vault_key_versionless_id' used in the FHIR API designed to connect to FHIR service managed Cosmos DB?**
 
-Yes, when you are enabling Customer managed keys on FHIR APIs, selecting 'cosmosdb_key_vault_key_versionless_id' connects to FHIR service managed Cosmos DB.
+Yes, when you are enabling customer-managed keys on FHIR APIs, selecting 'cosmosdb_key_vault_key_versionless_id' connects to FHIR service managed Cosmos DB.
 
 ## Next steps
 

articles/healthcare-apis/fhir/convert-data-troubleshoot.md

@@ -43,9 +43,7 @@ In addition to testing templates on an instance of the service, a [Visual Studio
 
 ## Troubleshooting Azure Container Registry
 
-## The AHDS FHIR Service should work with Azure Container Registry (ACR) for custom template storage, but it encounters a "Failed to get access token for Azure Container Registry" error when reading templates.
-
-Check the configuration related to Azure Managed Identity and its role. [Configure settings for $convert-data](convert-data-configuration.md)
+When using Azure Container Registry (ACR) for custom template storage, if you encounter a "Failed to get access token for Azure Container Registry" error when reading templates, check to make sure that the correct role assignments are configured for the managed identity. [Configure settings for $convert-data](convert-data-configuration.md)
 
 ## Next steps
 [Overview of $convert-data](convert-data-overview.md)

articles/healthcare-apis/fhir/deploy-azure-portal.md

@@ -63,7 +63,7 @@ If deployed to the wrong subscription, we can move the resource to the desired s
 
 **How can I delete a service and then re-add it with the same settings?**
 
-It is not possible to replicate a service with the exact same settings. 
+To replicate settings between FHIR instance, you can follow below steps 
 
 *	Create standard ARM templates with the configurations.
 

articles/healthcare-apis/fhir/fhir-faq.md

@@ -143,19 +143,12 @@ To perform a health check on a FHIR service, enter `{{fhirurl}}/health/check` in
 
 If there are errors, you may receive an error response with HTTP status code 404 (Not Found) or status code 500 (Internal Server Error), and detailed information in the response body.
 
-**What are the recommended methods for syncing data between Azure FHIR Service and a Dataverse?**
+**What are the recommended methods for syncing data between Azure FHIR Service and Dataverse?**
 
-To connect FHIR services with Dataverse, we have introduced a new capability known as the Dataverse Health APIs.
-[Dataverse healthcare APIs](https://learn.microsoft.com/en-us/dynamics365/industry/healthcare/dataverse-healthcare-apis-overview)
+Please refer to documentation for
+[Dataverse healthcare APIs](https://learn.microsoft.com/dynamics365/industry/healthcare/dataverse-healthcare-apis-overview)
 
 
-
-**Why can't I create new resources from the Azure Marketplace? It always fails when I enter a name for the account or workspace.**
-
- Check if organizations impose restrictions on the creation of Azure Marketplace services due to their different pricing structures.
-
-Check for standard version of that service available outside the Marketplace.
-
 ## Next steps
 
 In this article, you've learned the answers to frequently asked questions about FHIR service. To see the frequently asked questions about FHIR service in Azure API for FHIR, see

articles/healthcare-apis/fhir/import-data.md

@@ -257,11 +257,6 @@ Cause: You reached the storage limit of the FHIR service.
 
 Solution: Reduce the size of your data or consider Azure API for FHIR, which has a higher storage limit.
 
-**import operation failed for reason: Input string was not in the correct format**
-
-Cause: An NDJSON Patient resource was submitted in Blob storage. After a POST request to {{fhirUrl}}/$import, a GET request to the callback link from the Content-Location header resulted in a 500 Internal Server Error.
-
-Solution:  Ensure that the JSON file is imported using a compatible storage account version. If an export is made from storage account v2, it should be imported into a storage account v2 to avoid compatibility issues.
 
 ### 423 Locked
 

articles/healthcare-apis/fhir/overview-of-search.md

@@ -163,13 +163,7 @@ Currently, the FHIR service in Azure Health Data Services only supports the `nex
 ## Troubleshooting FHIR Search
 **Is the HL7 FHIR API, specifically the lastN operation for observations, supported by Microsoft?**
 
-This option is not supported. Please refer to the alternative approach provided below:
-
-GET [base]/Observation?_count=N&_sort=-_lastUpdated&patient=Patient/123&category=vital-signs.  
-
-_count=N : This specifies the TOTAL number of records to be returned per page of results. In this example N results will be returned, not N per search parameter.   
-
-_sort=-_lastUpdated : This sorts the results by newest first. This is what gets the behavior to be like $lastn. Combined with _count with would return the most recent X results.
+This option is not supported. Please refer to the alternative approach would be to use _count to restrict resources returned per page and then use sort parameter to provide results in descending order.
 
 ## Next steps
 

articles/healthcare-apis/fhir/rest-api-capabilities.md

@@ -186,12 +186,7 @@ Content-Type: `application/json`
 The $bulk-delete operation allows you to delete resources from the FHIR server asynchronously. You can execute the $bulk-delete operation either at the system level or for specific resource types.
 [Bulk-delete](fhir-bulk-delete.md)
 
-If customers want to delete all resources that reference Patient, they can use a conditional delete. It would still require multiple requests: at least one to delete the linked resources and one to delete the Patient.
- [Conditional delete](rest-api-capabilities.md#conditional-delete)
 
- **The encountered error is: "Resource type Observation with id eaf42d04-1c93-451a-b320-85363155ab49 and version '1' couldn't be found." The same request was working fine until a week ago, but now it only works when the "If-Match" header is removed.**
-
- By design If-match header must match the most recent version of the identified resource. Incase there is no match with the recent version, error will occur.
 
 ## Related content
 

articles/healthcare-apis/fhir/troubleshoot-identity-provider-configuration.md

@@ -31,7 +31,7 @@ Here are the error messages that occur if the FHIR service SMART identity provid
 | **One or more SMART application `audience` values are null, empty, or invalid.** | The `audience` string in one or more application configurations is null, empty, or malformed. | Ensure the `audience` string isn't null or empty and that the value is a string type. |
 | **All SMART identity provider application client ids must be unique.** | The `clientId` value in one or more application configurations is the same value as another `clientId` value. | Ensure all `clientId` values are unique (including across identity provider configurations). |
 | **One or more SMART application client id values are null, empty, or invalid.** | The `clientId` string in one or more application configurations is null, empty, or malformed. | Ensure the `clientId` string isn't null or empty and that the value is a string type. |
-| **An authorization failure with the Azure Health Data Services FHIR API using OKTA.** | FHIR SMART user role will cause this issue as it adds an authentication layer. | Ensure that the FHIR SMART user role is not assigned. |
+| **An authorization failure with the Azure Health Data Services FHIR API using third party identity provider.** | FHIR SMART user role will cause this issue as it adds an authentication layer. | Ensure that the FHIR SMART user role is not assigned. |
 
 ## FHIR API request errors