Skip to content

Commit d342d52

Browse files
redirect snafu
1 parent 0c6aeb4 commit d342d52

File tree

3 files changed

+17
-24
lines changed

3 files changed

+17
-24
lines changed

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -550,7 +550,7 @@
550550
{
551551
"source_path_from_root": "/articles/healthcare-apis/fhir/overview-of-convert-data.md",
552552
"redirect_url": "/azure/healthcare-apis/fhir/convert-data-overview",
553-
"redirect_document_id": false
553+
"redirect_document_id": true
554554
},
555555
{
556556
"source_path_from_root": "/articles/healthcare-apis/fhir/frequently-asked-questions-convert-data.md",
@@ -560,8 +560,7 @@
560560
{
561561
"source_path_from_root": "/articles/healthcare-apis/datatransformation/convert-data.md",
562562
"redirect_url": "/azure/healthcare-apis/fhir/convert-data-overview",
563-
"redirect_document_id": true
564-
563+
"redirect_document_id": false
565564
},
566565
{
567566
"source_path_from_root": "/articles/healthcare-apis/fhir/bulk-importing-fhir-data.md",

articles/healthcare-apis/fhir/fhir-features-supported.md

Lines changed: 7 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Supported FHIR features in FHIR service
3-
description: This article explains which features of the FHIR specification that are implemented in Azure Health Data Services
2+
title: Supported FHIR features in the FHIR service
3+
description: Learn which features of the FHIR specification are implemented in the FHIR service in Azure Health Data Services
44
services: healthcare-apis
55
author: expekesheth
66
ms.service: healthcare-apis
@@ -12,7 +12,7 @@ ms.author: kesheth
1212

1313
# Supported FHIR Features
1414

15-
FHIR® service in Azure Health Data Services (hereby called FHIR service) provides a fully managed deployment of the [open-source FHIR Server](https://github.com/microsoft/fhir-server) and is an implementation of the [FHIR](https://hl7.org/fhir) standard. This document lists the main features of the FHIR service.
15+
The FHIR® service in Azure Health Data Services provides a fully managed deployment of the [open-source FHIR Server](https://github.com/microsoft/fhir-server) and is an implementation of the [FHIR](https://hl7.org/fhir) standard. This article lists the main features of the FHIR service.
1616

1717
## FHIR version
1818

@@ -22,7 +22,7 @@ Previous versions also currently supported include: `3.0.2`
2222

2323
## REST API
2424

25-
Below is a summary of the supported RESTful capabilities. For more information on the implementation of these capabilities, see [FHIR REST API capabilities](fhir-rest-api-capabilities.md).
25+
Here is a summary of the supported RESTful capabilities. For more information on the implementation of these capabilities, see [FHIR REST API capabilities](fhir-rest-api-capabilities.md).
2626

2727
| API | Azure API for FHIR | FHIR service in Azure Health Data Services | Comment |
2828
|--------|--------------------|---------------------------------|---------|
@@ -67,14 +67,11 @@ FHIR service uses [Microsoft Entra ID](https://azure.microsoft.com/services/acti
6767

6868
* **Bundle size** - Each bundle is limited to 500 items.
6969
* **Subscription Limit** - By default, each subscription is limited to a maximum of 10 FHIR services. The limit can be used in one or many workspaces.
70-
* **Storage size** - By default each FHIR instance is limited to storage capacity of 4TB. To provision a FHIR instance with storage capacity beyond 4TB, create support request with Issue type 'Service and Subscription limit (quotas)'.
70+
* **Storage size** - By default each FHIR instance is limited to storage capacity of 4 TB. To deploy a FHIR instance with storage capacity beyond 4 TB, create support request with Issue type **Service and Subscription limit (quotas)**.
7171

7272

7373
## Next steps
7474

75-
In this article, you've read about the supported FHIR features in the FHIR service. For information about deploying FHIR service, see
76-
77-
>[!div class="nextstepaction"]
78-
>[Deploy FHIR service](fhir-portal-quickstart.md)
75+
[Deploy the FHIR service](fhir-portal-quickstart.md)
7976

80-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
77+
[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/fhir/get-started-with-fhir.md

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: mode-api
1414

1515
This article outlines the basic steps to get started with the FHIR service in [Azure Health Data Services](../healthcare-apis-overview.md).
1616

17-
As a prerequisite, you'll 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 PowerShell, Azure CLI, and REST API scripts.
17+
As a prerequisite, you need an Azure subscription and 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 PowerShell, Azure CLI, and REST API scripts.
1818

1919
[![Get started with the FHIR service flow diagram.](media/get-started-with-fhir.png)](media/get-started-with-fhir.png#lightbox)
2020

@@ -33,23 +33,23 @@ Optionally, you can create a [DICOM service](../dicom/deploy-dicom-services-in-a
3333

3434
## Access the FHIR service
3535

36-
The FHIR service is secured by Microsoft Entra ID that can't be disabled. To access the service API, you must create a client application that's also referred to as a service principal in Microsoft Entra ID and grant it with the right permissions.
36+
The FHIR service is secured by Microsoft Entra ID that can't be disabled. To access the service API, you must create a client application also referred to as a service principal in Microsoft Entra ID and grant it with the right permissions.
3737

3838
### Register a client application
3939

4040
You can create or register a client application from the [Azure portal](../register-application.md), or using PowerShell and Azure CLI scripts. This client application can be used for one or more FHIR service instances. It can also be used for other services in Azure Health Data Services.
4141

4242
If the client application is created with a certificate or client secret, ensure that you renew the certificate or client secret before expiration and replace the client credentials in your applications.
4343

44-
You can delete a client application. Before you delete a client application, ensure that it's not used in production, dev, test, or quality assurance (QA) environments.
44+
You can delete a client application. Before you delete a client application, ensure it isn't used in production, dev, test, or quality assurance (QA) environments.
4545

4646
### Grant access permissions
4747

4848
You can grant access permissions or assign roles from the [Azure portal](../configure-azure-rbac.md), or using PowerShell and Azure CLI scripts.
4949

5050
### Perform create, read, update, and delete (CRUD) transactions
5151

52-
You can perform create, read (search), update, and delete (CRUD) transactions against the FHIR service in your applications or by using tools such as Postman, REST Client, and cURL. Because the FHIR service is secured by default, you must obtain an access token and include it in your transaction request.
52+
You can perform Create, Read (search), Update, and Delete (CRUD) transactions against the FHIR service in your applications or by using tools such as Postman, REST Client, and cURL. Because the FHIR service is secured by default, you must obtain an access token and include it in your transaction request.
5353

5454
#### Get an access token
5555

@@ -71,13 +71,13 @@ You can find more details on interoperability and patient access, search, profil
7171

7272
### Export data
7373

74-
Optionally, you can export ($export) data to [Azure Storage](../data-transformation/export-data.md) and use it in your analytics or machine-learning projects. You can export the data "as-is" or [de-id](../data-transformation/de-identified-export.md) in `ndjson` format.
74+
Optionally, you can export ($export) data to [Azure Storage](../data-transformation/export-data.md) and use it in your analytics or machine-learning projects. You can export the data "as-is" or [deid](../data-transformation/de-identified-export.md) in `ndjson` format.
7575

7676
### Converting data
7777

7878
Optionally, you can convert [HL7 v2](convert-data-overview.md) and other format data to FHIR.
7979

80-
### Using FHIR data in Power BI Dashboard
80+
### Using FHIR data in Power BI dashboard
8181

8282
Optionally, you can create Power BI dashboard reports with FHIR data.
8383

@@ -86,9 +86,6 @@ Optionally, you can create Power BI dashboard reports with FHIR data.
8686

8787
## Next steps
8888

89-
This article described the basic steps to get started using the FHIR service. For information about deploying FHIR service in the Azure Health Data Services workspace, see
89+
[Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
9090

91-
>[!div class="nextstepaction"]
92-
>[Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
93-
94-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
91+
[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

0 commit comments

Comments
 (0)