Skip to content

Commit d49a1e2

Browse files
v-regandownerv-regandowner
authored
Merge pull request #197796 from SteveWohl/april-2022-release-notes
Added april 2022 azure api for fhir release notes
2 parents 621c3b9 + 3fa2cbf commit d49a1e2

File tree

4 files changed

+97
-5
lines changed

4 files changed

+97
-5
lines changed

‎articles/healthcare-apis/azure-api-for-fhir/release-notes.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: mikaelweave
66
ms.service: healthcare-apis
77
ms.subservice: fhir
88
ms.topic: reference
9-
ms.date: 04/14/2022
9+
ms.date: 05/13/2022
1010
ms.custom: references_regions
1111
ms.author: mikaelw
1212
---
@@ -16,6 +16,23 @@ ms.author: mikaelw
1616
Azure API for FHIR provides a fully managed deployment of the Microsoft FHIR Server for Azure. The server is an implementation of the [FHIR](https://hl7.org/fhir) standard. This document provides details about the features and enhancements made to Azure API for FHIR.
1717

1818

19+
## April 2022
20+
21+
### **Enhancements**
22+
23+
|Enhancements                                                                                                         |Related information |
24+
| :----------------------------------- | ---------------: |
25+
|FHIRPath Patch |FHIRPath Patch was added as a feature to both the Azure API for FHIR. This implements FHIRPath Patch as defined on the [HL7](http://hl7.org/fhir/fhirpatch.html) website. |
26+
|Move Bundle notification to Core |With the introduction of the Resource.Bundle namespace to Core, the Resource references to the string resources file had to be made more explicit. For more information, see [PR #2478](https://github.com/microsoft/fhir-server/pull/2478). |
27+
|Handles invalid header on versioned update |When the versioning policy is set to "versioned-update", we required that the most recent version of the resource is provided in the request's if-match header on an update. The specified version must be in ETag format. Previously, a 500 would be returned if the version was invalid or in an incorrect format. This update now returns a 400 Bad Request. For more information, see [PR #2467](https://github.com/microsoft/fhir-server/pull/2467). |
28+
29+
### **Bug fixes**
30+
31+
|Bug fixes |Related information |
32+
| :----------------------------------- | ---------------: |
33+
|Adds core to resource path |Part of the path to a string resource was accidentally removed in the versioning policy. This fix adds it back in. For more information, see [PR #2470](https://github.com/microsoft/fhir-server/pull/2470). |
34+
|SQL timeout is returning a 500 error |Fixed a bug when a SQL request hits a timeout and the request returns a 500. In the logs, this is a timeout from SQL compared to getting a 429 error from front end. For more information, see [PR #2497](https://github.com/microsoft/fhir-server/pull/2497). |
35+
1936
## March 2022
2037

2138
### **Features**
@@ -38,8 +55,8 @@ Azure API for FHIR provides a fully managed deployment of the Microsoft FHIR Ser
3855

3956
|Enhancements                                                                                                         |Related information |
4057
| :----------------------------------- | ---------------: |
41-
|Added 429 retry and logging in BundleHandler |We sometimes encounter 429 errors when processing a bundle. If the FHIR service receives a 429 at the BundleHandler layer, we abort processing of the bundle and skip the remaining resources. We've added an additional retry (in addition to the retry present in the data store layer) that will execute one time per resource that encounters a 429. For more about this feature enhancement, see [PR #2400](https://github.com/microsoft/fhir-server/pull/2400).|
42-
|Billing for $convert-data and $de-id |Azure API for FHIR's data conversion and de-identified export features are now Generally Available. Billing for $convert-data and $de-id operations in Azure API for FHIR has been enabled. Billing meters were turned on March 1, 2022. |
58+
|Added 429 retry and logging in BundleHandler |We sometimes encounter 429 errors when processing a bundle. If the FHIR service receives a 429 at the BundleHandler layer, we abort processing of the bundle and skip the remaining resources. We've added another retry (in addition to the retry present in the data store layer) that will execute one time per resource that encounters a 429. For more about this feature enhancement, see [PR #2400](https://github.com/microsoft/fhir-server/pull/2400).|
59+
|Billing for `$convert-data` and `$de-id` |Azure API for FHIR's data conversion and de-identified export features are now Generally Available. Billing for `$convert-data` and `$de-id` operations in Azure API for FHIR has been enabled. Billing meters were turned on March 1, 2022. |
4360

4461
### **Bug fixes**
4562

‎articles/healthcare-apis/known-issues.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: Azure Health Data Services known issues
3+
description: This article provides details about the known issues of Azure Health Data Services.
4+
services: healthcare-apis
5+
author: mikaelweave
6+
ms.service: healthcare-apis
7+
ms.subservice: fhir
8+
ms.topic: reference
9+
ms.date: 05/13/2022
10+
ms.author: mikaelw
11+
---
12+
13+
# Known issues: Azure Health Data Services
14+
15+
This article describes the currently known issues with Azure Health Data Services and its different service types (FHIR service, DICOM service, and MedTech service) that seamlessly work with one another.
16+
17+
Refer to the table below to find details about resolution dates or possible workarounds. For more information about the different feature enhancements and bug fixes in Azure Health Data Services, see [Release notes: Azure Health Data Services](release-notes.md).
18+
19+
## FHIR service
20+
21+
|Issue | Date discovered | Status | Date resolved |
22+
| :------------------------------------- | :------------ | :------------- | :------------- |
23+
|The SQL Provider will cause the `RawResource` column in the database to save incorrectly. This issue occurs in a few cases when a transient exception occurs that causes the provider to use its retry logic. |April 2022 |Doesn't have a workaround. |Not resolved |
24+
25+
26+
## Next steps
27+
28+
In this article, you learned about the currently known issues with Azure Health Data Services. For more information about Azure Health Data Services, see
29+
30+
>[!div class="nextstepaction"]
31+
>[About Azure Health Data Services](healthcare-apis-overview.md)
32+
33+
For information about the features and bug fixes in Azure API for FHIR, see
34+
35+
>[!div class="nextstepaction"]
36+
>[Release notes: Azure API for FHIR](./azure-api-for-fhir/release-notes.md)

‎articles/healthcare-apis/release-notes.md

Lines changed: 39 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: mikaelweave
66
ms.service: healthcare-apis
77
ms.subservice: fhir
88
ms.topic: reference
9-
ms.date: 04/14/2022
9+
ms.date: 05/13/2022
1010
ms.author: mikaelw
1111
---
1212

@@ -19,6 +19,38 @@ ms.author: mikaelw
1919
2020
Azure Health Data Services is a set of managed API services based on open standards and frameworks for the healthcare industry. They enable you to build scalable and secure healthcare solutions by bringing protected health information (PHI) datasets together and connecting them end-to-end with tools for machine learning, analytics, and AI. This document provides details about the features and enhancements made to Azure Health Data Services including the different service types (FHIR service, DICOM service, and MedTech service) that seamlessly work with one another.
2121

22+
## April 2022
23+
24+
### FHIR service
25+
26+
### **Features and enhancements**
27+
28+
|Enhancements                                                                                                         |Related information |
29+
| :------------------- | ---------------: |
30+
|FHIRPath Patch |FHIRPath Patch was added as a feature to both the Azure API for FHIR. This implements FHIRPath Patch as defined on the [HL7](http://hl7.org/fhir/fhirpatch.html) website. |
31+
|Handles invalid header on versioned update |When the versioning policy is set to "versioned-update", we required that the most recent version of the resource is provided in the request's if-match header on an update. The specified version must be in ETag format. Previously, a 500 would be returned if the version was invalid or in an incorrect format. This update now returns a 400 Bad Request. For more information, see [PR #2467](https://github.com/microsoft/fhir-server/pull/2467). |
32+
|Bulk import in public preview |The bulk-import feature enables importing FHIR data to the FHIR server at high throughput using the $import operation. It's designed for initial data load into the FHIR server. For more information, see [Bulk-import FHIR data (Preview)](./../healthcare-apis/fhir/import-data.md). |
33+
34+
### **Bug fixes**
35+
36+
|Bug fixes |Related information |
37+
| :----------------------------------- | ---------------: |
38+
|Adds core to resource path |Part of the path to a string resource was accidentally removed in the versioning policy. This fix adds it back in. For more information, see [PR #2470](https://github.com/microsoft/fhir-server/pull/2470). |
39+
40+
### **Known issues**
41+
42+
For more information about the currently known issues with the FHIR service, see [Known issues: FHIR service](known-issues.md).
43+
44+
### DICOM service
45+
46+
### **Bug fixes**
47+
48+
|Bug fixes |Related information |
49+
| :----------------------------------- | ---------------: |
50+
|Reduce the strictness of validation applied to incoming DICOM files |When value representation (VR) is a decimal string (DS)/ integer string (IS), `fo-dicom` serialization treats value as a number. Customer DICOM files could be old and contains invalid numbers. Our service blocks such file upload due to the serialization exception. For more information, see [PR #1450](https://github.com/microsoft/dicom-server/pull/1450). |
51+
|Correctly parse a range of input in the content negotiation headers |Currently, WADO with Accept: multipart/related; type=application/dicom will throw an error. It will accept Accept: multipart/related; type="application/dicom", but they should be equivalent. For more information, see [PR #1462](https://github.com/microsoft/dicom-server/pull/1462). |
52+
|Fixed an issue where parallel upload of images in a study could fail under certain circumstances |Handle race conditions during parallel instance inserts in the same study. For more information, see [PR #1491](https://github.com/microsoft/dicom-server/pull/1491) and [PR #1496](https://github.com/microsoft/dicom-server/pull/1496). |
53+
2254
## March 2022
2355

2456
### Azure Health Data Services
@@ -120,7 +152,7 @@ Azure Health Data Services is a set of managed API services based on open standa
120152
|Bug fixes |Related information |
121153
| :----------------------------------- | ---------------: |
122154
|Resolved 500 error when the date was passed with a time zone. |This fixes a 500 error when a date with a time zone was passed into a datetime field [#2270](https://github.com/microsoft/fhir-server/pull/2270). |
123-
|Resolved issue where posting a bundle with incorrect Media Type returned a 500 error. |Previously when posting a search with a key that contains certain characters, a 500 error is returned. This fixes this issue [#2264](https://github.com/microsoft/fhir-server/pull/2264), and it addresses [#2148](https://github.com/microsoft/fhir-server/issues/2148). |
155+
|Resolved issue when posting a bundle with incorrect Media Type returned a 500 error. |Previously when posting a search with a key that contains certain characters, a 500 error is returned. This fixes this issue [#2264](https://github.com/microsoft/fhir-server/pull/2264), and it addresses [#2148](https://github.com/microsoft/fhir-server/issues/2148). |
124156

125157
### DICOM service
126158

@@ -230,6 +262,11 @@ Azure Health Data Services is a set of managed API services based on open standa
230262

231263
## Next steps
232264

265+
In this article, you learned about the features and enhancements made to Azure Health Data Services. For more information about the known issues with Azure Health Data Services, See
266+
267+
>[!div class="nextstepaction"]
268+
>[Known issues: Azure Health Data Services](known-issues.md)
269+
233270
For information about the features and bug fixes in Azure API for FHIR, see
234271

235272
>[!div class="nextstepaction"]

‎articles/healthcare-apis/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,8 @@ items:
7676
href: healthcare-apis-faqs.md
7777
- name: GitHub projects
7878
href: github-projects.md
79+
- name: Known issues
80+
href: known-issues.md
7981
- name: Release notes
8082
href: release-notes.md
8183

0 commit comments

Comments
 (0)