ENABLE FHIR R5 in my subscription

Question

ENABLE FHIR R5 in my subscription

Palani Perumal 0

In my current Azure scripting, using FHIR Service instance under Healthdata services. We are trying to upload data to FHIR server under R5 release version. However, our instance of FHIR service support only R4, STU3. Require help to enable R5 support in our subscription, service. What do we need to do to get this working?

Palani Perumal 0 Reputation points

2026-03-09T05:16:23.9566667+00:00

Thanks for the response. Unfortunately, these won't work as our scope focus entirely on new profiles introduced in R5.

Thanks for confirming though, we will look for hosting our own servers instead.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-03-17T05:34:16.92+00:00

Hi @Anonymous

Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2026-03-25T11:17:54.36+00:00

Hi @Palani Perumal,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Palani Perumal 0 Reputation points

2026-03-09T05:16:23.9566667+00:00

Thanks for the response. Unfortunately, these won't work as our scope focus entirely on new profiles introduced in R5.

Thanks for confirming though, we will look for hosting our own servers instead.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Siddhesh Desai 8,210 Reputation points Microsoft External Staff Moderator

2026-03-17T05:34:16.92+00:00

Hi @Anonymous

Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.
Praveen Kumar Gudipudi 2,295 Reputation points Microsoft External Staff Moderator

2026-03-25T11:17:54.36+00:00

Hi @Palani Perumal,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Hi @Palani Perumal

Thank you for reaching out to Microsoft Q&A.

According to these Documents: https://github.com/microsoft/fhir-server/discussions/3091#discussioncomment-12454671 and https://learn.microsoft.com/en-us/azure/healthcare-apis/azure-api-for-fhir/fhir-faq#what-fhir-version-do-you-support-

What FHIR version do you support? We support versions 4.0.0 and 3.0.1. For more information, see the FHIR supported features. You can also read about what has changed between FHIR versions (STU3 to R4) in the version history for HL7 FHIR.

Azure Health Data Services currently supports only:

FHIR R4 (primary, GA)
FHIR STU3 (legacy / limited scenarios)

FHIR R5 is not yet available as a supported version in Azure Health Data Services. Because the FHIR version is a service-level characteristic, it cannot be upgraded or changed after the service is created, and it cannot be enabled via Azure support, subscription changes, or ARM/Bicep/CLI updates.

What can you do today?

Refer below points for supported paths forward:

Use FHIR R4 (Recommended)

Azure Health Data Services fully supports FHIR R4 and is production ready.

Most R5 features can be modeled or adapted in R4 with extensions.

This is the only officially supported production option today. [github.com]

Use the FHIR R5 Backport Implementation Guide

If you specifically need R5-style Subscriptions or behaviors, Microsoft recommends using the R5 Backport IG with an R4 server.

This allows partial R5 functionality while staying within a supported R4 service.

Transform R5 payloads to R4 before ingestion

Introduce a transformation layer (Azure Functions, Logic Apps, or ADF) to:

Convert R5 resources → R4-compatible resources

Strip unsupported elements

This is a common enterprise pattern when upstream systems already emit R5.

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.