Skip to content

Commit ea4e7f3

Browse files
Merge pull request #275805 from EXPEkesheth/patch-166
Import data operation updates on performance optimization
2 parents b5374c3 + b6013dc commit ea4e7f3

File tree

1 file changed

+6
-28
lines changed

1 file changed

+6
-28
lines changed

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

Lines changed: 6 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ To achieve the best performance with the `import` operation, consider these fact
5858

5959
- **Use large files for import**. The file size of a single `import` operation should be more than 200 MB. Smaller files might result in slower import times.
6060

61-
- **Import FHIR resource files as a single batch**. For optimal performance, import all the FHIR resource files that you want to ingest in the FHIR server in one `import` operation. Importing all the files in one operation reduces the overhead of creating and managing multiple import jobs.
61+
- **Import FHIR resource files as a single batch**. For optimal performance, import all the FHIR resource files that you want to ingest in the FHIR server in one `import` operation. Importing all the files in one operation reduces the overhead of creating and managing multiple import jobs. The combined total size of all the files in a single import should be greater than 100 GB or 100 M resources.
6262

6363
- **Limit the number of parallel import jobs**. You can run multiple `import` jobs at the same time, but running multiple jobs might affect the overall throughput of the `import` operation. The FHIR server can handle up to five parallel `import` jobs. If you exceed this limit, the FHIR server might throttle or reject your requests.
6464

@@ -94,7 +94,7 @@ Content-Type:application/fhir+json
9494

9595
| Input part name | Description | Cardinality | Accepted values |
9696
| ----------- | ----------- | ----------- | ----------- |
97-
| `type`| Resource type of the input file. | 0..1 | A valid [FHIR resource type](https://www.hl7.org/fhir/resourcelist.html) that matches the input file. |
97+
| `type`| Resource type of the input file. | 0..1 | A valid [FHIR resource type](https://www.hl7.org/fhir/resourcelist.html) that matches the input file. This field is optional.|
9898
|`url`| Azure storage URL of the input file. | 1..1 | URL value of the input file. The value can't be modified. |
9999
| `etag`| ETag of the input file in the Azure storage. Used to verify that the file content isn't changed after `import` registration. | 0..1 | ETag value of the input file.|
100100

@@ -113,32 +113,15 @@ Content-Type:application/fhir+json
113113
{
114114
"name": "input",
115115
"part": [
116-
{
117-
"name": "type",
118-
"valueString": "Patient"
119-
},
120-
{
116+
{
121117
"name": "url",
122-
"valueUri": "https://example.blob.core.windows.net/resources/Patient.ndjson"
118+
"valueUri": "https://example.blob.core.windows.net/resources/filename.ndjson"
123119
},
124120
{
125121
"name": "etag",
126122
"valueUri": "0x8D92A7342657F4F"
127123
}
128124
]
129-
},
130-
{
131-
"name": "input",
132-
"part": [
133-
{
134-
"name": "type",
135-
"valueString": "CarePlan"
136-
},
137-
{
138-
"name": "url",
139-
"valueUri": "https://example.blob.core.windows.net/resources/CarePlan.ndjson"
140-
}
141-
]
142125
}
143126
]
144127
}
@@ -176,14 +159,9 @@ The following table describes the important fields in the response body:
176159
"request": "https://importperf.azurewebsites.net/$Import",
177160
"output": [
178161
{
179-
"type": "Patient",
162+
"type": <null in case type parameter in not populated in request. If provided, resource name will be added>,
180163
"count": 10000,
181-
"inputUrl": "https://example.blob.core.windows.net/resources/Patient.ndjson"
182-
},
183-
{
184-
"type": "CarePlan",
185-
"count": 199949,
186-
"inputUrl": "https://example.blob.core.windows.net/resources/CarePlan.ndjson"
164+
"inputUrl": "https://example.blob.core.windows.net/resources/filename.ndjson"
187165
}
188166
],
189167
"error": [

0 commit comments

Comments
 (0)