Skip to content

Commit 4eddf2f

Browse files
authored
Update configure-import-data.md
1 parent 9ed9419 commit 4eddf2f

File tree

1 file changed

+9
-17
lines changed

1 file changed

+9
-17
lines changed

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

Lines changed: 9 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ The FHIR service supports $import operation that allows you to import data into
1515

1616
The three steps below are used in configuring import settings in the FHIR service:
1717

18-
Step 1: Enable managed identity for the FHIR service.
19-
Step 2: Create an Azure storage account or use an existing storage account, and then grant permissions to the FHIR service to access it.
20-
Step 3: Set the import configuration in the FHIR service.
18+
* Step 1: Enable managed identity for the FHIR service.
19+
* Step 2: Create an Azure storage account or use an existing storage account, and then grant permissions to the FHIR service to access it.
20+
* Step 3: Set the import configuration in the FHIR service.
2121

2222
## Step 1: Enable managed identity on the FHIR service
2323

@@ -81,14 +81,14 @@ This option permits two different configurations depending on whether or not the
8181

8282
Go to your ADLS Gen2 account in the Azure portal and select the **Networking** blade. Select **Enabled from selected virtual networks and IP addresses** under the **Firewalls and virtual networks** tab.
8383

84-
:::image type="content" source="media/export-data/storage-networking-1.png" alt-text="Screenshot of Azure Storage Networking Settings." lightbox="media/export-data/storage-networking-1.png":::
84+
[![Screenshot of Azure Storage Networking Settings.](media/export-data/storage-networking-1.png)](media/export-data/storage-networking-1.png#lightbox)
8585

8686
Select **Microsoft.HealthcareApis/workspaces** from the **Resource type** dropdown list and then select your workspace from the **Instance name** dropdown list.
8787

8888
Under the **Exceptions** section, select the box **Allow Azure services on the trusted services list to access this storage account**. Make sure to click **Save** to retain the settings.
8989

90-
:::image type="content" source="media/export-data/exceptions.png" alt-text="Allow trusted Microsoft services to access this storage account.":::
91-
90+
[![Allow trusted Microsoft services to access this storage account.](media/export-data/exceptions.png)](media/export-data/exceptions.png#lightbox)
91+
9292
Next, run the following PowerShell command to install the `Az.Storage` PowerShell module in your local environment. This will allow you to configure your Azure storage account(s) using PowerShell.
9393

9494
```PowerShell
@@ -113,8 +113,8 @@ Add-AzStorageAccountNetworkRule -ResourceGroupName $resourceGroupName -Name $sto
113113

114114
After running this command, in the **Firewall** section under **Resource instances** you will see **2 selected** in the **Instance name** dropdown list. These are the names of the workspace instance and FHIR service instance that you just registered as Microsoft Trusted Resources.
115115

116-
:::image type="content" source="media/export-data/storage-networking-2.png" alt-text="Screenshot of Azure Storage Networking Settings with resource type and instance names." lightbox="media/export-data/storage-networking-2.png":::
117-
116+
[![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)
117+
118118
You're now ready to securely import FHIR data from the storage account. Note that the storage account is on selected networks and isn't publicly accessible. To securely access the files, you can enable [private endpoints](../../storage/common/storage-private-endpoints.md) for the storage account.
119119

120120
### Option 2: Allowing specific IP addresses to access the Azure storage account
@@ -159,21 +159,13 @@ The configuration process for IP addresses in the same region is just like above
159159
> It is possible that a private IP address within the range of 10.0.2.0/24 may be used, but there is no guarantee that the `$import` operation will succeed in such a case. You can retry if the `$import` request fails, but until an IP address within the range of 100.64.0.0/10 is used, the request will not succeed. This network behavior for IP address ranges is by design. The alternative is to configure the storage account in a different region.
160160
161161

162-
163162
## Next steps
164163

165-
In this article, you've learned the FHIR service supports $import operation and how it allows you to import data into FHIR service account from a storage account. You also learned about the three steps used in configuring import settings in the FHIR service. For more information about converting data to FHIR, exporting settings to set up a storage account, and moving data to Azure Synapse, see
164+
In this article, you've learned the FHIR service supports $import operation and learned on the steps used in configuring import settings. For more information on using $import in the FHIR service, see
166165

167166
>[!div class="nextstepaction"]
168167
>[Use $import](import-data.md)
169168
170-
>[!div class="nextstepaction"]
171-
>[Converting your data to FHIR](convert-data.md)
172-
173-
>[!div class="nextstepaction"]
174-
>[Configure export settings and set up a storage account](configure-export-data.md)
175169

176-
>[!div class="nextstepaction"]
177-
>[Copy data from FHIR service to Azure Synapse Analytics](copy-to-synapse.md)
178170

179171
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

0 commit comments

Comments
 (0)