Skip to content

Commit 6a54fc3

Browse files
authored
Merge pull request #204949 from mcevoy-building7/get-started-iot-02
Azure branding
2 parents f3bf243 + eaaeecf commit 6a54fc3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ ms.custom: mode-api
1212

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

15-
This article outlines the basic steps to get started with MedTech service in [Azure Health Data Services](../healthcare-apis-overview.md). MedTech service first processes data that has been sent to an event hub from a medical device, and then saves the data to the Fast Healthcare Interoperability Resources (FHIR®) service as Observation resources. This procedure makes it possible to link the FHIR service Observation to patient and device resources.
15+
This article outlines the basic steps to get started with Azure MedTech service in [Azure Health Data Services](../healthcare-apis-overview.md). MedTech service ingests health data from a medical device using Azure Event Hubs service. It then persists the data to the Azure Fast Healthcare Interoperability Resources (FHIR®) service as Observation resources. This data processing procedure makes it possible to link FHIR service Observations to patient and device resources.
1616

17-
The following diagram shows the four development steps of the data flow needed to get MedTech service to receive data from a device and send it to FHIR service.
17+
The following diagram shows the four-step data flow that enables MedTech service to receive data from a device and send it to FHIR service.
1818

1919
- Step 1 introduces the subscription and permissions prerequisites needed.
2020

0 commit comments

Comments
 (0)