You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/azure-api-for-fhir/export-data.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,9 @@ The Bulk Export feature allows data to be exported from the FHIR Server per the
17
17
18
18
Before using $export, you want to make sure that the Azure API for FHIR is configured to use it. For configuring export settings and creating Azure storage account, refer to [the configure export data page](configure-export-data.md).
19
19
20
+
> [!NOTE]
21
+
> Only storage accounts in the same subscription as that for Azure API for FHIR are allowed to be registered as the destination for $export operations.
22
+
20
23
## Using $export command
21
24
22
25
After configuring the Azure API for FHIR for export, you can use the $export command to export the data out of the service. The data will be stored into the storage account you specified while configuring export. To learn how to invoke $export command in FHIR server, read documentation on the [HL7 FHIR $export specification](https://www.hl7.org/fhir/uv/bulkdata/).
@@ -68,7 +71,7 @@ The Azure API for FHIR supports the following query parameters. All of these par
68
71
|\_isparallel| No |The "_isparallel" query parameter can be added to the export operation to enhance its throughput. The value needs to be set to true to enable parallelization. It is important to note that using this parameter may result in an increase in the request units consumption over the life of export. |
69
72
70
73
> [!NOTE]
71
-
> Only storage accounts in the same subscription as that for Azure API for FHIR are allowed to be registered as the destination for $export operations.
74
+
> There is a known issue with the $export operation that could result in incomplete exports with status success. Issue occurs when the is_parallel flag was used. Export jobs executed with _isparallel query parameter starting February 13th, 2024 are impacted with this issue.
Copy file name to clipboardExpand all lines: articles/healthcare-apis/azure-api-for-fhir/release-notes.md
+10-17Lines changed: 10 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,10 +22,12 @@ Azure API for FHIR provides a fully managed deployment of the Microsoft FHIR Ser
22
22
The query parameter _summary=count and _count=0 can be added to _history endpoint to get count of all versioned resources. This count includes soft deleted resources. For more information, see [history management](././../azure-api-for-fhir/purge-history.md).
23
23
24
24
**Improve throughput for export operation**
25
-
The "_isparallel" query parameter can be added to the export operation to enhance its throughput. It is important to note that using this parameter may result in an increase in Request Units consumption over the life of export. For more information, see [Export operation query parameters](././../azure-api-for-fhir/export-data.md).
25
+
The "_isparallel" query parameter can be added to the export operation to enhance its throughput. Its' important to note that using this parameter may result in an increase in Request Units consumption over the life of export. For more information, see [Export operation query parameters](././../azure-api-for-fhir/export-data.md).
26
+
> [!NOTE]
27
+
> There's a known issue with the $export operation that could result in incomplete exports with status success. Issue occurs when the is_parallel flag was used. Export jobs executed with _isparallel query parameter starting February 13th, 2024 are impacted with this issue.
26
28
27
29
**Change in name nomenclature for exported file name and default storage account**
28
-
With this change exported file names follow the format '{FHIR Resource Name}-{Number}-{Number}.ndjson'. The order of the files is not guaranteed to correspond to any ordering of the resources in the database.Default storage account name is updated to 'Export-{Number}'. There is no change to number of resources added in individual exported files.
30
+
With this change, exported file names follow the format '{FHIR Resource Name}-{Number}-{Number}.ndjson'. The order of the files isn't guaranteed to correspond to any ordering of the resources in the database.Default storage account name is updated to 'Export-{Number}'. There's no change to number of resources added in individual exported files.
29
31
30
32
31
33
**Performance Enhancement**
@@ -41,7 +43,7 @@ Conditional interactions can be complex and performance-intensive. To enhance th
41
43
$export operation now supports exporting versioned resources and soft deleted resources. For more information, see [Export query parameters](../../healthcare-apis/azure-api-for-fhir/export-data.md).
42
44
43
45
## **November 2023**
44
-
**Bulk delete capability now available**
46
+
**Bulk delete capability now available in preview**
45
47
`$bulk-delete' allows you to delete resources from FHIR server asynchronously. Bulk delete operation can be executed at system level or for individual resource type. For more information, see [bulk-delete operation](../../healthcare-apis/azure-api-for-fhir/bulk-delete-operation.md).
46
48
47
49
Bulk delete operation is currently in public preview. Review disclaimer for details. [!INCLUDE public preview disclaimer]
@@ -50,15 +52,6 @@ Bulk delete operation is currently in public preview. Review disclaimer for deta
50
52
51
53
Issue is now addressed and FHIR queries using continuation token with include/ revinclude, no longer report an exception. For details on fix, visit [#3525](https://github.com/microsoft/fhir-server/pull/3525).
52
54
53
-
## **July 2023**
54
-
**Feature enhancement: Change to the exported file name format**
55
-
56
-
FHIR service enables customers to export data with $export operation. Export can be conducted across various levels, such as System, Patient and Group of patients. There are name changes with exported file and default storage account name.
57
-
* Exported file names will follow the format \<FHIR Resource Name\>-\<Number\>- \<Number\>.ndjson. The order of the files is not guaranteed to correspond to any ordering of the resources in the database.
58
-
* Default storage account name is updated to Export-\<Number\>.
59
-
60
-
There is no change to number of resources added in individual exported files.
61
-
62
55
## **June 2023**
63
56
**Bug Fix: Metadata endpoint URL in capability statement is relative URL**
64
57
Per FHIR specification, metadata endpoint URL in capability statement needs to be an absolute URL.
@@ -74,7 +67,7 @@ For more details, visit [#3250](https://github.com/microsoft/fhir-server/pull/32
74
67
## **April 2023**
75
68
76
69
**Fixed transient issues associated with loading custom search parameters**
77
-
This bug fix address the issue, where the FHIR service would not load the latest SearchParameter status in event of failure.
70
+
This bug fix addresses the issue, where the FHIR service wouldn't load the latest SearchParameter status in the event of failure.
78
71
For more details, visit [#3222](https://github.com/microsoft/fhir-server/pull/3222)
79
72
80
73
## **November 2022**
@@ -89,7 +82,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
|Azure API for FHIR does not create a new version of the resource if the resource content has not changed. |If a user updates an existing resource and only meta.versionId or meta.lastUpdated have changed then we return OK with existing resource information without updating VersionId and lastUpdated. For more information, see [#2519](https://github.com/microsoft/fhir-server/pull/2519). |
85
+
|Azure API for FHIR doesn't create a new version of the resource if the resource content hasn't changed. |If a user updates an existing resource and only meta.versionId or meta.lastUpdated have changed then we return OK with existing resource information without updating VersionId and lastUpdated. For more information, see [#2519](https://github.com/microsoft/fhir-server/pull/2519). |
93
86
94
87
## April 2022
95
88
@@ -121,7 +114,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
|Duplicate resources in search with `_include`|Fixed issue where a single resource can be returned twice in a search that has `_include`. For more information, see [PR #2448](https://github.com/microsoft/fhir-server/pull/2448). |
124
-
|PUT creates on versioned update |Fixed issue where creates with PUT resulted in an error when the versioning policy is configured to `versioned-update`. For more information, see [PR #2457](https://github.com/microsoft/fhir-server/pull/2457). |
117
+
|PUT creates on versioned update |Fixed issue were creates with PUT resulted in an error when the versioning policy is configured to `versioned-update`. For more information, see [PR #2457](https://github.com/microsoft/fhir-server/pull/2457). |
125
118
|Invalid header handling on versioned update |Fixed issue where invalid `if-match` header would result in an HTTP 500 error. Now an HTTP Bad Request is returned instead. For more information, see [PR #2467](https://github.com/microsoft/fhir-server/pull/2467). |
126
119
127
120
## February 2022
@@ -220,8 +213,8 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments