Skip to content

Commit 138293c

Browse files
Merge pull request #228798 from msjasteppe/quick-edits
Minor edits
2 parents 7ddd22c + 4a9d2b8 commit 138293c

File tree

2 files changed

+11
-5
lines changed

2 files changed

+11
-5
lines changed

articles/healthcare-apis/iot/get-started.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,17 @@ author: msjasteppe
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: quickstart
8-
ms.date: 1/20/2023
8+
ms.date: 02/27/2023
99
ms.author: jasteppe
1010
ms.custom: mode-api
1111
---
1212

1313
# Get started with the MedTech service in the Azure Health Data Services
1414

15-
This article will show you how to get started with the Azure MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). There are six steps you need to follow to be able to deploy and process MedTech service to ingest data from a device using Azure Event Hubs service, persist the data to Azure Fast Healthcare Interoperability Resources (FHIR®) service as Observation resources, and link FHIR service Observations to user and device resources. This article provides an architecture overview to help you follow the six steps of the implementation process.
15+
> [!NOTE]
16+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17+
18+
This article will show you how to get started with the Azure MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). There are six steps you need to follow to be able to deploy and process MedTech service to ingest data from a device using Azure Event Hubs service, persist the data to Azure FHIR service as Observation resources, and link FHIR service Observations to user and device resources. This article provides an architecture overview to help you follow the six steps of the implementation process.
1619

1720
## Architecture overview of the MedTech service
1821

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

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,14 @@ services: healthcare-apis
55
author: msjasteppe
66
ms.service: healthcare-apis
77
ms.topic: reference
8-
ms.date: 1/12/2023
8+
ms.date: 02/27/2023
99
ms.author: jasteppe
1010
---
1111
# Open-source projects
1212

13+
> [!NOTE]
14+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
15+
1316
Check out our open-source projects on GitHub that provide source code and instructions to deploy services for various uses with the MedTech service.
1417

1518
> [!IMPORTANT]
@@ -19,11 +22,11 @@ Check out our open-source projects on GitHub that provide source code and instru
1922

2023
### FHIR integration
2124

22-
* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Health Data Services MedTech service managed service. Can be used with any Fast Healthcare Interoperability Resources (FHIR®) service that supports [FHIR R4®](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491)
25+
* [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Health Data Services MedTech service managed service. Can be used with any FHIR service that supports [FHIR R4®](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491)
2326

2427
### Device and FHIR destination mappings
2528

26-
* [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): Tool for editing, testing, and troubleshooting MedTech service Device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the open-source version.
29+
* [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): Tool for editing, testing, and troubleshooting MedTech service device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the open-source version.
2730

2831
### Wearables integration
2932

0 commit comments

Comments
 (0)