Skip to content

Commit bb2db8f

Browse files
authored
Merge pull request #279442 from v-nikitaraut/docs-editor/register-application
Docs editor/register application
2 parents 96f6b4f + 97e417a commit bb2db8f

File tree

6 files changed

+10
-8
lines changed

6 files changed

+10
-8
lines changed
41.5 KB
Loading

articles/healthcare-apis/fhir/configure-import-data.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ To enable a managed identity on the FHIR service:
3131

3232
After you enable the managed identity, a system-assigned GUID value appears.
3333

34-
[![Screenshot that shows selections for enabling a managed identity for the FHIR service.](media/export-data/fhir-mi-enabled.png)](media/export-data/fhir-mi-enabled.png#lightbox)
34+
![Screenshot that shows selections for enabling a managed identity for the FHIR service.](media/configure-import-data/fhir-managed-identity-enabled.png)
3535

3636
## Step 2: Assign permissions to the FHIR service
3737

@@ -44,7 +44,7 @@ Use the following steps to assign permissions to access the storage account:
4444
3. Add the [Storage Blob Data Contributor](../../role-based-access-control/built-in-roles.md#storage-blob-data-contributor) role to the FHIR service.
4545
4. Select **Save**.
4646

47-
[![Screenshot of the page for adding a role assignment.](media/bulk-import/add-role-assignment-page.png)](media/bulk-import/add-role-assignment-page.png#lightbox)
47+
![Screenshot of the page for adding a role assignment.](media/configure-import-data/add-role-assignment-page.png)
4848

4949
Now you're ready to select the storage account for import.
5050

@@ -60,7 +60,7 @@ For this step, you need to get the request URL and JSON body:
6060
3. Select **JSON View**.
6161
4. Select the API version as **2022-06-01** or later.
6262

63-
To specify the Azure storage account in JSON view, you need to use the [REST API](/rest/api/healthcareapis/services/create-or-update) to update the FHIR service.
63+
To specify the Azure storage account in JSON view, you need to use the [REST API](/rest/api/healthcareapis/fhir-services/create-or-update) to update the FHIR service.
6464

6565
[![Screenshot of selections for opening the JSON view.](media/bulk-import/fhir-json-view.png)](media/bulk-import/fhir-json-view.png#lightbox)
6666

@@ -111,13 +111,13 @@ To securely import FHIR data into the FHIR service from an Azure Data Lake Stora
111111
1. On the **Firewalls and virtual networks** tab, select **Enabled from selected virtual networks and IP addresses**.
112112

113113
[![Screenshot of Azure Storage networking settings.](media/export-data/storage-networking-1.png)](media/export-data/storage-networking-1.png#lightbox)
114-
114+
115115
1. In the **Resource type** dropdown list, select **Microsoft.HealthcareApis/workspaces**. In the **Instance name** dropdown list, select your workspace.
116116

117117
1. In the **Exceptions** section, select the **Allow trusted Microsoft services to access this storage account** checkbox.
118118

119119
[![Screenshot that shows the option to allow trusted Microsoft services to access this storage account.](media/export-data/exceptions.png)](media/export-data/exceptions.png#lightbox)
120-
120+
121121
1. Select **Save** to retain the settings.
122122

123123
1. Run the following PowerShell command to install the `Az.Storage` PowerShell module in your local environment. You can use this module to configure your Azure storage accounts by using PowerShell.
@@ -145,7 +145,7 @@ To securely import FHIR data into the FHIR service from an Azure Data Lake Stora
145145
1. Confirm that under **Resource instances**, **2 selected** appears in the **Instance name** dropdown list. The two selected instances are the name of the workspace instance and the name of the FHIR service instance that you registered as trusted Microsoft resources.
146146

147147
[![Screenshot of Azure Storage networking settings with resource type and instance names.](media/export-data/storage-networking-2.png)](media/export-data/storage-networking-2.png#lightbox)
148-
148+
149149
You're now ready to securely import FHIR data from the storage account. The storage account is on selected networks and isn't publicly accessible. To securely access the files, you can use [private endpoints](../../storage/common/storage-private-endpoints.md) for the storage account.
150150

151151
[!INCLUDE [Specific IP ranges for storage account](../includes/common-ip-address-storage-account.md)]
95.7 KB
Loading
133 KB
Loading

articles/healthcare-apis/fhir/use-postman.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -201,6 +201,8 @@ Select **Send**. You should see a new patient in the JSON response.
201201

202202
After you obtain a Microsoft Entra access token, you can export FHIR data to an Azure storage account.
203203

204+
To configure export settings and create a Data Lake Storage Gen2 account, refer to [Configure settings for export](./configure-export-data.md).
205+
204206
Create a new `GET` request: `{{fhirurl}}/$export?_container=export`
205207

206208
Select **Bearer Token** as authorization type. Enter `{{bearerToken}}` in the **Token** section. Select **Headers** to add two new headers:

articles/healthcare-apis/register-application.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,9 +83,9 @@ The following steps are required for the DICOM service, but optional for the FHI
8383

8484
If you're referencing a different resource application, select your DICOM API Resource Application Registration that you created previously under **APIs my organization**.
8585

86-
3. Select scopes (permissions) that the confidential client application will ask for on behalf of a user. Select **user_impersonation**, and then select **Add permissions**.
86+
3. Select scopes (permissions) that the confidential client application will ask for on behalf of a user. Select **Dicom.ReadWrite**, and then select **Add permissions**.
8787

88-
[ ![Screenshot of scopes (permissions) that the client application will ask for on behalf of a user.](dicom/media/dicom-select-scopes.png) ](dicom/media/dicom-select-scopes.png#lightbox)
88+
[ ![Screenshot of scopes (permissions) that the client application will ask for on behalf of a user.](dicom/media/dicom-select-scope.png) ](dicom/media/dicom-select-scope.png#lightbox)
8989

9090
>[!NOTE]
9191
>Use grant_type of client_credentials when trying to obtain an access token for the FHIR service using tools such as Postman or REST Client. For more details, visit [Access using Postman](./fhir/use-postman.md) and [Accessing Azure Health Data Services using the REST Client Extension in Visual Studio Code](./fhir/using-rest-client.md).

0 commit comments

Comments
 (0)