Merge pull request #288041 from KendalBond007/APIforFHIRbatch12_Oct24

APIforFHIRbatch12_Oct24

Author: denrea

articles/healthcare-apis/azure-api-for-fhir/tutorial-member-match.md

@@ -10,48 +10,46 @@ author: expekesheth
 ms.date: 09/27/2023
 ---
 
-# $member-match operation for Azure API for FHIR
+# Use the $member-match operation for Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-[$member-match](http://hl7.org/fhir/us/davinci-hrex/2020Sep/OperationDefinition-member-match.html) is an operation that is defined as part of the Da Vinci Health Record Exchange (HRex). In this guide, we'll walk through what $member-match is and how to use it.
+[$member-match](http://hl7.org/fhir/us/davinci-hrex/2020Sep/OperationDefinition-member-match.html) is an operation that is defined as part of the Da Vinci Health Record Exchange (HRex). In this guide, we walk through what `$member-match` is and how to use it.
 
 ## Overview of $member-match
 
-The $member-match operation was created to help with the payer-to-payer data exchange, by allowing a new payer to get a unique identifier for a patient from the patient’s previous payer. The $member-match operation
-requires three pieces of information to be passed in the body of the request:
+The `$member-match` operation was created to help with the payer-to-payer data exchange, by allowing a new payer to get a unique identifier for a patient from the patient’s previous payer. The `$member-match` operation requires three pieces of information to be passed in the body of the request:
 
 * Patient demographics
 
 * The old coverage information
 
 * The new coverage information (not required based on our implementation)
 
-After the data is passed in, the Azure API for FHIR validates that it can find a patient that exactly matches the demographics passed in with the old coverage information passed in. If a result is found, the response will be a bundle with the original patient data plus a new identifier added in from the old payer, and the old coverage information.
+After the data is passed in, the Azure API for FHIR validates that it can find a patient that exactly matches the demographics passed in with the old coverage information passed in. If a result is found, the response is a bundle with the original patient data plus a new identifier added in from the old payer, and the old coverage information.
 
 > [!NOTE]
-> The specification describes passing in and back the new
-coverage information. We've decided to omit that data to keep the results smaller.
+> The specification describes passing the new coverage information in and back. We've decided to omit that data to keep the results smaller.
 
 ## Example of $member-match
 
-To use $member-match, use the following call:
+To use `$member-match`, use the following call.
 
 `POST {{fhirurl}}/Patient/$member-match`
 
-You'll need to include a parameters resource in the body that includes the patient, the old coverage, and the new coverage. To see a JSON representation, see [$member-match example request](http://hl7.org/fhir/us/davinci-hrex/2020Sep/Parameters-member-match-in.json.html).
+You need to include a parameters resource in the body that includes the patient, the old coverage, and the new coverage. For a JSON representation, see [$member-match example request](http://hl7.org/fhir/us/davinci-hrex/2020Sep/Parameters-member-match-in.json.html).
 
-If a single match is found, you'll receive a 200 response with another identifier added:
+If a single match is found, you receive a 200 response with another identifier added.
 
 :::image type="content" source="media/cms-tutorials/two-hundred-response.png" alt-text="200 hundred response code.":::
 
-If the $member-match can't find a unique match, you'll receive a 422 response with an error code.
+If the `$member-match` can't find a unique match, you receive a 422 response with an error code.
 
 ## Next steps
 
-In this guide, you've learned about the $member-match operation. Next, you can learn about testing the Da Vinci Payer Data Exchange IG in Touchstone, which requires the $member-match operation.
+In this guide, you learned about the `$member-match` operation. Next, you can learn about testing the Da Vinci Payer Data Exchange IG in Touchstone, which requires the `$member-match` operation.
 
 >[!div class="nextstepaction"]
 >[DaVinci PDex](../fhir/davinci-pdex-tutorial.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-fhir-server.md

@@ -12,11 +12,11 @@ ms.custom: devx-track-js
 
 ---
 
-# Deploy JavaScript app to read data from Azure API for FHIR
+# Deploy a JavaScript app to read data from Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In this tutorial, you'll deploy a small JavaScript app, which reads data from a FHIR service. The steps in this tutorial are:
+In this tutorial, you deploy a small JavaScript app which reads data from a FHIR service. The steps in this tutorial are:
 
 1. Deploy a FHIR server
 1. Register a public client application
@@ -25,7 +25,7 @@ In this tutorial, you'll deploy a small JavaScript app, which reads data from a
 
 ## Prerequisites
 
-Before starting this set of tutorials, you'll need the following items:
+You need the following before starting this set of tutorials.
 1. An Azure subscription
 1. A Microsoft Entra tenant
 1. [Postman](https://www.getpostman.com/) installed
@@ -51,4 +51,4 @@ Now that you have your Azure API for FHIR deployed, you're ready to register a p
 >[!div class="nextstepaction"]
 >[Register public client application](tutorial-web-app-public-app-reg.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-public-app-reg.md

@@ -12,9 +12,9 @@ ms.date: 09/27/2023
 
 # Client application registration for Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In the previous tutorial, you deployed and set up your Azure API for FHIR. Now that you have your Azure API for FHIR setup, we’ll register a public client application. You can read through the full [register a public client app](register-public-azure-ad-client-app.md) how-to guide for more details or troubleshooting, but we’ve called out the major steps for this tutorial in this article.
+In the previous tutorial, you deployed and set up your Azure API for FHIR®. Now that you have your Azure API for FHIR setup, we register a public client application. You can read through the full [register a public client app](register-public-azure-ad-client-app.md) how-to guide for more details or troubleshooting. We call out the major steps in this tutorial.
 
 1. Navigate to Microsoft Entra ID
 1. Select **App Registration** --> **New Registration**
@@ -37,15 +37,15 @@ If you’ve [written your web app](tutorial-web-app-write-web-app.md) to connect
 
 1. To add a new platform configuration, select **Web**.
 
-1. Set up the redirect URI in preparation for when you create your web application in the fourth part of this tutorial. To do this, add `https://\<WEB-APP-NAME>.azurewebsites.net` to the redirect URI list. If you choose a different name during the step where you [write your web app](tutorial-web-app-write-web-app.md), you’ll need to come back and update this.
+1. Set up the redirect URI in preparation for when you create your web application. To do this, add `https://\<WEB-APP-NAME>.azurewebsites.net` to the redirect URI list. If you choose a different name during the step where you [write your web app](tutorial-web-app-write-web-app.md), you’ll need to come back and update this.
 
 1. Select the **Access Token** and **ID token** check boxes.
 
    :::image type="content" source="media/tutorial-web-app/web-app-authentication.png" alt-text="Screenshot of the app Authentication settings blade, with the steps to add a platform highlighted.":::
 
 ## Add API permissions
 
-Now that you have set up the correct authentication, set the API permissions:
+Now that you have set up the correct authentication, set the API permissions.
 
 1. Select **API permissions** and select **Add a permission**.
 1. Under **APIs my organization uses**, search for Azure Health Data Services.
@@ -60,4 +60,4 @@ You now have a public client application. In the next tutorial, we’ll walk thr
 >[!div class="nextstepaction"]
 >[Test client application in Postman](tutorial-web-app-test-postman.md)
 
-FHIR&#174; is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-test-postman.md

@@ -12,25 +12,26 @@ ms.date: 09/27/2023
 
 # Testing the FHIR API on Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In the previous tutorial, you deployed the Azure API for FHIR and registered your client application. You're now ready to test your Azure API for FHIR.
+In the previous tutorial, you deployed the Azure API for FHIR® and registered your client application. You're now ready to test your Azure API for FHIR.
 
-## Retrieve capability statement
+## Retrieve the capability statement
 
-First we'll get the capability statement for your Azure API for FHIR.
+First we get the capability statement for your Azure API for FHIR.
 1. Open Postman.
-1. Retrieve the capability statement by doing `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/metadata`. In the image below the FHIR server name is **fhirserver**.
+1. Retrieve the capability statement by using `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/metadata`. In the image below the FHIR server name is **fhirserver**.
 
 ![Capability Statement](media/tutorial-web-app/postman-capability-statement.png)
 
-Next we'll attempt to retrieve a patient. To retrieve a patient, enter `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/Patient`. You’ll receive a 401 Unauthorized error. This error is because you haven't proven that you should have access to patient data.
-
-## Get patient from FHIR server
+Next we attempt to retrieve a patient. To retrieve a patient, use `GET https://\<FHIR-SERVER-NAME>.azurehealthcareapis.com/Patient`. You receive a `401 Unauthorized` error because you haven't proven you should have access to patient data.
 
 ![Failed Patient](media/tutorial-web-app/postman-patient-authorization-failed.png)
 
+## Get patient from FHIR server
+
 In order to gain access, you need an access token.
+
 1. Select **Authorization** and set the Type to **OAuth2.0** in Postman.
 1. Select **Get New Access Token**.
 1. Fill in the fields and select **Request Token**. Below you can see the values for each field for this tutorial.
@@ -50,12 +51,13 @@ In order to gain access, you need an access token.
 
 4. Sign in with your credentials and select **Accept**
 1. Scroll down on the result and select **Use Token**
-1. Select **Send** again at the top and this time you should get a result
+1. Select **Send** again at the top and this time you should get a result:
+
 ![Success Patient](media/tutorial-web-app/postman-patient-authorization-success.png)
 
 ## Post patient into FHIR server
 
-Now you have access, you can create a new patient. Here's a sample of a simple patient you can add into your FHIR server. Enter this `json` into the **Body** section of Postman.
+Now that you have access, you can create a new patient. Here's a sample of a simple patient you can add into your FHIR server. Enter this `json` into the **Body** section of Postman.
 
 ``` json
     {
@@ -81,10 +83,11 @@ Now you have access, you can create a new patient. Here's a sample of a simple p
         "birthDate": "1960-12-25"
     }
 ```
-This POST will create a new patient in your FHIR server with the name James Tiberious Kirk.
+This POST creates a new patient in your FHIR server with the name James Tiberious Kirk.
+
 ![Post Patient](media/tutorial-web-app/postman-post-patient.png)
 
-If you do the GET command to retrieve a patient again, you'll see James Tiberious Kirk listed in the output.
+If you use the GET command to retrieve a patient again, you'll see James Tiberious Kirk listed in the output.
 
 > [!NOTE]
 > When sending requests to the Azure API for FHIR, you need to ensure that you've set the content-type header to `application/json`
@@ -103,4 +106,4 @@ Now that you can successfully connect to your client application, you’re ready
 >[!div class="nextstepaction"]
 >[Write a web application](tutorial-web-app-write-web-app.md)
 
-FHIR&#174; is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-write-web-app.md

@@ -10,21 +10,21 @@ author: expekesheth
 ms.date: 09/27/2023
 ---
 
-# Write Azure web application to read FHIR data in Azure API for FHIR
+# Write an Azure web application to read FHIR data in Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-Now that you're able to connect to your FHIR server and POST data, you’re ready to write a web application that will read FHIR data. In this final step of the tutorial, we’ll walk through writing and accessing the web application.
+Once you're able to connect to your FHIR® server and POST data, you’re ready to write a web application that will read FHIR data. In this final step of the tutorial, we walk through writing and accessing the web application.
 
 ## Create web application
-In Azure, select **Create a resource** and select **Web App**. Make sure to name your web application whatever you specified in the redirect URI for your client application or go back and update the redirect URI with the new name. 
+In Azure, select **Create a resource** and select **Web App**. Make sure to name your web application whatever you specified in the redirect URI for your client application, or go back and update the redirect URI with the new name. 
 
 ![Create Web Application](media/tutorial-web-app/create-web-app.png)
 
-Once the web application is available, **Go to resource**. Select **App Service Editor (Preview)** under Development Tools on the right and then select **Go**. Selecting Go will open up the App Service Editor. Right select in the grey space under *Explore* and create a new file called **index.html**.
+Once the web application is available, select **Go to resource**. Select **App Service Editor (Preview)** under Development Tools on the right and then select **Go**. Selecting **Go** opens up the App Service Editor. Right select in the grey space under *Explore* and create a new file called **index.html**.
 
-Included is the code that you can input into **index.html**. You’ll need to update the following items:
-* **clientId** - Update with your client application ID. This ID will be the same ID you pulled when retrieving your token
+The following is code you can input into **index.html**. You’ll need to update the following items.
+* **clientId** - Update with your client application ID. This ID is the same ID you pulled when retrieving your token
 * **authority** - Update with your Microsoft Entra tenant ID
 * **FHIRendpoint** - Update the FHIRendpoint to have your FHIR service name
 * **scopes** - Update to reflect the full URL for your audience
@@ -146,9 +146,9 @@ From here, you can go back to your web application resource and open the URL fou
 
 ## Next Steps
 
-You’ve successfully deployed the Azure API for FHIR, registered a public client application, tested access, and created a small web application. Check out the Azure API for FHIR supported features as a next step.
+You’ve successfully deployed the Azure API for FHIR, registered a public client application, tested access, and created a small web application. As a next step, check out the Azure API for FHIR supported features.
 
 >[!div class="nextstepaction"]
 >[Supported Features](fhir-features-supported.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/use-custom-headers.md

@@ -12,13 +12,13 @@ ms.date: 09/27/2023
 
  # Add custom HTTP headers to audit logs in FHIR service 
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-[!INCLUDE [Specific IP ranges for storage account](../includes/custom-header-auditlog.md)]
+[!INCLUDE[Specific IP ranges for storage account](../includes/custom-header-auditlog.md)]
 
 ## Next steps
 
-In this article, you learned how to add data to audit logs by using custom headers in the Azure API for FHIR. For information about Azure API for FHIR configuration settings, see
+In this article, you learned how to add data to audit logs by using custom headers in the Azure API for FHIR®. For information about Azure API for FHIR configuration settings, see
 
 >[!div class="nextstepaction"]
 >[Configure Azure RBAC](configure-azure-rbac.md)
@@ -38,5 +38,4 @@ In this article, you learned how to add data to audit logs by using custom heade
 >[!div class="nextstepaction"]
 >[Configure Private Link](configure-private-link.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
-
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]