Merge pull request #284479 from EXPEkesheth/patch-179

Aug release notes

Author: prmerger-automator[bot]

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

@@ -17,6 +17,14 @@ ms.author: kavitagaddam
 
 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.
 
+## **August 2024**
+
+### FHIR service
+
+**Bug Fixes** 
+A fix was implemented to address issues with large exports incorrectly displaying a "completed" status while child tasks are still processing. The solution incorporates a delay to mitigate the occurrence of these status errors, improving export reliability. 
+
+
 ## **July 2024**
 
 ### FHIR service

articles/healthcare-apis/fhir/import-data.md

@@ -204,7 +204,7 @@ Here are the error messages that occur if the `import` operation fails, along wi
 
 #### 200 OK, but there's an error with the URL in the response
 
-**Behavior:** The `import` operation succeeds and returns `200 OK`. However, `error.url` is present in the response body. Files present at the `error.url` location contain JSON fragments similar to this example:
+The `import` operation succeeds and returns `200 OK`. However, `error.url` is present in the response body. Files present at the `error.url` location contain JSON fragments similar to this example:
 
 ```json
 {
@@ -221,73 +221,35 @@ Here are the error messages that occur if the `import` operation fails, along wi
 }
 ```
 
-**Cause:** NDJSON files contain resources with conditional references that `import` doesn't support.
+Cause: NDJSON files contain resources with conditional references that `import` doesn't support.
 
-**Solution:** Replace the conditional references to normal references in the NDJSON files.
+Solution: Replace the conditional references to normal references in the NDJSON files.
 
 #### 400 Bad Request
 
-**Behavior:** The `import` operation fails and returns `400 Bad Request`. The response body includes this content:
+The `import` operation fails and returns `400 Bad Request`. The response body contains diagnostic content
 
-```json
-{
-    "resourceType": "OperationOutcome",
-    "id": "13876ec9-3170-4525-87ec-9e165052d70d",
-    "issue": [
-        {
-            "severity": "error",
-            "code": "processing",
-            "diagnostics": "import operation failed for reason: No such host is known. (example.blob.core.windows.net:443)"
-        }
-    ]
-}
-```
+**import operation failed for reason: No such host is known. (example.blob.core.windows.net:443)**
+Solution: Verify that the link to the Azure storage is correct. Check the network and firewall settings to make sure that the FHIR server can access the storage. If your service is in a virtual network, ensure that the storage is in the same virtual network or in a virtual network peered with the FHIR service's virtual network.
 
-**Solution:** Verify that the link to the Azure storage is correct. Check the network and firewall settings to make sure that the FHIR server can access the storage. If your service is in a virtual network, ensure that the storage is in the same virtual network or in a virtual network peered with the FHIR service's virtual network.
+**SearchParameter resources cannot be processed by import**
+Solution: The import operation returns a HTTP 400 error when a search parameter resource is ingested via the import process. This change is intended to prevent search parameters from being placed in an invalid state when ingested with an import operation.
 
 #### 403 Forbidden
 
-**Behavior:** The `import` operation fails and returns `403 Forbidden`. The response body contains this content:
-
-```json
-{
-    "resourceType": "OperationOutcome",
-    "id": "bd545acc-af5d-42d5-82c3-280459125033",
-    "issue": [
-        {
-            "severity": "error",
-            "code": "processing",
-            "diagnostics": "import operation failed for reason: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature."
-        }
-    ]
-}
-```
-
-**Cause:** The FHIR service uses a managed identity for source storage authentication. This error indicates a missing or incorrect role assignment.
+The `import` operation fails and returns `403 Forbidden`. The response body contains diagnostic content
 
-**Solution:** Assign the **Storage Blob Data Contributor** role to the FHIR server. For more information, see [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml?tabs=current).
+**import operation failed for reason: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.**
+Cause: The FHIR service uses a managed identity for source storage authentication. This error indicates a missing or incorrect role assignment.
+Solution: Assign the **Storage Blob Data Contributor** role to the FHIR server. For more information, see [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml?tabs=current).
 
 #### 500 Internal Server Error
 
-**Behavior:** The `import` operation fails and returns `500 Internal Server Error`. The response body contains this content:
-
-```json
-{
-    "resourceType": "OperationOutcome",
-    "id": "0d0f007d-9e8e-444e-89ed-7458377d7889",
-    "issue": [
-        {
-            "severity": "error",
-            "code": "processing",
-            "diagnostics": "import operation failed for reason: The database '****' has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions."
-        }
-    ]
-}
-```
-
-**Cause:** You reached the storage limit of the FHIR service.
+The `import` operation fails and returns `500 Internal Server Error`. The response body contains diagnostic content
 
-**Solution:** Reduce the size of your data or consider Azure API for FHIR, which has a higher storage limit.
+**import operation failed for reason: The database '****' has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.**
+Cause: You reached the storage limit of the FHIR service.
+Solution: Reduce the size of your data or consider Azure API for FHIR, which has a higher storage limit.
 
 ## Limitations
 - The maximum number of files allowed for each `import` operation is 10,000.

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

@@ -15,6 +15,16 @@ ms.custom: references_regions
 
 This article describes features, enhancements, and bug fixes released in 2024 for the FHIR® service, DICOM® service, and MedTech service in Azure Health Data Services.
 
+## August 2024
+
+### Azure Health Data Services
+
+### FHIR service
+
+#### Import operation error handling
+1. The import operation returns a HTTP 400 error when a search parameter resource is ingested via the import process. This change is intended to prevent search parameters from being placed in an invalid state when ingested with an import operation.
+2. The import operation will return a HTTP 400 status code, as opposed to the previous HTTP 500 status code, in cases where configuration issues with the storage account occur. This update aims to improve error handling associated with managed identities during import operations. 
+
 ## July 2024
 
 ### Azure Health Data Services