Skip to content

Commit cbab275

Browse files
authored
Merge pull request #191802 from SteveWohl/feb-2022-release-notes
Updated Health Data Services and Azure API for FHIR release notes and…
2 parents 9e376c2 + 34f4df3 commit cbab275

File tree

4 files changed

+34
-8
lines changed

4 files changed

+34
-8
lines changed

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

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: caitlinv39
66
ms.service: healthcare-apis
77
ms.subservice: fhir
88
ms.topic: reference
9-
ms.date: 01/11/2022
9+
ms.date: 03/15/2022
1010
ms.custom: references_regions
1111
ms.author: cavoeg
1212
---
@@ -15,6 +15,22 @@ ms.author: cavoeg
1515

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

18+
## February 2022
19+
20+
### **Features and enhancements**
21+
22+
|Enhancements                                                                                                         |Related information |
23+
| :----------------------------------- | ---------------: |
24+
|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).|
25+
|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. |
26+
27+
### **Bug fixes**
28+
29+
|Bug fixes |Related information |
30+
| :----------------------------------- | ---------------: |
31+
|Update compartment search index |There was a corner case where the compartment search index wasn't being set on resources. Now we use the same index as the main search for compartment search to ensure all data is being returned. For more about the code fix, see [PR #2430](https://github.com/microsoft/fhir-server/pull/2430).|
32+
33+
1834
## December 2021
1935

2036
### **Features and enhancements**

articles/healthcare-apis/healthcare-apis-overview.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: healthcare-apis
55
author: stevewohl
66
ms.service: healthcare-apis
77
ms.topic: overview
8-
ms.date: 03/01/2022
8+
ms.date: 03/15/2022
99
ms.author: ginle
1010
---
1111

@@ -30,17 +30,20 @@ Azure Health Data Services enables you to:
3030

3131
**Linked Services**
3232

33-
Azure Health Data Services now supports multiple health data standards for the exchange of structured data. A single collection of Azure Health Data Services enables you to deploy multiple instances of different service types (FHIR service, DICOM service, and IoT connector) that seamlessly work with one another.
33+
Azure Health Data Services now supports multiple health data standards for the exchange of structured data. A single collection of Azure Health Data Services enables you to deploy multiple instances of different service types (FHIR, DICOM, and MedTech) that seamlessly work with one another. Services deployed within a workspace also share a compliance boundary and common configuration settings. The product scales automatically to meet the varying demands of your workloads, so you spend less time managing infrastructure and more time generating insights from health data.
3434

3535
**Introducing DICOM service**
3636

37-
Azure Health Data Services now includes support for DICOM services. DICOM enables the secure exchange of image data and its associated metadata. DICOM is the international standard to transmit, store, retrieve, print, process, and display medical imaging information, and is the primary medical imaging standard accepted across healthcare. For more information about the DICOM service, see [Overview of DICOM](./dicom/dicom-services-overview.md).
37+
Azure Health Data Services now includes support for DICOM service. DICOM enables the secure exchange of image data and its associated metadata. DICOM is the international standard to transmit, store, retrieve, print, process, and display medical imaging information, and is the primary medical imaging standard accepted across healthcare. For more information about the DICOM service, see [Overview of DICOM](./dicom/dicom-services-overview.md).
3838

3939
**Incremental changes to the FHIR Service**
4040

41-
For the secure exchange of FHIR data, Azure Health Data Services offers a few incremental capabilities that aren't available in the Azure API for FHIR.
42-
* Support for Transactions: In Azure Health Data Services, the FHIR service supports transaction bundles. For more information about transaction bundles, visit [HL7.org](http://www.hl7.org/) and refer to batch/transaction interactions.
43-
* Chained Search Improvements: Chained Search & Reserve Chained Search are no longer limited by 100 items per sub query.
41+
For the secure exchange of FHIR data, Azure Health Data Services offers a few incremental capabilities that aren't available in Azure API for FHIR.
42+
43+
* **Support for Transactions**: In Azure Health Data Services, the FHIR service supports transaction bundles. For more information about transaction bundles, visit [HL7.org](http://www.hl7.org/) and refer to batch/transaction interactions.
44+
* [Chained Search Improvements](./././fhir/overview-of-search.md#chained--reverse-chained-searching): Chained Search & Reserve Chained Search are no longer limited by 100 items per sub query.
45+
* The $convert-data operation can now transform JSON objects to FHIR R4.
46+
* Events: Trigger new workflows when resources are created, updated, or deleted in a FHIR service.
4447

4548

4649
## Next steps

articles/healthcare-apis/release-notes.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,17 @@ author: caitlinv39
66
ms.service: healthcare-apis
77
ms.subservice: fhir
88
ms.topic: reference
9-
ms.date: 02/15/2022
9+
ms.date: 03/15/2022
1010
ms.author: cavoeg
1111
---
1212

1313
# Release notes: Azure Health Data Services
1414

15+
>[!Note]
16+
> Azure Health Data Services is Generally Available.
17+
>
18+
>For more information about Azure Health Data Services Service Level Agreements, see [SLA for Azure Health Data Services](https://azure.microsoft.com/support/legal/sla/health-data-services/v1_1/).
19+
1520
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 IoT connector) that seamlessly work with one another.
1621

1722
## January 2022

articles/healthcare-apis/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,8 @@ items:
5757
items:
5858
- name: Configure Private Link
5959
href: healthcare-apis-configure-private-link.md
60+
- name: Configure Events
61+
href: ./events/events-deploy-portal.md
6062
- name: Diagnostic logging
6163
expanded: true
6264
items:

0 commit comments

Comments
 (0)