Skip to content

Commit 00df0f4

Browse files
Merge pull request #273291 from shellyhaverkamp/smh-ketki-deploy
Deployment article updates
2 parents 73634b1 + 54091cd commit 00df0f4

13 files changed

+66
-60
lines changed

articles/healthcare-apis/.openpublishing.redirection.healthcare-apis.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -450,6 +450,11 @@
450450
"redirect_url": "/azure/healthcare-apis/get-access-token",
451451
"redirect_document_id": false
452452
},
453+
{
454+
"source_path_from_root": "/articles/healthcare-apis/fhir/fhir-portal-quickstart.md",
455+
"redirect_url": "/azure/healthcare-apis/deploy-azure-portal",
456+
"redirect_document_id": false
457+
},
453458
{
454459
"source_path_from_root": "/articles/healthcare-apis/dicom/dicom-get-access-token-azure-cli.md",
455460
"redirect_url": "/azure/healthcare-apis/get-access-token",
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Deploy the FHIR service in Azure Health Data Services
3+
description: This article teaches users how to deploy a FHIR service in the Azure portal.
4+
author: EXPEkesheth
5+
ms.service: healthcare-apis
6+
ms.topic: quickstart
7+
ms.date: 04/30/2024
8+
ms.author: kesheth
9+
ms.custom: mode-api
10+
---
11+
12+
# Deploy the FHIR service by using the Azure portal
13+
14+
The Azure portal provides a web interface with guided workflows, making it an efficient tool for deploying the FHIR service and ensuring accurate configuration within Azure Health Data Services.
15+
16+
## Prerequisites
17+
18+
- Verify you have an Azure subscription and permissions for creating resource groups and deploy resources.
19+
20+
- Deploy a workspace for Azure Health Data Services. For steps, see [Deploy workspace in the Azure portal](../healthcare-apis-quickstart.md).
21+
22+
## Create a new FHIR service
23+
24+
1. From your Azure Health Data Services workspace, choose **Create FHIR service**.
25+
1. Choose **Add FHIR service**.
26+
1. On the **Create FHIR service** page, complete the fields on each tab.
27+
28+
- **Basics tab**: Give the FHIR service a friendly and unique name. Select the **FHIR version** (**STU3** or **R4**), and then choose **Next: Additional settings**.
29+
30+
:::image type="content" source="media/fhir-service/create-ahds-fhir-service-sml.png" alt-text="Screenshot showing how to create a FHIR service from the Basics tab." lightbox="media/fhir-service/create-ahds-fhir-service-lrg.png":::
31+
32+
- **Additional settings tab (optional)**: This tab allows you to:
33+
- **View authentication settings**: The default configuration for the FHIR service is **Use Azure RBAC for assigning data plane roles**. When configured in this mode, the authority for the FHIR service is set to the Microsoft Entra tenant for the subscription.
34+
35+
- **Integration with non-Microsoft Entra ID (optional)**: Use this option when you need to configure up to two additional identity providers other than Microsoft Entra ID to authenticate and access FHIR resources with SMART on FHIR scopes.
36+
37+
- **Setting versioning policy (optional)**: The versioning policy controls the history setting for FHIR service at the system level or individual resource type level. For more information, see [FHIR versioning policy and history management](fhir-versioning-policy-and-history-management.md). Choose **Next: Security**.
38+
39+
- On the **Security settings** tab, review the fields.
40+
41+
By default, data is encrypted with Microsoft-managed keys. For additional control over encryption keys, you can supply customer-managed keys to use for encryption of data. Customer-managed keys must be stored in an Azure Key Vault. You can either create your own keys and store them in a key vault, or use the Azure Key Vault APIs to generate keys. For more information, see [Configure customer-managed keys for the FHIR service](configure-customer-managed-keys.md). Choose **Next: Tags**.
42+
43+
- On the **Tags** tab (optional), enter any tags.
44+
45+
Tags are name and value pairs used for categorizing resources and aren't required. For more information, see [Use tags to organize your Azure resources and management hierarchy](../../azure-resource-manager/management/tag-resources.md).
46+
47+
- Choose **Review + Create** to begin the validation process. Wait until you receive confirmation that the deployment completed successfully. Review the confirmation screen, and then choose **Create** to begin the deployment.
48+
49+
The deployment process might take several minutes. When the deployment completes, you see a confirmation message.
50+
51+
:::image type="content" source="media/fhir-service/deployment-success-fhir-service-sml.png" alt-text="Screenshot showing successful deployment." lightbox="media/fhir-service/deployment-success-fhir-service-sml.png":::
52+
53+
1. Validate the deployment. Fetch the capability statement from your new FHIR service. Fetch a capability statement by browsing to `https://<WORKSPACE-NAME>-<FHIR-SERVICE-NAME>.fhir.azurehealthcareapis.com/metadata`.
54+
55+
## Related content
56+
57+
[Access the FHIR service by using Postman](../fhir/use-postman.md)
58+
59+
[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
60+

articles/healthcare-apis/fhir/fhir-portal-quickstart.md

Lines changed: 0 additions & 59 deletions
This file was deleted.
Binary file not shown.
Binary file not shown.
2.09 MB
Loading
195 KB
Loading
Binary file not shown.
Binary file not shown.
1.77 MB
Loading

0 commit comments

Comments
 (0)