FHIR service documentation Update for Postman link removal

Author: Shashank Narang

articles/healthcare-apis/access-healthcare-apis.md

@@ -1,6 +1,6 @@
 ---
 title: Access Azure Health Data Services
-description: Learn how to access the FHIR, DICOM, and MedTech services in Azure Health Data Services by using Postman, cURL, REST Client, and programming languages like Python and C# for efficient data management.
+description: Learn how to access the FHIR, DICOM, and MedTech services in Azure Health Data Services by using cURL, REST Client, and programming languages like Python and C# for efficient data management.
 services: healthcare-apis
 author: EXPEkesheth
 ms.service: azure-health-data-services
@@ -13,11 +13,10 @@ ms.author: kesheth
 
 # Access Azure Health Data Services
 
-After you deploy a FHIR® service, DICOM® service, or MedTech service, you can then access it in your applications by using tools like Postman, cURL, REST Client in Visual Studio Code, or with programming languages such as Python or C#.
+After you deploy a FHIR® service, DICOM® service, or MedTech service, you can then access it in your applications by using tools like cURL, REST Client in Visual Studio Code, or with programming languages such as Python or C#.
 
 ## Access the FHIR service
 
-- [Access the FHIR service by using Postman](././fhir/use-postman.md)
 - [Access the FHIR service by using cURL](././fhir/using-curl.md)
 - [Access the FHIR service by using REST Client](././fhir/using-rest-client.md)
 
@@ -32,7 +31,6 @@ After you deploy a FHIR® service, DICOM® service, or MedTech service, yo
 The MedTech service works with the IoT Hub and Event Hubs to receive message data, and works with the FHIR service to persist the data.
 
 - [Receive device data through Azure IoT Hub](iot/device-data-through-iot-hub.md)
-- [Access the FHIR service by using Postman](fhir/use-postman.md)
 - [Access the FHIR service by using cURL](fhir/using-curl.md)
 - [Access the FHIR service by using REST Client](fhir/using-rest-client.md)
 

articles/healthcare-apis/azure-api-for-fhir/get-healthcare-apis-access-token-cli.md

@@ -35,9 +35,9 @@ curl -X GET --header "Authorization: Bearer $token" https://<FHIR ACCOUNT NAME>.
 
 ## Next steps
 
-In this article, you learned how to obtain an access token for the Azure API for FHIR using the Azure CLI. To learn how to access the FHIR API using Postman, proceed to the Postman tutorial:
+In this article, you learned how to obtain an access token for the Azure API for FHIR using the Azure CLI. To learn how to access the FHIR API using REST Client:
 
 >[!div class="nextstepaction"]
