Merge pull request #297983 from EXPEkesheth/patch-380124

Update fhir-faq.yml

Author: JillGrant615

articles/healthcare-apis/azure-api-for-fhir/fhir-faq.yml

@@ -53,18 +53,6 @@ sections:
           
           Azure IoT Connector for FHIR (preview) currently supports only FHIR version R4 and is visible on R4 instances of Azure API for FHIR.
 
-      - question: |
-          What's the difference between Azure Health Data Services and Azure API for FHIR?
-        answer: |
-          Azure API for FHIR is a generally available managed FHIR service. Azure Health Data Services allows you to deploy a FHIR service and a DICOM service in the same workspace. The Azure Health Data Services overview provides more details.         
-          
-      - question: |
-          What's the difference between the Microsoft FHIR Server for Azure and Azure API for FHIR?
-        answer: |
-          Azure API for FHIR is a hosted and managed version of the open-source Microsoft FHIR Server for Azure. In the managed service, Microsoft provides all maintenance and updates. 
-          
-          When you run the FHIR Server for Azure, you have direct access to the underlying services, but we're responsible for maintaining and updating the server and all required compliance work if you're storing PHI data.
-          
       - question: |
           In which regions is Azure API for FHIR available?
         answer: |
@@ -227,4 +215,9 @@ sections:
       - question: |
           What should I do if I am unable to delete a FHIR Resource due to its provisioning state?
         answer: |
-          Check if disaster recovery is enabled for the FHIR resource. If it is, disable the disaster recovery feature.  
+          Check if disaster recovery is enabled for the FHIR resource. If it is, disable the disaster recovery feature.  
+
+      - question: |
+          What should I do if I receive HTTP status code 429 from Azure API for FHIR service?
+        answer: |
+         Check the RU consumption associated with the FHIR instance. In case of high RU consumption (around 100%), check if the throttling error corresponds to the time of high RU usage. If it does, consider enabling autoscaling for your service and increasing the RU allocated to your service. Refer to [autoscaling Azure API for FHIR](autoscale-azure-api-fhir.md) for more details.