Merge pull request #230131 from kgaddam10/Febr-2023-Notes-2

Feb v2 content

Author: v-shils

articles/healthcare-apis/release-notes.md

@@ -19,9 +19,88 @@ ms.custom: references_regions
 
 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.
 
+## February 2023
+#### FHIR  service
+
+**Introduction of _till parameters and throughput improvement by 50x**
+
+_till parameter is introduced as optional parameter and allows you to export resources that have been modified till the specified time. 
+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)
+
+Also visit [Export your FHIR data by invoking the $export command on the FHIR service | Microsoft Learn](./../healthcare-apis/fhir/export-data.md)
+
+
+**Fixed issue for Chained search with :contains modifier results with no resources are returned**
+
+This bug-fix addresses the issue and identified resources, per search criteria with :contains modifier are returned. 
+
+For more details, visit  [#2990](https://github.com/microsoft/fhir-server/pull/2990) 
+
+
+
+**Provide the ability to tweak continuation token size limit with header.**
+
+
+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 that can be used to send this value is x-ms-documentdb-responsecontinuationtokenlimitinkb
+
+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](./../healthcare-apis/azure-api-for-fhir/overview-of-search.md)
+
+
+**Fixed issue related to HTTP Status code 500 was encountered when :not modifier was used with chained searches**
+
+This bug-fix addresses the issue. Identified resources are returned per search criteria with :contains modifier . for more details on bug fix visit  [#3041](https://github.com/microsoft/fhir-server/pull/3041) 
+
+
+**Versioning policy enabled at resource level still required If-match header for transaction requests.**
+
+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)
+
+
+
+
+#### MedTech service
+
+**Mapping Debugger released in public-preview**
+
+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. 
+
+For more information, visit [How to use the MedTech service Mapping debugger - Azure Health Data Services | Microsoft Learn](./../healthcare-apis/iot/how-to-use-mapping-debugger.md)
+
+
+
+**Error Message released in private-preview**
+
+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](./../healthcare-apis/iot/troubleshoot-errors-logs.md)
+
+
+
+
+
+#### DICOM service
+
+**New DICOM Event Types are GA**
+
+[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.
+
+
+**Validation errors included with the FailedSOPSequence**
+
+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.
+
+
+#### Toolkit and Samples Open Source
+
+
+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)
+
+
+
+
+
+
 ## January 2023
 
-#### Azure Health Data Services
+### Azure Health Data Services
 
 **Azure Health Data services General Available (GA) in new regions**
 
@@ -39,7 +118,11 @@ The DICOM service now supports `ModalitiesInStudy` as a [searchable attribute](d
 
 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).  
 
-#### Toolkit and Samples (Open Source)
+
+
+#### Toolkit and Samples Open Source
+
+
 **New sample app has been released**
 
 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
 
 **Fixed the Error generated when resource is updated using if-match header and PATCH**
 
-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)
+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)
 
 
-#### Toolkit and Samples (Open Source)
+#### Toolkit and Samples Open Source
 
 
 **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
 
 **Fixed issue where Querying with :not operator was returning more results than expected** 
 
-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). 
+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). |
 
 
 
@@ -135,11 +218,11 @@ The service will now accept the following:
 * IS, DS, SV, and UV VRs that are not valid numbers
 * Invalid private creator tags
 
-#### Toolkit and Samples (Open Source)
+#### Toolkit and Samples Open Source
 
 **The [Azure Health Data Services Toolkit](https://github.com/microsoft/azure-health-data-services-toolkit) is now in the public preview.** 
 
-The toolkit is open-source and allows you to easily customize and extend the functionality of their Azure Health Data Services implementations.  
+The toolkit is open-source and allows to easily customize and extend the functionality of their Azure Health Data Services implementations.  
 
 ## **August 2022**
 
@@ -170,7 +253,7 @@ Analytics pipeline can process FHIR extensions to generate parquet data. See [FH
 
 **Fixed issue related to History bundles being sorted with the oldest version first.** 
 
-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).
+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).
 
 **Fixed issue where Queries were not providing consistent result count after appended with `_sort` operator.**
 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
 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). 
 
 
-#### MedTech service 
+### MedTech service 
 
 **Improvements to documentations for Events and MedTech and availability zones.**
 
@@ -216,6 +299,7 @@ Tested and enhanced usability and functionality. Added new documents to enable c
 
 #### DICOM service
 
+#### **Features**
 
 **DICOM Service availability expands to new regions.**
 
@@ -276,7 +360,7 @@ Attributes that are defined to have a single value but have specified multiple v
 #### FHIR service
 
 
-**Added FHIRPath Patch**
+** Added 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. 
 
 
@@ -311,17 +395,14 @@ Currently, WADO with Accept: multipart/related; type=application/dicom will thro
 
 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). 
 
-
-
 ## March 2022
 
-
 #### Azure Health Data Services 
 
 **Private Link is now available**
 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).   
 