->[Access the FHIR service using Postman](./../fhir/use-postman.md)
+>[Access the FHIR service using REST Client](./../fhir/using-rest-client.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/configure-azure-rbac.md

@@ -62,8 +62,6 @@ In the **Select** box, search for a user, service principal, or group that you w
 
 ## Next steps
 
-[Access by using Postman](./fhir/use-postman.md)
-
 [Access by using the REST Client](./fhir/using-rest-client.md)
 
 [Access by using cURL](./fhir/using-curl.md)

articles/healthcare-apis/fhir/azure-ad-b2c-setup.md

@@ -148,7 +148,7 @@ The B2C resource application handles authentication requests from your healthcar
 
 1. In the **Supported account types** list, choose **Accounts in any identity provider or organizational directory (for authenticating users with user flows)**.
 
-1. In the **Redirect URI (recommended)** drop-down list, select ***Public client/native (mobile & desktop)**. Populate the value with the [Postman](https://www.postman.com) callback URI [https://oauth.pstmn.io/v1/callback](#create-a-new-b2c-resource-application). This callback URI is for testing purposes.
+1. In the **Redirect URI (recommended)** drop-down list, select ***Public client/native (mobile & desktop)**. Populate the value with the callback URI. This callback URI is for testing purposes. 
 
 1. In the **Permissions** section, select **Grant admin consent to openid and offline_access permissions**.
 
@@ -295,13 +295,13 @@ az deployment group create --resource-group $resourcegroupname --template-uri ht
 
 ## Validate Azure AD B2C users are able to access FHIR resources
 
-The validation process involves creating a patient resource in the FHIR service, linking the patient resource to the Azure AD B2C user, and configuring Postman to get an access token for B2C users. After the validation process is complete, you can fetch the patient resource by using the B2C test user.
+The validation process involves creating a patient resource in the FHIR service, linking the patient resource to the Azure AD B2C user, and configuring REST Client to get an access token for B2C users. After the validation process is complete, you can fetch the patient resource by using the B2C test user.
 
-#### Run Postman to get an access token
+#### Use REST Client to get an access token
 
-Run the [Postman](https://www.postman.com) application locally or in a web browser. For steps to obtain the proper access to the FHIR service, see [Access the FHIR service using Postman](use-postman.md).
+For steps to obtain the proper access to the FHIR service, see [Access the FHIR service using REST Client](using-rest-client.md).
 
-When you follow the steps in the [Get the FHIR resource](use-postman.md#get-the-fhir-resource) section, the request returns an empty response because the FHIR service is new and doesn't have any patient resources.
+When you follow the steps in the [Get the FHIR patient data](using-rest-client.md#get-fhir-patient-data) section, the request returns an empty response because the FHIR service is new and doesn't have any patient resources.
 
 #### Create a patient resource in the FHIR service
 
@@ -380,28 +380,24 @@ Create an explicit link between the test user in the B2C tenant and the resource
 
    :::image type="content" source="media/azure-ad-b2c-setup/graph-patch-sml.png" alt-text="Screenshot showing Graph patch." lightbox="media/azure-ad-b2c-setup/graph-patch-lrg.png":::
 
-#### Configure Postman to obtain an access token for B2C users
+#### Configuration to obtain an access token for B2C users
 
-Obtain an access token to test the authentication flow.
+Obtain an access token to test the authentication flow. 
 
-1. Launch the Postman application, and then create a new **Blank collection**. In this example, the collection is named **FHIR Patient**.
+>[!Note] 
+>The `grant_type` of `authorization_code` is used to obtain an access token.
+>There are tools available online offering intuitive interfaces for API testing and development.
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-new-collection-sml.png" alt-text="Screenshot showing Postman new collection." lightbox="media/azure-ad-b2c-setup/postman-new-collection-lrg.png":::
+1. Launch the API testing application.
 
-1. Select the **Authorization** tab in the collection overview.
+1. Select the **Authorization** tab in the tool.
 
 1. In the **Type** dropdown list, select **OAuth 2.0**.
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-auth.png" alt-text="Screenshot showing Postman auth." lightbox="media/azure-ad-b2c-setup/postman-auth.png":::
-
-1. Scroll to the **Configure New Token** section and enter the following values.
+1. Enter the following values.
 
    - **Callback URL**. This value is configured when the B2C resource application is created.
 
-      ```http
-      https://oauth.pstmn.io/v1/callback
-      ```
-
    - **Auth URL**. This value can be created using the name of the B2C tenant and the name of the user flow.
 
       ```http
@@ -428,36 +424,26 @@ Obtain an access token to test the authentication flow.
       {YOUR_APPLICATION_ID_URI}/patient.all.read
       ```
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-urls.png" alt-text="Screenshot showing Postman URLs." lightbox="media/azure-ad-b2c-setup/postman-urls.png":::
-
 #### Fetch the patient resource by using the B2C user
 
 Verify that Azure AD B2C users can access FHIR resources.
 
-1. When the authorization configuration in Postman is set up to launch the B2C user flow, choose **Get New Access Token** to get an access token.
-
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-get-token-3.png" alt-text="Screenshot showing Postman get access token." lightbox="media/azure-ad-b2c-setup/postman-get-token-3.png":::
+1. When the authorization configuration is set up to launch the B2C user flow, choose **Get New Access Token** to get an access token.
 
 1. Use the **Test Patient** credentials to sign in.
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-get-token-2.png" alt-text="Screenshot showing Postman get token." lightbox="media/azure-ad-b2c-setup/postman-get-token-2.png":::
-
-1. Choose **Use Token** to use the access token for any requests in the collection.
+1. Copy the access token and use it in fetching the Patient data
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-use-token.png" alt-text="Screenshot showing Postman use token." lightbox="media/azure-ad-b2c-setup/postman-use-token.png":::
+Follow the steps in the [Get the FHIR patient data](using-rest-client.md#get-fhir-patient-data) to fetch the patient resource.
 
-1. Create a new request to search for patient resources in the FHIR service. Select the ellipsis button (...) next to the name of the collection, and then choose **Add request**.
+1. Set the method to `GET`, enter the fully qualified FHIR service URL, and then add the path `/Patient`.
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-request-1-sml.png" alt-text="Screenshot showing Postman request added." lightbox="media/azure-ad-b2c-setup/postman-request-1-lrg.png":::
+1. Use the fetched token in the authorization parameter.
 
-1. Set the method to `GET`, enter the fully qualified FHIR service URL, and then add the path `/Patient`. 
-
-1. Choose **Send**.
+1. Choose **Send Request**.
 
 1. Verify that the response contains the single patient resource.
 
-   :::image type="content" source="media/azure-ad-b2c-setup/postman-request-2.png" alt-text="Screenshot showing Postman request response." lightbox="media/azure-ad-b2c-setup/postman-request-2.png":::
-
 ## Next steps
 
 [Configure multiple identity providers](configure-identity-providers.md)

articles/healthcare-apis/fhir/convert-data-faq.md

@@ -36,11 +36,11 @@ There's an example published in the [Azure Data Factory template gallery](../../
 >
 > In a scenario with batch processing of HL7v2 messages, this template doesn't take sequencing into account. Post processing is needed if sequencing is a requirement. 
 
-## How can I persist the converted data into the FHIR service by using Postman?
+## How can I persist the converted data into the FHIR service?
 
 You can use the FHIR service's APIs to persist the converted data into the FHIR service by using `POST {{fhirUrl}}/{{FHIR resource type}}` with the request body containing the FHIR resource to be persisted in JSON format. 
 
-For more information, see [Access the FHIR service in Azure Health Data Services by using Postman](use-postman.md).
+For more information, see [Access the FHIR service in Azure Health Data Services by using REST Client](using-rest-client.md).
 
 ## What's the difference between the $convert-data endpoint in Azure API for FHIR versus the FHIR service in Azure Health Data Services?
 

articles/healthcare-apis/fhir/deploy-azure-portal.md

@@ -71,7 +71,7 @@ To replicate settings between FHIR instance, you can follow below steps
 
 ## Related content
 
-[Access the FHIR service by using Postman](../fhir/use-postman.md)
+[Access the FHIR service](../fhir/get-started-with-fhir.md#access-the-fhir-service)
 
 [!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
 

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

@@ -57,9 +57,9 @@ You can obtain a Microsoft Entra access token by using PowerShell, Azure CLI, RE
 
 #### Access using existing tools
 
-- [Postman](../fhir/use-postman.md)
 - [REST Client](../fhir/using-rest-client.md)
 - [cURL](../fhir/using-curl.md)
+- There are tools available online offering intuitive interfaces for API testing and development such as Postman for example. To use tools for accessing the FHIR service, refer to the open-source sample. [Starter collection of Postman sample queries](https://github.com/Azure-Samples/azure-health-data-services-samples/tree/main/samples/sample-postman-queries) 
 
 #### Load data
 

articles/healthcare-apis/fhir/index.yml

@@ -40,8 +40,8 @@ landingContent:
             url: fhir-service-access-token-validation.md
       - linkListType: tutorial
         links:
-          - text: Access using Postman
-            url: ./../fhir/use-postman.md
+          - text: Access using REST Client
+            url: ./../fhir/using-rest-client.md
   - title: FHIR search capabilities
     linkLists:
       - linkListType: overview

articles/healthcare-apis/fhir/migration-strategies.md

@@ -98,7 +98,7 @@ Migrate applications that were pointing to the old FHIR server.
 
 - After migration, reconfigure any remaining settings in the new Azure Health Data Services FHIR service server.
 
-- If you’d like to double check that the Azure Health Data Services FHIR service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](use-postman.md#get-the-capability-statement) to compare the two servers.
+- If you’d like to double check that the Azure Health Data Services FHIR service and Azure API for FHIR servers have the same configurations, you can check both metadata endpoints to compare the two servers.
 
 - Set up any jobs that were previously running in your old Azure API for FHIR server (for example, `$export` jobs)
 

articles/healthcare-apis/fhir/smart-on-fhir.md

@@ -105,7 +105,7 @@ Add the reply URL to the public client application that you created previously f
 
 ### Step 3:  Get a test patient
 
-To test the FHIR service and the SMART on FHIR proxy, you need to have at least one patient in the database. If you've not used the API yet, and you don't have data in the database, see [Access the FHIR service using Postman](./../fhir/use-postman.md) to load a patient. Make a note of the ID of a specific patient.
+To test the FHIR service and the SMART on FHIR proxy, you need to have at least one patient in the database. If you've not used the API yet, and you don't have data in the database, see [Access the FHIR service using REST Client](./../fhir/using-rest-client.md) to load a patient. Make a note of the ID of a specific patient.
 
 ### Step 4:  Download the SMART on FHIR app launcher