You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/iot-connector-faqs.md
+11-16Lines changed: 11 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,39 +6,34 @@ author: msjasteppe
6
6
ms.custom: references_regions
7
7
ms.service: healthcare-apis
8
8
ms.topic: reference
9
-
ms.date: 07/19/2022
9
+
ms.date: 12/06/2022
10
10
ms.author: jasteppe
11
11
---
12
12
13
13
# Frequently asked questions about the MedTech service
14
14
15
15
Here are some of the frequently asked questions about the MedTech service.
16
16
17
-
## MedTech service: The basics
17
+
## The MedTech service: The basics
18
18
19
-
### What are the differences between the Azure IoT Connector for FHIR and the Azure Health Data Services MedTech service?
19
+
### Where is the MedTech service available?
20
20
21
-
Azure Health Data Services MedTech service is the successor to the Azure IoT Connector for Fast Healthcare Interoperability Resources (FHIR®).
22
-
23
-
Several improvements have been introduced including customer-hosted device message ingestion endpoints (for example: an Azure Event Hubs), the use of a system-assigned managed identity, and Azure role-based access control (Azure RBAC).
24
-
25
-
> [!IMPORTANT]
26
-
>
27
-
> As of September 2022, the IoT Connector feature within the Azure API for FHIR will be retired and replaced with the [MedTech service](../../healthcare-apis/iot/deploy-iot-connector-in-azure.md) for enhanced service quality and functionality.
28
-
>
29
-
> All new users are directed to deploy and use the MedTech service feature within the Azure Health Data Services.
30
-
> For more information about the MedTech service, see [What is the MedTech service?](../../healthcare-apis/iot/iot-connector-overview.md).
21
+
The MedTech service is available in these regions: [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=health-data-services).
31
22
32
23
### Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
33
24
34
-
No. The Azure Health Data Services MedTech service currently only supports the Azure Health Data Services FHIR service for persistence of data. The open-source version of the MedTech service supports the use of different FHIR services.
25
+
No. The Azure Health Data Services 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.
35
26
36
27
For more information, see the [Open-source projects](iot-git-projects.md) section of our documentation.
37
28
38
29
### What versions of FHIR does the MedTech service support?
39
30
40
31
The MedTech service currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
41
32
33
+
### Does the MedTech service perform backups of device messages?
34
+
35
+
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 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-)
36
+
42
37
### What are the subscription quota limits for the MedTech service?
43
38
44
39
* 25 MedTech services per Subscription (not adjustable)
@@ -49,9 +44,9 @@ The MedTech service currently only supports the persistence of [HL7 FHIR® R
49
44
50
45
### Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
51
46
52
-
Yes. The MedTech service supports device messages from all these vendors.
47
+
Yes. The MedTech service supports device messages from all these vendors through the open-source version.
53
48
54
-
For more information, see the [Open-source projects](iot-git-projects.md) section of our documentation.
49
+
For more information, see the [Open-source projects](iot-git-projects.md) section of our documentation.
55
50
56
51
## More frequently asked questions
57
52
[FAQs about the Azure Health Data Services](../healthcare-apis-faqs.md)
0 commit comments