Merge pull request #230279 from msjasteppe/minor-updates

Minor updates

Author: prmerger-automator[bot]

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

@@ -5,12 +5,15 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 1/5/2023
+ms.date: 03/10/2023
 ms.author: jasteppe
 ---
 
 # Quickstart: Part 2: Configure the MedTech service for manual deployment using the Azure portal
 
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
 Before you can manually deploy the MedTech service, you must complete the following configuration tasks:
 
 ## Set up the MedTech service configuration
@@ -94,7 +97,7 @@ To begin configuring the device mapping tab, go to the Create MedTech service pa
 
 For more information regarding device mappings, see the relevant GitHub open source documentation at [Device Content Mapping](https://github.com/microsoft/iomt-fhir/blob/master/docs/Configuration.md#device-content-mapping).
 
-For Azure docs information about device mapping, see [How to configure device mappings](how-to-configure-device-mappings.md).
+For Azure docs information about the device mapping, see [How to configure the MedTech service device mapping](how-to-configure-device-mappings.md).
 
 ## Configure the Destination tab
 
@@ -109,7 +112,7 @@ To begin configuring destination mapping, go to the Create MedTech service page
 
 Under the **Destination** tab, use these values to enter the destination properties for your MedTech service instance:
 
-- First, enter the name of your **Fast Healthcare Interoperability Resources (FHIR®) server** using the following four steps:
+- First, enter the name of your **FHIR server** using the following four steps:
 
   1. The **FHIR Server** name (also known as the **FHIR service**) can be located by using the **Search** bar at the top of the screen. 
   1. To connect to your FHIR service instance, enter the name of the FHIR service you used in the manual deploy configuration article at [Deploy the FHIR service](deploy-new-manual.md#deploy-the-fhir-service).
@@ -189,7 +192,7 @@ If your MedTech service didn't validate, review the validation failure message,
 
 ## Continue on to Part 3: Deployment and post-deployment
 
-After your configuration is successfully completed, you can go on to Part 3: Deployment and post deployment. See **Next steps** below.
+After your configuration is successfully completed, you can go on to Part 3: Deployment and post deployment. See **Next steps**.
 
 ## Next steps
 

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

@@ -5,12 +5,15 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 1/5/2023
+ms.date: 03/10/2023
 ms.author: jasteppe
 ---
 
 # Quickstart: Part 3: Manual deployment and post-deployment of the MedTech service
 
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
 When you're satisfied with your configuration and it has been successfully validated, you can complete the deployment and post-deployment process.
 
 ## Create your manual deployment
@@ -35,7 +38,7 @@ Your screen should look something like this:
 There are two post-deployment steps you must perform or the MedTech service can't:
 
 1. Read device data from the device message event hub. 
-2. Read or write to the Fast Healthcare Interoperability Resources (FHIR®) service. 
+2. Read or write to the FHIR service. 
 
 These steps are:
 

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

@@ -5,12 +5,15 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 11/29/2022
+ms.date: 03/10/2022
 ms.author: jasteppe
 ---
 
 # Quickstart: Deploy the MedTech service manually using the Azure portal
 
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
 You may prefer to manually deploy the MedTech service if you need to track every step of the developmental process. Manual deployment might be necessary if you have to customize or troubleshoot your deployment. Manual deployment will help you by providing all the details for implementing each task.
 
 The explanation of the MedTech service manual deployment using the Azure portal is divided into three parts that cover each of key tasks required:
@@ -19,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 Fast Healthcare Interoperability Resources (FHIR®) Observation.
+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.
 
 ## Part 1: Prerequisites
 
@@ -88,7 +91,7 @@ After you have deployed FHIR service, it will be ready to receive the data proce
 
 ## Continue on to Part 2: Configuration
 
-After your prerequisites are successfully completed, you can go on to Part 2: Configuration. See **Next steps** below.
+After your prerequisites are successfully completed, you can go on to Part 2: Configuration. See **Next steps**.
 
 ## Next steps