Major update to Get Started

Author: msjasteppe

articles/healthcare-apis/iot/deploy-new-choose.md

@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-arm-template
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/20/2023
 ms.author: jasteppe
 ---
 
@@ -52,11 +52,11 @@ Using the Azure portal manual deployment will allow you to see the details of ea
 
 To learn more about deploying the MedTech service manually using the Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
 
-## Deployment architecture overview
+## Deployment overview
 
 The following diagram outlines the basic steps of the MedTech service deployment and shows how these steps fit together with its data processing procedures. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
 
-:::image type="content" source="media/get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architecture overview." lightbox="media/get-started/get-started-with-iot.png":::
+:::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
 
 > [!IMPORTANT]
 > If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.

articles/healthcare-apis/iot/deploy-new-manual.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 03/10/2022
+ms.date: 04/19/2022
 ms.author: jasteppe
 ---
 
@@ -22,7 +22,7 @@ The explanation of the MedTech service manual deployment using the Azure portal
 - Part 2: Configuration (see [Configure for manual deployment](deploy-new-config.md))
 - Part 3: Deployment and Post Deployment (see [Manual deployment and post-deployment](deploy-new-deploy.md))
 
-If you need a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-new-choose.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a FHIR Observation.
+If you need a diagram with information on the MedTech service deployment, there's an overview at [Choose a deployment method](deploy-new-choose.md#deployment-overview). This diagram shows the steps of deployment and how MedTech service processes device data into FHIR Observations.
 
 ## Part 1: Prerequisites
 

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

@@ -5,7 +5,7 @@ services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 04/14/2023
+ms.date: 04/20/2023
 ms.author: jasteppe
 ---
 # Open-source projects
@@ -22,7 +22,7 @@ Check out our open-source projects on GitHub that provide source code and instru
 
 ### FHIR integration
 
-* [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)
+* [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](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491)
 
 ### Wearables integration
 

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

@@ -1,19 +1,19 @@
 ### YamlMime:Landing
 
 title: MedTech service documentation
-summary: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
+summary: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
 
 metadata:
   title: Azure Health Data Services MedTech service
-  description: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. 
+  description: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. 
   services: healthcare-apis
   ms.service: healthcare-apis
   ms.subservice: data-transformation
   ms.topic: landing-page 
   ms.collection: collection
   author: msjasteppe
   ms.author: jasteppe
-  ms.date: 04/04/2023
+  ms.date: 04/20/2023
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -25,7 +25,7 @@ landingContent:
         links:
           - text: What is the MedTech service?
             url: overview.md
-          - text: Overview of the MedTech service device data processing stages
+          - text: Overview of the device data processing stages
             url: overview-of-device-data-processing-stages.md
       - linkListType: quickstart
         links:
@@ -56,14 +56,14 @@ landingContent:
           - text: Device mapping
             url: overview-of-device-mapping.md
           - text: FHIR destination mapping
-            url: how-to-configure-fhir-mappings.md 
+            url: overview-of-fhir-destination-mapping.md 
       - linkListType: how-to-guide
         links:
           - text: Mapping debugger
             url: how-to-use-mapping-debugger.md
-          - text: CalculatedContent
+          - text: CalculatedContent mappings
             url: how-to-use-calculatedcontent-mappings.md
-          - text: IotJsonPathContent
+          - text: IotJsonPathContent mappings
             url: how-to-use-iotjsonpathcontent-mappings.md
           - text: Custom functions
             url: how-to-use-custom-functions.md

articles/healthcare-apis/iot/index.yml

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: overview
-ms.date: 04/14/2023
+ms.date: 04/20/2023
 ms.author: jasteppe
 ---
 
@@ -55,13 +55,13 @@ The MedTech service can be customized and configured by using [device](overview-
 
 Useful options could include:
 
-- Link devices and consumers together for enhanced insights, trend captures, interoperability between systems, and proactive and remote monitoring.
+* Link devices and consumers together for enhanced insights, trend captures, interoperability between systems, and proactive and remote monitoring.
 
-- Update or create FHIR Observations according to existing or new mapping template types.
+* Update or create FHIR Observations according to existing or new mapping template types.
 
-- Choose data terms that work best for your organization and provide consistency in device data ingestion.
+* Choose data terms that work best for your organization and provide consistency in device data ingestion.
 
-- Customize, edit, test, and troubleshoot MedTech service device and FHIR destination mappings with the [Mapping debugger](how-to-use-mapping-debugger.md) tool.
+* Customize, edit, test, and troubleshoot MedTech service device and FHIR destination mappings with the [Mapping debugger](how-to-use-mapping-debugger.md) tool.
 
 ### Scalable
 
@@ -71,21 +71,21 @@ The MedTech service enables you to easily modify and extend the capabilities of
 
 The MedTech service may also be integrated for ingesting device data from these wearables using our [open-source projects](git-projects.md): 
 
-- Fitbit®
+* Fitbit®
 
-- Apple®
+* Apple®
 
-- Google®
+* Google®
 
 The following Microsoft solutions can use MedTech service for extra functionality:
 
-- [**Microsoft Azure IoT Hub**](../../iot-hub/iot-concepts-and-iot-hub.md) - enhances workflow and ease of use.
+* [**Microsoft Azure IoT Hub**](../../iot-hub/iot-concepts-and-iot-hub.md) - enhances workflow and ease of use.
 
-- [**Azure Machine Learning Service**](concepts-machine-learning.md) - helps build, deploy, and manage models, integrate tools, and increase open-source operability.
+* [**Azure Machine Learning Service**](concepts-machine-learning.md) - helps build, deploy, and manage models, integrate tools, and increase open-source operability.
 
-- [**Microsoft Power BI**](concepts-power-bi.md) - enables data visualization features.
+* [**Microsoft Power BI**](concepts-power-bi.md) - enables data visualization features.
 
-- [**Microsoft Teams**](concepts-teams.md) - facilitates virtual visits.
+* [**Microsoft Teams**](concepts-teams.md) - facilitates virtual visits.
 
 ## Next steps
 

articles/healthcare-apis/iot/media/get-started/get-started-with-iot.png

@@ -51,9 +51,9 @@ items:
       items:
       - name: Overview of the device mapping
         href: overview-of-device-mapping.md
-      - name: Use CalculatedContent
+      - name: Use CalculatedContent mappings
         href: how-to-use-calculatedcontent-mappings.md
-      - name: Use IotJsonPathContent
+      - name: Use IotJsonPathContent mappings
         href: how-to-use-iotjsonpathcontent-mappings.md
       - name: Use custom functions
         href: how-to-use-custom-functions.md