-#### FHIR service
+### FHIR service
 
 **FHIRPath Patch operation available**
 |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
 
 ## January 2022
 
-#### FHIR service
-
 
 **Export FHIR data behind firewalls**
 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
 
 #### FHIR service
 
+#### **Feature enhancements**
 
 **Process Patient-everything links**
 
@@ -473,6 +553,7 @@ We've updated Azure Health Data Services GitHub samples repo to include a 
 #### **DICOM service**
 
 
+**Regions**
 
 **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/). 
 
@@ -492,68 +573,73 @@ Enabled DICOM service to work with workspaces that have names beginning with a l
 
 
 
-**Added support for conditional patch [Conditional patch](./././azure-api-for-fhir/fhir-rest-api-capabilities.md#patch-and-conditional-patch)**
+**Added support for conditional patch**
 
+ 
+[Conditional patch](./././azure-api-for-fhir/fhir-rest-api-capabilities.md#patch-and-conditional-patch)
+[#2163](https://github.com/microsoft/fhir-server/pull/2163)
 
-Conditional patch [#2163](https://github.com/microsoft/fhir-server/pull/2163) 
-
-
-Added conditional patch audit event. [#2213](https://github.com/microsoft/fhir-server/pull/2213) 
-
+ 
+Added conditional patch audit event.  [#2213](https://github.com/microsoft/fhir-server/pull/2213) 
 
-**Allow JSON patch in bundles** 
+**Allow JSON patch in bundles**
 
 
 Allows for search history bundles with Patch requests. [#2156](https://github.com/microsoft/fhir-server/pull/2156) 
 
 
-Enabled JSON patch in bundles using Binary resources.[#2143](https://github.com/microsoft/fhir-server/pull/2143) 
+Enabled JSON patch in bundles using Binary resources. [#2143](https://github.com/microsoft/fhir-server/pull/2143) 
 
 
 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) 
 
+
+
 **Running a reindex job**
 
-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)
+ 
+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)
 
 
-Updated error message for reindex parameter boundaries.[#2109](https://github.com/microsoft/fhir-server/pull/2109)
+Updated error message for reindex parameter boundaries[#2109](https://github.com/microsoft/fhir-server/pull/2109)
 
 
-Added final reindex count check. [#2099](https://github.com/microsoft/fhir-server/pull/2099)
+Added final reindex count check.[#2099](https://github.com/microsoft/fhir-server/pull/2099)
 
-**Bug Fixes**
+**Bug fixes** 
 
 
-Provided Wider catch for exceptions during applying patch [#2192](https://github.com/microsoft/fhir-server/pull/2192)
+Wider catch for exceptions during applying patch [#2192](https://github.com/microsoft/fhir-server/pull/2192)
 
 
-Fixed history with PATCH in STU3 [#2177](https://github.com/microsoft/fhir-server/pull/2177) 
+Fix history with PATCH in STU3[#2177](https://github.com/microsoft/fhir-server/pull/2177) 
 
+**Custom search bugs** 
 
-Addressed the delete failure with Custom Search parameters [#2133](https://github.com/microsoft/fhir-server/pull/2133) 
 
+Addresses the delete failure with Custom Search parameters [#2133](https://github.com/microsoft/fhir-server/pull/2133) 
 
-Added retry logic while Deleting Search parameter  [#2121](https://github.com/microsoft/fhir-server/pull/2121)
 
+Added retry logic while Deleting Search parameter [#2121](https://github.com/microsoft/fhir-server/pull/2121)
 
-Set max item count in search options in SearchParameterDefinitionManager [#2141](https://github.com/microsoft/fhir-server/pull/2141) 
 
+Set max item count in search options in SearchParameterDefinitionManager [#2141](https://github.com/microsoft/fhir-server/pull/2141)
 
-Better exception if there's a bad expression in a search parameter [#2157](https://github.com/microsoft/fhir-server/pull/2157) 
 
+Better exception if there's a bad expression in a search parameter [#2157](https://github.com/microsoft/fhir-server/pull/2157)
 
-Resolved SQL batch reindex if one resource fails 
+**Resolved SQL batch reindex if one resource fails** 
+Updates SQL batch reindex retry logic [#2118](https://github.com/microsoft/fhir-server/pull/2118) 
 
-Updated SQL batch reindex retry logic [#2118](https://github.com/microsoft/fhir-server/pull/2118) 
+**GitHub issues closed** 
 
-**GitHub issues closed**
 
 Unclear error message for conditional create with no ID [#2168](https://github.com/microsoft/fhir-server/issues/2168) 
 
 #### **DICOM service**
 
-**Implemented fix to resolve QIDO paging-ordering issues** |  [#989](https://github.com/microsoft/dicom-server/pull/989) |
+**Implemented fix to resolve QIDO paging-ordering issues**  [#989](https://github.com/microsoft/dicom-server/pull/989) 
 
 
 #### **MedTech service**