Skip to content

Commit 85daca6

Browse files
authored
Merge pull request #176447 from msjasteppe/iot-oss-updates
Updates to the OSS page of IoT connector
2 parents 35d451b + f2f707c commit 85daca6

File tree

1 file changed

+19
-9
lines changed

1 file changed

+19
-9
lines changed

articles/healthcare-apis/iot/iot-git-projects.md

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: healthcare-apis
55
author: msjasteppe
66
ms.service: healthcare-apis
77
ms.topic: reference
8-
ms.date: 10/18/2021
8+
ms.date: 10/19/2021
99
ms.author: jasteppe
1010
---
1111
# Open-source projects
@@ -14,19 +14,29 @@ Check out our open-source projects on GitHub that provide source code and instru
1414

1515
## IoT connector GitHub projects
1616

17-
#### Integration with IoT Hub and IoT Central
17+
#### FHIR integration
1818

19-
* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): integration with IoT Hub or IoT Central to Fast Healthcare Interoperability Resources (FHIR®) with data normalization and FHIR conversion of the normalized data
20-
* Normalization: device data information is extracted into a common format for further processing
21-
* FHIR Conversion: normalized and grouped data is mapped to FHIR. Observations are created or updated according to configured templates and linked to the device and patient.
19+
* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Healthcare APIs IoT connector managed service. Can be used with any Fast Healthcare Interoperability Resources (FHIR®) service that supports [FHIR R7®](https://https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491)
2220

23-
#### Device and FHIR destination mappings authoring and troubleshooting
21+
#### Device and FHIR destination mappings
2422

25-
* [Tools to help build Device and FHIR destination mappings](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): visualize the mapping configuration for normalizing the device input data and transform it to FHIR resources. Developers can use this tool to edit and test Device mappings and FHIR destination mappings. Export them for uploading to IoT connector in the Azure portal.
23+
* [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): Tool for editing, testing, and troubleshooting IoT connector Device and FHIR destination mappings. Export mappings for uploading to IoT connector in the Azure portal or use with the open-source version.
2624

27-
#### HealthKit and FHIR integration
25+
#### Wearables integration
2826

29-
* [microsoft/healthkit-on-fhir](https://github.com/microsoft/healthkit-on-fhir): a Swift library that automates the export of Apple HealthKit Data to a FHIR service.
27+
Fitbit
28+
29+
* [microsoft/fitbit-on-fhir](https://github.com/microsoft/FitbitOnFHIR): Bring Fitbit® data to a FHIR service.
30+
31+
HealthKit
32+
33+
* [microsoft/healthkit-on-fhir](https://github.com/microsoft/healthkit-on-fhir): Bring Apple® HealthKit® data to a FHIR service.
34+
35+
* [microsoft/healthkit-to-fhir](https://github.com/microsoft/healthkit-to-fhir): Provides a simple way to create FHIR Resources from HKObjects
36+
37+
Health Data Sync
38+
39+
* [microsoft/health-data-sync](https://github.com/microsoft/health-data-sync): A Swift library that simplifies and automates the export of HealthKit data to an external store.
3040

3141
## Next steps
3242
Learn how to deploy IoT connector in the Azure portal

0 commit comments

Comments
 (0)