|
| 1 | +--- |
| 2 | +title: FAQs about IoT connector - Azure Healthcare APIs |
| 3 | +description: This document provides answers to the frequently asked questions about IoT connector. |
| 4 | +services: healthcare-apis |
| 5 | +author: msjasteppe |
| 6 | +ms.custom: references_regions |
| 7 | +ms.service: healthcare-apis |
| 8 | +ms.topic: reference |
| 9 | +ms.date: 10/21/2021 |
| 10 | +ms.author: jasteppe |
| 11 | +--- |
| 12 | + |
| 13 | +# Frequently asked questions about IoT connector |
| 14 | + |
| 15 | +Here are some of the frequently asked questions about IoT connector. |
| 16 | + |
| 17 | +## IoT connector: The basics |
| 18 | + |
| 19 | +### What are the differences between the Azure API for FHIR IoT connector (preview) and the Azure Healthcare APIs IoT connector? |
| 20 | + |
| 21 | +Azure Healthcare APIs IoT connector is the successor to the Azure API for Fast Healthcare Interoperability Resources (FHIR®) IoT connector (preview). |
| 22 | + |
| 23 | +Several improvements have been introduced including customer-hosted device message ingestion endpoints (for example: an Azure Event Hub), the use of Managed Identities, and Role-Based Access Control. |
| 24 | + |
| 25 | +### Can I use IoT connector with a different FHIR service other than the Azure Healthcare APIs FHIR service? |
| 26 | + |
| 27 | +No. The Azure Healthcare APIs IoT connector currently only supports the Azure Healthcare APIs FHIR service for persistence of data. The open-source version of the IoT connector supports the use of different FHIR services. For more information, see the [Open-source projects](iot-git-projects.md) section. |
| 28 | + |
| 29 | +### What versions of FHIR does the IoT connector support? |
| 30 | + |
| 31 | +The IoT connector currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491). |
| 32 | + |
| 33 | +### What are the subscription quota limits for IoT connector? |
| 34 | + |
| 35 | +* 25 IoT Connectors per Subscription (adjustable with an Azure support request) |
| 36 | +* 10 IoT Connectors per Workspace (adjustable with an Azure support request) |
| 37 | +* One FHIR Destination* per IoT Connector (not adjustable) |
| 38 | + |
| 39 | +(* - FHIR Destination is a child resource of IoT connector) |
| 40 | + |
| 41 | +### Can I use the IoT connector with device messages from Apple®, Google®, or Fitbit® devices? |
| 42 | + |
| 43 | +Yes. IoT connector supports device messages from all these platforms. For more information, see the [Open-source projects](iot-git-projects.md) section. |
| 44 | + |
| 45 | +## More frequently asked questions |
| 46 | +[FAQs about the Azure Healthcare APIs](../healthcare-apis-faqs.md) |
| 47 | + |
| 48 | +[FAQs about Azure Healthcare APIs FHIR service](../fhir/fhir-faq.md) |
| 49 | + |
| 50 | +[FAQs about Azure Healthcare APIs DICOM service](../dicom/dicom-services-faqs.yml) |
| 51 | + |
| 52 | +(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7. |
0 commit comments