Skip to content

Commit 7b842d6

Browse files
committed
Updates based on feedback.
1 parent 4f9b999 commit 7b842d6

File tree

1 file changed

+3
-13
lines changed

1 file changed

+3
-13
lines changed

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

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: msjasteppe
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: quickstart
8-
ms.date: 04/20/2023
8+
ms.date: 04/21/2023
99
ms.author: jasteppe
1010
ms.custom: mode-api
1111
---
@@ -17,23 +17,13 @@ ms.custom: mode-api
1717
1818
This article and diagram outlines the basic steps to get started with the MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). These basic steps may help you analyze the MedTech service deployment options and determine which deployment method is best for you.
1919

20+
As a prerequisite, you need an Azure subscription and have been granted proper permissions to create Azure resource groups and deploy Azure resources. You can follow all the steps, or skip some if you have an existing environment. Also, you can combine all the steps and complete them in Azure PowerShell, Azure CLI, and REST API scripts.
21+
2022
:::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing the MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
2123

2224
> [!TIP]
2325
> See the MedTech service article, [Quickstart: Choose a deployment method for the MedTech service](deploy-new-choose.md), for a description of the different deployment methods that can help to simply and automate the deployment of the MedTech service.
2426
25-
## Subscription prerequisites
26-
27-
To begin the deployment, you need to determine if you have:
28-
29-
* An active Azure subscription.
30-
* Azure role-based access control (Azure RBAC) role assignments at the subscription level for deploying resources and granting access permissions. The roles required for you to complete the deployment are: **Contributor and User Access Administrator** or **Owner**. The **Contributor** role allows you to deploy resources, and the **User Access Administrator** role allows you to grant access between resources. The **Owner** role can perform both actions.
31-
32-
If you already have the appropriate active subscription and Azure RBAC role assignments, you can skip this section.
33-
34-
* If you don't have an active Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).
35-
* If you don't have the correct Azure RBAC role assignments, see [Azure role-based access control (RBAC)](/azure/cloud-adoption-framework/ready/considerations/roles).
36-
3727
## Deploy resources
3828

3929
After you obtain the required subscription prerequisites, the first step is to deploy the MedTech service prerequisite resources:

0 commit comments

Comments
 (0)