Skip to content

Commit 7da40cc

Browse files
kgaddam10kgaddam10
committed
Feb v2 content
1 parent 47f84d6 commit 7da40cc

File tree

1 file changed

+134
-75
lines changed

1 file changed

+134
-75
lines changed

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

Lines changed: 134 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,88 @@ ms.custom: references_regions
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+
## February 2023
23+
#### FHIR service
24+
25+
**Introduction of _till parameters and throughput improvement by 50x**
26+
27+
_till parameter is introduced as optional parameter and allows you to export resources that have been modified till the specified time.
28+
This feature improvement is applicable to System export, for more information on export, visit [FHIR specification](https://hl7.org/fhir/uv/bulkdata/export/index.html)
29+
30+
Also visit [Export your FHIR data by invoking the $export command on the FHIR service | Microsoft Learn](azure/healthcare-apis/fhir/export-data)
31+
32+
33+
**Fixed issue for Chained search with :contains modifier results with no resources are returned**
34+
35+
This bug-fix addresses the issue and identified resources, per search criteria with :contains modifier are returned.
36+
37+
For more details, visit [#2990](https://github.com/microsoft/fhir-server/pull/2990)
38+
39+
40+
41+
**Provide the ability to tweak continuation token size limit with header.**
42+
43+
44+
Previous to this change, during pagination Cosmos DB continuation token had a default limit of 3Kb. With this change, customers can send Cosmos DB Continuation Token limit in the header. Valid range is set to 1-3 Kb. Header value to use to send this value is x-ms-documentdb-responsecontinuationtokenlimitinkb
45+
46+
For more details, visit [#2971](https://github.com/microsoft/fhir-server/pull/2971/files) and [Overview of search in Azure API for FHIR | Microsoft Learn](azure/healthcare-apis/azure-api-for-fhir/overview-of-search)
47+
48+
49+
**Fixed issue related to HTTP Status code 500 was encountered when :not modifier was used with chained searches**
50+
51+
Bug fix addresses the issue and identified resources are returned per the search criteria, for more details on bug fix visit [#3041](https://github.com/microsoft/fhir-server/pull/3041)
52+
53+
54+
**Versioning policy enabled at resource level still required If-match header for transaction requests.**
55+
56+
Bug fix addresses the issue and versioned policy at resource level does not require if-match header, for more details on bug fix visit [#2994](https://github.com/microsoft/fhir-server/pull/2994)
57+
58+
59+
60+
61+
#### MedTech service
62+
63+
**Mapping Debugger released**
64+
65+
The MedTech service's new Mapping Debugger is a self-service tool that is used for creating, updating, and troubleshooting the MedTech service device and FHIR destination mappings. It enables you to easily view and make inline adjustments in real-time, without ever having to leave the Azure portal.
66+
67+
For more information, visit [How to use the MedTech service Mapping debugger - Azure Health Data Services | Microsoft Learn](azure/healthcare-apis/iot/how-to-use-mapping-debugger)
68+
69+
70+
71+
**Error Message released**
72+
73+
The MedTech service now has an error message feature that allows you to easily view any errors generated, as well as the message that caused each error. You can now understand the context behind any errors without manual effort. For more info on error logs, visit [Troubleshoot errors using the MedTech service logs - Azure Health Data Services | Microsoft Learn](azure/healthcare-apis/iot/troubleshoot-errors-logs)
74+
75+
76+
77+
78+
79+
#### DICOM service
80+
81+
**New DICOM Event Types are GA**
82+
83+
[DICOM Events](events/events-message-structure.md#dicom-events-message-structure) are now generally available in the HDS workspace-level event subscriptions. These new event types enable event-driven workflows in medical imaging applications by subscribing to events for newly created and deleted DICOM images.
84+
85+
86+
**Validation errors included with the FailedSOPSequence**
87+
88+
Previously, DICOM validation failures returned by the Store (STOW) API have lacked the detail necessary to diagnose and resolve problems. The latest API changes improve the error messages by including additional details about the specific attributes that failed validation and the reason for the failures. See the [conformance statement](dicom/dicom-services-conformance-statement.md#store-response-payload) for details.
89+
90+
91+
#### Toolkit and Samples Open Source
92+
93+
94+
Two new sample apps have been released in the open source samples repo: [Azure-Samples/azure-health-data-services-samples: Samples for using the Azure Health Data Services (github.com)](https://github.com/Azure-Samples/azure-health-data-services-samples)
95+
96+
97+
98+
99+
100+
22101
## January 2023
23102

24-
#### Azure Health Data Services
103+
### Azure Health Data Services
25104

26105
**Azure Health Data services General Available (GA) in new regions**
27106

@@ -39,7 +118,11 @@ The DICOM service now supports `ModalitiesInStudy` as a [searchable attribute](d
39118

40119
Two new attributes for returning the count of Instances in a Study or Series are available in Search [responses](dicom/dicom-services-conformance-statement.md#additional-series-tags).
41120

42-
#### Toolkit and Samples (Open Source)
121+
122+
123+
#### Toolkit and Samples Open Source
124+
125+
43126
**New sample app has been released**
44127

45128
One new sample app has been released in the [Health Data Services samples repo](https://github.com/Azure-Samples/azure-health-data-services-samples)
@@ -61,10 +144,10 @@ Azure Health Data Services [Events](events/events-overview.md) now include a pub
61144

62145
**Fixed the Error generated when resource is updated using if-match header and PATCH**
63146

64-
Bug is now fixed and Resource will be updated if matches the Etag header. For details, see [#2877](https://github.com/microsoft/fhir-server/issues/2877)
147+
Bug is now fixed and Resource will be updated if matches the Etag header. For details , see [#2877](https://github.com/microsoft/fhir-server/issues/2877)
65148

66149

67-
#### Toolkit and Samples (Open Source)
150+
#### Toolkit and Samples Open Source
68151

69152

70153
**Azure Health Data Services Toolkit is released**
@@ -92,7 +175,7 @@ Customers can now determine if their mappings are working as intended, as they c
92175

93176
**Fixed issue where Querying with :not operator was returning more results than expected**
94177

95-
The issue is now fixed and querying with :not operator should provide correct results. For more information, see [#2790](https://github.com/microsoft/fhir-server/pull/2785).
178+
The issue is now fixed and querying with :not operator should provide correct results. For more information, see [#2790](https://github.com/microsoft/fhir-server/pull/2785). |
96179

97180

98181

@@ -135,11 +218,11 @@ The service will now accept the following:
135218
* IS, DS, SV, and UV VRs that are not valid numbers
136219
* Invalid private creator tags
137220

138-
#### Toolkit and Samples (Open Source)
221+
#### Toolkit and Samples Open Source
139222

140223
**The [Azure Health Data Services Toolkit](https://github.com/microsoft/azure-health-data-services-toolkit) is now in the public preview.**
141224

142-
The toolkit is open-source and allows you to easily customize and extend the functionality of their Azure Health Data Services implementations.
225+
The toolkit is open-source and allows to easily customize and extend the functionality of their Azure Health Data Services implementations.
143226

144227
## **August 2022**
145228

@@ -170,7 +253,7 @@ Analytics pipeline can process FHIR extensions to generate parquet data. See [FH
170253

171254
**Fixed issue related to History bundles being sorted with the oldest version first.**
172255

173-
We've recently identified an issue with the sorting order of history bundles on FHIR® server. History bundles were sorted with the oldest version first. Per FHIR specification, the sorting of versions defaults to the oldest version last. This bug fix, addresses FHIR server behavior for sorting history bundle. <br><br>We understand if you would like to keep the sorting per existing behavior (oldest version first). To support existing behavior, we recommend you append `_sort=_lastUpdated` to the HTTP GET command utilized for retrieving history. <br><br>For example: `<server URL>/_history?_sort=_lastUpdated` <br><br>For more information, see [#2689](https://github.com/microsoft/fhir-server/pull/2689).
256+
We've recently identified an issue with the sorting order of history bundles on FHIR® server. History bundles were sorted with the oldest version first. Per FHIR specification, the sorting of versions defaults to the oldest version last.This bug fix, addresses FHIR server behavior for sorting history bundle. <br><br>We understand if you would like to keep the sorting per existing behavior (oldest version first). To support existing behavior, we recommend you append `_sort=_lastUpdated` to the HTTP GET command utilized for retrieving history. <br><br>For example: `<server URL>/_history?_sort=_lastUpdated` <br><br>For more information, see [#2689](https://github.com/microsoft/fhir-server/pull/2689).
174257

175258
**Fixed issue where Queries were not providing consistent result count after appended with `_sort` operator.**
176259
The issue is now fixed and queries should provide consistent result count, with and without sort operator.
@@ -203,7 +286,7 @@ The modality worklists (UPS-RS) service is now generally available. Learn more a
203286
We've recently identified an issue with the sorting order of history bundles on FHIR® server. History bundles were sorted with the oldest version first. Per [FHIR specification](https://hl7.org/fhir/http.html#history), the sorting of versions defaults to the oldest version last. This bug fix, addresses FHIR server behavior for sorting history bundle.<br /><br />We understand if you would like to keep the sorting per existing behavior (oldest version first). To support existing behavior, we recommend you append `_sort=_lastUpdated` to the HTTP `GET` command utilized for retrieving history. <br /><br />For example: `<server URL>/_history?_sort=_lastUpdated` <br /><br />For more information, see [#2689](https://github.com/microsoft/fhir-server/pull/2689).
204287

205288

206-
#### MedTech service
289+
### MedTech service
207290

208291
**Improvements to documentations for Events and MedTech and availability zones.**
209292

@@ -216,6 +299,7 @@ Tested and enhanced usability and functionality. Added new documents to enable c
216299

217300
#### DICOM service
218301

302+
#### **Features**
219303

220304
**DICOM Service availability expands to new regions.**
221305

@@ -276,7 +360,7 @@ Attributes that are defined to have a single value but have specified multiple v
276360
#### FHIR service
277361

278362

279-
**Added FHIRPath Patch**
363+
** Added FHIRPath Patch**
280364
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.
281365

282366

@@ -311,17 +395,14 @@ Currently, WADO with Accept: multipart/related; type=application/dicom will thro
311395

312396
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).
313397

314-
315-
316398
## March 2022
317399

318-
319400
#### Azure Health Data Services
320401

321402
**Private Link is now available**
322403
With Private Link, you can access Azure Health Data Services securely from your VNet as a first-party service without having to go through a public Domain Name System (DNS). For more information, see [Configure Private Link for Azure Health Data Services](./../healthcare-apis/healthcare-apis-configure-private-link.md).
323404

324-
#### FHIR service
405+
### FHIR service
325406

326407
**FHIRPath Patch operation available**
327408
|This new feature enables you to use the FHIRPath Patch operation on FHIR resources. For more information, see [FHIR REST API capabilities for Azure Health Data Services FHIR service](./../healthcare-apis/fhir/fhir-rest-api-capabilities.md).
@@ -355,8 +436,6 @@ Enables easier deployment and use of MedTech service for customers without the n
355436

356437
## January 2022
357438

358-
#### FHIR service
359-
360439

361440
**Export FHIR data behind firewalls**
362441
This new feature enables exporting FHIR data to storage accounts behind firewalls. For more information, see [Configure export settings and set up a storage account](./././fhir/configure-export-data.md).
@@ -416,6 +495,7 @@ If SQL Server timed out, the PUT `/resource{id}` returned a 500 error. Now we ha
416495

417496
#### FHIR service
418497

498+
#### **Feature enhancements**
419499

420500
**Process Patient-everything links**
421501

@@ -473,6 +553,7 @@ We've updated Azure Health Data Services GitHub samples repo to include a 
473553
#### **DICOM service**
474554

475555

556+
**Regions**
476557

477558
**South Brazil and Central Canada.** For more information about Azure regions and availability zones, see [Azure services that support availability zones](https://azure.microsoft.com/global-infrastructure/services/).
478559

@@ -491,65 +572,43 @@ Enabled DICOM service to work with workspaces that have names beginning with a l
491572
#### FHIR service
492573

493574

494-
495-
**Added support for conditional patch [Conditional patch](./././azure-api-for-fhir/fhir-rest-api-capabilities.md#patch-and-conditional-patch)**
496-
497-
498-
Conditional patch [#2163](https://github.com/microsoft/fhir-server/pull/2163)
499-
500-
501-
Added conditional patch audit event. [#2213](https://github.com/microsoft/fhir-server/pull/2213)
502-
503-
504-
**Allow JSON patch in bundles**
505-
506-
507-
Allows for search history bundles with Patch requests. [#2156](https://github.com/microsoft/fhir-server/pull/2156)
508-
509-
510-
Enabled JSON patch in bundles using Binary resources.[#2143](https://github.com/microsoft/fhir-server/pull/2143)
511-
512-
513-
Added new audit event [OperationName subtypes](./././azure-api-for-fhir/enable-diagnostic-logging.md#audit-log-details) [#2170](https://github.com/microsoft/fhir-server/pull/2170)
514-
515-
**Running a reindex job**
516-
517-
Added [boundaries for reindex](./././azure-api-for-fhir/how-to-run-a-reindex.md#performance-considerations) parameters.[#2103](https://github.com/microsoft/fhir-server/pull/2103)
518-
519-
520-
Updated error message for reindex parameter boundaries.[#2109](https://github.com/microsoft/fhir-server/pull/2109)
521-
522-
523-
Added final reindex count check. [#2099](https://github.com/microsoft/fhir-server/pull/2099)
524-
525-
**Bug Fixes**
526-
527-
528-
Provided Wider catch for exceptions during applying patch [#2192](https://github.com/microsoft/fhir-server/pull/2192)
529-
530-
531-
Fixed history with PATCH in STU3 [#2177](https://github.com/microsoft/fhir-server/pull/2177)
532-
533-
534-
Addressed the delete failure with Custom Search parameters [#2133](https://github.com/microsoft/fhir-server/pull/2133)
535-
536-
537-
Added retry logic while Deleting Search parameter [#2121](https://github.com/microsoft/fhir-server/pull/2121)
538-
539-
540-
Set max item count in search options in SearchParameterDefinitionManager [#2141](https://github.com/microsoft/fhir-server/pull/2141)
541-
542-
543-
Better exception if there's a bad expression in a search parameter [#2157](https://github.com/microsoft/fhir-server/pull/2157)
544-
545-
546-
Resolved SQL batch reindex if one resource fails
547-
548-
Updated SQL batch reindex retry logic [#2118](https://github.com/microsoft/fhir-server/pull/2118)
549-
550-
**GitHub issues closed**
551-
552-
Unclear error message for conditional create with no ID [#2168](https://github.com/microsoft/fhir-server/issues/2168)
575+
|Enhancements | |
576+
| :------------------- | :------------------------------- |
577+
|Added support for conditional patch | [Conditional patch](./././azure-api-for-fhir/fhir-rest-api-capabilities.md#patch-and-conditional-patch)|
578+
|Conditional patch | [#2163](https://github.com/microsoft/fhir-server/pull/2163) |
579+
|Added conditional patch audit event. | [#2213](https://github.com/microsoft/fhir-server/pull/2213) |
580+
581+
|Allow JSON patch in bundles | |
582+
| :------------------- | :-------------------------------|
583+
|Allows for search history bundles with Patch requests. |[#2156](https://github.com/microsoft/fhir-server/pull/2156) |
584+
|Enabled JSON patch in bundles using Binary resources. |[#2143](https://github.com/microsoft/fhir-server/pull/2143) |
585+
|Added new audit event [OperationName subtypes](./././azure-api-for-fhir/enable-diagnostic-logging.md#audit-log-details)| [#2170](https://github.com/microsoft/fhir-server/pull/2170) |
586+
587+
| Running a reindex job | |
588+
| :------------------- | :-------------------------------|
589+
|Added [boundaries for reindex](./././azure-api-for-fhir/how-to-run-a-reindex.md#performance-considerations) parameters. |[#2103](https://github.com/microsoft/fhir-server/pull/2103)|
590+
|Updated error message for reindex parameter boundaries. |[#2109](https://github.com/microsoft/fhir-server/pull/2109)|
591+
|Added final reindex count check. |[#2099](https://github.com/microsoft/fhir-server/pull/2099)|
592+
593+
|Bug fixes | |
594+
| :------------------- | :-------------------------------- |
595+
| Wider catch for exceptions during applying patch | [#2192](https://github.com/microsoft/fhir-server/pull/2192)|
596+
|Fix history with PATCH in STU3 |[#2177](https://github.com/microsoft/fhir-server/pull/2177) |
597+
598+
|Custom search bugs | |
599+
| :------------------- | :------------------------------- |
600+
|Addresses the delete failure with Custom Search parameters |[#2133](https://github.com/microsoft/fhir-server/pull/2133) |
601+
|Added retry logic while Deleting Search parameter | [#2121](https://github.com/microsoft/fhir-server/pull/2121)|
602+
|Set max item count in search options in SearchParameterDefinitionManager |[#2141](https://github.com/microsoft/fhir-server/pull/2141) |
603+
|Better exception if there's a bad expression in a search parameter |[#2157](https://github.com/microsoft/fhir-server/pull/2157) |
604+
605+
|Resolved SQL batch reindex if one resource fails | |
606+
| :------------------- | :------------------------------- |
607+
|Updates SQL batch reindex retry logic |[#2118](https://github.com/microsoft/fhir-server/pull/2118) |
608+
609+
|GitHub issues closed | |
610+
| :------------------- | :------------------------------- |
611+
|Unclear error message for conditional create with no ID |[#2168](https://github.com/microsoft/fhir-server/issues/2168) |
553612

554613
#### **DICOM service**
555614

0 commit comments

Comments
 (0)