Additional edits and additions

Author: msjasteppe

articles/healthcare-apis/iot/frequently-asked-questions.md

@@ -6,70 +6,65 @@ author: msjasteppe
 ms.custom: references_regions
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 1/5/2023
+ms.date: 1/26/2023
 ms.author: jasteppe
 ---
 
 # Frequently asked questions about the MedTech service
 
-Here are some of the frequently asked questions (FAQs) about the MedTech service.
+This article provides answers to frequently asked questions (FAQs) about the MedTech service.
 
-## The MedTech service: The basics
-
-### Where is the MedTech service available?
+## Where is the MedTech service available?
 
 The MedTech service is available in these Azure regions: [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=health-data-services).
 
-### Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
+## Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
 
-No. The MedTech service currently only supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service for the persistence of data. The open-source version of the MedTech service supports the use of different FHIR services. 
+No. The MedTech service currently only supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service for the persistence of transformed device message data. The open-source version of the MedTech service supports the use of different FHIR services. 
 
 To learn more about the MedTech service open-source projects, see [Open-source projects](git-projects.md). 
 
-### What versions of FHIR does the MedTech service support?
+## What versions of FHIR does the MedTech service support?
 
 The MedTech service currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
 
-### How long does it take for device message data to show up on the FHIR service?
+## How long does it take for device message data to show up on the FHIR service?
 
 The MedTech service buffers the FHIR Observations resources created during the transformation stage and provides near real-time processing. However, it can potentially take up to five minutes for FHIR Observation resources to be persisted in the FHIR service. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md). 
 
-### Why do I have to provide device and FHIR destination mappings to my MedTech service?
+## Why do I have to provide device and FHIR destination mappings to the MedTech service?
 
 The MedTech service requires the device and FHIR destination mappings to perform normalization and transformation processes on the device message data. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).  
 
-### Does the MedTech service perform backups of device messages?
+## Does the MedTech service perform backups of device messages?
 
 No. The MedTech service doesn't back up the device messages that come into the customer's event hub. The customer controls the device message retention period within their event hub, which can be from 1-7 days. If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the FHIR service backup policy applies. 
 
 To learn more about event hub message retention, see [What is the maximum retention period for events?](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events-) 
 
-### What are the subscription quota limits for the MedTech service?
+## What are the subscription quota limits for the MedTech service?
 
 * 25 MedTech services per Subscription (not adjustable)
 * 10 MedTech services per workspace (not adjustable)
 * One FHIR destination* per MedTech service (not adjustable)
 
 (* - FHIR Destination is a child resource of the MedTech service)
 
-### Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
+## Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
 
 Yes. The MedTech service supports device messages from all these vendors through the open-source version of the MedTech service. 
 
 To learn more about the MedTech service open-source projects, see [Open-source projects](git-projects.md). 
 
-## More frequently asked questions
-
-[FAQs about the Azure Health Data Services](../healthcare-apis-faqs.md)
-
-[FAQs about Azure Health Data Services FHIR service](../fhir/fhir-faq.md)
-
-[FAQs about Azure Health Data Services DICOM service](../dicom/dicom-services-faqs.yml)
-
 ## Next steps
 
 In this article, you learned about the MedTech service frequently asked questions (FAQs)
 
+To learn about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [What is the MedTech service?](overview.md)
+
 To learn about methods for deploying the MedTech service, see
 
 > [!div class="nextstepaction"]