Merge pull request #101982 from CaitlinV39/master

Flow updates

Author: Jak-MS

.openpublishing.redirection.json

@@ -46629,6 +46629,16 @@
       "source_path": "articles/healthcare-apis/tutorial-3-connect-to-endpoint.md",
       "redirect_url": "/azure/healthcare-apis/tutorial-web-app-fhir-server",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/tutorial-1-decision-flow.md",
+      "redirect_url": "/azure/healthcare-apis/fhir-app-registration",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/healthcare-apis/overview-open-source-server.md",
+      "redirect_url": "/azure/healthcare-apis/overview",
+      "redirect_document_id": false
     }
   ]
 }

articles/healthcare-apis/TOC.yml

@@ -4,8 +4,6 @@
   items:
   - name: About Azure API for FHIR
     href: overview.md
-  - name: About FHIR Server for Azure
-    href: overview-open-source-server.md
 - name: Quickstarts
   expanded: true
   items:
@@ -46,7 +44,7 @@
     expanded: false
     items:
     - name: Register applications for Azure API for FHIR overview
-      href: tutorial-1-decision-flow.md
+      href: fhir-app-registration.md
     - name: Resource application
       href: register-resource-azure-ad-client-app.md
     - name: Confidential client application

articles/healthcare-apis/configure-cross-origin-resource-sharing.md

@@ -29,4 +29,11 @@ To configure a CORS setting in the Azure API for FHIR, specify the following set
 ![Cross-origin resource sharing (CORS) settings](media/cors/cors.png)
 
 >[!NOTE]
->You can't specify different settings for different domain origins. All settings (**Headers**, **Methods**, **Max age**, and **Allow credentials**) apply to all origins specified in the Origins setting.
+>You can't specify different settings for different domain origins. All settings (**Headers**, **Methods**, **Max age**, and **Allow credentials**) apply to all origins specified in the Origins setting.
+
+## Next steps
+
+In this article, you learned how to configure cross-origin sharing in Azure API for FHIR. Next deploy a fully managed Azure API for FHIR:
+ 
+>[!div class="nextstepaction"]
+>[Deploy Azure API for FHIR](fhir-paas-portal-quickstart.md)

articles/healthcare-apis/configure-database.md

@@ -19,9 +19,17 @@ Throughput must be provisioned to ensure that sufficient system resources are av
 > [!NOTE]
 > As different operations consume different number of RU, we return the actual number of RUs consumed in every API call in response header. This way you can profile the number of RUs consumed by your application.
 
-To change this setting in the Azure portal, you can navigate to your Azure API for FHIR and open the Database blade, then change the Provisioned throughput to the desired value depending on your performance needs. You can change the value up to a maximum of 10,000 RU/s.* If you need a higher value, contact Azure support.
+## Update throughput
+To change this setting in the Azure portal, navigate to your Azure API for FHIR and open the Database blade. Next, change the Provisioned throughput to the desired value depending on your performance needs. You can change the value up to a maximum of 10,000 RU/s. If you need a higher value, contact Azure support.
 
 > [!NOTE] 
 > Higher value means higher Azure API for FHIR throughput and higher cost of the service.
 
 ![Config Cosmos DB](media/database/database-settings.png)
+
+## Next steps
+
+In this article, you learned how to update your RUs for Azure API for FHIR. Next deploy a fully managed Azure API for FHIR:
+ 
+>[!div class="nextstepaction"]
+>[Deploy Azure API for FHIR](fhir-paas-portal-quickstart.md)

articles/healthcare-apis/tutorial-1-decision-flow.md renamed to articles/healthcare-apis/fhir-app-registration.md

@@ -25,14 +25,10 @@ landingContent:
         links:
           - text: What is Azure API for FHIR?
             url: overview.md
-          - text: What is FHIR Server for Azure?
-            url: overview-open-source-server.md
       - linkListType: quickstart
         links:
           - text: Deploy API Server for FHIR
             url: fhir-paas-portal-quickstart.md 
-          - text: Deploy open source FHIR Server
-            url: fhir-oss-portal-quickstart.md
 
   - title: Set-up tutorials
     linkLists:

articles/healthcare-apis/index.yml

@@ -11,7 +11,7 @@ author: caitlinv39
 ms.date: 01/03/2020
 ---
 
-# Client Application Registration
+# Client application registration
 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 will 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 have called out the major steps for this tutorial below.
 
 1. Navigate to Azure Active Directory
@@ -21,7 +21,7 @@ In the previous tutorial, you deployed and set up your Azure API for FHIR. Now t
 
 ![Client Application Registration](media/tutorial-web-app/reg-public-app.png)
 
-## Client Application Settings
+## Client application settings
 Once your client application is registered, copy the Application (client) ID from the Overview Page. You will need this value later when accessing the client.
 
 ![Copy App ID](media/tutorial-web-app/app-id.png)